Route Refresh - Juniper JUNOSE 11.2.X BGP AND MPLS Configuration Manual

JunosE 11.2.x BGP and MPLS Configuration Guide
neighbor capability
130
On PE2, which is the helper router, use the bgp graceful-restart stalepaths-time
3.
command in Router Configuration mode to set the maximum time BGP waits to
receive an End-of-RIB marker from any restarted peer before flushing all remaining
stale routes from that peer as 3600 seconds.
host1(config-router)#bgp graceful-restart stalepaths-time 3600

Route Refresh

If the router detects that a peer supports both Cisco-proprietary and standard route
refresh messages, it uses the standard route refresh messages.
Use to control the advertisement of BGP capabilities to peers. Capability negotiation
and advertisement of all capabilities are enabled by default.
You can specify the deprecated-dynamic-capability-negotiation,
dynamic-capability-negotiation, four-octet-as-numbers, orf, route-refresh, and
route-refresh-cisco capabilities. The graceful restart capability is controlled by specific
graceful-restart commands.
If you specify a BGP peer group by using the peerGroupName argument, all the members
of the peer group inherit the characteristic configured with this command unless it is
overridden for a specific peer.
You cannot configure the receive direction for the orf capability for a peer that is a
member of a peer group or for a peer.
If you issue the route-refresh or route-refresh-cisco keywords, the command takes
effect immediately. If dynamic capability negotiation was negotiated for the session,
a capability message is sent to inform the peer of the new capability configuration. If
dynamic capability negotiation was not negotiated for the session, the session is
bounced automatically.
If you issue the deprecated-dynamic-capability-negotiation,
dynamic-capability-negotiation, four-octet-as-numbers, negotiation, or orf keywords,
the command takes effect immediately and bounces the session.
If the BGP speaker receives a capability message for a capability that BGP did not
previously advertise in the dynamic capability negotiation capability, BGP sends a
notification to the peer with the error code " capability message error" and error subcode
" unsupported capability code."
IPv6 ORF prefix lists are not supported. Therefore you can specify an IPv6 address with
the orf keyword only within the IPv4 address family and when you want to advertise
IPv4 routes to IPv6 peers.
Example
host1(config-router)#neighbor 10.6.2.5 capability orf prefix-list both
Use the no version to prevent advertisement of the specified capability or use the
negotiation keyword with the no version to prevent all capability negotiation with the
specified peer. Use the default version to restore the default, advertising the capability.
See neighbor capability.
Copyright © 2010, Juniper Networks, Inc.