OSNTC.047: EVPN Multihoming, ESI, and DF Election

Original oil painting of a white male network engineer inspecting switch ports, racks and yellow and blue fiber cables in a data center

OSNTC.047 answers a practical data-center question: how can a server connected to two switches lose traffic when both Ethernet links still appear healthy? Ethernet VPN (EVPN) multihoming lets two or more provider-edge switches connect to the same customer-edge device while coordinating forwarding through BGP. The safeguards rely on more than a link aggregation group: operators must inspect the Ethernet Segment Identifier (ESI), EVPN Route Types 1 and 4, and the designated-forwarder role. The lesson extends OSNTC.046 on Route Types 2 and 5 and OSDCEC.009 on network fabrics.

Sneaky Subnet, July 29, 2026: EVPN Multihoming Deep Dive, covering Ethernet Segment routes, designated-forwarder election and split horizon. Public video listing confirmed. Embedded player playback requires a separate live browser check.

What an Ethernet Segment Identifier tells the fabric

An Ethernet segment (ES) is the set of Ethernet links connecting a multihomed device or network to its provider-edge switches. An ESI identifies that segment; the identifier is 10 octets long. The participating switches must consistently identify the intended shared segment. Otherwise, a remote switch may not recognize both attachments as one redundancy group. The authoritative RFC 7432 defines the original EVPN multihoming procedures, while Juniper’s EVPN multihoming reference explains ESIs, all-active and single-active operation.

An ESI does not replace the LACP relationship between a server bond and its attached switches. A misconfigured bond, incompatible aggregation settings, or a failed member can disrupt forwarding even if BGP EVPN looks healthy. Compare OSNTC.020 on LACP before blaming the overlay.

Type 4 discovers peers; Type 1 advertises attachment

Route Type 4, the Ethernet Segment route, helps the switches discover which EVPN peers serve the same segment. The participants can use the information in designated-forwarder election. Route Type 1, Ethernet Auto-Discovery, serves different purposes, including signaling ES and EVI attachment for functions such as aliasing and faster withdrawal after a failure. The route types are complementary, not interchangeable. Their roles are documented in Cisco’s EVPN multihoming guide.

Route Type 2, covered in the previous lesson, carries MAC reachability and optionally host IP information. Route Type 5 carries IP prefixes. A healthy Type 2 or Type 5 table alone cannot establish that the multihoming control plane is correctly discovering the shared ES. A fault investigation should keep the Ethernet segment, the tenant EVPN instance and the remote VTEP separate.

BGP L2VPN EVPN Multihome Lab, published 2022: lab coverage of Ethernet Auto-Discovery, Ethernet Segment routes and designated-forwarder behavior. Public video listing confirmed. Embedded player playback requires a separate live browser check.

What the designated forwarder actually forwards

On a multihomed Ethernet segment, the designated forwarder (DF) controls delivery of relevant broadcast, unknown-unicast and multicast traffic toward the attached site for a given service. DF election reduces the risk of duplicate BUM forwarding or Layer 2 loops. In all-active multihoming, known unicast can still use multiple qualified paths. A non-DF does not necessarily mean its entire physical uplink is broken or every unicast packet is prohibited. The precise behavior depends on redundancy mode and implementation.

The original DF election procedures appear in RFC 7432. RFC 8584 extends the framework and describes Highest Random Weight election, while RFC 9785 specifies preference-based alternatives. An operator must verify which algorithm and capabilities both peers actually support rather than assume that a preferred switch always wins.

Read-only verification on supported switches

Begin with the exact switch model, operating-system release, active routing instance, ESI, VLAN or VNI, and neighboring device. Check LACP membership, EVPN BGP neighbor state, received and advertised routes, and the DF result on both peers. The commands below illustrate separate operating systems and are not a universal procedure. Verify syntax in the local vendor release reference before running any command.

# Cisco NX-OS, on releases that support these forms
show bgp l2vpn evpn route-type 1
show bgp l2vpn evpn route-type 4

# Junos, on supported platforms and releases
show evpn instance designated-forwarder

Cisco documents Type 1 route verification in its Nexus 9000 ESI multihoming guide. Juniper documents the designated-forwarder inspection command in its active-active configuration and verification example. Do not infer absent routes from a single filtered command without checking which tenant and ESI the output represents.

Sneaky Subnet, July 31, 2026: EVPN Multihoming Auto Discovery Routes, Fast Convergence and Aliasing, with live lab verification. Public video listing confirmed. Embedded player playback requires a separate live browser check.

Practice: a server remains up but duplicate traffic appears

Fictional lab: Server A uses an approved bond to Leaf 1 and Leaf 2. Both physical links are up. Leaf 1 receives an expected Type 4 route from Leaf 2, but Leaf 2’s read-only output shows no matching Type 4 advertisement for the shared ESI. A monitoring system also reports intermittent duplicate broadcast delivery. Record the configured ESI on each attachment, BGP sessions, route import/export status, redundancy mode, DF roles and BUM counters. Missing Type 4 information is an investigation lead, not definitive proof that the mismatch caused the duplicates.

Explain why a Type 1 Auto-Discovery route cannot simply be treated as a Type 4 Ethernet Segment route. Identify what evidence would distinguish a route-policy mismatch, inconsistent ESI, unreachable EVPN peer or stale operational view. Make a recommendation for further verification, but do not shut a port, alter a bond, change the DF algorithm, or clear live routes without an approved change and rollback plan.

If the physical side is suspect, return to OSNTC.044 on DOM and FEC. If performance degrades without clear Layer 2 failure, compare OSNTC.045 on RoCEv2 congestion. A successful lab report separates facts, hypotheses, missing evidence and approved next steps.

Takeaway: EVPN multihoming coordinates multiple attachments using the ESI, Type 4 discovery, Type 1 Auto-Discovery and a DF election. Correct troubleshooting requires an end-to-end view of the physical bond, BGP advertisements, tenant context and forwarding roles, without treating one apparently healthy port as proof of fabric health.

Editor’s Note: The technical mechanisms were checked against RFCs 7432, 8584 and 9785 and the linked Cisco and Juniper references. The sample incident is fictional. No physical switch, server or production configuration was accessed, and no commands were executed on network hardware. All three video identities were checked against their public listings; playback and mobile-browser appearance remain unverified. The original 1200 × 630 fine-art oil-painting featured cover is not repeated inside the article.

Original BitcoinVersus.Tech optional 5,000-satoshi Bitcoin contribution QR

BitcoinVersus.Tech publishes independent technical education. An optional 5,000-satoshi Bitcoin donation supports research. Independently verify wallet recipient 3C9o19EH5HSiwEPyCTmEKzxhNCbo2X6TTb and amount before transferring funds. Bitcoin transactions are generally irreversible.

We work to make technical information Verifiably True. Educational examples do not authorize changes to production networks or replace site safety procedures, professional engineering review, financial advice or investment advice.

One response to “OSNTC.047: EVPN Multihoming, ESI, and DF Election”

  1. […] 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 […]

    Like

Leave a Reply