CSR1
xconnect 192.0.2.5 1 encapsulation mpls
%LINEPROTO-5-UPDOWN: Line protocol on Interface pseudowire0, changed state to up
%LDP-5-NBRCHG: LDP Neighbor 192.0.2.5:0 (2) is UP
CSR5
xconnect 192.0.2.1 1 encapsulation mpls
%LINEPROTO-5-UPDOWN: Line protocol on Interface pseudowire0, changed state to up
%LDP-5-NBRCHG: LDP Neighbor 192.0.2.1:0 (2) is UP
The configuration of the PE routers is straightforward, we configure the customer facing interfaces, the attachment circuits with the cross connect. Once this is completed, we see the pseudowire0 interface come online. We won’t see a targeted LDP peering until we exit the cross connect configuration. After we exit xconnect sub-config mode, the LDP peerings spin up. This LDP peering allocates the labels we’ll need for the data plane for the customers use, this is the VPN label from L3 VPN. BGP VPNv4/v6 isn’t used, so LDP allocates both the transport and VPN labels.
CSR5#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi3:9(Ethernet) UP mpls 192.0.2.1:1 UP
CSR1#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi5:11(Ethernet) UP mpls 192.0.2.5:1 UP
We see that both cross connects are online and operational.
CSR1#show xconnect all detail
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi5:11(Ethernet) UP mpls 192.0.2.5:1 UP
Interworking: none Local VC label 66
Remote VC label 44
CSR5#show xconnect all detail
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi3:9(Ethernet) UP mpls 192.0.2.1:1 UP
Interworking: none Local VC label 44
Remote VC label 66
We look at the details and see that there are Local VC and Remote VC labels. This is the VPN label allocation mentioned earlier. These labels are locally significant, when traffic with these labels are received, it points to the interface connecting to the customer. The Transport label gets the traffic from the ingress PE to the egress PE.
CSR5#show l2vpn atom vc vcid 1 detail
pseudowire100001 is up, VC status is up PW type: Ethernet
Create time: 00:02:59, last status change time: 00:02:59
Last label FSM state change time: 00:02:58
Destination address: 192.0.2.1 VC ID: 1
Output interface: Gi1, imposed label stack {16 66}
Preferred path: not configured
Default path: active
Next hop: 10.3.5.3
Member of xconnect service Gi3-9, group right
Associated member Gi3 is up, status is up
Interworking type is Like2Like
Service id: 0xf8000001
Signaling protocol: LDP, peer 192.0.2.1:0 up
Targeted Hello: 192.0.2.5(LDP Id) -> 192.0.2.1, LDP is UP
Graceful restart: not configured and not enabled
Non stop routing: not configured and not enabled
PWid FEC (128), VC ID: 1
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 44 66
Group ID n/a 0
Interface
MTU 1500 1500
Control word on (configured: autosense) on
PW type Ethernet Ethernet
VCCV CV type 0x02 0x02
LSPV [2] LSPV [2]
VCCV CC type 0x07 0x07
CW [1], RA [2], TTL [3] CW [1], RA [2], TTL [3]
Status TLV enabled supported
SSO Descriptor: 192.0.2.1/1, local label: 44
Dataplane:
SSM segment/switch IDs: 4097/4096 (used), PWID: 1
Rx Counters
1 input transit packets, 99 bytes
0 drops, 0 seq err
Tx Counters
0 output transit packets, 0 bytes
0 drops
CSR1#show l2vpn atom vc vcid 1 detail
pseudowire100001 is up, VC status is up PW type: Ethernet
Create time: 00:05:14, last status change time: 00:03:38
Last label FSM state change time: 00:03:38
Destination address: 192.0.2.5 VC ID: 1
Output interface: Gi1, imposed label stack {17 44}
Preferred path: not configured
Default path: active
Next hop: 10.1.3.3
Member of xconnect service Gi5-11, group right
Associated member Gi5 is up, status is up
Interworking type is Like2Like
Service id: 0x56000003
Signaling protocol: LDP, peer 192.0.2.5:0 up
Targeted Hello: 192.0.2.1(LDP Id) -> 192.0.2.5, LDP is UP
Graceful restart: not configured and not enabled
Non stop routing: not configured and not enabled
PWid FEC (128), VC ID: 1
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 66 44
Group ID n/a 0
Interface
MTU 1500 1500
Control word on (configured: autosense) on
PW type Ethernet Ethernet
VCCV CV type 0x02 0x02
LSPV [2] LSPV [2]
VCCV CC type 0x07 0x07
CW [1], RA [2], TTL [3] CW [1], RA [2], TTL [3]
Status TLV enabled supported
SSO Descriptor: 192.0.2.5/1, local label: 66
Dataplane:
SSM segment/switch IDs: 4103/4102 (used), PWID: 1
Rx Counters
0 input transit packets, 0 bytes
0 drops, 0 seq err
Tx Counters
1 output transit packets, 103 bytes
0 drops
On CSR5 we see an imposed label stack of 16 and 66. Label 16 is the label that gets us to CSR3 and label 66 is the label CSR1 allocated for the cross connect. The LDP peering is up and running and the PW type is Ethernet meaning the main interface.
On CSR1 we see an imposed label stack of 17 and 44. Label 17 is the label that gets us to CSR3 and label 44 is the label CSR5 allocated from the cross connect. The LDP peering is up and running and the PW type is Ethernet like CSR5.
CSR8
interface GigabitEthernet4
ip address 10.100.1.8 255.255.255.0
IOS18
interface GigabitEthernet0/2
ip address 10.100.1.18 255.255.255.0
The customer routers are configured with a subnet in the same VLAN.
CSR8#ping 10.100.1.18
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.1.18, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 17/23/34 ms
IOS18#show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.100.1.8 0 5000.0008.0003 ARPA GigabitEthernet0/2
Internet 10.100.1.18 - 5000.0012.0002 ARPA GigabitEthernet0/2
CSR1#show l2vpn atom vc vcid 1 detail | b Rx|Tx
Rx Counters
26 input transit packets, 5030 bytes
0 drops, 0 seq err
Tx Counters
6 output transit packets, 749 bytes
0 drops
CSR8 pings IOS18 and gets 4 successful ICMP replies. IOS18 shows that ARP was successfully resolved. CSR1 shows that the virtual circuit sees traffic in both directions.
CSR8#ping 10.100.1.18
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.1.18, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 13/22/44 ms
CSR1#show l2vpn atom vc vcid 1 detail | b Rx|Tx
Rx Counters
35 input transit packets, 6336 bytes
0 drops, 0 seq err
Tx Counters
11 output transit packets, 1449 bytes
0 drops
We ping some more and see an increase in the counters.
CSR1#show mpls forwarding-table labels 66
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
66 No Label l2ckt(1) 7126 Gi5 point2point
CSR5#show mpls forwarding-table labels 44
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
44 No Label l2ckt(1) 1405 Gi3 point2point
The MPLS label counters also show under the bytes switched, that the counters have increased.
xconnect 192.0.2.5 1 encapsulation mpls
%LINEPROTO-5-UPDOWN: Line protocol on Interface pseudowire0, changed state to up
%LDP-5-NBRCHG: LDP Neighbor 192.0.2.5:0 (2) is UP
CSR5
xconnect 192.0.2.1 1 encapsulation mpls
%LINEPROTO-5-UPDOWN: Line protocol on Interface pseudowire0, changed state to up
%LDP-5-NBRCHG: LDP Neighbor 192.0.2.1:0 (2) is UP
The configuration of the PE routers is straightforward, we configure the customer facing interfaces, the attachment circuits with the cross connect. Once this is completed, we see the pseudowire0 interface come online. We won’t see a targeted LDP peering until we exit the cross connect configuration. After we exit xconnect sub-config mode, the LDP peerings spin up. This LDP peering allocates the labels we’ll need for the data plane for the customers use, this is the VPN label from L3 VPN. BGP VPNv4/v6 isn’t used, so LDP allocates both the transport and VPN labels.
CSR5#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi3:9(Ethernet) UP mpls 192.0.2.1:1 UP
CSR1#show xconnect all
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi5:11(Ethernet) UP mpls 192.0.2.5:1 UP
We see that both cross connects are online and operational.
CSR1#show xconnect all detail
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi5:11(Ethernet) UP mpls 192.0.2.5:1 UP
Interworking: none Local VC label 66
Remote VC label 44
CSR5#show xconnect all detail
Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Gi3:9(Ethernet) UP mpls 192.0.2.1:1 UP
Interworking: none Local VC label 44
Remote VC label 66
We look at the details and see that there are Local VC and Remote VC labels. This is the VPN label allocation mentioned earlier. These labels are locally significant, when traffic with these labels are received, it points to the interface connecting to the customer. The Transport label gets the traffic from the ingress PE to the egress PE.
CSR5#show l2vpn atom vc vcid 1 detail
pseudowire100001 is up, VC status is up PW type: Ethernet
Create time: 00:02:59, last status change time: 00:02:59
Last label FSM state change time: 00:02:58
Destination address: 192.0.2.1 VC ID: 1
Output interface: Gi1, imposed label stack {16 66}
Preferred path: not configured
Default path: active
Next hop: 10.3.5.3
Member of xconnect service Gi3-9, group right
Associated member Gi3 is up, status is up
Interworking type is Like2Like
Service id: 0xf8000001
Signaling protocol: LDP, peer 192.0.2.1:0 up
Targeted Hello: 192.0.2.5(LDP Id) -> 192.0.2.1, LDP is UP
Graceful restart: not configured and not enabled
Non stop routing: not configured and not enabled
PWid FEC (128), VC ID: 1
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 44 66
Group ID n/a 0
Interface
MTU 1500 1500
Control word on (configured: autosense) on
PW type Ethernet Ethernet
VCCV CV type 0x02 0x02
LSPV [2] LSPV [2]
VCCV CC type 0x07 0x07
CW [1], RA [2], TTL [3] CW [1], RA [2], TTL [3]
Status TLV enabled supported
SSO Descriptor: 192.0.2.1/1, local label: 44
Dataplane:
SSM segment/switch IDs: 4097/4096 (used), PWID: 1
Rx Counters
1 input transit packets, 99 bytes
0 drops, 0 seq err
Tx Counters
0 output transit packets, 0 bytes
0 drops
CSR1#show l2vpn atom vc vcid 1 detail
pseudowire100001 is up, VC status is up PW type: Ethernet
Create time: 00:05:14, last status change time: 00:03:38
Last label FSM state change time: 00:03:38
Destination address: 192.0.2.5 VC ID: 1
Output interface: Gi1, imposed label stack {17 44}
Preferred path: not configured
Default path: active
Next hop: 10.1.3.3
Member of xconnect service Gi5-11, group right
Associated member Gi5 is up, status is up
Interworking type is Like2Like
Service id: 0x56000003
Signaling protocol: LDP, peer 192.0.2.5:0 up
Targeted Hello: 192.0.2.1(LDP Id) -> 192.0.2.5, LDP is UP
Graceful restart: not configured and not enabled
Non stop routing: not configured and not enabled
PWid FEC (128), VC ID: 1
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 66 44
Group ID n/a 0
Interface
MTU 1500 1500
Control word on (configured: autosense) on
PW type Ethernet Ethernet
VCCV CV type 0x02 0x02
LSPV [2] LSPV [2]
VCCV CC type 0x07 0x07
CW [1], RA [2], TTL [3] CW [1], RA [2], TTL [3]
Status TLV enabled supported
SSO Descriptor: 192.0.2.5/1, local label: 66
Dataplane:
SSM segment/switch IDs: 4103/4102 (used), PWID: 1
Rx Counters
0 input transit packets, 0 bytes
0 drops, 0 seq err
Tx Counters
1 output transit packets, 103 bytes
0 drops
On CSR5 we see an imposed label stack of 16 and 66. Label 16 is the label that gets us to CSR3 and label 66 is the label CSR1 allocated for the cross connect. The LDP peering is up and running and the PW type is Ethernet meaning the main interface.
On CSR1 we see an imposed label stack of 17 and 44. Label 17 is the label that gets us to CSR3 and label 44 is the label CSR5 allocated from the cross connect. The LDP peering is up and running and the PW type is Ethernet like CSR5.
CSR8
interface GigabitEthernet4
ip address 10.100.1.8 255.255.255.0
IOS18
interface GigabitEthernet0/2
ip address 10.100.1.18 255.255.255.0
The customer routers are configured with a subnet in the same VLAN.
CSR8#ping 10.100.1.18
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.1.18, timeout is 2 seconds:
.!!!!
Success rate is 80 percent (4/5), round-trip min/avg/max = 17/23/34 ms
IOS18#show arp
Protocol Address Age (min) Hardware Addr Type Interface
Internet 10.100.1.8 0 5000.0008.0003 ARPA GigabitEthernet0/2
Internet 10.100.1.18 - 5000.0012.0002 ARPA GigabitEthernet0/2
CSR1#show l2vpn atom vc vcid 1 detail | b Rx|Tx
Rx Counters
26 input transit packets, 5030 bytes
0 drops, 0 seq err
Tx Counters
6 output transit packets, 749 bytes
0 drops
CSR8 pings IOS18 and gets 4 successful ICMP replies. IOS18 shows that ARP was successfully resolved. CSR1 shows that the virtual circuit sees traffic in both directions.
CSR8#ping 10.100.1.18
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.100.1.18, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 13/22/44 ms
CSR1#show l2vpn atom vc vcid 1 detail | b Rx|Tx
Rx Counters
35 input transit packets, 6336 bytes
0 drops, 0 seq err
Tx Counters
11 output transit packets, 1449 bytes
0 drops
We ping some more and see an increase in the counters.
CSR1#show mpls forwarding-table labels 66
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
66 No Label l2ckt(1) 7126 Gi5 point2point
CSR5#show mpls forwarding-table labels 44
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
44 No Label l2ckt(1) 1405 Gi3 point2point
The MPLS label counters also show under the bytes switched, that the counters have increased.
