Creating a ce connection – H3C Technologies H3C S7500E Series Switches User Manual
Page 206

5-14
To do…
Use the command…
Remarks
Create a VPN and enter MPLS
L2VPN view
mpls l2vpn vpn-name
[ encapsulation { ethernet | vlan }
[ control-word |
no-control-word
] ]
Required
Configure an RD for the L2VPN
route-distinguisher
route-distinguisher
Required
Associate a particular VPN with
one or more VPN targets
vpn-target vpn-target
&<1-16>
[ both | export-extcommunity |
import-extcommunity
]
Required
Set the Layer 2 MTU for the VPN
mtu mtu
Optional
z
The mtu command is not recommended. It affects only parameter negotiation, which may occur;
it does not affect data forwarding.
z
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.
z
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.
Creating a CE Connection
CE ID is used for identifying a CE uniquely in a VPN. To facilitate the configuration, it is recommended
to 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, the following are true:
z
For the first connection of the CE, the CE offset is the value specified by the default-offset
parameter in the ce command.
z
For any other connection of the CE, the CE offset is that of the former connection plus 1.
z
When planning a VPN, you are recommended to encode CE IDs in incremental sequence starting
from 1. When configuring connections, you are recommended to adopt the sequence of the CE
IDs, in which case you can omit the ce-offset portion from most of the required commands. This
simplifies the configuration.