- play_arrow EVPN-VXLAN
- play_arrow Overview
- Understanding EVPN with VXLAN Data Plane Encapsulation
- EVPN-over-VXLAN Supported Functionality
- Understanding VXLANs
- VXLAN Constraints on EX Series, QFX Series, PTX Series, and ACX Series Devices
- EVPN Over VXLAN Encapsulation Configuration Overview for QFX Series and EX4600 Switches
- Implementing EVPN-VXLAN for Data Centers
- PIM NSR and Unified ISSU Support for VXLAN Overview
- Routing IPv6 Data Traffic through an EVPN-VXLAN Network with an IPv4 Underlay
- Understanding How to Configure VXLANs and Layer 3 Logical Interfaces to Interoperate
- Understanding GBP Profiles
- play_arrow Configuring EVPN-VXLAN Interfaces
- Understanding Flexible Ethernet Services Support With EVPN-VXLAN
- EVPN-VXLAN Lightweight Leaf to Server Loop Detection
- Overlapping VLAN Support Using VLAN Translation in EVPN-VXLAN Networks
- Overlapping VLAN Support Using Multiple Forwarding Instances or VLAN Normalization
- Layer 2 Protocol Tunneling over VXLAN Tunnels in EVPN-VXLAN Bridged Overlay Networks
- MAC Filtering, Storm Control, and Port Mirroring Support in an EVPN-VXLAN Environment
- Example: Micro and Macro Segmentation using Group Based Policy in a VXLAN
- DHCP Smart Relay in EVPN-VXLAN
- play_arrow Configuring VLAN-Aware Bundle Services, VLAN-Based Services, and Virtual Switch Support
- play_arrow Load Balancing with EVPN-VXLAN Multihoming
- play_arrow Setting Up a Layer 3 VXLAN Gateway
- play_arrow Configuring an EVPN-VXLAN Centrally-Routed Bridged Overlay
- play_arrow Configuring an EVPN-VXLAN Edge-Routed Bridging Overlay
- play_arrow IPv6 Underlay for VXLAN Overlays
- play_arrow Multicast Features with EVPN-VXLAN
- Multicast Support in EVPN-VXLAN Overlay Networks
- Overview of Multicast Forwarding with IGMP Snooping or MLD Snooping in an EVPN-VXLAN Environment
- Example: Preserving Bandwidth with IGMP Snooping in an EVPN-VXLAN Environment
- Overview of Selective Multicast Forwarding
- Configuring the number of SMET Nexthops
- Assisted Replication Multicast Optimization in EVPN Networks
- Optimized Intersubnet Multicast in EVPN Networks
- play_arrow Configuring the Tunneling of Q-in-Q Traffic
- play_arrow Tunnel Traffic Inspection on SRX Series Devices
- play_arrow Fault Detection and Isolation in EVPN-VXLAN Fabrics
-
- play_arrow EVPN-MPLS
- play_arrow Overview
- play_arrow Convergence in an EVPN MPLS Network
- play_arrow Pseudowire Termination at an EVPN
- play_arrow Configuring the Distribution of Routes
- Configuring an IGP on the PE and P Routers on EX9200 Switches
- Configuring IBGP Sessions Between PE Routers in VPNs on EX9200 Switches
- Configuring a Signaling Protocol and LSPs for VPNs on EX9200 Switches
- Configuring Entropy Labels
- Configuring Control Word for EVPN-MPLS
- Understanding P2MPs LSP for the EVPN Inclusive Provider Tunnel
- Configuring Bud Node Support
- play_arrow Configuring VLAN Services and Virtual Switch Support
- play_arrow Configuring Integrated Bridging and Routing
- EVPN with IRB Solution Overview
- An EVPN with IRB Solution on EX9200 Switches Overview
- Anycast Gateways
- Configuring EVPN with IRB Solution
- Configuring an EVPN with IRB Solution on EX9200 Switches
- Example: Configuring EVPN with IRB Solution
- Example: Configuring an EVPN with IRB Solution on EX9200 Switches
- play_arrow Configuring IGMP or MLD Snooping with EVPN-MPLS
-
- play_arrow EVPN E-LAN Services
- play_arrow EVPN-VPWS
- play_arrow Configuring VPWS Service with EVPN Mechanisms
- Overview of VPWS with EVPN Signaling Mechanisms
- Control word for EVPN-VPWS
- Overview of Flexible Cross-Connect Support on VPWS with EVPN
- Overview of Headend Termination for EVPN VPWS for Business Services
- Configuring VPWS with EVPN Signaling Mechanisms
- Example: Configuring VPWS with EVPN Signaling Mechanisms
- FAT Flow Labels in EVPN-VPWS Routing Instances
- Configuring EVPN-VPWS over SRv6
- Configuring Micro-SIDs in EVPN-VPWS
-
- play_arrow EVPN-ETREE
- play_arrow Overview
- play_arrow Configuring EVPN-ETREE
-
- play_arrow Using EVPN for Interconnection
- play_arrow Interconnecting VXLAN Data Centers With EVPN
- play_arrow Interconnecting EVPN-VXLAN Data Centers Through an EVPN-MPLS WAN
- play_arrow Extending a Junos Fusion Enterprise Using EVPN-MPLS
-
- play_arrow PBB-EVPN
- play_arrow Configuring PBB-EVPN Integration
- play_arrow Configuring MAC Pinning for PBB-EVPNs
-
- play_arrow EVPN Standards
- play_arrow Supported EVPN Standards
-
- play_arrow VXLAN-Only Features
- play_arrow Flexible VXLAN Tunnels
- play_arrow Static VXLAN
-
- play_arrow Configuration Statements and Operational Commands
Changing Duplicate MAC Address Detection Settings
When a host is physically moved or when a host is reconfigured on a different Ethernet
segment, the PE device sends an updated MAC advertisement route to other PE devices to update
their route table. If there is a misconfiguration in the network, MAC advertisement messages
oscillate between the different routes causing MAC address flapping. This makes the network
more vulnerable and wastes network resources. Junos supports MAC mobility automatically by
default. To disable MAC mobility, use the set protocols evpn mac-mobility
no-sequence-numbers
statement.
Junos OS also automatically detects and suppresses duplicate MAC addresses. Optionally, you can also configure the length of time that the duplicate MAC address is suppressed. When the PE device encounters duplicate MAC addresses, Junos OS generates a syslog message.
To change the duplicate MAC address detection settings , include the
duplicate-mac-detection
statement at either the [edit
routing-instances routing-instance-name protocols]
hierarchy
level or the[edit logical-systems logical-system-name
routing-instances routing-instance-name protocols]
hierarchy
level:
evpn duplicate-mac-detection { detection-threshold detection-threshold; detection-window seconds; auto-recovery-time minutes; }
You can modify the following options under the duplicate-mac-detection
statement:
detection-window
—The time interval used in detecting a duplicate MAC address. The value can be from 5 through 600 seconds. The default is 180 secondsdetection-threshold
—The number of MAC mobility events that are detected for a given MAC address within thedetection-window
before it is identified as a duplicate MAC address. Once the detection threshold is reached, updates for the MAC address are suppressed. The value can be from 2 through 20. The default is 5.auto-recovery-time
—(Optional) The length of time a device suppresses a duplicate MAC address. At the end of this duration, MAC address updates will resume. The value can be from 1 through 360 minutes. If a value is not specified, then the MAC address continues to be suppressed.
To ensure that the mobility advertisements have sufficient time to age out, set an
auto-recovery-time
greater than the
detection-window
.
To manually clear the suppression of duplicate MAC addresses, use the clear evpn
duplicate-mac-suppression
command.
To view MAC duplicate addresses in the EVPN MAC database, use the show evpn
database
command. The following example displays a sample output. The output
fields related to duplicate MAC detections are State, Mobility history, and MAC
advertisement route status:
user@PE1> show evpn database mac-address 00:00:00:00:00:02 extensive Instance: ALPHA VLAN ID: 100, MAC address: 00:00:00:00:00:02 State: 0x1 <Duplicate-Detected> Mobility history Mobility event time Type Source Seq num Aug 03 17:22:28.585619 Local ge-0/0/2.0 31 Aug 03 17:22:30.307198 Remote 10.255.0.3 32 Aug 03 17:22:37.611786 Local ge-0/0/2.0 33 Aug 03 17:22:39.289357 Remote 10.255.0.3 34 Aug 03 17:22:45.609449 Local ge-0/0/2.0 35 Source: ge-0/0/2.0, Rank: 1, Status: Active Mobility sequence number: 35 (minimum origin address 10.255.0.2) Timestamp: Aug 03 17:22:44 (0x5983be54) State: <Local-MAC-Only Local-To-Remote-Adv-Allowed> MAC advertisement route status: Not created (duplicate MAC suppression) IP address: 10.0.0.2 Source: 10.255.0.3, Rank: 2, Status: Inactive MAC label: 300176 Mobility sequence number: 34 (minimum origin address 10.255.0.3) Timestamp: Aug 03 17:22:39 (0x5983be4f) State: <> MAC advertisement route status: Not created (inactive source) IP address: 10.0.0.3