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

jomedusa's avatar
jomedusa
Icon for Cirrus rankCirrus
Jul 05, 2023

LTM Traffic group failover

We have 4 LTM's in a device group and moved one of our Traffic groups to a different LTM a few weeks ago.  All 4 devices show that padf5-core1.csiweb.com (the LTM it was moved to) as the active devic...
application delivery
whisperer's avatar
whisperer
Icon for MVP rankMVP
Jul 05, 2023

Well, that is why you have a mish mash of active devices. It all depends where that traffic group is located. The shared objects, such as Virtual Servers, associated with that traffic group will still process traffic on the unit where that traffic group is active.

Not sure what you mean by versions btw. Are you suggesting the units are running different version of BIG-IP software (that shouldnt be the case) or that the configs are out of sync?

jomedusa's avatar
jomedusa
Icon for Cirrus rankCirrus
Jul 05, 2023

Version of padf5-core1

Device listing from PadF5-2 shows wrong version for 2 devices, all devices are running the same version and have been verified multiple times.  I had this issue when upgrading to 13.5.X as well and the "workaround" was do a a force load on all 4 devices.

CORESERVICES VIP on PADF5-2 (it is active but not for this traffic group) all the traffic is still being processed by this LTM.

Even PADF5-2 reflects that padf5-core1 shold be the active device.

No stats or data present on padf5-core1

padf5-core1 should be the primary for that traffic group and it would allow the option to Force to standby.

We have split traffic in the past betwen our different traffic groups without issue.

Thanks,

Joe