Table of Contents
Advertisement
Table 4: Default Route Preferences
enable — Static routes can be administratively enabled or disabled. Use the enable parameter to re-
disable — Static routes can be administratively enabled or disabled. Use the disable parameter to
bfd-enable — ssociates the state of the static route to a BFD session between the local system and the
mcast-family — Enables submission of the IPv4 or IPv6 static route into IPv4 or IPv6 multicast
rsvp-te — This parameter allows the static route to be resolved via an RSVP-TE based LSP. The
cpe-check target-ip-address — This parameter specifies the IP address of the target CPE device.
7710 SR OS Router Configuration Guide
Route Type
IS-IS level 1 internal
IS-IS level 2 internal
OSPF External
IS-IS level 1 external
IS-IS level 2 external
BGP
Default
5
Values
1 — 255
enable a disabled static route. In order to enable a static route, it must be uniquely identified by
the IP address, mask, and any other parameter that is required to identify the exact static route.
The administrative state is maintained in the configuration file.
Default
enable
disable a static route while maintaining the static route in the configuration. In order to enable a
static route, it must be uniquely identified by the IP address, mask, and any other parameter that
is required to identify the exact static route.
The administrative state is maintained in the configuration file.
Default
enable
configured nexthop. This keyword cannot be configured if the nexthop is indirect or blackhole
keywords are specified.
RTM.
Values
mcast-ipv4, mcast-ipv6
static route nexthop will be resolved via the best RSVP-TE based LSP to the associated indirect
next hop. By default, if an RSVP-TE LSP is not available, the IGP route table will be used to
resolve the associated nexthop. If the keyword "disallow-igp" is configured, the associated static
route will not be resolved through the IPv4 route table if an RSVP-TE based LSP is not available.
ICMP pings will be sent to this target IP address. This parameter must be configured to enable
the CPE connectivity feature for the associated static route. The target-ip-address cannot be in the
same subnet as the static route subnet itself to avoid possible circular references. This option is
mutually exclusive with BFD support on a given static route.
Preference
Configurable
15
Yes
18
Yes
150
Yes
160
Yes
165
Yes
170
Yes
IP Router Configuration
Page 97
Advertisement
Table of Contents
