router
config
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure router parameters and interfaces.
allow-icmp-redirect
no allow-icmp-redirect
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command enables or disables ICMP redirects received on the management interface.
The no form of this command disables ICMP redirects.
no allow-icmp-redirect
allow-icmp6-redirect
no allow-icmp6-redirect
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command enables or disables IPv6 ICMP redirects received on the management interface.
The no form of this command disables IPv6 ICMP redirects.
no allow-icmp6-redirect
autonomous-system autonomous-system
no autonomous-system
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the autonomous system (AS) number for the router. A router can only belong to one AS. An AS number is a globally unique number with an AS. This number is used to exchange exterior routing information with neighboring ASs and as an identifier of the AS itself.
If the AS number is changed on a router with an active BGP instance, the new AS number is not used until the BGP instance is restarted either by administratively disabling or enabling (shutdown or no shutdown) the BGP instance or rebooting the system with the new configuration.
Specifies the autonomous system number expressed as a decimal integer.
ecmp max-ecmp-routes
no ecmp
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command enables ECMP and configures the number of routes for path sharing. For example, a value of 2 means two equal-cost routes are used for cost sharing.
ECMP can only be used for routes learned with the same preference and same protocol. When more ECMP routes are available at the best preference than configured in max-ecmp-routes, the lowest next-hop IP address algorithm is used to select the number of routes configured in max-ecmp-routes.
The no form of this command disables ECMP path sharing. If ECMP is disabled, and multiple routes are available at the best preference and equal cost, route selection is as follows:
IGP selects the next-hop based on the lowest router ID
static-route chooses the next-hop based on lowest next-hop IP address
no ecmp
Specifies the maximum number of equal cost routes allowed on this routing table instance, expressed as a decimal integer. Setting ECMP max-ecmp-routes to 1 yields the same result as entering no ecmp.
mpls-labels
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Commands in this context configure global parameters related to MPLS labels.
static-label-range static-range
no static-label-range
config>router>mpls-labels
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the range of MPLS static label values shared among static LSP, MPLS-TP LSP, and static service VC labels. When this range is configured, it is reserved and cannot be used by other protocols such as RSVP, LDP, BGP, or segment routing to assign a label dynamically.
The no form of this command reverts to the default value.
18400
Specifies the size of the static label range in number of labels. The minimum label value in the range is 32. The maximum label value is computed as {32+ static-range-1}.
sr-labels start start-value end end-value
no sr-labels
config>router>mpls-labels
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the range of the segment routing global block (SRGB). It is a label block that is used for assigning labels to SR prefix SIDs originated by the router. The range is carved from the system dynamic label range and is not instantiated by default.
This is a reserved label and when configured it cannot be used by other protocols such as RSVP, LDP, and BGP to assign a label dynamically.
The no form of this command reverts to the default value.
no sr-labels
Specifies the start label value in the SRGB.
Specifies the end label value in the SRGB.
router-id ip-address
no router-id
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the router ID for the router instance.
The router ID is used by both OSPF and BGP routing protocols in this instance of the routing table manager. IS-IS uses the router ID value as its system ID.
When configuring a new router ID, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized, the new router ID is used. This can result in an interim period of time when different protocols use different router IDs.
To force the new router ID to be used, issue the shutdown and no shutdown commands for each protocol that uses the router ID, or restart the entire router.
The no form of this command to reverts to the default value.
The system uses the system interface address (which is also the loopback address)
If a system interface address is not configured, use the last 32 bits of the chassis MAC address.
Specifies the 32-bit router ID expressed in dotted decimal notation or as a decimal value.
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [enable | disable] next-hop ip-address
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [enable | disable] black-hole
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] next-hop ip-int-name | ip-address [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}] [description description]
config>router
7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
This command creates static route entries for both the network and access routes.
When configuring a static route, either next-hop or black-hole must be configured.
If a CPE connectivity check target address is already being used as the target address in a different static route, the cpe-check parameters must match. If they do not, the new configuration command is rejected.
If a static-route command is issued with no cpe-check target but the destination prefix/netmask and next-hop match a static route that did have an associated cpe-check, the cpe-check test is removed from the associated static route.
The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.
Specifies the destination address of the static route.
Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Specifies the subnet mask in dotted decimal notation.
Specifies the prefix-list to be considered.
Specifies the preference of this static route versus the routes from different sources, such as BGP or OSPF, expressed as a decimal integer. When modifying the preference of an existing static route, the metric is not changed unless specified.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is according to the route preference defaults listed in Table: Default route preferences.
If multiple routes are learned with an identical preference using the same protocol, the lowest- cost route is used. If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the route to use is determined by the next-hop with the lowest address.
Specifies the cost metric for the static route, expressed as a decimal integer. When modifying the metric of an existing static route, the preference does not change unless specified. This value also determines which static route to install in the forwarding table.
If there are multiple routes with different preferences, the lower preference route is installed. If there are multiple static routes with the same preference but different metrics, the lower cost (metric) route is installed. If there are multiple static routes with the same preference and metric, the route with the lowest next-hop IP address is installed.
Specifies that the route is a blackhole route. If the destination address on a packet matches this static route, it is silently discarded.
The black-hole and next-hop keyword are mutually exclusive. If an identical command is entered (with the exception of the next-hop keyword), this static route is replaced with the newly entered command and, unless specified, the respective defaults for preference and metric is applied.
Specifies the directly connected next hop IP address used to reach the destination.
The next-hop and black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of the black-hole keyword), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric is applied.
The ip-address configured here can be either on the network side or the access side on this node. This address must be associated with a network directly connected to a network configured on this node.
Static routes can be administratively enabled or disabled. The enable parameter reenables a disabled static route. 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.
Static routes can be administratively enabled or disabled. The disable parameter disables a static route while maintaining the static route in the configuration. 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.
Specifies the IP address of the target CPE device. ICMP pings are sent to this target IP address. This parameter must be configured to enable CPE connectivity for the associated static route. To avoid possible circular references, the target IP address cannot be in the same subnet as the static route subnet.
Specifies the interval between ICMP pings to the target IP address, in seconds.
Specifies the number of consecutive ping replies that must be missed to declare the CPE down and to deactivate the associated static route.
Sets the ability to log transitions between active and inactive based on the CPE connectivity check. Events should be sent to the system log, syslog, and SNMP traps.
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] next-hop ip-int-name | ip-address [bfd-enable | {cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}]] [ldp-sync] [description description]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] indirect ip-address [mcast-family] [community comm-id] [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}] [description description]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] black-hole] [prefix-list prefix-list-name [all | none]] [description description]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} black-hole [preference preference] [metric metric] [tag tag] [enable | disable] [description description]
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command creates static route entries for both the network and access routes. When configuring a static route, the next-hop, indirect, or black-hole parameter, indicating the type of static route, must be configured. Multiple types of static routes (next-hop, indirect, black-hole) can be applied to the same IP prefix. If a static route that is forwarding traffic goes down, the default route is used instead. The preference parameter is used to specify the order in which the routes are applied. If a blackhole static route has the same preference as another route with the same prefix, the blackhole route takes a lower precedence.
If a CPE connectivity check target address is already being used as the target address in a different static route, the cpe-check parameters must match. If they do not, the new configuration command is rejected.
If a static-route command is issued with no cpe-check target, but the destination prefix/netmask and next hop matches a static route that did have an associated CPE check, the cpe-check test is removed from the associated static route.
The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.
no static-route
Specifies the destination address of the static route.
Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Specifies the subnet mask in dotted decimal notation.
Specifies the prefix-list to be considered.
Specifies the preference of this static route versus the routes from different sources such as OSPF, IS-IS, or BGP expressed as a decimal integer. When modifying the preference of an existing static route, the metric is not changed unless specified.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is according to the route preference defaults listed in the following table.
Route type |
Preference |
Configurable |
|---|---|---|
Direct attached |
0 |
No |
Static-route |
5 |
Yes |
OSPF Internal routes |
10 |
Yes |
IS-IS level 1 internal |
15 |
Yes |
IS-IS level 2 internal |
18 |
Yes |
OSPF External |
150 |
Yes |
IS-IS level 1 external |
160 |
Yes |
IS-IS level 2 external |
165 |
Yes |
If multiple routes are learned with an identical preference using the same protocol, the lowest- cost route is used. If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the route to use is determined by the next hop with the lowest address.
Specifies the cost metric for the static route, expressed as a decimal integer. When modifying the metric of an existing static route, the preference does not change unless specified. This value is also used to determine which static route to install in the forwarding table.
If there are multiple routes with different preferences, the lower preference route is installed. If there are multiple static routes with the same preference but different metrics, the lower cost (metric) route is installed. If there are multiple static routes with the same preference and metric, the route with the lowest next-hop IP address is installed.
Specifies that the route is a blackhole route. If the destination address on a packet matches this static route, it is silently discarded.
The black-hole and next-hop keyword are mutually exclusive. If an identical command is entered (with the exception of the next-hop keyword), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric are applied.
Specifies the directly connected next-hop interface name or IP address used to reach the destination. If the next hop is over an unnumbered interface, the ip-int-name of the unnumbered interface (on this node) can be configured.
The next-hop and black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of the black-hole keyword), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric is applied.
The ip-int-name is the interface name of the next hop. Interface names must be unique within the group of defined IP interfaces for config router interface commands. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The ip-address configured for the next-hop parameter can be either on the network side or the access side on this node. This address must be associated with a network that is directly connected to a network configured on this node.
Specifies a 32-bit integer tag to be added to the static route. The tag is used in route policies to control distribution of the route into other protocols.
Specifies that a disabled static route will be reenabled. 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.
Specifies that the static route will be disabled while maintaining the static route in the configuration. 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.
Specifies that the route is indirect and specifies the next-hop IP address used to reach the destination. The configured IP address is not directly connected to a network configured on this node. The destination can be reachable via multiple paths. The indirect address can be resolved either via a dynamic routing protocol or by another static route.
If a static route is configured with the same destination address, subnet mask, and indirect next-hop IP address as a previously configured static route, the newly configured route replaces the previous one, and unless specified, the respective defaults for preference and metric will be applied. The IP address configured for the indirect keyword must be on the network side of this node and be at least one hop away from the node.
Specifies that the state of the static route is associated with a BFD session between the local system and the configured next hop. This keyword cannot be configured if the next hop is configured as indirect or black-hole. For more information about the protocols and platforms that support BFD, see the BFD section in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
Specifies the IP address of the target CPE device. ICMP pings are sent to this target IP address. This parameter must be configured to enable CPE connectivity for the associated static route. To avoid possible circular references, the target IP address cannot be in the same subnet as the static route subnet. This parameter option and BFD support are mutually exclusive on a specific static route.
Specifies the interval between ICMP pings to the target IP address, in seconds.
Specifies the number of consecutive ping replies that must be missed to declare the CPE down and to deactivate the associated static route.
Specifies that the LDP synchronization feature is extended to a static route. When an interface comes back up after a failure, it is possible that a preferred static route, using the interface as the next hop for a specific prefix, is enabled before the LDP adjacency to the peer LSR comes up on this interface. When this happens, traffic on an SDP that uses the static route for the far-end address is blackholed until the LDP session comes up and the FECs exchanged. When LDP synchronization is enabled, activation of the static route is delayed until the LDP session comes up over the interface and the ldp-sync-timer configured on that interface has expired (see ldp-sync-timer).
Sets the ability to log transitions between active and in-active based on the CPE connectivity check. Events should be sent to the system log, syslog, and SNMP traps.
triggered-policy
no triggered-policy
config>router
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command triggers route policy reevaluation.
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 7210 SAS Mrouter, 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 specific 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.