[no] interface ip-int-name
config>router
Supported on all 7210 SAS platforms as described in this document
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.
MPLS-TP unnumbered interfaces are only supported on 7210 SAS-T (network operating mode), 7210 SAS-R6, and 7210 SAS-R12.
IP unnumbered interfaces are supported on all 7210 SAS platforms as described in this document, except for those operating in access-uplink mode.
See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for information about allocating addresses toward IP subnets using the config>system>resource-profile>max-ip-subnets CLI command.
Before using IPv6, resources for IPv6 routes must be allocated. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for information about the config>system>resource-profile>max-ipv6-routesCLI command.
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.
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.
accounting-policy acct-policy-id
no accounting-policy
config>router
Supported on all 7210 SAS platforms as described in this document
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.
Specifies the accounting policy-id as configured in the config>router>accounting-policy context.
address {ip-address/mask | ip-address netmask} [broadcast {all-ones | host-ones}]
no address
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
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.
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.
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.
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.
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.
arp-timeout seconds
no arp-timeout
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
14400 seconds (4 hours)
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.
bfd transmit-interval [receive receive-interval] [multiplier multiplier] [echo-receive echo-interval] [type iom-hw]
no bfd
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
These hardware sessions cannot be used for IP interfaces configured over a LAG or for BFD-over-IP interfaces with a system IP address or loopback address. LAG-based IP interfaces always use the CPM-based centralized CPU sessions on the 7210 SAS-R6 and 7210 SAS-R12, and CPU-based sessions on the 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), 7210 SAS-Sx 10/100GE, 7210 SAS-T, and 7210 SAS-Mxp with a minimum timer support of 100 ms. The user cannot configure centralized CPU sessions on the 7210 SAS-R6 and 7210 SAS-R12, and CPU-based sessions on the 7210 SAS-T for port-based IP interfaces.
For more information about protocols and platforms that support BFD, see Bidirectional Forwarding Detection.
The no form of this command removes BFD from the router interface, regardless of the RSVP.
no bfd
Specifies the transmit interval, in milliseconds, for the BFD session.
Specifies the receive interval, in milliseconds, for the BFD session.
Specifies the multiplier for the BFD session.
Specifies the minimum echo receive interval, in milliseconds, for the session.
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.
delayed-enable seconds
no delayed-enable
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
Specifies a delay, in seconds, to make the interface operational.
ldp-sync-timer seconds
no ldp-sync-timer
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
IGP-LDP synchronization is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Static route-LDP synchronization is supported on all 7210 SAS platforms as described in this document, except platforms operating in access-uplink mode.
For more information, see IGP-LDP and static route-LDP synchronization.
no ldp-sync-timer
Specifies the time interval for the IGP-LDP synchronization timer, in seconds.
[no] local-proxy-arp
config>router>interface
Supported on all 7210 SAS platforms as described in this document
This command enables local proxy ARP on the interface.
no local-proxy-arp
[no] loopback
config>router>interface
Supported on all 7210 SAS platforms as described in this document
This command configures the interface as a loopback interface.
mac ieee-mac-addr
no mac
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
IP interface has a system-assigned MAC address
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.
[no] ntp-broadcast
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
no ntp-broadcast
port port-name
no port
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
Specifies the physical port identifier to associate with the IP interface.
[no] proxy-arp-policy policy-name [policy-name...(up to 5 max)]
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
no proxy-arp-policy
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.
qos network-policy-id
no qos
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
2
Specifies an existing network policy ID to associate with the IP. interface.
[no] remote-proxy-arp
config>router>interface
Supported on all 7210 SAS platforms as described in this document
This command enables remote proxy ARP on the interface.
no remote-proxy-arp
secondary {ip-address/mask | ip-address netmask} [broadcast {all-ones | host-ones}] [igp-inhibit]
no secondary {ip-address/mask | ip-address netmask}
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
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.
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.
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.
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.
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
Specifies that the secondary IP address should not be recognized as a local interface by the running IGP.
static-arp ip-addr ieee-mac-addr unnumbered
no static-arp unnumbered
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
When used within the context for an MPLS-TP unnumbered interface, the unnumbered parameter is only supported on 7210 SAS-R6, 7210 SAS-R12, and 7210 SAS-T (network operating mode).
When used within the context for an MPLS IP unnumbered interface, the unnumbered parameter is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
The no form of this command removes a static ARP entry.
Specifies the IP address for the static ARP in IP address dotted-decimal notation.
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.
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.
static-arp ieee-mac-addr unnumbered
no static-arp
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
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.
Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. When this command is configured, it overrides any dynamic ARP.
tos-marking-state {trusted | untrusted}
no tos-marking-state
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
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
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.
unnumbered [ip-address | ip-int-name]
no unnumbered
config>router>interface
Supported on all 7210 SAS platforms as described in this document
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.
no unnumbered
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.