Monday, January 27, 2014

F5-BIG-IP Redundancy Configuration

Used BIG-IP Config Utility (GUI) to setup the Redundancy.

Followed Steps as mentioned in Creating an Active-Standby Configuration Using the Setup Utility

    | external                 external |
    |                                   |
[bigip1]-----------------------------[bigip2]
    |   HA                        HA    |
    | internal                internal  |

Three different networks needs to be configured for internal/external and HA VLANs

After giving IP addresses to each interface (internal, external and HA). Make sure, you are able to ping external/internal and HA interface from each BIG-IP appliance to other BIG-IP appliance.

You need to create Floating IP for internal and external interfaces only. This configuration has to be done on each bigip appliance.

After the second device has discovered (Steps in "Discovering a peer device" Section in Creating an Active-Standby Configuration Using the Setup Utility) the first device, the two devices have a trust relationship and constitute a two-member device group. Also, each device in the pair contains a default traffic group named Traffic-Group-1. By default, this traffic group contains the floating IP addresses that you defined for VLANs internal and external.

At this time, both the devices are paired, and prompt changes to Active (bigip2 in my case):-
root@(bigip2)(cfg-sync Awaiting Initial Sync)(Active)(/Common)(tmos)#

and on standby it looks like

root@(bigip1)(cfg-sync Awaiting Initial Sync)(Standby)(/Common)(tmos)#


Go ahead and change some config on e.g. bigip2 (Say create a pool and add member node to it). You can see the prompt changed to "Changes Pending" on Active and Standby as below:-
root@(bigip2)(cfg-sync Changes Pending)(Active)(/Common)(tmos)#

root@(bigip1)(cfg-sync Changes Pending)(Standby)(/Common)(tmos)#

Now, its time to Sync the Config.

Follow Synchronizing the BIG-IP configuration section. If all goes well, then the prompt changes to:-
root@(bigip2)(cfg-sync In Sync)(Active)(/Common)(tmos)#
root@(bigip1)(cfg-sync In Sync)(Standby)(/Common)(tmos)#

You can also verify that the config done on Active (bigip2) is not present on Standby (bigip1).

Sync status for device groups





4 comments:

  1. This comment has been removed by the author.

    ReplyDelete
  2. Hello! I just would like to give a huge thumbs up for the great info you have here on this post. I will be coming back to your blog for more soon. http://www.dbcomp.ie/products/virtualization/

    ReplyDelete
  3. You know your projects stand out of the herd. There is something special about them. It seems to me all of them are really brilliant! bookmetoday.com

    ReplyDelete