Configuring BGP4

•RFC 2842. This RFC specifies the Capability Advertisement, which a BGP4 router uses to dynamically negotiate a capability with a neighbor.

•RFC 2858 for Multi-protocol Extension.

NOTE: The HP implementation of dynamic route refresh supports negotiation of IP version 4 unicasts only.

•bgp-draft-route-refresh-1.txt, which describes the dynamic route refresh capability

The dynamic route refresh capability is enabled by default when you upgrade to software release 07.1.X and cannot be disabled. When the routing switch sends a BGP4 OPEN message to a neighbor, the routing switch includes a Capability Advertisement to inform the neighbor that the routing switch supports dynamic route refresh.

NOTE: The option for dynamically refreshing routes received from a neighbor requires the neighbor to support dynamic route refresh. If the neighbor does not support this feature, the option does not take effect and the software displays an error message. The option for dynamically re-advertising routes to a neighbor does not require the neighbor to support dynamic route refresh.

To use the dynamic refresh feature, use either of the following methods.

Dynamically Refreshing Routes

The following sections describe how to dynamically refresh BGP4 routes to place new or changed filters into effect.

USING THE CLI

To request a dynamic refresh of all routes from a neighbor, enter a command such as the following:

HP9300(config-bgp-router)# clear ip bgp neighbor 192.168.1.170 soft in

This command asks the neighbor to send its BGP4 table (Adj-RIB-Out) again. The routing switch applies its filters to the incoming routes and adds, modifies, or removes BGP4 routes as necessary.

Syntax: clear ip bgp neighbor all <ip-addr> <peer-group-name> <as-num> [soft-outbound soft [in out]]

The all <ip-addr> <peer-group-name> <as-num> specifies the neighbor. The <ip-addr> parameter specifies a neighbor by its IP interface with the routing switch. The <peer-group-name> specifies all neighbors in a specific peer group. The <as-num> parameter specifies all neighbors within the specified AS. The all parameter specifies all neighbors.

The soft-outboundparameter updates all outbound routes by applying the new or changed filters, but sends only the existing routes affected by the new or changed filters to the neighbor.

The soft [in out] parameter specifies whether you want to refresh the routes received from the neighbor or sent to the neighbor:

•soft in requests the neighbor’s entire BGP4 route table (Adj-RIB-Out), then applies the filters to add, change, or exclude routes.

•soft out updates all outbound routes, then sends the routing switch’s entire BGP4 route table (Adj-RIB-Out) to the neighbor, after changing or excluding the routes affected by the filters.

If you do not specify in or out, the routing switch performs both options.

NOTE: The soft-outboundparameter updates all outbound routes by applying the new or changed filters, but sends only the existing routes affected by the new or changed filters to the neighbor. The soft out parameter updates all outbound routes, then sends the routing switch’s entire BGP4 route table (Adj-RIB-Out) to the neighbor, after changing or excluding the routes affected by the filters. Use soft-outboundif only the outbound policy is changed.

To dynamically resend all the routing switch’s BGP4 routes to a neighbor, enter a command such as the following:

HP9300(config-bgp-router)# clear ip bgp neighbor 192.168.1.170 soft out

10 - 115