Binding An Ethernet Service Instance To A Vsi - HP FlexNetwork 10500 Series Configuration Manual

Creating a BGP auto-discovery LDP PW
Step
1. Enter system view.
2. Enter VSI view.
3. Configure the VSI to
automatically discover
neighbors through BGP and
enter auto-discovery VSI
view.
4. Configure an RD for the
auto-discovery VSI.
5. Configure route targets for
the auto-discovery VSI.
6. (Optional.) Specify a PW
class for the auto-discovery
VSI.
7. (Optional.) Specify a tunnel
policy for the auto-discovery
VSI.
8. Use LDP to create a PW to
an automatically discovered
remote PE and enter
auto-discovery VSI LDP
signaling view.
9. Configure a VPLS ID for the
VSI.

Binding an Ethernet service instance to a VSI

IMPORTANT:
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 Layer
2 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.
When you bind an Ethernet service instance to a VSI, you can associate Track with the Ethernet
service instance. Then, the Ethernet service instance is up only when one or more of the associated
track entries are positive.
To bind an Ethernet service instance to a VSI:
Step
1. Enter system view.
Command
system-view
vsi vsi-name
auto-discovery bgp
route-distinguisher
route-distinguisher
vpn-target vpn-target&<1-8>
[ both | export-extcommunity |
import-extcommunity ]
pw-class class-name
tunnel-policy tunnel-policy-name
signaling-protocol ldp
vpls-id vpls-id
Command
system-view
383
Remarks
N/A
N/A
By default, a VSI does not
automatically discover neighbors
through BGP.
By default, no RD is configured for
the auto-discovery VSI.
By default, no route targets are
configured for the auto-discovery
VSI.
By default, no PW class is
specified.
By default, no tunnel policy is
specified.
By default, no signaling protocol is
specified.
By default, no VPLS ID is
configured.
Remarks
N/A