Solution for duplicate F5 Self IP's at two datacenters using OTV
We are planning a migration of a F5 LTM VIPRION pair in datacenter A to a F5 LTM VE pair in datacenter B. We would like to do this in a phased approach (bringing waves of servers at a time) and keeping all IP addresses the same (servers, VIP's, self IP's, VLAN ID's, route domains, gateway, routes etc.) We are using OTV to extend the Layer 2 networks across the datacenters. My concern is duplicate self IP addresses between the F5's, because you cannot disable ARP for a F5 self IP like you can for an F5 VIP. I was thinking to do something like this to support the F5's at Datacenter A and B to operate simultaneously. Perhaps blocking the F5 MAC addresses of Datacenter A from reaching Datacenter B and vis versa: Cisco: mac-list F5-OTHER-DC_vMAC seq 10 deny 0000.xxxx.xxx1 ffff.ffff.ffff mac-list F5-OTHER-DC_vMAC seq 11 deny 0000.xxxx.xxx2 ffff.ffff.ffff mac-list F5-OTHER-DC_vMAC seq 20 permit 0000.0000.0000 0000.0000.0000 route-map F5-OTHER-DC_Filtering permit 10 match mac-list F5-OTHER-DC_vMAC otv-isis default vpn Overlay200 redistribute filter route-map F5-OTHER-DC_Filtering Is this a supported design? Thanks!BIG-IP DNS with vmotion/SRM/OTV - 2DC's
Hey everyone - We have an active DC and a cold DC. (meaning, the cold DC would not have active running VM's. If there is a failure, a VM will use SRM/vmotion to transfer to the other DC). My question is, if the VM host networking stays the same and use the same default gateway. Traffic will continue to use the Default Gateway through DC1. Will the BIG-IP DNS be able to detect the failure (through iQuery) since the LTM would not? Is there an advanced monitor I could use on the BIG-IP DNS box to detect a failure of the VM or LTM VIP and then remain on the switched Public IP? Thanks!