Forum Discussion
jomedusa
Altostratus
AltostratusLTM 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...
jomedusaAltostratus
AltostratusMy ultimate goal will be to have only 2 devices in the traffic group for failover as we will be decommisioning 2 of the LTM's later this year.
From the image below I would like to ultimately only have the padf5-core1 and padf5-core2 in the traffic group, but currenly all the traffic is on Pad-F5-2.
Can you please provide more information on the iqdump?
Thanks,
whisperer
MVP
MVPDo you have more than one traffic group configured? That is another instance where you would have more than one F5 unit active. If the traffic groups are not on the same unit, then multiple units may be active. If you need to move connections ASAP, just force offline the problematic F5 unit.
Looks like the devices should all see each other and configs are synced. So there shouldnt be any issue with network failover, the port lockdown settings, or iquery comms in this case. (If you log into each unit and the standby / active devices all look the same in GUI .. connected, grey balls or green balls, same ball colors, etc. then connectivity wise you should be OK. I would check the traffic groups.
- jomedusa
Yes we have seperate traffic groups for each Partition. My goal is migrate each Partion/Traffic group to the new LTM in phases. I know I have moved between all of the devices in the past but I am not sure I have since we performed an upgrade a few months ago. I think I am going to migrate traffic off the "problem one" this weekend and then perform a reboot. I have held off on this but I am pretty sure I am hitting a known issue where the versions don't show up correctly from one device to another, I have had this in the past and had to perform the following:
K13030: Forcing the mcpd process to reload the BIG-IP configuration
https://support.f5.com/csp/article/K13030
Thanks,
Joe
- whisperer
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
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