IP router configuration
This chapter provides information about commands required to configure basic router parameters.
Configuring IP router parameters
To provision services on a 7210 SAS device, logical IP routing interfaces must be configured to associate attributes, such as an IP address or the system with the IP interface.
A special type of IP interface is the system interface. A system interface must have an IP address with a 32-bit subnet mask.
Interfaces
7210 SAS routers use different types of interfaces for various functions. Interfaces must be configured with parameters, such as the interface type (system) and address. A port is not associated with a system interface. An interface can be associated with the system (loopback address).
Network interface on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
A network interface (a logical IP routing interface) can be configured on a physical port.
System interface on 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
The system interface is associated with the network entity (such as, a specific router or switch), not a specific interface. The system interface is also referred to as the loop-back address.
The system interface is used to preserve connectivity (when routing re-convergence is possible) when an interface fails or is removed. The system interface is also referred to as the loop-back address and is used as the router identifier. A system interface must have an IP address with a 32-bit subnet mask.
System interface on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
The system interface is associated with the network entity (such as a specific router or switch), and not a specific interface.
The system interface is associated during the configuration of the following entities:
the termination point of service tunnels
the hops when configuring MPLS paths and LSPs
the addresses on a target router for BGP and LDP peering
The system interface, also referred to as the loopback address, is used to preserve connectivity (when routing re-convergence is possible) when an interface fails or is removed. It is also used as the router identifier. A system interface must have an IP address with a 32- bit subnet mask.
Unicast Reverse Path Forwarding check on 7210 SAS-K 3SFP+ 8C
The Unicast Reverse Path Forwarding Check (Unicast RPF) feature helps mitigate problems caused by the introduction of malformed or forged (spoofed) IP source addresses into a network. The feature works by discarding IP packets that lack a verifiable IP source address. For example, common types of denial-of-service (DoS) attacks, including smurf and tribe flood network (TFN), can use forged or rapidly changing source addresses to thwart efforts to locate or filter the attacks. ISPs that provide public access can use Unicast RPF to deflect such attacks by only forwarding packets with source IP addresses that are valid and consistent with the IP routing table. This protects the network of the ISP, its customer, and the rest of the Internet.
Unicast RPF is supported for both IPv4 and IPv6 on access ports only. It is supported on any IP interface configured in the IES and VPRN services.
Unicast RPF has two modes: strict and loose, but the 7210 SAS-K 3SFP+ 8C supports only strict mode in this release.
In strict mode, Unicast RPF checks whether there is a matching prefix entry for the source address of the incoming packet in the routing table, and whether the interface expects to receive a packet with this source address prefix. If urpf-check is enabled on the interface, all interfaces are assumed to be enabled for strict mode Unicast RPF check.
In the case of ECMP, the 7210 SAS-K 3SFP+ 8C allows a packet received on an IP interface configured in strict mode Unicast RPF to be forwarded, if the IP interface on which the packet is received matches any one of the interfaces used by that ECMP route.
If there is a default route, the following is included in the Unicast RPF check:
If there is a default route, a strict mode Unicast RPF check only succeeds if the source address matches any route (including the default route) where the next-hop is on the incoming interface for the packet. A per node option exists to ignore the default route for a strict mode Unicast RPF check.
If a match is not found, the Unicast RPF check fails.
If the source IP address matches a discard/blackhole route, the packet is treated as if it failed the Unicast RPF check.
Unnumbered interfaces
Unnumbered interfaces are point-to-point interfaces that are not explicitly configured with a dedicated IP address and subnet; instead, they borrow (or link to) an IP address from another interface on the system (the system IP address, another loopback interface, or any other numbered interface) and use it as the source IP address for packets originating from the interface.
The benefits of using unnumbered interfaces are the following:
ISP backhaul can be enabled with a single IP address allocated to the CE nodes (the network interface address is coupled with the system IP address).
Nodes can be added to or deleted from a network without address changes; unnumbered interfaces are linked to a centralized IP address and therefore do not require any address change if the nodes are relocated. After a topology change, the ARP table is updated to ensure reachability, and the upper layer protocols re-establish the peering sessions.
Unnumbered interfaces are supported on:
network interfaces
IES interfaces
VPRN interfaces
Only IPv4 addresses are supported.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, unnumbered interfaces are supported for the IS-IS and OSPF routing protocols and for MPLS routing (RSVP-TE and LDP). This feature is supported through both dynamic and static ARP. Any Ethernet port with null, dot1q, or QinQ encapsulation supports IP unnumbered interfaces.
See the 7210 SAS-K 2F6C4T, K 3SFP+ 8C Routing Protocols Guide for more information about IS-IS and OSPF unnumbered interface support. See ‟Unnumbered Point-to-Point Interface in RSVP” and ‟Unnumbered Interface Support in LDP” in the 7210 SAS-K 2F6C4T, K 3SFP+ 8C MPLS Guide for more information about MPLS unnumbered interface support.
Unnumbered interfaces do not support PIM routing or IGMP listener capabilities.
Router ID
This feature is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
The router ID, a 32-bit number, uniquely identifies the router within an autonomous system (AS). In protocols such as OSPF, routing information is exchanged between areas, groups of networks that share routing information. It can be set to be the same as the loop-back address. The router ID is used by both OSPF and BGP routing protocols in the routing table manager instance.
There are several ways to obtain the router ID. On each 7210 SAS router, the router ID can be derived in the following ways:
Define the value in the config>router router-id context. The value becomes the router ID.
Configure the system interface with an IP address in theconfig>router>interface ip-int-name context. If the router ID is not manually configured in the config>router router-id context, the system interface acts as the router ID.
If neither the system interface or router ID are implicitly specified, the router ID is inherited from the last four bytes of the MAC address.
The router can be derived on the protocol level.
Autonomous systems (AS)
AS is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
BGP protocol (only selected families) is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Networks can be grouped into areas. An area is a collection of network segments within an AS that have been administratively assigned to the same group. An area’s topology is concealed from the rest of the AS, which results in a significant reduction in routing traffic.
Routing in the AS takes place on two levels, depending on whether the source and destination of a packet reside in the same area (intra-area routing) or different areas (inter-area routing). In intra-area routing, the packet is routed solely on information obtained within the area; no routing information obtained from outside the area can be used. This protects intra-area routing from the injection of bad routing information.
Routers that belong to more than one area are called area border routers. All routers in an AS do not have an identical topological database. An area border router has a separate topological database for each area it is connected to. Two routers, which are not area border routers, belonging to the same area, have identical area topological databases.
Autonomous systems share routing information, such as routes to each destination and information about the route or AS path, with other ASs using BGP. Routing tables contain lists of next hops, reachable addresses, and associated path cost metrics to each router. BGP uses the information and path attributes to compile a network topology.
Proxy ARP
This feature is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
Proxy ARP is the technique in which a router answers ARP requests intended for another node. The router appears to be present on the same network as the ‟real” node that is the target of the ARP and takes responsibility for routing packets to the ‟real” destination. Proxy ARP can help nodes on a subnet reach remote subnets without configuring routing or a default gateway. Typical routers only support proxy ARP for directly attached networks; the router is targeted to support proxy ARP for all known networks in the routing instance where the virtual interface proxy ARP is configured.
To support DSLAM and other edge like environments, proxy ARP supports policies that allow the provider to configure prefix lists that determine for which target networks proxy ARP will be attempted and prefix lists that determine for which source hosts proxy ARP will be attempted.
In addition, the proxy ARP implementation supports the ability to respond for other hosts within the local subnet domain. This is needed in environments such as DSL where multiple hosts are in the same subnet but cannot reach each other directly.
Static ARP is used when a Nokia router needs to know about a device on an interface that cannot or does not respond to ARP requests. Therefore, the configuration can state that if it has a packet with a specific IP address to send it to the corresponding ARP address. Use proxy ARP so the router responds to ARP requests on behalf of another device.
Internet Protocol versions
IPv4 and IPv6 support on the different platforms is as follows:
IPv6 is supported on all 7210 SAS platforms as described in this document, except the 7210 SAS-K 2F1C2T.
The 7210 SAS-D and 7210 SAS-Dxp platforms only support the use of IPv6 for management purposes. IPv6 cannot be used to deliver a service.
The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C platforms can be used as dual-stack IPv6 and IPv4 routers capable of IPv6 forwarding and the provision of IPv6 services, including IPv6 VPN (6VPE) services. IPv6 support can also be used for management of the node (in-band management is available).
The TiMOS implements IP routing functionality, providing support for IP version 4 (IPv4) and IP version 6 (IPv6). IP version 6 (RFC 1883, Internet Protocol, Version 6 (IPv6)) is a newer version of the Internet Protocol designed as a successor to IP version 4 (IPv4) (RFC-791, Internet Protocol). The changes from IPv4 to IPv6 effects the following categories:
Expanded addressing capabilities
IPv6 increases the IP address size from 32 bits (IPv4) to 128 bits, to support more levels of addressing hierarchy, a much greater number of addressable nodes, and simpler auto-configuration of addresses. The scalability of multicast routing is improved by adding a scope field to multicast addresses. Also, a new type of address called an anycast address is defined that is used to send a packet to any one of a group of nodes.
Note:The 7210 SAS-Dxp supports a maximum 64-bit prefix length for IPv6 addresses. This restriction applies when configuring static routes; for example, a static route can be configured with a /64 prefix using the configure router static-route 2001::0/64 next-hop 4001::5 command.
Header format simplification
Some IPv4 header fields have been dropped or made optional to reduce the common-case processing cost of packet handling and to limit the bandwidth cost of the IPv6 header.
Improved support for extensions and options
Changes in the way IP header options are encoded allows for more efficient forwarding, less stringent limits on the length of options, and greater flexibility for introducing new options in the future.
Flow labeling capability
The capability to enable the labeling of packets belonging to particular traffic flows for which the sender requests special handling, such as non-default quality of service or ‟real-time” service was added in IPv6.
Authentication and privacy capabilities
Extensions to support authentication, data integrity, and (optional) data confidentiality are specified for IPv6.
The following figure shows the IPv6 header format.
The following table describes IPv6 header fields.
Table 1. IPv6 header field descriptions Field
Description
Version
4-bit Internet Protocol version number = 6.
Prio.
4-bit priority value.
Flow Label
24-bit flow label.
Payload Length
6-bit unsigned integer. The length of payload, for example, the rest of the packet following the IPv6 header, in octets. If the value is zero, the payload length is carried in a jumbo payload hop-by-hop option.
Next Header
8-bit selector. Identifies the type of header immediately following the IPv6 header.
This field uses the same values as the IPv4 protocol field.
Hop Limit
8-bit unsigned integer. Decremented by 1 by each node that forwards the packet.
The packet is discarded if the hop limit is decremented to zero.
Source Address
128-bit address of the originator of the packet.
Destination Address
128-bit address of the intended recipient of the packet (possibly not the ultimate recipient if a routing header is present).
IPv6 applications for 7210 SAS-D and 7210 SAS-Dxp
The IPv6 applications for 7210 SAS-D and 7210 SAS-Dxp are:
IPv6 inband management of the node using access-uplink port IPv6 IP interface
IPv6 transit management traffic (using access-uplink port IPv6 IP interfaces)
IPv6 applications for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
The IPv6 applications for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C are:
IPv6 services
IPv6 dual-stack router with capability to route/forward IPv6 packets
IPv6 inband management of the node
IPv6 Provider Edge router over MPLS (6PE)
6PE allows IPv6 domains to communicate with each other over an IPv4 MPLS core network. This architecture requires no backbone infrastructure upgrades and no re-configuration of core routers, because forwarding is purely based on MPLS labels. 6PE is a cost effective solution for IPv6 deployment. The following figure shows an example of a 6PE topology with one AS.
6PE control plane support
The 6PE MP-BGP routers support:
IPv4/IPv6 dual-stack
MP-BGP can be used between 6PE routers to exchange IPv6 reachability information as follows:
The 6PE routers exchange IPv6 prefixes over MP-BGP sessions running over IPv4 transport. The MP-BGP AFI used is IPv6 (value 2).
An IPv4 address of the 6PE router is encoded as an IPv4-mapped IPv6 address in the BGP next-hop field of the IPv6 NLRI. By default, the IPv4 address that is used for peering is used. It is configurable through the route policies.
The 6PE router binds MPLS labels to the IPv6 prefixes it advertises. The SAFI used in MP-BGP is the SAFI (value 4) label. The router uses the IPv6 explicit null (value 2) label for all the IPv6 prefixes that it advertises and can accept an arbitrary label from its peers.
LDP is used to create the MPLS full mesh between the 6PE routers and the IPv4 addresses that are embedded in the next-hop field are reachable by LDP LSPs. The ingress 6PE router uses the LDP LSPs to reach remote 6PE routers.
6PE data plane support
The ingress 6PE router can push two MPLS labels to send the packets to the egress 6PE router. The top label is an LDP label used to reach the egress 6PE router. The bottom label is advertised in MP-BGP by the remote 6PE router. Typically, the IPv6 explicit null (value 2) label is used but an arbitrary value can be used when the remote 6PE router is from a vendor other than Nokia.
The egress 6PE router pops the top LDP tunnel label. It sees the IPv6 explicit null label, which indicates an IPv6 packet is encapsulated. It also pops the IPv6 explicit null label and performs an IPv6 route lookup to find out the next hop for the IPv6 packet.
DNS
The DNS client is extended to use IPv6 as transport and to handle the IPv6 address in the DNS AAAA resource record from an IPv4 or IPv6 DNS server. An assigned name can be used instead of an IPv6 address as IPv6 addresses are more difficult to remember than IPv4 addresses.
Bidirectional forwarding detection for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Bidirectional Forwarding Detection (BFD) is a light-weight, low-overhead, short-duration mechanism to detect failures in the path between two systems. If a system stops receiving BFD messages for a long enough period (based on configuration) it is assumed that a failure along the path has occurred and the associated protocol or service is notified of the failure.
The following are the advantages of implementing the BFD mechanism”
used for activity detection over any media type
can be used at any protocol layer
proliferation of different methods and be avoided.
can be used with a wide range of detection times and overhead
BFD is implemented in asynchronous mode, in this mode periodic BFD control messages are used to test the path between the systems.
A path is declared operational when two-way communication has been established between both the systems. A separate BFD session is created for each communication path and data protocol between two systems.
BFD also supports the Echo function defined in draft-ietfbfd-base-04.txt, Bidirectional Forwarding Detection. In this scenario one of the systems send a sequence of BFD echo packets to the other system which loops back the echo packets within the systems forwarding plane. If many of the echo packets are lost, the BFD session is declared as down.
BFD control packet
The base BFD specification does not specify the encapsulation type to be used for sending BFD control packets. Choice of the appropriate encapsulation-type to be implemented is based on the network and medium. The encapsulation for BFD over IPv4 networks is specified in draft-ietf-bfd-v4v6-1hop-04.txt, BFD for IPv4 (Single Hop). This specification requires that BFD control packets be sent over UDP with a destination port number of 3784 and the source port number must be within the range 49152 to 65535.
The TTL of all transmitted BFD packets must have an IP TTL of 255.
If authentication is not enabled, all BFD packets received must have an IP TTL of 255.
If authentication is enabled, the IP TTL should be 255. In case the IP TTL is not 255 the BFD packets are still processed, if packet passes the enabled authentication mechanism.
If multiple BFD sessions exist between two nodes, the BFD discriminator is used to demultiplex the BFD control packet to the appropriate BFD session.
Control packet format
The BFD control packet has 2 sections, a mandatory section and an optional authentication section.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Vers | Diag |Sta|P|F|C|A|D|R| Detect Mult | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| My Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Your Discriminator |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Desired Min TX Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Min RX Interval |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Required Min Echo RX Interval |
The following table describes BFD control packet fields.
Field |
Description |
---|---|
Vers |
The version number of the protocol. The initial protocol version is 0. |
Diag |
A diagnostic code specifying the local system’s reason for the last transition of the session from Up to some other state. Possible values are: 0-No diagnostic 1-Control detection time expired 2-Echo function failed 3-Neighbor signaled session down 4-Forwarding plane reset 5-Path down 6-Concatenated path down 7-Administratively down |
H Bit |
The ‟I Hear You” bit. This bit is set to 0 if the transmitting system either is not receiving BFD packets from the remote system, or is in the process of tearing down the BFD session for some reason. Otherwise, during normal operation, it is set to 1. |
D Bit |
The ‟demand mode” bit. (Not supported) |
P Bit |
The poll bit. If set, the transmitting system is requesting verification of connectivity, or of a parameter change. |
F Bit |
The final bit. If set, the transmitting system is responding to a received BFD control packet that had the poll (P) bit set. |
Rsvd |
Reserved bits. These bits must be zero on transmit and ignored on receipt. |
Detect Mult |
|
Length |
Length of the BFD control packet, in bytes. |
My Discriminator |
A unique, nonzero discriminator value generated by the transmitting system, used to demultiplex multiple BFD sessions between the same pair of systems. |
Your Discriminator |
The discriminator received from the corresponding remote system. This field reflects back the received value of my discriminator, or is zero if that value is unknown. |
Desired Min TX Interval |
This is the minimum interval, in microseconds, that the local system would like to use when transmitting BFD control packets. |
Required Min RX Interval |
This is the minimum interval, in microseconds, between received BFD control packets that this system is capable of supporting. |
Required Min Echo RX Interval |
This is the minimum interval, in microseconds, between received BFD echo packets that this system is capable of supporting. If this value is zero, the transmitting system does not support the receipt of BFD echo packets. |
BFD echo support
In the BFD echo support scenario, the 7210 SAS loops back received BFD echo messages to the original sender based on the destination IP address in the packet.
The echo function is useful when the local router does not have sufficient CPU power to handle a periodic polling rate at a high frequency. As a result, it relies on the echo sender to send a high rate of BFD echo messages through the receiver node, which is only processed by the receiver’s forwarding path. This allows the echo sender to send BFD echo packets at any rate.
The 7210 SAS supports only response to echo requests and does not support sending of echo requests.
BFD support on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C platforms
BFD support on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C platforms is as follows:
BFD in a VPRN service can be used for:
OSPFv2 PE-CE routing protocol
Static routes (IPv4)
BGP for PE-CE protocol (IPv4)
BFD in IES service can be used for:
OSPFv2
IS-IS for IPv4 interfaces
Static routes (IPv4)
BFD in Base routing instance can be used for:
OSPFv2 on network IPv4 interfaces
IS-IS on network IPv4 interfaces
MP-BGP for vpn-ipv4 families (only multi-hop)
Static routes (IPv4)
RSVP-TE
TLDP (IPv4)
Interface LDP (link-level) (IPv4)
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, BFD processing is supported in hardware enabling faster detection (minimum timer supported is 10ms).
DHCP
DHCP server support on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C is designed to be used for IP address assignment used for local management access to the node or to the devices connected to the node for maintenance activities.
DHCP is a configuration protocol used to communicate network information and configuration parameters from a DHCP server to a DHCP-aware client. DHCP is based on the BOOTP protocol, with additional configuration options and the added capability of allocating dynamic network addresses. DHCP-capable devices are also capable of handling BOOTP messages.
A DHCP client is an IP-capable device (typically a computer or base station) that uses DHCP to obtain configuration parameters such as a network address. A DHCP server is an Internet host or router that returns configuration parameters to DHCP clients. A DHCP/BOOTP Relay agent is a host or router that passes DHCP messages between clients and servers.
Home computers in a residential high-speed Internet application typically use the DHCP protocol to have their IP address assigned by their Internet service provider.
The following is supported on different 7210 SAS platforms:
The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C platforms can act as a DHCP Relay agent, or a local DHCP server.
The 7210 SAS-K 2F1C2T platform can act as a DHCP relay agent only.
The 7210 SAS-D and 7210 SAS-Dxp platforms can act as a DHCP relay agent only.
The following paragraphs describe the functionality available on 7210 SAS as DHCP server, and as a relay agent.
For DHCP, the DHCP protocol requires the client to transmit a request packet with a destination broadcast address of 255.255.255.255 that is processed by the DHCP server. Because IP routers do not forward broadcast packets, this would suggest that the DHCP client and server must reside on the same network segment. However, for various reasons, it is sometimes impractical to have the server and client reside in the same IP network. When the 7210 is acting as a DHCP Relay agent, it processes these DHCP broadcast packets and relays them to a preconfigured DHCP server. Therefore, DHCP clients and servers do not need to reside on the same network segment.
When the 7210 SAS is acting as a local DHCP server, it processes these DHCP broadcast packets and allocates IP addresses for the DHCP client as needed.
DHCP principles
The references to spoke-SDP and mesh-SDP in this section are only applicable to the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
In a Triple Play network, client devices (such as a routed home gateway, a session initiation protocol (SIP) phone or a set-top box) use DHCP to dynamically obtain their IP address and other network configuration information. The 7210 SAS auto-init procedure also uses DHCP to dynamically obtain the BOF used for first-time booting of the system (along with IP address required to retrieve the BOF, the configuration file and the TiMOS software image from the network). DHCP is defined and shaped by several RFCs and drafts in the IETF DHC working group including the following:
RFC 2131, Dynamic Host Configuration Protocol
RFC 3046, DHCP Relay Agent Information Option
The DHCP operation is shown in the following figure.
During boot-up, the client device sends a DHCP discover message to get an IP address from the DHCP Server. The message contains the following:
destination MAC address - broadcast
source MAC address - MAC of client device
client hardware address - MAC of client device
If this message passes through a DSLAM or other access node (possibly a 7210 SAS device), typically the Relay information option (Option 82) field is added, indicating shelf, slot, port, VPI, VCI and other fields, to identify the subscriber.
DHCP relay is enabled on the first IP interface in the upstream direction. Depending on the scenario, the DSLAM, 7210 SAS access node, or the BSR relays the discover message as a unicast packet toward the configured DHCP server. DHCP relay is configured to insert the giaddr to indicate to the DHCP server in which subnet an address should be allocated.
The DHCP server looks up the client MAC address and Option 82 information in its database. If the client is recognized and authorized to access the network, an IP address is assigned and a DHCP offer message returned. The BSA or BSR relays this back to the client device.
It is possible that the discover reached more than one DHCP server, and therefore that more than one offer was returned. The client selects one of the offered IP addresses and confirms it needs to use this in a DHCP request message, sent as unicast to the DHCP server that offered it.
The DHCP server confirms that the IP address is still available, updates its database to indicate it is now in use, and replies with a DHCP ACK message back to the client. The ACK also contains the Lease Time of the IP address.
DHCP relay
The 7210 SAS provides DHCP/BOOTP Relay agent services for DHCP clients. DHCP is used for IPv4 network addresses. DHCP is known as stateful protocols because they use dedicated servers to maintain parameter information. In the stateful auto-configuration model, hosts obtain interface addresses and configuration information and parameters from a server. The server maintains a database that keeps track of which addresses have been assigned to which hosts.
DHCP relay on different 7210 SAS platforms is as follows:
7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T support DHCP Relay on the base router, and on access IP interfaces associated with IES service used for management.
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C support DHCP Relay on the base router, and on access IP interfaces associated with IES service and VPRN service.
DHCP relay agent options
DHCP options are codes that the router inserts in packets being forwarded from a DHCP client to a DHCP server. Some options have more information stored in sub-options.
The 7210 SAS supports Option 60 and Option 61 as specified in RFC 2132. Option 60 is the vendor class identifier, which can contain information such as the client's hardware configuration. Option 61 is the client identifier.
The 7210 SAS supports the Relay Agent Information Option 82 as specified in RFC3046. The following sub-options are supported for the base router:
action
circuit ID
copy-82
remote ID
Option 82
Option 82, or the relay information option is specified in RFC 3046, DHCP Relay Agent Information Option, allows the router to append some information to the DHCP request that identifies where the original DHCP request arrives from.
There are two sub-options under Option 82:
Agent Circuit ID Sub-option (RFC 3046, section 3.1): This sub-option specifies data which must be unique to the box that is relaying the circuit.
Remote ID Sub-option (RFC 3046 section 3.2): This sub-option identifies the host at the other end of the circuit. This value must be globally unique.
Both sub-options are supported by the 7210 SAS and can be used separately or together.
Inserting Option 82 information is supported independently of DHCP relay.
When the circuit ID sub-option field is inserted by the 7210 SAS, it can take following values:
sap-id
This is the SAP index (only under an IES service).
ifindex
This is the index of the IP interface (only under an IES service).
ascii-tuple
This is an ASCII-encoded concatenated tuple, consisting of [system-name|serviceid| interface-name] (for IES) or [system-name|service-id|sap-id] (for VPLS).
vlan-ascii-tuple
This is an ASCII-encoded concatenated tuple, consisting of the ascii-tuple followed by dot1p bits and dot1q tags.
When a DHCP packet is received with Option 82 information already present, the system can do one of three things. The available actions are:
Replace
On ingress the existing information-option is replaced with the information-option parameter configured on the 7210 SAS. On egress (toward the customer) the information-option is stripped (per the RFC).
Drop
The DHCP packet is dropped and a counter is incremented.
Keep
The existing information is kept on the packet and the router does not add any more information. On egress the information option is not stripped and is sent on to the downstream node.
In accordance with the RFC, the default behavior is to keep the existing information; except if the giaddr of the packet received is identical to a local IP address on the router, then the packet is dropped and an error incremented regardless of the configured action.
The maximum packet size for a DHCP relay packet is 1500 bytes. If adding the Option 82 information would cause the packet to exceed this size, the DHCP relay request is forwarded without the Option 82 information. This packet size limitation exists to ensure that there is no fragmentation on the end Ethernet segment where the DHCP server attaches.
In the downstream direction, the inserted Option 82 information should not be passed back toward the client (as per RFC 3046, DHCP Relay Agent Information Option). To enable downstream stripping of the option 82 field, DHCP snooping should be enabled on the SDP or SAP connected to the DHCP server.
Local DHCP server on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C supports local DHCP server functionality on the base router and on access IP interfaces associated with VPRN, by dynamically assigning IPv4 addresses to access devices that request them. This standards-based, full DHCP server implementation allows a service provider the option. The 7210 SAS can support public and private addressing in the same router, including overlapped private addressing in the form of VPRNs in the same router. The 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C acts as a DHCP server.
An administrator creates pools of addresses that are available for assigned hosts. Locally attached hosts can obtain an address directly from the server. Routed hosts receive addresses through a relay point in the customer's network. When a DHCP server receives a DHCP message from a DHCP Relay agent, the server looks for a subnet to use for assigning an IP address. If configured with the use-pool-from-client command, the server searches Option 82 information for a pool name. If a pool name is found, an available address from any subnet of the pool is offered to the client. If configured with the use-gi-address command, the server uses the gateway IP address (GIADDR) supplied by the Relay agent to find a matching subnet. If a subnet is found, an address from the subnet is offered to the client. If no pool or subnet is found, then no IP address is offered to the client.
IPv4 address assignments are temporary and expire when the configured lease time is up. The server can reassign addresses after the lease expires.
If both the no use-pool-from-client command and the no use-gi-address command or no use-link-address command are specified, the server does not act.
DHCP server options
Options and identification strings can be configured on several levels.
DHCP servers support the following options, as defined in RFC 2132:
Option 1 - Subnet Mask
Option 3 - Default Routers
Option 6 - DNS Name Servers
Option 12 - Host Name
Option 15 - Domain Name
Option 44 - Netbios Name Server
Option 46 - Netbios Node Type Option
Option 50 - IP Address
Option 51 - IP Address Lease Time
Option 53 - DHCP Message Type
Option 54 - DHCP Server IP Address
Option 55 - Parameter Request List
Option 58 - Renew (T1) Timer
Option 59 - Renew (T2) Timer
Option 60 - Class Identifier
Option 61 - Client Identifier
DHCP servers also support Sub-option 13 Relay Agent Information Option 82 as specified in RFC 3046, to enable the use of a pool indicated by the DHCP client.
These options are copied into the DHCP reply message, but if the same option is defined several times, the order of priority is the following:
subnet option
pool options
options from the DHCP client request
A local DHCP server must be bound to a specified interface by referencing the server from that interface. The DHCP server is then addressable by the IP address of that interface. A normal interface or a loop-back interface can be used.
A DHCP client is defined by the MAC address and the circuit identifier. This implies that for a specific combination of MAC and circuit identifier, only one IP address can be returned; if more than one request is made, the same address is returned.
Trusted and untrusted
There is a case where the relay agent could receive a request where the downstream node added Option 82 information without also adding a giaddr (giaddr of 0). In this case the default behavior is for the router to drop the DHCP request. This behavior is in line with the RFC.
The 7210 SAS supports a command trusted, which allows the router to forward the DHCP request even if it receives one with a giaddr of 0 and Option 82 information attached. This could occur with older access equipment. In this case the relay agent would modify the request's giaddr to be equal to the ingress interface. This only makes sense when the action in the information option is keep, and the service is IES. In the case where the Option 82 information gets replaced by the relay agent, either through explicit configuration or the VPLS DHCP Relay case, the original Option 82 information is lost, and the reason for enabling the trusted option is lost.
DHCP snooping
To support DHCP based address assignment in L2 aggregation network, 7210 supports DHCP snooping. 7210 can copy packets designated to the standard UDP port for DHCP (port 67) to its control plane for inspection, this process is called DHCP snooping.
DHCP snooping can be performed in two directions:
From the client to the DHCP server (Discover or Request messages) to insert Option 82 information; For these applications, DHCP snooping must be enabled on the SAP toward the subscriber.
From the DHCP server (ACK messages), to remove the Option 82 field toward the client. For these applications, DHCP snooping must be enabled on both the SAP toward the network and the SAP toward the subscriber.
IGP-LDP and static route-LDP synchronization on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
With LDP, FECs learned from an interface do not necessarily link to that interface state. As long as the router that advertised the labels is reachable, the learned labels are stored in the incoming label map (ILM) table.
Although this feature provides LDP with a lot of flexibility, it can also cause problems. For example, when an interface comes back up from a failure or from a shutdown state, the static routes bound to that interface are installed immediately. However, the LDP adjacency to the next hop may not be up, which means that the LDP SDP remains down. In this case, the MPLS traffic is blackholed until the LDP adjacency comes up.
The same issue also applies to dynamic routes (OSPF and IS-IS).
To resolve this issue, the LDP synchronization timer enables synchronization of IGP or static routes to the LDP state.
With IGP, when a link is restored after a failure, IGP sets the link cost to infinity and advertises it. The value advertised in OSPF is 0xFFFF (65535). The value advertised in IS-IS regular metric is 0x3F (63) and in IS-IS wide-metric is 0xFFFFFE (16777214).
After IGP advertises the link cost, 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 announces a new best next-hop and LDP uses 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, 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.
Process overview on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
The following items are components to configure basic router parameters.
interface
A logical IP routing interface. When created, attributes like an IP address, port, link aggregation group or the system can be associated with the IP interface.
address
The address associates the device system name with the IP system address. An IP address must be assigned to each IP interface.
system interface
This creates an association between the logical IP interface and the system (loop-back) address. The system interface address is the circuit-less address (loop-back) and is used by default as the router ID for protocols such as OSPF and BGP.
router ID
(Optional) The router ID specifies the router IP address.
autonomous system
(Optional) An autonomous system (AS) is a collection of networks that are subdivided into smaller, more manageable areas.
Process overview on the 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
The following items are components to configure basic router parameters.
interface
A logical IP routing interface. When created, attributes like an IP address, port, link aggregation group or the system can be associated with the IP interface.
address
The address associates the device system name with the IP system address. An IP address must be assigned to each IP interface.
system interface
This creates an association between the logical IP interface and the system (loop-back) address. The system interface address is the circuit-less address (loop-back) and is used by default as the router ID for protocols such as OSPF and BGP (if supported by the platform).
Configuration notes
The following information describes router configuration guidelines:
A system interface and associated IP address should be specified.
Boot options file (BOF) parameters must be configured before configuring router parameters.
On 7210 SAS-D and 7210 SAS-Dxp IPv4 and IPv6 route table lookup entries are shared. Before adding routes for IPv6 destinations, route entries in the routed lookup table needs to be allocated for IPv6 addresses. This can be done using the CLI command config>system>resource-profile>max-ipv6-routes. This command allocates route entries for /64 IPv6 prefix route lookups. The system does not allocate any IPv6 route entries by default and user needs to allocate some resources before using IPv6. For the command to take effect the node must be rebooted after making the change. Please see the following example and the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information.
On 7210 SAS-D, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, a separate route table (or a block in the route table) is used for IPv6 /128-bit prefix route lookup. A limited amount of IPv6 /128 prefixes route lookup entries is supported. The software enables lookups in this table by default (that is, no user configuration is required to enable IPv6 /128-bit route lookup).
On 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, IPv6 interfaces are allowed to be created without allocating IPv6 route entries. With this only IPv6 hosts on the same subnet are reachable.
Configuration guidelines for DHCP relay and snooping
The following configuration guidelines must be followed to configure DHCP relay and snooping:
7210 SAS devices do not support the ARP populate based on the DHCP lease, assigned to the DHCP client
7210 SAS devices do not maintain the DHCP lease assigned to the client
7210 SAS devices do not perform IP spoofing checks and MAC spoofing checks based on the DHCP parameters assigned to the client
MAC learning must be enabled in the VPLS service, for DHCP snooping.
DHCP snooping is not supported for B-SAPs in B-VPLS services and I-SAPs in I-VPLS services.
Ingress ACLs cannot be used to drop DHCP control packet.
On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, DHCP packets received over an SDP are identified and option-82 inserted by the node can be removed by the node, in the downstream direction. SAP or a SDP, as applicable. DHCP snooping configuration on an SDP is supported only on the7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
Configuring an IP router with CLI
This section provides information to configure an IP router.
Router configuration overview of 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
In a 7210 SAS, an interface is a logical named entity. An interface is created by specifying an interface name under the config>router context. This is the global router configuration context where objects like static routes are defined. An IP interface name can be up to 32 alphanumeric characters long, must start with a letter, and is case-sensitive; for example, the interface name ‟1.1.1.1” is not allowed, but ‟int-1.1.1.1” is allowed.
To create an interface on a 7210 SAS router, the basic configuration tasks that must be performed are as follows:
Assign a name to the interface.
Associate an IP address with the interface.
Associate the interface with a system or a loop-back interface.
A system interface should be configured.
System interface on 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
The system interface is associated with the network entity, not a specific interface.
The system interface is used to preserve connectivity (when routing re-convergence is possible) when an interface fails or is removed. The system interface is used as the router identifier. A system interface must have an IP address with a 32-bit subnet mask.
Router configuration overview on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
In a 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, an interface is a logical named entity. An interface is created by specifying an interface name under the configure>router context. This is the global router configuration context where objects like static routes are defined. An IP interface name can be up to 32 alphanumeric characters long, must start with a letter, and is case-sensitive; for example, the interface name ‟1.1.1.1” is not allowed, but ‟int-1.1.1.1” is allowed.
To create an interface on a 7210 SAS router, the basic configuration tasks that must be performed are as follows:
Assign a name to the interface.
Associate an IP address with the interface.
Associate the interface with a network interface or the system interface.
Associate the interface with a system or a loop-back interface.
Configure appropriate routing protocols.
A system interface and network interface should be configured.
System interface on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
The system interface is associated with the network entity, not a specific interface. The system interface is also referred to as the loop-back address. The system interface is associated during the configuration of the following entities:
the termination point of service tunnels
the hops when configuring MPLS paths and LSPs
the addresses on a target router for BGP and LDP peering.
The system interface is used to preserve connectivity (when routing re-convergence is possible) when an interface fails or is removed. The system interface is used as the router identifier. A system interface must have an IP address with a 32-bit subnet mask.
Network interface
Network port and network IP interfaces are only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
A network interface can be configured on a physical port or LAG on a physical or logical port.
Basic configuration
The most basic router configuration must have the following:
system name
system address
Router configuration for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
A:ALA-A> config# info
. . .
#------------------------------------------
# Router Configuration
#------------------------------------------
router
interface "system"
address 10.10.10.103/32
exit
interface "to-104"
address 10.0.0.103/24
port 1/1/1
exit
exit
autonomous-system 12345
router-id 10.10.10.103
...
exit
isis
exit
...
#------------------------------------------
A:ALA-A> config#
Common configuration tasks
The following sections describe the basic system configuration tasks.
Configuring a system name
Use the system command to configure a name for the device. The name is used in the prompt string. Only one system name can be configured. If multiple system names are configured, the last one configured overwrites the previous entry.
If special characters are included in the system name string, such as spaces, #, or ?, the entire string must be enclosed in double quotes. Use the following syntax to configure the system name.
config# system
name system-name
config# system
config>system# name ALA-A
ALA-A>config>system# exit all
ALA-A#
System name configuration output
A:ALA-A>config>system# info
#------------------------------------------
# System Configuration
#------------------------------------------
name "ALA-A"
location "Mt.View, CA, NE corner of FERG 1 Building"
coordinates "37.390, -122.05500 degrees lat."
snmp
exit
. . .
exit
----------------------------------------------
Configuring interfaces
The following command sequences create a system IP interface.
The system interface cannot be deleted.
Configuring a system interface
Use the following syntax to configure a system interface.
config>router
interface interface-name
address {[ip-address/mask] | [ip-address] [netmask]}
IP configuration output showing interface information
A:ALA-A>config>router# info
#------------------------------------------
# IP Configuration
#--------------------------------------------------------
interface "system"
address 10.10.0.4/32
exit
#------------------------------------------------
Configure a network interface on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Use the following to configure a network interface on 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
config>router
interface interface-name
address ip-addr{/mask-length | mask} [broadcast {all-ones | host-ones}]
egress
filter ip ip-filter-id
ingress
filter ip ip-filter-id
port port-name
IP configuration output showing network interface information
A:ALA-A>config>router# info
#------------------------------------------
# IP Configuration
#------------------------------------------
interface "system"
address 10.10.0.4/32
exit
interface "to-ALA-2"
address 10.10.24.4/24
port 1/1/1
egress
filter ip 10
exit
exit
...
#------------------------------------------
A:ALA-A>config>router#
Configuring IPv6 parameters on 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
On the 7210 SAS-D and 7210 SAS-Dxp IPv6 interfaces with static routing can be configured. On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, IPv6 interfaces can be configured with static routing or using routing protocols such as OSPFv3 and IS-IS Ipv6 can be configured.
Before configuring the use of IPv6, system resource must be allocated for IPv6 routes on the 7210 SAS-D and 7210 SAS-Dxp using the following command.
configure>system>resource-profile>router> max-ipv6-routes num-routes
The following is a sample interface configuration showing the IPv6 default configuration when IPv6 is enabled on the interface.
*A:dut-d>config>router>if>ipv6# info detail
----------------------------------------------
icmp6
packet-too-big 100 10
param-problem 100 10
redirects 100 10
time-exceeded 100 10
unreachables 100 10
exit
address 2001:db8::/64
no dad-disable
no reachable-time
no neighbor-limit
no qos-route-lookup
no local-proxy-nd
no tcp-mss
----------------------------------------------
Use the following syntax to configure IPv6 parameters on a router interface.
config>router# interface interface-name
port port-name
ipv6
address {ipv6-address/prefix-length} [eui-64]
icmp6
packet-too-big [number seconds]
param-problem [number seconds]
redirects [number seconds]
time-exceeded [number seconds]
unreachables [number seconds]
neighbor ipv6-address mac-address
Configuration showing interface information
A:ALA-49>config>router>if# info
----------------------------------------------
address 10.11.10.1/64
port 1/1/10
ipv6
address 2001:db8::1/64
exit
----------------------------------------------
A:ALA-49>config>router>if#
Configuring an unnumbered interface
Use the following syntax to configure an unnumbered interface.
config>router
interface interface-name
unnumbered [ip-int-name | ip-address]
config>router> interface "to-ALU-3"
config>router>if# unnumbered ‟system”
config>router>if# exit
Router advertisement on 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
This feature is supported on all 7210 SAS platforms as described in this document, except the 7210 SAS-K 2F1C2T.
To configure the router to originate router advertisement messages on an interface, the interface must be configured under the router-advertisement context and be enabled (no shutdown). All other router advertisement configuration parameters are optional.
Use the following syntax to enable router advertisement and configure router advertisement parameters.
config>router# router-advertisement
interface ip-int-name
current-hop-limit number
managed-configuration
max-advertisement-interval seconds
min-advertisement-interval seconds
mtu mtu-bytes
other-stateful-configuration
prefix ipv6-prefix/prefix-length
autonomous
on-link
preferred-lifetime {seconds | infinite}
valid-lifetime {seconds | infinite}
reachable-time milli-seconds
retransmit-time milli-seconds
router-lifetime seconds
no shutdown
Router advertisement configuration output
*A:sim131>config>router>router-advert# info
----------------------------------------------
interface "n1"
prefix 2001:db8:3::/64
exit
no shutdown
exit
----------------------------------------------
*A:sim131>config>router>router-advert# interface n1
*A:sim131>config>router>router-advert>if# prefix 2001:db8:3::/64
*A:sim131>config>router>router-advert>if>prefix# info detail
----------------------------------------------
autonomous
on-link
preferred-lifetime 604800
valid-lifetime 2592000
----------------------------------------------
*A:tahi>config>router>router-advert>if>prefix#
Configuring proxy ARP
This feature is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
To configure proxy ARP, you can configure:
A prefix list in the config>router>policy-options>prefix-list context.
A route policy statement in the config>router>policy-options>policy-statement context and apply the specified prefix list as follows:
In the policy statement entry>to context, specify the host source address(es) for which ARP requests can or cannot be forwarded to non-local networks, depending on the specified action.
In the policy statement entry>from context, specify network prefixes that ARP requests will or will not be forwarded to depending on the action if a match is found. For more information about route policies, see the 7210 SAS-D, Dxp, K 2F1C2T Routing Protocols Guide and 7210 SAS-K 2F6C4T, K 3SFP+ 8C Routing Protocols Guide.
Apply the policy statement to the proxy-arp configuration in the config>router>interface context.
config>router# policy-options
begin
commit
prefix-list name
prefix ip-prefix/mask [exact | longer | through length | prefix-length-range length1-length2]
Use the following syntax to configure the policy statement specified in the proxy-arp-policy policy-statement command.
config>router# policy-options
begin
commit
policy-statement name
default-action {accept | next-entry | next-policy | reject}
entry entry-id
action {accept | next-entry | next-policy | reject}
to
prefix-list name [name...(upto 5 max)]
from
prefix-list name [name...(upto 5 max)]
Prefix list and policy statement configuration output
A:ALA-49>config>router>policy-options# info
----------------------------------------------
prefix-list "prefixlist1"
prefix 10.20.30.0/24 through 32
exit
prefix-list "prefixlist2"
prefix 10.10.10.0/24 through 32
exit
...
policy-statement "ProxyARPpolicy"
entry 10
from
prefix-list "prefixlist1"
exit
to
prefix-list "prefixlist2"
exit
action reject
exit
default-action accept
exit
exit
...
----------------------------------------------
A:ALA-49>config>router>policy-options#
Use the following syntax to configure proxy ARP.
config>router>interface interface-name
local-proxy-arp
proxy-arp-policy policy-name [policy-name...(upto 5 max)]
remote-proxy-arp
Proxy ARP configuration output
A:ALA-49>config>router>if# info
----------------------------------------------
address 192.0.2.59/24
local-proxy-arp
proxy-arp
policy-statement "ProxyARPpolicy"
exit
----------------------------------------------
A:ALA-49>config>router>if#
ECMP considerations
These ECMP considerations only apply to the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
IPv4 ECMP is supported.
LDP LSR and LDP LER ECMP are supported.
When ECMP is enabled and multiple equal-cost next-hops exit for the IGP route, the packets for this route are sprayed based on the hashing routine currently supported for IPv4 packets.
When the preferred RTM entry corresponds to a regular IP route, spraying is performed across regular IP next-hops for the prefix.
Configuration notes
IPv6 ECMP is not supported. Only a single IPv6 route for an IPv6 destination is programmed in the IPv6 FIB. IPv6 routing and IPv6 IP interfaces cannot be used if IPv4 ECMP is in use (these features are mutually exclusive).
Deriving the router ID
This feature is only supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
The router ID defaults to the address specified in the system interface command. If the system interface is not configured with an IP address, then the router ID inherits the last four bytes of the MAC address. The router ID can also be manually configured in the config>router>router-id context. On the BGP protocol level, a BGP router ID can be defined in the config>router>bgp router-id context and is only used within BGP.
If a new router ID is configured, protocols are not automatically restarted with the new router ID. The next time a protocol is initialized the new router ID is used. An interim period of time can occur when different protocols use different router IDs. To force the new router ID, issue the shutdown and no shutdown commands for each protocol that uses the router ID, or restart the entire router.
Use the following syntax to configure the router ID.
config>router
router-id router-id
interface ip-int-name
address {ip-address/mask | ip-address netmask} [broadcast all-ones | host-ones]
Router ID configuration output
A:ALA-4>config>router# info
#------------------------------------------
# IP Configuration
#------------------------------------------
interface "system"
address 10.10.0.4/32
exit
. . .
router-id 10.10.0.4
#------------------------------------------
A:ALA-4>config>router#
Configuring an autonomous system
This feature is supported only on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
Configuring an autonomous system is optional. Use the following syntax to configure an autonomous system.
config>router
autonomous-system as-number
Autonomous system configuration output
A;ALA-A>config>router# info
#------------------------------------------
# IP Configuration
#------------------------------------------
interface "system"
address 10.10.10.103/32
exit
interface "to-104"
address 10.0.0.103/24
port 1/1/1
exit
exit
autonomous-system 100
router-id 10.10.10.103
#------------------------------------------
A:ALA-A>config>router#
Configuring Option 82 handling
Option 82, or ‟Relay Information Option” is a field in DHCP messages used to identify the subscriber. The Option 82 field can already be filled in when a DHCP message is received at the router, or it can be empty. If the field is empty, the router should add identifying information (circuit ID, remote ID or both). If the field is not empty, the router can decide to replace it.
The following is a sample of a partial BSA configuration with Option 82 adding on a VPLS service. Note that snooping must be enabled explicitly on a SAP or a SDP, as applicable. DHCP snooping configuration on an SDP is supported only on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C.
*A:7210SAS>config>service#
----------------------------------------------
vpls 2 customer 1 create
shutdown
stp
shutdown
exit
sap 1/1/12:100 create
dhcp //Configuration example to add option 82
option
action replace
circuit-id
no remote-id
exit
no shutdown
exit
exit
no shutdown
exit
----------------------------------------------
*A:7210SAS>config>service#
The following example displays an example of a partial BSA configuration to remove
the Option 82 on a VPLS service.
vpls 2 customer 1 create
stp
shutdown
exit
sap 1/1/14:100 create //Configuration example to remove option 82
dhcp
snoop
no shutdown
exit
exit
Configuring a local DHCP server
Local DHCP servers provide a standards-based full DHCP server implementation which allows a service provider the option of decentralizing IP address management into the network. Local DHCP servers is supported for IP address assignment when a front-facing port on the 7210 SAS is used for local craft terminal access.
The following CLI syntax shows an example of configuring a local DHCP server (‟DHCP”).
config>service# vprn 100 customer 2 create
config>service>vprn$ autonomous-system 65535
config>service>vprn$ route-distinguisher 100:100
config>service>vprn$ interface ‟WAN” create
config>service>vprn>if$ address 192.168.17.1/31
config>service>vprn>if$ sap 1/1/1:101 create
config>service>vprn>if>sap$ exit
config>service>vprn>if$ exit
config>service>vprn$ dhcp
config>service>vprn>dhcp$ local-dhcp-server ‟DHCP” create
config>service>vprn>dhcp>server$ description ‟DHCP-TO-CUSTOMER”
config>service>vprn>dhcp>server$ use-gi-address
config>service>vprn>dhcp>server$ pool ‟DHCP-POOL” create
config>service>vprn>dhcp>server>pool$ subnet 10.0.0.0/24 create
config>service>vprn>dhcp>server>pool>subnet$ address-range 10.0.0.5 10.0.0.50
config>service>vprn>dhcp>server>pool>subnet$ exit
config>service>vprn>dhcp>server>pool$ exit
config>service>vprn>dhcp>server$ no shutdown
config>service>vprn>dhcp>server$ exit
config>service>vprn>dhcp$ exit
The following CLI syntax shows an example of mapping the configured local DHCP server (‟DHCP”) to an IP address, and configuring the customer-facing interface (‟LAN”) to relay DHCP requests to the local DHCP server.
config>service>vprn$ interface ‟DHCP” create
config>service>vprn>if$ address 10.2.2.2/32
config>service>vprn>if$ local-dhcp-server ‟DHCP”
config>service>vprn>if$ loopback
config>service>vprn>if$ exit
config>service>vprn$ interface ‟LAN” create
config>service>vprn>if$ address 10.0.0.1/31
config>service>vprn>if$ dhcp
config>service>vprn>if>dhcp$ server 10.2.2.2
config>service>vprn>if>dhcp$ trusted
config>service>vprn>if>dhcp$ no shutdown
config>service>vprn>if>dhcp$ exit
config>service>vprn>if$ exit
Service management tasks
This section discusses the service management tasks.
Changing the system name
The system command sets the name of the device and is used in the prompt string. Only one system name can be configured. If multiple system names are configured, the last one configured overwrites the previous entry.
Use the following syntax to change the system name.
config# system
name system-name
Command usage to change the system name
A:ALA-A>config>system# name tgif
A:TGIF>config>system#
System name change output
A:ALA-A>config>system# name TGIF
A:TGIF>config>system# info
#------------------------------------------
# System Configuration
#------------------------------------------
name "TGIF"
location "Mt.View, CA, NE corner of FERG 1 Building"
coordinates "37.390, -122.05500 degrees lat."
synchronize
snmp
exit
security
snmp
community "private" rwa version both
exit
exit
. . .
----------------------------------------------
A:TGIF>config>system#
Modifying interface parameters
Starting at the config>router level, navigate down to the router interface context. Follow the steps shown in the examples in this section to modify an IP address and a port.
Modifying an IP address
A:ALA-A>config>router# interface ‟to-sr1”
A:ALA-A>config>router>if# shutdown
A:ALA-A>config>router>if# no address
A:ALA-A>config>router>if# address 10.0.0.25/24
A:ALA-A>config>router>if# no shutdown
Modifying a port
A:ALA-A>config>router# interface ‟to-sr1”
A:ALA-A>config>router>if# shutdown
A:ALA-A>config>router>if# no port
A:ALA-A>config>router>if# port 1/1/2
A:ALA-A>config>router>if# no shutdown
Interface configuration output
A:ALA-A>config>router# info
#------------------------------------------
# IP Configuration
#------------------------------------------
interface "system"
address 10.0.0.103/32
exit
interface "to-sr1"
address 10.0.0.25/24
port 1/1/2
exit
router-id 10.10.0.3
#------------------------------------------
A:ALA-A>config>router#
Deleting a logical IP interface
The no form of the interface command typically removes the entry, but all entity associations must be shut down or deleted before an interface can be deleted.
Before loop-back IP interface can be deleted, it must first be administratively disabled with the shutdown command.
After the interface has been shut down, it can then be deleted with the no interface command.
config>router
no interface ip-int-name
config>router# interface test-interface
config>router>if# shutdown
config>router>if# exit
config>router# no interface test-interface
config>router#
IP router command reference
Command hierarchies
-
Router commands for 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
Router commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Router interface commands for 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
Router interface commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Router DHCP local user database commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Configuration commands
Router commands for 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
config
- router [router-name]
- interface interface-name
- no interface interface-name
- router-id ip-address
- no router-id
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [enable | disable] next-hop ip-address
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [enable | disable] black-hole
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] next-hop ip-int-name | ip-address [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}]] [description description]
- [no] triggered-policy
Router commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
config
- router [router-name]
- allow-icmp-redirect
- no allow-icmp-redirect
- allow-icmp6-redirect
- no allow-icmp6-redirect
- autonomous-system autonomous-system
- no autonomous-system
- bgp
- no bgp
- dhcp
- ecmp max-ecmp-routes
- no ecmp
- if-attribute
- admin-group group-name value group-value
- no admin-group group-name
- srlg-group group-name value group-value
- no srlg-group group-name
- interface ip-int-name
- isis
- no isis
- mpls-labels
- static-label-range static-range
- no static-label-range
- sr-labels start start-value end end-value
- no sr-labels
- ospf
- no ospf
- ospf3
- no ospf3
- route-next-hop-policy
- abort
- begin
- commit
- [no] template name
- description description-string
- no description
- [no] exclude-group ip-admin-group-name
- include-group ip-admin-group-name [pref preference]
- no include-group ip-admin-group-name
- nh-type {ip | tunnel}
- no nh-type
- protection-type {link | node}
- no protection-type
- [no] srlg-enable
- router-id ip-address
- no router-id
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] next-hop ip-int-name | ip-address [bfd-enable | {cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}]] [ldp-sync] [description description]
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] indirect ip-address [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}] [description description]
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] black-hole [prefix-list prefix-list-name [all | none]] [description description]
- [no] static-route {ip-prefix/prefix-length | ip-prefix netmask} black-hole [preference preference] [metric metric] [tag tag] [enable | disable] [description description]
- no interface interface-name
- [no] triggered-policy
- router
- sgt-qos
- application dscp-app-name dscp {dscp-value | dscp-name
- application dot1p-app-name dot1p dot1p-priority
- no application
- dscp dscp-name fc fc-name
- no dscp dscp-name
See the 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide section ‟Self-Generated Traffic Commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C” for information about self-generated traffic and applicable command descriptions.
Router interface commands for 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
config
- router [router-name]
- [no] interface interface-name
- address {ip-address/mask | ip-address netmask} [broadcast {all-ones | host-ones}]
- no address
- delayed-enable
- no delayed-enable
- description long-description-string
- no description
- icmp
- redirects [number seconds]
- no redirects
- ttl-expired [number seconds]
- no ttl-expired
- unreachables [number seconds]
- no unreachables
- [no] loopback
- [no] shutdown
Router interface commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
config
- router [router-name]
- if-attribute
- admin-group group-name value group-value
- no admin-group group-name
- srlg-group group-name value group-value
- no srlg-group group-name
- [no] interface interface-name
- address {ip-address/mask | ip-address netmask} [broadcast {all-ones | host-ones}]
- no address
- arp-timeout seconds
- no arp-timeout
- bfd transmit-interval [receive receive-interval] [multiplier multiplier] [echo-receive echo-interval [type iom-hw]
- no bfd
- delayed-enable
- no delayed-enable
- description long-description-string
- no description
- egress
- filter ip ip-filter-id
- no filter
- icmp
- [no] mask-reply
- redirects [number seconds]
- no redirects
- ttl-expired [number seconds]
- no ttl-expired
- unreachables [number seconds]
- no unreachables
- ingress
- filter ip ip-filter-id
- filter ipv6 ipv6-filter-id
- no filter [ip ip-filter-id] [ipv6 ipv6-filter-id
- ldp-sync-timer seconds
- no ldp-sync-timer
- [no] local-proxy-arp
- [no] loopback
- mac ieee-mac-addr
- no mac
- [no] ntp-broadcast
- port port-name
- no port
- [no] proxy-arp-policy policy-name [policy-name...(upto 5 max)]
- [no] remote-proxy-arp
- [no] shutdown
- srlg-group group-name [group-name...(up to 5 max)]
- [no] srlg-group group-name
- static-arp ip-address ieee-address
- static-arp ieee-address unnumbered
- no static-arp ip-address
- no static-arp unnumbered
- no unnumbered [ip-int-name | ip-address]
- no unnumbered
- urpf-check
- [no] ignore-default
Router DHCP local user database commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
config
- router
- dhcp
- local-dhcp-server server-name [create]
- no local-dhcp-server server-name
- description description-string
- no description
- [no] force-renews
- lease-hold-time [lease-hold-time]
- no lease-hold-time
- pool pool-name [create]
- no pool pool-name
- description description-string
- no description
- max-lease-time [max-lease-time]
- no max-lease-time
- min-lease-time [min-lease-time]
- no min-lease-time
- minimum-free minimum-free [percent] [event-when-depleted]
- no minimum-free
- [no] nak-non-matching-subnet
- offer-time [min minutes] [sec seconds]
- no offer-time
- options
- custom-option option-number address [ip-address (up to 4 max)]
- custom-option option-number hex hex-string
- custom-option option-number string ascii-string
- no custom-option option-number
- dns-server [ip-address (up to 4 max)]
- domain-name domain-name
- no domain-name
- lease-rebind-time [lease-rebind-time]
- no lease-rebind-time
- lease-renew-time [lease-renew-time]
- no lease-renew-time
- lease-time [lease-time]
- no lease-time
- subnet {ip-address/mask | ip-address netmask} [create]
- no subnet {ip-address/mask | ip-address netmask}
- [no] address-range start-ip-address end-ip-address
- [no] exclude-addresses start-ip-address [end-ip-address]
- maximum-declined maximum-declined
- no maximum-declined
- minimum-free minimum-free [percent] [event-when-depleted]
- no minimum-free
- options
- custom-option option-number address [ip-address...(up to 4 max)]
- custom-option option-number hex hex-string
- custom-option option-number string ascii-string
- no custom-option option-number
- default-router ip-address [ip-address...(up to 4 max)]
- no default-router
- subnet-mask ip-address
- no subnet-mask
- use-gi-address [scope scope]
- no use-gi-address
- user-db local-user-db-name
- no user-db
Router interface IPv6 commands (supported only on 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C)
config
- router [router-name]
- [no] interface ip-int-name
- [no] ipv6
- address ipv6-address/prefix-length [eui-64] [preferred]
- no address ipv6-address/prefix-length
- icmp6
- packet-too-big [number seconds]
- no packet-too-big
- param-problem [number seconds]
- no param-problem
- redirects [number seconds]
- no redirects
- time-exceeded number seconds]
- no time-exceeded
- unreachables [number seconds]
- no unreachables
- link-local-address ipv6-address [preferred]
- [no] local-proxy-nd
- neighbor ipv6-address [mac-address]
- no neighbor ipv6-address
- proxy-nd-policy policy-name [policy-name...(up to 5 max)]
- no proxy-nd-policy
- urpf-check ipv6
- [no] ignore-default
IPv6 router advertisement commands (supported only on 7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C)
config
- router [router-name]
- router-advertisement
- no router-advertisement
- interface ip-int-name
- no interface ip-int-name
- current-hop-limit number
- no current-hop-limit
- managed-configuration
- no managed-configuration
- max-advertisement-interval seconds
- no max-advertisement-interval
- min-advertisement-interval seconds
- no min-advertisement-interval
- mtu
- no mtu
- other-stateful-configuration
- no other-stateful-configuration
- prefix ipv6-prefix/prefix-length
- no prefix
- autonomous
- no autonomous
- on-link
- no on-link
- preferred-lifetime [seconds | infinite]
- no preferred-lifetime
- valid-lifetime [seconds | infinite]
- no valid-lifetime
- reachable-time milli-seconds
- no reachable-time
- retransmit-time milli-seconds
- no retransmit-time
- router-lifetime seconds
- no router-lifetime
- shutdown
Show commands
Router show commands
show
- router router-instance
- aggregate [family] [active]
- arp [ip-int-name | ip-address/mask | mac ieee-msac-address | summary] [local | dynamic | static | managed]
- bgp
- ecmp
- fib fib slot-number [family] [ip-prefix/prefix-length] [longer] [secondary]
- fib fib slot-number [family] [summary
- fib fib slot-number [nh-table-usage]
- icmp6
- interface [[ip-address | ip-int-name]
- interface [{[ip-address | ip-int-name] [detail] [family]} | summary | exclude-services]
- interface [ip-address | ip-int-name] statistics
- isis
- neighbor [ip-address | ip-int-name | mac ieee-mac-address | summary] [dynamic | static | managed]
- ospf
- policy
- route-table [family] [ip-prefix[/prefix-length] [longer | exact]| [protocol protocol-name | [summary]
- rsvp
- rtr-advertisement [interface interface-name] [prefix ipv6-prefix[/prefix-length]]
- sgt-qos (See Note below)
- application [app-name] [dscp | dot1p]
- dscp-map [dscp-name]
- static-arp [ip-address | ip-int-name | mac ieee-mac-addr]
- static-route [family] [[ip-prefix /mask] [ip-prefix /prefix-length] | [preference preference] | [next-hop ip-address | tag tag] | [detail]
- status
- tunnel-table summary [ipv4 | ipv6]
- tunnel-table [protocol protocol] [ipv4 | ipv6]
- tunnel-table [ip-prefix [/mask]] [alternative] [ipv4 | ipv6] detail
- tunnel-table [ip-prefix [/mask]] [alternative]
- tunnel-table [ip-prefix [/mask]] protocol protocol
- tunnel-table [ip-prefix [/mask]] sdp sdp-id
For descriptions of the show>router>sgt-qos commands, see the ‟Network QoS Policy Command Reference, Show Commands” section in the 7210 SAS-K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Quality of Service Guide.
DHCP show commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
show
- router
- dhcp
- local-dhcp-server server-name
- declined-addresses ip-address[/mask] [detail]
- declined-addresses pool pool-name
- free-addresses ip-address[/mask]
- free-addresses summary [subnet ip-address[/mask]
- free-addresses pool pool-name
- leases [detail]
- leases ip-address[/mask] address-from-user-db [detail]
- leases ip-address[/mask] dhcp-host dhcp-host-name [detail]
- leases ip-address[/mask] [detail] [state]
- server-stats
- subnet-ext-stats ip-address[/mask]
- subnet-ext-stats pool pool-name
- subnet-stats ip-address[/mask]
- subnet-stats pool pool-name
- summary
- servers
- servers all
- statistics [interface ip-int-name | ip-address]
- summary
Clear commands
Router clear commands
clear
- router [router-instance]
- arp {all | ip-addr | interface {ip-int-name | ip-addr}}
- icmp6 all
- icmp6 global
- icmp6 interface interface-name
- neighbor {all | ipv6-address}
- neighbor interface [ip-int-name | ipv6-address]
- router-advertisement all
- router-advertisement [interface interface-name]
DHCP clear commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
clear
- router
- dhcp
- local-dhcp-server server-name
- declined-addresses ip-address[/mask]
- declined-addresses pool pool-name
- leases ip-address[/mask] [state]
- leases all [state]
- server-stats
- statistics [ip-int-name | ip-address]
Debug commands
debug
- trace
- router router-instance
- ip
- [no] arp
- [no] icmp
- icmp6 [ip-int-name]
- no icmp6
- interface [ip-int-name]
- no interface
- [no] interface [ip-int-name | ip-address]
- neighbor [ip-int-name]
- packet [ip-int-name | ip-address] [headers] [protocol-id]
- no packet [ip-int-name | ip-address]
- route-table [ip-prefix/prefix-length] [longer]
- no route-table
Command descriptions
Configuration commands
Generic commands
shutdown
Syntax
[no] shutdown
Context
config>router>interface
config>router>router-advertisement>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
The config>router>router-advertisement>interface context is not supported on the 7210 SAS-K 2F1C2T.
This command administratively disables the 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.
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 puts an entity into the administratively enabled state.
Default
no shutdown
description
Syntax
description description-string
no description
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 up to 80 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.
Router global commands
router
Syntax
router
Context
config
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
Commands in this context configure router parameters and interfaces.
allow-icmp-redirect
Syntax
allow-icmp-redirect
no allow-icmp-redirect
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables or disables ICMP redirects received on the management interface.
The no form of this command disables ICMP redirects.
Default
no allow-icmp-redirect
allow-icmp6-redirect
Syntax
allow-icmp6-redirect
no allow-icmp6-redirect
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables or disables IPv6 ICMP redirects received on the management interface.
The no form of this command disables IPv6 ICMP redirects.
Default
no allow-icmp6-redirect
autonomous-system
Syntax
autonomous-system autonomous-system
no autonomous-system
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the autonomous system (AS) number for the router. A router can only belong to one AS. An AS number is a globally unique number with an AS. This number is used to exchange exterior routing information with neighboring ASs and as an identifier of the AS itself.
If the AS number is changed on a router with an active BGP instance, the new AS number is not used until the BGP instance is restarted either by administratively disabling or enabling (shutdown or no shutdown) the BGP instance or rebooting the system with the new configuration.
Parameters
- autonomous-system
Specifies the autonomous system number expressed as a decimal integer.
ecmp
Syntax
ecmp max-ecmp-routes
no ecmp
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables ECMP and configures the number of routes for path sharing. For example, a value of 2 means two equal-cost routes are used for cost sharing.
ECMP can only be used for routes learned with the same preference and same protocol. When more ECMP routes are available at the best preference than configured in max-ecmp-routes, the lowest next-hop IP address algorithm is used to select the number of routes configured in max-ecmp-routes.
The no form of this command disables ECMP path sharing. If ECMP is disabled, and multiple routes are available at the best preference and equal cost, route selection is as follows:
IGP selects the next-hop based on the lowest router ID
static-route chooses the next-hop based on lowest next-hop IP address
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 1 yields the same result as entering no ecmp.
mpls-labels
Syntax
mpls-labels
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
Commands in this context configure global parameters related to MPLS labels.
static-label-range
Syntax
static-label-range static-range
no static-label-range
Context
config>router>mpls-labels
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the range of MPLS static label values shared among static LSP, MPLS-TP LSP, and static service VC labels. When this range is configured, it is reserved and cannot be used by other protocols such as RSVP, LDP, BGP, or segment routing to assign a label dynamically.
The no form of this command reverts to the default value.
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 computed as {32+ static-range-1}.
sr-labels
Syntax
sr-labels start start-value end end-value
no sr-labels
Context
config>router>mpls-labels
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the range of the segment routing global block (SRGB). It is a label block that is used for assigning labels to SR prefix SIDs originated by the router. The range is carved from the system dynamic label range and is not instantiated by default.
This is a reserved label and when configured it cannot be used by other protocols such as RSVP, LDP, and BGP to assign a label dynamically.
The no form of this command reverts to the default value.
Default
no sr-labels
Parameters
- start start-value
Specifies the start label value in the SRGB.
- end end-value
Specifies the end label value in the SRGB.
router-id
Syntax
router-id ip-address
no router-id
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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
The system uses the system interface address (which is also the loopback address)
If a system interface address is not configured, use the last 32 bits of the chassis MAC address.
Parameters
- router-id
Specifies the 32-bit router ID expressed in dotted decimal notation or as a decimal value.
static-route
Syntax
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [enable | disable] next-hop ip-address
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [enable | disable] black-hole
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] next-hop ip-int-name | ip-address [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}] [description description]
Context
config>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T
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.
If a CPE connectivity check target address is already being used as the target address in a different static route, the cpe-check parameters must match. If they do not, the new configuration command is rejected.
If a static-route command is issued with no cpe-check target but the destination prefix/netmask and next-hop match a static route that did have an associated cpe-check, the cpe-check test is removed from the associated static route.
The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.
Parameters
- ip-prefix/prefix-length
Specifies the destination address of the static route.
- ip-address
Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
- netmask
Specifies the subnet mask in dotted decimal notation.
- 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 is not changed unless specified.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is according to the route preference defaults listed in Default route preferences.
If multiple routes are learned with an identical preference using the same protocol, the lowest- cost route is used. If multiple routes are learned with an identical preference using the same protocol and the costs (metrics) are equal, then the route to use is determined by the next-hop with the lowest address.
- 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 does not change unless specified. This value also determines which static route to install in the forwarding table.
If there are multiple routes with different preferences, the lower preference route is installed. If there are multiple static routes with the same preference but different metrics, the lower cost (metric) route is installed. If there are multiple static routes with the same preference and metric, the route with the lowest next-hop IP address is installed.
- black-hole
Specifies that the route is a blackhole route. If the destination address on a packet matches this static route, it is silently discarded.
The black-hole and next-hop keyword are mutually exclusive. If an identical command is entered (with the exception of the next-hop keyword), this static route is replaced with the newly entered command and, unless specified, the respective defaults for preference and metric is applied.
- next-hop ip-address
Specifies the directly connected next hop IP address used to reach the destination.
The next-hop and black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of the black-hole keyword), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric is applied.
The ip-address configured here can be either on the network side or the access side on this node. This address must be associated with a network directly connected to a network configured on this node.
- enable
Static routes can be administratively enabled or disabled. The enable parameter reenables a disabled static route. To enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route. The administrative state is maintained in the configuration file.
- disable
Static routes can be administratively enabled or disabled. The disable parameter disables a static route while maintaining the static route in the configuration. To enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route. The administrative state is maintained in the configuration file.
- cpe-check cpe-ip-address
Specifies the IP address of the target CPE device. ICMP pings are sent to this target IP address. This parameter must be configured to enable CPE connectivity for the associated static route. To avoid possible circular references, the target IP address cannot be in the same subnet as the static route subnet.
- interval seconds
Specifies the interval between ICMP pings to the target IP address, in seconds.
- drop-count count
Specifies the number of consecutive ping replies that must be missed to declare the CPE down and to deactivate the associated static route.
- log
Sets the ability to log transitions between active and inactive based on the CPE connectivity check. Events should be sent to the system log, syslog, and SNMP traps.
static-route
Syntax
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] next-hop ip-int-name | ip-address [bfd-enable | {cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}]] [ldp-sync] [description description]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] indirect ip-address [mcast-family] [community comm-id] [{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} | {prefix-list prefix-list-name [all | none]}] [description description]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [enable | disable] black-hole] [prefix-list prefix-list-name [all | none]] [description description]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} black-hole [preference preference] [metric metric] [tag tag] [enable | disable] [description description]
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command creates static route entries for both the network and access routes. When configuring a static route, the next-hop, indirect, or black-hole parameter, indicating the type of static route, must be configured. Multiple types of static routes (next-hop, indirect, black-hole) can be applied to the same IP prefix. If a static route that is forwarding traffic goes down, the default route is used instead. The preference parameter is used to specify the order in which the routes are applied. If a blackhole static route has the same preference as another route with the same prefix, the blackhole route takes a lower precedence.
If a CPE connectivity check target address is already being used as the target address in a different static route, the cpe-check parameters must match. If they do not, the new configuration command is rejected.
If a static-route command is issued with no cpe-check target, but the destination prefix/netmask and next hop matches a static route that did have an associated CPE check, the cpe-check test is removed from the associated static route.
The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.
Default
no static-route
Parameters
- ip-prefix/prefix-length
Specifies the destination address of the static route.
- ip-address
Specifies the IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that is used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
- netmask
Specifies the subnet mask in dotted decimal notation.
- 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 OSPF, IS-IS, or BGP expressed as a decimal integer. When modifying the preference of an existing static route, the metric is not changed unless specified.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is according to the route preference defaults listed in the following table.
Table 3. 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
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.
- 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 does not change unless specified. This value is also used to determine which static route to install in the forwarding table.
If there are multiple routes with different preferences, the lower preference route is installed. If there are multiple static routes with the same preference but different metrics, the lower cost (metric) route is installed. If there are multiple static routes with the same preference and metric, the route with the lowest next-hop IP address is installed.
- black-hole
Specifies that the route is a blackhole route. If the destination address on a packet matches this static route, it is silently discarded.
The black-hole and next-hop keyword are mutually exclusive. If an identical command is entered (with the exception of the next-hop keyword), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric are applied.
- next-hop ip-int-name | ip-address
Specifies the directly connected next-hop interface name or IP address used to reach the destination. If the next hop is over an unnumbered interface, the ip-int-name of the unnumbered interface (on this node) can be configured.
The next-hop and black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of the black-hole keyword), this static route is replaced with the newly entered command, and unless specified, the respective defaults for preference and metric is applied.
The ip-int-name is the interface name of the next hop. Interface names must be unique within the group of defined IP interfaces for config router interface commands. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
The ip-address configured for the next-hop parameter can be either on the network side or the access side on this node. This address must be associated with a network that is directly connected to a network configured on this node.
- 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.
- enable
Specifies that a disabled static route will be reenabled. To enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route. The administrative state is maintained in the configuration file.
- disable
Specifies that the static route will be disabled while maintaining the static route in the configuration. To enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route. The administrative state is maintained in the configuration file.
- 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 keyword must be on the network side of this node and be at least one hop away from the node.
- bfd-enable
Specifies that the state of the static route is associated with a BFD session between the local system and the configured next hop. This keyword cannot be configured if the next hop is configured as indirect or black-hole. For more information about the protocols and platforms that support BFD, see the BFD section in the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Router Configuration Guide.
- cpe-check cpe-ip-address
Specifies the IP address of the target CPE device. ICMP pings are sent to this target IP address. This parameter must be configured to enable CPE connectivity for the associated static route. To avoid possible circular references, the target IP address cannot be in the same subnet as the static route subnet. This parameter option and BFD support are mutually exclusive on a specific static route.
- interval seconds
Specifies the interval between ICMP pings to the target IP address, in seconds.
- drop-count count
Specifies the number of consecutive ping replies that must be missed to declare the CPE down and to deactivate the associated static route.
- 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).
- log
Sets the ability to log transitions between active and in-active based on the CPE connectivity check. Events should be sent to the system log, syslog, and SNMP traps.
triggered-policy
Syntax
triggered-policy
no triggered-policy
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command triggers route policy reevaluation.
By default, when a change is made to a policy in the config>router>policy>options context and then committed, the change is effective immediately. There may be circumstances when the changes should or must be delayed; for example, if a policy change is implemented that would affect every BGP peer on a 7210 SAS Mrouter, the consequences could be dramatic. It would be more effective to control changes on a peer-by-peer basis.
If the triggered-policy command is enabled, and a specific peer is established, and you want the peer to remain up, in order for a change to a route policy to take effect, a clear command with the soft or soft inbound option must be used.
Router DHCP commands for 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
local-dhcp-server
Syntax
local-dhcp-server server-name [create]
no local-dhcp-server server-name
Context
config>router>dhcp
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command instantiates a local DHCP server. A local DHCP server can serve multiple interfaces but is limited to the routing context it was which it was created.
Parameters
- server-name
Specifies the name of local DHCP server.
- create
Specifies that the local DHCP server is created. The create keyword requirement can be enabled or disabled in the environment>create context.
force-renews
Syntax
[no] force-renews
Context
config>router>dhcp>server
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables the sending of force-renew messages.
The no form of this command disables the sending of force-renew messages.
Default
no force-renews
lease-hold-time
Syntax
lease-hold-time [lease-hold-time]
no lease-hold-time
Context
config>router>dhcp>server
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the time to remember this lease. This lease-hold-time is for unsolicited release conditions such as lease timeout and normal solicited release from DHCP client.
The no form of this command reverts to the default.
Default
sec 0
Parameters
- lease-hold-time
Specifies the amount of time to remember the lease.
pool
Syntax
pool pool-name [create]
no pool pool-name
Context
config>router>dhcp>server
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures a DHCP address pool on the router.
Parameters
- pool name
Specifies the name of this IP address pool. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters.
- create
Specifies that the pool is created. The create keyword requirement can be enabled or disabled in the environment>create context.
max-lease-time
Syntax
max-lease-time [max-lease-time]
no max-lease-time
Context
config>router>dhcp>server>pool
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the maximum lease time.
The no form of this command reverts the value to the default.
Default
10 days
Parameters
- time
Specifies the maximum lease time.
min-lease-time
Syntax
min-lease-time [min-lease-time]
no min-lease-time
Context
config>router>dhcp>server>pool
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the minimum lease time.
The no form of this command returns the value to the default.
Default
10 minutes
Parameters
- time
Specifies the minimum lease time.
minimum-free
Syntax
minimum-free minimum-free [percent] [event-when-depleted]
no minimum-free
Context
config>router>dhcp>server>pool
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command specifies the minimum number of free addresses in this pool.
The no form of this command reverts to the default.
Default
1
Parameters
- minimum-free
Specifies the minimum number of free addresses.
0 to 255
- percent
Specifies that the value indicates a percentage.
- event-when-depleted
Enables a system-generate event when all available addresses in the pool or subnet of local DHCP server are depleted.
nak-non-matching-subnet
Syntax
[no] nak-non-matching-subnet
Context
config>router>dhcp>server>pool
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the system to return a DHCP NAK message if the following conditions are met:
the local DHCPv4 server receives a DHCP request with option 50 (meaning the client is trying to request a previously allocated message as described in section 3.2 of RFC 2131, Dynamic Host Configuration Protocol)
the address allocation algorithm uses a pool and the address in option 50 is not in the pool
If the conditions are not met, the system drops the DHCP packet.
Default
no nak-non-matching-subnet
offer-time
Syntax
offer-time [min minutes] [sec seconds]
no offer-time
Context
config>router>dhcp>server>pool
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the offer time.
The no form of this command reverts the value to the default.
Default
1 minute
Parameters
- time
Specifies the offer time.
options
Syntax
options
Context
config>router>dhcp>server>pool
config>router>dhcp>server>pool>subnet
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
Commands in this context configure pool options. The options defined here can be overruled by defining the same option in the local user database.
custom-option
Syntax
custom-option option-number address [ip-address...(up to 4 max)]
custom-option option-number hex hex-string
custom-option option-number string ascii-string
no custom-option option-number
Context
config>router>dhcp>server>pool>options
config>router>dhcp>server>pool>subnet>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures specific DHCP options. The options defined here can overrule options in the local user database.
The no form of this command removes the option from the configuration.
Parameters
- option-number
Specifies the option number that the DHCP server uses to send the identification strings to the DHCP client.
- address ip-address
Specifies the IP address of this host.
- hex hex-string
Specifies the hex value of this option.
- string ascii-string
Specifies the value of this option, up to 127 characters.
dns-server
Syntax
dns-server address [ip-address...(up to 4 max)]
no dns-server
Context
config>router>dhcp>server>pool>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the IP address of the DNS server.
Parameters
- ipv-address
Specifies the IP address of the DNS server in dotted-decimal notation. Up to four addresses can be entered.
domain-name
Syntax
domain-name domain-name
no domain-name
Context
config>router>dhcp>server>pool>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the default domain for a DHCP client that the router uses to complete unqualified hostnames (without a dotted-decimal domain name).
The no form of this command removes the name from the configuration.
Parameters
- domain-name
Specifies the domain name for the client.
lease-rebind-time
Syntax
lease-rebind-time [lease-rebind-time]
no lease-rebind-time
Context
config>router>dhcp>server>pool>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the time the client transitions to a rebinding state.
The no form of this command removes the time from the configuration.
Parameters
- time
Specifies the lease rebind time.
lease-renew-time
Syntax
lease-renew-time [lease-renew-time]
no lease-renew-time
Context
config>router>dhcp>server>pool>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the time the client transitions to a renew state.
The no form of this command removes the time from the configuration.
Parameters
- time
Specifies the lease renew time.
lease-time
Syntax
lease-time [lease-time]
no lease-time
Context
config>router>dhcp>server>pool>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the amount of time that the DHCP server grants to the DHCP client permission to use a particular IP address.
The no form of this command removes the lease time parameters from the configuration.
Parameters
- time
Specifies the lease time.
subnet
Syntax
subnet {ip-address/mask | ip-address netmask} [create]
no subnet {ip-address/mask | ip-address netmask}
Context
config>router>dhcp>server>pool
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command creates a subnet of IP addresses to be served from the pool. The subnet cannot include any addresses that were assigned to subscribers without those addresses specifically excluded. When the subnet is created no IP addresses are made available until a range is defined.
Parameters
- ip-address
Specifies the base IP address of the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
- mask
Specifies the subnet mask in Classless Inter-Domain Routing (CIDR) notation, expressed as a decimal integer.
- netmask
Specifies a string of 0s and 1s that mask or screen out the network part of an IP address so that only the host computer part of the address remains.
- create
Specifies that the subnet is created. The create keyword requirement can be enabled or disabled in the environment>create context.
address-range
Syntax
[no] address-range start-ip-address end-ip-address [failover {local | remote}]
Context
config>router>dhcp>server>pool>subnet
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures a range of IP addresses to be served from the pool. All IP addresses between the start and end IP addresses are included (other than specific excluded addresses).
Parameters
- start-ip-address
Specifies the start address of this range to include. This address must be unique within the subnet and specified in dotted decimal notation.
- end-ip-address
Specifies the end address of this range to include. This address must be unique within the subnet and specified in dotted decimal notation.
- failover local
Specifies that the DHCP server failover control type is in control under normal operation.
- failover remote
Specifies that the remote DHCP server failover system is in control under normal operation.
exclude-addresses
Syntax
[no] exclude-addresses start-ip-address [end-ip-address]
Context
config>router>dhcp>server>pool>subnet
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command specifies a range of IP addresses that excluded from the pool of IP addresses in this subnet.
Parameters
- start-ip-address
Specifies the start address of this range to exclude. This address must be unique within the subnet and specified in dotted decimal notation.
- end-ip-address
Specifies the end address of this range to exclude. This address must be unique within the subnet and specified in dotted decimal notation.
maximum-declined
Syntax
maximum-declined maximum-declined
no maximum-declined
Context
config>router>dhcp>server>pool>subnet
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the maximum number of declined addresses allowed.
Default
64
Parameters
- maximum-declined
Specifies the maximum number of declined addresses allowed.
minimum-free
Syntax
minimum-free minimum-free [percent] [event-when-depleted]
no minimum-free
Context
config>router>dhcp>server>pool>subnet
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the minimum number of free addresses in this subnet. If the actual number of free addresses in this subnet falls below this configured minimum, a notification is generated.
Default
1
Parameters
- minimum-free
Specifies the minimum number of free addresses in this subnet.
- percent
Specifies that the value indicates a percentage.
- event-when-depleted
This parameter enables a system-generate event when all available addresses in the pool or subnet of local DHCP server are depleted.
default-router
Syntax
default-router ip-address [ip-address...(up to 4 max)]
no default-router
Context
config>router>dhcp>server>pool>subnet>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the IP address of the default router for a DHCP client. Up to four IP addresses can be specified.
The no form of this command removes the address or addresses from the configuration.
Parameters
- ip-address
Specifies the IP address of the default router. This address must be unique within the subnet and specified in dotted decimal notation.
subnet-mask
Syntax
subnet-mask ip-address
no subnet-mask
Context
config>router>dhcp>server>pool>subnet>options
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command specifies the subnet-mask option to the client. The mask can either be defined (for super-netting) or taken from the pool address.
The no form of this command removes the address from the configuration.
Parameters
- ip-address
Specifies the IP address of the subnet mask. This address must be unique within the subnet and specified in dotted decimal notation.
use-gi-address
Syntax
use-gi-address [scope scope]
Context
config>router>dhcp>local-dhcp-server
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables the use of gi-address matching. If the gi-address flag is enabled, a pool can be used even if a subnet is not found. If the local-user-db-name is not used, the gi-address flag is used and addresses are handed out by GI only. If a user must be blocked from getting an address, the server maps to a local user database and configures the user with no address.
A pool can include multiple subnets. Because the GI is shared by multiple subnets in a subscriber interface, the pool may provide IP addresses from any of the subnets included when the GI is matched to any of its subnets. This allows a pool to be created that represents a sub-int.
Default
no use-gi-address
Parameters
- scope scope
Specifies if addresses are assigned for a specific subnet where the GI address belongs to only or for all subnets part of the pool.
user-db
Syntax
user-db local-user-db-name [create]
no user-db
Context
config>router>dhcp>server
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures a local user database for authentication.
Default
no user-db
Parameters
- local-user-db-name
Specifies the name of a local user database.
- create
Specifies that the local user database is created. The create keyword requirement can be enabled or disabled in the environment>create context.
Route next-hop policy commands
route-next-hop-policy
Syntax
route-next-hop-policy
Context
config>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
Commands in this context configure route next-hop policies.
abort
Syntax
abort
Context
config>router>route-next-hop-policy
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command discards the changes that have been made to route next-hop templates during the current session.
begin
Syntax
begin
Context
config>router>route-next-hop-policy
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables the editing mode for 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.
commit
Syntax
commit
Context
config>router>route-next-hop-policy
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command saves the changes that have been made to route next-hop templates during the current session.
template
Syntax
[no] template-name name
Context
config>router>route-next-hop-policy
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 an LFA backup next-hop for a subset of prefixes which resolve to a specific primary next-hop.
First, the user 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.
To create a template, the user enters the name of the new template directly under the route-next-hop-policy context.
To delete a template which is not in use, the user enters the no form for the template name under the route-next-hop-policy context.
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 is still stored temporarily in the template module until the commit command is executed under the route-next-hop-policy context. Any temporary parameter changes are lost if the user enters the abort command before the commit command.
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 has no effect on the prior deletion or creation of a template.
After the commit command is executed, IS-IS or OSPF reevaluates the templates. If there are any net changes, IS-IS or OSPF 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 a template.
Parameters
- template-name
Specifies the name of the template, up to 32 characters.
description
Syntax
description description-string
no description
Context
config>router>route-next-hop-policy>template
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the description of the next-hop template.
Parameters
- description-string
Specifies the description of the next-hop template. 80 characters maximum.
exclude-group
Syntax
[no] exclude-group ip-admin-group-name
Context
config>router>route-next-hop-policy>template
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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-namec d
Specifies the name of the admin group to be excluded, up to 32 characters.
include-group
Syntax
include-group ip-admin-group-name [pref preferences]
no include-group ip-admin-group-name
Context
config>router>route-next-hop-policy>template
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 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.
- preferences
Specifies the relative preference of a group, with 1 corresponding to the highest preference and 255 corresponding to the lowest preference.
nh-type
Syntax
nh-type {ip | tunnel}
no nh-type
Context
config>router>route-next-hop-policy>template
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the next-hop type for the route next-hop policy template.
The user can select IP backup next-hop is preferred.
When the route next-hop policy template is applied to an IP interface, all prefixes using this interface as a primary next-hop follow the next-hop type preference specified in the template.
The no form deletes the next-hop type constraint from the route next-hop policy template.
Default
ip
Parameters
- {ip | tunnel}
Specifies the two possible values for the next-hop type.
protection-type
Syntax
protection-type {link | node}
no protection-type
Context
config>router>route-next-hop-policy>template
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 falls 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 follow the protection type preference specified in the template.
The no form 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.
srlg-enable
Syntax
[no] srlg-enable
Context
config>router>route-next-hop-policy>template
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 attempts 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.
Router interface commands
interface
Syntax
[no] interface interface-name
Context
config>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command creates a system or a loopback IP routing interface. When created, attributes like IP address, 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, not a specific interface. The system interface is also referred to as the loopback address.
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
- interface-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.
If the interface-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 occurs and the context is not changed to that IP interface. If interface-name does not exist, the interface is created and the context is changed to that interface for further command processing.
address
Syntax
address {ip-address/mask | ip-address netmask} [broadcast {all-ones | host-ones}]
no address
Context
config>router>interface
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command assigns an IP address to a system IP interface. Only one IP address can be associated with an IP interface.
The IP address for the interface can be entered in either CIDR (Classless Inter-Domain Routing) or traditional dotted decimal notation. Show commands 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.
If a new address is entered while another address is still active, the new address is rejected.
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.
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 is 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.
- 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 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.
- netmask
Specifies the subnet mask in dotted decimal notation.
- broadcast {all-ones | host-ones}
Specifies an optional 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-ones or 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-address 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
Syntax
arp-timeout seconds
no arp-timeout
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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
Parameters
- seconds
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 are not aged.
bfd
Syntax
bfd transmit-interval [receive receive-interval] [multiplier multiplier] [echo-receive echo-interval] [type iom-hw]
no bfd
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
- receive receive-interval
Specifies the receive interval, in milliseconds, for the BFD session.
- multiplier multiplier
Specifies the multiplier for the BFD session.
- echo-receive echo-interval
Specifies the minimum echo receive interval, in milliseconds, for the session.
- type iom-hw
Specifies that IOM-based hardware BFD sessions are used. The user must explicitly set this keyword when configuring a BFD on an IP interface that is configured on a port.
delayed-enable
Syntax
delayed-enable seconds
no delayed-enable
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
local-proxy-arp
Syntax
local-proxy-arp
no local-proxy-arp
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables local proxy ARP on the interface.
The no form of this command disables local proxy ARP on the interface.
Default
no local-proxy-arp
ldp-sync-timer
Syntax
ldp-sync-timer seconds
no ldp-sync-timer
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures the IGP-LDP synchronization timer. This timer enables synchronization of IGP and LDP, and synchronization of static routes and LDP. This command is not supported on RIP interfaces.
When a link is restored after a failure, IGP sets the link cost to infinity and advertises it; if it’s a static route, the route activation is delayed until this timer expires. The supported IGPs are OSPF and IS-IS. The value advertised in OSPF is 0xFFFF (65535). The value advertised in IS-IS regular metric is 0x3F (63) and in IS-IS wide-metric is 0xFFFFFE (16777214).
If an interface belongs to both IS-IS and OSPF, a physical failure causes 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, only the affected IGP advertises the infinite metric and follows the IGP-LDP synchronization procedures.
After IGP advertises the link cost, the LDP hello adjacency is brought up with the neighbor. IGP starts the LDP synchronization timer when the LDP session to the neighbor becomes operationally 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 readvertised. IGP announces a new best next-hop and LDP uses it if the label binding for the neighbor’s 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 is only advertised after the timer expires. Also, if the currently advertised cost is different, the new cost value is advertised after the user executes any of the following commands:
tools>perform>router>ospf>ldp-sync-exit
tools>perform>router>isis>ldp-sync-exit
config>router>interface>no ldp-sync-timer
config>router>ospf>disable-ldp-sync
config>router>isis>disable-ldp-sync
See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C OAM and Diagnostics Guidefor the tools commands and to the 7210 SAS-D, Dxp, K 2F1C2T Routing Protocols Guide and the 7210 SAS-K 2F6C4T, K 3SFP+ 8C Routing Protocols Guide for the OSPF and IS-IS commands.
If the user changes the value of the LDP synchronization timer parameter, the new value takes effect at the next synchronization event. That is, if the timer is still running, it continues using the previous value.
If parallel links exist to the same neighbor, 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, the 7210 SAS only considers this interface for forwarding after IGP re-advertises its actual cost value.
The LDP Sync Timer State is not always synchronized across to the standby CSM, so after an activity switch the timer state may not be same as it was on the previously active CSM.
If the ldp-sync-timer value is configured on the interface but LDP is not running on the interface, the configuration causes the IGP route cost to increase to the maximum value.
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
loopback
Syntax
[no] loopback
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.
mac
Syntax
mac ieee-mac-addr
no mac
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
ntp-broadcast
Syntax
[no] ntp-broadcast
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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
port
Syntax
port port-name
no port
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
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.
proxy-arp-policy
Syntax
[no] proxy-arp-policy policy-name [policy-name...(up to 5 max)]
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 specific 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 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 names must already be defined.
remote-proxy-arp
Syntax
[no] remote-proxy-arp
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables remote proxy ARP on the interface.
Default
no remote-proxy-arp
static-arp
Syntax
static-arp ip-address ieee-address
no static-arp ip-address
static-arp ieee-address unnumbered
no static-arp unnumbered
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures a static Address Resolution Protocol (ARP) entry associating an IP address or an unnumbered 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.
Static ARP is used when a 7210 SAS router 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 specific IP address to send the packet to the corresponding ARP address.
The no form of this command removes a static ARP entry.
Default
no static-arp
Parameters
- ip-address
Specifies the IP address for the static ARP in IP address dotted decimal notation.
- ieee-address
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 is for an unnumbered interface. Unnumbered interfaces support dynamic ARP. When this command is configured, it overrides any dynamic ARP.
unnumbered
Syntax
unnumbered [ip-int-name | ip-address]
no unnumbered
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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-address parameter configured.
An error message is generated when 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 the no unnumbered command is issued to delete the IP address from the interface.
Default
no unnumbered
Parameters
- ip-int-name | ip-address
Specifies the IP interface name or IP address with which to associate the unnumbered IP interface, in dotted decimal notation. The configured IP address must exist on this node. Nokia recommends to use 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 ip-int-name or ip-address is not configured.
urpf-check
Syntax
urpf-check
Context
config>router
Platforms
7210 SAS-K 3SFP+ 8Cs
Description
This command enables the Unicast RPF check feature on this router.
ignore-default
Syntax
[no] ignore-default
Context
config>router>urpf-check
config>router>urpf-check>ipv6>ignore-default
Platforms
7210 SAS-K 3SFP+ 8C
Description
This command configures the Unicast RPF check feature (if enabled) to ignore default routes for purposes of determining the validity of incoming packets.
The no form of this command considers the default route to be eligible when performing a Unicast RPF check.
Default
no ignore-default
Router interface filter commands
egress
Syntax
egress
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
ingress
Syntax
ingress
Context
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
filter
Syntax
filter ip ip-filter-id
no filter
Context
config>router>if>ingress
config>router>if>egress
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 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.
For more information about service and IP interface support for different ACL match criteria for each platform, see Filter policy entities.
The no form of this command removes the filter policy association with the IP interface.
Parameters
- ip 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.
Router interface ICMP commands
icmp
Syntax
icmp
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.
mask-reply
Syntax
[no] mask-reply
Context
config>router>if>icmp
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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
redirects
Syntax
redirects [number seconds]
no redirects
Context
config>router>if>icmp
Platforms
7210 SAS-D, 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
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.
By default, generation of ICMP redirect messages is enabled at a maximum rate of 100 per 10 second 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.
- seconds
Specifies the time frame, in seconds, used to limit the number of ICMP redirect messages that can be issued. This value is expressed as a decimal integer.
ttl-expired
Syntax
ttl-expired [number seconds]
no ttl-expired
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.
By default, generation of ICMP TTL expired messages is enabled at a maximum rate of 100 per 10 second time interval.
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.
- seconds
Specifies the time frame, in seconds, used to limit the number of ICMP TTL expired messages that can be issued. This value is expressed as a decimal integer.
unreachables
Syntax
unreachables [number seconds]
no unreachables
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.
By default, generation of ICMP destination unreachables messages is enabled at a maximum rate of 100 per 10 second 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.
- seconds
Specifies the time frame, in seconds, used to limit the number of ICMP unreachable messages that can be issued. The value is expressed as a decimal integer.
Interface attribute commands
if-attribute
Syntax
if-attribute
Context
config>router
config>router>interface
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
Commands in this context configure or apply IP interface attributes such as administrative group (admin-group) or Shared Risk Loss Group (SRLG).
admin-group
Syntax
admin-group group-name value group-value
no admin-group group-name
Context
config>router>if-attribute
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
First, the user configures, locally on each router, the name and identifier of each admin group. A maximum of 32 admin groups can be configured per system.
Next, the user 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 computes a path that satisfies the inclusion and exclusion constraints of the admin group.
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 the admin group configuration. The system rejects the creation of an admin group if it reuses the same name or group value as an existing group.
Only admin groups bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.
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.
- 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.
srlg-group
Syntax
srlg-group group-name value group-value
no srlg group group-name
Context
config>router>if-attribute
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 that 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.
First, the user configures, locally on each router, the name and identifier of each SRLG group. A maximum of 1024 SRLGs can be configured per system.
Next, the user 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.
Only the SRLGs bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.
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.
- 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.
admin-group
Syntax
[no] admin-group group-name [group-name ... (up to 5 max)]
no admin-group
Context
config>router>interface>if-attribute
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
Only the admin groups bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.
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.
srlg-group
Syntax
srlg-group group-name [group-name... (up to 5 max)]
no srlg-group group-name
Context
config>router>interface>if-attribute
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
Only the SRLGs bound to an MPLS interface are advertised in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF.
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.
Router interface IPv6 commands
ipv6
Syntax
[no] ipv6
Context
config>router>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
This command configures IPv6 for a router interface.
The no form of this command disables IPv6 on the interface.
Default
not enabled
address
Syntax
address {ipv6-address/prefix-length} [eui-64]
no address {ipv6-address/prefix-length}
Context
config>router>if>ipv6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
This command assigns an IPv6 address to the interface.
Parameters
- ipv6-address/prefix-length
Specifies the IPv6 address on the interface.
- 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 addresses on Ethernet interfaces. For interfaces without a MAC address, for example POS interfaces, the Base MAC address of the chassis should be used.
icmp6
Syntax
icmp6
Context
config>router>if>ipv6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
Commands in this context configure ICMPv6 parameters for the interface.
packet-too-big
Syntax
packet-too-big [number seconds]
no packet-too-big
Context
config>router>if>ipv6>icmp6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
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.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of packet-too-big messages issued per time frame.
param-problem
Syntax
param-problem [number seconds]
no param-problem
Context
config>router>if>ipv6>icmp6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
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.
- seconds
specifies the time frame, in seconds, that is used to limit the number of param-problem messages issued per time frame.
redirects
Syntax
redirects [number seconds]
no redirects
Context
config>router>if>ipv6>icmp6
Platforms
7210 SAS-D, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
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 (when IPv6 is enabled on the interface)
Parameters
- number
Specifies that the number of redirects issued per the time frame, specified in seconds parameter, will be limited.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of redirects issued per time frame.
time-exceeded
Syntax
time-exceeded [number seconds]
no time-exceeded
Context
config>router>if>ipv6>icmp6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
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.
- seconds
Specifies the time frame, in seconds, that is used to limit the number of time-exceeded messages issued per time frame.
unreachables
Syntax
unreachables [number seconds]
no unreachables
Context
config>router>if>ipv6>icmp6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
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.
- seconds
Sets the time frame, in seconds, to limit the number of destination unreachable ICMPv6 messages issued per time frame.
link-local-address
Syntax
link-local-address ipv6-address [preferred]
no link-local-address
Context
config>router>if>ipv6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
This command configures the link local address.
local-proxy-nd
Syntax
[no] local-proxy-nd
Context
config>router>if>ipv6
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command enables local proxy neighbor discovery on the interface.
The no form of this command disables local proxy neighbor discovery.
proxy-nd-policy
Syntax
proxy-nd-policy policy-name [policy-name...(up to 5 max)]
no proxy-nd-policy
Context
config>router>if>ipv6
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command configures a proxy neighbor discovery policy for the interface.
Parameters
- policy-name
Specifies the neighbor discovery policy name. Allowed values are any string 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 names must already be defined.
neighbor
Syntax
neighbor [ipv6-address] [mac-address]
no neighbor [ipv6-address]
Context
config>router>if>ipv6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
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.
- 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.
IPv6 router advertisement commands
router-advertisement
Syntax
router-advertisement
no router-advertisement
Context
config>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command enables router advertisement on IPV6 interfaces. By default, it is disabled for all IPv6-enabled interfaces.
The no form of this command disables router advertisement on all IPv6 interfaces.
Default
no router-advertisement
interface
Syntax
interface ip-int-name
no interface ip-int-name
Context
config>router>router-advertisement
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures router advertisement properties on a specified IPv6 interface. The interface name must already exist in the config>router>interface>ipv6 context.
The no form of this command disables the specifies IPv6 interface.
Parameters
- template-name
Specifies the name of an existing IPv6 interface. An interface name cannot be in the form of an IPv6 address. If the string contains special characters (such as #, $, spaces), the entire string must be enclosed within double quotes. The string must start with a letter and the max is 32 characters.
current-hop-limit
Syntax
current-hop-limit number
no current-hop-limit
Context
config>router>router-advertisement>if
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command enables the router to advertise the hop-limit in ICMPv6 Neighbor Discovery (ND) router advertisement messages.
The no form of this command disables the advertising of the hop-limit in ICMPv6 ND router advertisement messages by the router.
Default
no current-hop-limit
Parameters
- number
Specifies the number of hop limits.
managed-configuration
Syntax
managed-configuration
no managed-configuration
Context
config>router>router-advertisement>if
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command enables the ‟managed-config-flag” to be advertised in ICMPv6 ND router advertisement messages.
The no form of this command disables the advertising of the ‟managed-config-flag” in ICMPv6 router advertisement messages.
Default
no managed-configuration
max-advertisement-interval
Syntax
max-advertisement-interval seconds
no max-advertisement-interval
Context
config>router>router-advertisement>if
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the maximum interval between sending ICMPv6 ND router advertisement messages.
The no form of this command disables the setting of a maximum interval between sending ICMPv6 ND router advertisement messages.
Default
no max-advertisement-interval
Parameters
- seconds
Specifies the maximum interval, in seconds.
min-advertisement-interval
Syntax
min-advertisement-interval seconds
no min-advertisement-interval
Context
config>router>router-advertisement>if
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the minimum interval between sending ICMPv6 ND router advertisement messages.
The no form of this command disables the setting of a minimum interval between sending ICMPv6 ND router advertisement messages.
Default
no min-advertisement-interval
Parameters
- seconds
Specifies the minimum interval, in seconds.
mtu
Syntax
mtu mtu-bytes
no mtu
Context
config>router>router-advertisement>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the MTU for sending packets to the router.
The no form of this command disables the sending of MTU in the router advertisement messages
Default
no mtu
Parameters
- mtu-bytes
Specifies the MTU for the nodes to use when sending packets.
other-stateful-configuration
Syntax
other-stateful-configuration
no other-stateful-configuration
Context
config>router>router-advertisement>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command enables the ‟other-config-flag” to be advertised in ICMPv6 ND router advertisement messages.
The no form of this command disables the advertising of the ‟other-config-flag” in ICMPv6 router advertisement messages.
Default
no other-stateful-configuration
prefix
Syntax
prefix ipv6-prefix/prefix-length
no prefix
Context
config>router>router-advertisement>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the IPv6 prefix to include in router advertisement messages. To support multiple IPv6 prefixes, use multiple prefix statements.
The no form of this command disables the inclusion of an IPv6 prefix in router advertisement messages.
Default
no prefix
Parameters
- ipv6-prefix/prefix-length
The Pv6 prefix.
autonomous
Syntax
autonomous
no autonomous
Context
config>router>router-advertisement>interface>prefix
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command specifies whether the prefix can be used for a stateless address autoconfiguration.
The no form of this command disables the prefix to be used for a stateless address autoconfiguration.
Default
autonomous
on-link
Syntax
on-link
no on-link
Context
config>router>router-advertisement>interface>prefix
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command specifies whether the prefix can be used for onlink determination.
The no form of this command disables the prefix to be used for onlink determination.
Default
on-link
preferred-lifetime
Syntax
preferred-lifetime [seconds | infinite]
no preferred-lifetime
Context
config>router>router-advertisement>interface>prefix
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the remaining time, in seconds, that this prefix continues to be preferred (time until deprecation). The address generated from a deprecated prefix should not be used as a source address in new communications. However, packets received on such an interface are processed as expected.
The no form of this command does disables the configuration of the time until deprecation for the prefix.
Default
no preferred-lifetime
Parameters
- seconds
Specifies the remaining length of time, in seconds, that this prefix will be preferred.
- infinite
Specifies that the prefix will always be preferred. A value of 4294967295 represents infinity.
valid-lifetime
Syntax
valid-lifetime [seconds | infinite]
no valid-lifetime
Context
config>router>router-advertisement>interface>prefix
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command specifies the length of time, in seconds, that the prefix is valid for the purpose of onlink determination. The address generated from an invalidated prefix should not appear as the destination or source address of a packet.
The no form of this command disables configuration of the time that the prefix is valid for the purpose of onlink determination.
Default
no valid-lifetime
Parameters
- seconds
Specifies the remaining length of time, in seconds, that this prefix will be valid.
- infinite
Specifies that the prefix will always be valid. A value of 4294967295 represents infinity.
reachable-time
Syntax
reachable-time milli-seconds
no reachable-time
Context
config>router>router-advertisement>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures how long the router should be considered reachable by other nodes on the link after receiving a reachability confirmation.
The no form of this command disables the configuration of how long the router should be considered reachable.
Default
no reachable-time
Parameters
- milli-seconds
Specifies the amount of time, in milliseconds, that the router will be considered reachable.
retransmit-time
Syntax
retransmit-time milli-seconds
no retransmit-time
Context
config>router>router-advertisement>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the retransmission frequency of neighbor solicitation messages.
The no form of this command disables the configuration of the retransmission frequency of neighbor solicitation messages.
Default
no retransmit-time
Parameters
- milli-seconds
Specifies the length of time, in milliseconds, that a host should wait before retransmitting neighbor solicitation messages.
router-lifetime
Syntax
router-lifetime seconds
no router-lifetime
Context
config>router>router-advertisement>interface
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 3SFP+ 8C
Description
This command configures the router lifetime.
The no form of this command disables the configuration of the router lifetime.
Default
no router-lifetime
Parameters
- seconds
Specifies the router lifetime, in seconds.
Show commands
aggregate
Syntax
aggregate [family] [active]
Context
show>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command displays aggregate routes.
Parameters
- active
Specifies that inactive aggregates are filtered out.
- family
Specifies the router IP interface family to display.
arp
Syntax
arp [ip-int-name | ip-address/mask | mac ieee-mac-address | summary] [local | dynamic | static]
Context
show>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays the router ARP table sorted by IP address. If no command line options are specified, all ARP entries are displayed.
Parameters
- ip-address/mask
Displays only ARP entries associated with the specified IP address and mask.
- ip-int-name
Displays only ARP entries associated with the specified IP interface name.
- mac ieee-mac-addr
Displays only ARP entries associated with the specified MAC address.
- summary
Displays an abbreviated list of ARP entries.
- [local | dynamic | static]
Displays only ARP information associated with the keyword.
Output
The following output is an example of router ARP table information, and Output fields: ARP describes the output fields.
Sample output*B:7710-Red-RR# show router arp
===============================================================================
ARP Table (Router: Base)
===============================================================================
IP Address MAC Address Expiry Type Interface
-------------------------------------------------------------------------------
10.20.1.24 00:16:4d:23:91:b8 00h00m00s Oth system
10.10.4.11 00:03:fa:00:d0:c9 00h57m03s Dyn[I] to-core-sr1
10.10.4.24 00:03:fa:41:8d:20 00h00m00s Oth[I] to-core-sr1
-------------------------------------------------------------------------------
No. of ARP Entries: 3
===============================================================================
Label |
Description |
---|---|
IP Address |
Displays the IP address of the ARP entry |
MAC Address |
Displays the MAC address of the ARP entry |
Expiry |
Displays the age of the ARP entry |
Type |
Dyn — The ARP entry is a dynamic ARP entry Inv — The ARP entry is an inactive static ARP entry (invalid) Oth — The ARP entry is a local or system ARP entry Sta — The ARP entry is an active static ARP entry |
Int |
Specifies that the ARP entry is an internal ARP entry |
[I} |
Specifies that the ARP entry is in use |
Interface |
Displays the IP interface name associated with the ARP entry |
No. of ARP Entries |
Displays the number of ARP entries displayed in the list |
neighbor
Syntax
neighbor [ip-int-name | ip-address | mac ieee-mac-address | summary] [dynamic | static | managed]
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
Description
This command displays information about the IPv6 neighbor cache.
Parameters
- ip-int-name
Specifies the IP interface name.
- ip-address
Specifies the address of the IPv6 interface address.
- mac ieee-mac-address
Specify the MAC address.
- summary
Displays summary neighbor information.
- dynamic
Specifies that the IPv6 neighbor entry is a dynamic neighbor entry.
- static
Specifies that the IPv6 neighbor entry is an active static neighbor entry.
- managed
Specifies that the IPv6 neighbor entry is a managed neighbor entry.
Output
The following output is an example of neighbor information, and Output fields: neighbor describes the output fields.
Sample output*A:Dut-A>config>router# show router neighbor
===============================================================================
Neighbor Table (Router: Base)
===============================================================================
IPv6 Address Interface
MAC Address State Expiry Type RTR
-------------------------------------------------------------------------------
2001:db8::5 A_to_B2_17
00:00:1b:00:00:01 REACHABLE - Static No
2001:db8::2 A_to_B2_23
e4:81:84:24:1d:6c STALE 01h12m35s Dynamic Yes
-------------------------------------------------------------------------------
No. of Neighbor Entries: 2
===============================================================================
*A:Dut-A>config>router# show router neighbor dynamic
===============================================================================
Neighbor Table (Router: Base)
===============================================================================
IPv6 Address Interface
MAC Address State Expiry Type RTR
-------------------------------------------------------------------------------
2001:db8::2 A_to_B2_23
e4:81:84:24:1d:6c STALE 01h12m27s Dynamic Yes
-------------------------------------------------------------------------------
No. of Neighbor Entries: 1
===============================================================================
*A:Dut-A>config>router#
*A:Dut-A>config>router# show router neighbor static
===============================================================================
Neighbor Table (Router: Base)
===============================================================================
IPv6 Address Interface
MAC Address State Expiry Type RTR
-------------------------------------------------------------------------------
2001:db8::5 A_to_B2_17
00:00:1b:00:00:01 REACHABLE - Static No
-------------------------------------------------------------------------------
No. of Neighbor Entries: 1
===============================================================================
*A:Dut-A>config>router# show router neighbor ma
mac managed
*A:Dut-A>config>router# show router neighbor managed
===============================================================================
Neighbor Table (Router: Base)
===============================================================================
IPv6 Address Interface
MAC Address State Expiry Type RTR
Label |
Description |
---|---|
IPv6 Address |
Displays the IPv6 address |
Interface |
Displays the name of the IPv6 interface name |
MAC Address |
Specifies the link-layer address |
State |
Displays the current administrative state |
Exp |
Displays the number of seconds until the entry expires |
Type |
Displays the type of IPv6 interface |
Interface |
Displays the interface name |
Rtr |
Specifies whether a neighbor is a router |
Dynamic |
The Ipv6 neighbor entry is a dynamic neighbor entry |
Static |
The Ipv6 neighbor entry is an active static neighbor entry |
Managed |
The Ipv6 neighbor entry is a managed neighbor entry |
Mtu |
Displays the MTU size |
dhcp
Syntax
dhcp
Context
show>router
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays DHCP information for the specified service.
local-dhcp-server
Syntax
local-dhcp-server server-name
Context
show>router>dhcp
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays local DHCP or DHCP 6server information.
Parameters
- server-name
Specifies information about the local DHCP server.
declined-addresses
Syntax
declined-addresses ip-address[/mask] [detail]
declined-addresses pool pool-name
Context
show>router>dhcp>server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays information about declined addresses.
Parameters
- pool pool-name
Specifies a DHCP pool name on the router.
- ip-address
Specifies the IP address of the DNS server. This address must be unique within the subnet and specified in dotted-decimal notation.
- mask
Specifies the subnet mask in Classless Inter-Domain Routing (CIDR) notation, expressed as a decimal integer.
- detail
Displays detailed information.
Output
The following output is an example of declined addresses information, and Output fields: declined addresses describes the output fields.
Sample output*A:ALA-48>show>router>dhcp>server# declined-addresses pool test
===============================================================================
Declined addresses for server test Base
===============================================================================
Pool Subnet IP Address
PPPoe User Name/ Time MAC Address Type
Option 82 Circuit ID
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
*A:ALA-48>show>router>dhcp>server#
Label |
Description |
---|---|
Pool |
Displays the name of the DHCP address pool |
PPoe User Name/Option 82 Circuit ID |
Displays the PPoE username or Option 82 circuit ID |
Subnet |
Displays the subnet of the DHCP address pool |
Time |
Displays the time that the address was declined |
IP Address |
Displays the declined IP address |
MAC Address |
Displays the declined MAC address |
Type |
Displays the type of pool |
free-addresses
Syntax
free-addresses ip-address[/mask]
free-addresses summary [subnet ip-address[/mask]
free-addresses pool pool-name
Context
show>router>dhcp>local-dhcp-server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays the free addresses in a subnet.
Parameters
- pool pool-name
Specifies a DHCP pool name on the router.
- subnet subnet
Specifies a subnet of IP addresses that are served from the pool.
- summary
Displays summary output of the free addresses.
Output
The following output is an example of free addresses information, and Output fields: free addresses describes the output fields.
Sample output*A:ALA-48>show>router>dhcp>local-dhcp-server# free-addresses pool test subnet
1.0.0.0/24
===============================================================================
Free addresses in subnet 1.0.0.0/24
===============================================================================
IP Address
-------------------------------------------------------------------------------
No. of free addresses: 0
===============================================================================
*A:ALA-48>show>router>dhcp>local-dhcp-server#
Label |
Description |
---|---|
IP Address |
The free IP address |
No. of free addresses |
Displays the number of free IP addresses |
leases
Syntax
leases [detail]
leases ip-address[/mask] address-from-user-db [detail]
leases ip-address[/mask] dhcp-host dhcp-host-name [detail]
leases ip-address[/mask] [detail]
Context
show>router>dhcp>local-dhcp-server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays the DHCP leases.
Parameters
- ip-address
Specifies the base IP address of the subnet. This address must be unique within the subnet and specified in dotted-decimal notation.
- mask
Specifies the subnet mask, in dotted-decimal notation.
- address-from-user-db [detail]
Displays only leases that have ip-addresses from the local-user-db.
- dhcp-host dhcp-host-name [detail]
Displays all leases that match a certain DHCP host from the local-user-db.
- detail
Displays detailed information of all leases that fall into the indicated subnet.
The command with no parameters will show all leases from the local-user-db.
Output
The following output is an example of DHCP lease information, and Output fields: lease describes the output fields.
Sample output*A:ALA-48>show>router>dhcp>local-dhcp-server# leases ip-address 10.0.0.4
===============================================================================
Leases for DHCP server test router Base
===============================================================================
IP Address Lease State Mac Address Remaining Clnt
PPPoE user name/Opt82 Circuit Id LifeTime Type
-------------------------------------------------------------------------------
No leases found
*A:ALA-48>show>router>dhcp>local-dhcp-server#
Label |
Description |
---|---|
IP Address |
The leased IP address |
PPoE user name/Opt82 Circuit Id |
The PPoE username or Option 82 circuit ID |
Lease State |
The state of the lease. The state can be:
|
Mac Address |
The MAC address |
Remaining LifeTime |
The remaining time left in the lease |
Clnt Type |
The type of client |
server-stats
Syntax
server-stats
Context
show>router>dhcp>server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays DHCP or DHCP6 server statistics.
Output
The following output is an example of server stats information, and Output fields: server statistics describes the output fields.
Sample output*A:SUB-Dut-A# show router dhcp local-dhcp-server dhcpS1 server-stats
==============================================================================
Statistics for DHCP Server dhcpS1 router Base
==============================================================================
Rx Discover Packets : 0
Rx Request Packets : 0
Rx Release Packets : 0
Rx Decline Packets : 0
Rx Inform Packets : 0
Tx Offer Packets : 0
Tx Ack Packets : 0
Tx Nak Packets : 0
Tx Forcerenew Packets : 0
Client Ignored Offers : 0
Leases Timed Out : 0
Dropped Bad Packet : 0
Dropped Invalid Type : 0
Dropped No User Database : 0
Dropped Unknown Host : 0
Dropped User Not Allowed : 0
Dropped Lease Not Ready : 0
Dropped Lease Not Found : 0
Dropped Not Serving Pool : 0
Dropped Invalid User : 0
Dropped Overload : 0
Dropped Persistence Overload : 0
Dropped Generic Error : 0
Dropped Destined To Other : 0
Dropped Address Unavailable : 0
Dropped Max Leases Reached : 0
Dropped Server Shutdown : 0
Dropped No Subnet For Fixed IP: 0
==============================================================================
*A:SUB-Dut-A#
Label |
Description |
---|---|
Rx Discover Packets |
The number of DHCPDISCOVER (option 53 with value 1) packets received by the DHCP server |
Rx Request Packets |
The number of DHCPREQUEST (option 53 with value 3) packets received by the DHCP server |
Rx Release Packets |
The number of DHCPRELEASE (option 53 with value 7) packets received by the DHCP server |
Rx Decline Packets |
The number of DHCPDECLINE (option 53 with value 4) packets received by the DHCP server |
Rx Inform Packets |
The number of DHCPINFORM (option 53 with value 8) packets received by the DHCP server |
Tx Offer Packets |
The number of DHCPOFFER (option 53 with value 2) packets sent by the DHCP server |
Tx Ack Packets |
The number of DHCPACK (option 53 with value 5) packets sent by the DHCP server |
Tx Nak Packets |
The number of DHCPNAK (option 53 with value 6) packets sent by the DHCP server |
Tx Forcerenew Packets |
The number of DHCPFORCERENEW (option 53 with value 9) packets sent by the DHCP server |
Client Ignored Offers |
The number of DHCPOFFER (option 52 with value 2) packets sent by the DHCP server that were ignored by the clients |
Leases Timed Out |
The number of DHCP leases that timed out without renewal |
Dropped Bad Packet |
The number of DHCP packets received that were corrupt |
Dropped Invalid Type |
The number of DHCP packets received that had an invalid message type (option 53) |
Dropped No User Database |
The number of DHCP packets dropped because the user-db value of the server was not equal to the default value and a local user database with that name could not be found |
Dropped Unknown Host |
The number of DHCP packets dropped from hosts that were not found in the user database when use-gi-address was disabled |
Dropped User Not Allowed |
The number of DHCP packets dropped from hosts, which have no specified address or pool, that were found in the user database while use-gi-address was disabled |
Dropped Lease Not Ready |
The number of DHCP packets dropped by the server before the lease database was ready |
Dropped Lease Not Found |
The number of DHCP packets dropped by the server because no valid lease was found |
Dropped Not Serving Pool |
The number of DHCP packets dropped by the server because there were no free addresses in the pool |
Dropped Invalid User |
The number of DHCP packets dropped by the server because the MAC address of the sender or the Option 82 did not match the host lease state |
Dropped Overload |
The number of DHCP packets dropped by the server because they were received in excess of what the server can process |
Dropped Persistence Overload |
The number of DHCP packets dropped by the server because they were received in excess of what the DHCP persistence system can process. If this occurs, only releases and declines are processed. |
Dropped Generic Error |
The number of DHCP packets dropped by the server because of a generic error |
Dropped Destined to Other |
The number of DHCP requests dropped by the server because the broadcast request was not addressed to this server |
Dropped Address Unavailable |
The number of DHCP requests dropped by the server because the requested address is not available |
Dropped Max Leases Reached |
The number of DHCP packets dropped by the server because the maximum number of leases was reached |
Dropped Server Shutdown |
The number of DHCP packets dropped by the server during server shutdown |
Dropped No Subnet For Fixed IP |
The number of DHCP packets dropped by the server for user-db hosts with a fixed address because the subnet to which the address belongs is not configured |
Dropped Duplicate From Diff GI |
The number of DHCP requests dropped by the server because they were received from a different Gateway IP address within an interval of 10 s after the previous DHCP request |
subnet-ext-stats
Syntax
subnet-ext-stats ip-address[/mask]
subnet-ext-stats pool pool-name
Context
show>router>dhcp>server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays extended statistics per DHCPv4 subnet in local DHCPv4 server.
The following statistics are included in the output:
the number of stable leases in the subnet
the number of provisioned address in the subnet
the number of used address in the subnet
the number of free address in the subnet
the percentage of used address
the percentage of free address
For each statistic (except for provisioned addresses), there is current value and peak value, peak value is the highest value since subnet creation or last reset via the clear router rt-id dhcp local-dhcp-server svr-name subnet-ext-stats command.
When parameter pool is used, the statistics of each subnet in the pool will be displayed.
Parameters
- ip-address[/mask]
Specifies the subnet.
- pool-name
Specifies the name of local DHCPv4 server pool.
Output
The following output is an example of subnet extended statistics information, and Output fields: subnet extended statistics describes the output fields.
Sample outputshow router 500 dhcp local-dhcp-server "d4" subnet-ext-stats 10.10.10.0/24
===============================================================================
Extended statistics for subnet 10.10.10.0/24
===============================================================================
Current Peak TimeStamp
-------------------------------------------------------------------------------
Local:
Stable Leases 1 1 01/07/2013 19:38:36
Provisioned Addresses 101
Used Addresses 1 1 01/07/2013 19:38:36
Free Addresses 100 100 01/07/2013 19:38:36
Used Pct 1 1 01/07/2013 19:38:36
Free Pct 99 99 01/07/2013 19:38:36
Last Reset Time 01/07/2013 19:07:11
-------------------------------------------------------------------------------
Number of entries 1
===============================================================================
Label |
Description |
---|---|
Current |
The current value of the statistic |
Peak |
The highest value reached by the statistic since subnet creation or the last subnet statistics clearing operation |
TimeStamp |
The date and time of the current statistics capture |
Offered Leases |
The number of leases offered from the subnet |
Stable Leases |
The number of stable leases in the subnet |
Provisioned Addresses |
The number of provisioned addresses in the subnet |
Used Addresses |
The number of used addresses in the subnet |
Free Addresses |
The number of free addresses in the subnet |
Used Pct |
The percentage of used addresses in the subnet |
Free Pct |
The percentage of free addresses in the subnet |
Last Reset Time |
The date and time of the last subnet statistics clearing operation |
Number of entries |
The total number of subnet entries |
subnet-stats
Syntax
subnet-stats ip-address[/mask]
subnet-stats pool pool-name
Context
show>router>dhcp>server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays subnet statistics.
Output
The following output is an example of subnet-stats information, and Output fields: subnet statistics describes the output fields.
Sample output*A:SUB-Dut-A# show router dhcp local-dhcp-server dhcpS2 subnet-stats pool POOL2
===============================================================================
Statistics for pool POOL2
===============================================================================
Subnet Free Offered Stable
FRPending RemPending Declined
-------------------------------------------------------------------------------
10.0.0.0/8 16384 0 0
0 0 0
-------------------------------------------------------------------------------
No. of entries: 1
===============================================================================
*A:SUB-Dut-A#
Label |
Description |
---|---|
Subnet |
The subnet of the pool |
Free |
The number of free leases in the subnet |
FRPending |
The number of leases in the subnet that are pending a force renew |
Offered |
The number of offered leases in the subnet |
RemPending |
The number of leases in the subnet that are pending removal |
Stable |
The number of stable leases in the subnet |
Declined |
The number of declined leases in the subnet |
summary
Syntax
summary
Context
show>router>dhcp>server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command displays DHCP server summary information.
Output
The following output is an example of summary information, and Output fields: DHCP server summary describes the output fields.
Sample output*A:SUB-Dut-A# show router dhcp local-dhcp-server dhcpS2 summary
===============================================================================
DHCP server dhcpS2 router Base
===============================================================================
dhcpS2-POOL2
Admin State : inService
Persistency State : ok
User Data Base : N/A
Use gateway IP address : disabled
Send force-renewals : disabled
-------------------------------------------------------------------------------
Pool name : POOL2
-------------------------------------------------------------------------------
Subnet Free Stable Declined Offered Remove-pending
-------------------------------------------------------------------------------
10.0.0.0/8 16384 0 0 0 0
Totals for pool 16384 0 0 0 0
-------------------------------------------------------------------------------
Totals for server 16384 0 0 0 0
-------------------------------------------------------------------------------
Associations Admin
-------------------------------------------------------------------------------
No associations found
===============================================================================
*A:SUB-Dut-A#
*A:vsim-2# show router 500 dhcp local-dhcp-server "d4" summary
===============================================================================
DHCP server d4 router 500
===============================================================================
Admin State : inService
Operational State : inService
Persistency State : shutdown
User Data Base : N/A
Use gateway IP address : enabled (scope subnet)
Use pool from client : disabled
Send force-renewals : disabled
Creation Origin : manual
Lease Hold Time : 0h0m0s
Lease Hold Time For : N/A
User-ident : mac-circuit-id
Failover Admin State : outOfService
Failover Oper State : shutdown
Failover Persist Key : N/A
Administrative MCLT : 0h10m0s
Operational MCLT : 0h10m0s
Startup wait time : 0h2m0s
Partner down delay : 23h59m59s
Ignore MCLT : disabled
-------------------------------------------------------------------------------
Pool name : v4-1
-------------------------------------------------------------------------------
Failover Admin State : inService
Failover Oper State : normal
Failover Persist Key : N/A
Administrative MCLT : 0h10m0s
Operational MCLT : 0h10m0s
Startup wait time : 0h2m0s
Partner down delay : 23h59m59s
Ignore MCLT : disabled
-------------------------------------------------------------------------------
Subnet Free % Stable Declined Offered Rem-pend Drain
-------------------------------------------------------------------------------
10.20.20.0/24 (L) 10 90% 1 0 0 0 N
(R) N/A 0 N/A N/A N/A N
Totals for pool 10 90% 1 0 0 0
-------------------------------------------------------------------------------
Totals for server 10 90% 1 0 0 0
-------------------------------------------------------------------------------
Interface associations
Interface Admin
-------------------------------------------------------------------------------
l1 Up
-------------------------------------------------------------------------------
Local Address Assignment associations
Group interface Admin
-------------------------------------------------------------------------------
===============================================================================
*A:vsim-2#
Label |
Description |
---|---|
Admin State |
The administrative state of the DHCP server |
Persistency State |
The persistence state of the DHCP server |
User Data Base |
Indicates whether the DHCP server uses a user database |
Use gateway IP address |
Indicates whether the DHCP server uses GIADDR |
Send force-renewals |
Indicates whether the DHCP server sends FORCERENEW messages |
Operational State |
The operational state of the DHCPv6 server |
Persistency State |
The persistence state of the DHCPv6 server |
Use Link Address |
Indicates whether use-link-address is enabled, and, if enabled, the scope |
Use pool from client |
Indicates whether use-pool-from-client is enabled |
Creation Origin |
The creation method of the DHCPv6 server |
Lease Hold Time |
The lease retention time configured using the lease-hold-time command |
Lease Hold Time For |
The lease being held by the DHCPv6 server |
User-ident |
The user identification method configured using the user-ident command |
Interface-id-mapping |
Indicates whether interface ID mapping is enabled |
Ignore-rapid-commit |
Indicates whether the DHCPv6 server is configured to ignore rapid committing |
Allow-lease-query |
Indicates whether the DHCPv6 server allows lease query messages |
Pool |
|
Subnet |
The subnet of the pool |
Free |
The number of free IP addresses in the subnet |
Stable |
The number of stable IP addresses in the subnet |
Declined |
The number of declined IP addresses in the subnet |
Offered |
The number of offered IP addresses in the subnet |
Remove-pending |
The number of IP addresses pending removal in the subnet |
Associations |
|
Associations |
The name of the associated interface |
Admin |
The administrative state of the interface |
servers
Syntax
servers
servers all
Context
show>router>dhcp
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command lists the local DHCP servers.
Output
The following output is an example of DHCP server information, and Output fields: DHCP servers describes the output fields.
Sample output*A:ALA-49>show>router>dhcp# servers
=================================================================
Overview of DHCP Servers
=================================================================
Active Leases: 0
Maximum Leases: 159744
Router Server Admin State
-----------------------------------------------------------------
Router: Base base_router_dhcp_server outOfService
Service: 3 s1 inService
=================================================================
*A:ALA-49>show>router>dhcp#
Label |
Description |
---|---|
Active Leases |
The number of active leases |
Maximum Leases |
The maximum number of leases available |
Router |
The name of the router |
Server |
The name of the DHCP or DHCPv6 server |
Admin State |
The administrative state of the DHCP or DHCPv6 server |
statistics
Syntax
statistics [sap sap-id] | [sdp [sdp-id[:vc-id]] | interface ip-int-name]]
Context
show>router>dhcp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays statistics for DHCP relay and DHCP snooping.
If no IP address or interface name is specified, then all configured interfaces are displayed.
If an IP address or interface name is specified, then only data regarding the specified interface is displayed.
Parameters
- sap-id
Specifies the physical port identifier portion of the SAP definition.
- sdp-id
Specifies the SDP ID to be shown.
- vc-id
Specifies the virtual circuit ID on the ID to be shown.
- ip-int-name | ip-address
Displays statistics for the specified IP interface.
Output
The following output is an example of DHCP statistics information, and Output fields: DHCP statistics describes the output fields.
Sample outputA:ALA-A# show router 1000 dhcp statistics
===================================================================
DHCP Global Statistics (Service: 1000)
===================================================================
Rx Packets : 16000
Tx Packets : 15041
Rx Malformed Packets : 0
Rx Untrusted Packets : 0
Client Packets Discarded : 423
Client Packets Relayed : 0
Client Packets Snooped : 0
Client Packets Proxied (RADIUS) : 0
Client Packets Proxied (Lease-Split) : 0
Server Packets Discarded : 0
Server Packets Relayed : 0
Server Packets Snooped : 0
DHCP RELEASEs Spoofed : 0
DHCP FORCERENEWs Spoofed : 0
===================================================================
A:ALA-A#
Label |
Description |
---|---|
Received Packets |
The number of packets received from the DHCP clients |
Transmitted Packets |
The number of packets transmitted to the DHCP clients |
Received Malformed Packets |
The number of malformed packets received from the DHCP clients |
Received Untrusted Packets |
The number of untrusted packets received from the DHCP clients |
Client Packets Discarded |
The number of packets received from the DHCP clients that were discarded |
Client Packets Relayed |
The number of packets received from the DHCP clients that were forwarded |
Client Packets Snooped |
The number of packets received from the DHCP clients that were snooped |
Server Packets Discarded |
The number of packets received from the DHCP server that were discarded |
Server Packets Relayed |
The number of packets received from the DHCP server that were forwarded |
Server Packets Snooped |
The number of packets received from the DHCP server that were snooped |
summary
Syntax
summary
Context
show>router>dhcp
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays the status of the DHCP relay and DHCP snooping functions on each interface.
Output
The following output is an example of DHCP summary information, and Output fields: DHCP summary describes the output fields.
Sample outputA:ALA-48>show>router>dhcp# summary
===================================================================
Interface Name Arp Used/ Info Admin
Populate Provided Option State
-------------------------------------------------------------------
ccaiesif No 0/0 Keep Down
ccanet6 No 0/0 Keep Down
iesBundle No 0/0 Keep Up
spokeSDP-test No 0/0 Keep Down
test No 0/0 Keep Up
test1 No 0/0 Keep Up
test2 No 0/0 Keep Up
testA No 0/0 Keep Up
testB No 0/0 Keep Up
testIES No 0/0 Keep Up
to-web No 0/0 Keep Up
-------------------------------------------------------------------
Interfaces: 11
===================================================================
A:ALA-48>show>router>dhcp#
*A:vsim-2# show router 500 dhcp summary
===============================================================================
DHCP Summary (Service: 500)
===============================================================================
Interface Name Arp Leases Per Interface/ Info Admin
SapId/Sdp Populate Per Sap Limit Option State
-------------------------------------------------------------------------------
g1 No 1/1 Keep Up
sap:1/1/7 1/1
l1 No 0/0 Keep Down
-------------------------------------------------------------------------------
Interfaces: 2
===============================================================================
*A:vsim-2#
Label |
Description |
---|---|
Interface Name |
Name of the router interface |
ARP Populate |
Indicates whether ARP populate is enabled |
Used/Provided |
Indicates the number of used and provided DHCP leases |
Info Option |
Indicates whether Option 82 processing is enabled on the interface |
Admin State |
Indicates the administrative state |
statistics
Syntax
statistics interface [ip-int-name | ip-address]
Context
show>router>dhcp
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command isplays DHCP statistics information.
Parameters
- ip-int-name | ip-address
Displays statistics for the specified IP interface.
Output
The following output is an example of DHCP statistics information, and Output fields: DHCP statistics describes the output fields.
Sample output*A:7210SAS>show>router>dhcp# statistics
====================================================================
DHCP Global Statistics, service 1
====================================================================
Rx Packets : 416554
Tx Packets : 206405
Rx Malformed Packets : 0
Rx Untrusted Packets : 0
Client Packets Discarded : 0
Client Packets Relayed : 221099
Client Packets Snooped : 0
Client Packets Proxied (RADIUS) : 0
Client Packets Proxied (Lease-Split) : 0
Server Packets Discarded : 0
Server Packets Relayed : 195455
Server Packets Snooped : 0
DHCP RELEASEs Spoofed : 0
DHCP FORCERENEWs Spoofed : 0
====================================================================
*A:7210SAS>show>service>id>dhcp#
Label |
Description |
---|---|
Received Packets |
The number of packets received from the DHCP clients. Includes DHCP packets received from both DHCP client and DHCP server. |
Transmitted Packets |
The number of packets transmitted to the DHCP clients. Includes DHCP packets transmitted from both DHCP client and DHCP server. |
Received Malformed Packets |
The number of corrupted/invalid packets received from the DHCP clients. Includes DHCP packets received from both DHCP client and DHCP server. |
Received Untrusted Packets |
The number of untrusted packets received from the DHCP clients. In this case, a frame is dropped due to the client sending a DHCP packet with Option 82 filled in before ‟trust” is set under the DHCP interface command. |
Client Packets Discarded |
The number of packets received from the DHCP clients that were discarded |
Client Packets Relayed |
The number of packets received from the DHCP clients that were forwarded |
Client Packets Snooped |
The number of packets received from the DHCP clients that were snooped |
Server Packets Discarded |
The number of packets received from the DHCP server that were discarded |
Server Packets Relayed |
The number of packets received from the DHCP server that were forwarded |
Server Packets Snooped |
The number of packets received from the DHCP server that were snooped |
ecmp
Syntax
ecmp
Context
show>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command displays the ECMP settings for the router.
Weighted ECMP appears in the show output but is not supported on 7210 SAS platforms.
Output
The following output is an example of ECMP settings information, and Output fields: router ECMP describes the output fields.
Sample output*A:dut-d>show>router# ecmp
===============================================================================
Router ECMP
===============================================================================
Instance Router Name ECMP Max-ECMP- Weight ECMP
Rtes
-------------------------------------------------------------------------------
1 Base False n/a False
===============================================================================
*A:dut-d>show>router#
Label |
Description |
---|---|
Instance |
Displays the router instance number |
Router Name |
Displays the name of the router instance |
ECMP |
False — ECMP is disabled for the instance True — ECMP is enabled for the instance |
Max-ECMP-Rtes |
Displays the maximum amount of routes to be considered for ECMP |
Weight ECMP |
False — Weighted ECMP is disabled |
fib
Syntax
fib slot-number [family] [ip-prefix/prefix-length] [longer] [secondary]
fib slot-number [family] summary
fib slot-number [family] [nh-table-usage]
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
This command displays the active FIB entries for a specific IOM.
Parameters
- slot-number
Displays only the routes matching the specified chassis slot number.
- family
Displays the router IP interface table for the specified family.
- ip-prefix/prefix-length
Displays FIB entries matching only the specified ip-prefix and prefix-length.
- longer
Displays FIB entries matching the ip-prefix/prefix-length and routes with longer masks.
- secondary
Displays secondary FIB information.
- summary
Displays summary FIB information for the specified slot number.
- nh-table-usage
Displays next-hop table usage.
Output
The following output is an example of FIB BGP PIC information, and Output fields: FIB BGP PIC describes the output fields.
Sample outputThe following output applies to the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C only.
*A:Dut-A# show router fib 1 10.77.77.77/32
===============================================================================
FIB Display
===============================================================================
Prefix [Flags] Protocol
NextHop
-------------------------------------------------------------------------------
10.77.77.77/32 BGP
2.2.2.2 (Transport:LDP)
3.3.3.3 (Transport:LDP)
-------------------------------------------------------------------------------
Total Entries : 1
-------------------------------------------------------------------------------
===============================================================================
*A:Dut-A#
Label |
Description |
---|---|
Prefix[Flags] |
The route destination address and mask |
Protocol |
The active protocol (LOCAL, STATIC, OSPF, IS-IS, AGGREGATE, BGP, RIP, or BGP-VPN) |
Next Hop |
The next-hop or indirect next-hop IP address for the route destination |
Total Entries |
The total number of next-hop entries |
icmp6
Syntax
icmp6
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
Description
This command displays ICMPv6 statistics. ICMPv6 generates error messages to report errors during processing and other diagnostic functions. ICMPv6 packets can be used in the neighbor discovery protocol.
Output
The following output is an example of ICMP6 information, and Output fields: ICMP6 describes the output fields.
Sample outputA:SR-3>show>router>auth# show router icmp6
===============================================================================
Global ICMPv6 Stats
===============================================================================
Received
Total : 14 Errors : 0
Destination Unreachable : 5 Redirects : 5
Time Exceeded : 0 Pkt Too Big : 0
Echo Request : 0 Echo Reply : 0
Router Solicits : 0 Router Advertisements : 4
Neighbor Solicits : 0 Neighbor Advertisements : 0
-------------------------------------------------------------------------------
Sent
Total : 10 Errors : 0
Destination Unreachable : 0 Redirects : 0
Time Exceeded : 0 Pkt Too Big : 0
Echo Request : 0 Echo Reply : 0
Router Solicits : 0 Router Advertisements : 0
Neighbor Solicits : 5 Neighbor Advertisements : 5
===============================================================================
A:SR-3>show>router>auth#
Label |
Description |
---|---|
Total |
The total number of all messages |
Destination Unreachable |
The number of message that did not reach the destination |
Time Exceeded |
The number of messages that exceeded the time threshold |
Echo Request |
The number of echo requests |
Router Solicits |
The number of times the local router was solicited |
Neighbor Solicits |
The number of times the neighbor router was solicited |
Errors |
The number of error messages |
Redirects |
The number of packet redirects |
Pkt Too big |
The number of packets that exceed appropriate size |
Echo Reply |
The number of echo replies |
Router Advertisements |
The number of times the router advertised its location |
Neighbor Advertisements |
The number of times the neighbor router advertised its location |
interface
Syntax
interface [interface-name]
Context
show>router>icmp6
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
Description
This command displays ICMPv6 statistics for a specified interface. If the interface-name parameter is not entered, ICMPv6 statistics for all interfaces are displayed.
Parameters
- interface-name
Displays entries associated with the specified IP interface name.
Output
Output fields: ICMP6 interface describes the router ICMP6 interface output fields.
Label |
Description |
---|---|
Total |
The total number of all messages |
Destination Unreachable |
The number of message that did not reach the destination |
Time Exceeded |
The number of messages that exceeded the time threshold |
Echo Request |
The number of echo requests |
Router Solicits |
The number of times the local router was solicited |
Neighbor Solicits |
The number of times the neighbor router was solicited |
Errors |
The number of error messages |
Redirects |
The number of packet redirects |
Pkt Too big |
The number of packets that exceed appropriate size |
Echo Reply |
The number of echo replies |
Router Advertisements |
The number of times the router advertised its location |
Neighbor Advertisements |
The number of times the neighbor router advertised its location |
interface
Syntax
interface [{[ip-address | ip-int-name] [detail] [family]} | [summary] | [exclude-services]
interface [ip-address | ip-int-name] statistics
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 2F1C2T, and 7210 SAS-K 3SFP+ 8C.
Description
This command displays the router IP interface table sorted by interface index.
The 7210 SAS-K 2F6C4T does not support IPv6 parameters and options.
Parameters
- ip-address
Displays only the interface information associated with the specified IP address.
- ip-int-name
Only displays the interface information associated with the specified IP interface name.
- detail
Displays detailed IP interface information.
- family
Displays information for the specified IP interface family.
- summary
Displays summary IP interface information.
- exclude-services
Displays IP interface information, excluding IP interfaces configured for customer services. Only core network IP interfaces are displayed.
- statistics
Displays the number of transmitted, received, and discarded packets and bytes at the Layer 3 level for IP interface statistics. The collection of IP interface statistics is supported on any IP interface, regardless of encapsulation. Supported IP interfaces are access (IES, VPRN, routed VPLS, and spoke SDP) and network (IPv4, IPv6, and MPLS) interfaces. Discard statistics are only displayed for IPv4 interfaces.
Output
The following outputs are examples of router IP interface information. The associated tables describe the output fields.
Standard output: Sample output, Output fields: router interface
Detailed output: Sample output — detailed, Output fields: router interface detail
A:ALU-7210# show router interface
===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up Network system
10.22.24.169/32 n/a
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
A:ALU-7210#
A:ALA-A# show router interface 10.6.6.2
===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
to-PE-E Up Up IES 1/1/3:0.*
10.6.6.2/24 n/a
-------------------------------------------------------------------------------
Interfaces : 1
===============================================================================
A:ALA-A#
Label |
Description |
---|---|
Interface-Name |
The IP interface name |
Type |
n/a — No IP address has been assigned to the IP interface, so the IP address type is not applicable Pri — The IP address for the IP interface is the Primary address on the IP interface |
IP-Address |
The IP address and subnet mask length of the IP interface. n/a — Indicates no IP address has been assigned to the IP interface |
Adm |
Down — The IP interface is administratively disabled Up — The IP interface is administratively enabled |
Opr |
Down — The IP interface is operationally disabled Up — The IP interface is operationally disabled |
Mode |
Network — The IP interface is a network/core IP interface |
Port |
The physical network port associated with the IP interface |
A:SIM7# show router interface tosim6 detail
===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface
-------------------------------------------------------------------------------
If Name : tosim6
Admin State : Up Oper State : Up
Protocols : None
IP Addr/mask : 10.0.0.7/24 Address Type : Primary
IGP Inhibit : Disabled Broadcast Address: Host-ones
-------------------------------------------------------------------------------
Details
-------------------------------------------------------------------------------
If Index : 5 Virt. If Index : 5
Last Oper Chg: 01/09/2009 03:30:15 Global If Index : 4
SAP Id : 1/1/2:0.*
TOS Marking : Untrusted If Type : IES
SNTP B.Cast : False IES ID : 100
MAC Address : 2e:59:01:01:00:02 Arp Timeout : 14400
IP MTU : 1500 Arp Timeout : 14400
ICMP Details
Redirects : Number - 100 Time (seconds) - 10
Unreachables : Number - 100 Time (seconds) - 10
TTL Expired : Number - 100 Time (seconds) - 10
===============================================================================
A:SIM7#
*A:Dut-C# show router 1 mvpn
===============================================================================
MVPN 1 configuration data
===============================================================================
signaling : Bgp auto-discovery : Enabled
UMH Selection : Highest-Ip intersite-shared : Enabled
vrf-import : N/A
vrf-export : N/A
vrf-target : target:1:1
C-Mcast Import RT : target:10.20.1.3:2
ipmsi : pim-asm 224.1.1.1
admin status : Up three-way-hello : N/A
hello-interval : N/A hello-multiplier : 35 * 0.1
tracking support : Disabled Improved Assert : N/A
spmsi : pim-ssm 225.0.0.0/32
join-tlv-packing : N/A
data-delay-interval: 3 seconds
data-threshold : 224.0.0.0/4 --> 1 kbps
===============================================================================
Label |
Description |
---|---|
If Name |
The IP interface name |
Admin State |
Down — The IP interface is administratively disabled Up — The IP interface is administratively enabled |
Oper State |
Down — The IP interface is operationally disabled Up — The IP interface is operationally enabled |
IP Addr/ mask |
The IP address and subnet mask length of the IP interface. Not Assigned — Indicates no IP address has been assigned to the IP interface |
If Index |
The interface index of the IP router interface |
Virt If Index |
The virtual interface index of the IP router interface |
Last Oper Change |
The last change in operational status |
Global If Index |
The global interface index of the IP router interface |
If Type |
Network — The IP interface is a network/core IP interface |
SNTP B.cast |
Displays if the broadcast-client global parameter is configured |
QoS Policy |
The QoS policy ID associated with the IP interface |
MAC Address |
The MAC address of the interface |
Arp Timeout |
The ARP timeout for the interface, in seconds, which is the time an ARP entry is maintained in the ARP cache without being refreshed |
route-table
Syntax
route-table [family] [ip-prefix [prefix-length] [longer | exact] | [protocol protocol name | [summary]
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
Description
7210 SAS-K 2F6C4T does not support the IPv6 parameters and options.
This command displays the active routes in the routing table.
If no command line arguments are specified, all routes are displayed, sorted by prefix.
Parameters
- family
Displays information for the specified IP interface family.
- ip-prefix/prefix-length
Displays only those entries matching the specified IP prefix and prefix length.
- longer
Displays routes matching the ip-prefix/prefix-length and routes with longer masks.
- exact
Displays the exact route matching the ip-prefix/prefix-length masks.
- protocol name
Displays routes learned from the specified protocol.
- summary
Displays a route table summary information.
Output
The following outputs are examples of route table information. The associated tables describe the output fields.
Standard output: Sample output, Output fields: route table
Summary output: Sample output — summary, Output fields: route table summary
Summary output: Sample output — BGP PIC, Output fields: route-table BGP PIC
A:ALA# show router route-table
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
----------------------------------------------------------------------------------
10.1.1.1/32 Remote Static 00h22m29s 5
6.6.6.1 1
10.2.2.2/32 Local Local 00h22m52s 0
system 0
10.5.5.0/24 Remote Static 00h22m29s 5
6.6.6.1 1
10.6.6.0/24 Local Local 00h22m30s 0
to-PE-E 0
-----------------------------------------------------------------------------------
No. of Routes: 4
===============================================================================
A:ALA#
B:ALA-B# show router route-table 10.10.0.0 exact
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Address Next Hop Type Proto Age Metric Pref
-------------------------------------------------------------------------------
10.10.0.0/16 Black Hole Remote Static 00h03m17s 1 5
-------------------------------------------------------------------------------
No. of Routes: 1
===============================================================================
B:ALA-B#
Label |
Description |
---|---|
Dest Address |
The route destination address and mask |
Next Hop |
The next hop IP address for the route destination |
Type |
Local — The route is a local route Remote — The route is a remote route |
Protocol |
The protocol through which the route was learned |
Age |
The route age in seconds for the route |
Metric |
The route metric value for the route |
Pref |
The route preference value for the route |
A:ALA-A# show router route-table summary
===============================================================================
Route Table Summary
===============================================================================
Active Available
-------------------------------------------------------------------------------
Static 1 1
Direct 6 6
-------------------------------------------------------------------------------
Total 7 7
===============================================================================
A:ALA-A#
Label |
Description |
---|---|
Active |
The number of installed active routes in the FIB |
Available |
The number of uninstalled routes available in the RIB |
Static |
The number of static routes in the FIB |
Direct |
The number of direct routes (local subnets, including loopback) in the routing FIB |
Total |
The total number of routes |
The following output applies to the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C only.
*A:Dut-A# show router route-table 10.77.77.77/32
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.77.77.77/32 [B] Remote BGP 00h01m04s 170
2.2.2.2 (tunneled) 0
-------------------------------------------------------------------------------
No. of Routes: 1
Flags: n = Number of times nexthop is repeated
B = BGP backup route available
L = LFA nexthop available
S = Sticky ECMP requested
===============================================================================
*A:Dut-A# show router route-table 10.77.77.77/32 alternative
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix[Flags] Type Proto Age Pref
Next Hop[Interface Name] Metric
Alt-NextHop Alt-
Metric
-------------------------------------------------------------------------------
10.77.77.77/32 Remote BGP 00h01m09s 170
2.2.2.2 (tunneled) 0
10.77.77.77/32 (Backup) Remote BGP 00h01m09s 170
3.3.3.3 (tunneled) 0
-------------------------------------------------------------------------------
No. of Routes: 2
Flags: n = Number of times nexthop is repeated
Backup = BGP backup route
LFA = Loop-Free Alternate nexthop
S = Sticky ECMP requested
===============================================================================
Label |
Description |
---|---|
Dest Prefix |
The route destination address and mask |
[Flags] |
n — Number of times nexthop is repeated B — BGP backup route L — Loop-free alternate next hop S — Sticky ECMP requested |
Next Hop |
The next-hop IP address for the route destination |
Type |
Local — the route is a local route Remote — the route is a remote route |
Proto |
The protocol through which the route was learned |
Age |
The route age in seconds for the route |
Metric |
The route metric value for the route |
Pref |
The route preference value for the route |
No. of Routes |
The number of routes displayed in the list |
Alt-NextHop |
The LFA next hop to use if the primary next hop is not reachable |
Alt-Metric |
The metric value for secondary next hops |
rtr-advertisement
Syntax
rtr-advertisement [interface interface-name] [prefix ipv6-prefix[/prefix-length]]
Context
show>router
Platforms
7210 SAS-Dxp, 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command displays IPv6 router advertisement information.
If no command line arguments are specified, all IPv6 router advertisement information is displayed, sorted by prefix.
Parameters
- ip-int-name
Only displays the router advertisement information associated with the specified IP interface name.
- family
Displays information for the specified IP interface family.
- ipv6-prefix/prefix-length
Displays only those entries matching the specified IPv6 prefix and prefix length.
Output
The following output is an example of router advertisement information, and Output fields: router advertisement describes the output fields.
Sample outputA:7210SAS# show router rtr-advertisement
=======================================================================
Router Advertisement
=======================================================================
-------------------------------------------------------------------------------
Interface: interfaceNetworkNonDefault
-------------------------------------------------------------------------------
Rtr Advertisement Tx : 8 Last Sent : 00h01m28s
Nbr Solicitation Tx : 83 Last Sent : 00h00m17s
Nbr Advertisement Tx : 74 Last Sent : 00h00m25s
Rtr Advertisement Rx : 8 Rtr Solicitation Rx : 0
Nbr Advertisement Rx : 83 Nbr Solicitation Rx : 74
-------------------------------------------------------------------------------
Max Advert Interval : 601 Min Advert Interval : 201
Managed Config : TRUE Other Config : TRUE
Reachable Time : 00h00m00s400ms Router Lifetime : 00h30m01s
Retransmit Time : 00h00m00s400ms Hop Limit : 63
Link MTU : 1500
Prefix: 211::/120
Autonomous Flag : FALSE On-link flag : FALSE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
Prefix: 231::/120
Autonomous Flag : FALSE On-link flag : FALSE
Preferred Lifetime : 49710d06h Valid Lifetime : 49710d06h
Prefix: 241::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 00h00m00s Valid Lifetime : 00h00m00s
Prefix: 251::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
-------------------------------------------------------------------------------
Advertisement from: FE80::200:FF:FE00:2
Managed Config : FALSE Other Config : FALSE
Reachable Time : 00h00m00s0ms Router Lifetime : 00h30m00s
Retransmit Time : 00h00m00s0ms Hop Limit : 64
Link MTU : 0
-------------------------------------------------------------------------------
Interface: interfaceServiceNonDefault
-------------------------------------------------------------------------------
Rtr Advertisement Tx : 8 Last Sent : 00h06m41s
Nbr Solicitation Tx : 166 Last Sent : 00h00m04s
Nbr Advertisement Tx : 143 Last Sent : 00h00m05s
Rtr Advertisement Rx : 8 Rtr Solicitation Rx : 0
Nbr Advertisement Rx : 166 Nbr Solicitation Rx : 143
-------------------------------------------------------------------------------
Max Advert Interval : 601 Min Advert Interval : 201
Managed Config : TRUE Other Config : TRUE
Reachable Time : 00h00m00s400ms Router Lifetime : 00h30m01s
Retransmit Time : 00h00m00s400ms Hop Limit : 63
Link MTU : 1500
Prefix: 23::/120
Autonomous Flag : FALSE On-link flag : FALSE
Preferred Lifetime : infinite Valid Lifetime : infinite
Prefix: 24::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 00h00m00s Valid Lifetime : 00h00m00s
Prefix: 25::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
-------------------------------------------------------------------------------
Advertisement from: FE80::200:FF:FE00:2
Managed Config : FALSE Other Config : FALSE
Reachable Time : 00h00m00s0ms Router Lifetime : 00h30m00s
Retransmit Time : 00h00m00s0ms Hop Limit : 64
Link MTU : 0
Prefix: 2::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
Prefix: 23::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
Prefix: 24::/119
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
Prefix: 25::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : infinite
Prefix: 231::/120
Autonomous Flag : TRUE On-link flag : TRUE
Preferred Lifetime : 07d00h00m Valid Lifetime : 30d00h00m
-------------------------------------------------------------------------------
...
A:7210SAS#
Label |
Description |
---|---|
Rtr Advertisement Tx/Last Sent |
The number of router advertisements sent and time since they were sent |
Nbr Solicitation Tx |
The number of neighbor solicitations sent and time since they were sent |
Nbr Advertisement Tx |
The number of neighbor advertisements sent and time since they were sent |
Rtr Advertisement Rx |
The number of router advertisements received and time since they were received |
Nbr Advertisement Rx |
The number of neighbor advertisements received and time since they were received |
Max Advert Interval |
The maximum interval between sending router advertisement messages |
Managed Config |
True — Indicates that DHCPv6 is configured |
False — Indicates that DHCPv6 is not available for address configuration |
|
Reachable Time |
The time, in milliseconds, that a node assumes a neighbor is reachable after receiving a reachability confirmation |
Retransmit Time |
The time, in milliseconds, between retransmitted neighbor solicitation messages |
Link MTU |
The MTU number the nodes use for sending packets on the link |
Rtr Solicitation Rx |
The number of router solicitations received and time since they were received |
Nbr Solicitation Rx |
The number of neighbor solicitations received and time since they were received |
Min Advert Interval |
The minimum interval between sending ICMPv6 neighbor discovery router advertisement messages |
Other Config |
True — Indicates there are other stateful configurations |
False — Indicates there are no other stateful configurations |
|
Router Lifetime |
Displays the router lifetime in seconds |
Hop Limit |
Displays the current hop limit |
static-arp
Syntax
static-arp [ip-addr | ip-int-name | mac ieee-mac-addr]
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C.
Description
This command displays the router static ARP table information.
If no command line arguments are specified, all static ARP table information is displayed, sorted by prefix.
Parameters
- ip-addr
Displays only static ARP entries associated with the specified IP address.
- ip-int-name
Displays only static ARP entries associated with the specified IP interface name.
- mac ieee-mac-addr
Displays only static ARP entries associated with the specified MAC address.
Output
The following output is an example of static-arp information, and Output fields: static ARP describes the output fields.
Sample outputA:ALA-A# show router static-arp
===============================================================================
ARP Table
===============================================================================
IP Address MAC Address Age Type Interface
-------------------------------------------------------------------------------
10.200.0.253 00:00:5a:40:00:01 00:00:00 Sta to-ser1
10.200.1.1 00:00:5a:01:00:33 00:00:00 Inv to-ser1a
-------------------------------------------------------------------------------
No. of ARP Entries: 1
===============================================================================
A:ALA-A#
A:ALA-A# show router static-arp 12.200.1.1
===============================================================================
ARP Table
===============================================================================
IP Address MAC Address Age Type Interface
-------------------------------------------------------------------------------
10.200.1.1 00:00:5a:01:00:33 00:00:00 Inv to-ser1
===============================================================================
A:ALA-A#
A:ALA-A# show router static-arp to-ser1
===============================================================================
ARP Table
===============================================================================
IP Address MAC Address Age Type Interface
-------------------------------------------------------------------------------
10.200.0.253 00:00:5a:40:00:01 00:00:00 Sta to-ser1
===============================================================================
A:ALA-A#
A:ALA-A# show router static-arp mac 00:00:5a:40:00:01
===============================================================================
ARP Table
===============================================================================
IP Address MAC Address Age Type Interface
-------------------------------------------------------------------------------
10.200.0.253 00:00:5a:40:00:01 00:00:00 Sta to-ser1
===============================================================================
A:ALA-A#
Label |
Description |
---|---|
IP Address |
The IP address of the static ARP entry |
MAC Address |
The MAC address of the static ARP entry |
Age |
The age of the ARP entry. Static ARPs always have 00:00:00 for the age. |
Type |
Inv — The ARP entry is an inactive static ARP entry (invalid) |
Sta — The ARP entry is an active static ARP entry |
|
Interface |
The IP interface name associated with the ARP entry |
No. of ARP Entries |
The number of ARP entries displayed in the list |
static-route
Syntax
static-route [[ip-prefix /mask] | [preference preference] | [next-hop ip-address| tag tag]
Context
show>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
7210 SAS-K 2F6C4T does not support the IPv6 parameters and options.
This command displays the static entries in the routing table.
If no command line arguments are specified, all static routes information is displayed, sorted by prefix.
Parameters
- ip-prefix/prefix-length
Displays only those entries matching the specified IP prefix and prefix length.
- preference
Displays only static routes with the specified route preference.
- ip-address
Displays only static routes with the specified next hop IP address.
- tag
Displays the tag used to add a 32-bit integer tag to the static route. The tag is used in route policies to control distribution of the route into other protocols.
Output
The following output is an example of static route information, and Output fields: static route describes the output fields.
Sample outputA:ALA-A# show router static-route
===============================================================================
Route Table
===============================================================================
IP Addr/mask Pref Metric Type Nexthop Interface Active
-------------------------------------------------------------------------------
192.168.250.0/24 5 1 ID 10.200.10.1 to-ser1 Y
192.168.252.0/24 5 1 NH 10.10.0.254 n/a N
192.168.253.0/24 5 1 NH to-ser1 n/a N
192.168.253.0/24 5 1 NH 10.10.0.254 n/a N
192.168.254.0/24 4 1 BH black-hole n/a Y
===============================================================================
A:ALA-A#
A:ALA-A# show router static-route 192.168.250.0/24
===============================================================================
Route Table
===============================================================================
IP Addr/mask Pref Metric Type Nexthop Interface Active
-------------------------------------------------------------------------------
192.168.250.0/24 5 1 ID 10.200.10.1 to-ser1 Y
===============================================================================
A:ALA-A#
A:ALA-A# show router static-route preference 4
===============================================================================
Route Table
===============================================================================
IP Addr/mask Pref Metric Type Nexthop Interface Active
-------------------------------------------------------------------------------
192.168.254.0/24 4 1 BH black-hole n/a Y
===============================================================================
A:ALA-A#
A:ALA-A# show router static-route next-hop 10.10.0.254
===============================================================================
Route Table
===============================================================================
IP Addr/mask Pref Metric Type Nexthop Interface Active
-------------------------------------------------------------------------------
192.168.253.0/24 5 1 NH 10.10.0.254 n/a N
===============================================================================
A:ALA-A#
Label |
Description |
---|---|
IP Addr/mask |
The static route destination address and mask |
Pref |
The route preference value for the static route |
Metric |
The route metric value for the static route |
Type |
BH — The static route is a blackhole route. The next hop for this type of route is black hole. |
NH — The route is a static route with a directly connected next hop. The next hop for this type of route is either the next hop IP address or an egress IP interface name. |
|
Next Hop |
The next hop for the static route destination |
Protocol |
The protocol through which the route was learned |
Interface |
The egress IP interface name for the static route n/a — Indicates there is no current egress interface because the static route is inactive or a blackhole route |
Active |
N — The static route is inactive; for example, the static route is disabled or the next hop IP interface is down. |
Y — The static route is active. |
|
No. of Routes |
The number of routes displayed in the list |
status
Syntax
status
Context
show>router
Platforms
Supported on all 7210 SAS platforms as described in this document
7210 SAS-K 2F6C4T does not support the IPv6 parameters and options.
Description
This command displays the router status.
Output
The following output is an example of router status information, and Output fields: router status describes the output fields.
Sample outputA:DUT-B>show>router# show router status
================================================================
Router Status (Router: Base)
================================================================
Admin State Oper State
----------------------------------------------------------------
Router Up Up
Max Routes 10000
Total IPv4 Routes 5
ECMP Max Routes 1
================================================================
A:DUT-B>show>router#
Label |
Description |
---|---|
Router |
The administrative and operational states for the router |
Max Routes |
The maximum number of routes configured for the system |
Total Routes |
The total number of routes in the route table |
tunnel-table
Syntax
tunnel-table summary [ipv4 | ipv6]
tunnel-table [protocol protocol] [ipv4 | ipv6]
tunnel-table [ip-prefix [/mask] [alternative] [ipv4 | ipv6] detail
tunnel-table [ip-prefix [/mask] alternative
tunnel-table [ip-prefix [/mask] protocol protocol
tunnel-table [ip-prefix [/mask] sdp sdp-id
Context
show>router
Platforms
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
Description
This command displays tunnel table information.
Parameters
- ip-prefix [mask]
Displays only those entries matching the specified IP prefix and mask.
- summary ipv4 | ipv6
Displays IPv4 or IPv6 summary tunnel table information.
- protocol protocol ipv4 | ipv6
Displays IPv4 or IPv6 protocol information for the specified protocol.
- protocol
Displays information for the specified protocol.
- alternative ipv4 | ipv6
Displays IPv4 or IPv6 LFA and backup tunnel table. information.
- alternative
Displays LFA and backup tunnel table information.
- detail
Displays detailed tunnel table information.
- sdp sdp-id
Displays information for the specified SDP.
Output
The following output is an example of router tunnel table information, and Output fields: tunnel table describes the output fields.
Sample output*A:SAS-1# show router tunnel-table
===============================================================================
Tunnel Table (Router: Base)
===============================================================================
Destination Owner Encap TunnelId Pref Nexthop Metric
-------------------------------------------------------------------------------
10.0.0.1/32 sdp GRE 10 5 10.0.0.1 0
10.0.0.1/32 sdp GRE 21 5 10.0.0.1 0
10.0.0.1/32 sdp GRE 31 5 10.0.0.1 0
10.0.0.1/32 sdp GRE 41 5 10.0.0.1 0
===============================================================================
*A:SAS-1#
Label |
Description |
---|---|
Destination |
The route destination address and mask |
Owner |
Specifies the tunnel owner |
Encap |
Specifies the tunnel encapsulation type |
Tunnel ID |
Specifies the tunnel (SDP) identifier |
Pref |
Specifies the route preference for routes learned from the configured peer(s) |
Nexthop |
The next hop for the route destination |
Metric |
The route metric value for the route |
Clear commands
router
Syntax
router [router-instance]
Context
clear
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command clears information for the specified router instance.
Parameters
- router-instance
Specifies the router name or service ID.
arp
Syntax
arp {all | ip-addr | interface {ip-int-name | ip-addr}}
Context
clear>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command clears all or specific ARP entries.
The scope of ARP cache entries cleared depends on the command line option(s) specified.
Parameters
- all
Clears all ARP cache entries.
- ip-addr
Clears the ARP cache entry for the specified IP address.
- interface ip-int-name
Clears all ARP cache entries for the IP interface with the specified name.
- interface ip-addr
Clears all ARP cache entries for the specified IP interface with the specified IP address.
icmp6
Syntax
icmp6 all
icmp6 global
icmp6 interface interface-name
Context
clear>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command clears ICMP statistics.
Parameters
- all
Clears all statistics.
- global
Clears global statistics.
- interface-name
Clears ICMP6 statistics for the specified interface.
dhcp
Syntax
dhcp
Context
clear>router
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
Commands in this context clear and reset DHCP entities.
local-dhcp-server
Syntax
local-dhcp-server server-name
Context
clear>router>dhcp
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command clears DHCP server data.
Parameters
- server-name
Clears data for the specified local DHCP server.
declined-addresses
Syntax
declined-addresses ip-address[/mask]
declined-addresses pool pool-name
Context
clear>router>dhcp>local-dhcp-server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command clears declined DHCP addresses.
Parameters
- pool-name
Specifies the declined pool name.
- ip-address[/mask]
Specifies the declined IP address and mask.
leases
Syntax
leases ip-address[/mask] [state]
leases all [state]
Context
clear>router>dhcp>local-dhcp-server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command clears DHCP leases.
Parameters
- ip-address[/mask]
Clears the specified IP address and mask.
- state
Clears the state of the lease to be removed.
server-stats
Syntax
server-stats
Context
clear>router>dhcp>local-dhcp-server
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command clears all server statistics.
statistics
Syntax
statistics [ip-int-name | ip-address]
Context
clear>router>dhcp
Platforms
7210 SAS-K 2F6C4Tand 7210 SAS-K 3SFP+ 8C
Description
This command clears DHCP statistics.
Parameters
- ip-int-name
Clears DHCP statistics for the specified interface name.
- ip-address
Clears DHCP statistics for the specified IP address.
neighbor
Syntax
neighbor {all | ip-address [interface interface-name}
neighbor [interface ip-int-name | ipv6-address]
Context
clear>router
Platforms
7210 SAS-D, 7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
This command clears IPv6 neighbor information.
Parameters
- all
Clears IPv6 neighbors.
- ip-int-name
Clears the specified neighbor interface information, up to 32 characters.
- ip-address
Clears the specified IPv6 neighbors.
router-advertisement
Syntax
router-advertisement all
router-advertisement [interface interface-name]
Context
clear>router
Platforms
7210 SAS-Dxp, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C
Description
This command clears all IPV6 router advertisement counters.
Parameters
- all
Clears all router advertisement counters for all interfaces.
- interface interface-name
Clear router advertisement counters for the specified interface.
Debug commands
router
Syntax
router
Context
debug
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures debugging for a router instance.
Parameters
- router-instance
Specifies the router name or service ID.
ip
Syntax
ip
Context
debug>router
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures debugging for IP.
arp
Syntax
arp
Context
debug>router>ip
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures route table debugging.
icmp
Syntax
[no] icmp
Context
debug>router>ip
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables ICMP debugging.
icmp6
Syntax
icmp6 [ip-int-name]
no icmp6
Context
debug>router>ip
Platforms
Supported on all 7210 SAS platforms as described in this document, except 7210 SAS-K 2F1C2T
Description
This command enables ICMP6 debugging.
interface
Syntax
[no] interface [ip-int-name | ip-address]
Context
debug>router>ip
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command displays the router IP interface table sorted by interface index.
Parameters
- ip-address
Only displays the interface information associated with the specified IP address.
- ip-int-name
Only displays the interface information associated with the specified IP interface name, up to 32 characters.
packet
Syntax
packet [ip-int-name | ip-address] [headers] [protocol-id]
no packet [ip-int-name | ip-address]
Context
debug>router>ip
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command enables debugging for IP packets.
The no form of this command disables debugging for IP packets. If a protocol-id was previously specified, it will be removed from the criteria.
Parameters
- ip-int-name
Displays only the interface information associated with the specified IP interface name, up to 32 characters.
- ip-address
Displays only the interface information associated with the specified IP address.
- headers
Displays only information associated with the packet header.
- protocol-id
Specifies the value representing the IP protocol to debug. Well known protocol numbers include ICMP(1), TCP(6), UDP(17). The values can be expressed in decimal, hexadecimal, or binary.
route-table
Syntax
route-table [ip-prefix/prefix-length]
route-table ip-prefix/prefix-length longer
no route-table
Context
debug>router>ip
Platforms
Supported on all 7210 SAS platforms as described in this document
Description
This command configures route table debugging.
Parameters
- ip-prefix
Specifies the IP prefix for prefix list entry, in dotted-decimal notation.
- longer
Specifies the prefix list entry matches any route that matches the specified ip-prefix and prefix mask length values greater than the specified mask.