Skip to main content

SecuraWall.com

Email security and continuity

Explore

Technical Guide · Networking and Wi-Fi

EVPN-VXLAN Anycast Gateway Design: Underlay, VTEPs and Routes

EVPN-VXLAN builds VXLAN tunnels over a Layer 3 underlay and distributes MAC/IP reachability through BGP EVPN. A VTEP maps a local VLAN to a VXLAN Network Identifier. The underlay only…

Technical review:

Architecture and operating model

EVPN-VXLAN builds VXLAN tunnels over a Layer 3 underlay and distributes MAC/IP reachability through BGP EVPN. A VTEP maps a local VLAN to a VXLAN Network Identifier. The underlay only needs IP reachability between VTEP loopbacks, while the overlay carries tenant MAC, IP and prefix state. This separation reduces flood-and-learn dependence but creates two control planes to diagnose.

With an anycast gateway, every leaf hosting a segment presents the same virtual gateway IP and MAC. End systems keep the same first hop in every rack and after VM movement. VNI, VRF, route targets, gateway MAC and IRB behavior must remain consistent across leafs. Treating the shared address like active-standby VRRP defeats the distributed design.

Track EVPN route types by function. Type 2 advertises MAC/IP reachability, Type 3 carries inclusive multicast membership, and Type 5 advertises IP prefixes. Multihoming adds Ethernet Segment Identifier, Designated Forwarder and split-horizon checks. Platform behavior and supported combinations vary, so match RFC expectations with the deployed release and lab evidence.

Start with underlay loopback reachability, ECMP, failure detection and MTU. VXLAN adds outer headers, so physical MTU must exceed the tenant frame. In a pilot segment, test ARP or ND suppression, MAC mobility sequence, BUM replication and anycast return traffic. Collect VNI state, mobility events, drop reasons and underlay next-hop changes alongside BGP session state.

  1. 1IP underlay and VTEP loopbacks
  2. 2BGP EVPN control plane
  3. 3VXLAN VNI and anycast gateway
  4. 4Tenant traffic and telemetry
Validate underlay reachability, EVPN routes and data-plane counters for the same test flow.

Design parameters

VNI plan
Document L2 and L3 VNI ranges, tenant ownership and reuse rules.
Route target
Match import and export targets without crossing tenant isolation boundaries.
Anycast identity
Keep gateway IP, virtual MAC, subnet and IRB mode identical on participating leafs.
MTU budget
Calculate tenant MTU, VXLAN/UDP/IP headers and transport overhead end to end.
BUM method
Choose ingress replication or multicast using VTEP scale and replication capacity.

Worked example

A 1,500-byte tenant MTU needs room for VXLAN outer headers and any carrier tags. Do not choose 1,550 blindly; test the longest real path using DF probes, VXLAN counters and packet capture.

With ingress replication across 80 VTEPs, one BUM frame can create 79 source copies. Measure peak ARP, ND and unknown-unicast rates. Include temporary flooding during incomplete control-plane learning even when suppression is enabled.

Example commands: replace lab values and confirm permissions and software versions before use.

show bgp l2vpn evpn summary
show bgp l2vpn evpn route type macip
show bgp l2vpn evpn route type multicast
show bgp l2vpn evpn route type prefix
show evpn vni
ping 192.0.2.20 size 1472 do-not-fragment

Troubleshooting

ObservationLikely cause / distinctionVerification
BGP EVPN is up but VNI is downThe NVE source, VLAN mapping or L3 VNI may be missing.Compare VTEP source, VNI state and imported route targets.
Same-subnet works but routing failsThe anycast gateway, L3 VNI or VRF route may be incomplete.Trace gateway MAC, Type 2 IP binding and Type 5 or VRF next hop.
Traffic follows the old leaf after VM movementThe mobility sequence may not have advanced or an old route remains.Compare Type 2 sequence, duplicate-MAC alarms and remote forwarding state.

Acceptance checks

  1. Verify underlay loopback reachability and ECMP paths.
  2. Match the VTEP source with BGP next-hop resolution.
  3. Audit the VNI, VRF and route-target matrix.
  4. Compare anycast gateway IP and MAC across leafs.
  5. Observe Type 2, 3 and, when used, Type 5 routes.
  6. Measure MTU, BUM, MAC mobility and leaf-loss tests.

Related concepts

Layer 2 and Layer 3 boundaries

A VLAN creates a separate broadcast domain; routing and access policies govern communication between VLANs. Review trunk allowed lists, access-port assignment and gateway placement together. A network diagram should show where packets are routed and filtered, not merely which cables connect devices. Sharing a switch does not require sharing privileges. When access fails, confirm VLAN and addressing first, then gateway, route and policy matching.

Availability versus recovery

High availability aims to keep service running through specified failures with a short interruption; backup recovers lost or corrupted data from an earlier point. A cluster can replicate an accidental deletion to another node. HA therefore does not replace backup. Consider DNS, identity, network, storage and power dependencies together. Successful node failover is insufficient by itself: measure user sessions, application writes and external integrations after the transition as well.

Failover and failback

Failover moves service to another component; failback returns it to the preferred location. Their risks and sequencing may differ. DNS updates, routing, sessions, replication lag and application dependencies determine user interruption. Define failover triggers, false-alarm behavior and approval for returning service. Simply shutting down a VM does not test every failure type. Measure network, storage and management-plane failures separately.

MTU along the path

MTU concerns packet size on a link; tunnelling and encapsulation headers can reduce space available for useful payload. Small requests working while large transfers stall may suggest an MTU issue, but this is not proof. TCP MSS and interface MTU are distinct. Compare both endpoints and tunnel interfaces. Identify the affected segment with controlled tests instead of changing every device, and remember that blocked ICMP error messages can complicate path-MTU discovery.

Telemetry and time correlation

Telemetry combines logs, metrics and events that explain system behavior. A log describes an event, a metric shows behavior over time, and a distributed trace follows a request across components. Clock differences can make one event appear to occur at several times. Use synchronized clocks, reliable source identifiers and consistent time-zone handling. Alarm design should consider duration and user impact alongside thresholds. Monitor gaps in collection separately: absence of logs must not be interpreted as absence of incidents.

Capacity and usable headroom

Raw capacity is not the capacity available to applications. RAID or erasure coding, filesystems, reserved space, metadata, snapshots and growth headroom are separate deductions. TB and TiB representations also change the displayed number. Write calculations with units, establish protected usable capacity, then subtract operating reserves. Track growth rate as well as current utilization. The projected exhaustion date should leave enough time to procure and deploy additional capacity.

Primary documentation

Prepared by the Doz Teknoloji technical team using the primary references below. Calculations and lab scenarios state their assumptions; validate the applicable product version before rollout.

Knowledge Center

Enterprise IT Product Sales, Licensing and Deployment
Enterprise IT Project & Solution Scenarios
View all related content
Text on WhatsApp
Copied!