2.6. IP Router Command Reference

Note: 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.

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.

This command enables the context to configure router parameters and interfaces.

This command enables or disables ICMP redirects received on the management interface.

The no form of this command disables ICMP redirects.

This command enables or disables IPv6 ICMP redirects received on the management interface.

The no form of this command disables IPv6 ICMP redirects.

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.

This command enables ECMP and configures the number of routes for path sharing. For example, a value of 2 means two equal-cost routes will be used for cost sharing.

ECMP can only be used for routes learned with the same preference and same protocol. 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:

This command enables the context to configure global parameters related to MPLS labels.

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.

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

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.

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 will be 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 will be removed from the associated static route.

The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.

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 will be used instead. The preference parameter is used to specify the order in which the routes are applied. If a blackhole static route has the same 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, then cpe-check parameters must match. If they do not, the new configuration command will be rejected.

If a static-route command is issued with no cpe-check target, but the destination prefix/netmask and next hop matches a static route that did have an associated CPE check, the cpe-check test will be removed from the associated static route.

The no form of this command deletes the static route entry. If a static route needs to be removed when multiple static routes exist to the same destination, then as many parameters to uniquely identify the static route must be entered.

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.

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.

This command enables the sending of force-renew messages.

The no form of this command disables the sending of force-renew messages.

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.

This command configures a DHCP address pool on the router.

This command configures the maximum lease time.

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

This command configures the minimum lease time.

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

This command specifies the desired minimum number of free addresses in this pool.

The no form of this command reverts to the default.

This command configures the system to return a DHCP NAK message if the following conditions are met:

If the conditions are not met, the system drops the DHCP packet.

This command configures the offer time.

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

This command enables the context to configure pool options. The options defined here can be overruled by defining the same option in the local user database.

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.

This command configures the IP address of the DNS server.

This command configures the default domain for a DHCP client that the router uses to complete unqualified host names (without a dotted-decimal domain name).

The no form of this command removes the name from the configuration.

This command configures the time the client transitions to a rebinding state.

The no form of this command removes the time from the configuration.

This command configures the time the client transitions to a renew state.

The no form of this command removes the time from the configuration.

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.

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.

This command configures a range of IP addresses to be served from the pool. All IP addresses between the start and end IP addresses will be included (other than specific excluded addresses).

This command specifies a range of IP addresses that excluded from the pool of IP addresses in this subnet.

This command configures the maximum number of declined addresses allowed.

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.

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.

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.

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

This command configures a local user database for authentication.

This command enables the context to configure route next-hop policies.

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

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.

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

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.

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

The no form of this command deletes a template.

This command configures the description of the next-hop template.

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.

Note: 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.

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.

Note: 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.

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

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

The user can select if link protection or node protection is preferred in the selection of a LFA next-hop for all IP prefixes and LDP FEC prefixes to which a route next-hop policy template is applied. The default in SR OS implementation is node protection. The implementation will fall back to the other type if no LFA next-hop of the preferred type is found.

When the route next-hop policy template is applied to an IP interface, all prefixes using this interface as a primary next-hop will follow the protection type preference specified in the template.

The no form deletes the protection type constraint from the route next-hop policy template.

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

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

Note: 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.

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.

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 will be 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.

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.

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) is notified of the fault.

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

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.

This command enables local proxy ARP on the interface.

The no form of this command disables local proxy ARP on the interface.

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 will cause both IGPs to advertise infinite metric and to follow the IGP-LDP synchronization procedures. If only one IGP bounces on this interface or on the system, then only the affected IGP advertises the infinite metric and follows the IGP-LDP synchronization procedures.

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 will announce a new best next-hop and LDP will use 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 will only be advertised after the timer expires. Also, if the currently advertised cost is different, the new cost value will be advertised after the user executes any of the following commands:

Refer to 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 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 will take effect at the next synchronization event. That is, if the timer is still running, it will continue using the previous value.

If parallel links exist to the same neighbor, 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 will only consider 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 might 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 will cause the IGP route cost to increase to the maximum value.

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

This command configures the interface as a loopback interface.

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.

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.

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.

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

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

This command enables remote proxy ARP on the interface.

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 certain IP address to send the packet to the corresponding ARP address.

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

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.

This command enables the Unicast RPF check feature on this router.

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.

This command enables the context to configure egress network filter policies for the IP interface. If an egress filter is not defined, no filtering is performed.

This command enables the context to configure ingress network filter policies for the IP interface. If an ingress filter is not defined, no filtering is performed.

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.

Note: 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.

This command enables the context to 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.

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.

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.

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.

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.

This command enables the context to configure or apply IP interface attributes such as administrative group (admin-group) or Shared Risk Loss Group (SRLG).

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 will compute a path which 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 will reject the creation of an admin group if it reuses the same name or group value as an existing group.

Note: 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.

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

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

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.

Note: 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.

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.

Note: 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.

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.

Note: 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.

This command configures IPv6 for a router interface.

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

This command assigns an IPv6 address to the interface.

This command enables the context to configure ICMPv6 parameters for the interface.

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

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

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.

This command configures rate for ICMPv6 time-exceeded messages.

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.

This command configures the link local address.

This command enables local proxy neighbor discovery on the interface.

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

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

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.

This command enables the context to configure 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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

This command configures the remaining time, in seconds, that this prefix will continue 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.

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.

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.

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.

This command configures the router lifetime.

The no form of this command disables the configuration of the router lifetime.