For feedback, use the following:
ipd_online_feedback@alcatel-lucent.com
Table of Contents Previous Next Index PDF


Configuration Commands
Generic Commands
shutdown
Syntax 
[no] shutdown
Context 
config>router>interface
Description 
The shutdown 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.
The shutdown command administratively disables an entity. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system generated configuration files.
The no form of the command puts an entity into the administratively enabled state.
Default 
no shutdown
description
Syntax 
description description-string
no description
Context 
config>router>if
config>router>if>dhcp
config>router>if>vrrp
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command creates a text description stored in the configuration file for a configuration context.
The no form of the command removes the description string from the context.
Default 
No description is associated with the configuration context.
Parameters 
description-string
The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
 
 
Router Global Commands
router
Syntax 
router router-name
Context 
config
Description 
This command enables the context to configure router parameters, and interfaces, route policies, and protocols.
Parameters 
router-name
Specify the router-name.
Values
Default
aggregate
Syntax 
aggregate ip-prefix/ip-prefix-length [summary-only] [as-set] [aggregator as-number: ip-address] [community comm-id] [black-hole | indirect ip-address]
no aggregate ip-prefix/ip-prefix-length
Context 
config>router
Description 
This command creates an aggregate route.
Use this command to automatically install an aggregate in the routing table when there are one or more component routes. A component route is any route used for forwarding that is a more-specific match of the aggregate.
The use of aggregate routes can reduce the number of routes that need to be advertised to neighbor routers, leading to smaller routing table sizes.
Overlapping aggregate routes may be configured; in this case a route becomes a component of only the one aggregate route with the longest prefix match. For example if one aggregate is configured as 10.0.0.0/16 and another as 10.0.0.0/24, then route 10.0.128/17 would be aggregated into 10.0.0.0/16, and route 10.0.0.128/25 would be aggregated into 10.0.0.0/24. If multiple entries are made with the same prefix and the same mask the previous entry is overwritten.
A standard 4-byte BGP community may be associated with an aggregate route in order to facilitate route policy matching.
By default aggregate routes are not installed in the forwarding table, however there are configuration options that allow an aggregate route to be installed with a black-hole next hop or with an indirect IP address as next hop.
The no form of the command removes the aggregate.
Default 
No aggregate routes are defined.
Parameters 
ip-prefix
The destination address of the aggregate route in dotted decimal notation.
Values
ipv4-prefix a.b.c.d (host bits must be 0)
ipv4-prefix-length 0 — 32
ipv6-prefix x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
ipv6-prefix-length 0 — 128
The mask associated with the network address expressed as a mask length.
Values
summary-only
This optional parameter suppresses advertisement of more specific component routes for the aggregate.
To remove the summary-only option, enter the same aggregate command without the summary-only parameter.
as-set
This optional parameter is only applicable to BGP and creates an aggregate where the path advertised for this route will be an AS_SET consisting of all elements contained in all paths that are being summarized. Use this feature carefully as it can increase the amount of route churn due to best path changes.
aggregator as-number:ip-address
This optional parameter specifies the BGP aggregator path attribute to the aggregate route. When configuring the aggregator, a two-octet AS number used to form the aggregate route must be entered, followed by the IP address of the BGP system that created the aggregate route.
community comm-id
This configuration option associates a BGP community with the aggregate route. The community can be matched in route policies and is automatically added to BGP routes exported from the aggregate route.
Values
black-hole
This optional parameter installs the aggregate route, when activated, in the FIB with a black-hole next-hop; where packets matching this route are discarded.
indirect ip-address
This configuration option specifies that the aggregate route should be installed in the FIB with a next-hop taken from the route used to forward packets to ip-address.
Values
ipv4-prefix a.b.c.d
ipv6-prefix x:x:x:x:x:x:x:x
x:x:x:x:x:x:d.d.d.d
x: [0 — FFFF]H
d: [0 — 255]D
autonomous-system
Syntax 
autonomous-system autonomous-system
no autonomous-system
Context 
config>router
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/enabling (shutdown/no shutdown) the BGP instance or rebooting the system with the new configuration.
Default 
No autonomous system number is defined.
Parameters 
autonomous-system
The autonomous system number expressed as a decimal integer.
Values
confederation
Syntax 
confederation confed-as-num members as-number [as-number...up to 15 max]
no confederation [confed-as-num members as-number...up to 15 max]
Context 
config>router
Description 
This command creates confederation autonomous systems within an AS.
This technique is used to reduce the number of IBGP sessions required within an AS. Route reflection is another technique that is commonly deployed to reduce the number of IBGP sessions.
The no form of the command deletes the specified member AS from the confederation.
When no members are specified in the no statement, the entire list is removed and confederation is disabled.
When the last member of the list is removed, confederation is disabled.
Default 
no confederation - no confederations are defined.
Parameters 
confed-as-num
The confederation AS number expressed as a decimal integer.
Values
members member-as-num
The AS number(s) of members that are part of the confederation, expressed as a decimal integer. Up to 15 members per confed-as-num can be configured.
Values
ecmp
Syntax 
ecmp max-ecmp-routes
no ecmp
Context 
config>router
Description 
This command enables ECMP and configures the number of routes for path sharing; for example, the value 2 means two equal cost routes will be used for cost sharing.
ECMP can only be used for routes learned with the same preference and same protocol. See the discussion on preferences in the ­static-route command.
When more ECMP routes are available at the best preference than configured in max-ecmp-routes, then the lowest next-hop IP address algorithm is used to select the number of routes configured in max-ecmp-routes.
The no form of the command disables ECMP path sharing. If ECMP is disabled and multiple routes are available at the best preference and equal cost, then the route with the lowest next-hop IP address is used.
Default 
no ecmp
Parameters 
max-ecmp-routes
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.
Values
fib-priority
Syntax 
fib-priority {high | standard}
Context 
config>router
Description 
This command specifies the FIB priority for VPRN.
ignore-icmp-redirect
Syntax 
[no] ignore-icmp-redirect
Context 
config>router
Description 
This command drops ICMP redirects received on the management interface.
The no form of the command accepts ICMP redirects received on the management interface.
ip-fast-reroute
Syntax 
[no] ip-fast-reroute
Context 
config>router
Description 
This command enables IP Fast-Reroute (FRR) feature on the system.
This feature provides for the use of a Loop-Free Alternate (LFA) backup next-hop for forwarding in-transit and CPM generated IP packets when the primary next-hop is not available. IP FRR is supported on IPv4 and IPv6 OSPF/IS-IS prefixes forwarded in the base router instance to a network IP interface or to an IES SAP interface or spoke interface. It is also supported for VPRN VPN-IPv4 OSPF prefixes and VPN-IPv6 OSPF prefixes forwarded to a VPRN SAP interface or spoke interface.
IP FRR also provides a LFA backup next-hop for the destination prefix of a GRE tunnel used in an SDP or in VPRN auto-bind.
When any of the following events occurs, IGP instructs in the fast path on the IOMs to enable the LFA backup next-hop:
a. OSPF/IS-IS interface goes operationally down: physical or local admin shutdown.
b. Timeout of a BFD session to a next-hop when BFD is enabled on the OSPF/IS-IS interface
When the SPF computation determines there is more than one primary next-hop for a prefix, it will not program any LFA next-hop in RTM. Thus, the IP prefix will resolve to the multiple equal-cost primary next-hops that provide the required protection.
The no form of this command disables the IP FRR feature on the system
Default 
no ip-fast-reroute
mc-maximum-routes
Syntax 
mc-maximum-routes number [log-only] [threshold threshold]
no mc-maximum-routes
Context 
config>router
Description 
This command specifies the maximum number of multicast routes that can be held within a VPN routing/forwarding (VRF) context. When this limit is reached, a log and SNMP trap are sent. If the log-only parameter is not specified and the maximum-routes value is set below the existing number of routes in a VRF, then no new joins will be processed.
The no form of the command disables the limit of multicast routes within a VRF context. Issue the no form of the command only when the VPRN instance is shutdown.
Default 
no mc-maximum-routes
Parameters 
number
Specifies the maximum number of routes to be held in a VRF context.
Values
log-only
Specifies that if the maximum limit is reached, only log the event. log-only does not disable the learning of new routes.
threshold threshold
The percentage at which a warning log message and SNMP trap should be sent.
Values
Default
mpls-labels
Syntax 
mpls-labels
Context 
config>router
Description 
This command creates a context for the configuration of glocal parameters related to MPLS labels.
static-label
Syntax 
static-label max-lsp-labels number static-svc-labels number
no static-label
Context 
config>router>mpls-labels
Description 
This command enables the range of MPLS static label values reserved for LSPs and for VCs (pseudowires) to be configured. For LSPs, these ranges only apply to static MPLS-TP paths configured under config>router>mpls>lsp.
Default 
no static-label
Parameters 
max-lsp-labels number
The number of static label values that are reserved for use by statically configured LSPs. THe range is configured as follows: The minimum value of label is always 32. The maximum value in the range is then 32 + number. The allowed values of number are as follows for max-lsp-labels:
Values
Values
Default
static-svc-labels number
The number of static label values that are reserved for use by statically configured VCs (pseudowires). The range is configured as follows: The minimum value of static VC label is always [32 + max-lsp-labels + 1]. The maximum VC label value in the range is then [32 + max-lsp-labels + 1+ number]. The allowed values of number are as follows for static-svc-labels:
Values
Values
Default
multicast-info
Syntax 
multicast-info-policy policy-name
no multicast-info-policy
Context 
configure>router
Description 
This command configures multicast information policy.
Parameters 
policy-name
Specifies the policy name.
Values
network-domains
Syntax 
network-domains
Context 
config>router
Description 
This command opens context for defining network-domains. This command is applicable only in the base routing context.
description
Syntax 
[no] description string
Context 
config>router>network-domains>network-domain
Description 
This command creates a text description stored in the configuration file for a configuration context.
The no form of the command removes the description string from the context.
Default 
no description
Parameters 
string
The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special character (#, $, space, etc.), the entire string must be enclosed within double quotes.
network-domain
Syntax 
network-domain network-domain-name [create]
no network-domain network-domain-name
Context 
config>router>network-domains
Description 
This command creates network-domains that can be associated with individual interfaces and SDPs.
Default 
network-domain “default”
Parameters 
network-domain-name
Network domain name character string.
router-id
Syntax 
router-id ip-address
no router-id
Context 
config>router
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 the 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
The 32 bit router ID expressed in dotted decimal notation or as a decimal value.
service-prefix
Syntax 
service-prefix ip-prefix/mask | ip-prefix netmask [exclusive]
no service-prefix ip-prefix/mask | ip-prefix netmask
Context 
config>router
Description 
This command creates an IP address range reserved for IES or VPLS services.
The purpose of reserving IP addresses using service-prefix is to provide a mechanism to reserve one or more address ranges for services.
When services are defined, the address must be in the range specified as a service prefix. If a service prefix is defined, then IP addresses assigned for services must be within one of the ranges defined in the service-prefix command. If the service-prefix command is not configured, then no limitations exist.
Addresses in the range of a service prefix can be allocated to a network port unless the exclusive parameter is used. Then, the address range is exclusively reserved for services.
When a range that is a superset of a previously defined service prefix is defined, the subset is replaced with the superset definition; for example, if a service prefix exists for 10.10.10.0/24, and a service prefix is configured as 10.10.0.0/16, then 10.10.10.0/24 is replaced by the new 10.10.0.0/16 configuration.
When a range that is a subset of a previously defined service prefix is defined, the subset replaces the existing superset, providing addresses used by services are not affected; for example, if a service prefix exists for 10.10.0.0/16, and a service prefix is configured as 10.10.10.0/24, then the 10.10.0.0/16 entry is removed as long as no services are configured that use 10.10.x.x addresses other than 10.10.10.x.
The no form of the command removes all address reservations. A service prefix cannot be removed while one or more service uses an address or addresses in the range.
Default 
no service-prefix - no IP addresses are reserved for services.
Parameters 
ip-prefix/mask
The IP address prefix to include in the service prefix allocation in dotted decimal notation.
Values
Values
When this option is specified, the addresses configured are exclusively used for services and cannot be assigned to network ports.
sgt-qos
Syntax 
sgt-qos
Context 
config>router
Description 
This command configures DSCP/Dot1p re-marking for self-generated traffic.
application
Syntax 
application dscp-app-name dscp {dscp-value |dscp-name}
application dot1p-app-name dot1p dot1p-priority
no application {dscp-app-name|dot1p-app-name}
Context 
config>router>sgt-qos
Description 
This command configures DSCP/Dot1p re-marking for applications.
Parameters 
dscp-app-name
Specifies the DSCP application name.
Values
dscp-value
Specifies the DSCP value
Values
dscp-name
Specifies the DSCP name.
none, be, ef, cp1, cp2, cp3, cp4, cp5, cp6, cp7, cp9, cs1, cs2, cs3, cs4, cs5, nc1, nc2, af11, af12, af13, af21, af22, af23, af31, af32, af33, af41, af42, af43, cp11, cp13, cp15, cp17, cp19, cp21, cp23, cp25, cp27, cp29, cp31, cp33, cp35, cp37, cp39, cp41, cp42, cp43, cp44, cp45, cp47, cp49, cp50, cp51, cp52, cp53, cp54, cp55, cp57, cp58, cp59, cp60, cp61, cp62, cp63
dot1p-priority
Specifies the Dot1p priority.
Values
dot1p-app-name
Specifies the Dot1p application name.
Values
dscp
Syntax 
dscp dscp-name fc fc-name
no dscp dscp-name
Context 
config>router>sgt-qos
Description 
This command configures DSCP name to FC mapping.
Parameters 
dscp-name
Specifies the DSCP name.
Values
fc-name
Specifies the forward class name.
Values
bfd-template
Syntax 
bfd-template name [create]
no bfd-template name
Context 
config>router>bfd
Description 
This command creates or edits a BFD template. A BFD template defines the set of configurable parameters used by a BFD session. These include the transmit and receive timers used for BFD CC packets, the transmit timer interval used when the session is providing a CV function, the multiplier value, the echo-receive interval, and whether ther BFD session terminates in the CPM network processor.
Default 
no bfd-template
Parameters 
name
Specifies a text string name for the template up to 32 characters in printable 7-bit ASCII, enclosed in double quotes.
transmit-interval
Syntax 
transmit-interval transmit-interval
no transmit-interval
Context 
config>router>bfd>bfd-template
Description 
This command specifies the transmit timer used for BFD packets. If the template is used for a BFD session on an MPLS-TP LSP, then this timer is used for CC packets.
Default 
no transmit-interval
Parameters 
transmit-interval
Specifies the transmit interval. Note that the minimum interval that can be configured is hardware dependent.
Values
Default
receive-interval
Syntax 
receive-interval receive-interval
no receive-interval
Context 
config>router>bfd>bfd-template
Description 
This command specifies the receive timer used for BFD packets. If the template is used for a BFD session on an MPLS-TP LSP, then this timer is used for CC packets.
Default 
no receive-interval
Parameters 
receive-interval
Specifies the receive interval. Note that the minimum interval that can be configured is hardware dependent.
Values
Default
cv-tx
Syntax 
cv-tx transmit-interval
no cv-tx
Context 
config>router>bfd>bfd-template
Description 
This command specifies the transmit interval used by BFD packets used for MPLS-TP proactive CV.
Default 
no cv-tx
Parameters 
transmit-interval
Specifies the transmit interval. This parameter is only used if a BFD session is enabled with CV on an MPLS-TP LSP.
Values
Default
echo-receive
Syntax 
echo-receive echo-interval
no echo-receive
Context 
config>router>bfd>bfd-template
Description 
This command sets the minimum echo receive interval, in milliseconds, for a session. This is not used by a BFD session for MPLS-TP.
Default 
no echo-receive
Parameters 
echo-interval
Specifies the echo receive interval.
Values
Default
multiplier
Syntax 
multiplier multiplier
no multiplier
Context 
config>router>bfd>bfd-template
Description 
This command specifies the detect multiplier used for a BFD session. If a BFD control packet is not received for a period of multiplier x receive-interval, then the session is declared down.
Default 
3
Parameters 
multiplier
Specifies the multiplier.
Values
Default
type
Syntax 
[no] type cpm-np
Context 
config>router>bfd>bfd-template
Description 
This command selects the CPM network processor as the local termination point for the BFD session. This is enabled by default.
Default 
type cpm-np
triggered-policy
Syntax 
triggered-policy
no triggered-policy
Context 
config>router
Description 
This command triggers route policy re-evaluation.
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 router, 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 given 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; for example, clear router bgp neighbor x.x.x.x soft. This keeps the peer up, and the change made to a route policy is applied only to that peer or group of peers.
single-sfm-overload
Syntax 
single-sfm-overload [holdoff-time holdoff-time]
no single-sfm-overload
Context 
config>router
Description 
This command, if enabled, will cause the OSPF for the service to enter an overload state when the node only has a single SFM functioning.
The no form of this command causes the overload state to be cleared.
Default 
no single-sfm-overload
Parameters 
holdoff-time
This parameter specifies the delay between the detection of a single SFM and enacting the overload state.
Values
Default
static-route
Syntax 
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [community comm-id] [enable | disable] next-hop ip-int-name | ip-address [mcast-family] [bfd-enable |{cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]} {prefix-list prefix-list-name [all | none]} |{fc fc-name [priority {low | high}]} ] [ldp-sync]
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [community comm-id] [enable | disable] indirect ip-address [ldp | rsvp-te [disallow-igp]] [cpe-check cpe-ip-address [interval seconds] [drop-count count] [log]] {prefix-list prefix-list-name [all | none]} |{fc fc-name [priority {low | high}]}
[no] static-route {ip-prefix/prefix-length | ip-prefix netmask} [preference preference] [metric metric] [tag tag] [community comm-id] [enable | disable] black-hole [mcast-family] {prefix-list prefix-list-name [all | none]}
Context 
config>router
Description 
This command creates static route entries for both the network and access routes.
When configuring a static route, either next-hop, indirect or black-hole must be configured.
The no form of the 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.
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.
Default 
No static routes are defined.
Parameters 
ip-prefix/prefix-length
The destination address of the static route.
Values
ipv4-prefix a.b.c.d (host bits must be 0)
ipv4-prefix-length 0 — 32
ipv6-prefix x:x:x:x:x:x:x:x (eight 16-bit pieces)
x:x:x:x:x:x:d.d.d.d
x [0 — FFFF]H
d [0 — 255]D
ipv6-prefix-length 0 — 128
ip-address
The IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Values
ipv4-address a.b.c.d (host bits must be 0)
ipv6-address x:x:x:x:x:x:x:x[-interface]
x:x:x:x:x:x:d.d.d.d[-interface]
x: [0..FFFF]H
d: [0..255]D
interface: 32 characters maximum, mandatory for link local
addresses
netmask
The subnet mask in dotted decimal notation.
Values
community comm-id
This configuration option associates a BGP community with the static route. The community can be matched in route policies and is automatically added to BGP routes exported from the static route.
Values
ldp-sync
Extends the LDP synchronization feature to a static route. When an interface comes back up, it is possible that a preferred static route using the interface as next-hop for a given prefix is enabled before the LDP adjacency to the peer LSR comes up on this interface. In this case, traffic on an SDP that uses the static route for the far-end address would be black-holed until the LDP session comes up and the FECs exchanged.
This option when enabled delays the activation of the static route until the LDP session comes up over the interface and the ldp-sync-timer configured on that interface has expired.
preference preference
The preference of this static route versus the routes from different sources such as BGP or OSPF, expressed as a decimal integer. When modifing the preference of an existing static route, the metric will not be changed unless specified.
Different protocols should not be configured with the same preference. If this occurs, the tiebreaker is according to the default preference table defined in Table 5 .
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 configuration of the ­ecmp command
prefix-list prefix-list-name [all | none]
Specifies the prefix-list to be considered.
metric metric
The cost metric for the static route, expressed as a decimal integer. This value is used when importing the static route into other protocols such as OSPF. When the metric is configured as 0 then the metric configured in OSPF, default-import-metric, applies. When modifying the metric of an existing static route, the preference will not change unless specified. This value is also used to determine which static route to install in the forwarding table:
Default
Values
next-hop [ip-address | ip-int-name]
Specifies the directly connected next hop IP address used to reach the destination. If the next hop is over an unnumbered interface or a point-to-point interface, the ip-int-name of the unnumbered or point-to-point interface (on this node) can be configured.
The next-hop keyword and the indirect or black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of either the indirect or black-hole parameters), then this static route will be replaced with the newly entered command, and unless specified, the respective defaults for preference and metric will be applied.
The 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.
Values
ip-int-name 32 chars max
ipv4-address a.b.c.d
ipv6-address x:x:x:x:x:x:x:x[-interface]
x:x:x:x:x:x:d.d.d.d[-interface]
x: [0..FFFF]H
d: [0..255]D
interface: 32 characters maximum, mandatory for link local
addresses
indirect ip-address
Specifies that the route is indirect and specifies the next hop IP address used to reach the destination.
The configured ip-addr is not directly connected to a network configured on this node. The destination can be reachable via multiple paths. The indirect address can only resolved from dynamic routing protocol. Another static route cannot be used to resolve the indirect address.
The indirect keyword and the next-hop or black-hole keywords are mutually exclusive. If an identical command is entered (with the exception of either the next-hop or black-hole parameters), then this static route will be replaced with the newly entered command and unless specified the respective defaults for preference and metric will be applied.
The ip-addr configured can be either on the network or the access side and is normally at least one hop away from this node.
black-hole
Specifies the route is a black hole route. If the destination address on a packet matches this static route, it will be silently discarded.
The black-hole keyword and the next-hop or indirect keywords are mutually exclusive. If an identical command is entered (with the exception of either the next-hop or indirect parameters), then this static route will be replaced with the newly entered command, and unless specified, the respective defaults for preference and metric will be applied.
disallow-igp
This value is valid only for indirect static routes. If set and if none of the defined tunneling mechanisms (RSVP-TE, LDP or IP) qualify as a next-hop, the normal IGP next-hop to the indirect next-hop address will not be used. If not set then the IGP next-hop to the indirect next-hop address can be used as the next-hop of the last resort.
tag
Adds 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.
 
Default
Values
enable
Static routes can be administratively enabled or disabled. Use the enable parameter to re-enable a disabled static route. In order to enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route.
The administrative state is maintained in the configuration file.
Default
disable
Static routes can be administratively enabled or disabled. Use the disable parameter to disable a static route while maintaining the static route in the configuration. In order to enable a static route, it must be uniquely identified by the IP address, mask, and any other parameter that is required to identify the exact static route.
The administrative state is maintained in the configuration file.
Default
bfd-enable
Associates the state of the static route to a BFD session between the local system and the configured nexthop. This keyword cannot be configured if the indirect or blackhole keywords are specified. The remote end of the BFD session must also be configured to originate or accept the BFD session controlling the static-route state.
mcast-family
Enables submission of the IPv4 or IPv6 static route into IPv4 or IPv6 multicast RTM.
Values
mcast-ipv4, mcast-ipv6
rsvp-te
This parameter allows the static route to be resolved via an RSVP-TE based LSP. The static route nexthop will be resolved via the best RSVP-TE based LSP to the associated indirect next hop. By default, if an RSVP-TE LSP is not available, the IGP route table will be used to resolve the associated nexthop. If the keyword “disallow-igp” is configured, the associated static route will not be resolved through the IPv4 route table if an RSVP-TE based LSP is not available.
cpe-check target-ip-address
This parameter specifies the IP address of the target CPE device. ICMP pings will be sent to this target IP address. This parameter must be configured to enable the CPE connectivity feature for the associated static route. The target-ip-address cannot be in the same subnet as the static route subnet itself to avoid possible circular references. This option is mutually exclusive with BFD support on a given static route.
Default
interval seconds
This optional parameter specifies the interval between ICMP pings to the target IP address.
Values
Default
drop-count count
This optional parameter specifies the number of consecutive ping-replies that must be missed to declare the CPE down and to de-active the associated static route.
Values
Default
log
This optional parameter enables 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.
Sample Output
*B:Dut-C# configure router "management"
*B:Dut-C>config>router# info
----------------------------------------------
       static-route 1.1.1.0/24 next-hop 172.31.117.1
        static-route 1::/96 next-hop 3000::AC1F:7567
----------------------------------------------
*B:Dut-C>config>router#
 
 
*B:Dut-C>config>router# show router "management" route-table
===============================================================================
Route Table (Router: management)
===============================================================================
Dest Prefix                                   Type    Proto    Age         Pref
       Next Hop[Interface Name]                                     Metric
-------------------------------------------------------------------------------
1.1.1.0/24                                    Remote  Static   00h01m29s   0
       172.31.117.1                                                 1
138.203.0.0/16                                Remote  Static   05h01m11s   0
       172.31.117.1                                                 1
172.31.117.0/24                               Local   Local    05h04m10s   0
       management                                                   0
-------------------------------------------------------------------------------
No. of Routes: 3
===============================================================================
*B:Dut-C>config>router#
 
 
*B:Dut-C>config>router# show router "management" route-table ipv6
===============================================================================
IPv6 Route Table (Router: management)
===============================================================================
Dest Prefix                                   Type    Proto    Age         Pref
       Next Hop[Interface Name]                                     Metric
-------------------------------------------------------------------------------
1::/96                                        Remote  Static   00h01m09s   5
       3000::AC1F:7567                                              1
3000::/96                                     Local   Local    05h04m12s   5
       management                                                   0
3FFE::/96                                     Remote  Static   00h00m11s   5
       3000::AC1F:7567                                              0
-------------------------------------------------------------------------------
No. of Routes: 3
===============================================================================
*B:Dut-C>config>router#
 
Note that the help info output (?) is inherited from the basic router context and does not reflect the specific syntax for the management context.
Only next-hop is allowed with any extra parameters.
 
*B:Dut-C>config>router# show router "management" static-?
static-arp      static-route
 
 
*B:Dut-C>config>router# show router "management" static-route
===============================================================================
Static Route Table (Router: management)  Family: IPv4
===============================================================================
Prefix                                        Tag         Met    Pref Type Act
   Next Hop                                    Interface
-------------------------------------------------------------------------------
1.1.1.0/24                                    0           1      5    NH   Y
   172.31.117.1                                n/a
-------------------------------------------------------------------------------
No. of Static Routes: 1
===============================================================================
*B:Dut-C>config>router#
 
 
*B:Dut-C>config>router# show router "management" static-route ipv6
===============================================================================
Static Route Table (Router: management)  Family: IPv6
===============================================================================
Prefix                                        Tag         Met    Pref Type Act
Next Hop                                    Interface
-------------------------------------------------------------------------------
1::/96                                        0           1      5    NH   Y
   3000::AC1F:7567                             management
-------------------------------------------------------------------------------
No. of Static Routes: 1
===============================================================================
*B:Dut-C>config>router#
 
Router L2TP Commands
l2tp
Syntax 
l2tp
Context 
config>router
Description 
This command enables the context to configure L2TP parameters. L2TP extends the PPP model by allowing Layer 2 and PPP endpoints to reside on different devices interconnected by a packet-switched network.
calling-number-format
Syntax 
calling-number-format ascii-spec
no calling-number-format
Context 
config>router>l2tp
Description 
This command what string to put in the Calling Number AVP, for L2TP control messages related to a session in this L2TP protocol instance.
Parameters 
ascii-spec
Specifies the L2TP calling number AVP.
Values
exclude-avps
Syntax 
exclude-avps calling-number
no exclude-avps
Context 
config>router>l2tp
Description 
This command configures the L2TP AVPs to exclude.
next-attempt
Syntax 
next-attempt {same-preference-level | next-preference-level}
no next-attempt
Context 
configure>router>l2tp
configure>service>vprn>l2tp
Description 
This command enables tunnel selection algorithm based on the tunnel preference level.
Parameters 
same-preference-level
In case that the tunnel-spec selection algorithm evaluates into a tunnel that is currently unavailable (for example tunnel in a blacklist) then the next elected tunnel, if available, will be chosen within the same preference-level as the last attempted tunnel. Only when all tunnels within the same preference level are exhausted, the tunnel selection algorithm will move to the next preference level.
In case that a new session setup request is received while all tunnels on the same preference level are blacklisted, the L2TP session will try to be established on blacklisted tunnels before the tunnel selection moves to the next preference level.
next-preference-level
In case that the tunnel-spec selection algorithm evaluates into a tunnel that is currently unavailable (for example tunnel in a blacklist) then the selection algorithm will try to select the tunnel from the next preference level, even though the tunnels on the same preference level might be available for selection.
Default
replace-result-code
Syntax 
replace-result-code code [code...(upto 3 max)]
no replace-result-code
Context 
configure>router>l2tp
configure>service>vprn>l2tp
Description 
This command will replace CDN Result-Code 4, 5 and 6 on LNS with the Result Code 2. This is needed for interoperability with some implementation of LAC which only take action based on CDN Result-Code 2, while ignore CDN Result-Code 4, 5 and 6.
Default 
no replace-result-code
Parameters 
code
Specifies the L2TP Result codes that need to be replaced.
Values
tunnel-selection-blacklist
Syntax 
tunnel-selection-blacklist
Context 
config>router>l2tp
Description 
This command enables the context to configure L2TP Tunnel Selection Blacklist parameters.
add-tunnel
Syntax 
add-tunnel never
add-tunnel on reason [reason...(upto 8 max)]
no add-tunnel
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command will force the tunnel to the blacklist and render it unavailable for new sessions for the duration of pre-configured time. Peers are always forced to the black list in case that they time out (failure to receive response to control packets). In addition to time outs, certain events can be used to trigger placement of the tunnel on the black list.
Parameters 
reason
Specifies the return codes or events that determine which tunnels are added to the blacklist
Values
cdn-err-code — A tunnel will be forced to the blacklist in case that CDN message with the Result Code 2 ( Call disconnected for the reasons indicated in error code) is received.
cdn-inv-dest — A tunnel will be forced to the blacklist in case that CDN message with the Result Codes 6 ( Invalid destination) is received.
cdn-tmp-no-facilities — A tunnel will be forced to the blacklist in case that CDN message with the Result Code 4 is received ( Call failed due to lack of appropriate facilities being available - temporary condition) is received.
cdn-perm-no-facilities — A tunnel will be forced to the blacklist in case that CDN message with the Result Codes 5 ( Call failed due to lack of appropriate facilities being available - permanent condition) is received.
tx-cdn-not-established-in-time — A tunnel will be forced to the blacklist in case that CDN message with the Result Code 10 (Call was not established within time allotted by LAC) is sent from the LAC to the LNS.
stop-ccn-err-code — A tunnel will be forced to the blacklist in case that StopCCN message with the Result Code 2 (General error – Error Code indicates the problem) is sent or received.
stop-ccn-other — A tunnel will be forced to the blacklist in case that StopCCN message with the following Result Codes is received:
(1) General request to clear control connection
(4) Requestor is not authorized to establish a control channel
(5) Protocol version not supported
(6) Requestor is being shutdown
Or in the case that the StopCCN with the following result codes is transmitted:
(4) Requestor is not authorized to establish a control channel.
(5) Protocol version not supported
The receipt of the following Result Codes will NEVER blacklist a tunnel:
(0) Reserved
(3) Control channel already exist
(7) Finite state machine error
(8) Undefined
Transmission of the following Result Codes will NEVER blacklist a tunnel:
(1) General request to clear control connection
(3) Control channel already exist
(6) Requestor is being shutdown
(7) Finite state machine error

addr-change-timeout — A timed-out tunnel for which the peer IP address has changed mid-session (from the one that is provided initially during configuration) will be forced to the blacklist. In absence of this configuration option, only the configured peer for the tunnel will be blacklisted, but not the tunnel itself which now has a different peer address than the one initially configured.
never
When specified, no tunnels will be placed on blacklist under any circumstance. This parameter will available to preserve backward compatibility.
 
max-list-length
Syntax 
max-list-length unlimited
max-list-length count
no max-list-length
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command configured the maximum length of the peer/tunnel blacklist.
This command specifies how many items (tunnels or peers) can be in the tunnel-selection-blacklist. If a tunnel or peer needs to be added to the tunnel-selection-blacklist and the tunnel-selection-blacklist is full, the system will remove the item (tunnel or peer) from the blacklist that was in this blacklist forthe longest time.
Default 
unlimited
Parameters 
unlimited
Specifies there is no limit.
count
Specifies how many items (tunnels or peers) can be in the tunnel-selection-blacklist.
Values
max-time
Syntax 
max-time minutes
no max-time
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command configures time for which an entity (peer or a tunnel) are kept in the blacklist.
Default 
5 minutes
Parameters 
minutes
Specifies the maximum time a tunnel or peer may remain in the blacklist
Values
timeout-action
Syntax 
timeout-action action
no timeout-action
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command defines an action that will be executed on the entity (peer/tunnel) in the blacklist once the entity becomes eligible for selection again.
Default 
remove-from-blacklist
Parameters 
action
Specifies the Action to be taken when a tunnel or peer has been in the blacklist for the max-period of time.
Values
peer-address-change-policy
Syntax 
peer-address-change-policy {accept | ignore | reject}
Context 
config>router>l2tp
Description 
This command specifies what to do in case the system receives a L2TP responsefrom another address than the one the request was sent to.
Parameters 
accept
Specifies that this system accepts any source IP address change of received L2TP control messages related to a locally originated tunnel in the state waitReply and rejectsany peer address change for other tunnels; in case the new peer IPaddress is accepted, it is learned and used as destination addressin subsequent L2TP messages.
ignore
Specifiesthat this system ignores any source IP address change of received L2TP control messages, does not learn anynew peer IP address and does not change the destination address insubsequent L2TP messages.
reject
Specifies that this system rejects any source IP address change of received L2TP control messages and drops those messages.
receive-window-size
Syntax 
receive-window-size [4..1024]
no receive-window-size
Context 
config>router>l2tp
Description 
This command configures the L2TP receive window size.
session-limit
Syntax 
session-limit session-limit
no session-limit
Context 
config>router>l2tp
Description 
This command configures the L2TP session limit of this router.
Parameters 
session-limit
Specifies the session limit.
Values
group
Syntax 
group tunnel-group-name [create]
no group tunnel-group-name
Context 
config>router>l2tp
Description 
This command configures an L2TP tunnel group.
Parameters 
tunnel-group-name
Specifies a name string to identify a L2TP group up to 63 characters in length.
create
This keyword is mandatory when creating a tunnel group name. The create keyword requirement can be enabled/disabled in the environment>create context.
session-limit
Syntax 
session-limit session-limit
no session-limit
Context 
config>router>l2tp
Description 
This command configures the L2TP session limit for the router. L2TP is connection-oriented. The L2TP Network Server (LNS) and LAC maintain state for each call that is initiated or answered by an LAC. An L2TP session is created between the LAC and LNS when an end-to-end PPP connection is established between a remote system and the LNS. Datagrams related to the PPP connection are sent over the tunnel between the LAC and LNS. There is a one to one relationship between established L2TP sessions and their associated calls.
Parameters 
session-limit
Specifies the number of sessions allowed.
Default
Values
avp-hiding
Syntax 
avp-hiding sensitive | always
no avp-hiding
Context 
config>router>l2tp>group
Description 
This command configures Attribute Value Pair (AVP) hiding. This capability can be used to avoid the passing of sensitive data, such as user passwords, as cleartext in an AVP.
The no form of the command returns the value to never allow AVP hiding.
Parameters 
avp-hiding
Specifies the method to be used for the authentication of the tunnels in this L2TP group.
Default
Values
challenge
Syntax 
challenge always
no challenge
Context 
config>router>l2tp>group
Description 
This command configures the use of challenge-response authentication.
The no form of the command reverts to the default never value.
Parameters 
always
Specifies that the challenge-response authentication is always used.
Default
Values
destruct-timeout
Syntax 
destruct-timeout destruct-timeout
no destruct-timeout
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command configures the period of time that the data of a disconnected tunnel will persist before being removed.
The no form of the command removes the value from the configuration.
Default 
no destruct-timeout
Parameters 
destruct-timeout
[Specifies the automatic removal of dynamic L2TP sessions, in seconds, that are no longer active.
Default
Values
hello-interval
Syntax 
hello-interval hello-interval
no hello-interval
Context 
config>router>l2tp>group
Description 
This command configures the time interval between two consecutive tunnel Hello messages. The Hello message is an L2TP control message sent by either peer of a LAC-LNS control connection. This control message is used as a keepalive for the tunnel.
The no form of the command removes the interval from the configuration.
Default 
60
Parameters 
hello-interval
Specifies the time interval, in seconds, between two consecutive tunnel Hello messages.
Default
Values
idle-timeout
Syntax 
idle-timeout idle-timeout
no idle-timeout
Context 
config>router>l2tp>group
Description 
This command configures the period of time that an established tunnel with no active sessions will persist before being disconnected.
Enter the no form of the command to maintain a persistent tunnel.
The no form of the command removes the idle timeout from the configuration.
Default 
no idle-timeout
Parameters 
idle-timeout
Specifies the idle timeout value, in seconds until the group is removed.
Default
Values
lns-group
Syntax 
lns-group lns-group-id
no lns-group
Context 
config>router>l2tp>group
Description 
This command configures the ISA LNS group.
Parameters 
lns-group-id
Specifies the LNS group ID.
Values
load-balance-method
Syntax 
load-balance-method {per-session|per-tunnel}
no load-balance-method
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command describes how new sessions are assigned to an L2TP ISA MDA.
Parameters 
per-session
Specifies that the lowest granularity for load-balancing is a session; each session can be assigned to a different
ISA MDA.
per-tunnel
Specifies that the lowest granularity for load-balancing is a tunnel; all sessions associated with the same tunnel are assigned to the same ISA MDA; this may be useful or required in certain cases, for example:
local-address
Syntax 
local-address ip-address
no local-address
Context 
config>router>l2tp>group>tunnel
Description 
This command configures the local address.
Parameters 
ip-address
Specifies the IP address used during L2TP authentication.
local-name
Syntax 
local-name host-name
no local-name
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command creates the local host name used by this system for the tunnels in this L2TP group during the authentication phase of tunnel establishment. It can be used to distinguish tunnels.
The no form of the command removes thename from the configuration.
Default 
local-name
Parameters 
host-name
Specifies the host name, up to 64 characters in length, that the router will use to identify itself during L2TP authentication.
Default
max-retries-estab
Syntax 
max-retries-estab max-retries
no max-retries-estab
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command configures the number of retries allowed for this L2TP tunnel while it is established, before its control connection goes down.
The no form of the command removes the value from the configuration.
Default 
no max-retries-estab
Parameters 
max-retries
Specifies the maximum number of retries for an established tunnel.
Default
Values
max-retries-not-estab
Syntax 
max-retries-not-estab max-retries
no max-retries-not-estab
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command configures the number of retries allowed for this L2TP tunnel while it is not established, before its control connection goes down.
The no form of the command removes the value from the configuration.
Default 
no max-retries-not-estab
Parameters 
max-retries
Specifies the maximum number of retries for non-established tunnels.
Default
Values
password
Syntax 
password password [hash | hash2]
no password
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command configures the password between L2TP LAC and LNS
The no form of the command removes the password.
Default 
no password
Parameters 
password
Configures the password used for challenge/response calculation and AVP hiding. The maximum length can be up to 20 characters if unhashed, 32 characters if hashed, 54 characters if the hash2 keyword is specified.
hash
Specifies the key is entered in an encrypted form. If the hash parameter is not used, the key is assumed to be in a non-encrypted, clear text form. For security, all keys are stored in encrypted
hash2
Specifies the key is entered in a more complex encrypted form. If the hash2 parameter is not used, the less encrypted hash form is assumed.
Default
ppp
Syntax 
ppp
Context 
config>router>l2tp>group
Description 
This command configures PPP for the L2TP tunnel group.
authentication
Syntax 
authentication {chap|pap|pref-chap}
Context 
config>router>l2tp>group>ppp
Description 
This command configures the PPP authentication protocol to negotiate.
 
authentication-policy
Syntax 
authentication-policy auth-policy-name
no authentication-policy
Context 
config>router>l2tp>group>ppp
Description 
This command configures the authentication policy.
Parameters 
auth-policy-name
Specifies the authentication policy name.
Values
default-group-interface
Syntax 
default-group-interface ip-int-name service-id service-id
no default-group-interface
Context 
config>router>l2tp>group>ppp
Description 
This command configures the default group interface.
Parameters 
ip-int-name
Specifies the interface name.
Values
service-id
Specifies the service ID.
Values
svc-name
Specifies the service name (instead of service ID).
Values
keepalive
Syntax 
keepalive seconds [hold-up-multiplier multiplier]
no keepalive
Context 
config>router>l2tp>group>ppp
Description 
This command configures the PPP keepalive interval and multiplier.
Parameters 
seconds
Specifies in seconds the interval.
Values
multiplier
Specifies the multiplier.
Values
mtu
Syntax 
mtu mtu-bytes
no mtu
Context 
config>router>l2tp>group>ppp
Description 
This command configures the maximum PPP MTU size.
Parameters 
mtu-bytes
Specifies, in bytes, the maximum PPP MTU size.
Values
proxy-authentication
Syntax 
[no] proxy-authentication
Context 
config>router>l2tp>group>ppp
Description 
This command configures the use of the authentication AVPs received from the LAC.
proxy-lcp
Syntax 
[no] proxy-lcp
Context 
config>router>l2tp>group>ppp
Description 
This command configures the use of the proxy LCP AVPs received from the LAC.
user-db
Syntax 
user-db local-user-db-name
no user-db
Context 
config>router>l2tp>group>ppp
Description 
This command configures the local user database to use for PPP PAP/CHAP authentication.
Parameters 
local-user-db-name
Specifies the local user database name.
Values
session-assign-method
Syntax 
session-assign-method weighted
no session-assign-method
Context 
config>router>l2tp>group
Description 
This command specifies how new sessions are assigned to one of the set of suitable tunnels that are available or could be made available.
Default 
no session-assign-method
Parameters 
weighted
specifies that the sessions are shared between the available tunnels. If necessary, new tunnels are set up until the maximum number is reached. The distribution aims at an equal ratio of the actual number of sessions to the maximum number of sessions.
Default
Values
session-limit
Syntax 
session-limit session-limit
no session-limit
Context 
config>router>l2tp>group
config>router>l2tp>group>tunnel
Description 
This command configures the session limit. The value controls how many L2TP session will be allowed within a given context (system, group, tunnel).
The no form of the command removes the value from the configuration.
Default 
no session-limit
Parameters 
session-limit
Specifies the allowed number of sessions within the given context.
Values
Router L2TP Tunnel Commands
tunnel
Syntax 
tunnel tunnel-name [create]
no tunnel tunnel-name
Context 
config>router>l2tp>group
Description 
This command configures an L2TP tunnel. A tunnel exists between a LAC-LNS pair and consists of a Control Connection and zero or more L2TP sessions. The tunnel carries encapsulated PPP datagrams and control messages between the LAC and the L2TP Network Server (LNS).
Parameters 
tunnel-name
Specifies a valid string to identify a L2TP up to 32 characters in length.
create
mandatory while creating a new tunnel
auto-establish
Syntax 
[no] auto-establish
Context 
config>router>l2tp>group>tunnel
Description 
This command specifies if this tunnel is to be automatically set up by the system.
no auto-establish
avp-hiding
Syntax 
avp-hiding {never | sensitive | always}
no avp-hiding
Context 
config>router>l2tp>group>tunnel
Description 
This command configures Attribute Value Pair (AVP) hiding. This capability can be used to avoid the passing of sensitive data, such as user passwords, as cleartext in an AVP.
Note that it is recommended that sensitive information not be sent in clear text.
The no form of the command removes the parameter of the configuration and indicates that the value on group level will be taken.
Default 
no avp-hiding
Parameters 
avp-hiding
Specifies the method to be used for the authentication of the tunnel.
Values
challenge
Syntax 
challenge challenge-mode
no challenge
Context 
config>router>l2tp>group>tunnel
Description 
This command configures the use of challenge-response authentication.
The no form of the command removes the parameter from the configuration and indicates that the value on group level will be taken.
Default 
no challenge
Parameters 
challenge-mode
Specifies when challenge-response is to be used for the authentication of the tunnel.
Values
hello-interval
Syntax 
hello-interval hello-interval
hello-interval infinite
no hello-interval
Context 
config>router>l2tp>group>tunnel
Description 
This command configures the number of seconds between sending Hellos for a L2TP tunnel. The no form removes the parameter from the configuration and indicates that the value on group level will be taken.
Parameters 
hello-interval
Specifies the time interval, in seconds, between two consecutive tunnel Hello messages.
Values
infinite
Specifies that no hello messages are sent.
idle-timeout
Syntax 
idle-timeout idle-timeout
idle-timeout infinite
no idle-timeout
Context 
config>router>l2tp>group>tunnel
Description 
This command configures the idle timeout to wait before being disconnect. The no form indicates that the parameter will be removed from the configuration and that the value specified on group level will be taken.
Parameters 
idle-timeout
Specifies the idle timeout, in seconds.
Values
infinite
Specifies that the tunnel will not be closed when idle.
peer
Syntax 
peer ip-address
no peer
Context 
config>router>l2tp>group>tunnel
Description 
This command configures the peer address.
The no form of the command removes the IP address from the tunnel configuration.
Default 
no peer
Parameters 
ip-address
Sets the LNS IP address for the tunnel.
preference
Syntax 
preference preference
no preference
Context 
config>router>l2tp>group>tunnel
Description 
This command configures a preference number that indicates the relative preference assigned to a tunnel when using a weighted session assignment.
The no form of the command removes the preference value from the tunnel configuration.
Default 
no preference
Parameters 
preference
Specifies the tunnel preference number with its group. The value 0 corresponds to the highest preference.
Values
remote-name
Syntax 
remote-name host-name
no remote-name
Context 
config>router>l2tp>group>tunnel
Description 
This command configures a string to be compared to the host name used by the tunnel peer during the authentication phase of tunnel establishment.
Parameters 
host-name
Specifies a remote host name for the tunnel up to 64 characters in length.
tunnel-selection-blacklist
Syntax 
tunnel-selection-blacklist
Context 
config>router>l2tp
Description 
This command enables the context to configure L2TP Tunnel Selection Blacklist parameters.
add-tunnel
Syntax 
add-tunnel never
add-tunnel on reason [reason...(upto 8 max)]
no add-tunnel
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command will force the tunnel to the blacklist and render it unavailable for new sessions for the duration of pre-configured time. Peers are always forced to the black list in case that they time out (failure to receive response to control packets). In addition to time outs, certain events can be used to trigger placement of the tunnel on the black list.
Parameters 
reason
Specifies the return codes or events that determine which tunnels are added to the blacklist
Values
cdn-err-code — A tunnel will be forced to the blacklist in case that CDN message with the Result Code 2 ( Call disconnected for the reasons indicated in error code) is received.
cdn-inv-dest — A tunnel will be forced to the blacklist in case that CDN message with the Result Codes 6 ( Invalid destination) is received.
cdn-tmp-no-facilities — A tunnel will be forced to the blacklist in case that CDN message with the Result Code 4 is received ( Call failed due to lack of appropriate facilities being available - temporary condition) is received.
cdn-perm-no-facilities — A tunnel will be forced to the blacklist in case that CDN message with the Result Codes 5 ( Call failed due to lack of appropriate facilities being available - permanent condition) is received.
tx-cdn-not-established-in-time — A tunnel will be forced to the blacklist in case that CDN message with the Result Code 10 (Call was not established within time allotted by LAC) is sent from the LAC to the LNS.
stop-ccn-err-code — A tunnel will be forced to the blacklist in case that StopCCN message with the Result Code 2 (General error – Error Code indicates the problem) is sent or received.
stop-ccn-other — A tunnel will be forced to the blacklist in case that StopCCN message with the following Result Codes is received:
(1) General request to clear control connection
(4) Requestor is not authorized to establish a control channel
(5) Protocol version not supported
(6) Requestor is being shutdown
Or in the case that the StopCCN with the following result codes is transmitted:
(4) Requestor is not authorized to establish a control channel.
(5) Protocol version not supported
The receipt of the following Result Codes will NEVER blacklist a tunnel:
(0) Reserved
(3) Control channel already exist
(7) Finite state machine error
(8) Undefined
Transmission of the following Result Codes will NEVER blacklist a tunnel:
(1) General request to clear control connection
(3) Control channel already exist
(6) Requestor is being shutdown
(7) Finite state machine error

addr-change-timeout — A timed-out tunnel for which the peer IP address has changed mid-session (from the one that is provided initially during configuration) will be forced to the blacklist. In absence of this configuration option, only the configured peer for the tunnel will be blacklisted, but not the tunnel itself which now has a different peer address than the one initially configured.
never
When specified, no tunnels will be placed on blacklist under any circumstance. This parameter will available to preserve backward compatibility.
max-list-length
Syntax 
max-list-length unlimited
max-list-length count
no max-list-length
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command configured the maximum length of the peer/tunnel blacklist.
This command specifies how many items (tunnels or peers) can be in the tunnel-selection-blacklist. If a tunnel or peer needs to be added to the tunnel-selection-blacklist and the tunnel-selection-blacklist is full, the system will remove the item (tunnel or peer) from the blacklist that was in this blacklist forthe longest time.
Default 
unlimited
Parameters 
unlimited
Specifies there is no limit.
count
Specifies how many items (tunnels or peers) can be in the tunnel-selection-blacklist.
Values
max-time
Syntax 
max-time minutes
no max-time
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command configures time for which an entity (peer or a tunnel) are kept in the blacklist.
Default 
5 minutes
Parameters 
minutes
Specifies the maximum time a tunnel or peer may remain in the blacklist
Values
timeout-action
Syntax 
timeout-action action
no timeout-action
Context 
configure>router>l2tp>tunnel-selection-blacklist
configure>service>vprn>l2tp>tunnel-selection-blacklist
Description 
This command defines an action that will be executed on the entity (peer/tunnel) in the blacklist once the entity becomes eligible for selection again.
Default 
remove-from-blacklist
Parameters 
action
Specifies the Action to be taken when a tunnel or peer has been in the blacklist for the max-period of time.
Values
 
Router Interface Commands
interface
Syntax 
[no] interface ip-int-name [unnumbered-mpls-tp]
Context 
config>router
Description 
This command creates a logical IP routing or unnumbered MPLS-TP interface. Once created, attributes like IP address, port, or system can be associated with the IP interface.
Interface names are case-sensitive and must be unique within the group of IP interfaces defined for config router interface and config service ies 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. Duplicate interface names can exist in different router instances, although this is not recommended because it is confusing.
When a new name is entered, a new logical router interface is created. When an existing interface name is entered, the user enters the router interface context for editing and configuration.
Although not a keyword, the ip-int-name “system” is associated with the network entity (such as a specific 7450 ESS), not a specific interface. The system interface is also referred to as the loopback address.
An unnumbered MPLS-TP interface is a special type of interface that is only intended for MPLS-TP LSPs. IP routing protocols are blocked on interfaces of this type. If an interface is configured as unnumbered-mpls-tp, then it can only be associated with an Ethernet port or VLAN, using the port command. then either a unicast, multicast or broadcast remote MAC address may be configured. Only static ARP is supported.
The no form of the command removes the IP interface and all the associated configurations. The interface must be administratively shut down before issuing the no interface command.
Default 
No interfaces or names are defined within the system.
Parameters 
ip-int-name
The name of the IP interface. Interface names must be unique within the group of defined IP interfaces for config router interface and config service ies interface commands. An interface name cannot be in the form of an IP address. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
Values
1 32 alphanumeric characters.
If the ip-int-name already exists, the context is changed to maintain that IP interface. If ip-int-name already exists within another service ID or is an IP interface defined within the config router commands, an error will occur and the context will not be changed to that IP interface. If ip-int-name does not exist, the interface is created and the context is changed to that interface for further command processing.
unnumbered-mpls-tp
Specifies that an interface is of type Unnumbered MPLS-TP. An unnumbered MPLS-TP interface is a special type of interface that is only intended for MPLS-TP LSPs. IP routing protocols are blocked on interfaces of this type. If an interface is configured as unnumbered-mpls-tp, then it can only be associated with an Ethernet port or VLAN, using the port command. Either a unicast, multicast or broadcast remote MAC address may be configured using the static-arp command. Only static ARP is supported.
address
Syntax 
address {ip-address/mask | ip-address netmask} [broadcast {all-ones | host-ones}]
no address
Context 
config>router>interface
Description 
This command assigns an IP address, IP subnet, and broadcast address format to an IP interface. Only one IP address can be associated with an IP interface.
An IP address must be assigned to each IP interface. An IP address and a mask combine to create a local IP prefix. The defined IP prefix must be unique within the context of the routing instance. It cannot overlap with other existing IP prefixes defined as local subnets on other IP interfaces in the same routing context within the router.
The local subnet that the address command defines must not be part of the services address space within the routing context by use of the config router service-prefix command. Once a portion of the address space is allocated as a service prefix, that portion is not available to IP interfaces for network core connectivity.
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.
The no form of the command removes the IP address assignment from the IP interface. Interface- specific configurations for IGP protocols like OSPF are also removed. The no form of this command can only be performed when the IP interface is administratively shut down. Shutting down the IP interface will operationally stop any protocol interfaces or MPLS LSPs that explicitly reference that IP address. When a new IP address is defined, the IP interface can be administratively enabled (no shutdown), which reinitializes the protocol interfaces and MPLS LSPs associated with that IP interface. If the no form of the command is executed then the ptp-hw-assist is disabled.
If a new address is entered while another address is still active, the new address will be rejected.
Default 
No IP address is assigned to the IP interface.
Parameters 
ip-address
The IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Values
1.0.0.0 223.255.255.255
/
The forward slash is a parameter delimiter that separates the ip-addr portion of the IP address from the mask that defines the scope of the local subnet. No spaces are allowed between the ip-addr, the “/” and the mask-length parameter. If a forward slash does not ediately follow the ip-addr, a dotted decimal mask must follow the prefix.
mask-length
The subnet mask length when the IP prefix is specified in CIDR notation. When the IP prefix is specified in CIDR notation, a forward slash (/) separates the ip-addr from the mask-length parameter. The mask length parameter indicates the number of bits used for the network portion of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. Allowed values are integers in the range 1— 32. Note that a mask length of 32 is reserved for system IP addresses.
Values
mask
The subnet mask in dotted decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-addr from a traditional dotted decimal mask. The mask parameter indicates the complete mask that will be used in a logical ‘AND’ function to derive the local subnet of the IP address. Note that a mask of 255.255.255.255 is reserved for system IP addresses.
Values
128.0.0.0 255.255.255.255
netmask
The subnet mask in dotted decimal notation.
Values
broadcast {all-ones | host-ones}
The optional broadcast parameter overrides the default broadcast address used by the IP interface when sourcing IP broadcasts on the IP interface. If no broadcast format is specified for the IP address, the default value is host-ones, which indictates 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-addr and the mask-length or mask with all the host bits set to binary 1. This is the default broadcast address used by an IP interface.
The broadcast parameter within the address command does not have a negate feature, which is usually used to revert a parameter to the default value. To change the broadcast type to host-ones after being changed to all-ones, the address command must be executed with the broadcast parameter defined.
The broadcast format on an IP interface can be specified when the IP address is assigned or changed.
This parameter does not affect the type of broadcasts that can be received by the IP interface. A host sending either the local broadcast (all-ones) or the valid subnet broadcast address (host-ones) will be received by the IP interface.
Default
Values
all-ones, host-ones
allow-directed-broadcasts
Syntax 
[no] allow-directed-broadcasts
Context 
config>router>interface
Description 
This command enables the forwarding of directed broadcasts out of the IP interface.
A directed broadcast is a packet received on a local router interface destined for the subnet broadcast address of another IP interface. The allow-directed-broadcasts command on an IP interface enables or disables the transmission of packets destined to the subnet broadcast address of the egress IP interface.
When enabled, a frame destined to the local subnet on this IP interface is sent as a subnet broadcast out this interface. NOTE: Allowing directed broadcasts is a well-known mechanism used for denial-of-service attacks.
By default, directed broadcasts are not allowed and are discarded at this egress IP interface.
The no form of the command disables directed broadcasts forwarding out of the IP interface.
Default 
no allow-directed-broadcasts — Directed broadcasts are dropped.
arp-timeout
Syntax 
arp-timeout seconds
no arp-timeout
Context 
config>router>interface
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 the command reverts to the default value.
Default 
14400 seconds (4 hours)
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 will not be aged.
Values
bfd
Syntax 
bfd transmit-interval [receive receive-interval] [multiplier multiplier] [echo-receive echo-interval] [type cpm-np]
no bfd
Context 
config>router>interface
config>router>interface>ipv6
Description 
This command specifies the bi-directional 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, BGP or PIM) is notified of the fault.
The no form of the command removes BFD from the router interface regardless of the IGP/RSVP.
Important notes: On the 7750-SR, the transmit-interval and receive receive-interval values can only be modified to a value less than 100 ms when:
1.
The type cpm-np option is explicitly configured.
2. The service is shut down (shutdown)
3. The interval is specified 10 — 100000.
4. The service is re-enabled (no shutdown)
To remove the type cpm-np option, re-issue the bfd command without specifying the type parameter.
Default 
no bfd
Parameters 
transmit-interval
Sets the transmit interval, in milliseconds, for the BFD session.
Values
10 — 100000
10 — 100000 (see Important Notes above)
Default
receive receive-interval
Sets the receive interval, in milliseconds, for the BFD session.
Values
10 — 100000
10 — 100000 (see Important Notes above)
Default
multiplier multiplier
Set the multiplier for the BFD session.
Values
Default
echo-receive echo-interval
Sets the minimum echo receive interval, in milliseconds, for the session.
Values
Default
type cpm-np
Selects the CPM network processor as the local termination point for the BFD session. See Important Notes, above.
cflowd
Syntax 
cflowd {acl | interface} [direction]
no cflowd
Context 
config>router>interface
Description 
This command enables cflowd to collect traffic flow samples through a router for analysis.
cflowd is used for network planning and traffic engineering, capacity planning, security, application and user profiling, performance monitoring, usage-based billing, and SLA measurement. When cflowd is enabled at the interface level, all packets forwarded by the interface are subjected to analysis according to the cflowd configuration.
If cflowd is enabled without either egress-only or both specified or with the ingress-only keyword specified, then only ingress sampling will be enabled on the associated IP interface.
Default 
no cflowd
Parameters 
acl
Specifies the policy associated with a filter.
interface
Specifies the policy associated with an IP interface.
direction
Specifies the direction to collect traffic flow samples.
Values
cpu-protection
Syntax 
cpu-protection policy-id
no cpu-protection
Context 
config>router>interface
Description 
This command assigns an existing CPU protection policy for the interface. The CPU protection policies are configured in the config>sys>security>cpu-protection>policy cpu-protection-policy-id context.
Parameters 
policy-id
Specifies an existing CPU protection policy.
Values
delayed-enable
Syntax 
delayed-enable seconds
no delayed-enable
Context 
config>router>if
Description 
This command creates a delay to make the interface operational by the specified number of seconds
The value is used whenever the system attempts to bring the interface operationally up.
Parameters 
seconds
Specifies a delay, in seconds, to make the interface operational.
Values
dist-cpu-protection
Syntax 
dist-cpu-protection policy-name
no dist-cpu-protection
Context 
config>router>if
Description 
This command assigns a Distributed CPU protection policy for the interface.
enable-ingress-stats
Syntax 
[no] enable-ingress-stats
Context 
config>router>interface
config>service>ies >interface
config>service>vprn>interface
config>service>ies>sub-if>grp-if
config>service>vprn>sub-if>grp-if
Description 
This command enables the collection of ingress interface IP stats. This command is only appliable to IP statistics, and not to uRPF statistics.
If enabled, then the following statistics are collected:
Note that octet statistics for IPv4 and IPv6 bytes at IP interfaces include the layer 2 frame overhead.
Default 
no enable-ingress-stats
enable-mac-accounting
Syntax 
[no] enable-mac-accounting
Context 
config>router>interface
Description 
This command enables MAC Accounting functionality for the interface.
if-attribute
Syntax 
if-attribute
Context 
config>router>interface
Description 
This command adds and removes interface attributes.
if-admin-group
Syntax 
[no] if-admin-group group-name [group-name...(upto 5 max)]
Context 
config>router>interface
Description 
This command configures interface Admin Group memberships for this interface.
if-srlg-group
Syntax 
[no] if-srlg-group group-name [group-name...(upto 5 max)]
Context 
config>router>interface
Description 
This command configures interface SRLG Group memberships for this interface
local-proxy-arp
Syntax 
[no] local-proxy-arp
Context 
config>router>interface
Description 
This command enables local proxy ARP on the interface.
Default 
no local-proxy-arp
lag-link-map-profile
Syntax 
lag-link-map-profile link-map-profile-id
no lag-link-map-profile
Context 
config>router>if
Description 
This command assigns a pre-configured lag link map profile to a SAP/network interface configured on a LAG or a PW port that exists on a LAG. Once assigned/de-assigned, the SAP/network interface egress traffic will be re-hashed over LAG as required by the new configuration.
The no form of this command reverts the SAP/network interface to use per-flow, service or link hash as configured for the service/LAG.
Default 
no lag-link-map-profile
Parameters 
link-map-profile-id
An integer from 1 to 32 that defines a unique lag link map profile on which the LAG the SAP/network interface exist.
ldp-shortcut
Syntax 
[no] ldp-shortcut
Context 
config>router
Description 
This command enables the resolution of IGP routes using LDP LSP across all network interfaces participating in the IS-IS and OSPF routing protocol in the system.
When LDP shortcut is enabled, LDP populates the routing table with next-hop entries corresponding to all prefixes for which it activated an LDP FEC. For a given prefix, two route entries are populated in the system routing table. One route corresponds to the LDP shortcut next-hop and has an owner of LDP. The other route is the regular IP next-hop. The LDP shortcut next-hop always has preference over the regular IP next-hop for forwarding user packets and specified control packets over a given outgoing interface to the route next-hop.
All user and specified control packets for which the longest prefix match in RTM yields the FEC prefix will be forwarded over the LDP LSP.
When an IPv4 packet is received on an ingress network interface, a subscriber IES interface, or a regular IES interface, the lookup of the packet by the ingress IOM will result in the packet being sent labeled with the label stack corresponding to the NHLFE of the LDP LSP when the preferred RTM entry corresponds to an LDP shortcut.
If the preferred RTM entry corresponds to an IP next-hop, the IPv4 packet is forwarded unlabelled.
When ECMP is enabled and multiple equal-cost next-hops exit for the IGP route, the ingress IOM will spray the packets for this route based on hashing routine currently supported for IPv4 packets. When the preferred RTM entry corresponds to an LDP shortcut route, spraying will be performed across the multiple next-hops for the LDP FEC. The FEC next-hops can either be direct link LDP neighbors or T-LDP neighbors reachable over RSVP LSPs in the case of LDP-over-RSVP but not both.
When the preferred RTM entry corresponds to a regular IP route, spraying will be performed across regular IP next-hops for the prefix..
The no form of this command disables the resolution of IGP routes using LDP shortcuts.
Default 
no ldp-shortcut
ldp-sync-timer
Syntax 
ldp-sync-timer seconds
no ldp-sync-timer
Context 
config>router>interface
Description 
This command enables synchronization of IGP and LDP. When a link is restored after a failure, IGP sets the link cost to infinity and advertises it. The actual value advertised in OSPF is 0xFFFF (65535). The actual value advertised in IS-IS regular metric is 0x3F (63) and in IS-IS wide-metric is 0xFFFFFE (16777214). This feature is not supported on RIP interfaces.
Note that 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 bounced on this interface or on the system, then only the affected IGP advertises the infinite metric and follow the IGP-LDP synchronization procedures.
Next LDP hello adjacency is brought up with the neighbour. The LDP synchronization timer is started by IGP from the time the LDP session to the neighbor is UP over the interface. This is to allow time for the label-FEC bindings to be exchanged.
When the LDP synchronization timer expires, the link cost is restored and is re-advertised. IGP will announce a new best next-hop and LDP will use it if the label binding for the neighbor’s FEC is available.
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 expired. Also, the new cost value will be advertised after the user executes any of the following commands if the currently advertised cost is different:
If the user changes the value of the LDP synchronization timer parameter, the new value will take effect at the next synchronization event. In other words, if the timer is still running, it will continue using the previous value.
If parallel links exist to the same neighbor, then the bindings and services should remain UP as long as there is one interface that is UP. However, the user configured LDP synchronization timer still applies on the failed then restored interface. In this case, the router will only consider this interface for forwarding after IGP re-advertized its actual cost value.
Note that the LDP Sync Timer State is not always synched across to the standby CPM, so after an activity switch the timer state might not be same as it was on the previous active CPM.
The no form of this command disables IGP/LDP synchronization and deletes the configuration
Default 
no ldp-sync-timer
Parameters 
seconds
Specifies the time interval for the IGP-LDP synchronization timer in seconds.
Values
loopback
Syntax 
[no] loopback
Context 
config>router>interface
Description 
This command configures the interface as a loopback interface.
Default 
Not enabled
lsr-load-balancing
Syntax 
lsr-load-balancing hashing-algorithm
no lsr-load-balancing
Context 
config>router>if
Description 
This command specifies whether the IP header is used in the LAG and ECMP LSR hashing algorithm. This is the per interface setting.
Default 
no lsr-load-balancing
Parameters 
lbl-only
Only the label is used in the hashing algorithm.
lbl-ip
The IP header is included in the hashing algorithm.
ip-only
the IP header is used exclusively in the hashing algorithm
mac
Syntax 
mac ieee-mac-addr
no mac
Context 
config>router>interface
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 the command returns 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.
multihoming
Syntax 
[no] multihoming primary|secondary [hold-time holdover-time]
Context 
config>router>interface
Description 
This command sets the associated loopback interface to be an anycast address used in multi-homing resiliency, as either the primary or a secondary (a primary address on the alternate router). The optional hold-time parameter is only applicable for the secondary context and specifies how long label information learned about the secondary anycast address should be kept after that peer is declared down. This timer should be set to a value large enough for the remainder of the network to detect the failure and complete the reconvergence process.
The no form of the command disables this setting.
Default 
no multihoming
Parameters 
holdover-time
Specifies the number of seconds the router should hold label information learned from the alternate router in its secondary table. This is to allow the reset of the network to reconverge after a router failure before the anycase based label assignments are flushed from the forwarding plane.
Values
Default
network-domain
Syntax 
network-domain network-domain-name
no network-domain
Context 
config>router>interface
Description 
This command assigns a given interface to a given network-domain. The network-domain is then taken into account during sap-ingress queue allocation for VPLS SAP.
The network-domain association can only be done in a base-routing context. Associating a network domain with an loop-back or system interface will be rejected. Associating a network-domain with an interface that has no physical port specified will be accepted, but will have no effect as long as a corresponding port, or LAG, is defined..
Single interfaces can be associated with multiple network-domains.
Default 
per default “default” network domain is assigned
ntp-broadcast
Syntax 
[no] ntp-broadcast
Context 
config>router>interface
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 the command disables SNTP broadcast received on the IP interface.
Default 
no ntp-broadcast
port
Syntax 
port port-name
no port
Context 
config>router>interface
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 re-attempted. The port-id can be in one of the following forms:
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.
When the port-id represents a POS interface, the port-id must include the channel-id. The POS interface must be configured as a network port.
The no form of the command deletes the association with the port. The no form of this command can only be performed when the interface is administratively down.
Default 
No port is associated with the IP interface.
Parameters 
port-name
The physical port identifier to associate with the IP interface.
Values
port-name port-id[:encap-val]
encap-val 0 for null
0..4094 for dot1q
0..4094.* for qinq
port-id slot/mda/port[.channel]
bundle-id - bundle-type-slot/mda.bundle-num
bundle keyword
type ima, fr, ppp
bundle-num 1..336
bpgrp-id bpgrp-type-bpgrp-num
bpgrp keyword
type ima, ppp
bpgrp-num 1..2000
aps-id aps-group-id[.channel]
aps keyword
group-id 1..64
ccag-id ccag-id.path-id[cc-type]
ccag keyword
id 1..8
path-id a, b
cc-type .sap-net, .net-sap
lag-id lag-id
lag keyword
id 1..200
proxy-arp-policy
Syntax 
[no] proxy-arp-policy policy-name [policy-name...(up to 5 max)]
Context 
config>router>interface
Description 
This command enables and configure 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 given 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 router responds to ARP requests on behalf of another device. Static ARP is used when a 7750 SR needs to know about a device on an interface that cannot or does not respond to ARP requests. Thus, the 7750 SR OS configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address.
Default 
no proxy-arp-policy
Parameters 
policy-name
The export route policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. The specified policy name(s) must already be defined.
ptp-hw-assist
Syntax 
[no] ptp-hw-assist
Context 
config>router>interface
Description 
This command configures the 1588 port based timestamping assist function for the interface. Various checks are performed to ensure that this feature can be enabled. If a check fails, either:
Default 
no ptp-hw-assist
qos-route-lookup
Syntax 
qos-route-lookup [source | destination]
no qos-route-lookup
Context 
config>router>interface
config>router>interface>ipv6
Description 
This command enables QoS classification of the ingress IP packets on an interface based on the QoS information associated with routes in the forwarding table.
If the optional destination parameter is specified and the destination address of an incoming IP packet matches a route with QoS information the packet is classified to the fc and priority associated with that route, overriding the fc and priority/profile determined from the sap-ingress or network qos policy associated with the IP interface. If the destination address of the incoming packet matches a route with no QoS information the fc and priority of the packet remain as determined by the sap-ingress or network qos policy.
If the optional source parameter is specified and the source address of an incoming IP packet matches a route with QoS information the packet is classified to the fc and priority associated with that route, overriding the fc and priority/profile determined from the sap-ingress or network qos policy associated with the IP interface. If the source address of the incoming packet matches a route with no QoS information the fc and priority of the packet remain as determined by the sap-ingress or network qos policy.
If neither the optional source or destination parameter is present, then the default is destination address matching.
The functionality enabled by the qos-route-lookup command can be applied to IPv4 packets or IPv6 packets on an interface, depending on whether it is present at the interface context (applies to IPv4) or the interface>ipv6 context (applies to IPv6). The ability to specify source address based QoS lookup is not supported for IPv6. Subscriber management group interfaces also do not support the source QPPB option.
The no form of the command reverts to the default.
Default 
destination
Parameters 
source
Enables QoS classification of incoming IP packets based on the source address matching a route with QoS information.
destination
Enables QoS classification of incoming IP packets based on the destination address matching a route with QoS information.
 
qos
Syntax 
qos network-policy-id [egress-port-redirect-group queue-group-name] [egress-instance instance-id]] [ingress-fp- redirect-group queue-group-name ingress-instance instance-id]
no qos
Context 
config>router>interface
Description 
This command associates a network Quality of Service (QoS) policy with a network IP interface. Only one network QoS policy can be associated with an IP interface at one time. Attempts to associate a second QoS policy return an error.
Associating a network QoS policy with a network interface is useful for the following purposes:
The no form of the command removes the network QoS policy association from the network IP interface, and the QoS policy reverts to the default.
Default 
no qos
Parameters 
network-policy-id
An existing network policy ID to associate with the IP interface.
Values
egress-port-redirect-group queue-group-name
This optional parameter specifies the egress queue-group used for all egress forwarding-class redirections specified within the network QoS policy ID. The specified queue-group-name must exist as an egress queue group applied to the egress context of the port associated with the IP interface.
egress-instance instance-id
Since multiple instances of the same egress queue-group can be applied to the same port this optional parameter is used to specify which particular instance to associate with this particular network IP interface.
Values
ingress-fp- redirect-group queue-group-name
This optional parameter specifies the ingress queue-group used for all ingress forwarding-class redirections specified within the network QoS policy ID. The specified queue-group-name must exist as an ingress queue group applied to the ingress context of the forwarding plane associated with the IP interface.
ingress-instance instance-id
Since multiple instances of the same ingress queue-group can be applied to the same forwarding plane this parameter is required to specify which particular instance to associate with this particular network IP interface.
Values
remote-proxy-arp
Context 
config>router>interface
Description 
This command enables remote proxy ARP on the interface.
Default 
no remote-proxy-arp
secondary
Syntax 
secondary {[ip-address/mask | ip-address netmask]} [broadcast {all-ones | host-ones}] [igp-inhibit]
no secondary ip-addr
Context 
config>router>interface
Description 
Use this command to assign up to 16 secondary IP addresses to the interface. Each address can be configured in an IP address, IP subnet or broadcast address format.
ip-address
The IP address of the IP interface. The ip-address portion of the address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Values
/
The forward slash is 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-addr, the “/” and the mask-length parameter. If a forward slash does not ediately follow the ip-addr, a dotted decimal mask must follow the prefix.
mask-length
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-length parameter. The mask length parameter indicates the number of bits used for the network portion of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. Allowed values are integers in the range 1— 32. Note that a mask length of 32 is reserved for system IP addresses.
Values
mask
The subnet mask in dotted decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-addr from a traditional dotted decimal mask. The mask parameter indicates the complete mask that will be used in a logical ‘AND’ function to derive the local subnet of the IP address. Note that a mask of 255.255.255.255 is reserved for system IP addresses.
Values
broadcast {all-ones | host-ones}
The optional broadcast parameter overrides the default broadcast address used by the IP interface when sourcing IP broadcasts on the IP interface. If no broadcast format is specified for the IP address, the default value is host-ones, which indicates a subnet broadcast address. Use this parameter to change the broadcast address to all-ones or revert back to a broadcast address of host-ones.
The all-ones keyword following the broadcast parameter specifies that the broadcast address used by the IP interface for this IP address will be 255.255.255.255, also known as the local broadcast.
The host-ones keyword following the broadcast parameter specifies that the broadcast address used by the IP interface for this IP address will be the subnet broadcast address. This is an IP address that corresponds to the local subnet described by the ip-addr and the mask-length or mask with all the host bits set to binary 1. This is the default broadcast address used by an IP interface.
The broadcast parameter within the address command does not have a negate feature, which is usually used to revert a parameter to the default value. To change the broadcast type to host-ones after being changed to all-ones, the address command must be executed with the broadcast parameter defined.
The broadcast format on an IP interface can be specified when the IP address is assigned or changed.
This parameter does not affect the type of broadcasts that can be received by the IP interface. A host sending either the local broadcast (all-ones) or the valid subnet broadcast address (host-ones) will be received by the IP interface.
igp-inhibit
The secondary IP address should not be recognized as a local interface by the running IGP.
static-arp
Syntax 
static-arp ip-addr ieee-mac-addr unnumbered
no static-arp unnumbered
Context 
config>router>interface
Description 
This command configures a static Address Resolution Protocol (ARP) entry associating an IP address with a MAC address for the core router instance. This static ARP appears in the core routing ARP table. A static ARP can only be configured if it exists on the network attached to the IP interface.
If an entry for a particular IP address already exists and a new MAC address is configured for the IP address, the existing MAC address is replaced by the new MAC address.
The number of static-arp entries that can be configured on a single node is limited to 1000.
Static ARP is used when a
7750 SR needs to know about a device on an interface that cannot or does not respond to ARP requests. Thus, the 7750 SR OS configuration can state that if it has a packet that has a certain IP address to send it to the corresponding ARP address. Use proxy ARP so the 7750 SR responds to ARP requests on behalf of another device.
The no form of the command removes a static ARP entry.
Default 
No static ARPs are defined.
Parameters 
unnumbered
Specifies the static ARP MAC for an unnumbered interface. Unnumbered interfaces support dynamic ARP. Once this command is configured, it overrides any dynamic ARP.
ieee-mac-addr
Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.
strip-label
Syntax 
[no] strip-label
Context 
config>router>interface
Description 
This command forces packets to be stripped of all (max 5) MPLS labels before the packets are handed over for possible filter (PBR) processing.
If the packets do not have an IP header immediately following the MPLS label stack after the strip, they are discarded. Only MPLS encapsulated IP, IGP shortcuts and VPRN over MPLS packets will be processed.
This command is only supported on:
The no form of the command removes the strip-label command.
In order to associate an interface that is configured with the strip-label parameter with a port, the port must be configured as single-fiber for the command to be valid.
Default 
no strip-label
tos-marking-state
Syntax 
tos-marking-state {trusted | untrusted}
no tos-marking-state
Context 
config>router>interface
Description 
This command is used on a network IP interface to alter the default trusted state to a non-trusted state. When unset or reverted to the trusted default, the ToS field will not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set, in which case the egress network interface treats all IES and network IP interface as untrusted.
When the ingress network IP interface is set to untrusted, all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface. The egress network remarking rules also apply to the ToS field of IP packets routed using IGP shortcuts (tunneled to a remote next-hop). However, the tunnel QoS markings are always derived from the egress network QoS definitions.
Egress marking and remarking is based on the internal forwarding class and profile state of the packet once it reaches the egress interface. The forwarding class is derived from ingress classification functions. The profile of a packet is either derived from ingress classification or ingress policing.
The default marking state for network IP interfaces is trusted. This is equivalent to declaring no tos-marking-state on the network IP interface. When undefined or set to tos-marking-state trusted, the trusted state of the interface will not be displayed when using show config or show info unless the detail parameter is given. The
save config command will not store the default tos-marking-state trusted state for network IP interfaces unless the detail parameter is also specified.
The no form of the command is used to restore the trusted state to a network IP interface. This is equivalent to executing the tos-marking-state trusted command.
Default 
trusted
Parameters 
trusted
The default prevents the ToS field to not be remarked by egress network IP interfaces unless the egress network IP interface has the remark-trusted state set
untrusted
Specifies that all egress network IP interfaces will remark IP packets received on the network interface according to the egress marking definitions on each network interface.
unnumbered
Syntax 
unnumbered [ip-address | ip-int-name]
no unnumbered
Context 
config>router>interface
Description 
This command sets an IP interface as an unnumbered interface and specifies the IP address to be used for the interface.
To conserve IP addresses, unnumbered interfaces can be configured. The address used when generating packets on this interface is the ip-addr parameter configured.
An error message will be generated if an unnumbered interface is configured, and an IP address already exists on this interface.
The no form of the command removes the IP address from the interface, effectively removing the unnumbered property. The interface must be shutdown before no unnumbered is issued to delete the IP address from the interface, or an error message will be generated.
Parameters 
ip-addr | ip-int-name
Optional. The IP address or IP interface name to associate with the unnumbered IP interface in dotted decimal notation. The configured IP address must exist on this node. It is recommended 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 no ip-addr or ip-int-name is configured.
Default
no unnumbered
qos-route-lookup
Syntax 
qos-route-lookup [source | destination]
no qos-route-lookup
Context 
config>router>if
config>router>if>ipv6
Description 
This command enables QoS classification of the ingress IP packets on an interface based on the QoS information associated with routes in the forwarding table.
If the optional destination parameter is specified and the destination address of an incoming IP packet matches a route with QoS information the packet is classified to the fc and priority associated with that route, overriding the fc and priority/profile determined from the sap-ingress or network qos policy associated with the IP interface. If the destination address of the incoming packet matches a route with no QoS information the fc and priority of the packet remain as determined by the sap-ingress or network qos policy.
If the optional source parameter is specified and the source address of an incoming IP packet matches a route with QoS information the packet is classified to the fc and priority associated with that route, overriding the fc and priority/profile determined from the sap-ingress or network qos policy associated with the IP interface. If the source address of the incoming packet matches a route with no QoS information the fc and priority of the packet remain as determined by the sap-ingress or network qos policy.
If neither the optional source or destination parameter is present, then the default is destination address matching.
The functionality enabled by the qos-route-lookup command can be applied to IPv4 packets or IPv6 packets on an interface, depending on whether it is present at the interface context (applies to IPv4) or the interface>ipv6 context (applies to IPv6). The ability to specify source address based QoS lookup is not supported for IPv6. Subscriber management group interfaces also do not support the source QPPB option.
The no form of the command reverts to the default.
Default 
destination
Parameters 
source
Enables QoS classification of incoming IP packets based on the source address matching a route with QoS information.
destination
Enables QoS classification of incoming IP packets based on the destination address matching a route with QoS information.
urpf-check
Syntax 
[no] urpf-check
Context 
config>router>if
config>router>if>ipv6
Description 
This command enables unicast RPF (uRPF) Check on this interface.
The no form of the command disables unicast RPF (uRPF) Check on this interface.
Default 
disabled
mode
Syntax 
mode {strict | loose | strict-no-ecmp}
no mode
Context 
config>router>if>urpf-check
config>router>if>>ipv6>urpf-check
Description 
This command specifies the mode of unicast RPF check.
The no form of the command reverts to the default (strict) mode.
Default 
strict
Parameters 
strict
When specified, uRPF checks whether incoming packet has a source address that matches a prefix in the routing table, and whether the interface expects to receive a packet with this source address prefix.
loose
In loose mode, uRPF checks whether incoming packet has source address with a corresponding prefix in the routing table. However, the loose mode does not check whether the interface expects to receive a packet with a specific source address prefix. This object is valid only when urpf-check is enabled.
strict-no-ecmp
When a packet is received on an interface in this mode and the SA matches an ECMP route the packet is dropped by uRPF.
mh-primary-interface
Syntax 
[no] mh-primary-interface
Context 
config>router
Description 
This command creates a loopback interface for use in multihoming resiliency. Once active, this interface can be used to advertise reachability information to the rest of the network using the primary address, which is backed up by the secondary.
The reachability for this address is advertised via IGPs and LDP protocols to allow the resolution of BGP routes advertised with this address.
The no form of the command disables this setting.
Default 
no multihoming
address
Syntax 
address {ip-address/mask | ip-address netmask}
no address
Context 
config>router>mh-primary-interface
config>router>mh-secondary-interface
Description 
This command assigns an IP address, IP subnet and broadcast address format to an IP interface. Only one IP address can be associated with an IP interface. An IP address must be assigned to each IP interface for the interface to be active. An IP address and a mask combine to create a local IP prefix. The defined IP prefix must be unique within the context of the routing instance. It cannot overlap with other existing IP prefixes defined as local subnets on other IP interface in the same routing context within the router.
The local subnet that the address command defines must not be part of the services address space within the routing context by use of the config>router>service-prefix command. Once a portion of the address space is allocated as a service prefix, that portion is not available to IP interfaces for network core connectivity. 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.
The no form of the command removes the IP address assignment from the IP interface. Interface specific configurations for IGP protocols like OSPF are also removed. The no form of this command can only be performed when the IP interface is administratively shut down. Shutting down the IP interface will operationally stop any protocol interfaces or MPLS LSPs that explicitly reference that IP address. When a new IP address is defined, the IP interface can be administratively enabled (no shutdown), which reinitializes the protocol interfaces and MPLS LSPs associated with that IP interface.
If a new address is entered while another address is still active, the new address wil be rejected.
Parameters 
ip-address
The IP address of the IP interface. The ip-addr portion of the address command specifies the IP host address that will be used by the IP interface within the subnet. This address must be unique within the subnet and specified in dotted decimal notation.
Values
/
The forward slash is a parameter delimiter that separates the ipp-addr portion of the IP address from the mask that defines the scope of the local subnet. No spaces are allowed between the ip-addr, the “/” and the mask-length parameter. If a forward slash does not immediately follow the ip-addr, a dotted decimal mask must follow the prefix.
mask-length
The subnet mask length when the IP prefix is specified in CIDR notation. When the IP prefix is specified in CIDR notation, a forward slash (/) separates the ip-addr from the mask-length parameter. The mask length parameter indicates the number of bits used for the network portion of the IP address; the remainder of the IP address is used to determine the host portion of the IP address. Allowed values are integers in the range 1-32. Note that a mask length of 32 is reserved for system IP addresses.
Values
mask
The subnet mask in dotted decimal notation. When the IP prefix is not specified in CIDR notation, a space separates the ip-addr from a traditional dotted decimal mask. The mask parameters indicates the complete mask that will be used ina logical ‘AND’ function to derive the local subnet of the IP address. Note that a mask of 255.255.255.255 is reserved for system IP addresses.
Values
netmask
The subnet mask in dotted decimal notation.
Values
description
Syntax 
description description-string
no description
Context 
config>router>mh-primary-interface
config>router>mh-secondary-interface
Description 
This command creates a text description stored in the configuration file for a configuration context.
The no form of the command removes the description string from the context.
Default 
no description
Parameters 
description-string
The description character string. Allowed values are any string up to 80 characters long composed of printable, 7-bit ASCII characters. If the string contains special character (#, $, space, etc.), the entire string must be enclosed within double quotes.
shutdown
Syntax 
[no] shutdown
Context 
config>router>mh-primary-interface
config>router>mh-secondary-interface
Description 
The shutdown command administratively disables an entity. The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.
Unlike other commands and parameters where the default state is not indicated in the configuration file, shutdown and no shutdown are always indicated in system generated configuration files.
The no form of the command puts an entity into the administratively enabled state.
Default 
no shutdown
mh-secondary-interface
Syntax 
[no] mh-secondary-interface
Context 
config>router
Description 
This command creates a loopback interface for use in multihoming resiliency. This address is considered the secondary multihoming address and is only used to resolve routes advertised by the primary router in the event that router becomes unavailable. For this purpose, the reachability for this address is advertised via IGPs and LDP protocols to allow the resolution of BGP routes advertised with this address by the primary multihoming router.
The no form of the command disables this setting.
Default 
no mh-secondary-interface
hold-time
Syntax 
hold-time holdover-time
no hold-time
Context 
config>router>mh-secondary-interface
Description 
The optional hold-time parameter is only applicable for the secondary context and specifies how long label information leraned about the secondary anycast address should be kept after that peer is declared down. This timer should be set to a value large enough for the remainder of the network to detect the failure and complete the reconvergence process.
The no form of the command resets the hold-time back to the default value.
Default 
no hold-time
Parameters 
holdover-time
Specifies the number of seconds the router should hold label information learned from the alternate router in its secondary label table. This is to allow the reset of the network to reconverge after a router failure before the anycast based label assignments are flushed from the forwarding plane.
Values
Default
Router Interface Filter Commands
egress
Syntax 
egress
Context 
config>router>interface
Description 
This command enables access to the context to 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
Description 
This command enables access to the context to configure ingress network filter policies for the IP interface. If an ingress filter is not defined, no filtering is performed.
flowspec
Syntax 
[no] flowspec
Context 
config>router>interface>ingress
Description 
This command enables IPv4 flowspec filtering on a network IP interface. Filtering is based on all of the IPv4 flowspec routes that have been received and accepted by the base router BGP instance. Ingress IPv4 traffic on an interface can be filtered by both a user-defined IPv4 filter and flowspec. Evaluation proceeds in this order:
1.user-defined IPv4 filter entries
2.flowspec-derived filter entries
3.user-defined IPv4 filter default-action
The no form of the command removes IPv4 flowspec filtering from the network IP interface.
Default 
No network interfaces have IPv4 flowspec enabled.
flowspec-ipv6
Syntax 
[no] flowspec
Context 
config>router>interface>ingress
Description 
This command enables IPv6 flowspec filtering on a network IP interface. Filtering is based on all of the IPv6 flowspec routes that have been received and accepted by the base router BGP instance. Ingress IPv6 traffic on an interface can be filtered by both a user-defined IPv4 filter and flowspec. Evaluation proceeds in this order:
1.user-defined IPv6 filter entries
2.flowspec-derived filter entries
3.user-defined IPv6 filter default-action
The no form of the command removes IPv6 flowspec filtering from the network IP interface.
Default 
No network interfaces have IPv6 flowspec enabled.
filter
Syntax 
filter ip ip-filter-id
filter ipv6 ipv6-filter-id
no filter [ip ip-filter-ip] [ipv6 ipv6-filter-id]
Context 
config>router>if>ingress
config>router>if>egress
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 pre-configured before this filter command is executed. If the filter ID does not exist, an error occurs.
Only one filter ID can be specified.
The no form of the command removes the filter policy association with the IP interface.
Default 
No filter is specified.
Parameters 
ip ip-filter-id
The filter name acts as the ID for the IP filter policy expressed as a decimal integer. The filter policy must already exist within the config>filter>ip context.
Values
ipv6 ipv6-filter-id
The filter name acts as the ID for the IPv6 filter policy expressed as a decimal integer. The filter policy must already exist within the config>filter>ipv6 context.
Values
Router Interface ICMP Commands
icmp
Syntax 
icmp
Context 
config>router>interface
Description 
This command enables access to 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.
mask-reply
Syntax 
[no] mask-reply
Context 
config>router>if>icmp
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 the command disables replies to ICMP mask requests on the router interface.
Default 
mask-reply — Replies to ICMP mask requests.
redirects
Syntax 
redirects [number seconds]
no redirects
Context 
config>router>if>icmp
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 given 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 the command disables the generation of ICMP redirects on the router interface.
Default 
redirects 100 10 — Maximum of 100 redirect messages in 10 seconds.
Parameters 
number
The maximum number of ICMP redirect messages to send, expressed as a decimal integer. This parameter must be specified with the time parameter.
Values
seconds
The time frame, in seconds, used to limit the number of ICMP redirect messages that can be issued,expressed as a decimal integer.
Values
ttl-expired
Syntax 
ttl-expired [number seconds]
no ttl-expired
Context 
config>router>if>icmp
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 the command disables the generation of TTL expired messages.
Default 
ttl-expired 100 10 — Maximum of 100 TTL expired message in 10 seconds.
Parameters 
number
The maximum number of ICMP TTL expired messages to send, expressed as a decimal integer. The seconds parameter must also be specified.
Values
seconds
The time frame, in seconds, used to limit the number of ICMP TTL expired messages that can be issued, expressed as a decimal integer.
Values
unreachables
Syntax 
unreachables [number seconds]
no unreachables
Context 
config>router>if>icmp
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 given 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 the command disables the generation of ICMP destination unreachables on the router interface.
Default 
unreachables 100 10 — Maximum of 100 unreachable messages in 10 seconds.
Parameters 
number
The maximum number of ICMP unreachable messages to send, expressed as a decimal integer. The seconds parameter must also be specified.
Values
seconds
The time frame, in seconds, used to limit the number of ICMP unreachable messages that can be issued, expressed as a decimal integer.
Router Interface IPv6 Commands
ipv6
Syntax 
[no] ipv6
Context 
config>router>interface
Description 
This command configures IPv6 for a router interface.
The no form of the 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
Description 
This command assigns an IPv6 address to the interface.
Default 
none
Parameters 
ipv6-address/prefix-length
Specify the IPv6 address on the interface.
Values
eui-64
When the eui-64 keyword is specified, a complete IPv6 address from the supplied prefix and 64-bit interface identifier is formed. The 64-bit interface identifier is derived from MAC address on Ethernet interfaces. For interfaces without a MAC address, for example POS interfaces, the Base MAC address of the chassis should be used.
icmp6
Syntax 
icmp6
Context 
config>router>if>ipv6
Description 
This command enables the context to 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
Description 
This command configures the rate for ICMPv6 packet-too-big messages.
Parameters 
number
Limits the number of packet-too-big messages issued per the time frame specifed in the seconds parameter.
Values
seconds
Determines the time frame, in seconds, that is used to limit the number of packet-too-big messages issued per time frame.
Values
param-problem
Syntax 
param-problem [number seconds]
no param-problem
Context 
config>router>if>ipv6>icmp6
Description 
This command configures the rate for ICMPv6 param-problem messages.
Parameters 
number
Limits the number of param-problem messages issued per the time frame specifed in the seconds parameter.
Values
seconds
Determines the time frame, in seconds, that is used to limit the number of param-problem messages issued per time frame.
Values
redirects
Syntax 
redirects [number seconds]
no redirects
Context 
config>router>if>ipv6>icmp6
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 the command disables ICMPv6 redirects.
Default 
100 10 (when IPv6 is enabled on the interface)
Parameters 
number
Limits the number of redirects issued per the time frame specifed in seconds parameter.
Values
seconds
Determines the time frame, in seconds, that is used to limit the number of redirects issued per time frame.
Values
time-exceeded
Syntax 
time-exceeded [number seconds]
no time-exceeded
Context 
config>router>if>ipv6>icmp6
Description 
This command configures rate for ICMPv6 time-exceeded messages.
Parameters 
number
Limits the number of time-exceeded messages issued per the time frame specifed in seconds parameter.
Values
seconds
Determines the time frame, in seconds, that is used to limit the number of time-exceeded messages issued per time frame.
Values
unreachables
Syntax 
unreachables [number seconds]
no unreachables
Context 
config>router>if>ipv6>icmp6
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 the 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
Determines the number destination unreachable ICMPv6 messages to issue in the time frame specified in seconds parameter.
Values
seconds
Sets the time frame, in seconds, to limit the number of destination unreachable ICMPv6 messages issued per time frame.
Values
link-local-address
Syntax 
link-local-address ipv6-address [preferred]
no link-local-address
Context 
config>router>if>ipv6
Description 
This command configures the link local address.
local-proxy-nd
Syntax 
[no] local-proxy-nd
Context 
config>router>if>ipv6
Description 
This command enables local proxy neighbor discovery on the interface.
The no form of the 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
Description 
This command configure a proxy neighbor discovery policy for the interface.
Parameters 
policy-name
The neighbor discovery policy name. Allowed values are any string up to 32 characters long composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes. The specified policy name(s) must already be defined.
neighbor
Syntax 
neighbor [ipv6-address] [mac-address]
no neighbor [ipv6-address]
Context 
config>router>if>ipv6
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
The IPv6 address assigned to a router interface.
Values
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.
 
Router Advertisement Commands
router-advertisement
Syntax 
[no] router-advertisement
Context 
config>router
Description 
This command configures router advertisement properties. By default, it is disabled for all IPv6 enabled interfaces.
The no form of the command disables all IPv6 interface. However, the no interface interface-name command disables a specific interface.
Default 
disabled
interface
Syntax 
[no] interface ip-int-name
Context 
config>router>router-advertisement
Description 
This command configures router advertisement properties on a specific interface. The interface must already exist in the config>router>interface context.
Default 
No interfaces are configured by default.
Parameters 
ip-int-name
Specify the interface name. If the string contains special characters (#, $, spaces, etc.), the entire string must be enclosed within double quotes.
current-hop-limit
Syntax 
current-hop-limit number
no current-hop-limit
Context 
config>router>router-advert>if
Description 
This command configures the current-hop-limit in the router advertisement messages. It informs the nodes on the subnet about the hop-limit when originating IPv6 packets.
Default 
64
Parameters 
number
Specifies the hop limit.
Values
 
managed-configuration
Syntax 
[no] managed-configuration
Context 
config>router>router-advert>if
Description 
This command sets the managed address configuration flag. This flag indicates that DHCPv6 is available for address configuration in addition to any address autoconfigured using stateless address autoconfiguration. See RFC 3315, Dynamic Host Configuration Protocol (DHCP) for IPv6.
Default 
no managed-configuration
max-advertisement-interval
Syntax 
[no] max-advertisement-interval seconds
Context 
config>router>router-advert>if
Description 
This command configures the maximum interval between sending router advertisement messages.
Default 
600
Parameters 
seconds
Specifies the maximum interval in seconds between sending router advertisement messages.
Values
min-advertisement-interval
Syntax 
[no] min-advertisement-interval seconds
Context 
config>router>router-advert>if
Description 
This command configures the minimum interval between sending ICMPv6 neighbor discovery router advertisement messages.
Default 
200
Parameters 
seconds
Specify the minimum interval in seconds between sending ICMPv6 neighbor discovery router advertisement messages.
Values
mtu
Syntax 
[no] mtu mtu-bytes
Context 
config>router>router-advert>if
Description 
This command configures the MTU for the nodes to use to send packets on the link.
Default 
no mtu — The MTU option is not sent in the router advertisement messages.
Parameters 
mtu-bytes
Specify the MTU for the nodes to use to send packets on the link.
Values
other-stateful-configuration
Syntax 
[no] other-stateful-configuration
Description 
This command sets the "Other configuration" flag. This flag indicates that DHCPv6lite is available for autoconfiguration of other (non-address) information such as DNS-related information or information on other servers in the network.See RFC 3736, Stateless Dynamic Host Configuration Protocol (DHCP) for IPv6
Default 
no other-stateful-configuration
prefix
Syntax 
[no] prefix [ipv6-prefix/prefix-length]
Context 
config>router>router-advert>if
Description 
This command configures an IPv6 prefix in the router advertisement messages. To support multiple IPv6 prefixes, use multiple prefix statements. No prefix is advertised until explicitly configured using prefix statements.
Default 
none
Parameters 
ip-prefix
The IP prefix for prefix list entry in dotted decimal notation.
Values
prefix-length
Specifies a route must match the most significant bits and have a prefix length.
Values
autonomous
Syntax 
[no] autonomous
Context 
config>router>router-advert>if>prefix
Description 
This command specifies whether the prefix can be used for stateless address autoconfiguration.
Default 
enabled
on-link
Syntax 
[no] on-link
Context 
config>router>router-advert>if>prefix
Description 
This command specifies whether the prefix can be used for onlink determination.
Default 
enabled
preferred-lifetime
Syntax 
[no] preferred-lifetime {seconds | infinite}
Context 
config>router>router-advert>if
Description 
This command configures the remaining length of time in seconds that this prefix will continue to be preferred, such as, time until deprecation. The address generated from a deprecated prefix should not be used as a source address in new communications, but packets received on such an interface are processed as expected.
Default 
604800
Parameters 
seconds
Specifies the remaining length of time in seconds that this prefix will continue to be preferred.
infinite
Specifies that the prefix will always be preferred. A value of 4,294,967,295 represents infinity.
valid-lifetime
Syntax 
valid-lifetime {seconds | infinite}
Context 
config>router>router-advert>if
Description 
This command specifies the length of time in seconds that the prefix is valid for the purpose of on-link determination. A value of all one bits (0xffffffff) represents infinity.
The address generated from an invalidated prefix should not appear as the destination or source address of a packet.
Default 
2592000
Parameters 
seconds
Specifies the remaining length of time in seconds that this prefix will continue to be valid.
infinite
Specifies that the prefix will always be valid. A value of 4,294,967,295 represents infinity.
reachable-time
Syntax 
reachable-time milli-seconds
no reachable-time
Context 
config>router>router-advert>if
Description 
This command configures how long this router should be considered reachable by other nodes on the link after receiving a reachability confirmation.
Default 
no reachable-time
Parameters 
milli-seconds
Specifies the length of time the router should be considered reachable.
Values
retransmit-time
Syntax 
retransmit-timer milli-seconds
no retransmit-timer
Context 
config>router>router-advert>if
Description 
This command configures the retransmission frequency of neighbor solicitation messages.
Default 
no retransmit-time
Parameters 
milli-seconds
Specifies how often the retransmission should occur.
Values
router-lifetime
Syntax 
router-lifetime seconds
no router-lifetime
Context 
config>router>router-advert>if
Description 
This command sets the router lifetime.
Default 
1800
Parameters 
seconds
The length of time, in seconds, (relative to the time the packet is sent) that the prefix is valid for route determination.
Values
use-virtual-mac
Syntax 
[no] use-virtual-mac
Context 
config>router>router-advert>if
Description 
This command enables sending router advertisement messages using the VRRP virtual MAC address, provided that the virtual router is currently the master.
If the virtual router is not the master, no router advertisement messages are sent.
The no form of the command disables sending router advertisement messages.
Default 
no use-virtual-mac