To do...
Add the interface connecting the
CE to the VLAN
Return to system view
Enter the view of the interface
connecting the CE
Create a service instance and
enter its view
Configure a packet matching
rule for the service instance
Bind the service instance with a
VPLS instance
CAUTION:
Do not bind the control VLAN of an RRPP domain with a VPLS instance. Otherwise, a broadcast storm will
occur, crashing down the network. For more information about RRPP, see
Guide
.
NOTE:
Only when the VPLS instance is enabled with the hub-spoke capability (the hub-spoke keyword
•
included in the vsi static command), can you further specify the access mode as hub or spoke. The
default is spoke.
A P2P enabled VPLS instance cannot be bound with a service instance.
•
The xconnect vsi command is available for service instances with the ID in the range of 1 to 4094.
•
Configuring VPLS and MAC-in-MAC dual-stack
support
A device that supports VPLS and MAC-in-MAC dual-stack can serve as a PE on the VPLS network and a
backbone edge bridge (BEB) on the Provider Backbone Bridge Network (PBBN) at the same time to
connect the VPLS network and the PBBN together. Such a device is called a "BEB-PE", as shown in
35. For more information about MAC-in-MAC, see Layer 2—LAN Switching Configuration Guide.
Use the command...
port interface
quit
interface interface-type
interface-number
service-instance
service-instance-id
encapsulation { s-vid vlan-id
[ only-tagged ] | port-based |
tagged | untagged }
xconnect vsi vsi-name
[ access-mode { ethernet | vlan }
| { hub | spoke } ] *
137
Remarks
Required
—
—
Required
By default, no service instance is
created.
Required
By default, no packet matching rule is
configured for a service instance.
IMPORTANT:
For this configuration task, do not
configure the only-tagged, tagged, or
untagged keyword. Otherwise, the
packet matching rule does not take
effect.
Required
By default, a service instance is not
bound with any VPLS instance.
High Availability Configuration
Figure