router
config
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure router parameters, and interfaces.
aggregate ip-prefix/ip-prefix-length [summary-only] blackhole
no aggregate ip-prefix/ip-prefix-length
config>router
Supported on all 7210 SAS platforms as described in this document
This command creates an aggregate route.
Use this command to group a number of routes with common prefixes into a single entry in the routing table. This reduces the number of routes that need to be advertised by this router and reduces the number of routes in the routing tables of downstream routers.
Both the original components and the aggregated route (source protocol aggregate) are offered to the Routing Table Manager (RTM). Subsequent policies can be configured to assign protocol-specific characteristics (BGP, IS-IS or OSPF), such as the route type or OSPF tag to aggregate routes.
Multiple entries with the same prefix but a different mask can be configured; for example, routes are aggregated to the longest mask. If one aggregate is configured as 10.0./16 and another as 10.0.0./24, then route 10.0.128/17 would be aggregated into 10.0/16, and route 10.0.0.128/25 would be aggregated into 10.0.0/24. If multiple entries are made with the same prefix and the same mask, the previous entry is overwritten.
The no form of this command removes the aggregate.
Specifies the destination address of the aggregate route, in dotted-decimal notation.
Specifies the mask associated with the network address expressed as a mask length.
Specifies an optional parameter that suppresses advertisement of more specific component routes for the aggregate.
To remove the summary-only option, enter the same aggregate command without the summary-only parameter.
Specifies that the route is a blackhole route. If the destination address on a packet matches this static route, it will be silently discarded.
autonomous-system autonomous-system
no autonomous-system
config>router
Supported on all 7210 SAS platforms as described in this document
This command configures the autonomous system (AS) number for the router. A router can only belong to one AS. An ASN 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.
If the ASN is changed on a router with an active BGP instance, the new ASN is not used until the BGP instance is restarted either by administratively disabling/enabling (shutdown/no shutdown) the BGP instance or rebooting the system with the new configuration.
Specifies the autonomous system number expressed as a decimal integer.
cflowd-parameters
config>router>interface
7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)
Commands in this context configure traffic sampling for the interface.
sampling {unicast|multicast} type {interface}[direction {ingress-only}]
no sampling {unicast|multicast}
config>router>interface>cflowd-parameters
7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)
This command enables traffic sampling for the interface. See Configuration notes for more information.
The no form of this command disables traffic sampling for the interface.
no sampling
Keyword to enable unicast sampling.
Keyword to enable multicast sampling.
Keyword to configure the cflowd sampling type.
Keyword to configure interface cflowd sampling type.
keyword to configure the direction of the cflowd analysis.
Keyword to configure the ingress direction only for cflowd analysis.
ecmp max-ecmp-routes
no ecmp
config>router
Supported on all 7210 SAS platforms as described in this document
This command enables ECMP and configures the number of routes for path sharing; for example, the value 2 means two equal cost routes will be used for cost sharing. ECMP can only be used for routes learned with the same preference and same protocol. See the description on preferences in the static-route command. When more ECMP routes are available at the best preference than configured in max-ecmp-routes, then the lowest next-hop IP address algorithm is used to select the number of routes configured in max-ecmp-routes.
For the 7210 SAS-T (network mode), 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, and 7210 SAS-Mxp: Before enabling ECMP, user must allocate appropriate amount of resources using the command configure>system>resource-profile>router>ecmp>max-ecmp-routes. The value specified with this command must be less than or equal to the value specified with the command configure>system>resource-profile>router>ecmp> max-ecmp-routes. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.
For 7210 SAS-R6 and 7210 SAS-R12: Before enabling ECMP, user must allocate appropriate amount of resources using the configure>system>global-resource-profile>router>ecmp>max-ecmp-routes command The value specified with this command must be less than or equal to the value specified with the configure>system>global-resource-profile>router>ecmp>max-ecmp-routes command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.
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, then IGP chooses the next-hop based on lowest router-ID while static-route chooses the next-hop based on lowest next-hop ip address.
For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide.
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 one yields the same result as entering no ecmp.
mpls-labels
config>router
7210 SAS-Mxp
Commands in this context configure global parameters related to MPLS labels.
N/A
static-label-range static-range
no static-label-range
config>router>mpls-labels
7210 SAS-Mxp
This command configures the range of MPLS static label values shared among static LSP, MPLS-TP LSP, and static service VC label. Once 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.
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 thus computed as {32+ static-range-1}.
sr-labels start start-value end end-value
no sr-labels
config>router>mpls-labels
7210 SAS-Mxp
This command configures the range of the segment routing global block (SRGB). It is a label block which is used for assigning labels to segment routing prefix SIDs originated by this router. This range is carved from the system dynamic label range and is not instantiated by default.
This is a reserved label and once configured it cannot be used by other protocols such as RSVP, LDP, and BGP to assign a label dynamically.
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
Supported on all 7210 SAS platforms as described in this document
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.
system interface address (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] [tag tag] [enable | disable] next-hop gateway [bfd-enable] [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]}] [ldp-sync]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] indirect ip-address [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]}]
[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] [enable | disable] indirect ip-address {prefix-list prefixlist-name [all | none]}
[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 {prefix-list prefix-list-name [all | none]}
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] black-hole {prefix-list prefix-listname [all | none]}
config>router
Supported on all 7210 SAS platforms as described in this document
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 to indicate the type of static route. Different types of static routes can be applied to the same IP prefix. If a static route that is forwarding traffic goes down, the default route will be 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 reference 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, then cpe-check parameters must match. If they do not, the new configuration command will be rejected.
If a static-route command is issued with no cpe-check target but the destination prefix/netmask and next hop address matches a static route that did have an associated cpe-check, the cpe-check test will be 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 as necessary to uniquely identify the static route must be entered.
Specifies the destination address of the aggregate route in dotted-decimal notation.
Specifies the mask associated with the network address expressed as a mask length.
Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that will be 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 will not be changed unless specified. This parameter is also used to prioritize static routes applied to the same prefix. If a blackhole static route has the same preference as another route with the same prefix, the blackhole route takes a lower precedence. 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 |
BGP |
170 |
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 will not change unless specified. This value is also used to determine which static route to install in the forwarding table:
If there are multiple static routes with the same preference but different metrics then the lower cost (metric) route will be installed.
If there are multiple static routes with equal preferences and metrics the route with the lowest next hop will be installed.
If there are multiple routes with different preferences then the lower preference route will be installed.
Specifies the route as a blackhole route. If the destination address on a packet matches this static route, it will be silently discarded.
The black-hole keyword and the next-hop keyword are mutually exclusive. If an identical command is entered (with the exception of the next-hop keyword), then this static route will be replaced with the newly entered command, and unless specified, the respective defaults for preference and metric will be applied.
Specifies the directly connected next hop 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 keyword and the black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of the black-hole keyword), then this static route will be replaced with the newly entered command, and unless specified, the respective defaults for preference and metric will be applied.
The gateway 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.
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 static routes can be administratively enabled or disabled. Use the enable parameter to reenable 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.
Specifies that static routes can be administratively enabled or disabled. Use the disable parameter to disable 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 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 parameter 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 will be associated to a BFD session between the local system and the configured next hop. This keyword cannot be configured if the next hop is indirect or blackhole keywords are specified. Supported only in Network mode.
Specifies the IP address of the target CPE device. 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 to avoid possible circular references. This option is mutually exclusive with BFD support on a specific static route.
Specifies the interval, in seconds, between ICMP pings to the target IP address.
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).
triggered-policy
no triggered-policy
config>router
Supported on all 7210 SAS platforms as described in this document
This command enables 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-policycommand 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 clearcommand with the soft or soft inbound option must be used. This keeps the peer up, and the change made to a route policy is applied only to that peer or group of peers.