Creating VSIs and Configuring the BGP AD Signaling
Context
When configuring BGP AD VPLS, you need to create VSIs on PEs, set automatic VPLS member discovery and PW deployment for the VSIs, configure BGP AD signaling on the PEs, and set VPLS IDs and VPN targets for the VSIs in the VSI-BGPAD view.
Perform the following steps on PEs at both ends of a PW:
Procedure
- Run system-view
The system view is displayed.
- Run vsi vsi-name
A VSI is created.
- Run bgp-ad
Automatic VPLS member discovery and PW deployment are set for the VSI, and the VSI-BGP AD view is displayed.
- Run vpls-id vpls-id
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.
- Run vpn-target vpn-target & <1-16> [ both | export-extcommunity | import-extcommunity ]
A 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.
- (Optional) Run pw spoke-mode
Split horizon is disabled for all PWs in a VSI.
By default, all PW attributes of a BGP AD VSI are Hub.
The function of this command is similar to the function of configuring a peer PE as a UPE on a Martini 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.
- (Optional) The VPLS encapsulation type is configured.