Virtual server address space on disaster recovery F5 instance
I am working on setting up a disaster recovery instance of an existing HA BIGIP pair. I would like to ConfigSync (sync only) my local devices to the new device which is located in a different data center. The issue is that if/when I needed to "fail over" (manually) to the new disaster recovery device, the IP space of the virtual servers are different. So for example if my virtual server "A" has a destination address of 192.168.1.10 in my existing data center, the new destination address might be 10.1.1.10. (Note: I am less worried about pool member IP space, because I can use priority groups and have the disaster recovery pool member IPs pre-configured but disabled). My first thought was a "DR go live" script which would search & replace the config file and reload it, but is there a more "elegant" way to handle this dilemma, without having them have the same IP space?
GTM and Topology
Hi, I am quite new to DNS/GTM stuff so I had no chance yet to dig into how Topology LB works and what can be done. Wonder if such configuration is possible: Setup: Two DC - DC1 and DR1 LDNS in each DC sending request to GTM (LDNS_DC1, LDNS_DR1) Servers in each DC - defined as Generic Host GTM serwing one Wide IP pointing to Servers in both DC I would like to achieve this result: When LDNS_DC1 sends request logic is: If there is any Srv active in DC1 return IP of any (based on RR) If there is no active Srv in DC1 return IP of any active Srv in DR1 (based on RR) When LDNS_DR1 sends request logic is: If there is any Srv active in DR1 return IP of any (based on RR) If there is no active Srv in DR1 return IP of any active Srv in DC1 (based on RR) So depending on which LDNS issued request logic is switched around. Is that possible without iRule using just LB available at Wide IP and Pool level? Side question: Which LB methods will work at all for Generic Host? I guess in this case all is based on analyzing communication between LDNS and GTM (no data that is provided when BIG-IP type of server is used)DNS (GTM) best practice for DR
Hi, I need to set DR based on DNS module. After reading few posts and docs all I know that there is plenty approaches that can be implemented. I have little experience with DNS module so I will appreciate any advice what will be optimum solution. Scenario: Two Data Centers: DC1 (main), DR1 (used only when resources in DC not available) Each DC uses non overlapping subnet ranges DCs connected via internal private L2/L3 link All DNS queries will only come from devices inside DCs In each Data Center single BIG-IP DNS device In each DC one host (let's call it Main) requiring DNS resolution for resources it has to access In each DS eight hosts (let's call them Slaves) with separate IP and FQDN - those are not LTMs but standard servers - Generic Host type (monitoring via HTTP monitor) DNS device should perform DNS resolution for FQDNs for Main host DR rules: If any Slave in DC1 is down, DNS request should be resolved to IP of any working Slave If all Slaves in DC1 are down, DNS request should be resolved to IP of any Slave in DR1 What would be best approach? As far as I understand Global Availability method should be used, but at what level: Pool Wide IP Is that better to create on Pool with members from both DSs or separate Pool - one per DC - each containing members from respective DC? Now how to handle condition to return IP of active Slave inside one DC? I guess I need to create as many WideIPs as Slaves (8), or rather one wildcard IP: slave1.vip.site.com, slave2.vip.site.com,...,slave8.vip.site.com or .vip.site.com Then how to perform returning IP of another active Slave when Slave for which DNS request was made is down - inside DC HA? Piotr
Welcome to the new Disaster Recovery and Business Continuity discussion forum
Welcome to the new Disaster Recovery and Business Continuity discussion forum newly consolidated in the Availability Group. We've created this forum as a place to post questions and discuss design, configuration, and customization of F5's BIG-IP product family. To get the background details on this powerful global load balancing solution, you can go here: http://www.f5.com/solutions/busines...ontinuity/. Additionally, you'll see some great answers and feedback from some of the leading disaster recovery and business continuity experts in the world - from F5 and other companies - that can help you determine the most effective way to configure your available assets to respond no matter what happens t keep your business running. Warm regards, JonathanHA Configuration (One in primary and One in DR)
Hi folks, I currently have HA pair (active/passive) in a primary data center and we are bringing up a DR. wondering can I split up the HA pair (One in primary and One in DR) and continue to have HA with utilizing different subnets? We are using multiple IPSEC tunnels to connect the sites so we are still working on whether we can extend subnets but if we can't I wanted to ask if different subnets are possible. Thank you any info is appreciated