F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

Gopinath_Vedagi's avatar
Gopinath_Vedagi
Icon for Nimbostratus rankNimbostratus
Dec 03, 2013

LTM 4000s - Transit Vlan Active Standby Setup

It's new for me to work with F5 LTM box after saying goodbye to cisco LB . We bought a set of LTM 4000s boxes in new DC to work in active - standby concept using transit vlan .   I tried for pas...
deployment
design
Kevin_K_51432's avatar
Kevin_K_51432
Historic F5 Account
Dec 04, 2013

Hi, usually this can be caused by a few simple issues. The most popular is failing to define the failover and config sync IPs for the device. Sounds like that is complete. The next popular issue is the time on the devices is greater than one minute apart. Ensure they are using NTP and less than one minute in difference. Also, be sure you are adding the peer to trust domain by using the management IP address.

tmsh  list sys management-ip
sys management-ip 172.24.112.20/24 { }

One last trick that sometimes works if everything is correct above. Add device_1 to trust domain from device_2, wait a few minutes, then add device_2 from device_1.

/var/log/ltm can be helpful. This solution covers everything related to device group troubleshooting if you want to become well versed on the topic.

http://support.f5.com/kb/en-us/solutions/public/13000/900/sol13946.html?sr=33650106