Effects of Changing Outbound Policies

After you change the outbound policy for a peer or peer group, the policy changes do not take effect until you issue either a hard clear or an outbound soft clear. (See Resetting a BGP Connection for information about performing clears with the clear ip bgp command.) The clear action causes BGP to reapply the outbound policy of the peer or peer group to each route in the BGP routing table. BGP then stores the results in the Adj-RIBs-Out table for that peer or peer group. The BGP session with each peer or peer group member takes the routes from the appropriate Adj-RIBs-Out table and sends them in update messages to the peer or peer group member.

Note: You cannot change outbound policy for an individual peer group member. You can change outbound policy only for a peer group as a whole or for peers that are not members of a peer group.

neighbor rib-out disable

• Use to disable storage of routes (disable rib-out) in the specified neighbor’s Adj-RIBs-Out table or in a single Adj-RIBs-Out table for the entire specified peer group.
• Route storage is disabled by default.
• If you enable storage for a peer, the peer’s Adj-RIBs-Out table contains all routes actually sent to the peer. By contrast, if you enable storage for a peer group, the peer group’s Adj-RIBs-Out table contains those routes that the BGP speaker intends to send to the peer group members; individual members might or might not have already received updates that advertise the routes.
• If you specify a BGP peer group by using the peerGroupName argument, a single Adj-RIBs-Out table is enabled for the entire peer group. You can override this configuration for a member of the peer group by issuing the command for that peer.
• Limit the number of Adj-RIBs-Out tables to no more than ten for peer groups to conserve memory resources. No limit applies to peers.
• This command takes effect immediately and automatically bounces the BGP session(s) if the command changes the current configuration.
• Example

  host1(config-router)#no neighbor 10.15.24.5 rib-out disable

• Use the no version to enable the route storage. Use the default version to remove the explicit configuration from the peer or peer group and reestablish inheritance of the feature configuration.
• See neighbor rib-out disable.

rib-out disable

• Use to disable storage of routes in the Adj-RIBs-Out tables (disable rib-out) for all BGP peers.
• Route storage is disabled by default.
• This command takes effect immediately and automatically bounces the BGP session if the command changes the current configuration.
• Example

  host1(config)#rib-out disable

• Use the no version to enable the route storage. Use the default version to remove the explicit global configuration from all peers and reestablish inheritance of the feature configuration.
• See rib-out disable.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.