EVPN Active-Standby
Overview
EVPN Multihoming is a mechanism that allows a host or customer edge (CE) device to be connected to multiple Provider Edge (PE) devices called Multihoming (MH) peers for redundancy and load balancing purposes. This provides high availability and resiliency to the network, ensuring continuous connectivity even in case of a PE device failure.
Note: OcNOS support extends to a maximum of two MH peers.
Multihoming supports two kinds of redundancy, namely 1. All Active 2. Active-Standby.
Till now, OcNOS support All-Active (A-A) only. In OcNOS version 6.4.1, Port-Active mode is supported and in OcNOS version 6.4.2, Single-Active mode is supported in the context of Active-Standby redundancy.
Single-Active
• In this mode, traffic for a specific host or MAC address is handled by only one of the PE devices (MH peers) at a time.
• The other PE devices remain in standby mode, ready to take over if the active PE fails.
• The physical link state (either Physical port or LACP port) on the standby PE remains up, enabling a faster transition to the active role in the event of a failover. The CE devices use different interfaces, including LACP or physical connections, to connect to the Peer MH devices.
Port-Active
• In this mode, traffic for a specific host or MAC address is handled by only one of the PE devices (MH peers) at a time.
• Each MH peer connects through LACP with the same key as the CE devices (similar to A-A redundancy).
• The physical link state (LACP port) on the standby PE is made down, effectively blocking traffic on those ports.
• If a failover occurs, the standby PE must bring up its LACP ports to start forwarding traffic.
IRB Active-Standby: Active-standby mode is also applicable to Integrated Routing and Bridging (IRB) for both L3VPN symmetric and asymmetric modes.
Feature Characteristics
Single-Active standby redundancy mechanisms support both ELAN and ELINE services.
Single-Active ELINE
ELINE refers to Ethernet Line services, where two PEs are cross-connected to each other over an Ethernet link.
In Single-Active ELINE, the primary objective is to achieve redundancy for hosts while also using the same link for data exchange until it fails, at which point it should switch to the secondary or standby link. Here's how it works:
• MH Host Traffic
• One of the PE devices (MH peers) acts as the “Active” for the Attachment Circuit (AC) associated with the host. This PE sends and receives traffic to and from the host.
• The other PE acts as the “Standby” for the same AC and does not allow traffic to or from the host.
• The standby PE, despite receiving BUM traffic from the Host device (which is unaware of the cross-connect), blocks this traffic at the standby PE itself, as it operates in a standby role for the AC. Conversely, the active PE allows the flow of traffic.
• Remote Host Traffic: Traffic originating from remote hosts destined for the multihomed host is only sent to the active MH peer for the corresponding AC. This ensures that the cross connect is established only with the Active MH peer.
Single-Active ELAN
ELAN stands for Ethernet LAN services, where a group of PEs are interconnected in a multipoint Ethernet network.
In Single-Active ELAN, similar to Single-Active ELINE, redundancy for hosts and data exchange over the primary link are priorities, but there are some specific differences for Ethernet LAN (ELAN) scenarios:
• MH Host Traffic
• One of the PE devices (MH peers) is designated as the “Active” for the AC associated with the host. This PE handles sending and receiving traffic to and from remote locations.
• The other PE acts as the “Standby” role for the same AC. It receives BUM traffic from the host but blocks the traffic. Additionally, it refrains from learning MAC addresses and does not uplift Address Resolution Protocol/Neighbor Discovery (ARP/ND) packets.
• Unicast traffic from the host will be directed to the active PE, which will then allow the traffic to be sent across the network.
• Remote Host Unicast Traffic: Unicast traffic from remote hosts destined for the multihomed host is sent only to the active MH peer for the corresponding AC. This is because the MAC addresses of the host are learned only from the Active MH peer.
• Remote Host BUM Traffic: BUM traffic, such as broadcast and multicast packets from the remote PE device, is replicated to both MH PEs. However, only the active PE, which is also designated as a forwarder, allows this traffic to reach the host. The standby PE, classified as a Non-Designated Forwarder, drops the egress traffic.
Port-Active Ethernet LAN (ELAN) and Ethernet LINE (ELINE) are examples of port-active standby redundancy mechanisms.
Port-Active ELINE
Port-Active ELINE enables redundancy and optimized data exchange by designating an active port for traffic handling in multihomed network setups. Here's how it works:
• Active AC Link: Among the Multihomed (MH) peers, a designated PE is assigned as “Active” for the AC associated with the host. This PE manages bidirectional traffic to and from the host. In a port-active configuration, all hosts associated with the ESI link remain in the same state, as the Active and Standby status is determined per ESI link.
• Standby AC Link: The AC link attached to the host, designated as “Standby,” remains operationally down. It serves as a backup link for failover scenarios.
• MH Host traffic: BUM and unicast traffic from the host are always directed towards the Active PE because the link towards the Active PE is operational UP. Conversely, the link towards the Standby PE from the host devices is operational DOWN.
• Remote Host Traffic: Traffic originating from remote hosts and destined for the multihomed host is directed exclusively to the Active MH node that serves the corresponding AC. This ensures efficient traffic routing and intelligent cross-connection establishment.
Port-Active ELAN
Port-Active ELAN enhances redundancy and efficient data exchange by designating an active port for traffic management in multihomed Ethernet LAN environments. Here's how it works:
• Active AC Link: Within the MH peers, one PE is identified as the “Active” entity for the AC. It manages traffic to and from remote locations efficiently.
• Standby AC Link: Similar to Port-Active ELINE, the standby AC link attached to the host remains operationally down to ensure effective standby redundancy.
• MH Host Traffic: In a port-active scenario, the standby link does not receive any traffic from the host. Only the active link manages incoming traffic from the host. The Active PE also learns and advertises host information to remote locations, including MAC addresses and ARP/ND details.
• Remote Host Unicast Traffic: Unicast traffic from remote sources is directed exclusively to the Active MH PE that has advertised the host address, optimizing traffic flow.
• Remote Host BUM Traffic: BUM traffic is replicated across all MH nodes. However, egress traffic for BUM packets occurs only from the Active PE. The standby PE drops the traffic since the AC links are operational DOWN.
Benefits
The benefits of Single-Active and Port-Active include enhanced redundancy and fault tolerance for hosts and customer edge devices, efficient data exchange, minimized downtime, and improved network resiliency in multihomed Ethernet Line and Ethernet LAN environments. These mechanisms ensure uninterrupted connectivity and optimized traffic management, contributing to higher availability and improved user experience.
Prerequisites
Here are the prerequisites for configuring EVPN Multihoming:
Ensure EVPN Configuration: Make sure that the EVPN is configured already in the network as it is a requirement for EVPN Multihoming.
Configure Attachment Circuits (AC): Ensure that each CE device is appropriately linked to the PE devices through Attachment Circuits. These circuits must be configured correctly.
Set Up LACP Configuration: To use Link Aggregation Control Protocol (LACP) for multihoming, configure LACP appropriately on the relevant interfaces.
EVPN MPLS Global Configuration: To enable EVPN MPLS features, need to configure global settings, such as enabling EVPN MPLS, defining global VTEP IP addresses, enabling hardware profile filtering for multihoming, and activating EVPN MPLS multihoming functionality. These settings are essential for EVPN and MPLS operation.
Access Port Configuration: Depending on the network's redundancy plan (single-active or port-active), configure access ports, including parameters for load balancing, service carving preferences, and EVPN settings. These configurations are crucial for network access and connectivity in an EVPN environment.
These prerequisites ensure that the network is ready for the implementation of EVPN Multihoming, providing redundancy and load balancing for CE devices.
Configuration
Here are sample configurations for EVPN MPLS Active-Standby MultiHoming Configuration and EVPN SR Active-Standby Multi-Homing Configuration, including topology, configuration procedures, and corresponding validations.
For more information on the EVPN MPLS configurations, see the EVPN MPLS Configuration and EVPN MPLS IRB Configuration chapters in the Multi-Protocol Label Switching Guide.
EVPN MPLS Active-Standby MultiHoming Configuration
This section illustrates the Multi-Homed setup for the EVPN MPLS Active-Standby configuration, showcasing examples for both ELINE and ELAN services with LDP as the underlay MPLS path.
EVPN MPLS Active-Standby MH Topology
Figure 3-7 consists of customer edge routers CE1 and CE2, along with IPv4 Provider Edge routers PE1, PE2, PE3, and PE4, all interconnected through the core routers P1 and P2 in the IPv4 MPLS provider network.
EVPN MPLS AS MH Configuration
CE1
The following configuration steps under CE1 are set up to enable VLANs and configure interfaces for carrying VLAN traffic.
CE1#configure terminal | Enter configure mode. |
CE1(config)#bridge 1 protocol ieee vlan-bridge | Set up bridge 1 to use the IEEE VLAN bridge protocol. |
CE1(config)#vlan 2-100 bridge 1 state enable | Configure VLANs from 2-100 and associate them with bridge 1. |
CE1(config)#interface xe54 | Enter interface mode xe54. |
CE1(config-if)#switchport | Configure the interface xe54 as a Layer 2 switch port. |
CE1(config-if)#bridge-group 1 | Associate xe54 to bridge 1. |
CE1(config-if)#switchport mode trunk | Configure xe54 as a trunk port. |
CE1(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk interface xe54. |
CE1(config-if)#exit | Exit interface mode xe54. |
CE1(config)#interface po1 | Enter interface mode and configure LAG interface port-channel 1 (po1). |
CE1(config-if)#switchport | Configures port-channel 1 as a Layer 2 switch port. |
CE1(config-if)#bridge-group 1 | Associate po1 to bridge 1. |
CE1(config-if)#switchport mode trunk | Configure po1 as a trunk port. |
CE1(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk port-channel po1. |
CE1(config-if)#exit | Exit interface mode po1. |
CE1(config)#interface xe48 | Enter interface mode xe48. |
CE1(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE1(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE1(config-if)#exit | Exit interface mode xe48. |
CE1(config-if)#interface xe50 | Enter interface mode xe50. |
CE1(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE1(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE1(config-if)#commit | Commit the transaction. |
CE1(config-if)#end | Exit interface mode xe50 and configure mode. |
PE1: Loopback Interface
The configuration on PE1 for a loopback interface with IP address 10.10.10.1/32 secondary is set up to provide IP connectivity for the router.
PE1#configure terminal | Enter configure mode. |
PE1(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE1(config-if)#ip address 10.10.10.1/32 secondary | Configure a secondary IP address, 10.10.10.1/32, on the loopback interface. |
PE1(config-if)#exit | Exit interface mode lo. |
PE1(config)#commit | Commit the transaction. |
PE1: Global LDP
The configuration on PE1 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE1(config)#router ldp | Enter the Router LDP mode. |
PE1(config-router)#router-id 10.10.10.1 | Set the router ID for LDP to 10.10.10.1. |
PE1(config-router)#transport-address ipv4 10.10.10.1 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE1(config-router)#targeted-peer ipv4 10.10.10.2 | Configure targeted peer for LDP using IPv4 addresses. |
PE1(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE1(config-router)#targeted-peer ipv4 10.10.10.3 | Configure targeted peer for LDP using IPv4 addresses. |
PE1(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE1(config-router)#targeted-peer ipv4 10.10.10.4 | Configure targeted peer for LDP using IPv4 addresses. |
PE1(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE1(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: Global EVPN MPLS Command
The configuration on PE1 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE1(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE1, enabling it to participate in EVPN MPLS services. |
PE1(config)#commit | Commit candidate configuration to be running configuration. |
PE1(config)#evpn mpls vtep-ip-global 10.10.10.1 | Configure the global VTEP IP address 10.10.10.1, associating it with the loopback IP. |
PE1(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE1(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE1 to support multi-homed EVPN MPLS services. |
PE1(config)#commit | Commit the transaction. |
PE1: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE1 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE1(config)#interface xe1 | Enter interface mode xe1. |
PE1(config-if)#ip address 10.1.1.1/30 | Configure an IP address, 10.1.1.1/30, on the interface xe1. |
PE1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE1(config-if)#exit | Exit interface mode xe1. |
PE1(config)#commit | Commit the transaction. |
PE1(config)#interface xe2 | Enter interface mode xe2. |
PE1(config-if)#ip address 10.1.2.1/30 | Configure an IP address, 10.1.2.1/30, on the interface xe2. |
PE1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE1(config-if)#exit | Exit interface mode xe2. |
PE1(config)#commit | Commit the transaction. |
PE1: OSPF Configuration
The below configuration is performed to set up OSPF on PE1, specifying the router ID, defining network interfaces, and configuring BFD parameters for efficient routing.
PE1(config)#router ospf 100 | Enter the router OSPF mode. Configure PE1 to run OSPF with process ID 100. |
PE1(config-router)#ospf router-id 10.10.10.1 | Set the OSPF router ID to 10.10.10.1, identifying PE1 within the OSPF network. |
PE1(config-router)#network 10.10.10.1/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
PE1(config-router)#network 10.1.1.1/30 area 0.0.0.0 | Advertise network address in OSPF. |
PE1(config-router)#network 10.1.2.1/30 area 0.0.0.0 | Advertise network address in OSPF. |
PE1(config-router)#bfd interval 3 minrx 3 multiplier 3 | Configure BFD interval with an interval of 3, a minimum receive interval of 3, and a multiplier of 3. |
PE1(config-router)#exit | Exit router OSPF mode and return to configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: BGP Configuration
The below BGP configuration on PE1 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE1(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE1(config-router)#bgp router-id 10.10.10.1 | Configure BGP router ID 10.10.10.1, identifying PE1 within the BGP network. |
PE1(config-router)#neighbor 10.10.10.2 remote-as 65010 | Configure neighbor 10.10.10.2 as an iBGP neighbor with their remote AS number 65010. |
PE1(config-router)#neighbor 10.10.10.2 update-source lo | Configure neighbor 10.10.10.2 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE1(config-router)#neighbor 10.10.10.3 remote-as 65010 | Configure neighbor 10.10.10.3 as an iBGP neighbor with their remote AS number 65010. |
PE1(config-router)#neighbor 10.10.10.3 update-source lo | Configure neighbor 10.10.10.3 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE1(config-router)#neighbor 10.10.10.4 remote-as 65010 | Configure neighbor 10.10.10.4 as an iBGP neighbor with their remote AS number 65010. |
PE1(config-router)#neighbor 10.10.10.4 update-source lo | Configure neighbor 10.10.10.4 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE1(config-router)#neighbor 10.10.10.2 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE1(config-router)#neighbor 10.10.10.3 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE1(config-router)#neighbor 10.10.10.4 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE1(config-router)#neighbor 10.10.10.2 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE1(config-router)#neighbor 10.10.10.3 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE1(config-router)#neighbor 10.10.10.4 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE1(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE1(config-router-af)#neighbor 10.10.10.2 activate | Activate EVPN for iBGP neighbor 10.10.10.2 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE1(config-router-af)#neighbor 10.10.10.3 activate | Activate EVPN for iBGP neighbor 10.10.10.3 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE1(config-router-af)#neighbor 10.10.10.4 activate | Activate EVPN for iBGP neighbor 10.10.10.4 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE1(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE1(config-router)#commit | Commit the transaction. |
PE1(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE1: MAC VRF Configuration
The below MAC VRF configuration on PE1 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE1(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE1(config-vrf)#rd 10.10.10.1:1700 | Configure Route-Distinguisher value of 10.10.10.1:1700. |
PE1(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE1(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE1(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE1(config-vrf)#rd 10.10.10.1:1001 | Configure Route-Distinguisher value of 10.10.10.1:1001. |
PE1(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE1(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE1 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE1(config)#evpn mpls id 1800 xconnect target-mpls-id 1700 | Configure the EVPN-VPWS identifier with a source identifier of 1800 and a target identifier of 1700. |
PE1(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE1(config-evpn-mpls)#commit | Commit the transaction. |
PE1(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE1(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE1(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE1(config-evpn-mpls)#commit | Commit the transaction. |
PE1(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE1: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE1 is carried out to configure various parameters including system-mac, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE1(config)#interface po1 | Enter the port channel interface mode for po1 |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#evpn multi-homed system-mac 0000.1111.7777 load-balancing port-active | Configure the system-mac address 0000.1111.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE1(config-if-es)#service-carving auto | Configure service carving as auto. |
PE1(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE1(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE1(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE1(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE1(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE1(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE1(config)#interface xe0 | Enter the interface mode for xe0. |
PE1(config-if)#speed 10g | Set the speed to 10g. |
PE1(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE1(config-if)#exit | Exit interface mode xe0 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE1 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE1(config)#interface sa1 | Enter the single active interface mode for sa1 |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#evpn multi-homed esi 00:00:11:11:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:11:11:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE1(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE1(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE1(config-if)#exit | Exit interface mode sa1 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1(config)#interface sa1.1 switchport | Create a Layer 2 sub-interface sa1.1 within the port channel. |
PE1(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE1(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE1(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE1(config-if)#exit | Exit interface mode sa1.1 and return to the configure mode. |
PE1(config)#interface xe0 | Enter the interface mode for xe0. |
PE1(config-if)#speed 10g | Set the speed to 10g. |
PE1(config-if)#static-channel-group 1 | Attach the static-channel-group 1, the LAG interface sa1 to xe0. |
PE1(config-if)#exit | Exit interface mode xe0 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE2: Loopback Interface
The configuration on PE2 for a loopback interface with IP address 10.10.10.2/32 secondary is set up to provide IP connectivity for the router.
PE2#configure terminal | Enter configure mode. |
PE2(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE2(config-if)#ip address 10.10.10.2/32 secondary | Configure a secondary IP address, 10.10.10.2/32, on the loopback interface. |
PE2(config-if)#exit | Exit interface mode lo. |
PE2(config)#commit | Commit the transaction. |
PE2: Global LDP
The configuration on PE2 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE2(config)#router ldp | Enter the Router LDP mode. |
PE2(config-router)#router-id 10.10.10.2 | Set the router ID for LDP to 10.10.10.2. |
PE2(config-router)#transport-address ipv4 10.10.10.2 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE2(config-router)#targeted-peer ipv4 10.10.10.1 | Configure targeted peer for LDP using IPv4 addresses. |
PE2(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE2(config-router)#targeted-peer ipv4 10.10.10.3 | Configure targeted peer for LDP using IPv4 addresses. |
PE2(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE2(config-router)#targeted-peer ipv4 10.10.10.4 | Configure targeted peer for LDP using IPv4 addresses. |
PE2(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE2(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: Global EVPN MPLS Command
The configuration on PE2 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE2(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE2, enabling it to participate in EVPN MPLS services. |
PE2(config)#commit | Commit candidate configuration to be running configuration. |
PE2(config)#evpn mpls vtep-ip-global 10.10.10.2 | Configure the global VTEP IP address 10.10.10.2, associating it with the loopback IP. |
PE2(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE2(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE2 to support multi-homed EVPN MPLS services. |
PE2(config)#commit | Commit the transaction. |
PE2: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE2 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE2(config)#interface xe4 | Enter interface mode xe4. |
PE2(config-if)#ip address 10.1.3.1/30 | Configure an IP address, 10.1.3.1/30, on the interface xe4. |
PE2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE2(config-if)#exit | Exit interface mode xe4. |
PE2(config)#commit | Commit the transaction. |
PE2(config)#interface xe5 | Enter interface mode xe5. |
PE2(config-if)#ip address 10.1.4.1/30 | Configure an IP address, 10.1.4.1/30, on the interface xe5. |
PE2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE2(config-if)#exit | Exit interface mode xe5. |
PE2(config)#commit | Commit the transaction. |
PE2: OSPF Configuration
The below configuration is performed to set up OSPF on PE2, specifying the router ID, defining network interfaces, and configuring BFD parameters for efficient routing.
PE2(config)#router ospf 100 | Enter the router OSPF mode. Configure PE2 to run OSPF with process ID 100. |
PE2(config-router)#ospf router-id 10.10.10.2 | Set the OSPF router ID to 10.10.10.2, identifying PE2 within the OSPF network. |
PE2(config-router)#network 10.1.3.1/30 area 0.0.0.0 | Advertise loopback address in OSPF. |
PE2(config-router)#network 10.1.4.1/30 area 0.0.0.0 | Advertise network address in OSPF. |
PE2(config-router)#bfd interval 3 minrx 3 multiplier 3 | Configure BFD interval with an interval of 3, a minimum receive interval of 3, and a multiplier of 3. |
PE2(config-router)#exit | Exit router OSPF mode and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: BGP Configuration
The below BGP configuration on PE2 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE2(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE2(config-router)#bgp router-id 10.10.10.2 | Configure BGP router ID 10.10.10.2, identifying PE2 within the BGP network. |
PE2(config-router)#neighbor 10.10.10.1 remote-as 65010 | Configure neighbor 10.10.10.1 as an iBGP neighbor with their remote AS number 65010. |
PE2(config-router)#neighbor 10.10.10.1 update-source lo | Configure neighbor 10.10.10.1 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE2(config-router)#neighbor 10.10.10.3 remote-as 65010 | Configure neighbor 10.10.10.3 as an iBGP neighbor with their remote AS number 65010. |
PE2(config-router)#neighbor 10.10.10.3 update-source lo | Configure neighbor 10.10.10.3 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE2(config-router)#neighbor 10.10.10.4 remote-as 65010 | Configure neighbor 10.10.10.4 as an iBGP neighbor with their remote AS number 65010. |
PE2(config-router)#neighbor 10.10.10.4 update-source lo | Configure neighbor 10.10.10.4 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE2(config-router)#neighbor 10.10.10.1 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE2(config-router)#neighbor 10.10.10.3 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE2(config-router)#neighbor 10.10.10.4 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE2(config-router)#neighbor 10.10.10.1 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE2(config-router)#neighbor 10.10.10.3 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE2(config-router)#neighbor 10.10.10.4 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE2(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE2(config-router-af)#neighbor 10.10.10.1 activate | Activate EVPN for iBGP neighbor 10.10.10.1 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE2(config-router-af)#neighbor 10.10.10.3 activate | Activate EVPN for iBGP neighbor 10.10.10.3 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE2(config-router-af)#neighbor 10.10.10.4 activate | Activate EVPN for iBGP neighbor 10.10.10.4 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE2(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE2(config-router)#commit | Commit the transaction. |
PE2(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE2: MAC VRF Configuration
The below MAC VRF configuration on PE2 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE2(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE2(config-vrf)#rd 10.10.10.2:1700 | Configure Route-Distinguisher value of 10.10.10.2:1700. |
PE2(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE2(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE2(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE2(config-vrf)#rd 10.10.10.2:1001 | Configure Route-Distinguisher value of 10.10.10.2:1001. |
PE2(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE2(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE2 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE2(config)#evpn mpls id 1800 xconnect target-mpls-id 1700 | Configure the EVPN-VPWS identifier with a source identifier of 1800 and a target identifier of 1700. |
PE2(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE2(config-evpn-mpls)#commit | Commit the transaction. |
PE2(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE2(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE2(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE2(config-evpn-mpls)#commit | Commit the transaction. |
PE2(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE2: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE2 is carried out to configure various parameters including system-mac, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE2(config)#interface po1 | Enter the port channel interface mode for po1 |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#evpn multi-homed system-mac 0000.1111.7777 load-balancing port-active | Configure the system-mac address 0000.1111.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE2(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE2(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE2(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE2(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE2(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE2(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE2(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE2(config)#interface xe08 | Enter the interface mode for xe8. |
PE2(config-if)#speed 10g | Set the speed to 10g. |
PE2(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE2(config-if)#exit | Exit interface mode xe8 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE2 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE2(config)#interface sa2 | Enter the single active interface mode for sa2. |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#evpn multi-homed esi 00:00:11:11:77:77 load-balancing single-active | Configure the ESI with the value 00:00:11:11:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE2(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE2(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE2(config-if)#exit | Exit interface mode sa2 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2(config)#interface sa2.1 switchport | Create a Layer 2 sub-interface sa2.1 within the port channel. |
PE2(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE2(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE2(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE2(config-if)#exit | Exit interface mode sa2.1 and return to the configure mode. |
PE2(config)#interface xe8 | Enter the interface mode for xe8. |
PE2(config-if)#speed 10g | Set the speed to 10g. |
PE2(config-if)#static-channel-group 2 | Attach the static-channel-group 2, the LAG interface sa2 to xe8. |
PE2(config-if)#exit | Exit interface mode xe8 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
P1: Loopback Interface
The configuration on P1 for a loopback interface with IP address 10.10.10.5/32 secondary is set up to provide IP connectivity for the router.
P1#configure terminal | Enter configure mode. |
P1(config)#interface lo | Enter the interface mode for the loopback interface lo. |
P1(config-if)#ip address 10.10.10.5/32 secondary | Configure a secondary IP address, 10.10.10.5/32, on the loopback interface. |
P1(config-if)#exit | Exit interface mode lo. |
P1(config)#commit | Commit the transaction. |
P1: Global LDP
The configuration on P1 for the Global LDP router, specifying router ID and targeted peer, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
P1(config)#router ldp | Enter the Router LDP mode. |
P1(config-router)#router-id 10.10.10.5 | Set the router ID for LDP to 10.10.10.5. |
P1(config-router)#transport-address ipv4 10.10.10.5 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
P1(config-router)#exit | Exit router LDP mode and return to the configure mode. |
P1(config)#commit | Commit the transaction. |
P1: Interface Configuration
The below configuration is performed to set up interfaces on P1 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
P1(config)#interface xe1 | Enter interface mode xe1. |
P1(config-if)#ip address 10.1.1.2/30 | Configure an IP address, 10.1.1.2/30, on the interface xe1. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#exit | Exit interface mode xe1. |
P1(config)#commit | Commit the transaction. |
P1(config)#interface xe2 | Enter interface mode xe2. |
P1(config-if)#ip address 10.1.4.2/30 | Configure an IP address, 10.1.4.2/30, on the interface xe2. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#exit | Exit interface mode xe2. |
P1(config)#commit | Commit the transaction. |
P1(config)#interface xe3 | Enter interface mode xe3. |
P1(config-if)#ip address 10.1.5.2/30 | Configure an IP address, 10.1.5.2/30, on the interface xe3. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#exit | Exit interface mode xe3. |
P1(config)#commit | Commit the transaction. |
P1(config)#interface xe4 | Enter interface mode xe4. |
P1(config-if)#ip address 10.1.6.2/30 | Configure an IP address, 10.1.6.2/30, on the interface xe4. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#exit | Exit interface mode xe4. |
P1(config)#commit | Commit the transaction. |
P1: OSPF Configuration
The below configuration is performed to set up OSPF on P1, specifying the router ID, and defining network interfaces for efficient routing.
P1(config)#router ospf 100 | Enter the router OSPF mode. Configure P1 to run OSPF with process ID 100. |
P1(config-router)#ospf router-id 10.10.10.5 | Set the OSPF router ID to 10.10.10.5, identifying P1 within the OSPF network. |
P1(config-router)#network 10.10.10.5/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
P1(config-router)#network 10.1.1.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P1(config-router)#network 10.1.4.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P1(config-router)#network 10.1.5.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P1(config-router)#network 10.1.6.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P1(config-router)#exit | Exit router OSPF mode and return to the configure mode. |
P1(config)#commit | Commit the transaction. |
P2: Loopback Interface
The configuration on P2 for a loopback interface with IP address 10.10.10.6/32 secondary is set up to provide IP connectivity for the router.
P2#configure terminal | Enter configure mode. |
P2(config)#interface lo | Enter the interface mode for the loopback interface lo. |
P2(config-if)#ip address 10.10.10.6/32 secondary | Configure a secondary IP address, 10.10.10.6/32, on the loopback interface. |
P2(config-if)#exit | Exit interface mode lo. |
P2(config)#commit | Commit the transaction. |
P2: Global LDP
The configuration on P2 for the Global LDP router, specifying router ID and targeted peer, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
P2(config)#router ldp | Enter the Router LDP mode. |
P2(config-router)#router-id 10.10.10.6 | Set the router ID for LDP to 10.10.10.6. |
P2(config-router)#transport-address ipv4 10.10.10.6 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
P2(config-router)#exit | Exit router LDP mode and return to the configure mode. |
P2(config)#commit | Commit the transaction. |
P2: Interface Configuration
The below configuration is performed to set up interfaces on P2 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
P2(config)#interface xe12 | Enter interface mode xe12. |
P2(config-if)#ip address 10.1.2.2/30 | Configure an IP address, 10.1.2.2/30, on the interface xe12. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#exit | Exit interface mode xe12. |
P2(config)#commit | Commit the transaction. |
P2(config)#interface xe13 | Enter interface mode xe13. |
P2(config-if)#ip address 10.1.3.2/30 | Configure an IP address, 10.1.3.2/30, on the interface xe13. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#exit | Exit interface mode xe13. |
P2(config)#commit | Commit the transaction. |
P2(config)#interface xe11 | Enter interface mode xe11. |
P2(config-if)#ip address 10.1.7.2/30 | Configure an IP address, 10.1.7.2/30, on the interface xe11. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#exit | Exit interface mode xe11. |
P2(config)#commit | Commit the transaction. |
P2(config)#interface xe14 | Enter interface mode xe14. |
P2(config-if)#ip address 10.1.8.2/30 | Configure an IP address, 10.1.8.2/30, on the interface xe14. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#exit | Exit interface mode xe14. |
P2(config)#commit | Commit the transaction. |
P2: OSPF Configuration
The below configuration is performed to set up OSPF on P2, specifying the router ID, and defining network interfaces for efficient routing.
P2(config)#router ospf 100 | Enter the router OSPF mode. Configure P2 to run OSPF with process ID 100. |
P2(config-router)#ospf router-id 10.10.10.6 | Set the OSPF router ID to 10.10.10.6, identifying P2 within the OSPF network. |
P2(config-router)#network 10.10.10.6/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
P2(config-router)#network 10.1.2.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P2(config-router)#network 10.1.3.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P2(config-router)#network 10.1.7.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P2(config-router)#network 10.1.8.2/30 area 0.0.0.0 | Advertise network address in OSPF. |
P2(config-router)#exit | Exit router OSPF mode and return to the configure mode. |
P2(config)#commit | Commit the transaction. |
PE3: Loopback Interface
The configuration on PE3 for a loopback interface with IP address 10.10.10.3/32 secondary is set up to provide IP connectivity for the router.
PE3#configure terminal | Enter configure mode. |
PE3(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE3(config-if)#ip address 10.10.10.3/32 secondary | Configure a secondary IP address, 10.10.10.3/32, on the loopback interface. |
PE3(config-if)#exit | Exit interface mode lo. |
PE3(config)#commit | Commit the transaction. |
PE3: Global LDP
The configuration on PE3 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE3(config)#router ldp | Enter the Router LDP mode. |
PE3(config-router)#router-id 10.10.10.3 | Set the router ID for LDP to 10.10.10.3. |
PE2(config-router)#transport-address ipv4 10.10.10.3 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE3(config-router)#targeted-peer ipv4 10.10.10.1 | Configure targeted peer for LDP using IPv4 addresses. |
PE3(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE3(config-router)#targeted-peer ipv4 10.10.10.2 | Configure targeted peer for LDP using IPv4 addresses. |
PE3(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE3(config-router)#targeted-peer ipv4 10.10.10.4 | Configure targeted peer for LDP using IPv4 addresses. |
PE3(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE3(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: Global EVPN MPLS Command
The configuration on PE3 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE3(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE3, enabling it to participate in EVPN MPLS services. |
PE3(config)#commit | Commit candidate configuration to be running configuration. |
PE3(config)#evpn mpls vtep-ip-global 10.10.10.3 | Configure the global VTEP IP address 10.10.10.3, associating it with the loopback IP. |
PE3(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE3(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE3 to support multi-homed EVPN MPLS services. |
PE3(config)#commit | Commit the transaction. |
PE3: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE3 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE3(config)#interface xe1 | Enter interface mode xe1. |
PE3(config-if)#ip address 10.1.6.1/30 | Configure an IP address, 10.1.6.1/30, on the interface xe1. |
PE3(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE3(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE3(config-if)#exit | Exit interface mode xe1. |
PE3(config)#commit | Commit the transaction. |
PE3(config)#interface xe5 | Enter interface mode xe5. |
PE3(config-if)#ip address 10.1.7.1/30 | Configure an IP address, 10.1.7.1/30, on the interface xe5. |
PE3(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE3(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE3(config-if)#exit | Exit interface mode xe5. |
PE3(config)#commit | Commit the transaction. |
PE3: OSPF Configuration
The below configuration is performed to set up OSPF on PE3, specifying the router ID, defining network interfaces, and configuring BFD parameters for efficient routing.
PE3(config)#router ospf 100 | Enter the router OSPF mode. Configure PE3 to run OSPF with process ID 100. |
PE3(config-router)#ospf router-id 10.10.10.3 | Set the OSPF router ID to 10.10.10.3, identifying PE3 within the OSPF network. |
PE3(config-router)#network 10.10.10.3/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
PE3(config-router)#network 10.1.6.1/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
PE3(config-router)#network 10.1.7.1/30 area 0.0.0.0 | Advertise network address in OSPF. |
PE3(config-router)#bfd interval 3 minrx 3 multiplier 3 | Configure BFD interval with an interval of 3, a minimum receive interval of 3, and a multiplier of 3. |
PE3(config-router)#exit | Exit router OSPF mode and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: BGP Configuration
The below BGP configuration on PE3 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE3(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE3(config-router)#bgp router-id 10.10.10.3 | Configure BGP router ID 10.10.10.2, identifying PE3 within the BGP network. |
PE3(config-router)#neighbor 10.10.10.1 remote-as 65010 | Configure neighbor 10.10.10.1 as an iBGP neighbor with their remote AS number 65010. |
PE3(config-router)#neighbor 10.10.10.1 update-source lo | Configure neighbor 10.10.10.1 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE3(config-router)#neighbor 10.10.10.2 remote-as 65010 | Configure neighbor 10.10.10.2 as an iBGP neighbor with their remote AS number 65010. |
PE3(config-router)#neighbor 10.10.10.2 update-source lo | Configure neighbor 10.10.10.2 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE3(config-router)#neighbor 10.10.10.4 remote-as 65010 | Configure neighbor 10.10.10.4 as an iBGP neighbor with their remote AS number 65010. |
PE3(config-router)#neighbor 10.10.10.4 update-source lo | Configure neighbor 10.10.10.4 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE3(config-router)#neighbor 10.10.10.1 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE3(config-router)#neighbor 10.10.10.2 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE3(config-router)#neighbor 10.10.10.4 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE3(config-router)#neighbor 10.10.10.1 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE3(config-router)#neighbor 10.10.10.2 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE3(config-router)#neighbor 10.10.10.4 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE3(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE3(config-router-af)#neighbor 10.10.10.1 activate | Activate EVPN for iBGP neighbor 10.10.10.1 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE3(config-router-af)#neighbor 10.10.10.2 activate | Activate EVPN for iBGP neighbor 10.10.10.2 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE3(config-router-af)#neighbor 10.10.10.4 activate | Activate EVPN for iBGP neighbor 10.10.10.4 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE3(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE3(config-router)#commit | Commit the transaction. |
PE3(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE3: MAC VRF Configuration
The below MAC VRF configuration on PE3 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE3(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE3(config-vrf)#rd 10.10.10.3:1700 | Configure Route-Distinguisher value of 10.10.10.3:1700. |
PE3(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE3(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE3(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE3(config-vrf)#rd 10.10.10.3:1001 | Configure Route-Distinguisher value of 10.10.10.3:1001. |
PE3(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE3(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE3 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE3(config)#evpn mpls id 1700 xconnect target-mpls-id 1800 | Configure the EVPN-VPWS identifier with a source identifier of 1700 and a target identifier of 1800. |
PE3(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE3(config-evpn-mpls)#commit | Commit the transaction. |
PE3(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE3(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE3(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE3(config-evpn-mpls)#commit | Commit the transaction. |
PE3(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE3: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE3 is carried out to configure various parameters including system-MAC, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE3(config)#interface po1 | Enter the port channel interface mode for po1 |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#evpn multi-homed system-mac 0000.2222.7777 load-balancing port-active | Configure the system-mac address 0000.2222.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE3(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE3(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE3(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE3(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE3(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE3(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE3(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE3(config)#interface xe2 | Enter the interface mode for xe2. |
PE3(config-if)#speed 10g | Set the speed to 10g. |
PE3(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE3(config-if)#exit | Exit interface mode xe2 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE3 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE3(config)#interface sa1 | Enter the single active interface mode for sa1. |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#evpn multi-homed esi 00:00:22:22:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:22:22:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE3(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE3(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE3(config-if)#exit | Exit interface mode sa1 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3(config)#interface sa1.1 switchport | Create a Layer 2 sub-interface sa1.1 within the port channel. |
PE3(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE3(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE3(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE3(config-if)#exit | Exit interface mode sa1.1 and return to the configure mode. |
PE3(config)#interface xe2 | Enter the interface mode for xe2. |
PE3(config-if)#speed 10g | Set the speed to 10g. |
PE3(config-if)#static-channel-group 1 | Attach the static-channel-group 1, the LAG interface sa1 to xe2. |
PE3(config-if)#exit | Exit interface mode xe2 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE4: Loopback Interface
The configuration on PE4 for a loopback interface with IP address 10.10.10.4/32 secondary is set up to provide IP connectivity for the router.
PE4#configure terminal | Enter configure mode. |
PE4(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE4(config-if)#ip address 10.10.10.4/32 secondary | Configure a secondary IP address, 10.10.10.4/32, on the loopback interface. |
PE4(config-if)#exit | Exit interface mode lo. |
PE4(config)#commit | Commit the transaction. |
PE4: Global LDP
The configuration on PE4 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE4(config)#router ldp | Enter the Router LDP mode. |
PE4(config-router)#router-id 10.10.10.4 | Set the router ID for LDP to 10.10.10.4. |
PE4(config-router)#transport-address ipv4 10.10.10.4 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE4(config-router)#targeted-peer ipv4 10.10.10.1 | Configure targeted peer for LDP using IPv4 addresses. |
PE4(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE4(config-router)#targeted-peer ipv4 10.10.10.2 | Configure targeted peer for LDP using IPv4 addresses. |
PE4(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE4(config-router)#targeted-peer ipv4 10.10.10.3 | Configure targeted peer for LDP using IPv4 addresses. |
PE4(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE4(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: Global EVPN MPLS Command
The configuration on PE4 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE4(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE4, enabling it to participate in EVPN MPLS services. |
PE4(config)#commit | Commit candidate configuration to be running configuration. |
PE4(config)#evpn mpls vtep-ip-global 10.10.10.4 | Configure the global VTEP IP address 10.10.10.4, associating it with the loopback IP. |
PE4(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE4(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE4 to support multi-homed EVPN MPLS services. |
PE4(config)#commit | Commit the transaction. |
PE4: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE4 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE4(config)#interface xe2 | Enter interface mode xe2. |
PE4(config-if)#ip address 10.1.5.1/30 | Configure an IP address, 10.1.5.1/30, on the interface xe2. |
PE4(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE4(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE4(config-if)#exit | Exit interface mode xe2. |
PE4(config)#commit | Commit the transaction. |
PE4(config)#interface xe0 | Enter interface mode xe0. |
PE4(config-if)#ip address 10.1.8.1/30 | Configure an IP address, 10.1.8.1/30, on the interface xe0. |
PE4(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE4(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE4(config-if)#exit | Exit interface mode xe0. |
PE4(config)#commit | Commit the transaction. |
PE4: OSPF Configuration
The below configuration is performed to set up OSPF on PE4, specifying the router ID, defining network interfaces, and configuring BFD parameters for efficient routing.
PE4(config)#router ospf 100 | Enter the router OSPF mode. Configure PE4 to run OSPF with process ID 100. |
PE4(config-router)#ospf router-id 10.10.10.4 | Set the OSPF router ID to 10.10.10.4, identifying PE3 within the OSPF network. |
PE4(config-router)#network 10.10.10.4/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
PE4(config-router)#network 10.1.5.1/32 area 0.0.0.0 | Advertise loopback address in OSPF. |
PE4(config-router)#network 10.1.8.1/30 area 0.0.0.0 | Advertise network address in OSPF. |
PE4(config-router)#bfd interval 3 minrx 3 multiplier 3 | Configure BFD interval with an interval of 3, a minimum receive interval of 3, and a multiplier of 3. |
PE4(config-router)#exit | Exit router OSPF mode and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: BGP Configuration
The below BGP configuration on PE4 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE4(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE4(config-router)#bgp router-id 10.10.10.4 | Configure BGP router ID 10.10.10.4, identifying PE4 within the BGP network. |
PE4(config-router)#neighbor 10.10.10.1 remote-as 65010 | Configure neighbor 10.10.10.1 as an iBGP neighbor with their remote AS number 65010. |
PE4(config-router)#neighbor 10.10.10.1 update-source lo | Configure neighbor 10.10.10.1 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE4(config-router)#neighbor 10.10.10.2 remote-as 65010 | Configure neighbor 10.10.10.2 as an iBGP neighbor with their remote AS number 65010. |
PE4(config-router)#neighbor 10.10.10.2 update-source lo | Configure neighbor 10.10.10.2 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE4(config-router)#neighbor 10.10.10.3 remote-as 65010 | Configure neighbor 10.10.10.3 as an iBGP neighbor with their remote AS number 65010. |
PE4(config-router)#neighbor 10.10.10.3 update-source lo | Configure neighbor 10.10.10.3 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE4(config-router)#neighbor 10.10.10.1 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE4(config-router)#neighbor 10.10.10.2 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE4(config-router)#neighbor 10.10.10.3 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE4(config-router)#neighbor 10.10.10.1 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE4(config-router)#neighbor 10.10.10.2 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE4(config-router)#neighbor 10.10.10.3 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE4(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE4(config-router-af)#neighbor 10.10.10.1 activate | Activate EVPN for iBGP neighbor 10.10.10.1 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE4(config-router-af)#neighbor 10.10.10.2 activate | Activate EVPN for iBGP neighbor 10.10.10.2 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE4(config-router-af)#neighbor 10.10.10.3 activate | Activate EVPN for iBGP neighbor 10.10.10.3 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE4(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE4(config-router)#commit | Commit the transaction. |
PE4(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE4: MAC VRF Configuration
The below MAC VRF configuration on PE4 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE4(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE4(config-vrf)#rd 10.10.10.4:1700 | Configure Route-Distinguisher value of 10.10.10.4:1700. |
PE4(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE4(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE4(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE4(config-vrf)#rd 10.10.10.4:1001 | Configure Route-Distinguisher value of 10.10.10.4:1001. |
PE4(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE4(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE4 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE4(config)#evpn mpls id 1700 xconnect target-mpls-id 1800 | Configure the EVPN-VPWS identifier with a source identifier of 1700 and a target identifier of 1800. |
PE4(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE4(config-evpn-mpls)#commit | Commit the transaction. |
PE4(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE4(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE4(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE4(config-evpn-mpls)#commit | Commit the transaction. |
PE4(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE4: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE4 is carried out to configure various parameters including system-MAC, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE4(config)#interface po1 | Enter the port channel interface mode for po1 |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#evpn multi-homed system-mac 0000.2222.7777 load-balancing port-active | Configure the system-mac address 0000.2222.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE4(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE4(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE4(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE4(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE4(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE4(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE4(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE4(config)#interface xe11 | Enter the interface mode for xe11. |
PE4(config-if)#speed 10g | Set the speed to 10g. |
PE4(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE4(config-if)#exit | Exit interface mode xe11 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE4 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE4(config)#interface sa2 | Enter the single active interface mode for sa2. |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#evpn multi-homed esi 00:00:22:22:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:22:22:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE4(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE4(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE4(config-if)#exit | Exit interface mode sa2 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4(config)#interface sa2.1 switchport | Create a Layer 2 sub-interface sa2.1 within the port channel. |
PE4(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE4(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE4(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE4(config-if)#exit | Exit interface mode sa2.1 and return to the configure mode. |
PE4(config)#interface xe11 | Enter the interface mode for xe11. |
PE4(config-if)#speed 10g | Set the speed to 10g. |
PE4(config-if)#static-channel-group 2 | Attach the static-channel-group 2, the LAG interface sa2 to xe11. |
PE4(config-if)#exit | Exit interface mode xe11 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
CE2
The following configuration steps under CE2 are set up to enable VLANs and configure interfaces for carrying VLAN traffic.
CE2#configure terminal | Enter configure mode. |
CE2(config)#bridge 1 protocol ieee vlan-bridge | Set up bridge 1 to use the IEEE VLAN bridge protocol. |
CE2(config)#vlan 2-100 bridge 1 state enable | Configure VLANs from 2-100 and associate them with bridge 1. |
CE2(config)#interface xe24 | Enter interface mode xe24. |
CE2(config-if)#switchport | Configure the interface xe24 as a Layer 2 switch port. |
CE2(config-if)#bridge-group 1 | Associate xe24 to bridge 1. |
CE2(config-if)#switchport mode trunk | Configure xe24 as a trunk port. |
CE2(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk interface xe24. |
CE2(config-if)#exit | Exit interface mode xe24. |
CE2(config)#interface po1 | Enter interface mode and configure LAG interface port-channel 1 (po1). |
CE2(config-if)#switchport | Configures port-channel 1 as a Layer 2 switch port. |
CE2(config-if)#bridge-group 1 | Associate po1 to bridge 1. |
CE2(config-if)#switchport mode trunk | Configure po1 as a trunk port. |
CE2(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk port-channel po1. |
CE2(config-if)#exit | Exit interface mode po1. |
CE2(config)#interface xe22 | Enter interface mode xe22. |
CE2(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE2(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE2(config-if)#exit | Exit interface mode xe22. |
CE2(config-if)#interface xe23 | Enter interface mode xe23. |
CE2(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE2(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE2(config-if)#commit | Commit the transaction. |
CE2(config-if)#end | Exit interface mode xe23 and configure mode. |
EVPN MPLS Active-Standby MH Validation
The following show outputs provide validation results for both single-active and port-active modes, covering ELINE and ELAN services configurations with LDP as the underlay MPLS path.
Single-Active
The following show output displays the types of load-balancing port selection criteria (PSC) used on configured static aggregators for CE1, PE1, PE2, PE3, PE4, and CE2 devices in the network Figure 3-7 using the show static-channel-group command.
CE1#show static-channel-group
Static Aggregator: sa1
Member Status
xe48 up
------------------------------------------
Static Aggregator: sa2
Member Status
xe50 up
PE1#show static-channel-group
Static Aggregator: sa1
Member Status weight
xe0 up
PE2#show static-channel-group
Static Aggregator: sa2
Member Status weight
xe8 up
PE3#show static-channel-group
Static Aggregator: sa1
Member Status weight
xe2 up
PE4#show static-channel-group
Static Aggregator: sa2
Member Status weight
xe11 up
CE2#show static-channel-group
Static Aggregator: sa1
Member Status weight
xe23 up
------------------------------------------
Static Aggregator: sa2
Member Status weight
ge11 up
Single-Active ELINE
The following show output displays the active EVPN MPLS Tunnels and load balance for ELINE on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show evpn load-balance all and show evpn mpls xconnect tunnel commands.
PE1#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:11:22:33:00:00:00:55:66:77 sa1.1 10.10.10.1 single-active auto 0 NO NO ACTIVE
00:11:22:33:00:00:00:55:66:77 ---- 10.10.10.2 single-active auto 0 NO NO ----
PE1#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.1 10.10.10.4 Installed 00:14:05 00:03:58 1800 1700
10.10.10.1 10.10.10.3 Installed 00:14:05 00:04:29 1800 1700
Total number of entries are 2
PE2#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:11:22:33:00:00:00:55:66:77 ---- 10.10.10.1 single-active auto 0 NO NO ----
00:11:22:33:00:00:00:55:66:77 sa2.1 10.10.10.2 single-active auto 0 NO NO STANDBY
ELINE
PE2#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.2 10.10.10.4 Installed 00:12:33 00:04:08 1800 1700
10.10.10.2 10.10.10.3 Installed 00:12:33 00:04:08 1800 1700
Total number of entries are 2
PE3#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:12:22:33:00:00:00:55:66:77 sa1.1 10.10.10.3 single-active auto 0 NO NO ACTIVE
00:12:22:33:00:00:00:55:66:77 ---- 10.10.10.4 single-active auto 0 NO NO ----
PE3#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.3 10.10.10.2 Installed 00:13:15 00:04:12 1700 1800
10.10.10.3 10.10.10.1 Installed 00:13:15 00:04:44 1700 1800
Total number of entries are 2
PE4#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:12:22:33:00:00:00:55:66:77 ---- 10.10.10.3 single-active auto 0 NO NO ----
00:12:22:33:00:00:00:55:66:77 sa2.1 10.10.10.4 single-active auto 0 NO NO STANDBY
PE4#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.4 10.10.10.2 Installed 00:12:52 00:04:17 1700 1800
10.10.10.4 10.10.10.1 Installed 00:12:52 00:04:17 1700 1800
Total number of entries are 2
Single-Active ELAN
The following show output displays the active EVPN SR Tunnels and load balance for ELAN on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show evpn mpls tunnel and show evpn load-balance all commands.
PE1#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.1 10.10.10.2 Installed 00:17:00 00:17:00 3000
10.10.10.1 10.10.10.4 Installed 00:18:10 00:18:10 3000
10.10.10.1 10.10.10.3 Installed 00:18:10 00:18:10 3000
Total number of entries are 3
PE1#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:11:22:33:00:00:00:55:66:77 sa1.1 10.10.10.1 single-active auto 0 NO NO ACTIVE
00:11:22:33:00:00:00:55:66:77 ---- 10.10.10.2 single-active auto 0 NO NO ----
PE2#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.2 10.10.10.4 Installed 00:17:09 00:17:09 3000
10.10.10.2 10.10.10.3 Installed 00:17:09 00:17:09 3000
10.10.10.2 10.10.10.1 Installed 00:17:09 00:17:09 3000
Total number of entries are 3
PE2#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:11:22:33:00:00:00:55:66:77 ---- 10.10.10.1 single-active auto 0 NO NO ----
00:11:22:33:00:00:00:55:66:77 sa2.1 10.10.10.2 single-active auto 0 NO NO STANDBY
PE3#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.3 10.10.10.2 Installed 00:17:11 00:17:11 3000
10.10.10.3 10.10.10.1 Installed 00:18:21 00:18:21 3000
10.10.10.3 10.10.10.4 Installed 00:29:15 00:28:54 3000
Total number of entries are 3
PE3#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:12:22:33:00:00:00:55:66:77 sa1.1 10.10.10.3 single-active auto 0 NO NO ACTIVE
00:12:22:33:00:00:00:55:66:77 ---- 10.10.10.4 single-active auto 0 NO NO ----
PE4#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.4 10.10.10.2 Installed 00:17:13 00:17:13 3000
10.10.10.4 10.10.10.1 Installed 00:18:23 00:18:23 3000
10.10.10.4 10.10.10.3 Installed 00:29:18 00:29:14 3000
Total number of entries are 3
PE4#show evpn load-balance all
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:12:22:33:00:00:00:55:66:77 ---- 10.10.10.3 single-active auto 0 NO NO ----
00:12:22:33:00:00:00:55:66:77 sa2.1 10.10.10.4 single-active auto 0 NO NO STANDBY
Port-Active
The following show output displays the Ether Channel summary for CE1, CE2, PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show etherchannel summary command.
CE1#show etherchannel summary
Aggregator po1 100001
Aggregator Type: Layer2
Admin Key: 0001 - Oper Key 0001
Link: xe48 (5049) sync: 0
Link: xe50 (5051) sync: 1
CE2#show etherchannel summary
Aggregator po1 100001
Aggregator Type: Layer2
Admin Key: 0001 - Oper Key 0001
Link: ge11 (5011) sync: 1
Link: xe23 (5023) sync: 0
PE1#show etherchannel summary
Aggregator po1 100001
Aggregator Type: Layer3
Admin Key: 0001 - Oper Key 0001
Link: xe0 (10004) sync: 0
PE2#show etherchannel summary
Aggregator po1 100001
Aggregator Type: Layer3
Admin Key: 0001 - Oper Key 0001
Link: xe8 (10029) sync: 1
PE3#show etherchannel summary
Aggregator po1 100001
Aggregator Type: Layer3
Admin Key: 0001 - Oper Key 0001
Link: xe2 (10003) sync: 0
PE4#show etherchannel summary
Aggregator po1 100001
Aggregator Type: Layer3
Admin Key: 0001 - Oper Key 0001
Link: xe11 (10012) sync: 1
The following show output displays the status of LDP sessions on PE1, PE2, PE3, PE4, P1, and P2 devices in the network Figure 3-7 using the show ldp session command.
PE1#show ldp session
Codes: m - MD5 password is not set/unset.
g - GR configuration not set/unset.
t - TCP MSS not set/unset.
Session has to be cleared manually
Code Peer IP Address IF Name My Role State KeepAlive UpTime
10.10.10.2 xe2 Passive OPERATIONAL 30 00:06:57
10.10.10.3 xe14 Passive OPERATIONAL 30 00:07:12
10.10.10.4 xe14 Passive OPERATIONAL 30 00:06:42
10.10.10.5 xe14 Passive OPERATIONAL 30 00:07:26
10.10.10.6 xe2 Passive OPERATIONAL 30 00:06:36
PE2#show ldp session
Codes: m - MD5 password is not set/unset.
g - GR configuration not set/unset.
t - TCP MSS not set/unset.
Session has to be cleared manually
Code Peer IP Address IF Name My Role State KeepAlive UpTime
10.10.10.1 xe4 Active OPERATIONAL 30 00:07:05
10.10.10.3 xe4 Passive OPERATIONAL 30 00:07:05
10.10.10.4 xe4 Passive OPERATIONAL 30 00:07:05
10.10.10.5 xe5 Passive OPERATIONAL 30 00:07:03
10.10.10.6 xe4 Passive OPERATIONAL 30 00:07:13
P1#show ldp session
Codes: m - MD5 password is not set/unset.
g - GR configuration not set/unset.
t - TCP MSS not set/unset.
Session has to be cleared manually
Code Peer IP Address IF Name My Role State KeepAlive UpTime
10.10.10.1 xe1 Active OPERATIONAL 30 00:07:41
10.10.10.2 xe2 Active OPERATIONAL 30 00:07:11
10.10.10.3 xe4 Active OPERATIONAL 30 00:07:13
10.10.10.4 xe3 Active OPERATIONAL 30 00:07:10
P2#show ldp session
Codes: m - MD5 password is not set/unset.
g - GR configuration not set/unset.
t - TCP MSS not set/unset.
Session has to be cleared manually
Code Peer IP Address IF Name My Role State KeepAlive UpTime
10.10.10.1 xe12 Active OPERATIONAL 30 00:06:55
10.10.10.2 xe13 Active OPERATIONAL 30 00:07:24
10.10.10.3 xe11 Active OPERATIONAL 30 00:01:47
10.10.10.4 xe14 Active OPERATIONAL 30 00:06:56
PE3#show ldp session
Codes: m - MD5 password is not set/unset.
g - GR configuration not set/unset.
t - TCP MSS not set/unset.
Session has to be cleared manually
Code Peer IP Address IF Name My Role State KeepAlive UpTime
10.10.10.1 xe5 Active OPERATIONAL 30 00:07:35
10.10.10.2 xe5 Active OPERATIONAL 30 00:07:20
10.10.10.4 xe5 Passive OPERATIONAL 30 00:07:07
10.10.10.5 xe1 Passive OPERATIONAL 30 00:07:21
10.10.10.6 xe5 Passive OPERATIONAL 30 00:01:50
PE4#show ldp session
Codes: m - MD5 password is not set/unset.
g - GR configuration not set/unset.
t - TCP MSS not set/unset.
Session has to be cleared manually
Code Peer IP Address IF Name My Role State KeepAlive UpTime
10.10.10.1 xe0 Active OPERATIONAL 30 00:07:09
10.10.10.2 xe2 Active OPERATIONAL 30 00:07:24
10.10.10.3 xe0 Active OPERATIONAL 30 00:07:11
10.10.10.5 xe2 Passive OPERATIONAL 30 00:07:22
10.10.10.6 xe0 Passive OPERATIONAL 30 00:07:03
The below show output displays the details about BGP L2VPN EVPN multihoming ES routes and Ethernet advertisement per ES for PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show bgp l2vpn evpn multihoming es-route command.
PE1#show bgp l2vpn evpn multihoming es-route
RD[10.10.10.1:64512] VRF[evpn-gvrf-1]:
ESI PE IP-Address Encap Peer IP Algo AC-DF DP weight
00:00:00:11:11:77:77:00:00:00 10.10.10.1 MPLS ---------- DFT no no 0
00:00:00:11:11:77:77:00:00:00 10.10.10.2 MPLS 10.10.10.2 DFT no no 0
RD[10.10.10.2:64512]
ESI PE IP-Address Encap Peer IP Algo
AC-DF DP weight
00:00:00:11:11:77:77:00:00:00 10.10.10.2 MPLS 10.10.10.2 DFT
no no 0
PE2#show bgp l2vpn evpn multihoming es-route
RD[10.10.10.1:64512]
ESI PE IP-Address Encap Peer IP Algo AC-DF DP weight
00:00:00:11:11:77:77:00:00:00 10.10.10.1 MPLS 10.10.10.1 DFT no no 0
RD[10.10.10.2:64512] VRF[evpn-gvrf-1]:
ESI PE IP-Address Encap Peer IP Algo AC-DF DP weight
00:00:00:11:11:77:77:00:00:00 10.10.10.1 MPLS 10.10.10.1 DFT no no 0
00:00:00:11:11:77:77:00:00:00 10.10.10.2 MPLS ---------- DFT no no 0
PE3#show bgp l2vpn evpn multihoming es-route
RD[10.10.10.3:64512] VRF[evpn-gvrf-1]:
ESI PE IP-Address Encap Peer IP Algo
AC-DF DP weight
00:00:00:22:22:77:77:00:00:00 10.10.10.3 MPLS ---------- DFT
no no 0
00:00:00:22:22:77:77:00:00:00 10.10.10.4 MPLS 10.10.10.4 DFT
no no 0
RD[10.10.10.4:64512]
ESI PE IP-Address Encap Peer IP Algo
AC-DF DP weight
00:00:00:22:22:77:77:00:00:00 10.10.10.4 MPLS 10.10.10.4 DFT
no no 0
PE4#show bgp l2vpn evpn multihoming es-route
RD[10.10.10.3:64512]
ESI PE IP-Address Encap Peer IP Algo AC-DF DP weight
00:00:00:22:22:77:77:00:00:00 10.10.10.3 MPLS 10.10.10.3 DFT no no 0
RD[10.10.10.4:64512] VRF[evpn-gvrf-1]:
ESI PE IP-Address Encap Peer IP Algo AC-DF DP weight
00:00:00:22:22:77:77:00:00:00 10.10.10.3 MPLS 10.10.10.3 DFT no no 0
00:00:00:22:22:77:77:00:00:00 10.10.10.4 MPLS ---------- DFT no no 0
The following show output displays the details about Layer 2 Virtual Private Network (L2VPN) Ethernet Virtual Private Network (EVPN) routes on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show bgp l2vpn evpn multihoming ethernet-ad-per-es and show bgp l2vpn evpn multihoming ethernet-ad-per-evi comands.
PE1#show bgp l2vpn evpn multihoming ethernet-ad-per-es
RD[10.10.10.1:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
RD[10.10.10.1:64512] VRF[evpn-gvrf-1]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
RD[10.10.10.2:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
RD[10.10.10.3:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
RD[10.10.10.4:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
PE1#show bgp l2vpn evpn multihoming ethernet-ad-per-evi
RD[10.10.10.1:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
RD[10.10.10.2:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
RD[10.10.10.3:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
RD[10.10.10.4:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
PE2#show bgp l2vpn evpn multihoming ethernet-ad-per-es
RD[10.10.10.1:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
RD[10.10.10.2:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
RD[10.10.10.2:64512] VRF[evpn-gvrf-1]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
RD[10.10.10.3:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
RD[10.10.10.4:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
PE2#show bgp l2vpn evpn multihoming ethernet-ad-per-evi
RD[10.10.10.1:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
RD[10.10.10.2:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
RD[10.10.10.3:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
RD[10.10.10.4:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
PE3#show bgp l2vpn evpn multihoming ethernet-ad-per-es
RD[10.10.10.1:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
RD[10.10.10.2:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
RD[10.10.10.3:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
RD[10.10.10.3:64512] VRF[evpn-gvrf-1]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
RD[10.10.10.4:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
PE3#show bgp l2vpn evpn multihoming ethernet-ad-per-evi
RD[10.10.10.1:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
RD[10.10.10.2:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
RD[10.10.10.3:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
RD[10.10.10.4:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
PE4#show bgp l2vpn evpn multihoming ethernet-ad-per-es
RD[10.10.10.1:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
RD[10.10.10.2:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
RD[10.10.10.3:64512]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
RD[10.10.10.4:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.1 MPLS B flag
00:00:00:11:11:77:77:00:00:00 4294967295 440336 10.10.10.2 MPLS P flag
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.3 MPLS B flag
RD[10.10.10.4:64512] VRF[evpn-gvrf-1]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 4294967295 440336 10.10.10.4 MPLS P flag
PE4#show bgp l2vpn evpn multihoming ethernet-ad-per-evi
RD[10.10.10.1:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
RD[10.10.10.2:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
RD[10.10.10.3:1700]
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
RD[10.10.10.4:1700] VRF[vrf2]:
ESI Eth-Tag VNID/LABEL Nexthop IP Encap Flags
00:00:00:11:11:77:77:00:00:00 1800 27522 10.10.10.1 MPLS B flag
00:00:00:11:11:77:77:00:00:00 1800 27520 10.10.10.2 MPLS P flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.3 MPLS B flag
00:00:00:22:22:77:77:00:00:00 1700 27520 10.10.10.4 MPLS P flag
Port-Active ELINE
The following show output displays the active EVPN MPLS Tunnels for ELINE on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show evpn mpls xconnect tunnel command.
PE1#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.1 10.10.10.3 AC-Down 00:31:41 00:31:41 4 1700
10.10.10.1 10.10.10.4 AC-Down 00:31:41 00:31:41 4 1700
Total number of entries are 2
PE2#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.2 10.10.10.3 Installed 00:12:21 00:11:40 1800 1700
10.10.10.2 10.10.10.4 Installed 00:17:43 00:17:37 1800 1700
Total number of entries are 2
PE3#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.3 10.10.10.1 AC-Down 00:12:26 00:12:26 1700 1800
10.10.10.3 10.10.10.2 AC-Down 00:12:26 00:12:26 1700 1800
Total number of entries are 2
PE4#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.4 10.10.10.1 Installed 00:12:28 00:12:28 1700 1800
10.10.10.4 10.10.10.2 Installed 00:12:28 00:12:28 1700 1800
Total number of entries are 2
Port-Active ELAN
The following show outputs provide validation for ELAN configurations.
The following show output displays the active EVPN MPLS Tunnels for ELAN on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show evpn mpls tunnel command.
PE1#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.1 10.10.10.4 Installed 00:02:35 00:02:35 3000
10.10.10.1 10.10.10.3 Installed 00:03:00 00:03:00 3000
10.10.10.1 10.10.10.2 Installed 00:03:26 00:03:26 3000
Total number of entries are 3
PE2#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.2 10.10.10.4 Installed 00:02:45 00:02:45 3000
10.10.10.2 10.10.10.3 Installed 00:03:10 00:03:10 3000
10.10.10.2 10.10.10.1 Installed 00:03:36 00:03:36 3000
Total number of entries are 3
PE3#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.3 10.10.10.4 Installed 00:02:56 00:02:56 3000
10.10.10.3 10.10.10.2 Installed 00:03:22 00:03:22 3000
10.10.10.3 10.10.10.1 Installed 00:03:22 00:03:22 3000
Total number of entries are 3
PE4#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.4 10.10.10.3 Installed 00:03:00 00:03:00 3000
10.10.10.4 10.10.10.1 Installed 00:03:00 00:03:00 3000
10.10.10.4 10.10.10.2 Installed 00:03:00 00:03:00 3000
Total number of entries are 3
The following show output displays the EVPN active multi-homed and load-balanced details on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show evpn load-balance port-active and show evpn multi-homing all commands.
PE1#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
===========================================================================================================================
00:00:00:11:11:77:77:00:00:00 LOCAL 10.10.10.1 port-active auto 0 NO NA STANDBY
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.2 port-active auto 0 NO NA ACTIVE
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.3 port-active ---- ---- ---- ---- STANDBY
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.4 port-active ---- ---- ---- ---- ACTIVE
PE1#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 po1 10.10.10.1
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.2
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.3
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.4
Total number of entries are 4
PE2#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
===========================================================================================================================
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.1 port-active auto 0 NO NA STANDBY
00:00:00:11:11:77:77:00:00:00 LOCAL 10.10.10.2 port-active auto 0 NO NA ACTIVE
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.3 port-active --- ---- ---- ---- STANDBY
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.4 port-active ---- ---- ---- ---- ACTIVE
PE2#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.1
00:00:00:11:11:77:77:00:00:00 po1 10.10.10.2
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.3
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.4
Total number of entries are 4
PE3#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
============================================================================================================================
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.1 port-active ---- ---- ---- ---- STANDBY
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.2 port-active ---- ---- ---- ---- ACTIVE
00:00:00:22:22:77:77:00:00:00 LOCAL 10.10.10.3 port-active auto 0 NO NA STANDBY
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.4 port-active auto 0 NO NA ACTIVE
PE3#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.1
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.2
00:00:00:22:22:77:77:00:00:00 po1 10.10.10.3
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.4
Total number of entries are 4
PE4#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.1 port-active ---- ---- ---- ---- STANDBY
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.2 port-active ---- ---- ---- ---- ACTIVE
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.3 port-active auto 0 NO NA STANDBY
00:00:00:22:22:77:77:00:00:00 LOCAL 10.10.10.4 port-active auto 0 NO NA ACTIVE
PE4#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.1
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.2
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.3
00:00:00:22:22:77:77:00:00:00 po1 10.10.10.4
EVPN SR Active-Standby Multi-Homing Configuration
This section illustrates the Multi-Homed setup for the EVPN Segment Routing (SR) Active-Standby configuration, showcasing examples for both ELINE and ELAN services with SR as the underlay MPLS path.
EVPN SR Active-Standby MH Topology
Figure 3-8 consists of customer edge routers CE1 and CE2, along with IPv4 Provider Edge routers PE1, PE2, PE3, and PE4, all interconnected through the core routers P1 and P2 in the IPv4 MPLS provider network.
EVPN MPLS AS MH Configuration
CE1
The following configuration steps under CE1 are set up to enable VLANs and configure interfaces for carrying VLAN traffic.
CE1#configure terminal | Enter configure mode. |
CE1(config)#bridge 1 protocol ieee vlan-bridge | Set up bridge 1 to use the IEEE VLAN bridge protocol. |
CE1(config)#vlan 2-100 bridge 1 state enable | Configure VLANs from 2-100 and associate them with bridge 1. |
CE1(config)#interface xe54 | Enter interface mode xe54. |
CE1(config-if)#switchport | Configure the interface xe54 as a Layer 2 switch port. |
CE1(config-if)#bridge-group 1 | Associate xe54 to bridge 1. |
CE1(config-if)#switchport mode trunk | Configure xe54 as a trunk port. |
CE1(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk interface xe54. |
CE1(config-if)#exit | Exit interface mode xe54. |
CE1(config)#interface po1 | Enter interface mode and configure LAG interface port-channel 1 (po1). |
CE1(config-if)#switchport | Configures port-channel 1 as a Layer 2 switch port. |
CE1(config-if)#bridge-group 1 | Associate po1 to bridge 1. |
CE1(config-if)#switchport mode trunk | Configure po1 as a trunk port. |
CE1(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk port-channel po1. |
CE1(config-if)#exit | Exit interface mode po1. |
CE1(config)#interface xe48 | Enter interface mode xe48. |
CE1(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE1(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE1(config-if)#exit | Exit interface mode xe48. |
CE1(config-if)#interface xe50 | Enter interface mode xe50. |
CE1(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE1(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE1(config-if)#commit | Commit the transaction. |
CE1(config-if)#end | Exit interface mode xe50 and configure mode. |
PE1: Loopback Interface
The configuration on PE1 for a loopback interface with IP address 10.10.10.1/32 secondary is set up to provide IP connectivity for the ISIS router.
PE1#configure terminal | Enter configure mode. |
PE1(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE1(config-if)#ip address 10.10.10.1/32 secondary | Configure a secondary IP address, 10.10.10.1/32, on the loopback interface. |
PE1(config-if)#ip router isis 1 | Enable ISIS routing on a loopback interface lo for area 1. |
PE1(config-if)#prefix-sid index 800 | Configure a prefix segment identifier (prefix-SID) index value as 800. |
PE1(config-if)#exit | Exit interface mode lo. |
PE1(config)#commit | Commit the transaction. |
PE1: Configure SR
The following configurations aim to activate Segment Routing (SR) on PE1 and make MPLS the preferred method for segment routing, optimizing routing efficiency.
PE1(config)#segment-routing | Configure segment routing on PE1 device. |
PE1(config-sr)#mpls sr-prefer | Set MPLS as the preferred segment routing protocol over others. |
PE1(config-sr)#exit | Exit the router SR mode. |
PE1(config)#commit | Commit the transaction. |
PE1: Global LDP
The configuration on PE1 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE1(config)#router ldp | Enter the Router LDP mode. |
PE1(config-router)#router-id 10.10.10.1 | Set the router ID for LDP to 10.10.10.1. |
PE1(config-router)#transport-address ipv4 10.10.10.1 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE1(config-router)#targeted-peer ipv4 10.10.10.2 | Configure targeted peer for LDP using IPv4 addresses. |
PE1(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE1(config-router)#targeted-peer ipv4 10.10.10.3 | Configure targeted peer for LDP using IPv4 addresses. |
PE1(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE1(config-router)#targeted-peer ipv4 10.10.10.4 | Configure targeted peer for LDP using IPv4 addresses. |
PE1(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE1(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: Global EVPN MPLS Command
The configuration on PE1 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE1(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE1, enabling it to participate in EVPN MPLS services. |
PE1(config)#commit | Commit candidate configuration to be running configuration. |
PE1(config)#evpn mpls vtep-ip-global 10.10.10.1 | Configure the global VTEP IP address 10.10.10.1, associating it with the loopback IP. |
PE1(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE1(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE1 to support multi-homed EVPN MPLS services. |
PE1(config)#commit | Commit the transaction. |
PE1: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE1 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE1(config)#interface xe1 | Enter interface mode xe1. |
PE1(config-if)#ip address 10.1.1.1/30 | Configure an IP address, 10.1.1.1/30, on the interface xe1. |
PE1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE1(config-if)#ip router isis 1 | Enable ISIS IPv4 routing on an interface xe1. |
PE1(config-if)#exit | Exit interface mode xe1. |
PE1(config)#commit | Commit the transaction. |
PE1(config)#interface xe2 | Enter interface mode xe2. |
PE1(config-if)#ip address 10.1.2.1/30 | Configure an IP address, 10.1.2.1/30, on the interface xe2. |
PE1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE1(config-if)#ip router isis 1 | Enable ISIS IPv4 routing on an interface xe2. |
PE1(config-if)#exit | Exit interface mode xe2. |
PE1(config)#commit | Commit the transaction. |
PE1: ISIS Configuration
The below configuration is performed to set up ISIS on PE1, to enable MPLS Traffic Engineering, Segment Routing, and other related features for efficient routing and network management.
PE1(config)#router isis 1 | Enter router ISIS mode. |
PE1(config-router)#is-type level-1-2 | Configure IS-Type as Level-1-2 specifies that the router will participate in both Level-1 and Level-2 areas within the ISIS network. |
PE1(config-router)#metric-style wide | Configure the new style of metric type as wide. |
PE1(config-router)#mpls traffic-eng router-id 10.10.10.1 | Configure the router's MPLS Traffic Engineering (TE) router ID TLV to 10.10.10.1, which is used for MPLS-TE path calculations. |
PE1(config-router)#mpls traffic-eng level-1 | Enable MPLS-TE for IS-Type Level-1 routing. |
PE1(config-router)#mpls traffic-eng level-2 | Enable MPLS-TE for IS-Type Level-2 routing. |
PE1(config-router)#capability cspf | Enable Constraint Shortest Path First (CSPF) computation for traffic engineering. |
PE1(config-router)#dynamic-hostname | Configure the hostname to be advertised for an ISIS instance. |
PE1(config-router)#fast-reroute ti-lfa level-1 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE1(config-router)#fast-reroute ti-lfa level-2 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE1(config-router)#bfd all-interfaces | Configure BFD on all interfaces for fast link failure detection. |
PE1(config-router)#net 49.0000.0000.0001.00 | Set a Network Entity Title (NET) for this ISIS instance, specifying the area address and the system ID. |
PE1(config-router)#isis segment-routing global block 17000 23500 | Enable ISIS SR globally and allocates label blocks for Segment Routing. |
PE1(config-router)#segment-routing mpls | Enable SR ISIS. |
PE1(config-router)#exit | Exit router ISIS mode and return to configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: BGP Configuration
The below BGP configuration on PE1 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE1(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE1(config-router)#bgp router-id 10.10.10.1 | Configure BGP router ID 10.10.10.1, identifying PE1 within the BGP network. |
PE1(config-router)#neighbor 10.10.10.2 remote-as 65010 | Configure neighbor 10.10.10.2 as an iBGP neighbor with their remote AS number 65010. |
PE1(config-router)#neighbor 10.10.10.2 update-source lo | Configure neighbor 10.10.10.2 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE1(config-router)#neighbor 10.10.10.3 remote-as 65010 | Configure neighbor 10.10.10.3 as an iBGP neighbor with their remote AS number 65010. |
PE1(config-router)#neighbor 10.10.10.3 update-source lo | Configure neighbor 10.10.10.3 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE1(config-router)#neighbor 10.10.10.4 remote-as 65010 | Configure neighbor 10.10.10.4 as an iBGP neighbor with their remote AS number 65010. |
PE1(config-router)#neighbor 10.10.10.4 update-source lo | Configure neighbor 10.10.10.4 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE1(config-router)#neighbor 10.10.10.2 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE1(config-router)#neighbor 10.10.10.3 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE1(config-router)#neighbor 10.10.10.4 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE1(config-router)#neighbor 10.10.10.2 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE1(config-router)#neighbor 10.10.10.3 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE1(config-router)#neighbor 10.10.10.4 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE1(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE1(config-router-af)#neighbor 10.10.10.2 activate | Activate EVPN for iBGP neighbor 10.10.10.2 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE1(config-router-af)#neighbor 10.10.10.3 activate | Activate EVPN for iBGP neighbor 10.10.10.3 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE1(config-router-af)#neighbor 10.10.10.4 activate | Activate EVPN for iBGP neighbor 10.10.10.4 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE1(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE1(config-router)#commit | Commit the transaction. |
PE1(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE1: MAC VRF Configuration
The below MAC VRF configuration on PE1 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE1(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE1(config-vrf)#rd 10.10.10.1:1700 | Configure Route-Distinguisher value of 10.10.10.1:1700. |
PE1(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE1(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE1(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE1(config-vrf)#rd 10.10.10.1:1001 | Configure Route-Distinguisher value of 10.10.10.1:1001. |
PE1(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE1(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE1 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE1(config)#evpn mpls id 1800 xconnect target-mpls-id 1700 | Configure the EVPN-VPWS identifier with a source identifier of 1800 and a target identifier of 1700. |
PE1(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE1(config-evpn-mpls)#commit | Commit the transaction. |
PE1(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE1(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE1(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE1(config-evpn-mpls)#commit | Commit the transaction. |
PE1(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE1: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE1 is carried out to configure various parameters including system-mac, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE1(config)#interface po1 | Enter the port channel interface mode for po1 |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#evpn multi-homed system-mac 0000.1111.7777 load-balancing port-active | Configure the system-mac address 0000.1111.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE1(config-if-es)#service-carving auto | Configure service carving as auto. |
PE1(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE1(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE1(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE1(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE1(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE1(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE1(config)#interface xe0 | Enter the interface mode for xe0. |
PE1(config-if)#speed 10g | Set the speed to 10g. |
PE1(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE1(config-if)#exit | Exit interface mode xe0 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE1 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE1(config)#interface sa1 | Enter the single active interface mode for sa1 |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#evpn multi-homed esi 00:00:11:11:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:11:11:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE1(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE1(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE1(config-if)#exit | Exit interface mode sa1 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE1(config)#interface sa1.1 switchport | Create a Layer 2 sub-interface sa1.1 within the port channel. |
PE1(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE1(config-if)#load-interval 30 | Set the load interval to 30. |
PE1(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE1(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE1(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE1(config-if)#exit | Exit interface mode sa1.1 and return to the configure mode. |
PE1(config)#interface xe0 | Enter the interface mode for xe0. |
PE1(config-if)#speed 10g | Set the speed to 10g. |
PE1(config-if)#static-channel-group 1 | Attach the static-channel-group 1, the LAG interface sa1 to xe0. |
PE1(config-if)#exit | Exit interface mode xe0 and return to the configure mode. |
PE1(config)#commit | Commit the transaction. |
PE2: Loopback Interface
The configuration on PE2 for a loopback interface with IP address 10.10.10.2/32 secondary is set up to provide IP connectivity for the ISIS router.
PE2#configure terminal | Enter configure mode. |
PE2(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE2(config-if)#ip address 10.10.10.2/32 secondary | Configure a secondary IP address, 10.10.10.2/32, on the loopback interface. |
PE2(config-if)#ip router isis 1 | Enable ISIS routing on a loopback interface lo for area 1. |
PE2(config-if)#prefix-sid index 800 | Configure a prefix segment identifier (prefix-SID) index value as 800. |
PE2(config-if)#exit | Exit interface mode lo. |
PE2(config)#commit | Commit the transaction. |
PE2: Configure SR
The following configurations aim to activate Segment Routing (SR) on PE2 and make MPLS the preferred method for segment routing, optimizing routing efficiency.
PE2(config)#segment-routing | Configure segment routing on PE2 device. |
PE2(config-sr)#mpls sr-prefer | Set MPLS as the preferred segment routing protocol over others. |
PE2(config-sr)#exit | Exit the router SR mode. |
PE2(config)#commit | Commit the transaction. |
PE2: Global LDP
The configuration on PE2 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE2(config)#router ldp | Enter the Router LDP mode. |
PE2(config-router)#router-id 10.10.10.2 | Set the router ID for LDP to 10.10.10.2. |
PE2(config-router)#transport-address ipv4 10.10.10.2 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE2(config-router)#targeted-peer ipv4 10.10.10.1 | Configure targeted peer for LDP using IPv4 addresses. |
PE2(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE2(config-router)#targeted-peer ipv4 10.10.10.3 | Configure targeted peer for LDP using IPv4 addresses. |
PE2(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE2(config-router)#targeted-peer ipv4 10.10.10.4 | Configure targeted peer for LDP using IPv4 addresses. |
PE2(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE2(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: Global EVPN MPLS Command
The configuration on PE2 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE2(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE2, enabling it to participate in EVPN MPLS services. |
PE2(config)#commit | Commit candidate configuration to be running configuration. |
PE2(config)#evpn mpls vtep-ip-global 10.10.10.2 | Configure the global VTEP IP address 10.10.10.2, associating it with the loopback IP. |
PE2(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE2(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE2 to support multi-homed EVPN MPLS services. |
PE2(config)#commit | Commit the transaction. |
PE2: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE2 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE2(config)#interface xe4 | Enter interface mode xe4. |
PE2(config-if)#ip address 10.1.3.1/30 | Configure an IP address, 10.1.3.1/30, on the interface xe4. |
PE2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE2(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe4 for area 1. |
PE2(config-if)#exit | Exit interface mode xe4. |
PE2(config)#commit | Commit the transaction. |
PE2(config)#interface xe5 | Enter interface mode xe5. |
PE2(config-if)#ip address 10.1.4.1/30 | Configure an IP address, 10.1.4.1/30, on the interface xe5. |
PE2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE2(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe5 for area 1. |
PE2(config-if)#exit | Exit interface mode xe5. |
PE2(config)#commit | Commit the transaction. |
PE2: ISIS Configuration
The below configuration is performed to set up ISIS on PE2, to enable MPLS Traffic Engineering, Segment Routing, and other related features for efficient routing and network management.
PE2(config)#router isis 1 | Enter router ISIS mode. |
PE2(config-router)#is-type level-1-2 | Configure IS-Type as Level-1-2 specifies that the router will participate in both Level-1 and Level-2 areas within the ISIS network. |
PE2(config-router)#metric-style wide | Configure the new style of metric type as wide. |
PE2(config-router)#mpls traffic-eng router-id 10.10.10.2 | Configure the router's MPLS Traffic Engineering (TE) router ID TLV to 10.10.10.2, which is used for MPLS-TE path calculations. |
PE2(config-router)#mpls traffic-eng level-1 | Enable MPLS-TE for IS-Type Level-1 routing. |
PE2(config-router)#mpls traffic-eng level-2 | Enable MPLS-TE for IS-Type Level-2 routing. |
PE2(config-router)#capability cspf | Enable Constraint Shortest Path First (CSPF) computation for traffic engineering. |
PE2(config-router)#dynamic-hostname | Configure the hostname to be advertised for an ISIS instance. |
PE2(config-router)#fast-reroute ti-lfa level-1 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE2(config-router)#fast-reroute ti-lfa level-2 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE2(config-router)#bfd all-interfaces | Configure BFD on all interfaces for fast link failure detection. |
PE2(config-router)#net 49.0000.0000.0002.00 | Set a Network Entity Title (NET) for this ISIS instance, specifying the area address and the system ID. |
PE2(config-router)#isis segment-routing global block 17000 23500 | Enable ISIS SR globally and allocates label blocks for Segment Routing. |
PE2(config-router)#segment-routing mpls | Enable SR ISIS. |
PE2(config-router)#exit | Exit router ISIS mode and return to configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: BGP Configuration
The below BGP configuration on PE2 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE2(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE2(config-router)#bgp router-id 10.10.10.2 | Configure BGP router ID 10.10.10.2, identifying PE2 within the BGP network. |
PE2(config-router)#neighbor 10.10.10.1 remote-as 65010 | Configure neighbor 10.10.10.1 as an iBGP neighbor with their remote AS number 65010. |
PE2(config-router)#neighbor 10.10.10.1 update-source lo | Configure neighbor 10.10.10.1 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE2(config-router)#neighbor 10.10.10.3 remote-as 65010 | Configure neighbor 10.10.10.3 as an iBGP neighbor with their remote AS number 65010. |
PE2(config-router)#neighbor 10.10.10.3 update-source lo | Configure neighbor 10.10.10.3 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE2(config-router)#neighbor 10.10.10.4 remote-as 65010 | Configure neighbor 10.10.10.4 as an iBGP neighbor with their remote AS number 65010. |
PE2(config-router)#neighbor 10.10.10.4 update-source lo | Configure neighbor 10.10.10.4 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE2(config-router)#neighbor 10.10.10.1 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE2(config-router)#neighbor 10.10.10.3 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE2(config-router)#neighbor 10.10.10.4 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE2(config-router)#neighbor 10.10.10.1 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE2(config-router)#neighbor 10.10.10.3 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE2(config-router)#neighbor 10.10.10.4 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE2(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE2(config-router-af)#neighbor 10.10.10.1 activate | Activate EVPN for iBGP neighbor 10.10.10.1 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE2(config-router-af)#neighbor 10.10.10.3 activate | Activate EVPN for iBGP neighbor 10.10.10.3 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE2(config-router-af)#neighbor 10.10.10.4 activate | Activate EVPN for iBGP neighbor 10.10.10.4 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE2(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE2(config-router)#commit | Commit the transaction. |
PE2(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE2: MAC VRF Configuration
The below MAC VRF configuration on PE2 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE2(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE2(config-vrf)#rd 10.10.10.2:1700 | Configure Route-Distinguisher value of 10.10.10.2:1700. |
PE2(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE2(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE2(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE2(config-vrf)#rd 10.10.10.2:1001 | Configure Route-Distinguisher value of 10.10.10.2:1001. |
PE2(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE2(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE2 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE2(config)#evpn mpls id 1800 xconnect target-mpls-id 1700 | Configure the EVPN-VPWS identifier with a source identifier of 1800 and a target identifier of 1700. |
PE2(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE2(config-evpn-mpls)#commit | Commit the transaction. |
PE2(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE2(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE2(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE2(config-evpn-mpls)#commit | Commit the transaction. |
PE2(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE2: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE2 is carried out to configure various parameters including system-mac, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE2(config)#interface po1 | Enter the port channel interface mode for po1 |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#evpn multi-homed system-mac 0000.1111.7777 load-balancing port-active | Configure the system-mac address 0000.1111.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE2(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE2(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE2(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE2(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE2(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE2(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE2(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE2(config)#interface xe8 | Enter the interface mode for xe8. |
PE2(config-if)#speed 10g | Set the speed to 10g. |
PE2(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE2(config-if)#exit | Exit interface mode xe8 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE2 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE2(config)#interface sa2 | Enter the single active interface mode for sa2. |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#evpn multi-homed esi 00:00:11:11:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:11:11:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE2(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE2(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE2(config-if)#exit | Exit interface mode sa2 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
PE2(config)#interface sa2.1 switchport | Create a Layer 2 sub-interface sa2.1 within the port channel. |
PE2(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE2(config-if)#load-interval 30 | Set the load interval to 30. |
PE2(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE2(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE2(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE2(config-if)#exit | Exit interface mode sa2.1 and return to the configure mode. |
PE2(config)#interface xe8 | Enter the interface mode for xe8. |
PE2(config-if)#speed 10g | Set the speed to 10g. |
PE2(config-if)#static-channel-group 2 | Attach the static-channel-group 2, the LAG interface sa2 to xe8. |
PE2(config-if)#exit | Exit interface mode xe8 and return to the configure mode. |
PE2(config)#commit | Commit the transaction. |
P1: Loopback Interface
The configuration on P1 for a loopback interface with IP address 10.10.10.5/32 secondary is set up to provide IP connectivity for the router.
P1#configure terminal | Enter configure mode. |
P1(config)#interface lo | Enter the interface mode for the loopback interface lo. |
P1(config-if)#ip address 10.10.10.5/32 secondary | Configure a secondary IP address, 10.10.10.5/32, on the loopback interface. |
P1(config-if)#ip router isis 1 | Enable ISIS routing on a loopback interface lo for area 1. |
P1(config-if)#prefix-sid index 800 | Configure a prefix segment identifier (prefix-SID) index value as 800. |
P1(config-if)#exit | Exit interface mode lo. |
P1(config)#commit | Commit the transaction. |
P1: Configure SR
The following configurations aim to activate Segment Routing (SR) on P1 and make MPLS the preferred method for segment routing, optimizing routing efficiency.
P1(config)#segment-routing | Configure segment routing on P1 device. |
P1(config-sr)#mpls sr-prefer | Set MPLS as the preferred segment routing protocol over others. |
P1(config-sr)#exit | Exit the router SR mode. |
P1(config)#commit | Commit the transaction. |
P1: Global LDP
The configuration on P1 for the Global LDP router, specifying router ID and targeted peer, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
P1(config)#router ldp | Enter the Router LDP mode. |
P1(config-router)#router-id 10.10.10.5 | Set the router ID for LDP to 10.10.10.5. |
P1(config-router)#transport-address ipv4 10.10.10.5 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
P1(config-router)#exit | Exit router LDP mode and return to the configure mode. |
P1(config)#commit | Commit the transaction. |
P1: Interface Configuration
The below configuration is performed to set up interfaces on P1 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
P1(config)#interface xe1 | Enter interface mode xe1. |
P1(config-if)#ip address 10.1.1.2/30 | Configure an IP address, 10.1.1.2/30, on the interface xe1. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe1 for area 1. |
P1(config-if)#exit | Exit interface mode xe1. |
P1(config)#commit | Commit the transaction. |
P1(config)#interface xe2 | Enter interface mode xe2. |
P1(config-if)#ip address 10.1.4.2/30 | Configure an IP address, 10.1.4.2/30, on the interface xe2. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe2 for area 1. |
P1(config-if)#exit | Exit interface mode xe2. |
P1(config)#commit | Commit the transaction. |
P1(config)#interface xe3 | Enter interface mode xe3. |
P1(config-if)#ip address 10.1.5.2/30 | Configure an IP address, 10.1.5.2/30, on the interface xe3. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe3 for area 1. |
P1(config-if)#exit | Exit interface mode xe3. |
P1(config)#commit | Commit the transaction. |
P1(config)#interface xe4 | Enter interface mode xe4. |
P1(config-if)#ip address 10.1.6.2/30 | Configure an IP address, 10.1.6.2/30, on the interface xe4. |
P1(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P1(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P1(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe4 for area 1. |
P1(config-if)#exit | Exit interface mode xe4. |
P1(config)#commit | Commit the transaction. |
P1: ISIS Configuration
The below configuration is performed to set up ISIS on P1, to enable MPLS Traffic Engineering, Segment Routing, and other related features for efficient routing and network management.
P1(config)#router isis 1 | Enter router ISIS mode. |
P1(config-router)#is-type level-1-2 | Configure IS-Type as Level-1-2 specifies that the router will participate in both Level-1 and Level-2 areas within the ISIS network. |
P1(config-router)#metric-style wide | Configure the new style of metric type as wide. |
P1(config-router)#mpls traffic-eng router-id 10.10.10.5 | Configure the router's MPLS Traffic Engineering (TE) router ID TLV to 10.10.10.5, which is used for MPLS-TE path calculations. |
P1(config-router)#mpls traffic-eng level-1 | Enable MPLS-TE for IS-Type Level-1 routing. |
P1(config-router)#mpls traffic-eng level-2 | Enable MPLS-TE for IS-Type Level-2 routing. |
P1(config-router)#capability cspf | Enable Constraint Shortest Path First (CSPF) computation for traffic engineering. |
P1(config-router)#dynamic-hostname | Configure the hostname to be advertised for an ISIS instance. |
P1(config-router)#fast-reroute ti-lfa level-1 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
P1(config-router)#fast-reroute ti-lfa level-2 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
P1(config-router)#bfd all-interfaces | Configure BFD on all interfaces for fast link failure detection. |
P1(config-router)#net 49.0000.0000.0005.00 | Set a Network Entity Title (NET) for this ISIS instance, specifying the area address and the system ID. |
P1(config-router)#isis segment-routing global block 17000 23500 | Enable ISIS SR globally and allocates label blocks for Segment Routing. |
P1(config-router)#segment-routing mpls | Enable SR ISIS. |
P1(config-router)#exit | Exit router ISIS mode and return to the configure mode. |
P1(config)#commit | Commit the transaction. |
P2: Loopback Interface
The configuration on P2 for a loopback interface with IP address 10.10.10.6/32 secondary is set up to provide IP connectivity for the router.
P2#configure terminal | Enter configure mode. |
P2(config)#interface lo | Enter the interface mode for the loopback interface lo. |
P2(config-if)#ip address 10.10.10.6/32 secondary | Configure a secondary IP address, 10.10.10.6/32, on the loopback interface. |
P2(config-if)#ip router isis 1 | Enable ISIS routing on a loopback interface lo for area 1. |
P2(config-if)#prefix-sid index 800 | Configure a prefix segment identifier (prefix-SID) index value as 800. |
P2(config-if)#exit | Exit interface mode lo. |
P2(config)#commit | Commit the transaction. |
P2: Configure SR
The following configurations aim to activate Segment Routing (SR) on P2 and make MPLS the preferred method for segment routing, optimizing routing efficiency.
P2(config)#segment-routing | Configure segment routing on P2 device. |
P2(config-sr)#mpls sr-prefer | Set MPLS as the preferred segment routing protocol over others. |
P2(config-sr)#exit | Exit the router SR mode. |
P2(config)#commit | Commit the transaction. |
P2: Global LDP
The configuration on P2 for the Global LDP router, specifying router ID and targeted peer, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
P2(config)#router ldp | Enter the Router LDP mode. |
P2(config-router)#router-id 10.10.10.6 | Set the router ID for LDP to 10.10.10.6. |
P2(config-router)#transport-address ipv4 10.10.10.6 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
P2(config-router)#exit | Exit router LDP mode and return to the configure mode. |
P2(config)#commit | Commit the transaction. |
P2: Interface Configuration
The below configuration is performed to set up interfaces on P2 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
P2(config)#interface xe12 | Enter interface mode xe12. |
P2(config-if)#ip address 10.1.2.2/30 | Configure an IP address, 10.1.2.2/30, on the interface xe12. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe12 for area 1. |
P2(config-if)#exit | Exit interface mode xe12. |
P2(config)#commit | Commit the transaction. |
P2(config)#interface xe13 | Enter interface mode xe13. |
P2(config-if)#ip address 10.1.3.2/30 | Configure an IP address, 10.1.3.2/30, on the interface xe13. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe13 for area 1. |
P2(config-if)#exit | Exit interface mode xe13. |
P2(config)#commit | Commit the transaction. |
P2(config)#interface xe11 | Enter interface mode xe11. |
P2(config-if)#ip address 10.1.7.2/30 | Configure an IP address, 10.1.7.2/30, on the interface xe11. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe11 for area 1. |
P2(config-if)#exit | Exit interface mode xe11. |
P2(config)#commit | Commit the transaction. |
P2(config)#interface xe14 | Enter interface mode xe14. |
P2(config-if)#ip address 10.1.8.2/30 | Configure an IP address, 10.1.8.2/30, on the interface xe14. |
P2(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
P2(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
P2(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe14 for area 1. |
P2(config-if)#exit | Exit interface mode xe14. |
P2(config)#commit | Commit the transaction. |
P2: ISIS Configuration
The below configuration is performed to set up ISIS on P2, to enable MPLS Traffic Engineering, Segment Routing, and other related features for efficient routing and network management.
P2(config)#router isis 1 | Enter router ISIS mode. |
P2(config-router)#is-type level-1-2 | Configure IS-Type as Level-1-2 specifies that the router will participate in both Level-1 and Level-2 areas within the ISIS network. |
P2(config-router)#metric-style wide | Configure the new style of metric type as wide. |
P2(config-router)#mpls traffic-eng router-id 10.10.10.6 | Configure the router's MPLS Traffic Engineering (TE) router ID TLV to 10.10.10.6, which is used for MPLS-TE path calculations. |
P2(config-router)#mpls traffic-eng level-1 | Enable MPLS-TE for IS-Type Level-1 routing. |
P2(config-router)#mpls traffic-eng level-2 | Enable MPLS-TE for IS-Type Level-2 routing. |
P2(config-router)#capability cspf | Enable Constraint Shortest Path First (CSPF) computation for traffic engineering. |
P2(config-router)#dynamic-hostname | Configure the hostname to be advertised for an ISIS instance. |
P2(config-router)#fast-reroute ti-lfa level-1 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
P2(config-router)#fast-reroute ti-lfa level-2 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
P2(config-router)#bfd all-interfaces | Configure BFD on all interfaces for fast link failure detection. |
P2(config-router)#net 49.0000.0000.0006.00 | Set a Network Entity Title (NET) for this ISIS instance, specifying the area address and the system ID. |
P2(config-router)#isis segment-routing global block 17000 23500 | Enable ISIS SR globally and allocates label blocks for Segment Routing. |
P2(config-router)#segment-routing mpls | Enable SR ISIS. |
P2(config-router)#exit | Exit router ISIS mode and return to the configure mode. |
P2(config)#commit | Commit the transaction. |
PE3: Loopback Interface
The configuration on PE3 for a loopback interface with IP address 10.10.10.3/32 secondary is set up to provide IP connectivity for the router.
PE3#configure terminal | Enter configure mode. |
PE3(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE3(config-if)#ip address 10.10.10.3/32 secondary | Configure a secondary IP address, 10.10.10.3/32, on the loopback interface. |
PE3(config-if)#ip router isis 1 | Enable ISIS routing on a loopback interface lo for area 1. |
PE3(config-if)#prefix-sid index 800 | Configure a prefix segment identifier (prefix-SID) index value as 800. |
PE3(config-if)#exit | Exit interface mode lo. |
PE3(config)#commit | Commit the transaction. |
PE3: Configure SR
The following configurations aim to activate Segment Routing (SR) on PE3 and make MPLS the preferred method for segment routing, optimizing routing efficiency.
PE3(config)#segment-routing | Configure segment routing on PE3 device. |
PE3(config-sr)#mpls sr-prefer | Set MPLS as the preferred segment routing protocol over others. |
PE3(config-sr)#exit | Exit the router SR mode. |
PE3(config)#commit | Commit the transaction. |
PE3: Global LDP
The configuration on PE3 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE3(config)#router ldp | Enter the Router LDP mode. |
PE3(config-router)#router-id 10.10.10.3 | Set the router ID for LDP to 10.10.10.3. |
PE2(config-router)#transport-address ipv4 10.10.10.3 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE3(config-router)#targeted-peer ipv4 10.10.10.1 | Configure targeted peer for LDP using IPv4 addresses. |
PE3(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE3(config-router)#targeted-peer ipv4 10.10.10.2 | Configure targeted peer for LDP using IPv4 addresses. |
PE3(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE3(config-router)#targeted-peer ipv4 10.10.10.4 | Configure targeted peer for LDP using IPv4 addresses. |
PE3(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE3(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: Global EVPN MPLS Command
The configuration on PE3 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE3(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE3, enabling it to participate in EVPN MPLS services. |
PE3(config)#commit | Commit candidate configuration to be running configuration. |
PE3(config)#evpn mpls vtep-ip-global 10.10.10.3 | Configure the global VTEP IP address 10.10.10.3, associating it with the loopback IP. |
PE3(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE3(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE3 to support multi-homed EVPN MPLS services. |
PE3(config)#commit | Commit the transaction. |
PE3: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE3 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE3(config)#interface xe1 | Enter interface mode xe1. |
PE3(config-if)#ip address 10.1.6.1/30 | Configure an IP address, 10.1.6.1/30, on the interface xe1. |
PE3(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE3(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE3(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe1 for area 1. |
PE3(config-if)#exit | Exit interface mode xe1. |
PE3(config)#commit | Commit the transaction. |
PE3(config)#interface xe5 | Enter interface mode xe5. |
PE3(config-if)#ip address 10.1.7.1/30 | Configure an IP address, 10.1.7.1/30, on the interface xe5. |
PE3(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE3(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE3(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe5 for area 1. |
PE3(config-if)#exit | Exit interface mode xe5. |
PE3(config)#commit | Commit the transaction. |
PE3: ISIS Configuration
The below configuration is performed to set up ISIS on PE3, to enable MPLS Traffic Engineering, Segment Routing, and other related features for efficient routing and network management.
PE3(config)#router isis 1 | Enter router ISIS mode. |
PE3(config-router)#is-type level-1-2 | Configure IS-Type as Level-1-2 specifies that the router will participate in both Level-1 and Level-2 areas within the ISIS network. |
PE3(config-router)#metric-style wide | Configure the new style of metric type as wide. |
PE3(config-router)#mpls traffic-eng router-id 10.10.10.3 | Configure the router's MPLS Traffic Engineering (TE) router ID TLV to 10.10.10.3, which is used for MPLS-TE path calculations. |
PE3(config-router)#mpls traffic-eng level-1 | Enable MPLS-TE for IS-Type Level-1 routing. |
PE3(config-router)#mpls traffic-eng level-2 | Enable MPLS-TE for IS-Type Level-2 routing. |
PE3(config-router)#capability cspf | Enable Constraint Shortest Path First (CSPF) computation for traffic engineering. |
PE3(config-router)#dynamic-hostname | Configure the hostname to be advertised for an ISIS instance. |
PE3(config-router)#fast-reroute ti-lfa level-1 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE3(config-router)#fast-reroute ti-lfa level-2 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE3(config-router)#bfd all-interfaces | Configure BFD on all interfaces for fast link failure detection. |
PE3(config-router)#net 49.0000.0000.0003.00 | Set a Network Entity Title (NET) for this ISIS instance, specifying the area address and the system ID. |
PE3(config-router)#isis segment-routing global block 17000 23500 | Enable ISIS SR globally and allocates label blocks for Segment Routing. |
PE3(config-router)#segment-routing mpls | Enable SR ISIS. |
PE3(config-router)#exit | Exit router ISIS mode and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: BGP Configuration
The below BGP configuration on PE3 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE3(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE3(config-router)#bgp router-id 10.10.10.3 | Configure BGP router ID 10.10.10.3, identifying PE3 within the BGP network. |
PE3(config-router)#neighbor 10.10.10.1 remote-as 65010 | Configure neighbor 10.10.10.1 as an iBGP neighbor with their remote AS number 65010. |
PE3(config-router)#neighbor 10.10.10.1 update-source lo | Configure neighbor 10.10.10.1 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE3(config-router)#neighbor 10.10.10.2 remote-as 65010 | Configure neighbor 10.10.10.2 as an iBGP neighbor with their remote AS number 65010. |
PE3(config-router)#neighbor 10.10.10.2 update-source lo | Configure neighbor 10.10.10.2 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE3(config-router)#neighbor 10.10.10.4 remote-as 65010 | Configure neighbor 10.10.10.4 as an iBGP neighbor with their remote AS number 65010. |
PE3(config-router)#neighbor 10.10.10.4 update-source lo | Configure neighbor 10.10.10.4 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE3(config-router)#neighbor 10.10.10.1 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE3(config-router)#neighbor 10.10.10.2 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE3(config-router)#neighbor 10.10.10.4 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE3(config-router)#neighbor 10.10.10.1 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE3(config-router)#neighbor 10.10.10.2 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE3(config-router)#neighbor 10.10.10.4 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE3(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE3(config-router-af)#neighbor 10.10.10.1 activate | Activate EVPN for iBGP neighbor 10.10.10.1 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE3(config-router-af)#neighbor 10.10.10.2 activate | Activate EVPN for iBGP neighbor 10.10.10.2 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE3(config-router-af)#neighbor 10.10.10.4 activate | Activate EVPN for iBGP neighbor 10.10.10.4 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE3(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE3(config-router)#commit | Commit the transaction. |
PE3(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE3: MAC VRF Configuration
The below MAC VRF configuration on PE3 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE3(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE3(config-vrf)#rd 10.10.10.3:1700 | Configure Route-Distinguisher value of 10.10.10.3:1700. |
PE3(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE3(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE3(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE3(config-vrf)#rd 10.10.10.3:1001 | Configure Route-Distinguisher value of 10.10.10.3:1001. |
PE3(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE3(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE3 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE3(config)#evpn mpls id 1700 xconnect target-mpls-id 1800 | Configure the EVPN-VPWS identifier with a source identifier of 1700 and a target identifier of 1800. |
PE3(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE3(config-evpn-mpls)#commit | Commit the transaction. |
PE3(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE3(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE3(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE3(config-evpn-mpls)#commit | Commit the transaction. |
PE3(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE3: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE3 is carried out to configure various parameters including system-MAC, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE3(config)#interface po1 | Enter the port channel interface mode for po1 |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#evpn multi-homed system-mac 0000.2222.7777 load-balancing port-active | Configure the system-mac address 0000.2222.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE3(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE3(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE3(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE3(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE3(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE3(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE3(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE3(config)#interface xe2 | Enter the interface mode for xe2. |
PE3(config-if)#speed 10g | Set the speed to 10g. |
PE3(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE3(config-if)#exit | Exit interface mode xe2 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE3 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE3(config)#interface sa1 | Enter the single active interface mode for sa1. |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#evpn multi-homed esi 00:00:22:22:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:22:22:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE3(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE3(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE3(config-if)#exit | Exit interface mode sa1 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE3(config)#interface sa1.1 switchport | Create a Layer 2 sub-interface sa1.1 within the port channel. |
PE3(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE3(config-if)#load-interval 30 | Set the load interval to 30. |
PE3(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE3(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE3(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE3(config-if)#exit | Exit interface mode sa1.1 and return to the configure mode. |
PE3(config)#interface xe2 | Enter the interface mode for xe2. |
PE3(config-if)#speed 10g | Set the speed to 10g. |
PE3(config-if)#static-channel-group 1 | Attach the static-channel-group 1, the LAG interface sa1 to xe2. |
PE3(config-if)#exit | Exit interface mode xe2 and return to the configure mode. |
PE3(config)#commit | Commit the transaction. |
PE4: Loopback Interface
The configuration on PE4 for a loopback interface with IP address 10.10.10.4/32 secondary is set up to provide IP connectivity for the router.
PE4#configure terminal | Enter configure mode. |
PE4(config)#interface lo | Enter the interface mode for the loopback interface lo. |
PE4(config-if)#ip address 10.10.10.4/32 secondary | Configure a secondary IP address, 10.10.10.4/32, on the loopback interface. |
PE4(config-if)#ip router isis 1 | Enable ISIS routing on a loopback interface lo for area 1. |
PE4(config-if)#prefix-sid index 800 | Configure a prefix segment identifier (prefix-SID) index value as 800. |
PE4(config-if)#exit | Exit interface mode lo. |
PE4(config)#commit | Commit the transaction. |
PE4: Configure SR
The following configurations aim to activate Segment Routing (SR) on PE4 and make MPLS the preferred method for segment routing, optimizing routing efficiency.
PE4(config)#segment-routing | Configure segment routing on PE4 device. |
PE4(config-sr)#mpls sr-prefer | Set MPLS as the preferred segment routing protocol over others. |
PE4(config-sr)#exit | Exit the router SR mode. |
PE4(config)#commit | Commit the transaction. |
PE4: Global LDP
The configuration on PE4 for the Global LDP router, specifying router ID and targeted peers, is done to set up Label Distribution Protocol (LDP) settings for MPLS.
PE4(config)#router ldp | Enter the Router LDP mode. |
PE4(config-router)#router-id 10.10.10.4 | Set the router ID for LDP to 10.10.10.4. |
PE4(config-router)#transport-address ipv4 10.10.10.4 | Configure the transport address for IPv4 (for IPv6 use ipv6 parameter) to be used for a TCP session where LDP operates. Note: It is preferable to use the loopback address as the transport address. |
PE4(config-router)#targeted-peer ipv4 10.10.10.1 | Configure targeted peer for LDP using IPv4 addresses. |
PE4(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE4(config-router)#targeted-peer ipv4 10.10.10.2 | Configure targeted peer for LDP using IPv4 addresses. |
PE4(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE4(config-router)#targeted-peer ipv4 10.10.10.3 | Configure targeted peer for LDP using IPv4 addresses. |
PE4(config-router-targeted-peer)#exit-targeted-peer-mode | Exit router targeted-peer-mode. |
PE4(config-router)#exit | Exit router LDP mode and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: Global EVPN MPLS Command
The configuration on PE4 for the Global EVPN MPLS, includes activating EVPN MPLS, defining the global VTEP IP address, enabling hardware profile filtering for EVPN MPLS multi-homing, and activating EVPN MPLS multi-homing functionality, all of which are crucial for enabling EVPN MPLS features.
PE4(config)#evpn mpls enable | Activate the EVPN MPLS functionality on PE4, enabling it to participate in EVPN MPLS services. |
PE4(config)#commit | Commit candidate configuration to be running configuration. |
PE4(config)#evpn mpls vtep-ip-global 10.10.10.4 | Configure the global VTEP IP address 10.10.10.4, associating it with the loopback IP. |
PE4(config)#hardware-profile filter evpn-mpls-mh enable | Enable hardware-profile filter for EVPN MPLS multi-homing. |
PE4(config)#evpn mpls multihoming enable | Activate the EVPN MPLS multi-homing functionality, allowing PE4 to support multi-homed EVPN MPLS services. |
PE4(config)#commit | Commit the transaction. |
PE4: Interface Configuration Network Side
The below configuration is performed to set up network interfaces on PE4 and enable LDP for IPv4, ensuring proper routing and labeling functionality.
PE4(config)#interface xe2 | Enter interface mode xe2. |
PE4(config-if)#ip address 10.1.5.1/30 | Configure an IP address, 10.1.5.1/30, on the interface xe2. |
PE4(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE4(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE4(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe2 for area 1. |
PE4(config-if)#exit | Exit interface mode xe2. |
PE4(config)#commit | Commit the transaction. |
PE4(config)#interface xe0 | Enter interface mode xe0. |
PE4(config-if)#ip address 10.1.8.1/30 | Configure an IP address, 10.1.8.1/30, on the interface xe0. |
PE4(config-if)#enable-ldp ipv4 | Enable LDP on the physical interface, facilitating the exchange of label information between devices in the network. |
PE4(config-if)#label-switching | Enable label switching on the interface to enable MPLS-based packet forwarding. |
PE4(config-if)#ip router isis 1 | Enable ISIS routing on an interface xe2 for area 1. |
PE4(config-if)#exit | Exit interface mode xe0. |
PE4(config)#commit | Commit the transaction. |
PE4: ISIS Configuration
The below configuration is performed to set up ISIS on PE4, to enable MPLS Traffic Engineering, Segment Routing, and other related features for efficient routing and network management.
PE4(config)#router isis 1 | Enter router ISIS mode. |
PE4(config-router)#is-type level-1-2 | Configure IS-Type as Level-1-2 specifies that the router will participate in both Level-1 and Level-2 areas within the ISIS network. |
PE4(config-router)#metric-style wide | Configure the new style of metric type as wide. |
PE4(config-router)#mpls traffic-eng router-id 10.10.10.4 | Configure the router's MPLS Traffic Engineering (TE) router ID TLV to 10.10.10.4, which is used for MPLS-TE path calculations. |
PE4(config-router)#mpls traffic-eng level-1 | Enable MPLS-TE for IS-Type Level-1 routing. |
PE4(config-router)#mpls traffic-eng level-2 | Enable MPLS-TE for IS-Type Level-2 routing. |
PE4(config-router)#capability cspf | Enable Constraint Shortest Path First (CSPF) computation for traffic engineering. |
PE4(config-router)#dynamic-hostname | Configure the hostname to be advertised for an ISIS instance. |
PE4(config-router)#fast-reroute ti-lfa level-1 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE4(config-router)#fast-reroute ti-lfa level-2 proto ipv4 | Configure Remote Loop-Free Alternate (LFA) to calculate backup paths to those destinations whichever does not satisfy basic LFA FRR inequalities |
PE4(config-router)#bfd all-interfaces | Configure BFD on all interfaces for fast link failure detection. |
PE4(config-router)#net 49.0000.0000.0004.00 | Set a Network Entity Title (NET) for this ISIS instance, specifying the area address and the system ID. |
PE4(config-router)#isis segment-routing global block 17000 23500 | Enable ISIS SR globally and allocates label blocks for Segment Routing. |
PE4(config-router)#segment-routing mpls | Enable SR ISIS. |
PE4(config-router)#exit | Exit router ISIS mode and return to configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: BGP Configuration
The below BGP configuration on PE4 is established to enable BGP routing with ASN 65010, set the BGP router ID, define iBGP neighbors, configure BFD, and enable the EVPN address family for efficient routing in an EVPN environment.
PE4(config)#router bgp 65010 | Enter the Router BGP mode, ASN: 65010 |
PE4(config-router)#bgp router-id 10.10.10.4 | Configure BGP router ID 10.10.10.4, identifying PE4 within the BGP network. |
PE4(config-router)#neighbor 10.10.10.1 remote-as 65010 | Configure neighbor 10.10.10.1 as an iBGP neighbor with their remote AS number 65010. |
PE4(config-router)#neighbor 10.10.10.1 update-source lo | Configure neighbor 10.10.10.1 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE4(config-router)#neighbor 10.10.10.2 remote-as 65010 | Configure neighbor 10.10.10.2 as an iBGP neighbor with their remote AS number 65010. |
PE4(config-router)#neighbor 10.10.10.2 update-source lo | Configure neighbor 10.10.10.2 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE4(config-router)#neighbor 10.10.10.3 remote-as 65010 | Configure neighbor 10.10.10.3 as an iBGP neighbor with their remote AS number 65010. |
PE4(config-router)#neighbor 10.10.10.3 update-source lo | Configure neighbor 10.10.10.3 as an iBGP neighbor, specifying the source of routing updates as the loopback interface. |
PE4(config-router)#neighbor 10.10.10.1 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE4(config-router)#neighbor 10.10.10.2 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE4(config-router)#neighbor 10.10.10.3 fall-over bfd multihop | Configure BFD for the BGP neighbor to provide rapid failure detection. |
PE4(config-router)#neighbor 10.10.10.1 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE4(config-router)#neighbor 10.10.10.2 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE4(config-router)#neighbor 10.10.10.3 advertisement-interval 0 | Configure advertisement interval for the neighbor, allowing more frequent BGP updates. |
PE4(config-router)#address-family l2vpn evpn | Enter into address family mode for L2VPN EVPN. |
PE4(config-router-af)#neighbor 10.10.10.1 activate | Activate EVPN for iBGP neighbor 10.10.10.1 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE4(config-router-af)#neighbor 10.10.10.2 activate | Activate EVPN for iBGP neighbor 10.10.10.2 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE4(config-router-af)#neighbor 10.10.10.3 activate | Activate EVPN for iBGP neighbor 10.10.10.3 within the address family mode, ensuring that EVPN address family is enabled for the neighbor. |
PE4(config-router-af)#exit | Exit address family mode and return to the router BGP mode. |
PE4(config-router)#commit | Commit the transaction. |
PE4(config-router)#exit | Exit router BGP mode and return to the configure mode. |
PE4: MAC VRF Configuration
The below MAC VRF configuration on PE4 is carried out to define and set up VRFs named vrf2 and vpls1001 with specific Route-Distinguisher (RD) and route-target values, ensuring segregated MAC address spaces for distinct network services.
PE4(config)#mac vrf vrf2 | Enter VRF mode named vrf2. |
PE4(config-vrf)#rd 10.10.10.4:1700 | Configure Route-Distinguisher value of 10.10.10.4:1700. |
PE4(config-vrf)#route-target both 1700:1700 | Configure import and export values for the vrf2 as 1700:1700. |
PE4(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE4(config)#mac vrf vpls1001 | Enter VRF mode named vpls1001. |
PE4(config-vrf)#rd 10.10.10.4:1001 | Configure Route-Distinguisher value of 10.10.10.4:1001. |
PE4(config-vrf)#route-target both 1001:1001 | Configure import and export values for the vpls1001 as 1001:1001. |
PE4(config-vrf)#exit | Exit VRF mode and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: EVPN and VRF Mapping
The below EVPN and VRF mapping configuration on PE4 is performed to establish mappings between EVPN identifiers and VRFs, facilitating efficient routing and connectivity in an EVPN network environment.
PE4(config)#evpn mpls id 1700 xconnect target-mpls-id 1800 | Configure the EVPN-VPWS identifier with a source identifier of 1700 and a target identifier of 1800. |
PE4(config-evpn-mpls)#host-reachability-protocol evpn-bgp vrf2 | Map VRF vrf2 to the EVPN-VPWS identifier |
PE4(config-evpn-mpls)#commit | Commit the transaction. |
PE4(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE4(config)#evpn mpls id 3000 | Configure the EVPN-VPLS identifier an identifier of 3000. |
PE4(config-evpn-mpls)#host-reachability-protocol evpn-bgp vpls1001 | Map VRF vpls1001 to the EVPN-VPWS identifier |
PE4(config-evpn-mpls)#commit | Commit the transaction. |
PE4(config-evpn-mpls)#exit | Exit the EVPN MPLS mode and return to the configure mode. |
PE4: Access Port Configuration for Port-active
The below access port configuration for port-active mode on PE4 is carried out to configure various parameters including system-MAC, load balancing, service carving preferences, and EVPN settings for efficient network access and connectivity.
PE4(config)#interface po1 | Enter the port channel interface mode for po1 |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#evpn multi-homed system-mac 0000.2222.7777 load-balancing port-active | Configure the system-mac address 0000.2222.7777 for port-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE4(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE4(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE4(config-if)#exit | Exit interface mode po1 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4(config)#interface po1.1 switchport | Create a Layer 2 sub-interface po1.1 within the port channel. |
PE4(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE4(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE4(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE4(config-if)#exit | Exit interface mode po1.1 and return to the configure mode. |
PE4(config)#interface xe11 | Enter the interface mode for xe11. |
PE4(config-if)#speed 10g | Set the speed to 10g. |
PE4(config-if)#channel-group 1 mode active | Attach LAG interface po1. |
PE4(config-if)#exit | Exit interface mode xe11 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4: Access Port Configuration for Single-active
The below access port configuration for single-active mode on PE4 is implemented to set up various parameters, including Ethernet Segment Identifier (ESI) settings, service carving preferences, and EVPN configurations, ensuring efficient network access and connectivity.
PE4(config)#interface sa2 | Enter the single active interface mode for sa2. |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#evpn multi-homed esi 00:00:22:22:77:77 load-balancing single-active | Configure the ESI with the value with the value 00:00:22:22:77:77 for single-active mode, which plays a role in load balancing and enter to the EVPN Ethernet Segment (ES) mode. |
PE4(config-if-es)#service-carving auto | Configure service carving as auto, allowing automatic determination of service distribution preferences. |
PE4(config-if-es)#exit | Exit the EVPN ES mode and return to the configure mode. |
PE4(config-if)#exit | Exit interface mode sa2 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
PE4(config)#interface sa2.1 switchport | Create a Layer 2 sub-interface sa2.1 within the port channel. |
PE4(config-if)#encapsulation dot1q 100 | Set encapsulation to dot1q with VLAN ID 100. |
PE4(config-if)#load-interval 30 | Set the load interval to 30. |
PE4(config-if)#access-if-evpn | Enter the access mode for EVPN MPLS ID configuration. |
PE4(config-acc-if-evpn)#map vpn-id 1800 | Map VPN-ID 1800. |
PE4(config-acc-if-evpn)#exit | Exit the access mode and return to the interface mode. |
PE4(config-if)#exit | Exit interface mode sa2.1 and return to the configure mode. |
PE4(config)#interface xe11 | Enter the interface mode for xe11. |
PE4(config-if)#speed 10g | Set the speed to 10g. |
PE4(config-if)#static-channel-group 2 | Attach the static-channel-group 2, the LAG interface sa2 to xe11. |
PE4(config-if)#exit | Exit interface mode xe11 and return to the configure mode. |
PE4(config)#commit | Commit the transaction. |
CE2
The following configuration steps under CE2 are set up to enable VLANs and configure interfaces for carrying VLAN traffic.
CE2#configure terminal | Enter configure mode. |
CE2(config)#bridge 1 protocol ieee vlan-bridge | Set up bridge 1 to use the IEEE VLAN bridge protocol. |
CE2(config)#vlan 2-100 bridge 1 state enable | Configure VLANs from 2-100 and associate them with bridge 1. |
CE2(config)#interface xe24 | Enter interface mode xe24. |
CE2(config-if)#switchport | Configure the interface xe24 as a Layer 2 switch port. |
CE2(config-if)#bridge-group 1 | Associate xe24 to bridge 1. |
CE2(config-if)#switchport mode trunk | Configure xe24 as a trunk port. |
CE2(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk interface xe24. |
CE2(config-if)#exit | Exit interface mode xe24. |
CE2(config)#interface po1 | Enter interface mode and configure LAG interface port-channel 1 (po1). |
CE2(config-if)#switchport | Configures port-channel 1 as a Layer 2 switch port. |
CE2(config-if)#bridge-group 1 | Associate po1 to bridge 1. |
CE2(config-if)#switchport mode trunk | Configure po1 as a trunk port. |
CE2(config-if)#switchport trunk allowed vlan all | Allow all configured VLANs on the trunk port-channel po1. |
CE2(config-if)#exit | Exit interface mode po1. |
CE2(config)#interface xe22 | Enter interface mode xe22. |
CE2(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE2(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE2(config-if)#exit | Exit interface mode xe22. |
CE2(config-if)#interface xe23 | Enter interface mode xe23. |
CE2(config-if)#lacp timeout short | Configure LACP timeout as short. |
CE2(config-if)#channel-group 1 mode active | Add member to the LAG interface. |
CE2(config-if)#commit | Commit the transaction. |
CE2(config-if)#end | Exit interface mode xe23 and configure mode. |
EVPN SR Active-Standby MH Validation
This section provides show outputs validation for port-active mode, covering ELINE and ELAN services with SR as the underlay MPLS path.
The following show output displays the forwarding table entries on PE1, PE2, PE3, and PE4 devices in the network Figure 3-8 using the show mpls forwarding-table command.
PE1#show mpls forwarding-table
Codes: > - installed FTN, * - selected FTN, p - stale FTN, ! - using backup
B - BGP FTN, K - CLI FTN, (t) - tunnel, P - SR Policy FTN, (b) - bypass,
L - LDP FTN, R - RSVP-TE FTN, S - SNMP FTN, I - IGP-Shortcut,
U - unknown FTN, O - SR-OSPF FTN, i - SR-ISIS FTN, k - SR-CLI FTN
(m) - FTN mapped over multipath transport, (e) - FTN is ECMP
FTN-ECMP LDP: Disabled
Code FEC FTN-ID Nhlfe-ID Tunnel-id Pri LSP-Type Out-Label Out-Intf ELC Nexthop
i> 10.10.10.2/32 1 4 0 Yes LSP_DEFAULT 17700 xe2 No 10.1.2.2
i> 10.10.10.2/32 10 23 0 No LSP_DEFAULT 3 xe1 No 10.1.1.2
i(b)> 10.10.10.2/32 6 17 2201 Yes LSP_DEFAULT 17700 xe1 No 10.1.1.2
i> 10.10.10.3/32 2 6 0 Yes LSP_DEFAULT 17400 xe2 No 10.1.2.2
i> 10.10.10.3/32 11 24 0 No LSP_DEFAULT 3 xe1 No 10.1.1.2
i(b)> 10.10.10.3/32 7 19 2202 Yes LSP_DEFAULT 17400 xe1 No 10.1.1.2
i(b)> 10.10.10.3/32 9 22 2204 Yes LSP_DEFAULT 17400 xe2 No 10.1.2.2
i> 10.10.10.4/32 3 8 0 Yes LSP_DEFAULT 17300 xe2 No 10.1.2.2
i> 10.10.10.4/32 12 25 0 No LSP_DEFAULT 3 xe1 No 10.1.1.2
i(b)> 10.10.10.4/32 8 21 2203 Yes LSP_DEFAULT 17300 xe1 No 10.1.1.2
i> 10.10.10.5/32 4 9 0 Yes LSP_DEFAULT 3 xe1 No 10.1.1.2
i> 10.10.10.5/32 13 27 0 No LSP_DEFAULT 17600 xe2 No 10.1.2.2
i> 10.10.10.6/32 5 15 0 Yes LSP_DEFAULT 3 xe2 No 10.1.2.2
i> 10.10.10.6/32 14 29 0 No LSP_DEFAULT 17500 xe1 No 10.1.1.2
PE2#show mpls forwarding-table
Codes: > - installed FTN, * - selected FTN, p - stale FTN, ! - using backup
B - BGP FTN, K - CLI FTN, (t) - tunnel, P - SR Policy FTN, (b) - bypass,
L - LDP FTN, R - RSVP-TE FTN, S - SNMP FTN, I - IGP-Shortcut,
U - unknown FTN, O - SR-OSPF FTN, i - SR-ISIS FTN, k - SR-CLI FTN
(m) - FTN mapped over multipath transport, (e) - FTN is ECMP
FTN-ECMP LDP: Disabled
Code FEC FTN-ID Nhlfe-ID Tunnel-id Pri LSP-Type Out-Label Out-Intf ELC Nexthop
i> 10.10.10.1/32 1 10 0 Yes LSP_DEFAULT 17800 xe4 No 10.1.3.2
i> 10.10.10.1/32 10 27 0 No LSP_DEFAULT 3 xe5 No 10.1.4.2
i(b)> 10.10.10.1/32 6 21 2201 Yes LSP_DEFAULT 17800 xe5 No 10.1.4.2
i> 10.10.10.3/32 2 11 0 Yes LSP_DEFAULT 17400 xe4 No 10.1.3.2
i> 10.10.10.3/32 11 28 0 No LSP_DEFAULT 3 xe5 No 10.1.4.2
i(b)> 10.10.10.3/32 7 23 2202 Yes LSP_DEFAULT 17400 xe5 No 10.1.4.2
i(b)> 10.10.10.3/32 9 26 2204 Yes LSP_DEFAULT 17400 xe4 No 10.1.3.2
i> 10.10.10.4/32 3 12 0 Yes LSP_DEFAULT 17300 xe4 No 10.1.3.2
i> 10.10.10.4/32 12 29 0 No LSP_DEFAULT 3 xe5 No 10.1.4.2
i(b)> 10.10.10.4/32 8 25 2203 Yes LSP_DEFAULT 17300 xe5 No 10.1.4.2
i> 10.10.10.5/32 4 13 0 Yes LSP_DEFAULT 3 xe5 No 10.1.4.2
i> 10.10.10.5/32 13 31 0 No LSP_DEFAULT 17600 xe4 No 10.1.3.2
i> 10.10.10.6/32 5 19 0 Yes LSP_DEFAULT 3 xe4 No 10.1.3.2
i> 10.10.10.6/32 14 33 0 No LSP_DEFAULT 17500 xe5 No 10.1.4.2
PE3#show mpls forwarding-table
Codes: > - installed FTN, * - selected FTN, p - stale FTN, ! - using backup
B - BGP FTN, K - CLI FTN, (t) - tunnel, P - SR Policy FTN, (b) - bypass,
L - LDP FTN, R - RSVP-TE FTN, S - SNMP FTN, I - IGP-Shortcut,
U - unknown FTN, O - SR-OSPF FTN, i - SR-ISIS FTN, k - SR-CLI FTN
(m) - FTN mapped over multipath transport, (e) - FTN is ECMP
FTN-ECMP LDP: Disabled
Code FEC FTN-ID Nhlfe-ID Tunnel-id Pri LSP-Type Out-Label Out-Intf ELC Nexthop
i> 10.10.10.1/32 1 4 0 Yes LSP_DEFAULT 17800 xe5 No 10.1.7.2
i> 10.10.10.1/32 10 23 0 No LSP_DEFAULT 3 xe1 No 10.1.6.2
i(b)> 10.10.10.1/32 6 17 2201 Yes LSP_DEFAULT 17800 xe1 No 10.1.6.2
i(b)> 10.10.10.1/32 9 22 2204 Yes LSP_DEFAULT 17800 xe5 No 10.1.7.2
i> 10.10.10.2/32 2 6 0 Yes LSP_DEFAULT 17700 xe5 No 10.1.7.2
i> 10.10.10.2/32 11 24 0 No LSP_DEFAULT 3 xe1 No 10.1.6.2
i(b)> 10.10.10.2/32 7 19 2202 Yes LSP_DEFAULT 17700 xe1 No 10.1.6.2
i> 10.10.10.4/32 3 8 0 Yes LSP_DEFAULT 17300 xe5 No 10.1.7.2
i> 10.10.10.4/32 12 25 0 No LSP_DEFAULT 3 xe1 No 10.1.6.2
i(b)> 10.10.10.4/32 8 21 2203 Yes LSP_DEFAULT 17300 xe1 No 10.1.6.2
i> 10.10.10.5/32 4 9 0 Yes LSP_DEFAULT 3 xe1 No 10.1.6.2
i> 10.10.10.5/32 13 27 0 No LSP_DEFAULT 17600 xe5 No 10.1.7.2
i> 10.10.10.6/32 5 15 0 Yes LSP_DEFAULT 3 xe5 No 10.1.7.2
i> 10.10.10.6/32 14 29 0 No LSP_DEFAULT 17500 xe1 No 10.1.6.2
PE4#show mpls forwarding-table
Codes: > - installed FTN, * - selected FTN, p - stale FTN, ! - using backup
B - BGP FTN, K - CLI FTN, (t) - tunnel, P - SR Policy FTN, (b) - bypass,
L - LDP FTN, R - RSVP-TE FTN, S - SNMP FTN, I - IGP-Shortcut,
U - unknown FTN, O - SR-OSPF FTN, i - SR-ISIS FTN, k - SR-CLI FTN
(m) - FTN mapped over multipath transport, (e) - FTN is ECMP
FTN-ECMP LDP: Disabled
Code FEC FTN-ID Nhlfe-ID Tunnel-id Pri LSP-Type Out-Label Out-Intf ELC Nexthop
i> 10.10.10.1/32 1 4 0 Yes LSP_DEFAULT 17800 xe0 No 10.1.8.2
i> 10.10.10.1/32 10 23 0 No LSP_DEFAULT 3 xe2 No 10.1.5.2
i(b)> 10.10.10.1/32 6 17 2201 Yes LSP_DEFAULT 17800 xe2 No 10.1.5.2
i> 10.10.10.2/32 2 6 0 Yes LSP_DEFAULT 17700 xe0 No 10.1.8.2
i> 10.10.10.2/32 11 24 0 No LSP_DEFAULT 3 xe2 No 10.1.5.2
i(b)> 10.10.10.2/32 7 19 2202 Yes LSP_DEFAULT 17700 xe2 No 10.1.5.2
i> 10.10.10.3/32 3 8 0 Yes LSP_DEFAULT 17400 xe0 No 10.1.8.2
i> 10.10.10.3/32 12 25 0 No LSP_DEFAULT 3 xe2 No 10.1.5.2
i(b)> 10.10.10.3/32 8 21 2203 Yes LSP_DEFAULT 17400 xe2 No 10.1.5.2
i(b)> 10.10.10.3/32 9 22 2204 Yes LSP_DEFAULT 17400 xe0 No 10.1.8.2
i> 10.10.10.5/32 4 9 0 Yes LSP_DEFAULT 3 xe2 No 10.1.5.2
i> 10.10.10.5/32 13 27 0 No LSP_DEFAULT 17600 xe0 No 10.1.8.2
i> 10.10.10.6/32 5 15 0 Yes LSP_DEFAULT 3 xe0 No 10.1.8.2
i> 10.10.10.6/32 14 29 0 No LSP_DEFAULT 17500 xe2 No 10.1.5.2
The following show output displays the FEC-To-NHLF (FTN) table information on PE1, PE2, PE3, and PE4 devices in the network Figure 3-8 using the show mpls ftn-table command.
PE1#show mpls ftn-table
Primary FTN entry with FEC: 10.10.10.2/32, id: 1, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 7, in intf: - in label: 0 out-segment ix: 12
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 12, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17700
Nexthop addr: 10.1.2.2 cross connect ix: 7, op code: Push
Non-primary FTN entry with FEC: 10.10.10.2/32, id: 10, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.1.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 6
Primary FTN entry with FEC: 10.10.10.2/32, id: 6, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2201, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 5, in intf: - in label: 0 out-segment ix: 16
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 16, owner: ISIS-SR, Stale: NO, out intf: xe1, out label: 17700
Nexthop addr: 10.1.1.2 cross connect ix: 5, op code: Push
Primary FTN entry with FEC: 10.10.10.3/32, id: 2, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 3, in intf: - in label: 0 out-segment ix: 13
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 13, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17400
Nexthop addr: 10.1.2.2 cross connect ix: 3, op code: Push
Non-primary FTN entry with FEC: 10.10.10.3/32, id: 11, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.1.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 7
Primary FTN entry with FEC: 10.10.10.3/32, id: 7, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2202, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 8, in intf: - in label: 0 out-segment ix: 18
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 18, owner: ISIS-SR, Stale: NO, out intf: xe1, out label: 17400
Nexthop addr: 10.1.1.2 cross connect ix: 8, op code: Push
Primary FTN entry with FEC: 10.10.10.3/32, id: 9, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2204, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 3, in intf: - in label: 0 out-segment ix: 13
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 13, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17400
Nexthop addr: 10.1.2.2 cross connect ix: 3, op code: Push
Primary FTN entry with FEC: 10.10.10.4/32, id: 3, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 4, in intf: - in label: 0 out-segment ix: 14
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 14, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17300
Nexthop addr: 10.1.2.2 cross connect ix: 4, op code: Push
Non-primary FTN entry with FEC: 10.10.10.4/32, id: 12, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.1.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 8
Primary FTN entry with FEC: 10.10.10.4/32, id: 8, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2203, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 9, in intf: - in label: 0 out-segment ix: 20
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 20, owner: ISIS-SR, Stale: NO, out intf: xe1, out label: 17300
Nexthop addr: 10.1.1.2 cross connect ix: 9, op code: Push
Primary FTN entry with FEC: 10.10.10.5/32, id: 4, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.1.2 cross connect ix: 2, op code: Push
Non-primary FTN entry with FEC: 10.10.10.5/32, id: 13, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 10, in intf: - in label: 0 out-segment ix: 26
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 26, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe2, transport out intf: N/A, out label: 17600
Nexthop addr: 10.1.2.2 cross connect ix: 10, op code: Push and Lookup
bypass_ftn_ix 9
Primary FTN entry with FEC: 10.10.10.6/32, id: 5, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 6, in intf: - in label: 0 out-segment ix: 11
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 11, owner: N/A, Stale: NO, out intf: xe2, out label: 3
Nexthop addr: 10.1.2.2 cross connect ix: 6, op code: Push
Non-primary FTN entry with FEC: 10.10.10.6/32, id: 14, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 11, in intf: - in label: 0 out-segment ix: 28
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 28, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe1, transport out intf: N/A, out label: 17500
Nexthop addr: 10.1.1.2 cross connect ix: 11, op code: Push and Lookup
bypass_ftn_ix 7
PE2#show mpls ftn-table
Primary FTN entry with FEC: 10.10.10.1/32, id: 1, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 7, in intf: - in label: 0 out-segment ix: 16
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 16, owner: ISIS-SR, Stale: NO, out intf: xe4, out label: 17800
Nexthop addr: 10.1.3.2 cross connect ix: 7, op code: Push
Non-primary FTN entry with FEC: 10.10.10.1/32, id: 10, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe5, out label: 3
Nexthop addr: 10.1.4.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 6
Primary FTN entry with FEC: 10.10.10.1/32, id: 6, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2201, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 5, in intf: - in label: 0 out-segment ix: 20
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 20, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17800
Nexthop addr: 10.1.4.2 cross connect ix: 5, op code: Push
Primary FTN entry with FEC: 10.10.10.3/32, id: 2, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 3, in intf: - in label: 0 out-segment ix: 17
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 17, owner: ISIS-SR, Stale: NO, out intf: xe4, out label: 17400
Nexthop addr: 10.1.3.2 cross connect ix: 3, op code: Push
Non-primary FTN entry with FEC: 10.10.10.3/32, id: 11, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe5, out label: 3
Nexthop addr: 10.1.4.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 7
Primary FTN entry with FEC: 10.10.10.3/32, id: 7, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2202, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 8, in intf: - in label: 0 out-segment ix: 22
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 22, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17400
Nexthop addr: 10.1.4.2 cross connect ix: 8, op code: Push
Primary FTN entry with FEC: 10.10.10.3/32, id: 9, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2204, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 3, in intf: - in label: 0 out-segment ix: 17
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 17, owner: ISIS-SR, Stale: NO, out intf: xe4, out label: 17400
Nexthop addr: 10.1.3.2 cross connect ix: 3, op code: Push
Primary FTN entry with FEC: 10.10.10.4/32, id: 3, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 4, in intf: - in label: 0 out-segment ix: 18
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 18, owner: ISIS-SR, Stale: NO, out intf: xe4, out label: 17300
Nexthop addr: 10.1.3.2 cross connect ix: 4, op code: Push
Non-primary FTN entry with FEC: 10.10.10.4/32, id: 12, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe5, out label: 3
Nexthop addr: 10.1.4.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 8
Primary FTN entry with FEC: 10.10.10.4/32, id: 8, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2203, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 9, in intf: - in label: 0 out-segment ix: 24
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 24, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17300
Nexthop addr: 10.1.4.2 cross connect ix: 9, op code: Push
Primary FTN entry with FEC: 10.10.10.5/32, id: 4, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe5, out label: 3
Nexthop addr: 10.1.4.2 cross connect ix: 2, op code: Push
Non-primary FTN entry with FEC: 10.10.10.5/32, id: 13, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 10, in intf: - in label: 0 out-segment ix: 30
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 30, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe4, transport out intf: N/A, out label: 17600
Nexthop addr: 10.1.3.2 cross connect ix: 10, op code: Push and Lookup
bypass_ftn_ix 9
Primary FTN entry with FEC: 10.10.10.6/32, id: 5, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 6, in intf: - in label: 0 out-segment ix: 15
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 15, owner: N/A, Stale: NO, out intf: xe4, out label: 3
Nexthop addr: 10.1.3.2 cross connect ix: 6, op code: Push
Non-primary FTN entry with FEC: 10.10.10.6/32, id: 14, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 11, in intf: - in label: 0 out-segment ix: 32
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 32, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe5, transport out intf: N/A, out label: 17500
Nexthop addr: 10.1.4.2 cross connect ix: 11, op code: Push and Lookup
bypass_ftn_ix 7
PE3#show mpls ftn-table
Primary FTN entry with FEC: 10.10.10.1/32, id: 1, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 7, in intf: - in label: 0 out-segment ix: 12
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 12, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17800
Nexthop addr: 10.1.7.2 cross connect ix: 7, op code: Push
Non-primary FTN entry with FEC: 10.10.10.1/32, id: 10, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.6.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 6
Primary FTN entry with FEC: 10.10.10.1/32, id: 6, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2201, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 5, in intf: - in label: 0 out-segment ix: 16
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 16, owner: ISIS-SR, Stale: NO, out intf: xe1, out label: 17800
Nexthop addr: 10.1.6.2 cross connect ix: 5, op code: Push
Primary FTN entry with FEC: 10.10.10.1/32, id: 9, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2204, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 7, in intf: - in label: 0 out-segment ix: 12
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 12, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17800
Nexthop addr: 10.1.7.2 cross connect ix: 7, op code: Push
Primary FTN entry with FEC: 10.10.10.2/32, id: 2, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 3, in intf: - in label: 0 out-segment ix: 13
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 13, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17700
Nexthop addr: 10.1.7.2 cross connect ix: 3, op code: Push
Non-primary FTN entry with FEC: 10.10.10.2/32, id: 11, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.6.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 7
Primary FTN entry with FEC: 10.10.10.2/32, id: 7, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2202, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 8, in intf: - in label: 0 out-segment ix: 18
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 18, owner: ISIS-SR, Stale: NO, out intf: xe1, out label: 17700
Nexthop addr: 10.1.6.2 cross connect ix: 8, op code: Push
Primary FTN entry with FEC: 10.10.10.4/32, id: 3, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 4, in intf: - in label: 0 out-segment ix: 14
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 14, owner: ISIS-SR, Stale: NO, out intf: xe5, out label: 17300
Nexthop addr: 10.1.7.2 cross connect ix: 4, op code: Push
Non-primary FTN entry with FEC: 10.10.10.4/32, id: 12, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.6.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 8
Primary FTN entry with FEC: 10.10.10.4/32, id: 8, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2203, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 9, in intf: - in label: 0 out-segment ix: 20
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 20, owner: ISIS-SR, Stale: NO, out intf: xe1, out label: 17300
Nexthop addr: 10.1.6.2 cross connect ix: 9, op code: Push
Primary FTN entry with FEC: 10.10.10.5/32, id: 4, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe1, out label: 3
Nexthop addr: 10.1.6.2 cross connect ix: 2, op code: Push
Non-primary FTN entry with FEC: 10.10.10.5/32, id: 13, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 10, in intf: - in label: 0 out-segment ix: 26
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 26, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe5, transport out intf: N/A, out label: 17600
Nexthop addr: 10.1.7.2 cross connect ix: 10, op code: Push and Lookup
bypass_ftn_ix 9
Primary FTN entry with FEC: 10.10.10.6/32, id: 5, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 6, in intf: - in label: 0 out-segment ix: 11
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 11, owner: N/A, Stale: NO, out intf: xe5, out label: 3
Nexthop addr: 10.1.7.2 cross connect ix: 6, op code: Push
Non-primary FTN entry with FEC: 10.10.10.6/32, id: 14, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 11, in intf: - in label: 0 out-segment ix: 28
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 28, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe1, transport out intf: N/A, out label: 17500
Nexthop addr: 10.1.6.2 cross connect ix: 11, op code: Push and Lookup
bypass_ftn_ix 7
PE4#show mpls ftn-table
Primary FTN entry with FEC: 10.10.10.1/32, id: 1, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 7, in intf: - in label: 0 out-segment ix: 12
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 12, owner: ISIS-SR, Stale: NO, out intf: xe0, out label: 17800
Nexthop addr: 10.1.8.2 cross connect ix: 7, op code: Push
Non-primary FTN entry with FEC: 10.10.10.1/32, id: 10, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe2, out label: 3
Nexthop addr: 10.1.5.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 6
Primary FTN entry with FEC: 10.10.10.1/32, id: 6, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2201, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 5, in intf: - in label: 0 out-segment ix: 16
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 16, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17800
Nexthop addr: 10.1.5.2 cross connect ix: 5, op code: Push
Primary FTN entry with FEC: 10.10.10.2/32, id: 2, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 3, in intf: - in label: 0 out-segment ix: 13
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 13, owner: ISIS-SR, Stale: NO, out intf: xe0, out label: 17700
Nexthop addr: 10.1.8.2 cross connect ix: 3, op code: Push
Non-primary FTN entry with FEC: 10.10.10.2/32, id: 11, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe2, out label: 3
Nexthop addr: 10.1.5.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 7
Primary FTN entry with FEC: 10.10.10.2/32, id: 7, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2202, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 8, in intf: - in label: 0 out-segment ix: 18
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 18, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17700
Nexthop addr: 10.1.5.2 cross connect ix: 8, op code: Push
Primary FTN entry with FEC: 10.10.10.3/32, id: 3, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 4, in intf: - in label: 0 out-segment ix: 14
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 14, owner: ISIS-SR, Stale: NO, out intf: xe0, out label: 17400
Nexthop addr: 10.1.8.2 cross connect ix: 4, op code: Push
Non-primary FTN entry with FEC: 10.10.10.3/32, id: 12, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe2, out label: 3
Nexthop addr: 10.1.5.2 cross connect ix: 2, op code: Push
bypass_ftn_ix 8
Primary FTN entry with FEC: 10.10.10.3/32, id: 8, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2203, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 9, in intf: - in label: 0 out-segment ix: 20
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 20, owner: ISIS-SR, Stale: NO, out intf: xe2, out label: 17400
Nexthop addr: 10.1.5.2 cross connect ix: 9, op code: Push
Primary FTN entry with FEC: 10.10.10.3/32, id: 9, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 2204, Protected LSP id: 0, LSP-type: Bypass, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 4, in intf: - in label: 0 out-segment ix: 14
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 14, owner: ISIS-SR, Stale: NO, out intf: xe0, out label: 17400
Nexthop addr: 10.1.8.2 cross connect ix: 4, op code: Push
Primary FTN entry with FEC: 10.10.10.5/32, id: 4, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 2, in intf: - in label: 0 out-segment ix: 2
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 2, owner: N/A, Stale: NO, out intf: xe2, out label: 3
Nexthop addr: 10.1.5.2 cross connect ix: 2, op code: Push
Non-primary FTN entry with FEC: 10.10.10.5/32, id: 13, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 10, in intf: - in label: 0 out-segment ix: 26
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 26, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe0, transport out intf: N/A, out label: 17600
Nexthop addr: 10.1.8.2 cross connect ix: 10, op code: Push and Lookup
bypass_ftn_ix 9
Primary FTN entry with FEC: 10.10.10.6/32, id: 5, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to LSP, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Primary, Description: N/A, , Color: 0
Cross connect ix: 6, in intf: - in label: 0 out-segment ix: 11
Owner: N/A, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 11, owner: N/A, Stale: NO, out intf: xe0, out label: 3
Nexthop addr: 10.1.8.2 cross connect ix: 6, op code: Push
Non-primary FTN entry with FEC: 10.10.10.6/32, id: 14, row status: Active, Tunnel-Policy: N/A, State: Installed
Owner: ISIS-SR, distance: 115, Action-type: Redirect to Tunnel, Exp-bits: 0x0, Incoming DSCP: none
Tunnel id: 0, Protected LSP id: 0, LSP-type: Backup, QoS Resource id: 0, Description: N/A, , Color: 0
Cross connect ix: 11, in intf: - in label: 0 out-segment ix: 28
Owner: ISIS-SR, Persistent: No, Admin Status: Up, Oper Status: Up
Out-segment with ix: 28, owner: ISIS-SR, Stale: NO, ISIS-SR out intf: xe2, transport out intf: N/A, out label: 17500
Nexthop addr: 10.1.5.2 cross connect ix: 11, op code: Push and Lookup
bypass_ftn_ix 8
Port-Active
The following show output displays the Ethernet Segment (ES) and Intermediate System (IS) neighbor adjacencies for PE1, PE2, PE3, PE4, P1, and P2 devices in the network Figure 3-8 using the show clns neighbors command.
PE1#show clns neighbors
Total number of L1 adjacencies: 2
Total number of L2 adjacencies: 2
Total number of adjacencies: 4
Tag 1: VRF : default
System Id Interface SNPA State Holdtime Type Protocol
P2 xe2 e8c5.7a55.3c7e Up 22 L1 IS-IS
Up 22 L2 IS-IS
P1 xe1 e49d.73b3.c107 Up 23 L1 IS-IS
PE2#show clns neighbors
Total number of L1 adjacencies: 2
Total number of L2 adjacencies: 2
Total number of adjacencies: 4
Tag 1: VRF : default
System Id Interface SNPA State Holdtime Type Protocol
P2 xe4 e8c5.7a55.3c7f Up 8 L1 IS-IS
Up 8 L2 IS-IS
P1 xe5 e49d.73b3.c14c Up 29 L1 IS-IS
Up 29 L2 IS-IS
Up 23 L2 IS-IS
P1#show clns neighbors
Total number of L1 adjacencies: 4
Total number of L2 adjacencies: 4
Total number of adjacencies: 8
Tag 1: VRF : default
System Id Interface SNPA State Holdtime Type Protocol
PE3 xe4 b86a.97d9.2cdf Up 19 L1 IS-IS
Up 19 L2 IS-IS
PE2 xe2 e8c5.7a47.9dfc Up 7 L1 IS-IS
Up 7 L2 IS-IS
PE1 xe1 e8c5.7a78.c918 Up 7 L1 IS-IS
Up 7 L2 IS-IS
PE4 xe3 d077.ceda.7004 Up 19 L1 IS-IS
Up 19 L2 IS-IS
P2#show clns neighbors
Total number of L1 adjacencies: 4
Total number of L2 adjacencies: 4
Total number of adjacencies: 8
Tag 1: VRF : default
System Id Interface SNPA State Holdtime Type Protocol
PE3 xe11 b86a.97d9.2ccb Up 19 L1 IS-IS
Up 19 L2 IS-IS
PE1 xe12 e8c5.7a78.c908 Up 7 L1 IS-IS
Up 7 L2 IS-IS
PE2 xe13 e8c5.7a47.9dfb Up 19 L1 IS-IS
Up 19 L2 IS-IS
PE4 xe14 d077.ceda.7002 Up 19 L1 IS-IS
Up 19 L2 IS-IS
PE3#show clns neighbors
Total number of L1 adjacencies: 2
Total number of L2 adjacencies: 2
Total number of adjacencies: 4
Tag 1: VRF : default
System Id Interface SNPA State Holdtime Type Protocol
P2 xe5 e8c5.7a55.3c77 Up 7 L1 IS-IS
Up 7 L2 IS-IS
P1 xe1 e49d.73b3.c105 Up 5 L1 IS-IS
Up 5 L2 IS-IS
PE4#show clns neighbors
Total number of L1 adjacencies: 2
Total number of L2 adjacencies: 2
Total number of adjacencies: 4
Tag 1: VRF : default
System Id Interface SNPA State Holdtime Type Protocol
P2 xe0 e8c5.7a55.3c80 Up 5 L1 IS-IS
Up 5 L2 IS-IS
P1 xe2 e49d.73b3.c14d Up 6 L1 IS-IS
Up 6 L2 IS-IS
Port-Active ELAN
The following show outputs provide validation for ELAN configurations.
The following show output displays the EVPN active multi-homed and load-balanced details on PE1, PE2, PE3, and PE4 devices in the network Figure 3-8 using the show evpn load-balance port-active and show evpn multi-homing all commands.
PE1#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:00:00:11:11:77:77:00:00:00 LOCAL 10.10.10.1 port-active auto 0 NO NA STANDBY
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.2 port-active auto 0 NO NA ACTIVE
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.3 port-active ---- ---- ---- ---- STANDBY
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.4 port-active ---- ---- ---- ---- ACTIVE
PE2#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.1 port-active auto 0 NO NA STANDBY
00:00:00:11:11:77:77:00:00:00 LOCAL 10.10.10.2 port-active auto 0 NO NA ACTIVE
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.3 port-active ---- ---- ---- ---- STANDBY
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.4 port-active ---- ---- ---- ---- ACTIVE
PE3#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.1 port-active ---- ---- ---- ---- STANDBY
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.2 port-active ---- ---- ---- ---- ACTIVE
00:00:00:22:22:77:77:00:00:00 LOCAL 10.10.10.3 port-active auto 0 NO NA STANDBY
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.4 port-active auto 0 NO NA ACTIVE
PE4#show evpn load-balance port-active
ESI AC-IF/PE PE-IP-ADDRESS Redundancy Service-carving weight Revertive AC-DF Status
=====================================================================================================================================
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.1 port-active ---- ---- ---- ---- STANDBY
00:00:00:11:11:77:77:00:00:00 REMOTE 10.10.10.2 port-active ---- ---- ---- ---- ACTIVE
00:00:00:22:22:77:77:00:00:00 REMOTE 10.10.10.3 port-active auto 0 NO NA STANDBY
00:00:00:22:22:77:77:00:00:00 LOCAL 10.10.10.4 port-active auto 0 NO NA ACTIVE
PE1#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 po1 10.10.10.1
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.2
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.3
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.4
Total number of entries are 4
PE2#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.1
00:00:00:11:11:77:77:00:00:00 po1 10.10.10.2
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.3
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.4
Total number of entries are 4
PE3#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.1
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.2
00:00:00:22:22:77:77:00:00:00 po1 10.10.10.3
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.4
Total number of entries are 4
PE4#show evpn multi-homing all
ESI Access-IF PE-IP-ADDRESS
===========================================================
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.1
00:00:00:11:11:77:77:00:00:00 ---- 10.10.10.2
00:00:00:22:22:77:77:00:00:00 ---- 10.10.10.3
00:00:00:22:22:77:77:00:00:00 po1 10.10.10.4
Total number of entries are 4
The following show output displays the active EVPN MPLS Tunnels for ELAN on PE1, PE2, PE3, and PE4 devices in the network Figure 3-7 using the show evpn mpls tunnel command.
PE1#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.1 10.10.10.2 Installed 00:02:19 00:02:19 3000
10.10.10.1 10.10.10.4 Installed 00:10:21 00:10:21 3000
10.10.10.1 10.10.10.3 Installed 00:10:47 00:10:47 3000
Total number of entries are 3
PE2#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.2 10.10.10.1 Installed 00:02:01 00:02:01 3000
10.10.10.2 10.10.10.4 Installed 00:02:01 00:02:01 3000
10.10.10.2 10.10.10.3 Installed 00:02:01 00:02:01 3000
Total number of entries are 3
PE3#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn-id
===================================================================================
10.10.10.3 10.10.10.2 Installed 00:02:27 00:02:27 3000
10.10.10.3 10.10.10.4 Installed 00:10:29 00:10:29 3000
10.10.10.3 10.10.10.1 Installed 00:10:54 00:10:54 3000
Total number of entries are 3
PE4#show evpn mpls tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update evpn
-id
================================================================================
===
10.10.10.4 10.10.10.2 Installed 00:02:30 00:02:30 3000
10.10.10.4 10.10.10.3 Installed 00:10:32 00:10:32 3000
10.10.10.4 10.10.10.1 Installed 00:10:32 00:10:32 3000
Total number of entries are 3
Port-Active ELINE
The following show output displays the active EVPN SR Tunnels for ELINE on PE1, PE2, PE3, and PE4 devices in the network Figure 3-8 using the show evpn mpls xconnect tunnel command.
PE1#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.1 10.10.10.4 AC-Down 01:07:01 01:07:01 1800 1700
10.10.10.1 10.10.10.3 AC-Down 01:07:01 01:07:01 1800 1700
Total number of entries are 2
PE2#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.2 10.10.10.3 Installed 00:08:20 00:07:31 1800 1700
10.10.10.2 10.10.10.4 Installed 00:08:20 00:07:31 1800 1700
Total number of entries are 2
PE3#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.3 10.10.10.1 AC-Down 01:04:48 01:04:48 1700 1800
10.10.10.3 10.10.10.2 AC-Down 00:08:48 00:08:48 1700 1800
Total number of entries are 2
PE4#show evpn mpls xconnect tunnel
EVPN-MPLS Network tunnel Entries
Source Destination Status Up/Down Update local-evpn-id remote-evpn-id
========================================================================================================
10.10.10.4 10.10.10.1 Installed 00:09:00 00:08:28 1700 1800
10.10.10.4 10.10.10.2 Installed 00:09:01 00:08:28 1700 1800
Total number of entries are 2
Implementation Examples
Scenario: Customer wants to achieve redundancy for its hosts in a network using Single-Active or Port-Active redundancy.
• Customer configures the evpn multi-homed command with the load-balancing single-active or load-balancing port-active option on the relevant PE interfaces.
• Single-Active or Port-Active redundancy is now in effect, ensuring redundancy for hosts.
• The feature works in conjunction with other EVPN-related configurations, such as VRF, VLAN mapping, and other EVPN settings.
New CLI Commands
The EVPN Active-Standby feature introduces the following configuration commands. For more information of the EVPN MPLS commands, see the EVPN MPLS Commands chapter in the Multi-Protocol Label Switching Guide.
service-carving ac-driven
Use this command to enable the AC-influenced method for any selected Designated Forwarder (DF) algorithm.
Enabling the ac-driven method allows the Designated Forwarder (DF) algorithm to be influenced by the Attachment Circuits (AC’s) associated with a specific Ethernet Segment (ES). This means that the DF selection is based on the AC’s characteristics and conditions, such as whether an AC is operational UP, mapped, or unmapped on the ESI.
Use no form of this command to disable the AC-influenced method for any selected Designated Forwarder (DF) algorithm.
Command Syntax
service-carving ac-driven
no service-carving ac-driven
Parameters
None
Default
ac-driven is disabled.
Command Mode
EVPN Ethernet Segment (ES) Mode
Applicability
This command was introduced in the OcNOS version 6.4.2.
Example
The provided examples showcase the configuration of the service-carving ac-driven command in EVPN Ethernet Segment (ES) mode. The first two examples demonstrate enabling this feature with different DF election methods, and the final example illustrates the command to disable service-carving ac-driven.
OcNOS#configure terminal
OcNOS(config)#interface sa1
OcNOS(config-if)#evpn multi-homed esi 11:22:33:44:55:66:77:88:99 load-balancing single-active
OcNOS(config-if-es)#service-carving preference-based
OcNOS(config-if-es)#service-carving ac-driven
OcNOS(config-if-es)#end
OcNOS#configure terminal
OcNOS(config)#interface sa1
OcNOS(config-if)#evpn multi-homed esi 11:22:33:44:55:66:77:88:99 load-balancing single-active
OcNOS(config-if-es)#service-carving auto
OcNOS(config-if-es)#service-carving ac-driven
OcNOS(config-if-es)#no service-carving ac-driven
OcNOS(config-if-es)#end
service-carving
Use this command to provide the flexibility to select the Designated Forwarder (DF) election algorithm based on preference based or modulo-based DF election.
Use no form of this command to disable service-carving.
Command Syntax
service-carving (preference-based|auto)
no service-carving
Parameters
preference-based
Select the DF election algorithm based on preference based.
auto
Select the DF election algorithm based on modulo based.
Default
None
Command Mode
EVPN ES Mode
Applicability
This command was introduced in the OcNOS version 6.4.1.
Example
The following examples demonstrate the configuration of the service-carving command in both single-active or port-active mode for the EVPN multi-homed system, with one utilizing auto service carving and the other using preference-based service carving.
OcNOS#configure terminal
OcNOS(config)#interface sa1
OcNOS(config-if)#evpn multi-homed esi 11:22:33:44:55:66:77:88:99 load-balancing single-active
OcNOS(config-if-es)#service-carving auto
OcNOS(config-if-es)#end
OcNOS#configure terminal
OcNOS(config)#interface po1
OcNOS(config-if)#evpn multi-homed system-mac 0000.0000.0011 load-balancing port-active
OcNOS(config-if-es)#service-carving auto
OcNOS(config-if-es)#end
OcNOS#configure terminal
OcNOS(config)#interface po1
OcNOS(config-if)#evpn multi-homed system-mac 0000.0000.0011 load-balancing port-active
OcNOS(config-if-es)#service-carving preference-based
OcNOS(config-if-es)#end
The following example is used to disable the service-carving for the EVPN multi-homed system.
OcNOS(config-if-es)#no service-carving
OcNOS(config-if-es)#end
service-carving weight
Use this command to specify a preference value when the preference-based Designated Forwarder (DF) election algorithm is selected. This preference value determines the priority of the local PE device to become the DF for a particular Ethernet segment.
Use no form of this command to replace the preference weight value and choose the default preference value.
Command Syntax
service-carving weight <1-65535>
no service-carving weight
Parameters
weight <1-65535>
Specifies the preference weight value. A lower weight value indicates a higher priority for becoming the DF.
Default
The service-carving weight command is set to 32767 by default.
Command Mode
EVPN Ethernet Segment (ES) Mode
Applicability
This command was introduced in the OcNOS version 6.4.1.
Example
The service-carving weight command is used to configure the preference weight value for service-carving in both port-active and single-active modes.
OcNOS#configure terminal
OcNOS(config)#interface po1
OcNOS(config-if)#evpn multi-homed system-mac 0000.0000.0011 load-balancing port-active
OcNOS(config-if-es)#service-carving preference-based
OcNOS(config-if-es)#service-carving weight 100
OcNOS(config-if-es)#end
OcNOS#configure terminal
OcNOS(config)#interface sa1
OcNOS(config-if)#evpn multi-homed esi 11:22:33:44:55:66:77:88:99 load-balancing single-active
OcNOS(config-if-es)#service-carving preference-based
OcNOS(config-if-es)#service-carving weight 100
To disable the configured weight, use the no service-carving weight command.
OcNOS(config-if-es)#no service-carving weight
OcNOS(config-if-es)#end
Revised CLI Commands
Below is the revised command for configuring EVPN Active-Standby.
evpn multi-homed
• The command evpn multi-homed allows users to configure single-active and port-active load-balancing Ethernet Segment Identifier (ESI) on a link with a multihomed Customer Edge (CE) in the context of EVPN multi-homed configurations. For more details, refer to the evpn multi-homed command in the EVPN MPLS Commands chapter in the Multi-Protocol Label Switching Guide.
• The existing syntax now includes the newly added parameter for load-balancing, namely single-active and port-active.
Troubleshooting
To ensure the reliable operation of the single-active or port-active setup and maintain data accuracy and consistency, follow these troubleshooting steps:
1. Verify the Configuration:
• Use the show running-config command to confirm that the ESI configuration includes load-balancing single-active or port-active, such as:
evpn multi-homed esi 11:22:33:44:55:66:77:88:99 load-balancing single-active
or
evpn multi-homed system-mac 0000.4321.1234 load-balancing port-active
• Ensure that the service-carving algorithm type is configured.
2. Verify the show command:
• Use the show bgp l2vpn evpn multihoming es-route command to confirm that it matches the service-carving algorithm type.
• Use the show evpn load-balance single-active or port-active command to verify the status of the Multihomed (MH) nodes as ACTIVE and STANDBY.
3. Ensure Proper Connectivity: Validate the connectivity between the router and the EVPN tunnel to ensure it is up. This involves verifying network settings, ports, and firewalls.
4. For the server: Enable debugging on OcNOS and enable debug mode. Verify the logs in /var/log/messages for further insights.
Abbreviations
The following are some key abbreviations and their meanings relevant to this document:
Acronym | Description |
EVPN | Ethernet Virtual Private Network |
ELINE | Ethernet Line services |
ELAN | Ethernet LAN services |
LAN | Local Area Network |
CE | Customer Edge |
PE | Provider Edge |
MH | Multihoming |
AC | Attachment Circuit |
LACP | Link Aggregation Control Protocol |
BUM | Broadcast, Unknown Unicast, Multicast |
MAC | Media Access Control |
ARP/ND | Address Resolution Protocol/Neighbor Discovery |
DF | Designated Forwarder |
Glossary
The following provides definitions for key terms used throughout this document.
Ethernet Virtual Private Network (EVPN) | A network technology that extends Layer 2 Ethernet services over a Layer 3 IP/MPLS network. |
Ethernet Line services (ELINE) | Two PEs are directly connected over an Ethernet link, enabling redundancy and efficient data exchange. |
Ethernet LAN services (ELAN) | A group of PEs are interconnected in a multipoint Ethernet network, providing redundancy and optimized data transfer. |
Port-Active | A redundancy mechanism in which multiple Provider Edge (PE) devices can be active simultaneously for the same host or MAC address, with specific active ports associated with each active PE. |
Single-Active | A redundancy mechanism in which only one of the Provider Edge (PE) devices is active at a time for handling traffic for a specific host or MAC address. |
Customer Edge (CE) | A device at the customer's network edge that connects to the service provider's network. |
Provider Edge (PE) | A device at the service provider's network edge that connects to customer edge devices. |
Multihoming (MH) | Connecting a host or CE device to multiple PE devices for redundancy and load balancing. |
Attachment Circuit (AC) | The connection between a CE device and a PE device in an EVPN network. |
Link Aggregation Control Protocol (LACP) | A protocol used to manage and bundle multiple physical links into a single logical link for higher bandwidth and redundancy. |
Broadcast, Unknown Unicast, Multicast (BUM) | Categories of network traffic that includes broadcast, unknown unicast, and multicast packets. |
Media Access Control (MAC) | A unique identifier assigned to network interfaces, typically associated with a hardware address. |
Address Resolution Protocol/Neighbor Discovery (ARP/ND) | Protocols used to map IP addresses to MAC addresses in a local network. |
Designated Forwarder (DF) | A PE device selected to forward broadcast, unknown unicast, and multicast traffic within an Ethernet segment. |
Redundancy | The provision of duplicate equipment or links to ensure network availability in case of failures. |
Failover | The process of switching to a backup device or link in case of a primary device or link failure. |
Resiliency | The ability of a network to maintain its functionality even in the face of failures or disruptions. |
Unicast | Communication between a single sender and a single receiver in a network. |
Multicast | Communication from a single sender to multiple receivers in a network. |
Egress | The process of traffic leaving a device or network segment. |
Standby | In redundancy, a secondary device or link that is ready to take over in case the primary device or link fails. |
Active | In redundancy, the primary device or link that is currently handling traffic. |
Forwarding | The process of transmitting network packets from one device to another. |
Link State | The operational status of a network link, indicating whether it is up or down. |
Virtual Routing and Forwarding (VRF) | A technology that enables multiple instances of a routing table to coexist within a router. |
Virtual Local Area Network (VLAN) | A logical network segment within a physical network. |
Data Exchange | The process of sending and receiving data between network devices. |
Downtime | The period during which a network or service is not available due to maintenance or failures. |