IP router configuration

Context

config>router>interface

config>router>router-advertisement

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

The shutdown command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics. Many entities must be explicitly enabled using the no shutdown command.

The shutdown command administratively disables an entity. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system generated configuration files.

The no form of this command administratively enables an entity.

Default

no shutdown

Context

config>router>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a text description stored in the configuration file for a configuration context.

The no form of this command removes the description string from the context.

Parameters

description-string

Specifies the description character string. Allowed values are any string of up to 80 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.

Context

config

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure router parameters, and interfaces.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters

ip-prefix

Specifies the destination address of the aggregate route, in dotted-decimal notation.

Values

ipv4-prefix	a.b.c.d (host bits must be 0)
ipv6-prefix	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

ip-prefix-length

Specifies the mask associated with the network address expressed as a mask length.

Values

ipv4-prefix-length - 0 to 32

ipv6-prefix-length - 0 to 128

summary-only

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.

black-hole

Specifies that the route is a blackhole route. If the destination address on a packet matches this static route, it will be silently discarded.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters

autonomous-system

Specifies the autonomous system number expressed as a decimal integer.

Values

1 to 4294967295

Context

config>router>interface

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

Commands in this context configure traffic sampling for the interface.

Context

config>router>interface>cflowd-parameters

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

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.

Default

no sampling

Parameters

unicast

Keyword to enable unicast sampling.

multicast

Keyword to enable multicast sampling.

type

Keyword to configure the cflowd sampling type.

interface

Keyword to configure interface cflowd sampling type.

direction

keyword to configure the direction of the cflowd analysis.

ingress-only

Keyword to configure the ingress direction only for cflowd analysis.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

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.

Default

no ecmp

Parameters

max-ecmp-routes

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.

Values

0 to 16

Context

config>router

Platforms

7210 SAS-Mxp

Description

Commands in this context configure global parameters related to MPLS labels.

Default

N/A

Context

config>router>mpls-labels

Platforms

7210 SAS-Mxp

Description

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.

Default

18400

Parameters

static-range

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}.

Values

0 to 131040

Context

config>router>mpls-labels

Platforms

7210 SAS-Mxp

Description

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.

Default

no sr-labels

Parameters

start start-value

Specifies the start label value in the SRGB.

Values

18432 to 131071

Default

none

end end-value

Specifies the end label value in the SRGB.

Values

18432 to 131071

Default

None

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

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

Parameters

router-id

Specifies the 32 bit router ID, expressed in dotted decimal notation or as a decimal value.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters

ip-prefix

Specifies the destination address of the aggregate route in dotted-decimal notation.

Values

ipv4-prefix	a.b.c.d (host bits must be 0)
ipv6-prefix	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

prefix-length

Specifies the mask associated with the network address expressed as a mask length.

Values

ipv4-prefix-length	0 to 32
ipv6-prefix-length	0 to 128

ip-address

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.

Values

ipv4-address a.b.c.d (host bits must be 0)

Values

ipv6-address	x:x:x:x:x:x:x:x[-interface]
	x:x:x:x:x:x:d.d.d.d[-interface]
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

netmask

Specifies the subnet mask, in dotted decimal notation.

Values

a.b.c.d (network bits all 1 and host bits all 0)

prefix-list prefix-list-name [all | none]

Specifies the prefix-list to be considered.

preference preference

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.

Table 4. Default route preferences

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.

Values

1 to 255

Default

5

metric metric

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.

Values

0 to 65535

Default

1

black-hole

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.

next-hop gateway

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.

Values

ip-int-name 32 chars max (must start with a letter)

tag tag

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.

Values

1 to 4294967295

Default

5

enable

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.

Default

enable

disable

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.

Default

enable

indirect ip-address

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.

Values

ip-address a.b.c.d

bfd-enable

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.

cpe-check cpe-ip-address

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.

Default

no cpe-check enabled

seconds

Specifies the interval, in seconds, between ICMP pings to the target IP address.

Values

1 to 255

Default

1

count

Specifies the number of consecutive ping-replies that must be missed to declare the CPE down and to deactivate the associated static route.

Values

1 to 255

Default

3

ldp-sync

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).

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Context

config>router>bfd

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command discards the changes to the BFD template configuration.

Context

config>router>bfd

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

Commands in this context configure a BFD template.

Context

config>router>bfd

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command creates or edits a BFD template.

A BFD template defines the set of configurable parameters used by a BFD session. These parameters include the transmit and receive timers used for BFD CC packets, the transmit timer interval used when the session is providing a CV function, the multiplier value, the echo-receive interval, and whether the BFD session terminates in the CPM network processor.

The no form of this command reverts to the default behavior.

Default

no bfd-template

Parameters

32 chars max

Specifies a text string name for the template, up to 32 characters, in printable 7-bit ASCII, enclosed in double quotes.

Context

config>router>bfd>bfd-template

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command specifies the transmit timer used for BFD packets. If the template is used for a BFD session on an MPLS-TP LSP, this timer is used for CC packets.

The no form of this command removes the transit timer interval from the configuration.

Default

no transmit-interval

Parameters

milli-seconds

Specifies the transmit interval.

Values

10 ms to 100,000 ms in 1 ms intervals

Default

10 ms

Context

config>router>bfd>bfd-template

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command specifies the receive timer used for BFD packets. If the template is used for a BFD session on an MPLS-TP LSP, this timer is used for CC packets.

The no form of this command removes the receive timer interval from the configuration.

Default

no receive-interval

Parameters

milli-seconds

Specifies the receive timer interval.

Values

10 to 100,000 ms in 1 ms intervals

Default

10 ms

Context

config>router>bfd>bfd-template

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command sets the minimum echo receive interval, in milliseconds, for a session. This is not used by a BFD session for MPLS-TP.

The no form of this command removes the minimum echo receive interval from the configuration.

Default

no echo-receive

Parameters

milli-seconds

Specifies the echo receive interval.

Values

100 ms to 100,000 ms in 1 ms increments

Default

100 ms

Context

config>router>bfd>bfd-template

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command specifies the detect multiplier used for a BFD session. If a BFD control packet is not received for a period of multiplier x receive-interval, the session is declared down.

The no form of this command reverts to the default value.

Default

multiplier 3

Parameters

3...20

Specifies the multiplier, in integer notation.

Values

3 to 20

Context

config>router>bfd

Platforms

7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network mode)

Description

This command saves the changes made to the BFD template configuration. Executing this command is required for all BFD commands to take effect and become persistent after a system reboot.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a logical system or a loopback IP routing or unnumbered MPLS-TP interface. When created, attributes like IP address, port, or system can be associated with the IP interface.

Interface names are case-sensitive and must be unique within the group of IP interfaces defined for config router interface. Interface names must not be in the dotted-decimal notation of an IP address.; for example, the name ‟1.1.1.1” is not allowed, but ‟int-1.1.1.1” is allowed. Show commands for router interfaces use either the interface names or the IP addresses. Ambiguity can exist if an IP address is used as an IP address and an interface name.

When a new name is entered, a new logical router interface is created. When an existing interface name is entered, the user enters the router interface context for editing and configuration.

Although not a keyword, the ip-int-name ‟system” is associated with the network entity (such as a specific 7210 SAS IP router), not a specific interface. The system interface is also referred to as the loopback address.

An unnumbered MPLS-TP interface is a special type of interface that is only intended for MPLS-TP LSPs. IP routing protocols are blocked on interfaces of this type. If an interface is configured as unnumbered-mpls-tp, then it can only be associated with an Ethernet port or VLAN, using the port command. then either a unicast, multicast or broadcast remote MAC address may be configured. Only static ARP is supported.

The no form of this command removes the IP interface and all the associated configurations. The interface must be administratively shut down before issuing the no interface command.

Parameters

ip-int-name

Specifies the name of the IP interface. 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.

Values

1 to 32 alphanumeric characters.

If the ip-int-name already exists, the context is changed to maintain that IP interface. If ip-int-name already exists within another service ID or is an IP interface defined within the config router commands, an error will occur and the context will not be changed to that IP interface. If ip-int-name does not exist, the interface is created and the context is changed to that interface for further command processing.

unnumbered-mpls-tp

Specifies that an interface is of type Unnumbered MPLS-TP. An unnumbered MPLS-TP interface is a special type of interface that is only intended for MPLS-TP LSPs. IP routing protocols are blocked on interfaces of this type. If an interface is configured as unnumbered-mpls-tp, then it can only be associated with an Ethernet port or VLAN, using the port command. Either a unicast, multicast or broadcast remote MAC address may be configured using the static-arp command. Only static ARP is supported. This option is supported only on 7210 SAS-T network mode, 7210 SAS-Sx 1/10GE, 7210 SAS-Sx 10/100GE, 7210 SAS-R6 and 7210 SAS-R12.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures an accounting policy. An accounting policy must be defined before it can be associated with a SAP. If the policy-id does not exist, an error message is generated. A maximum of one accounting policy can be associated with a SAP at one time.

Parameters

acct-policy-id

Specifies the accounting policy-id as configured in the config>router>accounting-policy context.

Values

1 to 99

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command assigns an IP address, IP subnet, and broadcast address format to an IP system IP interface. Only one IP address can be associated with an IP interface.

An IP address must be assigned to each IP interface. An IP address and a mask combine to create a local IP prefix. The defined IP prefix must be unique within the context of the routing instance. It cannot overlap with other existing IP prefixes defined as local subnets on other IP interfaces in the same routing context within the router.

The IP address for the interface can be entered in either CIDR (Classless Inter-Domain Routing) or traditional dotted-decimal notation. Showcommands display CIDR notation and are stored in configuration files.

By default, no IP address or subnet association exists on an IP interface until it is explicitly created.

The no form of this command removes the IP address assignment from the IP interface. The no form of this command can only be performed when the IP interface is administratively shut down. Shutting down the IP interface will operationally stop any protocol interfaces or MPLS LSPs that explicitly reference that IP address. When a new IP address is defined, the IP interface can be administratively enabled (no shutdown), which reinitializes the protocol interfaces and MPLS LSPs associated with that IP interface.

If a new address is entered while another address is still active, the new address will be rejected.

Parameters

ip-address

Specifies the IP address of the IP interface. The ip-address 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.

Values

a.b.c.d (no multicast/broadcast address)

/

Specifies a parameter delimiter that separates the ip-address portion of the IP address from the mask that defines the scope of the local subnet. No spaces are allowed between the ip-address, the ‟/” and the mask-length parameter. If a forward slash does not immediately follow the ip-address, a dotted-decimal mask must follow the prefix.

mask

Specifies the subnet mask length when the IP prefix is specified in CIDR notation. When the IP prefix is specified in CIDR notation, a forward slash (/) separates the ip-addr from the mask-length parameter. The mask length parameter indicates the number of bits used for the network portion of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. Allowed values are integers in the range 1 to 32.

Values

1 to 32 (mask length of 32 is reserved for system IP addresses)

netmask

Specifies the subnet netmask, in dotted-decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-addr from a traditional dotted decimal mask. The mask parameter indicates the complete mask that will be used in a logical ‛AND’ function to derive the local subnet of the IP address. A mask of 255.255.255.255 is reserved for system IP addresses.

Values

a.b.c.d (network bits all 1 and host bits all 0)

broadcast {all-ones | host-ones}

Specifies an optional broadcast parameter that overrides the default broadcast address used by the IP interface when sourcing IP broadcasts on the IP interface. If no broadcast format is specified for the IP address, the default value is host-ones, which indicates a subnet broadcast address. Use this parameter to change the broadcast address to all-onesor revert back to a broadcast address of host-ones.

The all-ones keyword following the broadcast parameter specifies that the broadcast address used by the IP interface for this IP address will be 255.255.255.255, also known as the local broadcast.

The host-ones keyword following the broadcast parameter specifies that the broadcast address used by the IP interface for this IP address will be the subnet broadcast address. This is an IP address that corresponds to the local subnet described by the ip-addr and the mask-length or mask with all the host bits set to binary 1. This is the default broadcast address used by an IP interface.

The broadcast parameter within the address command does not have a negate feature, which is usually used to revert a parameter to the default value. To change the broadcast type to host-ones after being changed to all-ones, the address command must be executed with the broadcast parameter defined.

The broadcast format on an IP interface can be specified when the IP address is assigned or changed.

This parameter does not affect the type of broadcasts that can be received by the IP interface. A host sending either the local broadcast (all-ones) or the valid subnet broadcast address (host-ones) will be received by the IP interface.

Values

all-ones, host-ones

Default

host-ones

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the minimum time, in seconds, an ARP entry learned on the IP interface is stored in the ARP table. ARP entries are automatically refreshed when an ARP request or gratuitous ARP is seen from an IP host. Otherwise, the ARP entry is aged from the ARP table. If the arp-timeout value is set to 0 seconds, ARP aging is disabled.

The no form of this command reverts to the default value.

Default

14400 seconds (4 hours)

Parameters

seconds

Specifies the minimum number of seconds a learned ARP entry is stored in the ARP table, expressed as a decimal integer. A value of 0 specifies that the timer is inoperative and learned ARP entries will not be aged.

Values

0 to 65535

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the bidirectional forwarding detection (BFD) parameters for the associated IP interface. If no parameters are defined, the default values are used.

The multiplier specifies the number of consecutive BFD messages that must be missed from the peer before the BFD session state is changed to down and the upper level protocols (OSPF, IS-IS) are notified of the fault.

The no form of this command removes BFD from the router interface, regardless of the RSVP.

Default

no bfd

Parameters

transmit-interval

Specifies the transmit interval, in milliseconds, for the BFD session.

Values

10 to 100000

Default

100

receive receive-interval

Specifies the receive interval, in milliseconds, for the BFD session.

Values

10 to 100000

Default

100

multiplier multiplier

Specifies the multiplier for the BFD session.

Values

3 to 20

Default

3

echo-receive echo-interval

Specifies the minimum echo receive interval, in milliseconds, for the session.

Values

100 to 100000

Default

100

type iom-hw

Specifies the use of IMM-based hardware BFD sessions on IMMs on:

• the 7210 SAS-R6 and 7210 SAS-R12

• hardware sessions on the 7210 SAS-T, 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Sx 10/100GE

The user must explicitly set this keyword when configuring a BFD on an IP interface that is configured on a port.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a delay to make the interface operational by the specified number of seconds

The value is used whenever the system attempts to bring the interface operationally up.

Parameters

seconds

Specifies a delay, in seconds, to make the interface operational.

Values

1 to 1200

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the IGP-LDP synchronization timer. This timer enables synchronization of IGP and LDP, and synchronization of static routes and LDP. When a link is restored after a failure, IGP sets the link cost to infinity and advertises it; if it is a static route, the route activation is delayed until this timer expires. The supported IGPs are OSPF and IS-IS. The actual value advertised in OSPF is 0xFFFF (65535). The actual value advertised in IS-IS regular metric is 0x3F (63) and in IS-IS wide-metric is 0xFFFFFE (16777214). This command is not supported on RIP interfaces.

If an interface belongs to both IS-IS and OSPF, a physical failure will cause both IGPs to advertise infinite metric and to follow the IGP-LDP synchronization procedures. If only one IGP bounces on this interface or on the system, then only the affected IGP advertises the infinite metric and follows the IGP-LDP synchronization procedures.

The LDP hello adjacency is brought up with the neighbor. The LDP synchronization timer is started by IGP from the time the LDP session to the neighbor is up over the interface. This synchronization timer allows time for the label-FEC bindings to be exchanged.

When the LDP synchronization timer expires, the link cost is restored and is re-advertised. IGP will announce a new best next-hop and LDP will use it if the label binding for the neighbor FEC is available.

The preceding behavior is similar for static routes. If the static route is enabled for ldp-sync (see static-route), the route is not enabled immediately after the interface to the next hop comes up. Routes are suppressed until the LDP adjacency with the neighbor comes up and the synchronization timer expires. The timer does not start until the LDP adjacency with the neighbor node is fully established.

If the user changes the cost of an interface, the new value is advertised at the next flooding of link attributes by IGP. However, if the LDP synchronization timer is still running, the new cost value will only be advertised after the timer expires. Also, if the currently advertised cost is different, the new cost value will be advertised after the user executes any of the following commands:

• tools>perform>router>isis>ldp-sync-exit

• tools>perform>router>ospf>ldp-sync-exit

• config>router>interface>no ldp-sync-timer

• config>router>ospf>disable-ldp-sync

• router>isis>disable-ldp-sync

If the user changes the value of the LDP synchronization timer parameter, the new value will take effect at the next synchronization event. That is, if the timer is still running, it will continue using the previous value.

If parallel links exist to the same neighbor, then the bindings and services should remain UP as long as there is one interface that is up. However, the user-configured LDP synchronization timer still applies on the failed then restored interface. In this case, it will only consider this interface for forwarding after IGP re-advertised its actual cost value.

The LDP Sync Timer State is not always synchronized across to the standby CPM, so after an activity switch the timer state might not be same as it was on the previously active CPM.

The no form of this command disables IGP-LDP synchronization and deletes the configuration.

Default

no ldp-sync-timer

Parameters

seconds

Specifies the time interval for the IGP-LDP synchronization timer, in seconds.

Values

1 to 1800

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables local proxy ARP on the interface.

Default

no local-proxy-arp

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the interface as a loopback interface.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command assigns a specific MAC address to an IP interface. Only one MAC address can be assigned to an IP interface. When multiple mac commands are entered, the last command overwrites the previous command.

The no form of this command reverts the MAC address of the IP interface to the default value.

Default

IP interface has a system-assigned MAC address

Parameters

ieee-mac-addr

Specifies the 48-bit MAC address for the IP interface in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables SNTP broadcasts received on the IP interface. This parameter is only valid when the SNTP broadcast-client global parameter is configured.

The no form of this command disables SNTP broadcast received on the IP interface.

Default

no ntp-broadcast

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates an association with a logical IP interface and a physical port.

An interface can also be associated with the system (loopback address).

The command returns an error if the interface is already associated with another port or the system. In this case, the association must be deleted before the command is reattempted. The port-id can be in one of the following forms:

• Ethernet Interfaces

If the card in the slot has MDAs, port-id is in the slot_number/MDA_number/port_number format; for example, 1/1/3 specifies port 3 of the MDA installed in MDA slot 1 on the card installed in chassis slot 1.

The encapsulation type is an property of a Ethernet network port. The port in this context can be tagged with either IEEE 802.1Q (referred to as dot1q) encapsulation or null encapsulation. Dot1q encapsulation supports multiple logical IP interfaces on a specific network port and Null encapsulation supports a single IP interface on the network port.

The no form of this command deletes the association with the port. The no form of this command can only be performed when the interface is administratively down.

Parameters

port-name

Specifies the physical port identifier to associate with the IP interface.

Values

port-name	port-id [:encap-val]
encap-val	- 0	for null
	- 0 to 4094	for dot1q
port-id	- slot/mda/port[.channel]
lag-id	- lag-<id>
lag	- keyword
ID	- 1 to 200

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables and configures proxy ARP on the interface and specifies an existing policy statement to analyze match and action criteria that controls the flow of routing information to and from a specific protocol, set of protocols, or a particular neighbor. The policy name is configured in the config>router>policy-options context.

Use proxy ARP so the 7210 SAS responds to ARP requests on behalf of another device. Static ARP is used when a 7210 SAS needs to know about a device on an interface that cannot or does not respond to ARP requests. Therefore, the 7210 SAS configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address.

Default

no proxy-arp-policy

Parameters

policy-name

Specifies the export route policy name. Allowed values are any string of up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. The specified policy name must already be defined.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates a network QoS policy of the type ‟ip-interface” with an IP interface. Only one network QoS policy can be associated with an IP interface at one time. Attempts to associate a second QoS policy return an error.

The network QoS policy of the type ip-interface allows the user to configure an ingress and an egress component. The ingress component allows user to map the EXP bits in the MPLS packets received on the IP interface to one of the eight forwarding classes, and to rate-limit the traffic per FC using ingress policers and meters. The egress component allows the user to optionally enable the marking of EXP bits in MPLS packets by configuring the MPLS EXP values for each of the forwarding classes.

The no form of this command removes the QoS policy association from the IP interface, and the QoS policy reverts to the default.

Default

2

Parameters

network-policy-id

Specifies an existing network policy ID to associate with the IP. interface.

Values

2 to 65535

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables remote proxy ARP on the interface.

Default

no remote-proxy-arp

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command assigns up to 64 secondary IP addresses to the interface, including the primary IP address. Each address can be configured in an IP address, IP subnet, or broadcast address format.

Parameters

ip-address

Specifies the IP address of the IP interface. The ip-address 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.

Values

a.b.c.d

/

Specifies a parameter delimiter that separates the ip-address portion of the IP address from the mask that defines the scope of the local subnet. No spaces are allowed between the ip-address, the "/" and the mask parameter. If a forward slash does not immediately follow the ip-address, a dotted-decimal netmask must follow the prefix.

mask

Specifies the subnet mask length when the IP prefix is specified in CIDR notation. When the IP prefix is specified in CIDR notation, a forward slash (/) separates the ip-address from the mask parameter. The mask parameter indicates the number of bits used for the network portion of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. Allowed values are integers in the range 1 to 32. A mask length of 32 is reserved for system IP addresses.

Values

1 to 32

netmask

Specifies the subnet mask, in dotted decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-address from a traditional dotted decimal mask. The netmask parameter indicates the complete mask that will be used in a logical 'AND' function to derive the local subnet of the IP address. A netmask of 255.255.255.255 is reserved for system IP addresses.

Values

a.b.c.d (network bits all 1 and host bits all 0)

broadcast {all-ones | host-ones}

The optional broadcast parameter overrides the default broadcast address used by the IP interface when sourcing IP broadcasts on the IP interface. If no broadcast format is specified for the IP address, the default value is host-ones, which indicates a subnet broadcast address. Use this parameter to change the broadcast address to all-ones or revert back to a broadcast address of host-ones.

The broadcast parameter within the address command does not have a negate feature, which is usually used to revert a parameter to the default value. To change the broadcast type to host-ones after being configured as all-ones, the address command must be executed with the broadcast parameter defined. The broadcast format on an IP interface can be specified when the IP address is assigned or changed.

This parameter does not affect the type of broadcasts that can be received by the IP interface. A host sending either the local broadcast (all-ones) or the valid subnet broadcast address (host-ones) will be received by the IP interface

Values

all-ones — Specifies that the broadcast address used by the IP interface for this IP address will be 255.255.255.255, also known as the local broadcast.

host-ones — Specifies that the broadcast address used by the IP interface for this IP address will be the subnet broadcast address. This is an IP address that corresponds to the local subnet described by the ip-address and mask or netmask with all of the host bits set to binary 1. This is the default broadcast address used by an IP interface.

Default

host-ones

igp-inhibit

Specifies that the secondary IP address should not be recognized as a local interface by the running IGP.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a static Address Resolution Protocol (ARP) entry associating an IP address with a MAC address for the core router instance. This static ARP appears in the core routing ARP table. A static ARP can only be configured if it exists on the network attached to the IP interface.

If an entry for a particular IP address already exists and a new MAC address is configured for the IP address, the existing MAC address is replaced by the new MAC address. The number of static-arp entries that can be configured on a single node is limited to 1000. Static ARP is used when an IP router needs to know about a device on an interface that cannot or does not respond to ARP requests. Therefore, the static ARP configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address.

The no form of this command removes a static ARP entry.

Parameters

ip-addr

Specifies the IP address for the static ARP in IP address dotted-decimal notation.

ieee-mac-addr

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

unnumbered

Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. When this command is configured, it overrides any dynamic ARP. This parameter is only supported on 7210 SAS-T network mode, 7210 SAS-R6, and 7210 SAS-R12.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a static Address Resolution Protocol (ARP) entry associating an unnumbered interface with a MAC address for the core router instance. This static ARP appears in the core routing ARP table. A static ARP can only be configured if it exists on the network attached to an unnumbered interface.

If an entry for a particular unnumbered interface already exists and a new MAC address is configured for the interface, the existing MAC address is replaced by the new MAC address.

The number of static-arp entries that can be configured on a single node is limited to 1000.

Static ARP is used when the node needs to know about a device on an interface that cannot or does not respond to ARP requests. Therefore, the node configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address. Use proxy ARP so the node responds to ARP requests on behalf of another device.

The no form of this command removes a static ARP entry.

Parameters

ieee-mac-addr

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

ip-addr

Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. When this command is configured, it overrides any dynamic ARP.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command is used on a network IP interface to alter the default trusted state to a non-trusted state. When unset or reverted to the trusted default, the ToS field will not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set, in which case the egress network interface treats all IES and network IP interface as untrusted.

When the ingress network IP interface is set to untrusted, all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface. The egress network remarking rules also apply to the ToS field of IP packets routed using IGP shortcuts (tunneled to a remote next-hop). However, the tunnel QoS markings are always derived from the egress network QoS definitions.

Egress marking and remarking is based on the internal forwarding class and profile state of the packet when it reaches the egress interface. The forwarding class is derived from ingress classification functions. The profile of a packet is either derived from ingress classification or ingress policing.

The default marking state for network IP interfaces is trusted. This is equivalent to declaring no tos-marking-state on the network IP interface. When undefined or set to tos-marking-state trusted, the trusted state of the interface will not be displayed when using show config or show info unless the detail parameter is specified. The save config command will not store the default tos-marking-state trusted state for network IP interfaces unless the detail parameter is also specified.

The no form of this command is used to restore the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.

Default

trusted

Parameters

trusted

Specifies the default, which prevents the ToS field from being remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set

untrusted

Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command sets an IP interface as an unnumbered interface and specifies the IP address to be used for the interface.

To conserve IP addresses, unnumbered interfaces can be configured. The address used when generating packets on this interface is the ip-addr parameter configured.

An error message will be generated if an unnumbered interface is configured, and an IP address already exists on this interface.

The no form of this command removes the IP address from the interface, effectively removing the unnumbered property. The interface must be shutdown before no unnumbered is issued to delete the IP address from the interface, or an error message will be generated.

Default

no unnumbered

Parameters

ip-address | ip-int-name

Specifies the IP address or IP interface name to associate with the unnumbered IP interface, in dotted decimal notation. The configured IP address must exist on this node. Nokia recommends using the system IP address as it is not associated with a particular interface and is therefore always reachable. The system IP address is the default if no ip-address or ip-int-name is configured.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure route next-hop policies.

Context

config>router>route-next-hop-policy

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command discards the changes that have been made to route next-hop templates during the current session.

Context

config>router>route-next-hop-policy

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context edit route next-hop templates. Use the commit command to save edits made during the current session. Use the abort command to discard edits made during the current session.

Context

config>router>route-next-hop-policy

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command saves the changes that have been made to route next-hop templates during the current session.

Context

config>router>route-next-hop-policy

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a template to configure the attributes of a Loop-Free Alternate (LFA) Shortest Path First (SPF) policy. An LFA SPF policy allows the user to apply specific criteria, such as admin group and SRLG constraints, to the selection of a LFA backup next-hop for a subset of prefixes which resolve to a specific primary next-hop.

The user first creates a route next-hop policy template under the global router context and then applies it to a specific OSPF or ISIS interface in the global routing instance.

A policy template can be used in both IS-IS and OSPF to apply the specific criteria to prefixes protected by LFA. Each instance of IS-IS or OSPF can apply the same policy template to one or more interfaces.

The commands within the route next-hop policy template use the begin-commit-abort model.

The following are the steps needed to create and modify the template.

1. To create a template, the user enters the name of the new template directly under the route-next-hop-policy context.

2. To delete a template which is not in use, the user enters the no form of the template command under the route-next-hop-policy context.

3. The user enters the editing mode by executing the begin command under the route-next-hop-policy context. The user can then edit and change any number of route next-hop policy templates. However, the parameter value will still be stored temporarily in the template module until the commit command is executed under the route-next-hop-policy context. Any temporary parameter changes will be lost if the user enters the abort command before the commit command.

4. The user is allowed to create or delete a template instantly when in the editing mode without the need to enter the commit command. Also, if the abort command is executed, it will have no effect on the prior deletion or creation of a template.

When the commit command is executed, IS-IS or OSPF will reevaluate the templates. If there are any net changes, ISIS or OSPF will schedule a new LFA SPF to recompute the LFA next-hop for the prefixes associated with these templates.

The no form of this command deletes the specified template.

Parameters

name

Specifies the name of the template, up to 32 characters maximum.

Context

config>router>route-next-hop-policy>template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command is used to configure the description of the next-hop template.

Parameters

description-string

Specifies the description of the next-hop template, up to 80 characters maximum.

Context

config>router>route-next-hop-policy>template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command prunes all links belonging to the specified admin group before making the LFA backup next-hop selection for a prefix.

If the same group name is part of both include-group and exclude-group configurations, the exclude-group configuration takes precedence. It other words, the exclude-group statement can be viewed as having an implicit preference value of 0.

The admin group criteria are applied before running the LFA next-hop selection algorithm.

The no form of this command deletes the admin group exclusion constraint from the route next-hop policy template.

Parameters

ip-admin-group-name

Specifies the name of the admin group to be excluded, up to 32 characters maximum.

Context

config>router>route-next-hop-policy>template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command instructs the LFA SPF selection algorithm to pick up a subset of LFA next-hops among the links which belong to one or more of the specified admin groups. A link which does not belong to at least one of the admin groups is excluded. However, a link can still be selected if it belongs to one of the groups in an include-group configuration but also belongs to other groups which are not part of any include-group configuration in the route next-hop policy.

The pref option is used to provide a relative preference for the admin group to select. A lower preference value means that LFA SPF will first attempt to select an LFA backup next-hop which is a member of the corresponding admin group. If none is found, then the admin group with the next higher preference value is evaluated. If no preference is configured for a specific admin group name, then it is supposed to be the least preferred, or numerically the highest preference value.

When evaluating multiple include-group configurations within the same preference, any link which belongs to one or more of the included admin groups can be selected as an LFA next-hop. There is no relative preference based on how many of those included admin groups the link is a member of.

If the same group name is part of both include-group and exclude-group configurations, the exclude-group configuration takes precedence. It other words, the exclude-group statement can be viewed as having an implicit preference value of 0.

The admin group criteria are applied before running the LFA next-hop selection algorithm.

The no form of this command deletes the admin group constraint from the route next-hop policy template.

Parameters

ip-admin-group-name

Specifies the name of the admin group to be included, up to 32 characters maximum.

preferences

Specifies the relative preference of a group, with 1 corresponding to the highest preference and 255 corresponding to the lowest preference.

Values

1 to 255

Context

config>router>route-next-hop-policy>template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the next-hop type for the route next-hop policy template.

The user can select IP backup next-hop.

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 of this command deletes the next-hop type constraint from the route next-hop policy template.

Parameters

ip

Specifies that IP backup next-hop is preferred.

Context

config>router>route-next-hop-policy>template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the protection type for the route next-hop policy template.

The user can select if link protection or node protection is preferred in the selection of a 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 of this command deletes the protection type constraint from the route next-hop policy template.

Parameters

link

Specifies that link protection is preferred.

node

Specifies that node protection is preferred.

Context

config>router>route-next-hop-policy>template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the SRLG constraint for the route next-hop policy template.

When this command is applied to a prefix, the LFA SPF will attempt to select an LFA next-hop from the computed ones, which uses an outgoing interface that does not participate in any of the SLRGs of the outgoing interface used by the primary next-hop.

The SRLG criterion is applied before running the LFA next-hop selection algorithm.

The no form of this command deletes the SRLG constraint from the route next-hop policy template.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure egress network filter policies for the IP interface. If an egress filter is not defined, no filtering is performed.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure ingress network filter policies for the IP interface. If an ingress filter is not defined, no filtering is performed.

Context

config>router>if>ingress

config>router>if>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates an IP filter policy with an IP interface.

Filter policies control packet forwarding and dropping based on IP match criteria.

The ip-filter-id and ipv6-filter-id must have been preconfigured before this filter command is executed. If the filter ID does not exist, an error occurs.

Only one filter ID can be specified.

The no form of this command removes the filter policy association with the IP interface.

Parameters

ip-filter-id

Specifies the ID for the IP filter policy expressed as a decimal integer. The filter policy must already exist within the config>filter>ip context.

Values

1 to 65535

ipv6-filter-id

Specifies the ID for the IPv6 filter policy expressed as a decimal integer. The filter policy must already exist within the config>filter>ip context.

Values

1 to 65535

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure Internet Control Message Protocol (ICMP) parameters on a network IP interface. ICMP is a message control and error reporting protocol that also provides information relevant to IP packet processing.

Context

config>router>if>icmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables responses to ICMP mask requests on the router interface.

If a local node sends an ICMP mask request to the router interface, the mask-reply command configures the router interface to reply to the request.

The no form of this command disables replies to ICMP mask requests on the router interface.

Default

mask-reply

Context

config>router>if>icmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables and configures the rate for ICMP redirect messages issued on the router interface.

When routes are not optimal on this router, and another router on the same subnetwork has a better route, the router can issue an ICMP redirect to alert the sending node that a better route is available.

The redirects command enables the generation of ICMP redirects on the router interface. The rate at which ICMP redirects are issued can be controlled with the optional number and time parameters by indicating the maximum number of redirect messages that can be issued on the interface for a specific time interval.

The no form of this command disables the generation of ICMP redirects on the router interface.

Parameters

number

Specifies the maximum number of ICMP redirect messages to send, expressed as a decimal integer. This parameter must be specified with the time parameter.

Values

10 to 1000

Default

100

seconds

Specifies the time frame, in seconds, used to limit the number of ICMP redirect messages that can be issued

Values

1 to 60

Default

10

Context

config>router>if>icmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the rate that Internet Control Message Protocol (ICMP) Time To Live (TTL) expired messages are issued by the IP interface.

The no form of this command disables the generation of TTL expired messages.

Parameters

number

Specifies the maximum number of ICMP TTL expired messages to send, expressed as a decimal integer. The seconds parameter must also be specified.

Values

10 to 1000

Default

100

seconds

Specifies the time frame, in seconds, used to limit the number of ICMP TTL expired messages that can be issued, expressed as a decimal integer.

Values

1 to 60

Default

10

Context

config>router>if>icmp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables and configures the rate for ICMP host and network destination unreachable messages issued on the router interface.

The unreachables command enables the generation of ICMP destination unreachables on the router interface. The rate at which ICMP unreachables is issued can be controlled with the optional number and seconds parameters by indicating the maximum number of destination unreachable messages that can be issued on the interface for a specific time interval.

The no form of this command disables the generation of ICMP destination unreachables on the router interface.

Parameters

number

Specifies the maximum number of ICMP unreachable messages to send, expressed as a decimal integer. The seconds parameter must also be specified.

Values

10 to 1000

Default

100

seconds

Specifies the time frame, in seconds, used to limit the number of ICMP unreachable messages that can be issued, expressed as a decimal integer.

Values

1 to 60

Default

10

Context

config>router

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure or apply IP interface attributes such as administrative group (admin-group) or Shared Risk Loss Group (SRLG).

Context

config>router>if-attribute

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines an administrative group (admin-group) which can be associated with an IP or MPLS interface.

Admin groups, also known as affinity, are used to tag IP and MPLS interfaces which share a specific characteristic with the same identifier. For example, an admin group identifier could represent all links which connect to core routers, all links which have bandwidth higher than 10G, or all links which are dedicated to a specific service.

The user first configures locally on each router the name and identifier of each admin group. A maximum of 32 admin groups can be configured per system.

The user then configures the admin group membership of an interface. The user can apply admin groups to a network IP or MPLS interface.

When applied to MPLS interfaces, the interfaces can be included or excluded in the LSP path definition by inferring the admin group name. CSPF will compute a path which satisfies the admin group include and exclude constraints.

When applied to network IP interfaces, the interfaces can be included or excluded in the route next-hop selection by inferring the admin group name in a route next-hop policy template applied to an interface or a set of prefixes.

The following provisioning rules are applied to admin group configuration. The system will reject the creation of an admin group if it reuses the same name or group value as an existing group.

Parameters

group-name

Specifies the name of the administrative group. The association of the group name and value should be unique within an IP/MPLS domain, up to 32 characters maximum.

group-value

Specifies the value associated with the group. The association of the group name and value should be unique within an IP/MPLS domain.

Values

0 to 31

Context

config>router>if-attribute

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines a Shared Risk Loss Group (SRLG) which can be associated with an IP or MPLS interface.

SRLG is used to tag IP or MPLS interfaces that share a specific fate with the same identifier. For example, an SRLG group identifier could represent all links which use separate fibers but are carried in the same fiber conduit. If the conduit is accidentally cut, all the fiber links are cut which means that all interfaces using these fiber links will fail.

The user first configures locally on each router the name and identifier of each SRLG group. A maximum of 1024 SRLGs can be configured per system.

The user then configures the SRLG membership of an interface. The user can apply SRLGs to a network IP or MPLS interface. A maximum of 64 SRLGs can be applied to a specific interface.

When SRLGs are applied to MPLS interfaces, CSPF at LER will exclude the SRLGs of interfaces used by the LSP primary path when computing the path of the secondary path. CSPF at a LER or LSR will also exclude the SRLGs of the outgoing interface of the primary LSP path in the computation of the path of the FRR backup LSP. This provides path disjointness between the primary path and the secondary path or FRR backup path of an LSP.

When SRLGs are applied to network IP interfaces, they are evaluated in the route next-hop selection by adding the srlg-enable option in a route next-hop policy template applied to an interface or a set of prefixes. For instance, the user can enable the SRLG constraint to select a LFA next-hop for a prefix which avoids all interfaces that share fate with the primary next-hop.

The following provisioning rules are applied to SRLG configuration. The system will reject the creation of a SRLG if it reuses the same name but with a different group value than an existing group. The system will also reject the creation of an SRLG if it reuses the same group value but with a different name than an existing group.

Parameters

group-name

Specifies the name of the administrative group. The association of the group name and value should be unique within an IP/MPLS domain, up to 32 characters maximum.

group-value

Specifies the value associated with the group. The association of the group name and value should be unique within an IP/MPLS domain.

Values

0 to 4294967295

Context

config>router>interface>if-attribute

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the admin group membership of an interface. The user can apply admin groups to a network IP or MPLS interface.

Each single operation of the admin-group command allows a maximum of 5 groups to be specified at a time. However, a maximum of 32 groups can be added to a specific interface through multiple operations. When an admin group is bound to one or more interfaces, its value cannot be changed until all bindings are removed.

The configured admin group membership will be applied in all levels/areas the interface is participating in. The same interface cannot have different memberships in different levels/areas.

The no form of this command deletes one or more of the admin-group memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.

Parameters

group-name

Specifies the name of an admin-group, up to 32 characters maximum.

Context

config>router>interface>if-attribute

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the SRLG membership of an interface. The user can apply SRLGs to a network IP or MPLS interface.

An interface can belong to a maximum of 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of 5 groups to be specified at a time. When an SRLG group is bound to one or more interfaces, its value cannot be changed until all bindings are removed.

The configured SRLG membership will be applied in all levels/areas the interface is participating in. The same interface cannot have different memberships in different levels/areas.

The no form of this command deletes one or more of the SRLG memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.

Parameters

group-name

Specifies the name of an SRLG, up to 32 characters maximum.

Context

config>router>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures IPv6 for a router interface.

The no form of this command disables IPv6 on the interface.

Default

no ipv6

Context

config>router>if>ipv6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command assigns an IPv6 address to the interface.

Parameters

ip-prefix

Specifies the IPv6 address on the interface in dotted-decimal notation.

Values

ipv6-address	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

prefix-length

Specifies the mask associated with the network address expressed as a mask length.

Values

ipv6-prefix-length -

0 to 128

eui-64

Specifies that a complete IPv6 address from the supplied prefix and 64-bit interface identifier is formed. The 64-bit interface identifier is derived from MAC address on Ethernet interfaces. For interfaces without a MAC address, for example POS interfaces, the Base MAC address of the chassis should be used.

Context

config>router>if>ipv6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure ICMPv6 parameters for the interface.

Context

config>router>if>ipv6>icmp6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the rate for ICMPv6 packet-too-big messages.

Parameters

number

Specifies that the number of packet-too-big messages issued per the time frame specified in the seconds parameter will be limited.

Values

10 to 1000

seconds

Specifies the time frame, in seconds, that is used to limit the number of packet-too-big messages issued per time frame.

Values

1 to 60

Context

config>router>if>ipv6>icmp6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the rate for ICMPv6 param-problem messages.

Parameters

number

Specifies that the number of param-problem messages issued per the time frame specified in the seconds parameter will be limited.

Values

10 to 1000

seconds

Specifies the time frame, in seconds, that is used to limit the number of param-problem messages issued per time frame.

Values

1 to 60

Context

config>router>if>ipv6>icmp6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the rate for ICMPv6 redirect messages. When configured, ICMPv6 redirects are generated when routes are not optimal on the router and another router on the same subnetwork has a better route to alert that node that a better route is available.

The no form of this command disables ICMPv6 redirects.

Default

100 10

Parameters

number

Specifies that the number of redirects issued per the time frame specified in the seconds parameter will be limited.

Values

10 to 1000

seconds

Specifies the time frame, in seconds, that is used to limit the number of redirects issued per time frame.

Values

1 to 60

Context

config>router>if>ipv6>icmp6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures rate for ICMPv6 time-exceeded messages.

Parameters

number

Specifies that the number of time-exceeded messages issued per the time frame specified in seconds parameter will be limited.

Values

10 to 1000

seconds

Specifies the time frame, in seconds, that is used to limit the number of time-exceeded messages issued per time frame.

Values

1 to 60

Context

config>router>if>ipv6>icmp6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the rate for ICMPv6 unreachable messages. When enabled, ICMPv6 host and network unreachable messages are generated by this interface.

The no form of this command disables the generation of ICMPv6 host and network unreachable messages by this interface.

Default

100 10 (when IPv6 is enabled on the interface)

Parameters

number

Specifies the number destination unreachable ICMPv6 messages to issue in the time frame specified in seconds parameter.

Values

10 to 1000

seconds

Sets the time frame, in seconds, to limit the number of destination unreachable ICMPv6 messages issued per time frame.

Values

1 to 60

Context

config>router>if>ipv6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the link local address.

Context

config>router>if>ipv6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables local proxy neighbor discovery on the interface.

The no form of this command disables local proxy neighbor discovery.

Context

config>router>if>ipv6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configure a proxy neighbor discovery policy for the interface.

Parameters

policy-name

Specifies the neighbor discovery policy name. Allowed values are any string of up to 32 characters, composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. The specified policy name must already be defined.

Context

config>router>if>ipv6

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures an IPv6-to-MAC address mapping on the interface. Use this command if a directly attached IPv6 node does not support ICMPv6 neighbor discovery, or for some reason, a static address must be used. This command can only be used on Ethernet media.

The ipv6-address must be on the subnet that was configured from the IPv6 address command or a link-local address.

Parameters

ipv6-address

Specifies the IPv6 address assigned to a router interface.

Values

ipv6-address -	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

mac-address

Specifies the MAC address for the neighbor in the form of xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx.

Context

config>router

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the configuration of router advertisement properties.

The no form of this command disables all IPv6 interfaces. However, the no interface ip-int-name command disables a specific interface.

Default

disabled

Context

config>router>router-advertisement

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures router advertisement properties on a specific interface. The interface must already exist in the config>router>interface context.

Parameters

ip-int-name

Specifies the interface name. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the current-hop-limit in the router advertisement messages. It informs the nodes on the subnet about the hop-limit when originating IPv6 packets.

Default

64

Parameters

number

Specifies the hop limit.

Values

0 to 255. A value of zero means there is an unspecified number of hops.

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command sets the managed address configuration flag. This flag indicates that DHCPv6 is available for address configuration in addition to any address autoconfigured using stateless address autoconfiguration.

Default

no managed-configuration

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the maximum interval between sending router advertisement messages.

Default

600

Parameters

seconds

Specifies the maximum interval, in seconds, between sending router advertisement messages.

Values

4 to 1800

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the minimum interval between sending ICMPv6 neighbor discovery router advertisement messages.

Default

200

Parameters

seconds

Specifies the minimum interval, in seconds, between sending ICMPv6 neighbor discovery router advertisement messages.

Values

3 to 1350

Context

config>router>router-advertisement>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the MTU for the nodes to use to send packets on the link.

Default

no mtu

Parameters

mtu-bytes

Specifies the MTU for the nodes to use to send packets on the link.

Values

1280 to 9212

Context

config>router>router-advertisement>interface

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command sets the "Other configuration" flag. This flag indicates that DHCPv6lite is available for autoconfiguration of other (non-address) information such as DNS-related information or information about other servers in the network. See RFC 3736, Stateless Dynamic Host Configuration Protocol (DHCP) for IPv6.

Default

no other-stateful-configuration

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures an IPv6 prefix in the router advertisement messages. To support multiple IPv6 prefixes, use multiple prefix statements. No prefix is advertised until explicitly configured using prefix statements.

Parameters

ip-prefix

Specifies the IP prefix for the prefix list entry, in dotted decimal notation.

Values

ipv4-prefix	a.b.c.d (host bits must be 0)
ipv6-prefix	x:x:x:x:x:x:x:x (eight 16-bit pieces)
	x:x:x:x:x:x:d.d.d.d
	x - 0 to FFFF (hexadecimal)
	d - 0 to 255 (decimal)

prefix-length

Specifies that a route must match the most significant bits and have a prefix length.

Values

ipv4-prefix-length	0 to 32
ipv6-prefix-length	0 to 128

Context

config>router>router-advertisement>if>prefix

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies whether the prefix can be used for stateless address autoconfiguration.

Default

enabled

Context

config>router>router-advertisement>if>prefix

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies whether the prefix can be used for on-link determination.

Default

enabled

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the remaining length of time, in seconds, that this prefix will continue to be preferred, such as, time until deprecation. The address generated from a deprecated prefix should not be used as a source address in new communications, but packets received on such an interface are processed as expected.

Default

604800

Parameters

seconds

Specifies the remaining length of time, in seconds, that this prefix will continue to be preferred.

infinite

Specifies that the prefix will always be preferred. A value of 4,294,967,295 represents infinity.

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the length of time, in seconds, that the prefix is valid for the purpose of on-link determination. A value of all one bits (0xffffffff) represents infinity.

The address generated from an invalidated prefix should not appear as the destination or source address of a packet.

Default

2592000

Parameters

seconds

Specifies the remaining length of time, in seconds, that this prefix will continue to be valid.

infinite

Specifies that the prefix will always be valid. A value of 4,294,967,295 represents infinity.

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures how long this router should be considered reachable by other nodes on the link after receiving a reachability confirmation.

Default

no reachable-time

Parameters

milli-seconds

Specifies the length of time the router should be considered reachable.

Values

0 to 3600000

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the retransmission frequency of neighbor solicitation messages.

Default

no retransmit-time

Parameters

milli-seconds

Specifies how often the retransmission should occur, in milliseconds.

Values

0 to 1800000

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command sets the router lifetime.

Default

1800

Parameters

seconds

Specifies the length of time (relative to the time the packet is sent), in seconds, that the prefix is valid for route determination.

Values

0, 4 to 9000. A value of 0 means that the router is not a default router on this link.

Context

config>router>router-advertisement>if

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables sending router advertisement messages using the VRRP virtual MAC address, provided that the virtual router is currently the master. If the virtual router is not the master, no router advertisement messages are sent.

The no form of this command disables sending router advertisement messages.

Default

no use-virtual-mac