161
Session State: Up Interface: LoopBack0
Min Trans Inter: 400ms Act Trans Inter: 400ms
Min Recv Inter: 400ms Act Detect Inter: 2000ms
Running Up for: 00:00:01 Auth mode: None
Connect Type: Indirect Board Num: 6
Protocol: MFW/LDP
Diag Info: No Diagnostic
Local Discr: 4 Remote Discr: 0
Source IP: 1.1.1.9 Destination IP: 3.3.3.9
Session State: Up Interface: LoopBack0
Min Trans Inter: 400ms Act Trans Inter: 1000ms
Min Recv Inter: 400ms Act Detect Inter: 3000ms
Running Up for: 00:00:01 Auth mode: None
Connect Type: Indirect Board Num: 6
Protocol: MFW/LDP
Diag Info: No Diagnostic
# Execute the
display vpls connection vsi vpna
command on Switch A. You can see that the link
between Switch A and Switch B is up.
<SwitchA> display vpls connection vsi vpna
Total 2 connection(s),
connection(s): 1 up, 1 block, 0 down
VSI Name: vpna Signaling: ldp
VsiID VsiType PeerAddr InLabel OutLabel LinkID VCState
100 vlan 2.2.2.9 134312 138882 1 up
100 vlan 3.3.3.9 134216 140476 2 block
# Disconnect the link between Switch A and Switch B. Then, execute the
display vpls connection
vsi vpna
command. You can see that the link to 3.3.3.9 is up.
<SwitchA> display vpls connection vsi vpna
Total 1 connection(s),
connection(s): 1 up, 0 block, 0 down
VSI Name: vpna Signaling: ldp
VsiID VsiType PeerAddr InLabel OutLabel LinkID VCState
100 vlan 3.3.3.9 134216 140476 2 up
Implementing multi-AS VPN through multi-hop PW
Network requirements
Create a VPLS instance that supports P2P on ASBR 1 and ASBR 2, so as to set up a multi-hop PW
between PE 1 and PE 2.
On PE 1 and PE 2, configure a service instance and bind it to the VPLS instance. The service instance
matches the received packets that carry VLAN tag 100 on GigabitEthernet 3/0/1. The matched packets
are forwarded by the VPLS instance.