The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Configuring EoMPLS
EoMPLS is one of the AToM transport types. EoMPLS works by encapsulating Ethernet PDUs in MPLS packets and forwarding them across the MPLS network. Each PDU is transported as a single packet.
Cisco IOS XE Everest 16.6.1 supports only the following mode:
Port mode—Allows all traffic on a port to share a single VC across an MPLS network. Port mode uses VC type 5.
Catalyst Platform: |
Cat3650 |
Cat3850 |
Cat9300 |
Cat9400 |
Cat9500 |
Supported number of VCs: |
256 |
256 |
256 |
1000 |
1000 |
Before you configure EoMPLS, ensure that the network is configured as follows:
Configure IP routing in the core so that the PE routers can reach each other through IP.
Configure MPLS in the core so that a label switched path (LSP) exists between the PE routers.
Configure no switchport, no keepalive and no ip address before configuring xconnect on the attachment circuit.
For load-balancing, port-channel load-balance command is mandatory to be configured.
VLAN mode is not supported. Ethernet Flow Point is not supported.
Port-channel as attachment circuit is not supported
QoS : Customer DSCP Re-marking is not supported with VPWS and EoMPLS.
VCCV Ping with explicit null is not supported.
L2 VPN Interworking is not supported.
L2 Protocol Tunneling CLI is not supported.
Untagged, tagged and 802.1Q in 802.1Q are supported as incoming traffic.
Flow Aware Transport Pseudowire Redundancy (FAT PW) is supported only in Protocol-CLI mode. Supported load balancing parameters are Source IP, Source MAC address, Destination IP and Destination MAC address.
Enabling or disabling Control word is supported.
MPLS QoS is supported in Pipe and Uniform Mode. Default mode is Pipe Mode.
Both – the legacy xconnect and Protocol-CLI (interface pseudowire configuration) modes are supported.
By default, EoMPLS PW tunnels all protocols like CDP, STP. EoMPLS PW cannot perform selective protocol tunneling as part of L2 Protocol Tunneling CLI.
To configure port-mode EoMPLS in xconnect mode, perform the following task :
To configure port-mode EoMPLS in protocol-CLI mode, perform the following task :
PE Configuration |
CE Configuration |
---|---|
mpls ip mpls label protocol ldp mpls ldp graceful-restart mpls ldp router-id loopback 1 force interface Loopback1 ip address 1.1.1.1 255.255.255.255 ip ospf 100 area 0 router ospf 100 router-id 1.1.1.1 nsf system mtu 9198 port-channel load-balance dst-ip ! interface GigabitEthernet2/0/39 no switchport no ip address no keepalive ! interface pseudowire101 encapsulation mpls neighbor 4.4.4.4 101 load-balance flow ip dst-ip load-balance flow-label both l2vpn xconnect context pw101 member pseudowire101 member GigabitEthernet2/0/39 ! interface TenGigabitEthernet3/0/10 switchport trunk allowed vlan 142 switchport mode trunk channel-group 42 mode active ! interface Port-channel42 switchport trunk allowed vlan 142 switchport mode trunk ! interface Vlan142 ip address 142.1.1.1 255.255.255.0 ip ospf 100 area 0 mpls ip mpls label protocol ldp ! |
interface GigabitEthernet1/0/33 switchport trunk allowed vlan 912 switchport mode trunk spanning-tree portfast trunk ! interface Vlan912 ip address 10.91.2.3 255.255.255.0 ! |
Local interface: Gi1/0/1 up, line protocol up, Ethernet up Destination address: 1.1.1.1, VC ID: 101, VC status: up Output interface: Vl182, imposed label stack {17 16} Preferred path: not configured Default path: active Next hop: 182.1.1.1 Load Balance: ECMP flow classification: ip dst-ip Create time: 06:22:11, last status change time: 05:58:42 Last label FSM state change time: 05:58:42 Signaling protocol: LDP, peer 1.1.1.1:0 up Targeted Hello: 4.4.4.4(LDP Id) -> 1.1.1.1, LDP is UP Graceful restart: not configured and not enabled Non stop routing: not configured and not enabled Status TLV support (local/remote) : enabled/supported LDP route watch : enabled Label/status state machine : established, LruRru Last local dataplane status rcvd: No fault Last BFD dataplane status rcvd: Not sent Last BFD peer monitor status rcvd: No fault Last local AC circuit status rcvd: No fault Last local AC circuit status sent: No fault Last local PW i/f circ status rcvd: No fault Last local LDP TLV status sent: No fault Last remote LDP TLV status rcvd: No fault Last remote LDP ADJ status rcvd: No fault MPLS VC labels: local 512, remote 16 Group ID: local n/a, remote 0 MTU: local 9198, remote 9198 Remote interface description: Sequencing: receive disabled, send disabled Control Word: On (configured: autosense) SSO Descriptor: 1.1.1.1/101, local label: 512 Dataplane: SSM segment/switch IDs: 4096/4096 (used), PWID: 1 VC statistics: transit packet totals: receive 172116845, send 172105364 transit byte totals: receive 176837217071, send 172103349728 transit packet drops: receive 0, seq error 0, send 0
pseudowire101 is up, VC status is up PW type: Ethernet Create time: 06:30:41, last status change time: 06:07:12 Last label FSM state change time: 06:07:12 Destination address: 1.1.1.1 VC ID: 101 Output interface: Vl182, imposed label stack {17 16} Preferred path: not configured Default path: active Next hop: 182.1.1.1 Load Balance: ECMP Flow classification: ip dst-ip Member of xconnect service pw101 Associated member Gi1/0/1 is up, status is up Interworking type is Like2Like Service id: 0xe5000001 Signaling protocol: LDP, peer 1.1.1.1:0 up Targeted Hello: 4.4.4.4(LDP Id) -> 1.1.1.1, LDP is UP Graceful restart: not configured and not enabled Non stop routing: not configured and not enabled PWid FEC (128), VC ID: 101 Status TLV support (local/remote) : enabled/supported LDP route watch : enabled Label/status state machine : established, LruRru Local dataplane status received : No fault BFD dataplane status received : Not sent BFD peer monitor status received : No fault Status received from access circuit : No fault Status sent to access circuit : No fault Status received from pseudowire i/f : No fault Status sent to network peer : No fault Status received from network peer : No fault Adjacency status of remote peer : No fault Sequencing: receive disabled, send disabled Bindings Parameter Local Remote ------------ ------------------------------ ------------------------------ Label 512 16 Group ID n/a 0 Interface MTU 9198 9198 Control word on (configured: autosense) on PW type Ethernet Ethernet VCCV CV type 0x02 0x02 LSPV [2] LSPV [2] VCCV CC type 0x06 0x06 RA [2], TTL [3] RA [2], TTL [3] Status TLV enabled supported Flow Label T=1, R=1 T=1, R=1 SSO Descriptor: 1.1.1.1/101, local label: 512 Dataplane: SSM segment/switch IDs: 4096/4096 (used), PWID: 1 Rx Counters 176196691 input transit packets, 181028952597 bytes 0 drops, 0 seq err Tx Counters 176184928 output transit packets, 176182865992 bytes 0 drops The following is a sample output of show mpls forwarding-table network mask command. Local Outgoing Prefix Bytes Label Outgoing Next Hop Label Label or Tunnel Id Switched interface 57 No Label 1.1.1.1/32 0 Po45 145.1.1.1 No Label 1.1.1.1/32 0 Te1/0/2 147.1.1.1 No Label 1.1.1.1/32 0 Te1/0/11 149.1.1.1 No Label 1.1.1.1/32 0 Te1/0/40 155.1.1.1
Configuring Pseudowire Redundancy
The L2VPN Pseudowire Redundancy feature enables you to configure your network to detect a failure in the network and reroute the Layer 2 (L2) service to another endpoint that can continue to provide service. This feature provides the ability to recover from a failure either of the remote provider edge (PE) router or of the link between the PE and customer edge (CE) routers.
Pseudowire Redundancy (PWR) can be configured using both – the xconnect and the protocol-CLI method.
VLAN mode, EFP (Ethernet Flow Point) and IGMP Snooping is not supported.
PWR is supported with port mode EoMPLS only.
Untagged, tagged and 802.1Q in 802.1Q are supported as incoming traffic.
Flow Label for ECMP Load balancing in core network based on customer’s source IP, destination IP, source MAC and destination MAC.
Enabling or disabling Control word is supported.
MPLS QoS is supported in Pipe and Uniform Mode. Default mode is Pipe Mode.
Port-channel as attachment circuit is not supported.
QoS : Customer DSCP Re-marking is not supported with VPWS and EoMPLS.
VCCV Ping with explicit null is not supported.
L2 VPN Interworking is not supported.
Not more than one backup pseudowire supported.
PW redundancy group switchover is not supported
Note | To enable load balance, use the corresponding load-balance commands from Xconnect Mode section of Configuring Port-Mode EoMPLS. |
To configure pseudowire redundancy in protocol-CLI mode, perform the following task :
PE Configuration |
CE Configuration |
---|---|
mpls ip mpls label protocol ldp mpls ldp graceful-restart mpls ldp router-id loopback 1 force ! interface Loopback1 ip address 1.1.1.1 255.255.255.255 ip ospf 100 area 0 router ospf 100 router-id 1.1.1.1 nsf ! interface GigabitEthernet2/0/39 no switchport no ip address no keepalive ! interface pseudowire101 encapsulation mpls neighbor 4.4.4.4 101 ! interface pseudowire102 encapsulation mpls neighbor 3.3.3.3 101 l2vpn xconnect context pw101 member pseudowire101 group pwgrp1 priority 1 member pseudowire102 group pwgrp1 priority 15 member GigabitEthernet2/0/39 ! interface TenGigabitEthernet3/0/10 switchport trunk allowed vlan 142 switchport mode trunk channel-group 42 mode active ! interface Port-channel42 switchport trunk allowed vlan 142 switchport mode trunk ! interface Vlan142 ip address 142.1.1.1 255.255.255.0 ip ospf 100 area 0 mpls ip mpls label protocol ldp ! |
interface GigabitEthernet1/0/33 switchport trunk allowed vlan 912 switchport mode trunk spanning-tree portfast trunk ! interface Vlan912 ip address 10.91.2.3 255.255.255.0 ! |
Device# show mpls l2transport vc 101 Local intf Local circuit Dest address VC ID Status ------------- -------------------------- --------------- ---------- ---------- Gi2/0/39 Ethernet 4.4.4.4 101 UP Device# show mpls l2transport vc 102 Local intf Local circuit Dest address VC ID Status ------------- -------------------------- --------------- ---------- ---------- Gi2/0/39 Ethernet 3.3.3.3 102 STANDBY