To configure peer-level BGP

Note: For most parameters in this procedure, you can specify that the parameter value is inherited from the parent BGP configuration using the Inherit Value parameter.

If you disable value inheritance for a parameter, the available options are restricted, based on the parent parameter value and the protocol functionality. For example, if a parameter in the peer-group-level BGP configuration is set to True, the only available option for the same parameter in the peer-level BGP configuration is False, unless a value of False violates a protocol rule, in which case the only available option is True.

The parameters that you configure for a BGP peer take precedence over the parameters that are configured for group-level BGP.

Steps
 
1 

In the navigation tree Routing view, expand Network→NE→Routing Instance→BGP→Peer Group.

2 

Right-click on the Peer Group icon and choose Create Peer.

3 

Configure the general parameters.

4 

Select a TCP key chain in the KeyChain panel, if required.

Note: You can assign a TCP key chain to a BGP site, group, or peer on a 7450 ESS in mixed mode, 7705 SAR, 7750 SR, or 7950 XRS.

5 

Configure the required parameters in the Graceful Restart panel.

The graceful restart parameters are configurable when the Graceful Restart parameter is enabled.

6 

Configure the required parameters in the MED panel.

The MED parameters are used to find a way to leave the AS when there are multiple methods of leaving the AS.

7 

Click Apply.

8 

Configure the required parameters in the OLC panel.

9 

Click on the Behavior tab and configure the required parameters.

Note: The Fault Tolerance parameter allows BGP routers to be more tolerant of certain UPDATE message errors, use less disruptive error recovery mechanisms, and provide better operational and diagnostics information.

10 

Click on the AS Properties tab and configure the required parameters.

The Peer AS parameter specifies the peer AS for the group to which the peer belongs, and the behavior, internal or external. Multipath configurations are not supported at the BGP peer level.

11 

Configure the required parameters in the Local AS and Remove Private AS panels.

The No Prepend Global AS parameter is configurable when you set the Local AS parameter to a value other than 0.

12 

Click on the VPN tab and configure the required parameters.

Note the following:

  • To enable VPN IPv6, select VPN IPv6 and IPv6 for the Family parameter.

  • To enable VPN IPv6, select IPv6 for the Advertise Label parameter.

  • The Advertise LDP Prefix and Use Service Routes parameters are configurable when the Advertise Label parameter is enabled for IPv4 routes.

  • The Apply Import Route Policies and Apply Export Route Policies parameters specify whether to apply the existing import and export route policies configured on the Import Policies and Export Policies tabs.

  • Selecting an address family in the Rapid Update panel reduces the minimum route advertisement interval (MRAI) to zero. Families that are not selected will retain the default MRAI.

13 

Click on the ORF Extended Community tab and perform the following:

  1. Configure the Accept ORF parameter.

  2. Configure the Send ORF parameter.

    If Send ORF is set to True, provide the RTL details:

    1. Click on the Create button.

    2. Enter site and route target details.

    3. Click OK.

14 

Click on the Add Path tab and configure the required parameters.

You must select the Enable Add-Path parameter in order to configure the additional Add-Path parameters.

IMPORTANT INFORMATION

For release 22.2 and later, the modification of parameters under Add Path will still work with pre 22.2 OSSI scripts. However, to enable or disable Add-Path parameter using pre 22.2 OSSI scripts, the following workaround is mandatory;

  • To disable AddPath, specify <sendAddPath>false</sendAddPath> along with the <paramsInheritanceMask> tag with all AddPath bits removed.

  • To enable AddPath, specify <sendAddPath>true</sendAddPath> along with the <paramsInheritanceMask> tag with AddPath bits specified.

Note: It is recommended to use either pre-22.2 and 22.2 OSSI script consistently for Add-Path Configuration and do not alternate.

Note: The inheritance from parent BGP configuration applies to all the parameters.

The inheritance values are displayed as read-only fields for operational setup. For non-operational setup, inheritance values are not displayed.

15 

To configure prefix limits, perform the following steps:

  1. Click on the Prefix Limit tab.

    Note:

    For node releases earlier than 13.0R1, prefix limit parameters appear on the Behavior tab and the Prefix Limit tab is not available.

  2. Click Create. The Prefix Limit (Create) form opens.

  3. Configure the required parameters.

  4. Save your changes and close the form.

16 

Click on the Import Policies and Export Policies tabs and configure the required parameters.

Configure the import route policies to determine which routes are accepted from peers. The policies should match the policies you configure using the Routing Policy Manager, as described in Chapter 27, NE routing and forwarding . There is no validation performed by the router to ensure the policies match.

Configure the export route policies to determine which routes are advertised to peers. The policies should match the policies you configure using the Routing Policy Manager, as described in Chapter 27, NE routing and forwarding . A router performs no validation to ensure the policies match.

You can use the Select button to choose a single policy, or click on the Create Expression button to use a logical expression, as described in To create a BGP policy expression.

17 

Click on the Segment Routing V6 tab and configure the required parameters.

18 

Click on the Authentication tab and configure the required parameters.

19 

Save the changes and close the form.

20 

Configure the protocol for the far-end device, if applicable. Use CLI for devices that are managed outside the scope of the NFM-P.

End of steps