Creating VSIs and Configuring BGP Signaling

Procedure

1. Run system-view

   The system view is displayed.

2. Run vsi vsi-name

   A VSI is created.

3. Run bgp-ad

   Automatic VPLS member discovery and PW deployment are set for the VSI, and the VSI-BGPAD view is displayed.

4. Run vpls-id vplsIdValue

   A VPLS ID is set.

   

   • By default, the RD of BGP AD VPLS is the same as the VPLS ID. If a VPLS ID is set, an RD does not need to be set. The VSI ID is equal to the local LSR ID and does not need to be set.

   • The VPLS IDs for VSIs in one VPLS domain must be the same.

5. Run vpn-target vpn-target & <1-16> [ both | export-extcommunity | import-extcommunity ]

   The VPN target is configured for the VSI.

   The mappings between the local VPN target attribute and the peer VPN target attribute must be correct:

   • The local export-extcommunity is the same as the peer import-extcommunity.

   • The local import-extcommunity is the same as the peer export-extcommunity.

   Traffic is transmitted properly in a bidirectional manner only if the preceding two conditions are both met. If only one condition is met, traffic is transmitted only in a unidirectional manner. These four parameters are usually set to the same value.

6. (Optional) Run pw spoke-mode

   Split horizon is disabled for all PWs in a VPLS domain.

   

   The function of this command is similar to the function of configuring a peer PE as a UPE on a LDP HVPLS network. The difference is that this command allows all peer PEs in a VPLS domain to serve as UPEs. This means a star topology, in which a PE functions as a Hub, and other PEs connected to this Hub are Spoke PEs.

7. Run peer peer-address pw pw-name

   A PW is created.

8. Run commit

   The configuration is committed.