To configure a site for BGP VPLS Multi-homing

Purpose

This procedure provides the steps required to configure a site for BGP VPLS Multi-homing. BGP VPLS Multi-homing provides redundancy support through the configuration of a number of multi-homed sites, rather than through the use of MC-LAG or MC-Ring as access mechanisms. Dual-homing between a CE device and a pair of VPLS PE devices (potentially in different autonomous systems) is an example of such a configuration.

Note: VPLS sites, I-sites, and B-Sites can be configured for BGP VPLS Multi-homing. However, the B-Sites cannot be used as a backbone for an Epipe.

MVPLS services cannot be configured for this application.

An RD or RT configured under the BGP of a VPLS site cannot be removed as long as there is a multi-homing site ID configured whose administration state is up.

You can see a list of all current BGP VPLS Multi-homing sites in a multi-homing VPLS service by viewing the BGP Multi-homing Sites tab on the service configuration form.

Steps
 
1 

Prior to configuring a site for BGP VPLS Multi-homing, 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 for more information. 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:

    • Enable the L2 VPN parameter 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.

    Note: For optimal processing while a BGP multi-homing site is activated or de-activated, or the system is rebooted, you should also:

    • Enable the L2 VPN parameter in the Rapid Update Address Family panel on the BGP site VPN tab.

    • Enable the Enable Rapid Withdrawal parameter on the BGP site Behavior tab.

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

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

  6. Create SDPs for the BGP VPLS Multi-homing site(s), if manually-provisioned service tunnels are required. See To create an IP/MPLS service tunnel

2 

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

3 

Choose the required VPLS or HVPLS 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 VPLS multi-homing.

5 

Click on the BGP tab.

6 

Enable the Enable BGP parameter.

7 

Configure the Route Distinguisher parameter.

8 

Click Configuration to configure the Route Targets and the PW Templates. The BGP Configuration form opens.

9 

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

10 

Perform one of the following:

  1. Enter the Import Route Target name manually. The format must 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.

11 

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

12 

Perform one of the following:

  1. Enter the Export Route Target name manually. 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.

13 

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

  1. Select an existing PW Template Binding.

  2. Create a new PW Template Binding.

    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. Click on the PW Templates Binding Route Target tab and click Create. The PW Template Binding Route Target (Create) form is displayed.

      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.

    5. Click OK to accept the selection.

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

14 

Save the changes and close the form.

15 

Click on the Multi-homing tab and click Create. The BGP Multi-homing Site (Create) form opens.

16 

Configure the required parameters in the Service Panel.

You cannot turn up a BGP multi-homing site without specifying a Multi-homing ID. In addition, the Multi-homing ID of the site can only be removed at a later time when the site is shutdown.

17 

Select a SAP, Spoke SDP, Split Horizon Group, or Mesh SDP Binding, based on the option you selected for the Enable Multi-homing to parameter.

You cannot turn up a BGP multi-homing site without specifying a SAP. The SAP configured under this site can be part of an endpoint, but the only other object allowed in the endpoint is an ICB spoke-SDP. In addition, an assigned SAP can only be removed at a later time when the BGP multi-homing site is shutdown.

18 

Configure the required parameters in the Timer panel.

If you enable either the Use Node Level Boot Timer and/or Use Node Level Site Activation Timer parameters, then the associated Boot Timer (seconds) and/or Activation Timer (seconds) parameters are not configurable. These parameter values are inherited from the network element configuration.

The Boot Timer (seconds) and Activation Timer (seconds) parameters can be configured for an NE on the BGP Multi-homing sub-tab under the Redundancy tab in the Network Element (Edit) form. See To modify NE properties for more information about how to change device properties.

If you enable the Use Node Level Site-Down Minimum Timer parameter, the Site-Down Minimum Timer (seconds) parameter and Site-Down Minimum Timer Remaining (seconds) parameters are ignored and the values configured on the NE are used.

19 

Select a Monitored Group Name.

20 

Save the changes and close the form.

21 

Check the following indicators:

  • Operational State: indicates the operational status of the multi-homing site.

  • Designated Forwarder: indicates whether this site has been declared as designated forwarder, depending on the result of the BGP election.

22 

Save the changes and close the forms.

End of steps