users connected to the same VLAN interface must use different VCs to forward packets. For
more information about service instances, see
NOTE:
Service instances can be created only on Layer 2 Ethernet interfaces or Layer 2 aggregate interfaces.
Configuring the remote peer
Step
1.
Enter system view.
2.
Configure an MPLS LDP remote peer and enter its
view.
3.
Specify the IP address of the remote peer.
For remote peer configuration information, see
Creating a Martini VC on a Layer 3 interface
IMPORTANT:
A Martini VC has two main parameters: IP address of the peer PE, and VC ID. The combination of the VC
ID and the encapsulation type must be unique on a PE. Changing the encapsulation type may result in VC
ID conflicts.
To create a Martini VC on a Layer 3 interface of a PE:
Step
1.
Enter system view.
2.
Enter the view of the interface connecting the CE.
3.
Create a Martini VC.
Creating a Martini VC for a service instance
To complete this task, perform the following configurations on a PE:
Create a service instance on a Layer 2 Ethernet interface or Layer 2 aggregate interface.
•
•
Configure a packet matching rule for the service instance.
Create a Martini VC for the service instance.
•
After you perform these configurations, packets arriving at the interface and matching the packet
matching rule are forwarded over the created VC.
To create multiple VCs with the same attributes (such as VC encapsulation type and VC tunneling policy),
you do not need to configure the attributes one by one for each VC. Instead, you can create a PW class,
configure VC attributes in the PW class, and then reference the PW class in each VC.
To create a Martini VC for a service instance:
"Configuring
Command
system-view
mpls ldp remote-peer remote-peer-name
remote-ip ip-address
"Configuring basic
Command
system-view
interface interface-type interface-number
mpls l2vc destination vcid [ ethernet | vlan } |
[ tunnel-policy tunnel-policy-name ] ] *
202
VPLS."
MPLS."