How to safely switch from Multicast Heartbeats to Unicast Heartbeats?
I have a cluster of 4 SteelApp Traffic Managers that has always been using multicast communication for heartbeats between TMs.
I want to do big network changes that will make multicast temporarily unavailable. Because of this, I plan to fully switch the cluster to unicast communication. At least for the time of the network migration.
How does a cluster behave if you switch it to unicast? In case of failure I am mainly worried about a TM unable to communicate with the others, trying to grab all traffic group IP addresses.
Is there a way to do this change safely? Maybe disabling temporarily fault tolerance?
Re: How to safely switch from Multicast Heartbeats to Unicast Heartbeats?
There shouldn't be any problems. A TCPDUMP on my system during a multicast to unicast conversion, it just keeps ticking. So long as the STM's can see each other and can communicate via UDP 9090, you should be good.
root@i-stm001:~# tcpdump -ni any udp port 9090
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode