To configure BGP on a VPRN routing instance
Steps
1 |
Choose Manage→Service→Services from the NFM-P main menu. The Manage Services form opens. |
2 |
Choose a VPRN service and click Properties. The VPRN Service (Edit) form opens. |
3 |
On the service navigation tree, expand Sites→Routing Instance, right-click on the site on which you need to configure BGP and choose Properties. The VPRN Site (Edit) form opens. |
4 |
Click on the Routing tab. |
5 |
Enable the BGP Enabled parameter on the Protocols tab. A list of BGP routing instances appears. |
6 |
Select a routing instance and click Properties. The BGP Site, routing instance (Create) form opens. |
7 |
Configure the required parameters. |
8 |
To assign a TCP key chain, select a TCP key chain in the KeyChain panel. 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 a 7950 XRS. |
9 |
Configure the parameters in the Graceful Restart panel. The graceful restart parameters are configurable when you enable the Graceful Restart parameter. |
10 |
Configure the parameters in the MED panel. These parameters are used to find a way to leave the AS when there are multiple methods of leaving the AS. |
11 |
Configure the parameters in the MultiPath panel. Set the Multi Path parameter to 1 to disable. When set from 2 to 16, multipath is enabled and BGP load shares traffic across the number of links specified. If the equal cost routes available are greater than the configured value, then routes with the lowest next hop IP address are chosen. |
12 |
Configure the EIBGP Load Balance parameter in the EIBGP LoadBalance panel. |
13 |
Configure the Backup Path parameter in the Backup Path panel. |
14 |
Configure the parameters in the Best Path Selection panel. When you set the MED Compare parameter to off, the Strict parameter is set to true and is not configurable. When you set the MED Compare parameter to on, the Strict parameter is set to false and is not configurable. |
15 |
Click on the Behavior tab and configure the required parameters. |
16 |
Configure the parameters in the Hold Time panel. |
17 |
Configure the Fault Tolerance parameter in the Error Handling panel. The Fault Tolerance parameter allows BGP routers to be more tolerant of some Update message errors, use less disruptive error recovery mechanisms, and provide better operational and diagnostics information. |
18 |
Configure the parameters in the Damp Peer Oscillations panel. |
19 |
Click on the AS Properties tab and configure the Disable 4Byte ASN parameter. |
20 |
Configure the parameters in the Local AS panel. The No Prepend Global AS is configurable only if you set the Local AS parameter to a value other than 0. The Local AS parameters are used to configure a virtual AS. A virtual AS is used when a router (RTA) is moved from one AS (AS1) to another AS (AS2). However, the customer router (CR1) is configured to belong to the AS1. To avoid reconfiguring CR1 to belong to AS2, CR1 can continue to belong to AS1, but RTA has its local AS value set to AS1. RTA can advertise AS1 for routes advertised to CR1. |
21 |
Configure the parameters in the Remove Private AS panel. |
22 |
Click on the VPN tab and configure the required parameters. Note: 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. |
23 |
To add a group:
|
24 |
To add a peer:
|
25 |
Click on the Next-Hop Resolution tab and configure the Policy parameter. Configure the parameters in the Use Leaked Routes panel. |
26 |
Click on the Import Policies tab and configure the required parameters. Configure the import route policies to determine which routes are accepted from peers. These policies should match the policies you configure using the Routing Policy Manager, as described in Chapter 27, NE routing and forwarding . The router does not validate to ensure that the policies match. |
27 |
Click on the Export Policies tab and configure the required parameters. Configure the export route policies to determine which routes are advertised to peers. These policies should match the policies you configure using the Routing Policy Manager, as described in Chapter 27, NE routing and forwarding . The router does not validate to ensure that the policies match. |
28 |
Click on the RIB Management tab to assign leak import and export policies:
|
29 |
To configure interface instance, perform the following steps:
|
30 |
Click on the Authentication tab and configure the required parameters. |
31 |
Save the changes and close the forms. End of steps |