setting up redundant pair

The only way to set it up is via the GUI.

 

 

Here is the following criteria for setting up HA (Basic setup)

 

1. You need to connect the 2 LTMs via Serial Cable (Special one provided by F5.).

 

2. Create a VLAN and create a self-address on each

 

Example:

 

BIGIP1

 

- VLAN Internal

 

- Self Address: 192.168.1.2

 

- Floating Address: 192.168.1.1

 

- VLAN External

 

- Self Address: 192.168.2.2

 

- Floating Address: 192.168.2.1

 

 

BIGIP1

 

- VLAN Internal

 

- Self Address: 192.168.1.3

 

- Floating Address: 192.168.1.1

 

- VLAN External

 

- Self Address: 192.168.2.3

 

- Floating Address: 192.168.2.1

 

 

 

 

Hope this helps.

 

CB

 

Do you know does the serial cable come with the devices or does it come with the devices?

 

I am doing thesis for my school and dont know if the cable came with devices...

 

I´ll try to manage. thanks for help!

A cable should have come with the units. If they didn't then i believe you can ask your F5 rep to see if one can be sent. You can also make your own based on pin-outs which is published on the ask.f5.com site.

 

 

CB

 

Hi again,

 

 

One stupid question again. Do I connect the devices to each other by which physical interfaces? Dont remember if there was failover interface behind the the switch...

Hi

 

 

I got cable and devices are connected. Fail over seems to work, tested it by shutting down device and the other became active, but I cant connect the GUI via network. As a single device it works fine but when I activate redundant pair, I cannot connect the device. I have unit 1 self IP 172.16.50.101, Unit 2 self IP 172.16.50.102 and floating IP 172.16.50.100. What goes wrong??? Ping seemed to work at some moment...

Can you connect to each device's non-floating IP? If so, that's a good bit of data, and you're probably dealing with ARP issues - especially if you've been doing fail over testing with frequent fail overs. The reason why is that BigIP issues a gratuitous ARP for all floating addresses (and virtual servers). In certain situations devices may not honor the GARP update and you've got bad arp caches laying around the network. Try this:

 

 

1) Confirm you can log on to each unit's self-ip address (.101 and .102 in your case).

 

2) If you can, great. Go to the active unit via SSH and run 'b load', which will force another gratuitous arp out onto the network and will hopefully coax a few more systems to update their caches. If this doesn't work, you may want to clear the arp tables on your switches.

 

 

If you can't get to the self-ips at all, then you're probably dealing with other problems.

 

 

I hope this helps.

 

 

-Matt

Also check port lockdown. Set it for allow all to be sure you arent blocking something.