Specifications

Page 99 /148
allow the selection of the nexthop LSP based on route attributes like
community and as-path. This feature gives the user the flexibility to choose
the forwarding nexthop via policy.
Junos is providing the user with tools to control which one amongst a set of
equal cost nexthops gets installed in the forwarding table. If the desired
nexthop LSP is not a viable nexthop for the route Junos falls back to
choosing randomly from the ones that are available.
§ BGP route refresh
BGP route refresh enables you to dynamically request readvertisement of
routes from a peer. When the parameter ‘keep none” is configured for the
BGP session and the inbound policy changes, JUNOS forces
readvertisement of the full set of routes advertised by the peer. Route refresh
is supported :
o for all BGP,
o for all peers in a group,
o or for an individual peer.
A Route-REFRESH message is sent to peer. The peer will then re-advertise
the Adj-RIB-Out to the local router.
Route Refresh uses BGP capability negotiation when initially setting up the
bgp session, using capability code 2 (128 is sent as well for interoperability).
It conforms to the ietf draft draft-ietf-idr-bgp-route-refresh-01.txt.