Forum Discussion
jayson27
Cirrus
CirrusChanging the VS IP of DR Site to Production IP
Hi, Requesting your guidance. We are planning to replicate the VSIP of production device to our DR device. I'm wondering if this will cause a IP conflict. If I will disable the ARP and ICMP of ...
I still don't quite get your environment, do you perhaps a drawing?
You write about a production and disaster recovery IP, are those for virtual servers or self IP addresses of the BIG-IP?
I sort of expect something like this.
There is a production BIG-IP with virtual server with IP address 192.168.10.10. You want that same IP address on the disaster recovery BIG-IP so that if the production BIG-IP fails you can enable it on disaster recovery BIG-IP. For that to work you would have to add the 192.168.10.10 virtual IP on the disaster recovery BIG-IP but disabled and not responding to pings. Then afterwards you can add the rest of the virtual server configuration.
One question I still have is why the setup with a production and disaster recovery BIG-IP? Create a cluster and you have a way better way to handle one system breaking down.
whisperer
MVP
MVPI dont quite understand this on several levels....
- Usually you have services setup as Pool Members and use a singular application VIP. You failover the Pool Members. If you are across 2 datacenters and have LOW latency, you can get away with HA and a traffic group (also assuming you are spanning that network space).
- The other way would be to use DNS based failover using the GTM/DNS module. You would change the advertisement of the IP address of the VIP or server depending upon automatic health monitored conditions or manually modifying the Pool or failing over a Datacenter.
Both of those VIPs are in the same subnet. Are you performing routing changes to only advertise the 10.0.10.0/24 in one datecenter? If so, why use different IP addresses? Just perform the routing change.