H3C Technologies H3C SR8800 - Manual (Page 212)

201
Step Command Remarks
1. Enter system view. system-view N/A
2. Create a VPN and enter MPLS
L2VPN view.
mpls l2vpn vpn-name [ encapsulation { atm-aal5
| ethernet | fr | hdlc | ppp | vlan }
[ control-word | no-control-word ] ]
N/A
3. Configure an RD for the
L2VPN.
route-distinguisher route-distinguisher N/A
4. Associate a particular VPN
with one or more VPN targets.
vpn-target vpn-target&<1-16> [ both |
export-extcommunity | import-extcommunity ]
N/A
5. Set the Layer 2 MTU for the
VPN.
mtu mtu Optional
CAUTION:
•
H3C does not recommend configuring the mtu command. It affects only possible parameter
negotiations. It does not affect data forwarding.
• With Kompella MPLS L2VPN, you must create on the PE an L2VPN instance for each VPN where a
directly connected CE resides. When creating an L2VPN, you must specify an encapsulation type
matching that of the CE side interface.
• The configuration of the VPN targets and RD are the same as that for MPLS L3VPN. For Kompella MPLS
L2VPN, the RD is required. Once configured, an RD cannot be changed, unless you delete the L2VPN
and then re-create it.
• When configuring a Kompella MPLS L2VPN connection on a Layer 3 Ethernet sub-interface on an SPC
card, you must configure the VPN encapsulation mode as VLAN. Otherwise, packets may not be
forwarded correctly.
Creating a CE Connection
CE ID is used for identifying a CE uniquely in a VPN. To facilitate the configuration, encode the CE IDs
in continuous natural numbers starting from 1.
The CE range of a VPN indicates the maximum number of CEs that can be connected to the VPN. You
can configure a CE range greater than what is required based on your estimate of the future VPN
expansion if the label resources are abundant (they are usually abundant). This can reduce the
configuration modification required when CEs are added in the VPN in future.
When creating a CE connection, if you do not specify the CE offset:
• For the first connection of the CE, the CE offset is the value specified by the default-offset parameter
in the ce command.
• For any other connection of the CE, the CE offset is that of the former connection plus 1.
• When you plan a VPN, H3C recommends encoding CE IDs in incremental sequence starting from
1 and then configuring connections in the sequence of the CE IDs, in which case you can omit the
ce-offset keyword (use the default setting) for most of connections.
You can only increase the CE range. For example, if the original CE range is 10, you can increase it to
20, but cannot reduce it to 5. The only way to reduce the CE range is to delete the CE and re-create it.
When you increase the CE range, for example, from 10 to 20, the system does not release the original
label block and then re-apply for a new label block of the size of 20. Instead, the system applies for a
supplementary label block of the size of 10. This ensures that the existing services will not be interrupted.
To create a CE connection: