135
Configuring a BGP VPLS instance
When creating a BGP VPLS instance, you must specify a globally unique name for the VPLS instance and
set the peer discovery mechanism to automatic configuration.
When configuring a BGP VPLS instance, you must configure BGP as the signaling protocol to be used.
To configure a BGP VPLS instance:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a BGP VPLS instance and
enter VSI view
vsi
vsi-name
auto
Required
Specify BGP as the PW signaling
protocol and enter VSI BGP view
pwsignal bgp
Required
Configure an RD for the VPLS
instance
route-distinguisher
route-distinguisher
Required
Configure VPN targets for the VPLS
instance
vpn-target
vpn-target
&<1-16>
[
both
|
import-extcommunity
|
export-extcommunity
]
Required
Create a site for the VPLS instance
site
site-id
[
range
site-range
]
[
default-offset
{ 0 | 1 } ]
Required
Resetting VPLS BGP connections
When the BGP routing policy or protocol is changed, you must reset the BGP connections in a VPLS to
make the new configurations take effect to all connections.
To reset VPLS BGP connections:
To do…
Use the command…
Remarks
Reset a specific or all VPLS BGP
connections
reset bgp vpls
{
as-number
|
ip-address
|
all
|
external
|
internal
}
Available in user view
Binding a VPLS instance
You can establish the association between packets and a VPLS instance in either of the following
methods:
•
Binding a Layer 3 interface with the VPLS instance. After you configure such a binding, all packets
arriving at the Layer 3 interface will be forwarded by the VPLS instance.
•
Binding a service instance with the VPLS instance. After you configure such a binding, the switch
matches packets received on the Layer 2 Ethernet port according to the service instance. Packets
that match the service instance will be forwarded by the VPLS instance bound with the service
instance. A service instance can be used to match all packets received on the port, packets carrying
the specified VLAN tags, all tagged packets, or all packets with no VLAN tags, providing a more
flexible VPLS instance access control.