400-007 · Question #298
A customer migrates from a traditional Layer 2 data center network into a new SDN-based, spine- and-leaf VXLAN EVPN data center within the same location. The networks are joined to enable host…
The correct answer is B. Shut down legacy Layer 3 SVIs and activate new preconfigured Layer 3 SVIs on VXLAN. The final migration step to cut Layer 3 traffic over to a VXLAN EVPN fabric - without touching host configuration - is to disable legacy default gateway SVIs and enable their preconfigured VXLAN equivalents.
Question
A customer migrates from a traditional Layer 2 data center network into a new SDN-based, spine- and-leaf VXLAN EVPN data center within the same location. The networks are joined to enable host migration at Layer 2. What is the final migration step, after hosts have physically migrated, to have traffic flowing through the new network without changing any host configuration?
Options
- AIncrease VRRP priorities on new infrastructure over legacy VRRP values, then shut down legacy SVIs.
- BShut down legacy Layer 3 SVIs and activate new preconfigured Layer 3 SVIs on VXLAN.
- CShut down legacy infrastructure to allow VXLAN gateways to become active.
- DShut down legacy Layer 3 SVIs, clear ARP caches on all hosts being migrated, and then configure the
How the community answered
(40 responses)- A25% (10)
- B55% (22)
- C8% (3)
- D13% (5)
Why each option
The final migration step to cut Layer 3 traffic over to a VXLAN EVPN fabric - without touching host configuration - is to disable legacy default gateway SVIs and enable their preconfigured VXLAN equivalents.
VXLAN EVPN uses distributed anycast gateways, not VRRP, so adjusting VRRP priorities is not the correct mechanism for gateway failover in this architecture.
After hosts physically migrate, the legacy Layer 3 SVIs still serve as their default gateways. Shutting those SVIs down and activating the pre-staged VXLAN Layer 3 SVIs transfers the gateway function to the new fabric using the same IP addressing, so hosts route through VXLAN automatically with no local reconfiguration needed.
Shutting down all legacy infrastructure simultaneously is too disruptive and does not allow for a controlled, surgical cutover of just the Layer 3 gateway function.
Clearing ARP caches forces unnecessary host re-learning, and reconfiguring hosts directly violates the stated requirement of completing migration without changing host configuration.
Concept tested: VXLAN EVPN Layer 3 gateway migration cutover
Source: https://www.cisco.com/c/en/us/td/docs/dcn/whitepapers/cisco-vxlan-evpn-migration-with-fabric-peering.html
Topics
Community Discussion
No community discussion yet for this question.