Implementing Multi-As Vpn Through Multi-Hop Pw - HP 12500 Series Configuration Manual

Mpls, routing switch series
Table of Contents

Advertisement

Session State: Up
Min Trans Inter: 400ms
Min Recv Inter: 400ms
Running Up for: 00:00:01
Connect Type: Indirect
Local Discr: 4
Session State: Up
Min Trans Inter: 400ms
Min Recv Inter: 400ms
Running Up for: 00:00:01
Connect Type: Indirect
# 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
VsiID
100
100
# 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
VsiID
100

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.
Protocol: MFW/LDP
Diag Info: No Diagnostic
Source IP: 1.1.1.9
Protocol: MFW/LDP
Diag Info: No Diagnostic
VsiType
vlan
vlan
VsiType
vlan
Interface: LoopBack0
Act Trans Inter: 400ms
Act Detect Inter: 2000ms
Auth mode: None
Board Num: 6
Remote Discr: 0
Destination IP: 3.3.3.9
Interface: LoopBack0
Act Trans Inter: 1000ms
Act Detect Inter: 3000ms
Auth mode: None
Board Num: 6
Signaling: ldp
PeerAddr
InLabel OutLabel LinkID
2.2.2.9
134312
3.3.3.9
134216
Signaling: ldp
PeerAddr
3.3.3.9
161
138882
1
140476
2
InLabel OutLabel LinkID
134216
140476
2
VCState
up
block
VCState
up

Advertisement

Table of Contents
loading

Table of Contents