Configuring an I-VSI on an SPE

This section describes how to change a common virtual switching instance (VSI) on a superstratum provider edge (SPE) to be a multipoint-to-multipoint (MP2MP) I-VSI and bind the I-VSI to a backbone Ethernet VPN (B-EVPN) instance.

Context

During migration from a large-scale hierarchical virtual private LAN service (HVPLS) network to a provider backbone bridge Ethernet VPN (PBB-EVPN), HVPLS and PBB-EVPN will coexist for some time. To switch service traffic from the HVPLS network to the PBB-EVPN, you have to change the VSIs on SPEs to be MP2MP I-VSIs and bind these I-VSIs to B-EVPN instances. The I-tag of an I-VSI must be the same as the service instance identifier (I-SID) of the remote I-EVPN instance. Otherwise, services cannot be forwarded.

Procedure

Run system-view
The system view is displayed.
Run vsi vsi-name i-vsi b-evpn-interworking
An I-VSI is configured.
Run pwsignal ldp
LDP is configured as the signaling protocol for the I-VSI.
Run vsi-id vsi-id
An ID is configured for the I-VSI.
Run peer peer-address upe
A UPE is specified as an I-VSI peer.
Run quit
Return to the VSI view.
Run ignore-ac-state
The I-VSI is configured to ignore attachment circuit (AC) status changes.
Run pbb i-tag i-tag
An I-tag is configured for the I-VSI.

The I-tag of an I-VSI must be the same as the I-SID of the remote I-EVPN instance.
Run pbb binding b-evpn vpn-instance-name
The I-VSI is bound to the specified B-EVPN instance.
Run commit
The configuration is committed.