Design Reference
Table Of Contents
- Contents
- Chapter 1: Introduction
- Chapter 2: New in this release
- Chapter 3: Network design fundamentals
- Chapter 4: Hardware fundamentals and guidelines
- Chapter 5: Optical routing design
- Chapter 6: Platform redundancy
- Chapter 7: Link redundancy
- Chapter 8: Layer 2 loop prevention
- Chapter 9: Spanning tree
- Chapter 10: Layer 3 network design
- Chapter 11: SPBM design guidelines
- Chapter 12: IP multicast network design
- Multicast and VRF-Lite
- Multicast and MultiLink Trunking considerations
- Multicast scalability design rules
- IP multicast address range restrictions
- Multicast MAC address mapping considerations
- Dynamic multicast configuration changes
- IGMPv3 backward compatibility
- IGMP Layer 2 Querier
- TTL in IP multicast packets
- Multicast MAC filtering
- Guidelines for multicast access policies
- Multicast for multimedia
- Chapter 13: System and network stability and security
- Chapter 14: QoS design guidelines
- Chapter 15: Layer 1, 2, and 3 design examples
- Chapter 16: Software scaling capabilities
- Chapter 17: Supported standards, RFCs, and MIBs
- Glossary
Figure 44: Traditional routing before moving VMs
A VM is a virtual server. When you move a VM, the virtual server is moved as is. This action means
that the IP addresses of that server remain the same after the server is moved from one data center
to the other. This in turn dictates that the same IP subnet (and hence VLAN) exist in both data
centers.
In the following figure, the VM moved from the data center on the left to the data center on the right.
To ensure a seamless transition that is transparent to the user, the VM retains its network
connections through the default gateway. This method works, but it adds more hops to all traffic. As
you can see in the figure, one VM move results in a complicated traffic path. Multiply this with many
moves and soon the network look like a tangled mess that is very inefficient, difficult to maintain,
and almost impossible to troubleshoot.
Reference architectures
January 2015 Network Design Reference for Avaya VSP 4000 Series 93
Comments? infodev@avaya.com