F5 BIG-IP Basic Nomenclature

[@sameerkumar1884]

No matter how many times I these guys explaining topics, I always find something new... Thanks for you putting this up...

[@amricanca]

Guys, this is a bit misleading. In Cisco world an Etherchannel is not necessarily a trunk. I have Etherchannel that is configured as an access port on a Vlan.

[@THAT.RANDOM.GUY_]

Exactly. Trunking relates to 802.1Q whereas etherchannel relates to interface bundles or NIC teaming as some literature call it.

[@johnweaver6297]

Speaking of clarifying terms, what is referred to here as an "interface" is more appropriately called a "network interface card (NIC)," or "network interface."

[@abhijithks7419]

Jason and john : great video firstly, one query. When I have snat with automap, does it take the self ip or floating ip for my translation ? Assuming that my Devices are in HA.

[@JasonRahm]

abhijith ks snat automap will use the floating self as first preference, see support.f5.com/csp/article/K7336

[@taoli5497]

谢谢。

[@DinushaMadusankaChandrasinghe]

F5 Nomenclature quite similar to the HPE/Aruba world

[@lekeoluwatosin]

So pool member=Node+Port literally?

[@devcentral]

+Leke Oluwatosin (Laykay) pool member=node+port, yes. A Pool is a collection of node+port resources.

[@devcentral]

+Leke Oluwatosin (Laykay) thanks for the question! A node is a logical object on the BIG-IP that identifies the IP address of a physical resource on the network. A pool member is a logical object that represents a physical node (and a service) on the network. So, a node is the IP address while a pool member is the IP address and service port. Here's more info if you're interested: support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm_configuration_guide_10_0_0/ltm_pools.html

[@saqibrana7518]

its a confusing orientation. I was not expecting this from such big guns of F5.

[@devcentral]

Sorry to hear that! We did reshoot this video in lightboard format, hopefully the update is a little less confusing for you: kzbin.info/www/bejne/aIq1fIevgsyJaq8.

[@saqibrana7518]

yeaup this video is informative thanks.

[@nitinahuja2472]

Are node & VIP same thing?

[@devcentral]

+Nitin Ahuja no, a node object is just an IP address, pool members are IP address plus a port. So you could use ip-based monitors like ping to ensure availability of the node and tcp/udp/etc monitors to ensure availability of the different services available at that IP address. A virtual server is also IP+port (or IP alias/port alias) that is the basic block of how traffic is serviced by the BIG-IP. If there is no vip, there is no traffic allowed through the box.

[@devcentral]

+Nitin Ahuja Thanks for the great question! Node and VIP are not the same thing. A VIP is a virtual server on the BIG-IP (those terms are used interchangeably), and a node is the IP address of a physical device on the network. I know there are a lot of terms floating around here, so this link may provide a little more clarification on everything: devcentral.f5.com/questions/node-vs-member

[@Ruchikun]

Pity you jumped over the Vlan Group functionality so carelessly. It's not a basic concept. Considering you can literally vlan group 2 overlapping subnets.