IP Router Configuration
Router Configuration Guide 205
The user can select if link protection or node protection is preferred in the selection of an LFA next-
hop for all IP prefixes and LDP FEC prefixes to which a route next-hop policy template is applied. The
default in SR OS implementation is node protection. The implementation will fall back to the other
type if no LFA next-hop of the preferred type is found.
When the route next-hop policy template is applied to an IP interface, all prefixes using this interface
as a primary next-hop will follow the protection type preference specified in the template.
The no form deletes the protection type constraint from the route next-hop policy template.
Parameters {link | node} — Specifies the two possible values for the protection type.
Default node
nh-type
Syntax nh-type {ip | tunnel}
no nh-type
Context config>router>route-next-hop-policy>template
Description This command configures the next-hop type constraint into the route next-hop policy template.
The user can select if tunnel backup next-hop or IP backup next-hop is preferred. The default in SR
OS implementation is to prefer IP next-hop over tunnel next-hop. The implementation will fall back
to the other type if no LFA next-hop of the preferred type is found.
When the route next-hop policy template is applied to an IP interface, all prefixes using this interface
as a primary next-hop will follow the next-hop type preference specified in the template.
The no form deletes the next-hop type constraint from the route next-hop policy template.
Parameters {ip | tunnel} — Specifies the two possible values for the next-hop type.
Default ip
mh-secondary-interface
Syntax [no] mh-secondary-interface
Context config>router
Description This command creates a loopback interface for use in multihoming resiliency. This address is
considered the secondary multihoming address and is only used to resolve routes advertised by the
primary router in the event that router becomes unavailable. For this purpose, the reachability for this
address is advertised via IGPs and LDP protocols to allow the resolution of BGP routes advertised with
this address by the primary multihoming router.
The no form of the command disables this setting.
To Next Page
Loading...
