It’s hard for me to admit, but there just might be a corner use case for split subnets and inter-DC bridging: even if you move a cold VM between data centers in a controlled disaster avoidance process (moving live VMs rarely makes sense), you might not be able to change its IP address due to hard-coded IP addresses, be it in application code or configuration files.
Disaster recovery is a different beast: if you’ve lost the primary DC, it doesn’t hurt if you instantiate the same subnet in the backup DC.
Read more ...Thanks for reading my news about IP renumbering in disaster avoidance Data Center designs at my blog Bros Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.
More Articles :
Link Aggregation with Stackable Data Center Top-of-Rack Switches- Nexus 6000 and 40GE – why do I care?
- Intra-Spine Links in Leaf-and-Spine Fabrics
- How would you like to configure Policy-Based Routing (PBR)
- The Saga of Oversubscriptions
- Redundant Data Center Internet Connectivity – High-Level Design
- Hyper-V Network Virtualization (HNV/NVGRE): Simply Amazing
- Redundant Data Center Internet Connectivity – Problem Overview
- Long-Distance vMotion, Stretched HA Clusters and Business Needs
- NEC Launched a Virtual OpenFlow Switch – Does It Matter?