Forum Discussion
swo0sh_gt_13163
Altostratus
AltostratusHigh Availability - functions well, however peer device shows offline.
Hello Folks,
I have 2 LTM deployed in HA, running over firmware version 11.2.0 However, one of the devices shows offline status in peer list. At the same time the device is in Sync, failover works well too. However in peer list of Primary device, I can see secondary appliance as offline.
Anyone had experience similar issues before? What could be the possible and feasible solution?
Regards, Darshan
I ran across this thread while troubleshooting a similar issue, and I thought I would add what corrected the issue on my end. After clustering my 2, 6900s the configurations sync'd but the HA status for the peer device showed down (on both 6900s). After going round and round, I found that my HA self IPs on each device were set for "allow none". I changed them to "allow default" and BAM! Issue fixed.
Chris
Bart_Mollemans_Nimbostratus
at Chris, Many, many, many Thanks maestro!
jonathan_west_2Had the same issue, thought I'd tried everything. This fixed it. Thanks
VK_136173"Allow default" fixed it for me. Thanks.
OmarHenn_69084Had the same issuu running 11.4.1. Sync OK, HA OK, but overview stating connectivity problems to one box. Health check did not show anything wrong. After reading this thread I found an interface set to "allow none" after changing that to "allaow default" communication probem message dissapeard.
regards Omar
swo0sh_gt_13163Hi Chris,
Thank you very much to share your observation and findings. Of course this would be helpful while troubleshooting similar issue.
Appreciate your effort to post an answer of this query.
Thanks, Darshan
Chris_18457Cirrus
I ran across this thread while troubleshooting a similar issue, and I thought I would add what corrected the issue on my end. After clustering my 2, 6900s the configurations sync'd but the HA status for the peer device showed down (on both 6900s). After going round and round, I found that my HA self IPs on each device were set for "allow none". I changed them to "allow default" and BAM! Issue fixed.
Chris
san2hosh_306591This fixed my issue. Thanks a lot.
Patrick_Hendri1Still does the trick in 12.1.1. Did my lab setup by the book, but this one messed it up. So both units were active, but didn't see eachother. Changed the port lockdown on both ends to 'Allow Default' and BAM! working... Tnx!
- cmdpowell_16878"Allow default" fixed it for me, too. Thanks!
natheCirrocumulus
Can we presume that the other way round i.e. from the secondary device's GUI, the status of the primary looks ok? What about if you failover to the secondary, does the old primary (now secondary) appear offline?
afedden_1985Do you see the Serial number of the peer and its mac address in the Peer list to the right of the pers host name If not the Trust is not setup correctly
- swo0sh_gt_13163
Yes, I tried to even break the trust and re-bond the trust back. However it didn't work though.
- afedden_1985
from Device management> Device trust>peer List The only time I saw issues with the peer is when the trust was not set up correctly Do you see the Serial number of the peer and its mac address in the Peer list to the right of the pers host name?