Configuring L2VPN Instances on PE Devices

Context

On a Kompella VLL network, L2VPN instances are configured on PE devices, with each L2VPN instance representing a private Kompella VLL network. In an L2VPN instance, the PE device creates one CE entity for each CE device connected to it and assigns a CE ID to each CE entity. The CE ID is unique within the L2VPN instance. Any two CE devices in this L2VPN instance can set up P2P VLL connections to communicate at Layer 2.

Procedure

Perform the following operations on the PE devices at both ends of a VC:
1. Run system-view
  The system view is displayed.
2. Run mpls l2vpn l2vpn-name encapsulation { ethernet | vlan } [ control-word | no-control-word ]
  An L2VPN instance is created, an encapsulation mode is specified for the L2VPN instance, and the MPLS L2VPN instance view is displayed.
3. Run route-distinguisher route-distinguisher
  An RD is configured for the L2VPN instance.
  
  An L2VPN instance takes effect only after the RD is configured. Each L2VPN instance on a PE must have a unique RD.
  
  The RD cannot be changed once it is configured. The only way to modify the RD is to delete this VLL and create a new one.
4. (Optional) Run mtu mtu-value
  The Layer 2 MTU is set for the VPN.
  
  The MTU for the VPN must be consistent throughout the entire network. If different MTU values are configured for the same VPN on two PEs, the two PEs cannot exchange reachability information or set up connections. By default, the MTU of an MPLS-L2VPN instance is 1500 bytes.
  
  Devices of some manufacturers do not support the MTU matching check in the L2VPN instance. When Huawei devices are used with non-Huawei devices in Kompella mode, either:
  - Configure the L2VPN MTU on the PE to be the same as that on the non-Huawei devices.
  - Use the ignore-mtu-match command to disable the MTU matching check.
5. Run vpn-target vpn-target & <1-16> [ both | export-extcommunity | import-extcommunity ]
  The VPN target is configured for the L2VPN instance. A VPN target is a BGP extended community attribute. It is used to control the receiving and advertisement of L2VPN information. A maximum of 16 VPN targets can be configured using a vpn-target command.