R2511-HP MSR Router Series MPLS Configuration Guide(V5)

56
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
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
4. Specify the interface for the
TCP connection.
peer { group-name | ip-address }
connect-interface interface-type
interface-number
N/A
5. Enter BGP L2VPN address
family view.
l2vpn-family N/A
6. Enable the filtering by the
route target extended
community attributes for the
received routing information.
policy vpn-target
Optional.
Enabled by default.
7. Enable the specified peer or
peers to exchange BGP
routing information of the
BGP-L2VPN address family.
peer { group-name | ip-address }
enable
N/A
For more information about the configuration in BGP-L2VPN address family, see "Configuring MPLS
L3VPN."