To configure a site for BGP AD or BGP VPLS

Purpose

This procedure provides the steps required to enable BGP Auto Discovery or configure BGP VPLS on a VPLS site.

  • BGP AD enables a VPLS PE router to discover other PE routers that are part of the same VPLS domain. T-LDP based label signaling is used for the pseudowire.

  • BGP VPLS provides the mechanism for service member auto-discovery based on Route Target. MP-BGP based label signaling is used for the pseudowire.

The following considerations apply:

  • BGP AD and BGP VPLS implementations only apply to regular VPLS sites and B-Sites, but not to I-Sites. For BGP VPLS, the B-Site cannot be used as a backbone for an I-Site or Epipe.

  • For 7210 SAS NEs that support BGP AD, only VPLS service sites are supported (not MVPLS or B-sites).

  • Up to two BGP instances can be created per VPLS site.

Steps
 
1 

Prior to configuring a site for BGP AD or BGP VPLS, you must complete the following actions:

  1. Create a routing policy statement to define the required community members. See To configure a routing policy statement . This defines the VSI Import/Export Routing Targets.

  2. Enable BGP on the routing instance of each NE in the VPLS or BGP VPLS. See To enable BGP on a routing instance for more information.

  3. Configure global-level BGP on each NE in the VPLS or BGP VPLS. See To configure global-level BGP for more information.

    The following items are required for BGP AD implementation:

    • You must enable the L2 VPN parameter in the Family panel on one or more of the following:

      • the VPN tab of the BGP site form

      • the VPN tab of the BGP Peer Group form, which contains the peers that are involved in the BGP multi-homing

      • the VPN tab of the BGP peer form, which participates in BGP signaling

    • Create a peer group under BGP. This peer group is used to collectively define the peers involved in the VPLS.

    • Create the required peers under the peer group. These peers are the NEs involved in the VPLS.

  4. Create a PW template policy. See Chapter 83, Service PW template policies for information about PW template policies.

  5. Distribute the PW template policy to each NE that is or will be a component of the VPLS or BGP VPLS.

  6. Ensure that the BGP AD Administrative Status parameter is set to Up and that the VPLS ID parameter is configured.

2 

Choose Manage→Service→Services from the NFM-P main menu. The Manage Services form opens.

3 

Choose the required VPLS and click Properties. The VPLS Service (Edit) form opens.

4 

On the service tree, expand Sites and click on the site on which you want to configure BGP AD or BGP VPLS.

5 

Click on the BGP tab.

6 

Enable the Enable BGP parameter. The BGP panel is displayed.

7 

Click Create. The BGP Configuration form opens.

8 

Configure the Route Distinguisher parameter.

9 

Click on the VSI Import Policies tab.

10 

Select up to five import policies. Alternatively, you can enter the policy names manually.

11 

Perform one of the following:

  1. Enter the Import Route Target name manually in the provided field. The format be “target:x:y”.

  2. Select an import route target. The community members you defined when creating a routing policy in Step 1 can be selected.

12 

Click on the VSI Export Policies tab and select up to five export policies. Alternatively, you can enter the policy names manually.

13 

Perform one of the following:

  1. Enter the Export Route Target name manually in the provided field. The format must be “target:x:y”.

  2. Select an export route target. The community members you defined when creating a routing policy in Step 1 can be selected.

14 

Click on the PW Template Binding tab and perform one of the following:

  1. Select an existing PW Template Binding.

  2. Add a new PW Template Binding. Go to Step 15 .

15 

Create one or more PW Template Bindings:

  1. Click Create. The PW Template Binding (Create) form opens.

  2. Enter a Split Horizon Group name.

  3. Select the PW Template you created in Step 1 .

  4. Select an operational group.

  5. Click on the BFD tab and configure the required BFD parameters.

  6. Click on the PW Templates Binding Route Target tab and click Create. The PW Template Binding Route Target (Create) form opens.

    Note:

    This Import Route Target is used by the NE to decide which PW Template to use to create SDP bindings. If a far-end neighbor has a matching export target (that is, to the PW Template Import Target being defined here), then this PW Template is selected by the NE to create the pseudowire that is used to link both sites of the VPLS. If nothing is entered, and multiple PW Templates are defined, the first one found by the NE is used (most likely the one with the lowest PW Template Policy ID).

    Enter the required Import Route Target in the field and click OK. The PW Template Binding Route Target (Create) form closes and the entered Import Route Target is displayed in the table on the PW Template Binding Route Target tab.

  7. Click OK to accept the selection. The PW Template Binding (Create) form closes and the new PW Template Binding is displayed in the table on the PW Template Binding tab.

  8. Select the required entry or entries from the list.

16 

Save the changes and close the form.

17 

If you are configuring a BGP VPLS, go to Step 18 . Otherwise go to Step 21 .

18 

Enable the Enable BGP VPLS parameter.

19 

Configure the required BGP parameters.

20 

Select an operational group for the BGP site to monitor.

21 

To configure BGP AD, enable the Enable BGP AD parameter and configure the required BGP AD parameters.

Note: The Global Service VPLS ID is set to the value defined at the service level.

If VPLS ID is defined at the service level, then the NFM-P ensures that each site has the same VPLS ID. If a site has a different VPLS ID, an alarm is raised and the ID mismatch is indicated in the Status panel of the VPLS site properties form.

The same VPLS ID value is propagated to each site in a VPLS. If you change the VPLS ID of a site without using the NFM-P, the NFM-P displays a warning form.

22 

Save and close the forms.

End of steps