R3102-R3103-HP 6600/HSR6600 Routers MPLS Configuration Guide

169
Ste
p
Command
Remarks
11. Display information about one
or all service instances
configured on the interface.
display service-instance interface
interface-type interface-number
[ service-instance instance-id ] [ |
{ begin | exclude | include }
regular-expression ]
Available in any view.
To ensure normal forwarding of VPN traffic, the Layer 2 Ethernet interface must allow the VLANs that
might appear in the VPN traffic. For more information about VLAN configuration, see Layer 2—LAN
Switching Configuration Guide.
Inspecting VCs
On a MPLS L2VPN network, you can use the MPLS LSP ping function to test the VC connectivity and get
necessary information for troubleshooting VC failures.
On the local PE, the MPLS LSP ping function adds the label of the VC to be tested into MPLS Echo Request
messages so the messages will travel along the VC. The local PE determines whether the VC is valid and
reachable according to the replies received from the peer PE.
To test the VC connectivity, perform the following task in any view:
Task Command
Remarks
Use MPLS LSP ping to check VC
connectivity.
ping lsp [ -a source-ip | -c count |
-exp exp-value | -h ttl-value | -m
wait-time | -r reply-mode | -s
packet-size | -t time-out | -v ] * pw
ip-address pw-id pw-id
Applicable only to Martini VCs.
Configuring Kompella MPLS L2VPN
To configure a Kompella MPLS L2VPN, perform the following configurations on PEs:
Configure BGP L2VPN capability. (Not needed for a local connection.)
Create and configure MPLS L2VPN.
Create a CE connection.
Configuring BGP L2VPN capability
Ste
p
Command
Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Establish the peer relationship
with the peer PE.
peer { group-name | ip-address }
as-number as-number
N/A