IP Router Configuration Command Reference
136 Router Configuration Guide
When the next-hop is reachable again and present in the ARP/Neighbor Cache, the static route will be
considered valid and is subject to being placed into the active route-table.
Default no validate-next-hop
disallow-igp
Syntax disallow-igp
no disallow-igp
Context config>router>static-route-entry>tunnel-next-hop
Description This command is for indirect static routes using tunnel next-hops. When enabled, the static route will
not be activated using IGP next-hops in RTM if no tunnel next-hops are found in TTM.
triggered-policy
Syntax triggered-policy
no triggered-policy
Context config>router
Description This command triggers route policy re-evaluation.
By default, when a change is made to a policy in the config router policy options context and then
committed, the change is effective immediately. There may be circumstances when the changes should
or must be delayed; for example, if a policy change is implemented that would affect every BGP peer
on a router, the consequences could be dramatic. It would be more effective to control changes on a
peer-by-peer basis.
If the triggered-policy command is enabled, and a given peer is established, and you want the peer to
remain up, in order for a change to a route policy to take effect, a clear command with the soft or soft
inbound option must be used; for example, clear router bgp neighbor x.x.x.x soft. This keeps the peer
up, and the change made to a route policy is applied only to that peer or group of peers.
ttl-propagate
Syntax ttl-propagate
Context config>router
Description This command enables the context to configure TTL propagation for transit and locally generated
packets in the Global Routing Table (GRT) and VPRN routing contexts
Default none
To Next Page
Loading...
