Floating IPs uses IP addresses from Virtual Interfaces to masquerade the outbound traffic despite they’re going over a NIC, VLAN or Bonding interface in both nodes of the cluster. So when the cluster changes its master node, services (I.e. Farms) created over a Floating IP of the cluster will be switched from one node to another transparently without affecting to the clients, backends connections or data streams.

Floating IPs Table

This table lists all the Floating IPs configured in the system and will also be shown any interface with a configuration set where a Floating IP can be configured.

Interface. Name of the parent interface, which could be a physical NIC, VLAN or bonding interface. In brackets appears the alias of that interface if it is defined. The interface must have a configuration prior to being shown in this section.
Virtual Interface. Name of the virtual interface associated with the floating IP. In brackets appears the alias in the case that it is configured.
Floating IP. The network-layer IP address of the virtual interface configured as floating IP or “Not configured” if there is not a floating IP configured on the interface.
Actions. The actions available for floating IPs are the following:

• Configure. Assign a Floating IP to its parent interface. Only one floating interface can be configured per parent.
• Unset. Clear the configuration and remove the floating IP.

Using the Actions menu button you can apply one of the previously described actions to each selected interface. To select one or more interfaces, use the checkbox located on the first column.