Forum Discussion

Matthew_59082's avatar
Icon for Nimbostratus rankNimbostratus
Jul 05, 2011

Both LTM HA Peers going active.




I am having a problem with two HA peers, both are LTMs running 10.1.0. Both peers will go active and stay active no matter what.



I have the HB network on a dedicated link between the two LTMs, they can ping and config sync accross the HB network, this works everytime. I have to keep one LTM forced offline, and if I release it, it will go standby then active. If I force one to standby a few seconds later it goes back to active.



Virtual servers continue to work even when they both go active, I think this is because the second unit is not second a gratuitous arp. One unit has LVM, the other is on partitions thats the only difference between the LTMs, otherwise my setup is mirroring the setup used in another DC and it works fine.



How can I get a better view of the HA process? The LTM log simply gives a line "Standby" then "Active" but not the reason why.





7 Replies

  • nathe's avatar
    Icon for Cirrocumulus rankCirrocumulus



    Have you tried running a tcpdump on both LTMs to make sure the network heartbeat is reaching the other device?



    Also, is Redundancy State Preference set on both LTMs? Could you have both set as Active?



    Hope this helps


  • If the configuration is okay and the network between the two units is reachable, then it might be a resource issue where the failover state daemon isn't able to send heartbeats to the peer. You could open a case with F5 Support to get help diagnosing the issue.



  • Mathew,



    Is it possible for you to use or try the "hardwire" failover?
  • Thanks for all the replies...



    I haven't used tcpdump yet, that's a good idea I'll do that now. I'm looking for port tcp port 1026?



    The units are idle, so i don't think they're out of resources, unfortunately I cannot use hardwire failover either.
  • I can see the HA messages going back and forth.



    16:24:48.793179 IP >


    16:24:48.810475 IP >


    16:24:48.893170 IP >


    16:24:48.910457 IP >



    The LTMs just seem to be ignoring each other.
  • The start URL have to be the url that host Login Page.


    In fact is URL that will be trigged your SSO. when you will be in the login page, just retrieve the url where you are (Via F12 to be sure or you can see it in your web bar)...