For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Patrik_Jonsson's avatar
Patrik_Jonsson
Icon for MVP rankMVP
Aug 24, 2015

I'd advice for you to read the guides provided by F5.

https://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/bigip_getting_started_guide_10_1_0.html

That said, starting with the questions one by one hoping it will clear at least some things up:

The internal VLAN is normally used to host the servers you want to load balancer.

1. Self IP - I assume this is a unique IP address assigned to the box for internal connections. 
    The self IP is the IP each machine uses to communicate with each other and for monitoring.
2. Floating IP - this is used by both boxes and vdi will point to this address. 
    The floating IP is the one used ie. for for initiating traffic to pool members later on. Basically it can be owned by either box, depending on which one is active.
3. VLAN Interface - not sure what to pick here, 1.1. 1.2 or 1.3
    This depends on which interface you've configured as the internal VLAN in VMware. You can check what's what by comparing the Mac addresses (Network -> Interfaces) with the ones you have in VMware.
The external VLAN is used for incoming traffic that will be load balanced. The answers to the other questions are basically the same.

High Availability Network 
1. Self IP - another IP used for HA purposes I take it? 
Yes. In this case you don't need a floating IP.
2. VLAN interface?
 This depends on which interface you've configured as the HA VLAN in VMware. You can check what's what by comparing the Mac addresses (Network -> Interfaces) with the ones you have in VMware.

Hope that helps some.

/Patrik