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:
|
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:
|
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:
|
13 |
Click on the PW Template Binding tab and perform one of the following:
|
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:
|
22 |
Save the changes and close the forms. End of steps |