204Inspecting VCsOn a MPLS L2VPN network, you can use the MPLS LSP ping function to test the connectivity of VCs andget necessary information for troubleshooting VC failuresOn the local PE, the MPLS LSP ping function adds the label of the VC to be tested into MPLS Echo Requestmessages so the messages travel along the VC. The local PE determines whether the VC is valid andreachable according to the replies received from the peer PE.To test the VC connectivity, perform the following task in any view:Task Command RemarksUse MPLS LSP ping to test the VCconnectivity.ping lsp [ -a source-ip | -c count |-exp exp-value | -h ttl-value | -mwait-time | -r reply-mode | -spacket-size | -t time-out | -v ] * pwip-address pw-id pw-idMPLS LSP ping can be used to testthe connectivity of only a MartiniVC.Configuring Kompella MPLS L2VPNTo 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 capabilityStep Command Remarks1. Enter system view. system-view N/A2. Enter BGP view. bgp as-number N/A3. Establish the peer relationshipwith the peer PE.peer { group-name | ip-address }as-number as-number N/A4. Specify the interface for theTCP connection.peer { group-name | ip-address }connect-interface interface-typeinterface-numberN/A5. Enter BGP L2VPN addressfamily view. l2vpn-familyFor more information about theconfiguration in BGP-L2VPNaddress family, see "ConfiguringMPLS L3VPN."6. Enable the filtering by theVPN target extendedcommunity attributes for thereceived routing information.policy vpn-target Optional.Enabled by default.7. Enable the specified peer orpeers to exchange BGProuting information of theBGP-L2VPN address family.peer { group-name | ip-address }enable N/A