367
[
both
|
export-extcommunity
|
import-extcommunity
]
configured for the auto-discovery
VSI.
6.
class for the auto-discovery
VSI.
pw-class
class-name
By default, no PW class is
specified.
7. (Optional.) Specify a tunnel
policy for the auto-discovery
VSI.
tunnel-policy
tunnel-policy-name
By
default, no tunnel policy is
specified.
8. Use LDP to create a PW to
an automatically discovered
auto-
signaling view.
signaling-protocol
ldp
By default, no signaling protocol is
specified.
9. Configure a VPLS ID for the
VSI.
vpls-id
vpls-id
By default, no VPLS ID is
configured.
Binding an AC to a VSI
This task is mutually exclusive from Ethernet link aggregation. If a Layer 2 Ethernet interface has
been added to a link aggregation group, you cannot bind an Ethernet service instance on the
interface to a VSI, and vice versa.
On a Layer 2 Ethernet or Layer 2 aggregate interface, you can create an Ethernet service instance
and bind it to a VSI. The Ethernet service instance matches packets received on that interface. The
matching packets are then forwarded based on the MAC address table of the VSI. An Ethernet
service instance can match all packets, tagged packets, or untagged packets.
To bind an Ethernet service instance to a VSI:
1. Enter system view.
system-view
N/A
2. Enter Layer
interface view
aggregate interface view.
•
Enter Layer 2 Ethernet interface
view:
interface interface-type
interface-number
• Enter Layer 2 aggregate interface
view:
interface bridge-aggregation
interface-number
N/A
3. Create an Ethernet service
instance and enter Ethernet
service instance view.
service-instance
instance-id
By default, no Ethernet
service instance exists on
the interface.
4.
Bind the Ethernet service
instance to a VSI.
xconnect vsi
vsi-name [
access-mode
{
ethernet
|
vlan
} ]
service instance is not bound
to any VSI.
Configuring UPE dual homing
This task includes the following configurations:
• Create a backup PW for the primary PW.
To Next Page
Loading...
Need help?
General