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.
The no form of the command puts an entity into the administratively enabled state.
The no form of the command removes the description string from the context.
aggregate ip-prefix/ip-prefix-length [summary-only
] [as-set
] [aggregator
as-number:ip-address] [black-hole
] [community
comm-id] [description
description]
aggregate ip-prefix/ip-prefix-length [summary-only
] [as-set
] [aggregator
as-number:ip-address] [community
comm-id] [indirect
ip-address] [description
description]
The no form of the command removes the aggregate.
To remove the summary-only option, enter the same aggregate command without the
summary-only parameter.
|
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
|
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.
confederation confed-as-num members as-number [as-number...up to 15 max]
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 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.
The weight assigned to an LSP impacts only the forwarding decision, not the routing decision. In other words, it does not change the selection of the set of ECMP tunnel next-hops of a prefix when more next-hops exist than the value of the router ecmp option. Once the set of tunnel next-hops is selected, the LSP weight is used to modulate the amount of packets forwarded over each next-hop. It also does not change the hash routine, but only the spraying of the flows over the tunnel next-hops is modified to reflect the normalized weight of each tunnel next-hop.
The no form of command disables the tunneling of ICMP reply packets over MPLS LSP at a LSR node.
[no
] ignore-icmp-redirect
The no form of this command disables the IP FRR feature on the system
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.
The no form of the command removes the description string from the context.
This command is used to configure the refresh-time and
hold-time intervals that are used for liveness detection of the RPKI-Router session. The
refresh-time defaults to 300 seconds and is reset whenever a Reset Query PDU or Serial Query PDU is sent to the cache server. When the timer expires, a new Serial Query PDU is sent with the last known serial number.
The hold-time specifies the length of time in seconds that the session is to be considered UP without any indication that the cache server is alive and reachable. The timer defaults to 600 seconds and must be at least 2x the refresh-time (otherwise the CLI command is not accepted). Reception of any PDU from the cache server resets the hold timer. When the
hold-time expires, the session is considered to be DOWN and the stale timer is started.
static-entry ip-prefix/ip-prefix-length upto
prefix-length2 origin-as
as-number [valid
| invalid
]
no static-entry ip-prefix/ip-prefix-length upto
prefix-length2 origin-as
as-number
Note that static entries can only be configured under the config>router>origin-validation context of the base router.
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.
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
.
The purpose of reserving IP addresses using service-prefix is to provide a mechanism to reserve one or more address ranges for services.
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.
|
Values
|
bgp, cflowd, dhcp, dns, ftp, icmp, igmp, igmp-reporter, l2tp, ldp, mld, msdp, ndis, ntp, ospf, pim, ptp, radius, rip, rsvp, snmp, snmp-notification, srrp, ssh, syslog, tacplus, telnet, tftp, traceroute, vrrp
|
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
dscp dscp-name fc
fc-name
|
Values
|
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
|
The no form of this command configures the router to not set overload if an SFM fails.
[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] [
padding-size padding-size] [
log]} {
prefix-list prefix-list-name [
all |
none]} |{
fc fc-name [
priority {
low |
high}] [
ldp-sync] [
validate-next-hop]
[no]
static-route {
ip-prefix/prefix-length |
ip-prefix netmask} [
preference preference] [
metric metric] [
tag tag] [
community comm-id] [
enable |
disable]
indirect ip-address [
cpe-check cpe-ip-address [
interval seconds] [
drop-count count] [
padding-size padding-size] [
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]}
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.
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
|
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
|
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.
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.
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.
*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#
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#
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 ip-addr configured can be either on the network or the access side and is normally at least one hop away from this node.
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
|
The existing static-route command is still supported with all other options, including the
indirect option which can be used to resolve the indirect next-hops in RTM.
If tunnel-next-hop context is configured and
resolution is set to
disabled, the binding to tunnel is removed and resolution resumes in RTM to IP next-hops.
If resolution is set to
any, any supported tunnel type in static route context will be selected following TTM preference.
The ldp value instructs the code to search for an LDP LSP with a FEC prefix corresponding to the address of the indirect next-hop.
The rsvp value instructs the code to search for the best metric RSVP LSP to the address of the indirect next-hop. This address can correspond to the system interface or to another loopback used on the remote node. The LSP metric is provided by MPLS in the tunnel table. In the case of multiple RSVP LSPs with the same lowest metric, the code selects the LSP with the lowest tunnel-id.
The user must set resolution to
filter to activate the list of tunnel-types configured under
resolution-filter.
If disallow-igp is enabled, the static-route will not be activated using IGP next-hops in RTM if no tunnel next-hops are found in TTM.
config>router>static-route-entry>tunnel-next-hop
config>router>static-route-entry>tunnel-next-hop
This command configures the resolution mode in the resolution of a static route using tunnels to an indirect next-hop.
config>router>static-route-entry>tunnel-next-hop
This command configures the susbset of tunnel types which can be used in the resolution of a static route using tunnels to an indirect next-hop.
The following tunnel types are supported in a static route context RSVP and LDP. In the case of RSVP-TE tunnel type, the user can further restrict the selection by providing a list of LSP names.
rsvp-te [lsp
lsp-name]...[lsp
lsp-name]
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.
next-attempt {same-preference-level
| next-preference-level
}
|
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.
|
group tunnel-group-name [create
]
The no form of the command returns the value to
never allow AVP hiding.
The no form of the command reverts to the default
never value.
The no form of the command removes the value from the configuration.
The no form of the command removes the interval from the configuration.
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.
The no form of the command removes thename from the configuration.
The no form of the command removes the value from the configuration.
The no form of the command removes the value from the configuration.
keepalive seconds [hold-up-multiplier
multiplier]
[no
] proxy-authentication
The no form of the command removes the parameter of the configuration and indicates that the value on group level will be taken.
The no form of the command removes the parameter from the configuration and indicates that the value on group level will be taken.
The no form of the command removes the IP address from the tunnel configuration.
The no form of the command removes the preference value from the tunnel configuration.
|
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:
|
(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.
[no
] interface
ip-int-name [unnumbered-mpls-tp]
[no
] interface
ip-int-name gmpls-loopback
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.
Although not a keyword, the ip-int-name “system” is associated with the network entity (such as a specific 7750 SR), not a specific interface. The system interface is also referred to as the loopback address.
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.
|
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.
address {ip-address/mask|ip-address netmask} [broadcast all-ones | host-ones] [track-srrp srrp-instance]
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 no form of the command removes the IP address assignment from the IP interface. Interface specificconfigurations for MPLS/RSVP are also removed. This will operationally stop any MPLS LSPs that explicitly reference that IP address. When a new IP address is defined, interface specific configurations for MPLS/RSVP will need to be re-added. If the
no form of the command is executed then
ptp-hw-assist is disabled. If a new address is entered while another address is still active, the new address will be rejected.
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.
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.
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.
[no
] allow-directed-broadcasts
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.
The no form of the command disables directed broadcasts forwarding out of the IP interface.
arp-limit limit [log-only] [threshold
percent]
The no form of the command removes the
arp-limit.
The no form of the command reverts to the default value.
bfd transmit-interval [receive
receive-interval] [multiplier
multiplier] [echo-receive
echo-interval] [type cpm-np
]
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.
|
To remove the type cpm-np option, re-issue the
bfd command without specifying the
type parameter.
cflowd is used for network planning and traffic engineering, capacity planning, security, application and user profiling, performance monitoring, usage-based billing, and SLA measurement.
At a minimum, the sampling command must be configured within this context in order to enable cflowd sampling, otherwise traffic sampling will not occur.
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.
The no form of the command disables the associated type of traffic sampling on the associated interface.
Specifies that the sampling command will control the sampling of unicast traffic on the associated interface/SAP.
Specifies that the sampling command will control the sampling of multicast traffic on the associated interface/SAP.
The no form of the command removes the command from the active configuration and removes the delay in activating the associated IP interface. If the configuration is removed during a delay period, the currently running delay will continue until it expires.
[no
] enable-ingress-stats
[no
] enable-mac-accounting
[no
] if-admin-group
group-name [group-name...(upto 5 max)]
[no
] if-srlg-group
group-name [group-name...(upto 5 max)]
The no form of the command returns the associated IP interfaces MTU to its default value, which is calculated, based on the port MTU setting. (For Ethernet ports this will typically be 1554.)
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.
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.
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.
The no form of this command disables IGP/LDP synchronization and deletes the configuration
The no form of this command includes both source and destination parameters.
The no form disables the SPI function.
The no form of the command returns the MAC address of the IP interface to the default value.
[no
] multihoming primary|secondary
[hold-time
holdover-time]
The no form of the command disables SNTP broadcast received on the IP interface.
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.
|
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..800
|
[no
] proxy-arp-policy
policy-name [policy-name...(up to 5 max)]
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 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.
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 no form of the command reverts to the default.
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]
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.
secondary {[ip-address/
mask | ip-address netmask]} [broadcast
{all-ones
| host-ones
}] [igp-inhibit
]
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.
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.
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.
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 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.
The no form of the command removes the strip-label command.
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.
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.
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.
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 no form of the command reverts to the default.
The no form of the command reverts to the default and disabled SeND.
[no
] allow-unsecured-msgs
The no form of the command disables accepting unsecured messages.
The no form of the command removes the stale-time value.
The no form of the command removes the static value and allows the TCP MSS value to be calculated based on the IP MTU value by subtracting the base IP and TCP header lengths from the IP MTU value (tcp_mss = ip_mtu – 40).
The no form of the command disables unicast RPF (uRPF) Check on this interface.
vas-if-type {to-from-access
| to-from-network
| to-from-both
}
The no form of the command removes VAS interface type configuration.
mode {strict
| loose
| strict-no-ecmp
}
The no form of the command reverts to the default (strict) mode.
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.
[no
] mh-primary-interface
address {ip-address/mask | ip-address netmask}
Each single operation of the admin-group command allows a maximum of five (5) groups to be specified at a time. However, a maximum of 32 groups can be added to a given interface through multiple operations. Once an admin group is bound to one or more interface, its value cannot be changed until all bindings are removed.
The no form of this command deletes one or more of the admin-group memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.
srlg-group group-name value
group-value [penalty-weight penalty-weight]
When SRLGs applied to IES, VPRN, or network IP interfaces, they are evaluated in the route next-hop selection by adding the srlg-enable option in a route next-hop policy template applied to an interface or a set of prefixes. For instance, the user can enable the SRLG constraint to select a LFA next-hop for a prefix which avoids all interfaces that share fate with the primary next-hop.
It should be noted that only the SRLGs bound to an MPLS interface are advertised area-wide in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.
A user may specify a penalty weight (penalty-weight) associated with an SRLG. This controls the likelihood of paths with links sharing SRLG values with a primary path being used by a bypass or detour LSP. The higher the penalty weight, the less desirable it is to use the link with a given SRLG.
srlg-group group-name [group-name...(up to 5 max)
]
An interface can belong to up to 64 SRLG groups. However, each single operation of the srlg-group command allows a maximum of five (5) groups to be specified at a time. Once an SRLG group is bound to one or more interface, its value cannot be changed until all bindings are removed.
It should be noted that only the SRLGs bound to an MPLS interface are advertised area-wide in TE link TLVs and sub-TLVs when the traffic-engineering option is enabled in IS-IS or OSPF. IES and VPRN interfaces do not have their attributes advertised in TE TLVs.
The no form of this command deletes one or more of the SRLG memberships of an interface. The user can also delete all memberships of an interface by not specifying a group name.
[no
] template
template-name
The commands within the route next-hop policy template use the begin-commit-abort model. The following are the steps to create and modify the template:
Each group is entered individually. The include-group statement instructs the LFA SPF selection algorithm to pick up a subset of LFA next-hops among the links which belong to one or more of the specified admin groups. A link which does not belong to at least one of the admin-groups is excluded. However, a link can still be selected if it belongs to one of the groups in a include-group statement but also belongs to other groups which are not part of any include-group statement in the route next-hop policy.
The pref option is used to provide a relative preference for the admin group to select. A lower preference value means that LFA SPF will first attempt to select a LFA backup next-hop which is a member of the corresponding admin group. If none is found, then the admin group with the next higher preference value is evaluated. If no preference is configured for a given admin group name, then it is supposed to be the least preferred, i.e., numerically the highest preference value.
When evaluating multiple include-group statements within the same preference, any link which belongs to one or more of the included admin groups can be selected as an LFA next-hop. There is no relative preference based on how many of those included admin groups the link is a member of.
The exclude-group statement simply prunes all links belonging to the specified admin group before making the LFA backup next-hop selection for a prefix.
The no form deletes the admin group constraint from the route next-hop policy template.
Each group is entered individually. The include-group statement instructs the LFA SPF selection algorithm to pick up a subset of LFA next-hops among the links that belong to one or more of the specified admin groups. A link that does not belong to at least one of the admin-groups is excluded. However, a link can still be selected if it belongs to one of the groups in an include-group statement but also belongs to other groups that are not part of any include-group statement in the route next-hop policy.
The pref option is used to provide a relative preference for the admin group to select. A lower preference value means that LFA SPF will first attempt to select an LFA backup next-hop that is a member of the corresponding admin group. If none is found, then the admin group with the next highest preference value is evaluated. If no preference is configured for a given admin group name, then it is supposed to be the least preferred (i.e., numerically the highest preference value).
When evaluating multiple include-group statements within the same preference, any link that belongs to one or more of the included admin groups can be selected as an LFA next-hop. There is no relative preference based on how many of those included admin groups the link is a member of.
The exclude-group statement simply prunes all links belonging to the specified admin group before making the LFA backup next-hop selection for a prefix.
The no form deletes the admin group constraint from the route next-hop policy template.
The no form deletes the SRLG constraint from the route next-hop policy template.
The no form deletes the protection type constraint from the route next-hop policy template.
The no form deletes the next-hop type constraint from the route next-hop policy template.
[no
] mh-secondary-interface
Router Interface Filter Commands
The no form of the command removes IPv4 flowspec filtering from the network IP interface.
The no form of the command removes IPv6 flowspec filtering from the network IP interface.
no filter [ip
ip-filter-ip] [ipv6
ipv6-filter-id]
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.
The no form of the command removes the filter policy association with the IP 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.
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.
The no form of the command disables the generation of ICMP redirects on the router interface.
The no form of the command disables the generation of TTL expired messages.
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.
The no form of the command disables the generation of ICMP destination unreachables on the router interface.
The no form of the command disables IPv6 on the interface.
address {ipv6-address/prefix-length} [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.
The no form of the command turns off
dad-disable on the interface.
The no form of the command disables ICMPv6 redirects.
The no form of the command disables the generation of ICMPv6 host and network unreachable messages by this interface.
The no form of the command removes the configured link local address, and the router automatically generates a default link local address.
The no form of the command disables local proxy neighbor discovery.
The ipv6-address must be on the subnet that was configured from the IPv6
address command or a link-local address.
The no form of the command removes the neighbor-limit.
The no form of this command returns the system to the default.
action {replace
| drop
| keep
}
This command configures the processing required when the SR-Series router receives a DHCP request that already has a Relay Agent Information Option (Option 82) field in the packet.
The no form of this command returns the system to the default value.
Per RFC 3046, DHCP Relay Agent Information Option , section 2.1.1,
Reforwarded DHCP requests, the default is to keep the existing information intact. The exception to this is if the giaddr of the received packet is the same as the ingress address on the router. In that case the packet is dropped and an error is logged.
circuit-id [ascii-tuple
| ifindex
| sap-id
| vlan-ascii-tuple
]
When enabled, the router sends the interface index (If Index) in the circuit-id suboption of the DHCP packet. The If Index of a router interface can be displayed using the command
show>router>interface>detail. This option specifies data that must be unique to the router that is relaying the circuit.
If disabled, the circuit-id suboption of the DHCP packet will be left empty.
The no form of this command returns the system to the default.
When enabled, the router sends the MAC address of the remote end (typically the DHCP client) in the remote-id suboption of the DHCP packet. This command identifies the host at the other end of the circuit. If disabled, the
remote-id suboption of the DHCP packet will be left empty.
The no form of this command returns the system to the default.
[no
] vendor-specific-option
The no form of the command disables the sending of the MAC address in the Alcatel-Lucent vendor specific suboption of the DHCP relay packet.
The no form of the command disables the feature.
The no form of the command disables the sending.
The no form of the command disables the sending of the service ID in the Alcatel-Lucent vendor specific suboption of the DHCP relay packet.
The no form of the command returns the default value.
The no form of the command disables the relaying of plain BOOTP packets.
server server1 [server2...(up to 8 max)]
This command specifies a list of servers where requests will be forwarded. The list of servers can entered as either IP addresses or fully qualified domain names. There must be at least one server specified for DHCP relay to work. If there are multiple servers then the request is forwarded to all of the servers in the list. There can be a maximum of 8 DHCP servers configured.
The flood command is applicable only in the VPLS case. There is a scenario with VPLS where the VPLS node only wants to add Option 82 information to the DHCP request to provider per-subscriber information, but it does not do full DHCP relay. In this case, the server is set to "flood". This means the DHCP request is still a broadcast and is sent through the VPLS domain. A node running at L3 further upstream then can perform the full L3 DHCP relay function.
According to RFC 3046, DHCP Relay Agent Information Option, a DHCP request where the giaddr is 0.0.0.0 and which contains a Option 82 field in the packet, should be discarded, unless it arrives on a "trusted" circuit.
If trusted mode is enabled on an IP interface, the relay agent (the SR-Series) will modify the request's giaddr to be equal to the ingress interface and forward the request.
The no form of this command returns the system to the default.
[no
] router-advertisement
The no form of the command disables all IPv6 interface. However, the
no interface interface-name command disables a specific interface.
The no form of the command disables configuration of DNS information for Stateless Address Auto-Configuration (SLAAC) hosts.
The no form of the command disables the RDNSS option in router advertisements.
[no
] interface
ip-int-name
[no
] managed-configuration
[no
] max-advertisement-interval
seconds
[no
] min-advertisement-interval
seconds
Specify the MTU for the nodes to use to send packets on the link.
[no
] other-stateful-configuration
[no
] prefix
[ipv6-prefix/prefix-length]
[no
] preferred-lifetime
{seconds | infinite
}
The no form of the command disables sending router advertisement messages.
