For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

santsboy_145140's avatar
santsboy_145140
Icon for Nimbostratus rankNimbostratus
Mar 06, 2014
Solved

BIG-IP awareness of VM vmotion from one DC to the other

Hi,   We have twin DCs active/active and I would like to know if BIG-IP WOM on 2 LTM BIG-IP load balancers (each load balancer in each DC), could be aware that a VM has moved from one DC to the ot...
application delivery
BIG-IP DNS
cloud
deployment
design
LTM
vmware
IheartF5_45022's avatar
IheartF5_45022
Icon for Nacreous rankNacreous
Mar 06, 2014

I don't think the BigIP will be aware - the IP/MAC will remain the same after vMotion, however you should be able to setup an external script that will detect the event (using Vcentre logs?) and then you can use iControl to disable the relevant node.

 

I have to ask - if you don't want to access the VM after a vMotion - why vMotion it? Or why not vMotion to a physical host within the same datacentre?

 

IheartF5_45022's avatar
IheartF5_45022
Icon for Nacreous rankNacreous
Mar 06, 2014
Ignore the last question - I hadn't fully read your question. If you setup the GTM to use VS Capacity mode, then as long as you have an equal number of members active at each DC you will get round-robin (which should give you 50/50, however once you start having members moved from site to site and disabled/enabled as we discuss above, then you will get a skew of traffic to the site with more capacity. I would imagine this would be a desirable behaviour.