People keep mentioning ConfigSync when ConfigSync is NOT the issue. Forgive the frustration, but I've beaten my head against this for two days. Yes, I have opened a ticket. I have the same exact issue. Both LTMs are synced, but on the Primary LTM the traffic group lists only the Active LTM--as "current device"
Underneath that is "Next Active DeviceInitializing / Not Synced"
Essentially, the active F5 does not see the standby as being in its traffic group, even though both appear in the HA order box, even though the standby does sees the active. The gui on each is exactly the same, save that on the standby, the correct ltm name appears as "Next Active Device"
Testing this on a virtual pair with no traffic, andI found that if I force the primary to standby,
1. The previous standby LTM will go Active
2. Then the originally active LTM goes active AGAIN
3. And the previous standby LTM falls back to standby.
So the standby LTM behaves as it should, but as far as the primary is concerned, it is the only active ltm in the traffic group. Auto-failback is NOT enabled on either LTM