Forum Discussion

NiHo_202842's avatar
NiHo_202842
Icon for Cirrostratus rankCirrostratus
Dec 27, 2016
Solved

Move vIP to other cluster

Hello,

 

So I have a 11.5.1 cluster where we are having some problems. We have a fresh 12.1.1 cluster ready to take over some vIPs for testing.

 

I would like to flawlessly move vIPs from the old cluster to the new one. I prefer not to import the configuration to evade corrupt config or duplicate address problems.

 

Current method: Disable ARP on the old Virtual Address & enable this on the new one + wait for the ARP entry to expire on the L3 switches. However, I can never ping the virtual address when enabled on the new cluster. Ideas? The switch sees the new MAC address, but the ping does not reply. (nor when I ping the vIP from the new bigip itself.)

 

To move it back to the old cluster, I disabled ARP on the new cluster and re-enabled it on the old cluster. Then I needed to wait for the ARP entry to expire on the switches.

 

(Comparable to https://devcentral.f5.com/articles/ruby-and-icontrol-migrating-virtual-addresses-using-arp )

 

  • It seems the issue was something on the self-ip, it worked!

     

4 Replies

  • Hi NiHo, I have a suggestion for you based on my personal experience. The steps I follow in a similar situation are: OLD CLUSTER 1) change the ip (with a fake ip) in the old VS 2) delete the ip address from Virtual Address list NEW CLUSTER 3) set the ip address in the new VS When set the new IP address, the F5 send a gratuitous arp to the upstream network, so the arp tables would adjust automatically, and no mac duplication would occour.

     

    regards

     

    Leonardo

     

    • NiHo_202842's avatar
      NiHo_202842
      Icon for Cirrostratus rankCirrostratus

      Hello Leonardo, thanks for responding! Did you also try just disabling & enabled ARP too?

       

    • Leonardo_Accor1's avatar
      Leonardo_Accor1
      Icon for Nimbostratus rankNimbostratus

      No, I have just deleted the ip address in the virtual address list. In my experience this work fine.

       

  • It seems the issue was something on the self-ip, it worked!