OSNTC.048 asks why a server can disappear from an EVPN-VXLAN network after moving between racks, even when the new switch port is up. The answer often involves MAC mobility, an out-of-date MAC/IP advertisement, a duplicate-MAC protection state, or an ARP/ND proxy entry that has not converged. The lesson builds on OSNTC.046 on EVPN Route Types 2 and 5 and OSNTC.047 on multihoming and Ethernet Segment Identifiers. Its goal is evidence-based, read-only diagnosis, not changes to a production fabric.
Why a MAC address needs a new location
In an EVPN fabric, a leaf switch advertises endpoint MAC information using Route Type 2, potentially including an IP address. Other leaf switches learn which remote endpoint or VTEP can reach the host. When a VM moves, the newly attached leaf must advertise the updated location and the previous owner should withdraw its stale route. RFC 7432, Section 15, defines a MAC Mobility extended community with a sequence number that helps switches distinguish newer advertisements from older ones.
A first advertisement can omit the mobility community, effectively starting at sequence zero. For a genuine move to a different Ethernet segment, the new advertisement uses an incremented sequence number. The same MAC learned on two leaf switches sharing an identical nonzero Ethernet Segment Identifier is a separate multihoming case; it should not automatically be interpreted as a host moving repeatedly. The ESI distinction prevents misleading diagnoses.
Five rapid moves can trigger protection
Rapid apparent MAC moves may indicate a loop, duplicate addresses or unstable endpoint attachment. RFC 7432 describes a configurable duplicate-MAC mechanism with illustrative defaults of five moves in 180 seconds. A device reaching its configured threshold can suppress further MAC/IP advertisement processing for the offending address. Vendor defaults and recovery behavior vary, so never infer a configured threshold from the standards document alone. Juniper’s mobility configuration guide documents the detection window, event threshold and recorded mobility history.
A duplicate alarm is a symptom, not proof that two malicious endpoints exist. Repeated live migrations, a misplaced Ethernet loop, inconsistent ESI configuration or genuinely duplicated MAC settings can produce similar observations. The network-loop explainer helps separate a layer-two loop from a legitimate VM migration.
ARP suppression can preserve the wrong answer
EVPN proxy ARP and IPv6 Neighbor Discovery reduce broadcast and multicast address-resolution traffic by answering requests from learned IP-to-MAC bindings. RFC 9161 explains how proxy tables learn, refresh, age and respond to neighbor requests. A stale or conflicting binding can make a host appear unreachable even after the BGP route reflects its new location. Diagnose the MAC reachability advertisement and the IP-to-MAC cache separately; successful BGP exchange alone does not prove that every forwarding or proxy table is correct.
Cisco’s Nexus VXLAN configuration guide documents ARP suppression and MAC/IP route inspection. IPv6 Neighbor Discovery requires its own checks and policy considerations. Compare OSNTC.040 on broadcast and multicast storm control: suppression of address-resolution traffic and limiting broadcast storms solve different problems.
Read-only commands for Junos and Cisco
On supported Junos systems, the following operational commands expose MAC location, mobility sequence, history and duplicate state. Record the routing instance, VNI, source leaf and peer platform before interpreting their output.
show evpn database extensive
show evpn instance extensive
On supported Cisco Nexus NX-OS versions, inspect BGP EVPN, the MAC/IP route table and the suppression cache. The available options depend on software release and platform. These examples are read-only show commands, not configuration changes.
show bgp l2vpn evpn
show l2route evpn mac-ip all detail
show ip arp suppression-cache detail
Juniper’s show evpn database reference describes sequence, history and duplicate-detection fields. Check the same MAC and IP on both old and new leaves, then compare advertised next hops, route sequence, local forwarding installation and proxy-cache status. Do not clear routes, reset neighbors or disable protection during evidence collection.
A simulated migration ticket
A fictional VM with IP 192.0.2.25 and MAC 02:11:22:33:44:55 moves from Leaf A to Leaf B at 10:02. Leaf B advertises sequence 8, while one remote leaf still shows sequence 7 with Leaf A as its next hop at 10:03. At 10:04, an ARP proxy entry still points to the former association. The evidence suggests a convergence or state-installation problem, but does not establish why convergence stalled. All addresses, times and sequences are classroom data, not field telemetry.
Build an incident record listing the observed VNI, ESI, old and new MAC/IP Type 2 routes, current sequence numbers, MAC table entries, neighbor-cache records and timestamps. Identify which switch originated each value and whether information came from control-plane BGP, hardware forwarding or a proxy cache. Check OSNTC.045 on RoCEv2 congestion before blaming an overlay route for unrelated packet loss or network congestion.
Takeaway: A moved endpoint may have a correct new physical port but an obsolete route or address-resolution entry elsewhere. Follow the identity, route sequence, next hop and proxy binding across the fabric; document discrepancies before anyone authorizes remediation.
Editor’s Note: Core technical claims were verified against RFC 7432 and RFC 9161, together with Cisco and Juniper command references. The classroom timeline is fictional. Three independently identifiable educational YouTube videos are embedded in Gutenberg, but actual browser playback and mobile viewport rendering have not been independently confirmed. No device commands were executed on live infrastructure. The original featured image is a 1200 × 630 photorealistic editorial illustration and is not repeated inside the lesson.

BitcoinVersus.Tech is volunteer-run and publishes independent technical education. Optional contributions of 5,000 satoshis support research. Scan the original QR in a compatible wallet and independently verify recipient 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb and amount before sending. Bitcoin transfers are generally irreversible.
We volunteer daily to improve the credibility of information on BitcoinVersus.Tech and make it Verifiably True. The lesson is educational, not permission to modify a production network, a substitute for qualified engineering review or financial or investment advice.

Leave a Reply