slxs-18 1 02-Commandref
slxs-18 1 02-Commandref
slxs-18 1 02-Commandref
Extreme SLX-OS
Command Reference, 18s.1.02
9036144-00
May 2019
Copyright © 2019 Extreme Networks, Inc. All Rights Reserved.
Legal Notice
Extreme Networks, Inc. reserves the right to make changes in specifications and other information contained in this document and its
website without prior notice. The reader should in all cases consult representatives of Extreme Networks to determine whether any such
changes have been made.
The hardware, firmware, software or any specifications described or referred to in this document are subject to change without notice.
Trademarks
Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of Extreme Networks, Inc. in the United
States and/or other countries.
All other names (including any product names) mentioned in this document are the property of their respective owners and may be
trademarks or registered trademarks of their respective companies/owners.
Commands A - B..............................................................................................................................................................................................................39
aaa accounting......................................................................................................................................................................................................................................... 39
aaa authentication .................................................................................................................................................................................................................................. 41
action............................................................................................................................................................................................................................................................ 43
action python-script............................................................................................................................................................................................................................... 45
action-timeout.......................................................................................................................................................................................................................................... 47
activate (telemetry collector)............................................................................................................................................................................................................... 48
activate (telemetry server).................................................................................................................................................................................................................... 49
activate (VXLAN gateway)................................................................................................................................................................................................................... 50
add (telemetry)..........................................................................................................................................................................................................................................51
add destination.........................................................................................................................................................................................................................................52
address-family l2vpn evpn (BGP)....................................................................................................................................................................................................54
address-family unicast (BGP)............................................................................................................................................................................................................ 55
Commands G - J............................................................................................................................................................................................................421
graceful-restart (BGP EVPN)..........................................................................................................................................................................................................421
graceful-shutdown ............................................................................................................................................................................................................................. 423
gtp-de-encapsulation.........................................................................................................................................................................................................................425
hardware...................................................................................................................................................................................................................................................426
Commands K - M...........................................................................................................................................................................................................601
key.............................................................................................................................................................................................................................................................. 601
key-add-remove-interval..................................................................................................................................................................................................................603
key-rollover-interval............................................................................................................................................................................................................................ 604
keypair.......................................................................................................................................................................................................................................................605
lacp default-up .....................................................................................................................................................................................................................................606
lacp port-priority ..................................................................................................................................................................................................................................607
lacp system-priority ........................................................................................................................................................................................................................... 608
lacp timeout ...........................................................................................................................................................................................................................................609
ldap-server host .................................................................................................................................................................................................................................. 611
ldap-server maprole .......................................................................................................................................................................................................................... 613
license eula............................................................................................................................................................................................................................................. 614
line vty exec-timeout ......................................................................................................................................................................................................................... 616
link-fault-signaling rx .........................................................................................................................................................................................................................618
lldp profile ...............................................................................................................................................................................................................................................620
load-balance (default mode)............................................................................................................................................................................................................621
Conventions
This section discusses the conventions used in this guide.
NOTE
A Note provides a tip, guidance, or advice, emphasizes important information, or provides a reference to related information.
ATTENTION
An Attention statement indicates a stronger note, for example, to alert you when traffic might be interrupted or the device might
reboot.
CAUTION
A Caution statement alerts you to situations that can be potentially hazardous to you or cause damage to hardware,
firmware, software, or data.
DANGER
A Danger statement indicates conditions or situations that can be potentially lethal or extremely hazardous to you. Safety
labels are also attached directly to products to warn of these conditions or situations.
Format Description
bold text Identifies command names.
Identifies variables.
Format Description
Courier font Identifies CLI output.
Convention Description
bold text Identifies command names, keywords, and command options.
italic text Identifies a variable.
[] Syntax components displayed within square brackets are optional.
Training
Extreme Networks offers product training courses, both online and in person, as well as specialized certifications. For more information,
visit www.extremenetworks.com/education/.
Getting Help
If you require assistance, contact Extreme Networks using one of the following methods:
Extreme Portal Search the GTAC (Global Technical Assistance Center) knowledge base, manage support cases and service
contracts, download software, and obtain product licensing, training, and certifications.
The Hub A forum for Extreme Networks customers to connect with one another, answer questions, and share ideas and
feedback. This community is monitored by Extreme Networks employees, but is not intended to replace specific
guidance from GTAC.
Call GTAC For immediate support: 1-800-998-2408 (toll-free in U.S. and Canada) or +1 408-579-2826. For the support
phone number in your country, visit: www.extremenetworks.com/support/contact
Before contacting Extreme Networks for technical support, have the following information ready:
• Your Extreme Networks service contract number and/or serial numbers for all involved Extreme Networks products
• A description of the failure
• A description of any action(s) already taken to resolve the problem
• A description of your network environment (such as layout, cable type, other relevant environmental information)
• Network load at the time of trouble (if known)
• The device history (for example, if you have returned the device before, or if this is a recurring problem)
• Any related RMA (Return Material Authorization) numbers
1. Go to www.extremenetworks.com/support/service-notification-form.
2. Complete the form with your information (all fields are required).
3. Select the products for which you would like to receive notifications.
NOTE
You can modify your product selections or unsubscribe at any time.
4. Click Submit.
Providing Feedback to Us
Quality is our first concern at Extreme Networks, and we have made every effort to ensure the accuracy and completeness of this
document. We are always striving to improve our documentation and help you work better, so we want to hear from you! We welcome all
feedback but especially want to know about:
• Content errors or confusing or conflicting information.
• Ideas for improvements to our documentation so you can find the information you need faster.
• Broken links or usability issues.
If you would like to provide feedback to the Extreme Networks Information Development team, you can do so in two ways:
• Use our short online feedback form at https://www.extremenetworks.com/documentation-feedback/.
• Email us at documentation@extremenetworks.com.
Please provide the publication title, part number, and as much detail as possible, including the topic heading and page number if
applicable, as well as your suggestions for improvement.
Although many different software and hardware configurations are tested and supported by Extreme Networks, Inc. for this SLX-OS
release, documenting all possible configurations and scenarios is beyond the scope of this document.
NOTE
Some of the commands in this document use a slot/port designation. Because the SLX 9140 and the SLX 9240 do not
contain line cards, the slot designation must always be "0" (for example, 0/1 for port 1).
New commands
The following commands are new:
• add destination
• pbf destination
• pbf destination-group
• remove destination
• set interface (PBF destination)
• show pbf destination
• show pbf destination-group
• statistics-enable
Modified commands
The following commands are modified:
• interface (telemetry)
• ip port (telemetry)
• profile (telemetry)
Deprecated commands
The following commands are deprecated:
• interface-range (telemetry)
User accounts
A user account specifies that user's level of access to the device CLI.
The SLX-OS software uses role-based access control (RBAC) as the authorization mechanism. A role is a container for rules, which
specify which commands can be executed and with which permissions. When you create a user account you need to specify a role for
that account. In general, user (as opposed to user-level) refers to any account—to which any role can be assigned—user, admin, or a non-
default role.
The software ships with two default accounts—admin and user—and two corresponding default roles:
• admin—Accounts with admin permissions can execute all commands supported on the device. (For the initial admin login, refer
to the relevant Hardware Installation Guide.)
• user—Accounts with user-level permissions can execute all show commands supported on the device. User-level accounts can
also execute the following operational commands: cfm, execute-script, exit, mtrace, no, ping, rasman, ssh, sysmon, telnet,
timestamp, trace-l2, and traceroute.
For more information on user accounts and roles, refer to the Extreme SLX-OS Security Configuration Guide.
NOTE
Multiple users can open sessions on the device and issue commands. The device supports a maximum of 32 CLI sessions.
Command modes
The SLX-OS CLI uses an industry-standard hierarchical shell familiar to Ethernet/IP networking administrators. You can use one of three
major command modes to enter commands and access sub-configuration modes on the device.
For example, if you are configuring an Ethernet interface and you want to execute a privileged EXEC mode command, such as the dir
command, you would first have to exit the Interface configuration mode. By using the do command with the dir command, you can
ignore the need to change configuration modes, as shown in the following example.
device(config-if-eth-0/2)# do dir
total 32
drwxrwxr-x 3 21487 1011 4096 Mar 26 17:58 .
drwxrwxr-x 3 21487 1011 4096 Mar 13 06:45 ..
-rw-r--r-- 1 root sys 495 Mar 16 15:41 defaultconfig.cluster
-rw-r--r-- 1 root sys 210 Mar 16 15:41 defaultconfig.standalone
drwxrwxr-x 5 root sys 4096 Mar 26 17:57 flex-cli
-rw-r--r-- 1 root root 11093 Mar 26 18:04 startup-config
Enter a question mark (?) in any command mode to display the list of commands available in that mode.
To display a list of commands that start with the same characters, type the characters followed by a question mark (? ).
device# e?
Possible completions:
end Terminate configuration session
event-handler Event Handler Commands
evpn EVPN configuration.
exit Exit from current mode
To display the keywords and arguments associated with a command, enter the keyword followed by a space a then a question mark (?).
device# terminal ?
Possible completions:
length Sets Terminal Length for this session
monitor Enables terminal monitoring for this session
no Sets Terminal Length for this session to default :24.
timeout Sets the interval that the EXEC command interpreter wait for user input.
If the question mark (?) is typed within an incomplete keyword, but the keyword matches several keywords, the CLI displays help for all
the matching keywords.
device# show l
Possible completions:
lacp LACP commands
license Display license keys installed on the switch.
linecard Show linecard
link-fault-signaling Show Link Fault Signalling configs
lldp Link Layer Discovery Protocol(LLDP).
logging Show logging
The CLI accepts abbreviations for commands. This example is the abbreviation for the show qos interface all command.
device# sh q i a
If the device does not recognize a command after you press Enter, an error message displays.
device# hookup
^
syntax error: unknown argument.
device# show
^
syntax error: unknown argument.
device# te
device# terminal
If there is more than one command or keyword associated with the characters typed, the CLI displays all choices. For example, at the CLI
command prompt, type show l and press Tab.
device# show l
device# show l
Possible completions:
lacp LACP commands
license Display license keys installed on the switch.
linecard Show linecard
link-fault-signaling Show Link Fault Signalling configs
lldp Link Layer Discovery Protocol(LLDP).
logging Show logging
NOTE
In privileged EXEC mode, use the show history command to list the commands most recently entered. The device retains the
history of the last 1000 commands entered for the current session.
Extreme Networks recommends that you work closely with Extreme technical support in executing such commands and interpreting their
results.
NOTE
Not all diagnostic commands are documented.
device(config)# alias-config
3. Enter the alias command, specifying the alias and its corresponding command.
device(config-alias-config)# exit
device(config)# exit
device# ck
device# show clock
2016-06-14 13:03:55 Etc/GMT
device(config)# alias-config
4. Enter the alias command, specifying the alias and its corresponding command.
NOTE
The following verification example assumes that the user jdoe defined the user-level alias "int2". If an admin defined
the alias for this user, the example would show the admin logging out of the CLI and jdoe logging into the CLI.
device(config-alias-config)# exit
device(config-user-jdoe)# exit
device(config-alias-config)# exit
device(config)# int2
<Displayed automatically:>
device(config)#interface ethernet 0/2
device(conf-if-eth-0/2)#
Syntax
aaa accounting {commands default start-stop [none | tacacs+] | exec default start-stop [none | tacacs+]}
no aaa accounting {commands default start-stop [none | tacacs+] | exec default start-stop [none | tacacs+]}
Parameters
commands
Toggles the logging of commands.
exec
Toggles the logging of login information.
default
Sends the logged information to the default server.
start-stop
Sends a "start" accounting notice at the beginning of a process and a "stop" accounting notice at the end of a process.
The "start" accounting record is sent in the background. The requested user process begins regardless of whether the
"start" accounting notice was received by the accounting server.
tacacs+
Sends the logged information to the TACACS+ server.
none
Disables accounting services.
Modes
Global configuration mode
Usage Guidelines
Use the no aaa accounting command to disable command accounting.
Examples
This example configures full accounting, with the CLI information being forwarded to the TACACS+ server.
This example disables login accounting, but leaves command accounting active.
History
Release version Command history
aaa authentication
Configures the authentication, authorization, and accounting login sequence.
Syntax
aaa authentication login { default | ldap | local }
Command Default
The default server is Local.
Parameters
login
Specifies the type of server that will be used for authentication, authorization, and accounting (AAA) on the device. The
local server is the default. Specify one of the following options:
default
Specifies the default mode (local server). Authenticates the user against the local database only. If the
password does not match or the user is not defined, the login fails.
ldap
Specifies the Lightweight Directory Access Protocol (LDAP) servers.
local
Specifies to use the local device database if prior authentication methods are inactive.
radius
Specifies the RADIUS servers.
tacacs+
Specifies the TACACS+ servers.
local
Specifies to use the local device database if prior authentication methods are inactive.
local-auth-failback
Specifies to use the local device database if prior authentication methods are not active or if authentication
fails.
Modes
Global configuration mode
Usage Guidelines
This command selects the order of authentication sources to be used for user authentication during the login process. Two
sources are supported: primary and secondary. The secondary source of authentication is optional and will be used if the
primary source fails or is not available.
In a configuration with primary and secondary sources of authentication, the primary mode cannot be modified alone. For
example, you cannot change from “radius local" or "radius local-auth-fallback” to “tacacs+ local" or "tacacs+ local-auth-fallback”
respectively. First remove the existing configuration and then configure it to the required configuration.
Examples
To change the AAA server to TACACS+ using the local device database as a secondary source of authentication:
To change the AAA server from TACACS+ and local to TACACS+ only (no secondary source):
History
Release version Command history
action
Specifies which classification type in the policer remarking profile is being modified and whether the classification type applies
to conforming traffic or exceeding traffic.
Syntax
action classification-type conform | exceed
Command Default
The police-remark-profile command has been executed.
Parameters
classification-type
Specifies the classification type to be modified in the default policier remarking profile. Choices include:
• color
• color-and-cos
• color-and-dscp
• color-and-traffic-class
conform
Specifies that the settings for the classification type apply to conforming traffic.
exceed
Specifies that the settings for the classification type apply to exceeding traffic.
Modes
Policer remarking profile configuration mode
Usage Guidelines
Use this command after executing the police-remark-profile command. If you specify "color" as the choice for classification-
type, then you issue the set command to specify parameters for cos, traffic-class, and dscp. If you specify any of the other
choices for classification-type, then you issue the map command to include the parameters in the specified map in the default
policer remark profile.
Examples
The following is an example of executing the action command to specify the color classification type for conforming traffic.
Then, the example shows using the set command to specify the settings for the remark values in the default policer remark
profile.
The following is an example of executing the action command to specify the color-and-cos classification type for exceeding
traffic. Then, the example shows using the map command to specify the maps to be included in the default policer remark
profile for cos remarking for exceeding traffic. ("cm1," "ct1," and "cd1" are map names).
The following is an example of executing the action command to specify the color-and-dscp classification type for conforming
traffic. Then, the example shows using the map command to specify the maps to be included in the default policer remark
profile for dscp remarking for conforming traffic. ("dm1," "dc1," and "dt1" are map names).
The following is an example of executing the action command to specify the color-and-traffic-class classification type for
exceeding traffic. Then, the example shows using the map command to specify the maps to be included in the default policer
remark profile for traffic-class remarking for exceeding traffic. ("tm2," "tc2," and "td2" are map names).
History
Release version Command history
action python-script
Specifies a Python file that runs when a trigger condition occurs.
Syntax
action python-script file-name
Parameters
file-name
Specifies a Python script file name. Valid values range from 4 through 32 characters (including the .py extension). The
first character must be alphabetic.
Modes
Event-handler configuration mode
Usage Guidelines
You can assign only one action to a given event-handler profile.
You can also specify the Python file as part of the event-handler command.
To change the file assigned to a profile, you do not need to enter the no form of this command. You only need to enter action
python-script file-name, specifying the new file name.
Running this command copies the Python script file from the flash:// directory to the database. After specifying a file for all
relevant event-handler profiles, you can delete it from the flash:// directory.
If the event-handler for which you are modifying this command is active on the device, the changes take effect with no need to
de-activate and re-activate the event-handler.
If an event-handler profile is not activated, the no form of this command deletes its action.
Examples
The following example specifies Python files for two event-handler profiles.
History
Release version Command history
action-timeout
Specifies the maximum number of minutes to wait for an action-script to complete execution.
Syntax
action-timeout minutes
no action-timeout
Command Default
No action timeout is defined.
Parameters
minutes
Specifies the number of minutes to wait for an action-script to complete execution. If you specify "0", no timeout is set.
Valid timeout values are any positive integer.
Modes
Event-handler activation mode
Usage Guidelines
If the action-timeout expires, then script execution ends.
To restore the default setting of no timeout, enter the no form of this command.
Examples
The following example specifies an action timeout of 30 minutes.
History
Release version Command history
Syntax
activate
no activate
Command Default
The collector is deactivated.
Modes
Telemetry streaming mode
Usage Guidelines
Activates the collector object, which streams telemetry information to the external telemetry collector.
Use the no activate command to disable streaming to the external telemetry collector.
Examples
Typical command execution.
History
Release version Command history
Syntax
activate
no activate
Command Default
The internal gRPC telemetry-server is deactivated.
Modes
Telemetry-server configuration mode
Usage Guidelines
This command activates the internal gRPC telemetry-server.
To disable the internal gRPC telemetry-server, use the no form of this command.
Examples
Typical command execution.
History
Release version Command history
Syntax
activate
no activate
Command Default
By default, a gateway is not activated during initial configuration.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
It is recommended that you configure all gateway parameters before activating the gateway. This operation enables all tunnels
that are associated with this gateway.
The following conditions that must be in place before you can execute the activate command:
• Loopback interfaces must be configured on both the nodes of the logical VTEP (LVTEP),
• All loopback interfaces must be configured with the same IPv4 address and the same VRF instance.
• The IP address of the VXLAN gateway must be configured. Refer to the ip interface command.
Use the no activate command in VXLAN overlay gateway configuration mode to deactivate the gateway. All associated tunnels
are also deactivated.
Examples
The following example activates a VXLAN gateway named "gateway1" when the gateway is previously configured by means of
the overlay-gateway command.
History
Release version Command history
add (telemetry)
Restores a previously removed field to a telemetry profile.
Syntax
add telemetry-field
no add telemetry-field
Command Default
All of the default fields are included in the telemetry profile.
Parameters
telemetry-field
Specifies the profile field.
Modes
Telemetry-profile configuration mode
Usage Guidelines
To remove a field from a profile, use the no form of this command.
Examples
The following example removes the buffers field from the default_system_utilization_statistics profile.
History
Release version Command history
add destination
Adds policy-based forwarding (PBF)-destinations to a destination group.
Syntax
add destination destination-id
no add destination
Command Default
PBF destination groups contains no PBF destinations.
Parameters
destination-id
Specifies one or more PBF destination IDs. You can specify one ID, a range (example: 3-5), a comma-separated list
(example: 1,3,5,6), or combine IDs, ranges, and lists (example: 1-5,6,8).
Modes
PBF destination-group configuration mode
Usage Guidelines
The use case for this command is under Network Packet Broker (NPB) system mode.
To remove all PBF destination IDs included in a destination group, use the no add destination form of this command.
To remove some of the PBF destination IDs included in a destination group, use the remove destination destination-id
command.
Examples
The following example creates a PBF destination-group and adds three PBF destinations to it.
The following example accesses the above PBF destination-group and removes all PBF destinations from it.
History
Release version Command history
Syntax
address-family l2vpn evpn
Command Default
This feature is disabled.
Modes
BGP configuration mode
Usage Guidelines
Use this command in BGP configuration mode to enter BGP address-family L2VPN EVPN configuration mode. The L2VPN
EVPN configuration mode supports the EVPN Subsequent Address Family Identifier (SAFI), an address qualifier that provides
additional information about the Network Layer Reachability Information (NLRI) type for a given attribute. The no form of this
command removes the L2VPN EVPN address family configuration from the device and removes all configurations under the
L2VPN address family.
Examples
This example enables BGP address family L2VPN EVPN configuration mode.
History
Release version Command history
Syntax
address-family { ipv4 | ipv6 } unicast [ vrf vrf-name ]
Parameters
ipv4
Specifies an IPv4 address family.
ipv6
Specifies an IPv6 address family.
vrf vrf-name
Specifies a VRF instance.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes IPv4 or IPv6 address family configurations from the device.
Examples
The following example enables BGP IPv4 address-family configuration mode.
The following example enables BGP IPv4 address-family configuration mode for VRF "green".
The following example enables BGP IPv6 address-family configuration mode for VRF "red".
History
Release version Command history
advertise dot1-tlv
Advertises globally to any attached device IEEE 802.1 organizationally specific Type, Length, Values (TLV) values, or for a
specific LLDP profile.
Syntax
advertise dot1-tlv
Command Default
Advertisement is disabled.
Modes
Protocol LLDP configuration mode
Examples
The following example advertises TLV configuration for IEEE 802.1.
The following example advertises TLV configuration for IEEE 802.1 for a specific LLDP profile.
History
Release version Command history
advertise dot3-tlv
Advertises to any attached device IEEE 802.3 organizationally specific Type, Length, Values (TLV) values, or for a specific
LLDP profile.
Syntax
advertise dot3-tlv
Command Default
Advertisement is disabled.
Modes
Protocol LLDP configuration mode
Examples
The following example advertises TLV configuration for IEEE 802.3.
The following example advertises TLV configuration for IEEE 802.3 for a specific LLDP profile.
History
Release version Command history
advertise-backup
Enables a backup VRRP router to send advertisement frames to the master VRRP router.
Syntax
advertise-backup
no advertise-backup
Command Default
Advertisement is disabled.
Modes
Virtual-router-group configuration mode
Usage Guidelines
If a backup router is enabled to send advertisement frames, the frames are sent every 60 seconds.
This command can be used for VRRP-E, but not for VRRP.
Enter no advertise backup to return to the default setting (no periodic transmission).
Examples
To enable the backup VRRP routers to send advertisement frames to the master VRRP router:
History
Release version Command history
advertise optional-tlv
Advertises the optional Type, Length, and Values (TLV) values, or for a specific LLDP profile.
Syntax
advertise optional-tlv { management-address | port-description | system-capabilities | system-description | system-name }
no advertise optional-tlv
Command Default
Advertisement is disabled.
Parameters
management-address
Advertises the management address of the system.
port-description
Advertises the user-configured port.
system-capabilities
Advertises the capabilities of the system.
system-description
Advertises the system firmware version and the current image running on the system.
system-name
Advertises the name of the system.
Modes
Protocol LLDP configuration mode
Usage Guidelines
Enter no advertise optional-tlv to return to the default setting.
Examples
The following example advertises the management address of the system and the user-configured port.
The following example advertises the management address of the system for a specific LLDP profile.
History
Release version Command history
advertisement-interval (VRRP)
Configures the interval at which the master VRRP router advertises its existence to the backup routers.
Syntax
advertisement-interval range
Command Default
1 second for version 2, 1000 milliseconds for version 3.
Parameters
range
Interval at which the master VRRP router advertises its existence to the backup routers. Valid values range from 1
through 255 seconds for VRRPv2 and from 100 through 40900 milliseconds for VRRPv3.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This interval is the length of time, in seconds, between each advertisement sent from the master to its backup VRRP routers.
The advertisement notifies the backup routers that the master is still active. If the backup routers do not receive an
advertisement from the master in a designated amount of time, the backup with the highest priority can assume the role of
master.
This command can be used for either VRRP or VRRP-E and for VRRPv3 and VRRP-Ev3.
Examples
To set the advertisement interval to 30 seconds for VRRP-E group 10:
To set the advertisement interval to 3000 milliseconds for VRRP-Ev3 group 19:
History
Release version Command history
advertisement-interval-scale
Configures subsecond intervals at which the master VRRP-Ev3 device advertises its existence to the backup routers.
Syntax
advertisement-interval-scale scale
Command Default
The default advertisement interval scale is 1.
Parameters
scale
Number representing the scale of the division of a configured interval at which the master VRRP-Ev3 device
advertises its existence to the backup devices. Valid values are 1, 2, 5 and 10.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command scales the advertisement interval of the master VRRP-Ev3 device as configured by the advertisement-interval
command. A value of 1, 2, 5, or 10 can be set and the existing advertisement interval value is divided by the scaling value, for
example, if the advertisement interval is set to 1 second and the scaling value is set to 10, the new advertisement interval is
100 milliseconds. When all the advertisement intervals in a VRRP-Ev3 session are scaled, subsecond VRRP-Ev3 convergence
is possible if a master fails. The advertisement notifies the backup devices that the master is still active. If the backup devices do
not receive an advertisement from the master in a designated amount of time, the backup device with the highest priority can
assume the role of master. Using subsecond advertising intervals, subsecond device redundancy can be achieved.
Examples
To set the scaling of the advertisement interval to 500 milliseconds for VRRP-Ev3 group 19:
History
Release version Command history
aggregate-address (BGP)
Configures the device to aggregate routes from a range of networks into a single network prefix.
Syntax
aggregate-address { ip-addr ip-mask | ipv6-addr ipv6-mask } [ advertise-map map-name | as-set | attribute-map map-
name | summary-only | suppress-map map-name ]
no aggregate-address { ip-addr ip-mask | ipv6-addr ipv6-mask } [ advertise-map map-name | as-set | attribute-map map-
name | summary-only | suppress-map map-name ]
Command Default
The device advertises individual routes for all networks.
Parameters
ip-addr
IPv4 address.
ip-mask
IPv4 mask.
ipv6-addr
IPv6 address.
ipv6-mask
IPv6 mask.
advertise-map
Causes the device to advertise the more-specific routes in the specified route map.
map-name
Specifies a route map to be consulted. Range is from 1 through 63 ASCII characters.
as-set
Causes the device to aggregate AS-path information for all routes in the aggregate routes from a range of networks
into a single network prefix.
attribute-map
Causes the device to set attributes for the aggregate routes according to the specified route map.
map-name
Specifies a route map to be consulted.
summary-only
Prevents the device from advertising more-specific routes contained within the aggregate route.
suppress-map
Prevents the more-specific routes contained in the specified route map from being advertised.
map-name
Specifies a route map to be consulted.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command disables this feature so that the device advertises individual routes for all networks.
Examples
The following example aggregates routes from a range of networks into a single network prefix under the IPv6 address family
and advertises the paths for this route as AS_SET.
History
Release version Command history
alias
Configures global or user-level aliases for device commands.
Syntax
alias alias-name expansion
no alias alias-name
Parameters
alias-name
Specifies the alias name. The number of characters can be from 1 through 255.
expansion
Specifies the CLI command to be triggered when the alias is entered. If the command is more than one word, type
double quotes (") around the command. The number of characters can be from 1 through 1023.
Modes
Alias configuration mode
Usage Guidelines
Global aliases are available to all users.
In the alias configuration mode, to delete a global alias use the no form of his command.
In the user-alias configuration mode, to delete a user alias use the no form of his command.
Examples
The following example defines ck as a global alias that enters the show clock command.
For the user jdoe, the following example defines sv as a user-level alias that enters the show version command.
History
Release version Command history
alias-config
Launches the alias configuration mode, enabling you to define aliases.
Syntax
alias-config
Parameters
alias
(For the no option) Deletes all global aliases.
user username
(For the no option) Deletes all aliases defined for the specified user.
Modes
Global configuration mode
Usage Guidelines
From the alias configuration mode—which you access by entering this command—you can manage global aliases. From that
mode, you can also access the user-alias configuration mode for a specified user, from which you can manage aliases for that
user.
To delete all global aliases, use the no alias-config alias form of this command.
To delete all aliases defined for a specified user, use the no alias-config user form of this command.
Examples
The following example accesses the alias configuration mode. It then defines ck as a global alias for the show clock command.
The following example deletes all aliases defined for the user jdoe.
History
Release version Command history
allow-vn-tag
Changes an interface from the default support for 802.1BR headers to support for VN-Tag headers.
Syntax
allow-vn-tag
no allow-vn-tag
Command Default
802.1BR headers are supported and VN-Tag headers are not supported.
Modes
Interface configuration mode
Usage Guidelines
To learn where default support for 802.1BR headers was changed to support for VN-Tag headers—by running allow-vn-tag—
run the show running-config interface command:
• VN-Tag interfaces display allow-vn-tag.
• 802.1BR interfaces do not display allow-vn-tag.
Disabling 802.1BR header-mode on an interface also disables E-Tag support on that interface.
After you run this command, you do not need to reboot SLX-OS.
The no form of this command disables support for VN-Tag headers and restores the default support for 802.1BR headers.
Examples
The following example enables VN-Tag header-mode on an interface, disabling the default 802.1BR mode.
The following example restores the default 802.1BR header-mode on an interface, disabling support for VN-Tag headers.
History
Release version Command history
always-compare-med
Configures the device always to compare the Multi-Exit Discriminators (MEDs), regardless of the autonomous system (AS)
information in the paths.
Syntax
always-compare-med
no always-compare-med
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disallows the comparison of the MEDs for paths from neighbors in different autonomous
systems.
Examples
The following example configures the device always to compare the MEDs.
History
Release version Command history
always-propagate
Enables the device to advertise BGP routes even though they are not installed in the RIB Manager.
Syntax
always-propagate
no always-propagate
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default so that the device does not advertise BGP routes not installed in the RIB
manager.
Examples
The following example configures the device to advertise routes that are not installed in the RIB manager.
The following example configures the device to reflect advertise that are not installed in the RIB manager in IPv6 address-family
unicast configuration mode.
The following example configures the device to advertise routes that are not installed in the RIB manager in a nondefault VRF
instance.
History
Release version Command history
announce-interval
Configures the interval at which a Precision Time Protocol (PTP) slave clock receives PTP Announce messages from a master
clock.
Syntax
announce-interval [ interval ]
no announce-interval
Command Default
The default Announce message interval is 0 log seconds.
Parameters
interval
PTP Announce interval, in log seconds. Range is from 0 through 4. The default is 0 (1 packet/second).
Modes
PTP configuration mode
Usage Guidelines
This interval is configured on the interface of a slave device. The value for interval must be consistent on all Extreme SLX-OS
devices within a single PTP domain.
The inputs for interval represent base 2 exponents, where the packet rate is 1/(2log seconds).
Examples
To configure a PTP Announce interval of 2 packets per second on an Ethernet interface:
History
Release version Command history
announce-timeout
Configures the number of Announce message intervals that elapse before a timeout occurs on an interface.
Syntax
announce-timeout count
no announce-timeout
Command Default
Default number of Announce message intervals before a timeout is 3.
Parameters
count
Number of Announce message intervals. Range is from 3 through 10. The default is 3.
Modes
PTP configuration mode
Usage Guidelines
The value for count must be consistent on all Extreme SLX-OS devices within a single PTP domain.
Use the no form of this command to revert to the default Announce message interval of 3.
Examples
To configure a PTP Announce timeout interval of 9 on an Ethernet interface:
History
Release version Command history
Syntax
area { A.B.C.D | decimal } authentication spi value { ah | esp null } { hmac-md5 | hmac-sha1 } key key
Command Default
Authentication is not enabled on an area.
Parameters
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format.
spi
Specifies the Security Policy Index (SPI).
value
Specifies the Security Policy Index (SPI) value. Valid values range from decimal numbers 512 through
4294967295
ah
Specifies authentication header (ah) as the protocol to provide packet-level security.
esp
Specifies Encapsulating Security Payload (ESP) as the protocol to provide packet-level security.
null
Specifies that the ESP payload is not encrypted.
hmac-md5
Enables Hashed Message Authentication Code (HMAC) Message Digest 5 (MD5) authentication on the OSPF area.
hmac-sha1
Enables HMAC Secure Hash Algorithm 1 (SHA-1) authentication on the OSPF area.
key
Number used in the calculation of the message digest.
key
The 40 hexadecimal character key.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Enter no area authentication spi to remove an authentication specification for an area from the configuration.
Examples
The following example enables ah and MD5 authentication for an OSPF area, setting a SPI value of 750.
The following example enables esp and SHA-1 authentication for an OSPF area, setting a SPI value of 900.
History
Release version Command history
Syntax
area { ip-addr | decimal } nssa { metric [ no-summary ] | default-information-originate }
no area nssa
Command Default
No areas are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address In decimal format.
metric
Additional cost for using a route to or from this area. Valid values rante from 1 through 16777215.
no-summary
When configured on the NSSA area border router (ABR), this parameter prevents any Type 3 and Type 4 summary
link-state advertisement (LSA) from being injected into the area. The only exception is that a default route is injected
into the NSSA by the ABR, and strictly as a Type 3 LSA (not a Type 7, because that could cause intra-AS traffic to get
routed out the AS). This makes the NSSA an NSSA totally stubby area, which can only have Type 1, 2 and 7 LSAs.
Note: This parameter is disabled by default, which means the default route must use a Type 7 LSA.
default-information-originate
When configured on the ABR, this parameter injects a Type 7 default route into the NSSA area. As a result, the other
NSSA routers install the default route through the advertising NSSA ABR. By default the NSSA ABR does not
originate a default route to the NSSA.
Modes
OSPF router configuration mode
Usage Guidelines
NSSAs are typically needed when one-way transmission of Type-5 LSAs (out of the area) is desired but injection of the same
LSAs into the area is not acceptable.
Once created, the type of the area cannot be changed. The only exception to this rule is that an NSSA or stub area can be
changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 5 on an NSSA identified as 2, includes the no-summary parameter, and
prevents the device from importing type 3 and type 4 summary LSAs into the NSSA area.
History
Release version Command history
Syntax
area { ip-addr | decimal } nssa [ metric ] [ default-information-originate [ metric num ] [ metric-type { type1 | type2 } ] ] [ no-
redsitribution ] [ no-summary ] [ translator-always ] [ translator-interval interval ]
no area nssa
Command Default
No areas are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
metric
Additional cost for using a route to or from this area. Valid values range from 1 through 1048575.
default-information-originate
When configured on the ABR, this parameter injects a Type 7 default route into the NSSA area. As a result, the other
NSSA routers install the default route through the advertising NSSA ABR. By default the NSSA ABR does not
originate a default route to the NSSA.
metric num
Specifies the OSPF route metric.
metric-type
Specifies how the cost of a neighbor metric is determined.
type1
The metric of a neighbor is the cost between itself and the router plus the cost of using this router for routing
to the rest of the world.
type2
The metric of a neighbor is the total cost from the redistributing routing to the rest of the world.
no-redistribution
The no-redistribution parameter prevents an NSSA ABR from generating external (type-7) LSA into a NSSA area. This
is used in the case where an ASBR should generate type-5 LSA into normal areas and should not generate type-7
LSA into a NSSA area. By default, redistribution is enabled in a NSSA.
no-summary
When configured on the NSSA area border router (ABR), this parameter prevents any Type 3 and Type 4 summary
link-state advertisement (LSA) from being injected into the area. The only exception is that a default route is injected
into the NSSA by the ABR, and strictly as a Type 3 LSA (not a Type 7, because that could cause intra-AS traffic to get
routed out the AS). This makes the NSSA a NSSA totally stubby area, which can only have Type 1, 2 and 7 LSAs.
Note: This parameter is disabled by default, which means the default route must use a Type 7 LSA.
translator-always
Configures the translator-role. When configured on an ABR, this causes the router to unconditionally assume the role
of a NSSA translator. By default, translator-always is not set, the translator role by default is candidate.
translator-interval interval
Configures the time interval for which an elected NSSA translator continues to perform its duties even after its NSSA
translator role has been disposed by another router. Valid values range from 10 through 60 seconds. By default the
stability-interval is 40 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
NSSAs are typically needed when one-way transmission of Type-5 LSAs (out of the area) is desired but injection of the same
LSAs into the area is not acceptable.
Once created, the type of the area cannot be changed. The only exception to this rule is that a NSSA or stub area can be
changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 4 on a NSSA identified as 8 (in decimal format), and prevents any Type 3 or
Type 4 summary LSAs from being injected into the area.
History
Release version Command history
Syntax
area { ip-addr | decimal } prefix-list name { in | out }
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
prefix-list name
Specifies a prefix-list between 1 and 32 characters.
in
Specifies that the prefix list is applied to prefixes advertised to the specified area from other areas.
out
Specifies that the prefix list is applied to prefixes advertised out of the specified area to other areas.
Modes
OSPF router configuration mode
OSPF router VRF configuration mode
Usage Guidelines
This command is only applicable to ABRs. The no form of the command changes or cancels the configured filter and
advertises all type 3 LSAs.
Examples
The following example applies a prefix list to type 3 LSAs advertised out of an area with the area-id 10.1.1.1.
The following example applies a prefix list to type 3 LSAs advertised in to an area with the area-id 10.1.1.1.
History
Release version Command history
Syntax
area { A.B.C.D | decimal } range E.F.G.H I.J.K.L advertise [ cost cost-value ]
no area range
Parameters
A.B.C.D
Area address in IP address format.
decimal
Area address in decimal format.
E.F.G.H I.J.K.L
Specifies the IP address and mask portion of the range. All network addresses that match this network are
summarized in a single route and advertised by the ABR.
advertise
Sets the address range status to advertise and generates a Type 3 summary LSA.
cost cost-value
Sets the cost value for the area range. This value is used as the generated summary LSA cost. The range for
cost_value is 1 to 6777214. If this value is not specified, the cost value is the default range metric calculation for the
generated summary LSA cost.
not-advertise
Sets the address range status to DoNotAdvertise; the Type 3 LSA is suppressed, and the component networks remain
hidden from other networks. This setting is used to temporarily pause route summarization from the area.
Modes
OSPF router configuration mode
OSPF router VRF configuration mode
Usage Guidelines
Use this command only on ABRs to specify route summarization for an existing area. The result is that a single summary route
is advertised to other areas by the ABR, in the form of a Type 3 LSA. Routing information is condensed at area boundaries and
external to the area, and only a single route is advertised for each address range.
An example of when you might want to use this command is if you have many small networks advertised from area 0 to any
other area, or from any non-backbone area into the backbone. This command gives you a summary route instead of many
smaller routes. In an area, the OSPF database on each router must be an exact copy of the databases of the other routers. This
means that no summarization is allowed within the area.
The no form of the command disables the specification of range parameters on an ABR.
Examples
The following example advertises to Area 3 all the addresses on the network 10.1.1.0 10.255.255.0 in the ABR you are
signed into.
History
Release version Command history
Syntax
area { ip-addr | decimal } range ipv6 address/mask [ advertise | not-advertise ] [ cost cost-value ]
no area range
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
ipv6 address/mask
Specifies the IPv6 address in dotted-decimal notation and the IPv6 mask in CIDR notation. All network addresses that
match this network are summarized in a single route and advertised by the ABR.
advertise
Sets the address range status to advertise and generates a Type 3 summary LSA.
not-advertise
Sets the address range status to DoNotAdvertise; the Type 3 LSA is suppressed, and the component networks remain
hidden from other networks. This setting is used to temporarily pause route summarization from the area.
cost cost-value
Sets the cost value for the area range. This value is used as the generated summary LSA cost. The range for
cost_value is 1 to 6777214. If this value is not specified, the cost value is the default range metric calculation for the
generated summary LSA cost.
Modes
OSPFv3 router configuration mode
OSPFv3 router VRF configuration mode
Usage Guidelines
Use this command only on ABRs to specify route summarization for an existing area. The result is that a single summary route
is advertised to other areas by the ABR, in the form of a Type 3 LSA. Routing information is condensed at area boundaries and
external to the area, and only a single route is advertised for each address range.
An example of when you might want to use this command is if you have many small networks advertised from area 0 to any
other area, or from any non-backbone area into the backbone. This command gives you a summary route instead of many
smaller routes. In an area, the OSPF database on each router must be an exact copy of the databases of the other routers. This
means that no summarization is allowed within the area.
The no form of the command disables the specification of range parameters on an ABR.
Examples
The following example advertises to Area 3 all the addresses on the network 2001:db8:8::/45 in the ABR you are signed into.
History
Release version Command history
Syntax
area { A.B.C.D | decimal } stub metric [ no-summary ]
no area stub
Command Default
No areas are created.
Parameters
A.B.C.D
Area address in IP address format.
decimal
Area address In decimal format.
metric
Additional cost for using a route to or from this area. Valid values range from 1 through 6777215.
no-summary
When configured on the ABR, this parameter prevents any Type 3 and Type 4 summary LSAs from being injected into
the area. The only exception is that a default route is injected into the stub/totally stubby area by the ABR as a Type 3
LSA. Enabling this parameter makes the area a so-called totally stubby area, which can only have Types 1 and 2. This
parameter is disabled by default.
Modes
OSPF router configuration mode
Usage Guidelines
Once created, the type of the area cannot be changed. The only exception to this rule is that a NSSA or stub area can be
changed to a totally NSSA or a totally stub area, respectively.
The no form of the command deletes a stub area.
Examples
The following example sets an additional cost of 5 on a stub area called 2.
History
Release version Command history
Syntax
area { ip-addr | decimal } stub metric
no area stub
Command Default
No areas are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address In decimal format.
metric
Additional cost for using a route to or from this area. Valid values range from 3 through 1048575.
no-summary
When configured on the ABR, this parameter prevents any Type 3 and Type 4 summary LSAs from being injected into
the area. The only exception is that a default route is injected into the stub/totally stubby area by the ABR as a Type 3
LSA. Enabling this parameter makes the area a so-called totally stubby area, which can only have Types 1 and 2. This
parameter is disabled by default.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Once created, the type of the area cannot be changed. The only exception to this rule is that a NSSA or stub area can be
changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 5 on a stub area called 2.
History
Release version Command history
Syntax
area { ip-addr | decimal } virtual-link E.F.G.H [ authentication-key password ] [ dead-interval time ] [ hello-interval time ]
[ md5-authentication { key-activation-wait-time time | key-id num key } ] [ retransmit-interval time ] [ transmit-delay
time ]
no area virtual-link
Command Default
No virtual links are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
E.F.G.H
ID of the OSPF router at the remote end of the virtual link.
authentication-key password
Sets the password and encryption method. Only one encryption method can be active on an interface at a time. All
OSPF packets transmitted on the interface contain this password. All OSPF packets received on the interface are
checked for this password. If the password is not present, then the packet is dropped.
dead-interval time
How long a neighbor router waits for a hello packet from the current router before declaring the router down. This value
must be the same for all routers and access servers that are attached to a common network. Valid values range from 3
through 65535 seconds. The default is 40 seconds.
hello-interval time
Time between hello packets that the router sends on an interface. The value must be the same for all routers and
access servers that are attached to a common network. Valid values range from 1 through 65535 seconds. The
default is 10 seconds.
md5-authentication
Sets either MD5 key-activation wait time or key identifier.
key-activation-wait-time time
Time before a newly configured MD5 authentication key is valid. This parameter provides a graceful transition
from one MD5 key to another without disturbing the network. All new packets transmitted after the wait time
ends will use the newly configured MD5 Key. OSPF packets that contain the old MD5 key are accepted for
up to five minutes (300 seconds) after the new MD5 key is in operation. Valid values range from 0 through
14400 seconds. The default is 300 seconds.
retransmit-interval time
Time between Link State Advertisement (LSA) retransmissions for adjacencies belonging to the interface. Set
this interval to a value larger than the expected round-trip delay between any two routers on the attached
network. Valid values range from 0 through 3600 seconds. The default is 5 seconds.
transmit-delay time
Estimated time required to send an LSA on the interface. This value must be an integer greater than zero. The
age of each LSA in the update packet is incremented by the value of this parameter before transmission
occurs. Valid values range from 0 through 3600 seconds. The default is 1 second.
Modes
OSPF router configuration mode
Usage Guidelines
The no form of the command removes a virtual link.
Examples
The following example creates a virtual link for an area whose decimal address is 1, and where the ID of the OSPFv2 device at
the remote end of the virtual link is 10.1.2.3.
History
Release version Command history
Syntax
area { ip-addr | decimal } virtual-link A.B.C.D [ dead-interval time | hello-interval time | hello-jitter interval | retransmit-interval
time | transmit-delay time ]
no area virtual-link
Command Default
No virtual links are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
A.B.C.D
ID of the OSPFv3 device at the remote end of the virtual link.
dead-interval time
How long a neighbor device waits for a hello packet from the current device before declaring the device down. This
value must be the same for all devices and access servers that are attached to a common network. Valid values range
from 3 through 65535 seconds. The default is 40 seconds.
hello-interval time
Time between hello packets that the device sends on an interface. The value must be the same for all devices and
access servers that are attached to a common network. Valid values range from 1 through 65535 seconds. The
default is 10 seconds.
hello-jitter interval
Sets the allowed jitter between hello packets. Valid values range from 1 through 50 percent (%). The default value is
10%.
retransmit-interval time
Time between Link State Advertisement (LSA) retransmissions for adjacencies belonging to the interface. Set this
interval to a value larger than the expected round-trip delay between any two devices on the attached network. Valid
values range from 1 through 3600 seconds. The default is 5 seconds.
transmit-delay time
Estimated time required to send an LSA on the interface. This value must be an integer greater than zero. The age of
each LSA in the update packet is incremented by the value of this parameter before transmission occurs. Valid values
range from 0 through 3600 seconds. The default is 1 second.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The values of the dead-interval and hello-interval parameters must be the same at both ends of a virtual link. Therefore, if you
modify the values of these parameters at one end of a virtual link, you must make the same modifications on the other end of
the link. The values of the other virtual link parameters do not require synchronization.
Examples
The following example creates a virtual link for an area whose decimal address is 1, and where the ID of the OSPFv3 device at
the remote end of the virtual link is 209.157.22.1.
History
Release version Command history
Syntax
area { ip-addr | decimal } virtual-link E.F.G.H authentication spi spi-value { ah | esp null } { hmac-md5 | hmac-sha1 } key key
Command Default
Authentication is not enabled on a virtual-link.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
E.F.G.H
ID of the OSPFv3 device at the remote end of the virtual link.
spi spi-value
Specifies the security policy index (SPI) value. Valid values range from decimal numbers 512 through 4294967295
ah
Specifies authentication header (ah) as the protocol to provide packet-level security.
esp
Specifies Encapsulating Security Payload (ESP) as the protocol to provide packet-level security.
null
Specifies that the ESP payload is not encrypted.
hmac-md5
Enables Hashed Message Authentication Code (HMAC) Message Digest 5 (MD5) authentication on the OSPF area.
hmac-sha1
Enables HMAC Secure Hash Algorithm 1 (SHA-1) authentication on the OSPF area.
key key
Number used in the calculation of the message digest.40 hexadecimal character key.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Enter no area { A.B.C.D | decimal } virtual-link E.F.G.H authentication spi spi to remove authentication from the virtual-links in
the area.
Examples
The following example configures IPsec on a virtual link in an OSPFv3 area.
History
Release version Command history
arp
Creates a static Address Resolution Protocol (ARP) entry.
Syntax
arp A.B.C.D mac-address interface { ethernet slot / port | ve ve-id }
no arp A.B.C.D
Parameters
A.B.C.D
Specifies a valid IP address.
mac-address
Specifies a valid MAC address.
interface
Specifies an interface type.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
ve ve-id
Specifies a virtual Ethernet (VE) interface.
Modes
Global configuration mode
Usage Guidelines
The no form of the command deletes a static ARP entry.
Examples
The following example creates a static ARP entry that associates an IP address, a MAC address, and a physical port.
History
Release version Command history
arp access-list
Creates an Address Resolution Protocol (ARP) access control list (ACL), which is one of the steps implementing Dynamic ARP
Inspection (DAI) on a VLAN.
Syntax
arp access-list acl-name
Command Default
No ARP ACLs are defined.
Parameters
acl-name
Specifies the name of the ARP ACL. The name can be up to 63 characters in length, and must begin with an
alphanumeric character. No special characters are allowed, except for the underscore (_) and hyphen (-).
Modes
Global configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC addresses are accepted only if
all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
You can also append the permit ip host command to the arp access-list command.
The no form of the command deletes the ARP ACL if the ACL is not applied on any VLAN or port.
Examples
The following example implements DAI:
History
Release version Command history
as-path-ignore
Disables the comparison of the autonomous system (AS) path lengths of otherwise equal paths.
Syntax
as-path-ignore
no as-path-ignore
Command Default
The comparison of the AS path lengths of otherwise equal paths is enabled.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores default behavior.
Examples
The following example configures the device to always disable the comparison of AS path lengths.
History
Release version Command history
auth-port
Configures a user datagram protocol (UDP) port for Remote Authentication Dial-In User Service (RADIUS) server
authentication.
Syntax
auth-port portnum
no auth-port
Command Default
By default, port 1812 is used for RADIUS server authentication.
Parameters
portnum
Specifies the UDP port to use for RADIUS server authentication. The range is from 0 through 65535. The default port
is 1812.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to configure port 1234 as the port to use for RADIUS server authentication.
History
Release version Command history
Syntax
auto-cost reference-bandwidth { value | use-active-ports }
no auto-cost reference-bandwidth
Parameters
value
Reference bandwidth in Mbps. Valid values range from 1 through 4294967. The default reference bandwidth is 100
Mbps.
use-active-ports
Specifies that any dynamic change in bandwidth immediately affects the cost of OSPF routes. This parameter enables
cost calculation for currently active ports only.
Modes
OSPF router configuration mode
Usage Guidelines
Use this command to configure the cost of an interface that a device advertises to it's OSPF neighbors. OSPF calculates the
cost of a route as the ratio of the reference bandwidth to the bandwidth of the egress interface. An increase in the reference
bandwidth results in an increased cost. If the resulting cost is less than 1, the software rounds the cost up to 1.
The bandwidth for interfaces that consist of more than one physical port is calculated as follows:
• LAG group — The combined bandwidth of all the ports.
• Virtual interface — The combined bandwidth of all the ports in the port-based VLAN that contains the virtual interface.
If a change to the reference bandwidth results in a cost change to an interface, the device sends a link-state update to update
the costs of interfaces advertised by the device.
NOTE
If you specify the cost for an individual interface (by using the ip ospf cost command), the cost you specify overrides
the cost calculated by the software.
Examples
The following example configures a reference bandwidth of 500.
The reference bandwidth specified in this example results in the following costs:
• 10 Mbps port’s cost = 500/10 = 50.
• 100 Mbps port’s cost = 500/100 = 5.
• 1000 Mbps port’s cost = 500/1000 = 0.5, which is rounded up to 1.
The costs for 10 Mbps and 100 Mbps ports change as a result of the changed reference bandwidth. Costs for higher-speed
interfaces remain the same.
History
Release version Command history
Syntax
auto-cost reference-bandwidth value
no auto-cost reference-bandwidth
Parameters
value
Reference bandwidth in Mbps. Valid values range from 1 through 4294967. The default is 100 Mbps.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command to configure the cost of an interface that a device advertises to it's OSPF neighbors. OSPFv3 calculates the
cost of a route as the ratio of the reference bandwidth to the bandwidth of the egress interface. An increase in the reference
bandwidth results in an increased cost. If the resulting cost is less than 1, the software rounds the cost up to 1.
The bandwidth for interfaces that consist of more than one physical port is calculated as follows:
• LAG group — The combined bandwidth of all the ports.
• Virtual interface — The combined bandwidth of all the ports in the port-based VLAN that contains the virtual interface.
If a change to the reference bandwidth results in a cost change to an interface, the device sends a link-state update to update
the costs of interfaces advertised by the device.
NOTE
If you specify the cost for an individual interface using the ipv6 ospf cost command, the cost you specify overrides
the cost calculated by the software.
The no form of the command restores the reference bandwidth to its default value and, thus, restores the default costs of the
interfaces to their default values.
Examples
The following example configures a reference bandwidth of 500.
The reference bandwidth specified in this example results in the following costs:
• 10 Mbps port’s cost = 500/10 = 50.
• 100 Mbps port’s cost = 500/100 = 5.
• 1000 Mbps port’s cost = 500/1000 = 0.5, which is rounded up to 1.
• 155 Mbps port cost = 500/155 = 3.23, which is rounded up to 4
• 622 Mbps port cost = 500/622 = 0.80, which is rounded up to 1
• 2488 Mbps port cost = 500/2488 = 0.20, which is rounded up to 1
The costs for 10 Mbps, 100 Mbps, and 155 Mbps ports change as a result of the changed reference bandwidth. Costs for
higher-speed interfaces remain the same.
History
Release version Command history
auto-shutdown-new-neighbors
Disables the establishment of BGP connections with a remote peer when the peer is first configured.
Syntax
auto-shutdown-new-neighbors
no auto-shutdown-new-neighbors
Modes
BGP configuration mode
Usage Guidelines
The auto-shutdown-new-neighbors command applies to all neighbors configured under each VRF. When the auto-
shutdown-new-neighbors command is used, any new neighbor configured will have the shutdown flag enabled for them by
default. Once all the neighbor parameters are configured and it is ready to start the establishment of BGP session with the
remote peer, the BGP neighbor’s shutdown parameter has to disabled by removing the shutdown command for the neighbor.
Examples
The following example enables auto shutdown of BGP neighbors on initial configuration.
The following example disables the peer shutdown state and begins the BGP4 session establishment process.
History
Release version Command history
backup-advertisement-interval
Configures the interval at which backup VRRP routers advertise their existence to the master router.
Syntax
backup-advertisement-interval interval
Command Default
The default backup advertisement-interval is 60 seconds.
Parameters
interval
Interval at which a backup VRRP router advertises its existence to the master router. Valid values range from 60
through 3600 seconds.
Modes
Virtual-router-group configuration mode
Usage Guidelines
The interval is the length of time, in seconds, between each advertisement sent from the backup routers to the master router.
The advertisement notifies the master router that the backup is still active. If the master router does not receive an
advertisement from the backup in a designated amount of time, the backup with the highest priority can assume the role of
master.
Examples
To set the backup advertisement interval to 120 seconds for VRRP-E group 10:
History
Release version Command history
banner
Defines an incoming, login, or message of the day banner.
Syntax
banner { incoming | login | motd } string
Parameters
incoming
Sets the incoming terminal line banner that is displayed on the console when a user establishes a Telnet session.
login
Sets the login banner that is displayed on the user terminal when the user logs into the device.
motd
Sets the message of the day (MOTD) that is displayed on the user terminal when a Telnet CLI session is established.
string
Specifies a text string from 1 through 2048 characters in length including spaces.
Modes
Global configuration mode
Usage Guidelines
The banner can appear on multiple lines if you enter multiline mode by using Esc-M and exit by using CTRL-D.
Examples
To create a login banner with a single line:
History
Release version Command history
basedn
Defines the base domain name of the LDAP host.
Syntax
basedn { basedn }
no basedn
Command Default
The base domain name is not defined.
Parameters
basedn
The base domain name of the LDAP host.
Modes
LDAP host configuration mode.
Usage Guidelines
Use the no form of this command to remove the base domain name.
Examples
To change the domain in an existing configuration:
History
Release version Command history
bfd
Enables Bidirectional Forwarding Detection (BFD).
Syntax
bfd
no bfd
Modes
OSPF router configuration mode
Usage Guidelines
Use the bfd command in OSPF router configuration mode to enable BFD sessions on all OSPFv2 interfaces on which BFD
has been configured using the ip ospf bfd command. Use the bfd command in OSPFv3 router configuration mode to enable
BFD sessions on all OSPFv3 interfaces on which BFD has been configured using the ipv6 ospf bfd command.
Use the bfd command in VXLAN overlay gateway site configuration mode to configure BFD for Layer 2 extension tunnels. Use
the no form of this command in VXLAN overlay gateway site configuration mode to disable BFD for the tunnel.
The no form of the command disables BFD globally in OSPF router configuration mode or OSPFv3 router configuration
mode.
Examples
The following example enables BFD globally in OSPF router configuration mode.
The following example disables BFD globally in OSPFv3 router configuration mode.
History
Release version Command history
bfd holdover-interval
Sets the time interval for which Open Shortest Path First (OSPF) or Border Gateway Protocol (BGP) routes are withdrawn after a
Bidirectional Forwarding Detection (BFD) session is declared down.
Syntax
bfd holdover-interval time
Parameters
time
Specifies the BFD holdover interval in seconds. In BGP configuration mode, valid values range from 1 through 30 and
the default is 0. In OSPF router VRF and OSPFv3 router VRF configuration mode, valid values range from 1 through
20, and the default is 0.
Modes
BGP configuration mode
Usage Guidelines
The BFD holdover interval is supported for both single-hop and multihop sessions.
In BGP configuration mode, use this command to set the BFD holdover interval globally for BGP. In OSPF router configuration
mode or OSPF router VRF configuration mode, use this command to set the BFD holdover interval globally for OSPFv2. In
OSPFv3 router or OSPFv3 router VRF configuration mode, use this command to set the BFD holdover interval globally for
OSPFv3.
The no form of the command removes the configured BFD holdover interval from the configuration, and reverts to the default
value of 0.
Examples
The following example sets the BFD holdover interval globally to 15 in BGP configuration mode.
The following example sets the BFD holdover interval globally to 12 in OSPF router configuration mode.
The following example sets the BFD holdover interval globally to 20 in OSPFv3 router configuration mode.
The following example sets the BFD holdover interval globally to 20 for VRF instance “red” in OSPFv3 router VRF
configuration mode.
History
Release version Command history
bfd interval
Configures Bidirectional Forwarding Detection (BFD) session parameters on an interface.
Syntax
bfd interval transmit-time min-rx receive-time multiplier number
Parameters
transmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers. Valid values range from 50
through 30000. The default is 200 for chassis platforms. The default is 500 for non-chassis platforms. In VXLAN
overlay gateway site configuration mode, valid values range from 100 through 30000, and the default is 100 on all
platforms.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers. Valid values range
from 50 through 30000. The default is 200 for chassis platforms. The default is 500 for non-chassis platforms. In
VXLAN overlay gateway site configuration mode, valid values range from 300 through 30000, and the default is 300
on all platforms.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer before BFD
determines that the connection to that peer is not operational. Valid values range from 3 through 50. The default is 3.
Modes
BGP configuration mode
Interface subtype configuration mode
Usage Guidelines
The transmit-time and min-rx receive-time parameters are the intervals desired by the local device. The actual values in use will
be the negotiated values.
Use the bfd interval command in BGP configuration mode for multihop sessions only. Single-hop sessions in BGP use either
the values configured at the interface level using the bfd interval command or the default interval values.
The no form of the command reverts to the default parameters.
Examples
The following example sets the BFD session parameters globally for an Ethernet interface.
The following example sets the BFD session parameters globally for a virtual Ethernet (VE) interface.
The following example sets the BFD session parameters globally for BGP.
The following example sets the BFD session parameters on a VXLAN overlay gateway site.
History
Release version Command history
bfd shutdown
Disables Bidirectional Forwarding Detection (BFD) on an interface.
Syntax
bfd shutdown
no bfd shutdown
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command re-enables BFD sessions.
Examples
The following example disables BFD sessions on a specific Ethernet interface.
The following example disables BFD sessions on a specific virtual Ethernet (VE) interface.
History
Release version Command history
bgp-redistribute-internal
Causes the device to allow the redistribution of iBGP routes from BGP into OSPF.
Syntax
bgp-redistribute-internal
no bgp-redistribute-internal
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
By default, with default VRF instances, the device does not allow the redistribution of iBGP routes from BGP4 and BGP4+ into
OSPF. This helps to eliminate routing loops. In non-default VRF instances, by default the device allows the redistribution of
iBGP routes from BGP into OSPF.
Examples
The following example enables BGP4 route redistribution.
The following example enables BGP4+ route redistribution for VRF instance "red".
History
Release version Command history
breakout mode
Configures 40-Gbe or 100-Gbe ports as four 10-Gbe or four 25-Gbe ports dynamically.
Syntax
breakout mode { 4x10g | 4x25g }
no breakout
Command Default
See the Usage Guidelines.
Parameters
4x10g
Specifies 4x10G mode.
4x25g
Specifies 4x25G mode.
Modes
Hardware connector configuration mode
Usage Guidelines
Dynamic breakout is supported; the user does not need to reboot the switch to execute the breakout.
Examples
The following example shows the steps to configure 4x10G breakout mode on a 40G/100G port.
History
Release version Command history
bridge-domain
Creates a bridge domain.
Syntax
bridge-domain { id } [ p2mp | p2p ]
Command Default
No bridge domain is configured.
Parameters
id
Specifies a unique numeric bridge-domain identifier. On SLX 9140, the range is from 1 through 4096. On SLX
9240, the range is from 1 through 3566.
p2mp
Specifies a multipoint service type. This is the default service type.
p2p
Specifies a point-to-point cross-connect service type.
Modes
Global configuration mode.
Usage Guidelines
The SLX device supports bridge domain on an MCT cluster.
Examples
The following example shows how to configure bridge domain 1 and specifies a point-to-point cross-connect service for the
domain.
History
Release version Command history
bridge-domain (EVPN)
Configures a bridge domain (BD) in Ethernet VPN (EVPN) instance configuration mode and enters EVPN bridge-domain
configuration mode.
Syntax
bridge-domain number [ add | remove ]
no bridge-domain number
Command Default
No bridge domain is configured.
Parameters
number
Specifies an EVPN bridge domain. On SLX 9140, the range is from 1 through 4096. On SLX 9240, the range is
from 1 through 3566.
add
Adds a bridge domain or range of bridge domains to the EVPN instance.
remove
Removes a bridge domain or range of bridge domains from the EVPN instance.
Modes
EVPN instance configuration mode
Usage Guidelines
Use the no form of this command to delete a bridge domain from an EVPN instance.
Examples
To specify a bridge domain for an EVPN instance and enter EVPN bridge-domain configuration mode:
History
Release version Command history
bridge-priority
Specifies the bridge priority for the common instance.
Syntax
bridge-priority priority
no bridge-priority
Command Default
The default priority is 32768.
Parameters
priority
Specifies the bridge priority. Valid values range from 0 through 61440 in increments of 4096.
Modes
Protocol Spanning Tree mode
Usage Guidelines
The priority values can be set only in increments of 4096.
Using a lower priority value indicates that the bridge might become root.
Examples
To specify the bridge priority:
History
Release version Command history
bsr-candidate
Configures a bootstrap router (BSR) as a candidate to distribute rendezvous point (RP) information to the other PIM Sparse
devices within a PIM Sparse domain.
Syntax
bsr-candidate interface [ ethernet | loopback | port-channel| ve ]
no bsr-candidate
Command Default
The PIM router does not participate in BSR election.
Parameters
loopback num
Specifies the loopback interface for the candidate BSR.
ve num
Specifies the virtual interface for the candidate BSR.
port-channel num
Specifies the port-channel number for the candidate BSR.
Modes
PIM Router configuration mode
Usage Guidelines
The no form of this command makes the PIM router cease to act as a candidate BSR.
Each PIM Sparse domain has one active BSR. For redundancy, you can configure ports on multiple devices as candidate BSRs.
The PIM Sparse protocol uses an election process to select one of the candidate BSRs as the BSR for the domain. The BSR
with the highest BSR priority is elected. If the priorities result in a tie, the candidate BSR interface with the highest IP address is
elected.
Although you can configure the device as only a candidate BSR or an RP, it is recommended that you configure the same
interface on the same device as both a BSR and an RP.
Examples
The following example uses a physical interface to configure a device as a candidate BSR.
The following example uses a loopback interface to configure a device as a candidate BSR.
The following example uses a virtual interface to configure a device as a candidate BSR.
History
Release version Command history
Syntax
capability as4-enable
no capability as4-enable
Command Default
4-byte ASN capability is disabled.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disables 4-byte ASN capability if it has been enabled.
Examples
The following example enables 4-byte ASN capability.
History
Release version Command history
Syntax
capture packet interface ethernet slot/ port
capture packet interface ethernet slot / port direction { both | rx | tx } filter all [ packet-count count ]
Command Default
The capture packet interface Ethernet feature is disabled.
Parameters
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
direction
Specifies the direction of the frames.
both
(Not currently supported) Specifies frames either ingressing or egressing out through the port.
rx
Specifies frames ingressing into the port.
tx
Specifes frames egressing through the port.
filter
Specifies the filter.
l2
Captures only L2 control frames.
l3
Captures only L3 control frames.
all
Captures all supported frames on the port, as described in the Guidelines.
packet-count count
(Supported only in NPB system-mode, for the all option) Specifies the number of frames. The valid range is from 1
through 8000. The default is 2048.
Modes
Privileged EXEC mode
Usage Guidelines
In default system-mode, control frames and ACL-logged frames are captured.
In Network Packet Broker (NPB) system-mode, data frames are also captured.
When packet capture is active, the frames are saved to /tmp/pktcapture_running.pcap. Upon termination of packet
capture ( at packet-count count or by running no capture packet interface ethernet, this file is renamed /tmp/
pktcapture.pcap. By using the Unix scp command, you can securely copy/tmp/pktcapture.pcap for analysis.
Examples
(Under NPB system-mode) The following example captures up to 5000 frames ingressing to an Ethernet interface.
device# capture packet interface ethernet 0/9 direction rx filter all packet-count 5000
History
Release version Command history
cee
Applies the configured CEE map to the interface. This command also activates and configures QoS flow control on the
interface.
Syntax
cee default
no cee
Modes
Interface subtype configuration mode
Usage Guidelines
The only map name allowed is named default.
Use the no form of this command to remove the CEE map from the interface.
Examples
The following example configures the default CEE map to the interface.
History
Release version Command history
cee-map default
Accesses the default CEE map configuration mode.
Syntax
cee-map default
Modes
Global configuration mode
Usage Guidelines
The only map name allowed is named default.
Examples
The following example accesses the default CEE map configuration mode.
History
Release version Command history
Syntax
certutil import sshkey host remote_ip_address directory ssh_public_key_path file filename user user_acct password
password login login_id
no certutil sshkey
Parameters
host remote_ip
Specifies the IP address of the remote host.
directory path
Specifies the path to the certificate.
file filename
Specifies the SSH public key with a .pub extension.
user user_acct
Specifies the user name to access the remote host.
password password
Specifies the password to access the remote host.
login login_id
Specifies the login name in the remote host.
file filename
Specifies the SSH public key with a .pub extension.
Modes
Privileged EXEC mode
Usage Guidelines
Enter no certutil sshkey user to delete the SSH public key a specified user.
When using the 'pass' parameter with special characters (such as #$@`) use single or double-quotes around the password.
Alternatively, the special characters can be escaped with a backslash (\) preceding the special character.
Examples
The following command deletes the SSH public key for "testuser."
The following command deletes the SSH public key for "testuser."
device# certutil import ssh host 192.168.10.10 dir /home/brcd1/.ssh file id_rsa.pub user admin login
brcd1 pass Abcde\!
device# certutil import ssh host 192.168.10.10 dir /home/brcd1/.ssh file id_rsa.pub user admin login
brcd1 pass "Abcde!"
History
Release version Command history
channel-group
Enables Link Aggregation on an interface.
Syntax
channel-group number mode { active | passive | on } [ type standard ]
no channel-group
Command Default
The value for type is set to standard.
Parameters
number
Specifies a Link Aggregation Group (LAG) port-channel group number to which this link should administratively
belong. Values range from 1 through 6144.
mode
Specifies the mode of Link Aggregation.
active
Enables the initiation of LACP negotiation on an interface.
passive
Disables LACP on an interface.
on
Enables static link aggregation on an interface.
type standard
Specifies the 802.3ad standard-based LAG.
Modes
Interface subtype configuration mode
Usage Guidelines
This command adds an interface to a port-channel specified by the channel-group number. This command enables link
aggregation on an interface, so that it may be selected for aggregation by the local system.
Examples
The following example sets the channel-group ID to 10 and the mode to "passive".
History
Release version Command history
chassis
Sets the IPv4 or IPv6 address of a device chassis.
Syntax
chassis { virtual-ip IPv4-address | virtual-ipv6 IPv6-address }
no chassis
Command Default
The default is the initial address of the device chassis.
Parameters
virtual-ip IPv4-address
Sets an IPv4 address in dotted-decimal notation with a CIDR prefix (mask).
virtual-ipv6 IPv6-address
Sets an IPv6 address in colon-separated hexadecimal notation with a CIDR prefix.
Modes
Global configuration mode
Usage Guidelines
This command changes the default chassis IPv4 or IPv6 address. The default is the initial address of the device chassis.
Use this command to change the IP address to facilitate management, for example, if a device is moved to a different subnet.
The IP address of the management platform should be in the same subnet as the devices it manages.
Examples
IPv4:
IPv6:
History
Release version Command history
Syntax
chassis fan airflow-direction [ port-side-intake | port-side-exhaust ]
Parameters
port-side-intake
Specifies the airflow to enter the switch.
port-side-exhaust
Specifies the airflow to exit the switch.
Modes
Privileged EXEC mode
Usage Guidelines
This command must only be used after you purchase and install the appropriate fan/power supply that provides the desired
airflow direction in the switch. Please contact your Sales Representative to obtain the correct part numbers and pricing.
When the chassis fan airflow-direction command is issued, the switch will not recognize the configuration change until the
switch is rebooted.
Only one (1) configuration change is accepted per reboot. This means that even if this command is entered multiple times, only
the first configuration change entered will be effective after rebooting.
The switch serial number is registered with Extreme and the information recorded in the Extreme database about that switch
includes the airflow orientation at the time of shipment. Any subsequent change in airflow direction is not recorded in the
Extreme database. This means that if you request a Return Merchandise Authentication (RMA) for the switch, the replacement
switch will be sent with the original orientation.
Examples
To specify the fan airflow-direction:
cisco-interoperability
Configures the device to interoperate with some legacy Cisco switches.
Syntax
cisco-interoperability { disable | enable }
Command Default
Cisco interoperability is disabled.
Parameters
disable
Disables Cisco interoperability for the Multiple Spanning Tree Protocol (MSTP) device.
enable
Enables Cisco interoperability for the MSTP enabled device.
Modes
Protocol Spanning Tree MSTP mode
Usage Guidelines
For some devices, the MSTP field, Version 3 Length, does not adhere to the current standards.
If Cisco interoperability is required on any device in the network, then all devices in the network must be compatible, and
therefore enabled using this command for interoperability with a Cisco switch.
Examples
To enable Cisco interoperability on a device:
History
Release version Command history
class
Creates a class map in a policy map and enters the class map configuration mode.
Syntax
class class-mapname
no class class-mapname
Command Default
A policy map has been created. Two classes, "default" and "cee", cannot be created or deleted.
Parameters
class-mapname
The designated name for the class map.
Modes
Policy map configuration mode
Usage Guidelines
Use this command to configure a class map for a police policy map with QoS and policing parameters for inbound or outbound
traffic. The class map must have been created and associated with match criteria using the class-map command. (Refer to the
qos cos command.) When you launch the class command while in policy map configuration mode (refer to policy-map) for a
policy, the system is placed in "configure policy-map classification" (config-policymap-class) mode.
Each policy map can contain one class map. The police cir command is mandatory for configuring a class map.
Enter the no class class-mapname command to remove the class from the policy map.
Examples
This example configures a class-map called "default" within a policy-map.
History
Release version Command history
class-map
Enters class (classification) map configuration mode.
Syntax
class-map class-map-name
no class-map class-map-name
Command Default
The class map names "default" and "cee" are reserved and cannot be created by users.
Parameters
class-map-name
Name of classification map. The map name is restricted to 64 characters.
Modes
Global configuration mode.
Usage Guidelines
Enter no map class-mapclass-map-name while in global configuration mode to remove the classification map.
You can create up to 128 class maps.
Examples
To create a class map and place system into config-classmap mode:
History
Release version Command history
clear arp
Clears some or all Address Resolution Protocol (ARP) entries.
Syntax
clear arp [ ethernet slot / port | ip ip-address | ve ve-id ] [ no-refresh ] [ vrf vrf-name ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
ip ip-address
Specifies a next-hop IP address.
ve ve-id
Specifies a virtual ethernet (VE) interface.
no-refresh
Clears the ARP cache without resending ARP requests to the local hosts.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
If the no-refresh keyword is not included, ARP requests are automatically triggered for the cleared entries. To avoid this
triggering, include the no-refresh keyword.
Examples
The following example clears all ARP entries on the device.
History
Release version Command history
Syntax
clear bgp evpn neighbor { IPv4-address | IPv6-address | all } [ soft { in | out } | soft-outbound ]
Command Default
EVPN neighbors are not cleared.
Parameters
IPV4-address
Specifies an IPv4 address.
IPV6-address
Specifies an IPv6 address.
all
Specifies all addresses.
soft
Sends a route refresh or resends routes to the specified neighbor from the RIB-out table.
in
Sends a route refresh.
out
Resends routes to the specified neighbor from the RIB-out table.
soft-outbound
Modes
Privileged EXEC mode
Examples
To clear all IPv4 EVPN neighbors and send a route refresh:
History
Release version Command history
Syntax
clear bgp evpn routes { IPv4-address | IPv6-address | all }
Command Default
EVPN neighbors are not cleared.
Parameters
IPV4-address
Specifies an IPv4 address.
IPV6-address
Specifies an IPv6 address.
all
Specifies all addresses.
Modes
Privileged EXEC mode
Examples
To clear IPv4 EVPN routes and trigger running import rules on the routes received:
History
Release version Command history
Syntax
clear bgp evpn routes type igmp-join-sync|igmp-leave-sync
Parameters
igmp-join-sync
Clears the IGMP Join Sync routes from the EVPN routing table.
igmp-leave-sync
Clears the IGMP Leave Sync routes from the EVPN routing table.
Modes
Privileged EXEC mode
Examples
The following example clears the IGMP Join Sync routes from the EVPN routing table.
History
Release version Command history
clear counters
Clears the IP counter statistics on the device.
Syntax
clear counters all |[ interface { { ethernet0/port | fibrechannel 0/port | port-channel number | vlan vlan_id } ] slot0 ]
Parameters
all
Clears all IP counter statistics on the device or selected interface.
interface
Specifies an interface.
ethernet
Specifies a physical Ethernet interface.
0
Specifies a valid slot number. The only valid slot number is 0.
port
Specifies a valid port number.
fibrechannel
Specifies a fibrechannel interface.
0
Specifies a valid slot number. The only valid slot number is 0.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel. The number of available channels range from 1 through 6144.
slot 0
Specifies a valid slot id. The only valid slot number is 0.
Modes
Privileged EXEC mode
Examples
The following example clears all counter statistics.
History
Release version Command history
Syntax
clear counters access-list interface { ethernet 0 / port | port-channel index | vlan vlan_id } { in | out }
clear counters access-list { ip | ipv6 } acl-name interface { ethernet slot / port | port-channel index | ve vlan_id } { in | out }
clear counters access-list mac acl-name interface { ethernet slot / port | port-channel index | vlan vlan_id } { in | out }
Parameters
interface
Specifies an interface.
ethernet
Specifies a physical Ethernet interface.
0
Specifies a valid slot number. The only valid slot number is 0.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel. Available channels range from 1 through 6144.
in | out
Specifies the binding direction (incoming or outgoing).
vlan vlan_id
(Available only on Layer 2) Specifies a VLAN.
ve vlan_id
(Available only on Layer 3) Specifies a virtual Ethernet (VE) interface.
ip | ipv6 | mac
Specifies the network protocol.
global
Specifies Level 3 receive ACLs (rACLs), which are applied at device-level, rather than at interface-level.
mac acl-name
Specifies the MAC ACL name. To clear statistics on all counters of an ACL-type, do not specify acl-name.
in | out
Specifies the binding direction (incoming or outgoing).
Modes
Privileged EXEC mode
Examples
The following example clears ACL statistics on a specified Ethernet interface.
The following example clears ACL statistics for a specified MAC ACL on a specified Ethernet interface.
The following example clears ACL statistics for a specified MAC ACL on all interfaces on which this ACL is applied.
The following example clears ACL statistics for a specified IPv4 ACL on a specified interface.
The following example clears ACL statistics for a specified IPv4 ACL on all interfaces on which it is applied.
The following example clears incoming ACL statistics for a specified IPv6 ACL on a virtual Ethernet (VE) interface.
The following example clears receive-path ACL statistics for a specified IPv6 ACL.
History
Release version Command history
Syntax
clear counters link-fault-signaling [ all ]
clear counters link-fault-signaling interface ethernet slot / port { all | local | remote }
Parameters
all
Specifies local and remote LFS counters on all interfaces.
slot slot-num
Specifies a valid slot number. Must be 0 if the device does not contain slots.
interface ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the device does not contain slots.
port
Specifies a valid port number.
all
Specifies local and remote LFS counters.
local
Specifies local LFS counters only.
remote
Specifies remote LFS counters only.
Modes
Privileged EXEC mode
Examples
The following example clears local and remote LFS counters on all interfaces.
History
Release version Command history
Syntax
clear counters storm-control
Parameters
broadcast
Clears all BUM-related counters in the system for the broadcast traffic type.
multicast
Clears all BUM-related counters in the system for the multicast traffic type.
unknown-unicast
Clears all BUM-related counters in the system for the unknown-unicast traffic type.
interface ethernet 0/port
Clears all BUM-related counters in the system for the specified interface.
Modes
Privileged EXEC mode
Usage Guidelines
This command clears the counters for broadcast, unknown-unicast, and multicast traffic for the entire system, for specified
traffic types, for specified interfaces, or for specified traffic types on specified interfaces.
Examples
Clear counters for broadcast traffic on an Ethernet interface.
History
Release version Command history
Syntax
clear dot1x statistics [ interface ethernet slot/port ]
Parameters
interface ethernet slot/port
Causes clearing of all dot1x statistics for a specified interface port. When the switch does not contain slots, the slot
number must be 0.
Modes
Privileged EXEC mode
Examples
The following example clears accumulated dot1x port authentication statistics on all ports.
The following example clears all dot1x statistics for a specific Ethernet port (0/1).
History
Release version Command history
Syntax
clear ip arp inspection statistics
Modes
Privileged EXEC mode
Usage Guidelines
The capacity of each statistic counter is 64 bits, beyond which such a counter is reset to zero.
Examples
The following example clears DAI statistics for all DAI-enabled VLANs.
History
Release version Command history
Syntax
clear ip arp suppression-cache [ bridge-domain bridge-domain-id | vlan vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain. On SLX 9140, the range is from 1 through 4096. On SLX 9240, the range is from 1
through 3566.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Usage Guidelines
Running this command might impact traffic.
Examples
The following example clears the ARP-suppression cache.
History
Release version Command history
Syntax
clear ip arp suppression-statistics [ bridge-domain bridge-domain-id | vlan vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain. On SLX 9140, the range is from 1 through 4096. On SLX 9240, the range is from 1
through 3566.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example clears all ARP-suppression statistics.
History
Release version Command history
Syntax
clear ip bgp dampening [ ip-addr { / mask } ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
IPv4 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example unsuppresses all suppressed BGP4 routes.
The following example unsuppresses suppressed BGP4 routes for VRF "red".
History
Release version Command history
Syntax
clear ip bgp flap-statistics [ ip-addr { / mask } | neighbor ip-addr | regular-expression string ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
IPv4 mask of a specified route in CIDR notation.
neighbor
Clears dampening statistics only for routes learned from the specified neighbor.
ip-addr
IPv4 address of the neighbor.
regular-expression
Specifies a regular expression.
string
Regular expression.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears the dampening statistics for a BGP4 route.
The following example clears the dampening statistics for a BGP4 route for VRF "red".
History
Release version Command history
Syntax
clear ip bgp local routes [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears all BGP4 local routes.
The following example clears BGP4 local routes for VRF "red".
History
Release version Command history
Syntax
clear ip bgp neighbor { all | as-num | ip-addr | peer-group-name } [ last-packet-with-error | notification-errors | soft [ in
[ prefix-filter] | out ] | soft-outbound | traffic ] [ vrf vrf-name ]
Parameters
all
Resets and clears all BGP4 connections to all neighbors.
as-num
Clears all BGP4 connections within this autonomous system. Range is from 1 through 4294967295.
ip-addr
Clears all BGP4 connections with this IPv4 address, in dotted-decimal notation.
peer-group-name
Clears all BGP4 connections in this peer group. Range is from 1 through 63 characters.
last-packet-with-error
Clears all BGP4 connections identified as having the last packet received with an error.
notification-errors
Clears all BGP4 connections identified as having notification errors.
soft
Refreshes routes received from or sent to the neighbor.
in
Refreshes received routes.
prefix-filter
Refreshes Outbound Route Filters (ORFs) that are prefix-based.
out
Refreshes sent routes.
soft-outbound
Refreshes all outbound routes by applying new or changed filters, but sends only the existing routes affected by the
new or changed filters to the neighbor.
NOTE
Use soft-outbound only if the outbound policy is changed. This operand updates all outbound routes by applying the
new or changed filters. However, the device sends to the neighbor only the existing routes that are affected by the new
or changed filters. The soft out operand updates all outbound routes and then sends the entire BGP4 route table on
the device to the neighbor after the device changes or excludes the routes affected by the filters.
traffic
Clears the counters (resets them to 0) for BGP4 messages.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example refreshes all BGP4 neighbor connections.
The following example refreshes all BGP4 neighbor connections for VRF "red".
History
Release version Command history
Syntax
clear ip bgp routes [ ip-addr [ / mask ] ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
IPv4 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of the VRF instance to associate with subsequent address-family configuration mode commands.
Modes
Privileged EXEC mode
Examples
The following example clears all BGP4 routes.
The following example clears BGP4 routes for VRF instance "red":
History
Release version Command history
Syntax
clear ip bgp traffic [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears the BGP4 message counters.
History
Release version Command history
Syntax
clear ip dhcp relay statistics ip-address ip-address
Command Default
DHCP relay statistics are present on the DHCP server.
Parameters
ip-address ip-address
IPv4 address of DHCP server where client requests are to be forwarded.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to clear IP DHCP Relay statistics for a specific IP DHCP Relay address or all addresses on the device.
Examples
The following example clears statistics for IP DHCP Relay.
History
Release version Command history
Syntax
clear ip igmp groups [vlan vlan-id | {cluster [id ] }| client client-id } ]
Parameters
vlanvlan-id
Specifies a VLAN.
cluster [id]
Specifies the cluster or optionally the cluster ID to clear all groups learned through MCT on the MCT cluster.
client id
Specifies the cluster client ID to clear all groups learned on the Cluster Client Edge Port (CCEP).
Modes
Privileged EXEC mode
Examples
To clear information for all groups in the IGMP protocol:
To clear information for all IGMP routes learned over the MCT cluster:
History
Release version Command history
Syntax
clear ip igmp statistics [ vlan vlan-id ]
Parameters
vlanvlan-id
Specifies a VLAN.
Modes
Privileged EXEC mode
Examples
The following example clears statistics information for a VLAN in the IGMP protocol.
History
Release version Command history
clear ip ospf
Clears OSPF data processes, counters, neighbors, or routes.
Syntax
clear ip ospf all [ vrf vrf-name ]
clear ip ospf counters { all | ethernet slot/port | loopback number | ve vlan_id } [ vrf vrf-name ]
Parameters
all
Clears all OSPF data processes.
vrf vrf-name
Specifies a VRF.
counters
Clears OSPF counters.
all
Clears all counters.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
neighbor
Clears specified neighbors.
ip-addr
Specifies the IP address of the neighbor.
all
Clears all neighbors.
routes
Clears matching routes or clears all routes.
ip-addr/mask
Clears all routes that match the prefix and mask that you specify.
all
Clears all routes.
Modes
Privileged EXEC mode
Examples
The following example restarts the OSPF processes.
History
Release version Command history
clear ip route
Clears a specified route or all IP routes in the IP routing tables.
Syntax
clear ip route { all | [ slot 0 [ vrf vrf-name ] ] }
Parameters
all
Removes all IPv4 routes.
vrf vrf-name
Removes IPv4 routes for the specified VPN Routing and Forwarding (VRF) instance.
slot 0
Removes Clear IP route on slot ID (LP only) . The only valid slot number is 0.
Modes
Privileged EXEC mode
Examples
The following example clears the IP route specified by IP address 192.158.1.0/24.
History
Release version Command history
Syntax
clear ipv6 bgp dampening [ ipv6-addr { / mask } ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
IPv6 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example unsuppresses all suppressed BGP4+ routes.
The following example unsuppresses suppressed BGP4+ routes for VRF "red".
History
Release version Command history
Syntax
clear ipv6 bgp flap-statistics [ ipv6-addr { / mask } | neighbor ipv6-addr | regular-expression string ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
IPv6 mask of a specified route in CIDR notation.
neighbor
Clears route-flap statistics only for routes learned from the specified neighbor.
ipv6-addr
IPv6 address of the neighbor.
regular-expression
Specifies a regular expression.
string
Regular expression.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears all dampening statistics for a BGP4+ route.
The following example clears the dampening statistics for a BGP4+ route for VRF "red".
History
Release version Command history
Syntax
clear ipv6 bgp local routes [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears all BGP4+ local routes.
The following example clears BGP4+ local routes for VRF "red".
History
Release version Command history
Syntax
clear ipv6 bgp neighbor [ all | as-num | peer-group-name | ipv6-addr ] [ last-packet-with-error | notification-errors | soft [ in
[ prefix-filter ] | out ] | soft-outbound | traffic ] [ vrf vrfname ]
Parameters
all
Resets and clears all BGP4+ connections to all neighbors.
as-num
Clears all BGP4+ connections within this autonomous system. Range is from 1 through 4294967295.
peer-group-name
Clears all BGP4+ connections in this peer group. Range is from 1 through 63 characters.
ipv6-addr
Clears all BGP4+ connections with this IPv6 address, in dotted-decimal notation.
last-packet-with-error
Clears all BGP4+ connections identified as having the last packet received with an error.
notification-errors
Clears all BGP4+ connections identified as having notification errors.
soft
Refreshes routes received from or sent to the neighbor.
in
Refreshes received routes.
prefix-filter
Refreshes Outbound Route Filters (ORFs) that are prefix-based.
out
Refreshes sent routes.
soft-outbound
Refreshes all outbound routes by applying new or changed filters, but sends only the existing routes affected by the
new or changed filters to the neighbor.
NOTE
Use soft-outbound only if the outbound policy is changed. This operand updates all outbound routes by applying the
new or changed filters. However, the device sends to the neighbor only the existing routes that are affected by the new
or changed filters. The soft out operand updates all outbound routes and then sends the entire BGP4+ route table on
the device to the neighbor after the device changes or excludes the routes affected by the filters.
traffic
Clears the counters (resets them to 0) for BGP4+ messages.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example refreshes all BGP4+ neighbor connections.
The following example resets all the counters for BGP4+ messages.
The following example clears BGP4+ connections with a specified peer group.
The following example clears BGP4+ connections with a specified peer group for VRF "red".
History
Release version Command history
Syntax
clear ipv6 bgp routes [ ipv6-addr [ / mask ] ] [ vrf vrfname ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
IPv6 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears specific BGP4+ routes.
The following example clears specific BGP4+ routes for VRF "red".
History
Release version Command history
Syntax
clear ipv6 bgp traffic [ vrf vrf-name ]
Modes
Privileged EXEC mode
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Examples
The following example clears all BGP4+ message counters.
The following example clears BGP4+ message counters for VRF "red".
History
Release version Command history
Syntax
clear ipv6 counters [ all | interface { ethernet slot/port | loopback port-number | ve ve-id }
Parameters
all
Specifies all interfaces.
interface
Specifies interface.
ethernet
Represents a valid, physical Ethernet subtype.
slot
Specifies a valid slot number as 0.
port
Specifies a valid port number.
loopback
Specifies a loopback interface.
port-number
Port number of the loopback interface. The range is from 1 through 255.
ve
Specifies a virtual Ethernet (VE) interface.
ve_id
ID of the VE interface. The range is from 1 through 4096.
Modes
Privileged EXEC mode
Examples
The following example clears counters on Ethernet interface 0/1.
History
Release version Command history
Syntax
clear ipv6 dhcp relay statistics ip-address ip-address
Command Default
DHCP relay statistics are present on the DHCP server.
Parameters
ip-address ip-address
IPv6 address of DHCP server where client requests are to be forwarded.
Modes
Privileged EXEC mode
Examples
Clear all the DHCP Relay statistics on the device.
History
Release version Command history
Syntax
clear ipv6 mld groups vlan vlan-id
Parameters
vlanvlan-id
Specifies the VLAN ID.
Modes
Privileged EXEC mode
Examples
To clear IPv6 MLDv1 groups for a specific VLAN:
History
Release version Command history
Syntax
clear ipv6 mld statistics vlan vlan-id
Parameters
vlanvlan-id
Specifies the VLAN ID.
Modes
Privileged EXEC mode
Examples
To clear IPv6 MLDv1 snooping statistics for a specific VLAN:
History
Release version Command history
Syntax
clear ipv6 nd suppression-cache [ bridge-domain bridge-domain-id | vlan vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain. On SLX 9140, the range is from 1 through 4096. On SLX 9240, the range is from 1
through 3566.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example clears the ND-suppression cache.
History
Release version Command history
Syntax
clear ipv6 nd suppression-statistics [ bridge-domain bridge-domain-id | vlan vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain. On SLX 9140, the range is from 1 through 4096. On SLX 9240, the range is from 1
through 3566.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example clears all ND-suppression statistics.
History
Release version Command history
Syntax
clear ipv6 neighbor [ ipv6-address ] [ ethernet slot/port | ve ve-number ] [ force-delete | no-refresh | vrf vrf-name ]
Parameters
ipv6-address
Removes cache entries for the specified IPv6 address.
ethernet slot/port
Removes neighbor entries for the Ethernet interface. A valid slot number is 0.
ve ve-number
Removes neighbor entries for the the specified Virtual Ethernet (VE) interface.
force-delete
Force deletes all the dynamic neighbor entries.
no-refresh
Deletes all the dynamic neighbor entries.
vrf vrf-name
Removes entries from the IPv6 neighbor table for the specified VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
You must specify the ipv6-address parameter in hexadecimal using 16-bit values between colons as documented in RFC
2373.
Examples
The following example removes neighbor entries for Ethernet interface 0/1.
History
Release version Command history
Syntax
clear ipv6 ospf all [ vrf vrf-name ]
clear ipv6 ospf counts neighbor interface { ethernet slot/port | loopback number | ve vlan_id } [ A.B.C.D ]
clear ipv6 ospf neighbor interface { ethernet slot/port | loopback number | ve vlan_id } [ A.B.C.D ]
Parameters
all
Clears all OSPFv3 data.
counts
Clears OSPFv3 counters.
neighbor
Clears all OSPF counters for a specified neighbor.
A.B.C.D
Specifies a neighbor.
vrf vrf-name
Specifies a VRF.
interface
Specifies an interface.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
force-spf
Performs the shortest path first (SPF) calculation without clearing the OSPFv3 database.
redistribution
Clears OSPFv3 redistributed routes.
traffic
Clears OSPFv3 traffic statistics.
routes
Clears OSPFv3 routes.
ipv6-addr
Specifies an IPv6 address.
Modes
Privileged EXEC mode
Usage Guidelines
Use the force-spf keyword to perform the shortest path first (SPF) calculation without clearing the OSPFv3 database.
Examples
The following example restarts the OSPFv3 processes.
The following example clears all OSPFv3 counters for a specified neighbor.
History
Release version Command history
Syntax
clear ipv6 route [ ipv6-address vrf vrf-name ] [ all vrf vrf-name ] [ slot slot-number ]
Parameters
ipv6-address
Removes IPv6 routes for the specified IPv6 address.
vrf vrf-name
Removes IPv6 routes for the specified VPN Routing and Forwarding (VRF) instance.
all
Removes all IPv6 routes.
slot slot-number
Removes IPv6 routes for the specified slot. The valid slot number is 0.
Modes
Privileged EXEC mode
Examples
The following example clears IPv6 routes associated with the prefix 2000:7838::/32.
History
Release version Command history
Syntax
clear ipv6 vrrp statistics [ all ]
Parameters
all
Clears all IPv6 VRRP statistics.
interface
Specifies an interface.
ve vlan_id
Specifies the VE VLAN number. The range is from 1 through 4096.
session VRID
Specifies the virtual group ID on which to clear statistics. The range is from 1 through 128.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported in IPv6 VRRPv3 and VRRP-E-v3.
Examples
The following example clears all IPv6 VRRPv3 statistics for all virtual groups.
The following example clears statistics for an IPv6 VRRPv3 session of virtual group 25.
The following example clears IPv6 VRRPv3 statistics on a specified virtual Ethernet interface.
History
Release version Command history
clear lacp
Clears the Link Aggregation Group Control Protocol (LACP) counters on a specific port-channel.
Syntax
clear lacp number counters
Parameters
number
Specifies the port channel-group number. Valid values range from 1 through 6144.
counters
Clears traffic counters.
Modes
Privileged EXEC mode
Examples
To clear the LACP counters for a specific port-channel:
History
Release version Command history
Syntax
clear lacp counters
Modes
Privileged EXEC mode
Examples
To clear the counters for all port-channels:
History
Release version Command history
Syntax
clear lldp neighbors [ interface ethernet slot/port ]
Parameters
interface ethernet
Use this parameter to specify an Ethernet interface, followed by the slot or port number.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, this command clears the LLDP neighbor information received on all the interfaces.
Examples
To clear the LLDP neighbor information for all interfaces:
History
Release version Command history
Syntax
clear lldp statistics [ interface ethernet slot/port ]
Parameters
interface ethernet
Use this parameter to specify an Ethernet interface, followed by the slot or port number.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, this command clears all the LLDP statistics on all interfaces.
Examples
To clear all the LLDP statistics for all interfaces:
History
Release version Command history
clear mac-address-table
Removes interface entries from the MAC address table.
Syntax
clear mac-address-table cluster [ cluster-id [client client-id ] ]
Parameters
cluster cluster-id
Specifies clearing MAC addresses from an MCT cluster ID. The ID range is 1-65535.
client client-id
Specifies clearing the client instance. The ID range is 1-512.
dynamic
Specifies the clearing of the specified MAC address, interface,
address MAC-address
Specifies clearing the dynamic MAC address. The valid format is H.H.H (available in Privileged EXEC mode only).
bridge-domain
Specifies clearing MAC addresses learned under bridge domains or a specified bridge-domain identifier.
interface
Specifies the clearing of the specified interface.
ethernet 0/port
Specifies clearing the Ethernet interface with a valid port number.
port-channel number
Specifies clearing the port channel interface number. The range is from 1-1024 based on the platform.
vlan vlan id
Specifies clearing the VLAN interface. The VLAN ID range is from 1-4090.
Modes
Privileged EXEC mode
Usage Guidelines
When a bridge-domain identifier is not specified, MAC addresses learned under all bridge domains are removed from the MAC
address table. If a specific address is not specified, all dynamic mac-addresses are deleted from the MAC address table.
Examples
The following example shows how to clear MAC addresses learned under bridge domain 1 from the MAC address table.
The following example shows how to clear MAC addresses learned from vlan 1 from the MAC address table.
History
Release version Command history
clear policy-map-counters
Provides a mechanism for clearing the policy map counters.
Syntax
clear policy-map-counters system [ map-name ]
Parameters
system map-name
Specifies the map name for the system statistics.
interface
Specifies an interface.
ethernet
Represents a valid, physical Ethernet type for all available Ethernet speeds.
0/port
Specifies a port number (this switch does not support a slot number, so "0" is used.).
port-channel channel-number
Represents a port channel.
in
Specifies clearing the ingress counters.
out
Specifies clearing the egress counters.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command with a specific interface and direction to clear the policy map counters for that interface.
Use this command without identifying an interface and direction of traffic to clear all of the policy map counters.
Examples
To clear the policy map counters for a specific interface use the following command:
History
Release version Command history
Syntax
clear ptp counter interface [ interface ]
Parameters
interface
Name of a PTP-enabled interface.
Modes
Privileged EXEC mode
Usage Guidelines
If no interface is specified, counters are cleared on all PTP-enabled interfaces on the switch.
Examples
To clear counters on all PTP-enabled interfaces on the switch:
History
Release version Command history
Syntax
clear spanning-tree counter [ interface { ethernet slot/port | port-channel number }
Parameters
interface
Specifies an interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel. The number of available channels ranges from 1 through 6144.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, spanning-tree counters are cleared for all interfaces.
Examples
To clear spanning-tree counters for all interfaces:
History
Release version Command history
Syntax
clear spanning-tree detected-protocols [ interface { ethernet slot/port | port-channel number }
Parameters
interface
Specifies an interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel. The number of available channels ranges from 1 through 6144.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, spanning-tree detected protocols are cleared for all interfaces.
Examples
To clear detected protocols on all interfaces:
History
Release version Command history
Syntax
clear statistics bridge-domain bd-id
Parameters
bd-id
The bridge domain ID.
Command Default
Statistics are disabled.
Modes
Privileged EXEC mode
Usage Guidelines
This command is also available in global configuration mode.
The clear statistics bridge-domain bd-id command clears the statistics for all the logical interfaces on a specific bridge domain.
Examples
The following example shows how to clear the statistics for all the logical interfaces on all bridge domains.
The following example shows how to clear the statistics for all the logical interfaces on bridge domain 2.
History
Release version Command history
Syntax
clear statistics vlan vlan-id
Parameters
vlan-id
The specific VLAN ID.
Command Default
Statistics are disabled.
Modes
Privileged EXEC mode
Usage Guidelines
This command is also available in global configuration mode.
The clear statistics vlan vlan-id command clears the statistics for all the ports and port channels on the given VLAN.
Examples
The following example shows how to clear the statistics for all the ports and port channels on the given VLAN.
The following example shows how to clear the statistics for all the ports and port channels on VLAN 10.
History
Release version Command history
Syntax
clear tunnel statistics tunnel-id
Parameters
tunnel-id
Specifies the tunnel ID.
mode
Specifies the tunnel ID.
gre
Specifies GRE tunnels.
vxlan
Specifies VXLAN tunnels.
overlay-gateway overlay-gateway-name
Filters by Overlay gateway name.
Modes
Privileged EXEC mode
Examples
This example removes statistics from a tunnel interface.
History
Release version Command history
Syntax
clear vrrp statistics
Parameters
interface
Specifies an interface.
ve vlan_id
Specifies the VE VLAN number. The range is from 1 through 6144.
session VRID
Specifies the virtual group ID on which to clear statistics. The range is from 1 through 255.
Modes
Privileged EXEC mode
Usage Guidelines
This command clears VRRP session statistics for all virtual groups, for a specified interface or for a specified virtual group.
This command is for VRRP and VRRP-E. VRRP-E supports only the ve vlan_id interface type.
To clear all vrrp statistics, use the clear vrrp statistics command with no operands.
Examples
The following example clears all VRRP statistics for all virtual groups.
The following example clears statistics for a session for a VRRP virtual group called "vrrp-group-25".
The following example clears VRRP statistics on a specified virtual Ethernet (VE) interface.
History
Release version Command history
CLI
In a Python shell, runs a device CLI command or series of commands. You can also assign the output of such commands to a
Python object.
Syntax
CLI (' device-CLI-command ' [ \n ' device-CLI-command ' ] [ [ do_print = ] { True | False } ] )
Parameters
device-CLI-command
An SLX-OS CLI command. You separate additional commands with \n.
do_print =
Specify whether or not to print the output of device-CLI-command to the default device. The default is to print the
output.
True
Print the output.
False
Do not print the output.
Modes
Python command shell
Usage Guidelines
Divergences between Extreme CLI syntax and Python syntax include the following differences:
• Although in general, Extreme CLI syntax is not case-sensitive, our convention is to use lower-case.
• Python syntax is case sensitive. Regarding the syntax documented in the current topic, note the following:
– The syntax of the command is upper case (CLI) and not lower case (cli).
– The syntax of the do_print = options is to capitalize the first letter: { True | False }
In Python, double quotes (") and single quotes (') are equivalent.
There is a difference between running a sequence of SLX-OS CLI commands in the Python shell rather than in the standard
SLX-OS interface. Whereas in the standard interface the result of a command is persistent, in the Python shell each CLI( )
statement is independent of any preceding ones.
For support of the CLI( ) command, although a Python script must include a from CLI import CLI statement, this
statement is automatically implemented when launching the Python interpreter interactively.
Within a script or interactive session, if you assign an Extreme CLI command or series of commands to a Python variable, you
can then append the following functions to the variable:
• .rerun()—updates the variable from a new run of the CLI command or series of commands.
device# python
Python 3.3.2 (default, Apr 11 2014, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_show_running_ve = CLI('show running-config interface ve')
!Command: show running-config interface ve
!Time: Mon Aug 22 16:53:13 2016
% No entries found.
# The SLX-OS show running-config interface ve command is run,
# and that command is assigned to the Python variable cmd_show_running_ve.
>>> cmd_show_running_ve.rerun()
# The rerun() function appended to cmd_show_running_ve gives the following output:
!Command: show running-config interface ve
!Time: Mon Aug 22 16:53:13 2016
interface Ve 101
shutdown
!
interface Ve 102
shutdown
!
interface Ve 103
shutdown
!
!
• .get_output()—returns the value of a new run of the CLI command or series of commands, as a list.
print("SLOT_FIRMWARE:\n")
for key in slot_firmware:
print("\t", key, "\t=> ", slot_firmware[key])
Examples
The following example launches the Python shell and then both assigns a series of CLI configuration commands to a Python
variable and runs those commands.
device# python
Python 3.3.2 (default, Apr 11 2014, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_config_ve = CLI('configure \n interface ve 101-103')
!Command: configure
interface ve 101-103
!Time: Mon Aug 22 16:57:36 2016
>>>
The following example launches the Python shell and then both assigns a CLI operational command to a Python variable and
runs that command.
device# python
Python 3.3.2 (default, Apr 11 2014, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_reload_system = CLI('reload system \n y')
History
Release version Command history
client
Configures a Multi-Chassis Trunking (MCT) client for a cluster and access cluster client configuration mode.
Syntax
client client-name client-id
Parameters
client-name
Specifies the client name as an ASCII string. The name can be up to 64 characters in length.
client-id
Specifies the cluster client ID. The ID value range can be from 1 through 65535.
Modes
Cluster client configuration mode
Usage Guidelines
The no form of the command removes the client from the MCT cluster configuration.
Examples
The following example configures a cluster client.
History
Release version Command history
client-interface
Configures a client interface to the cluster client instance.
Syntax
client-interface { ethernet 0/port | port-channel number }
no client-interface
Parameters
ethernet 0/port
Configures the specified Ethernet port as the client interface.
port-channel number
Configures the specified port channel as the client interface. The port channel number specifies the LAG ID.
Modes
Cluster client configuration mode
Usage Guidelines
The no form of the command removes the client interface.
The same client interface cannot be added under multiple client entries.
A client interface is not allowed to be updated when the client is in deploy state. It needs to be removed first before adding a
new interface.
Examples
The following example shows how to configure a client interface.
History
Release version Command history
client-interfaces-shutdown
Disables the local client interfaces administratively in the cluster to moves all the traffic on the device to remote MCT peer
device, resulting in fail-over of traffic to the peer device.
Syntax
client-interfaces-shutdown
no client-interfaces-shutdown
Modes
Cluster configuration mode
Usage Guidelines
The no form of the command reenables the local client interfaces.
Examples
The following example shows the disabling of all the client interfaces in the cluster.
History
Release version Command history
client-isolation-strict
Sets the client-isolation mode to strict when the EVPN control session goes down between the MCT devices for Broadcast,
Unknown unicast and Multicast (BUM) handling over client interfaces.
Syntax
client-isolation-strict
no client-isolation-strict
Command Default
By default, client-isolation mode is loose.
Modes
Cluster configuration mode
Usage Guidelines
In strict mode, when the EVPN control session goes down, the interfaces on both the cluster devices are ports are not down.
None of the ports are made DF. There is no impact to unicast traffic. However, only BUM forwarding is not done. In strict mode,
the client is completely isolated from the network if the control session is not operational.
MCT cluster devices can operate in two modes. Both peer devices must be configured with the same mode configuration.
NOTE
The CLI allows modification of the client isolation mode on MCT cluster devices even when the cluster is deployed.
You must have the same isolation mode configuration on both cluster devices.
The no form of the command resets the default client isolation mode of loose.
Examples
The following example shows how to configure strict client-isolation mode.
History
Release version Command history
client-to-client-reflection
Enables routes from one Route Reflector (RR) client to be reflected to other clients by the host device on which it is configured.
Syntax
client-to-client-reflection
no client-to-client-reflection
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
When this command is used, the host device on which it is configured becomes the route-reflector server.
The no form of the command disables route reflection between clients.
Examples
The following example configures client-to-client reflection on the BGP host device for the IPv4 unicast address-family.
The following example disables client-to-client reflection on the BGP host device for the IPv6 unicast address-family.
History
Release version Command history
clock set
Sets the local clock time and date.
Syntax
clock set hh:mm:ss mm-dd-yy/yyyy
Parameters
hh:mm:ss
Specifies the local clock time in hours, minutes, and seconds.
mm-dd-yy/yyyy
Specifies the local clock date in month, day, and year format. Year may be specified with two or four numbers.
Modes
Privileged EXEC mode
Usage Guidelines
Valid date and time settings range from January 1, 1970 to December 31, 2035.
An active NTP server, if configured, automatically updates and overrides the local clock time.
Examples
The following example sets the time and date to 31 minutes past 4pm in the afternoon on July 28, 2016, for the local device:
History
Release version Command history
clock timezone
Sets the device system clock time zone options using a valid timezone region and city.
Syntax
clock timezone { timezone-region / city }
no clock timezone
Parameters
timezone-region/city
Specifies a timezone region and city.
Modes
Global configuration mode
Examples
The following example sets the system date and time to New York (Eastern) time.
History
Release version Command history
cluster
Configures a Multi-Chassis Trunking (MCT) cluster and accesses the cluster configuration mode.
Syntax
cluster cluster-name cluster-id
Parameters
cluster-name
Specifies the cluster name as an ASCII string. The cluster name can be up to 64 characters in length.
cluster-id
Specifies the cluster ID. The ID value range can be from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
NOTE
The cluster-id variable must be the same on both cluster devices.
Examples
The following example configures an MCT cluster.
History
Release version Command history
Syntax
cluster management node-id node_ID ]
Command Default
The default node ID is 1.
Parameters
node_ID
The node ID. Range is 1 through 255. Default is 1.
Modes
Privileged EXEC mode
Usage Guidelines
Use the no form of this command to revert to the default node ID.
Two nodes in a management cluster cannot have the same node ID.
The node ID persists after the execution of the copy default-config startup-config command and database corruption.
Examples
The following example changes the node ID to a nondefault value.
History
Release version Command history
Syntax
cluster management virtual { ip address ipv4_address/prefix_len inband interface veVE_number | ipv6 address
ipv6_address/prefix_len }
Parameters
ip address ipv4_address/prefix_len
Specifies the IPv4 address and prefix length means of a CIDR prefix (mask).
Modes
Global configuration mode
Usage Guidelines
When you configure the virtual IPv4 or IPv6 address for the first time, the address is assigned to the principal switch. You can
then access the principal switch through the management port IP address or the virtual IP address. The virtual IP configuration
is global in nature. All the nodes in the fabric will be configured with the same virtual IP address, but the address is always bound
to the current principal switch.
This command can be used only after the fabric has formed successfully.
The command can be executed from any node. You can remove a virtual IP address when you are logged on to the switch
through the virtual IP address. Use the management port IP address or the serial console to configure the virtual IP address.
The inband interface veparameter can only be used when assigning an IPv4 address. This parameter is not applicable for IPv6
addresses.
It is the responsibility of the network administrator to ensure that the virtual IP address assigned is not a duplicate of an address
assigned to any other management port in the fabric.
The virtual IP address should be configured on the same subnet as the management interface IP address.
Enter no cluster management virtual ip address or no cluster management virtual ipv6 address to remove a currently
configured virtual IPv4 or IPv6 address, respectively.
Examples
The following example assigns a virtual IPv4 address and mask to the principal switch and specify a VE interface.
The following example removes the currently configured virtual IPv4 address.
The following example assigns a virtual IPv6 address and mask to the principal switch.
History
Release version Command history
cluster-control-vlan
Configures the cluster control VLAN.
Syntax
cluster-control-vlan VLAN_ID
no cluster-control-vlan
Command Default
By default, the cluster control VLAN is 4090.
Parameters
VLAN_ID
Specifies the VLAN ID. Enter an integer from 1 through 4090.
Modes
Cluster configuration mode
Usage Guidelines
Use the no form of this command to reset the VLAN to the default value of 4090.
The cluster control VLAN is required for MAC learning, resolving ARP for the BGP peer, and to derive the outer MAC address
for the NSH tunnel.
If MCT is configured, other switch ports must not be part of the cluster control VLAN.
You cannot configure the cluster control VLAN when the cluster is deployed.
Examples
The following example configures the cluster control VLAN of 35.
History
Release version Command history
cluster-id
Configures a cluster ID for the route reflector.
Syntax
cluster-id { num | ip-addr }
Command Default
The default cluster ID is the device ID.
Parameters
num
Integer value for cluster ID. Range is from 1 through 65535.
ip-addr
IPv4 address in dotted-decimal notation.
Modes
BGP configuration mode
Usage Guidelines
When configuring multiple route reflectors in a cluster, use the same cluster ID to avoid loops within the cluster.
The no form of the command restores the default so that the cluster ID is the device ID.
Examples
The following example configures a cluster ID for the route reflector.
History
Release version Command history
cluster-system-id
Configures the last byte of the bridge ID to ensure that two or more MCT clusters do not have the same bridge IDs in a Layer 2
topology.
Syntax
cluster-system-id last-byte
Parameters
last-byte
Specifies the last byte of the bridge ID. Enter an integer from 1 to 255.
Modes
Spanning tree configuration mode
Usage Guidelines
The bridge ID (Switch MAC) used by all nodes participating in the STP domain should have unique MAC address.
Ensure that the global STP configuration is consistent on both cluster nodes. Configuration mismatch handling is not
supported.
Examples
The following example configures the last byte of the bridge ID to 2.
History
Release version Command history
compare-med-empty-aspath
Enables comparison of Multi-Exit Discriminators (MEDs) for internal routes that originate within the local autonomous system
(AS) or confederation.
Syntax
compare-med-empty-aspath
no compare-med-empty-aspath
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the default so that the device does not compare MEDs for internal routes that originate
within the local AS or confederation.
Examples
The following example configures the device to compare MEDs.
History
Release version Command history
compare-routerid
Enables comparison of device IDs, so that the path-comparison algorithm compares the device IDs of neighbors that sent
otherwise equal-length paths.
Syntax
compare-routerid
no compare-routerid
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disables the comparison of device IDs.
Examples
The following example configures the device always to compare device IDs.
History
Release version Command history
confederation identifier
Configures a BGP confederation identifier.
Syntax
confederation identifier autonomous-system number
no confederation identifier
Command Default
No BGP confederation identifier is identified.
Parameters
autonomous-system number
Specifies an autonomous system number (ASN). The configurable range of values is from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
Use this command to configure a single AS number to identify a group of smaller autonomous systems as a single
confederation.
Examples
The following example specifies that confederation 65220 belongs to autonomous system 100.
History
Release version Command history
confederation peers
Configures subautonomous systems to belong to a single confederation.
Syntax
confederation peers autonomous-system number [ …autonomous-system number ]
no confederation peers
Command Default
No BGP peers are configured to be members of a BGP confederation.
Parameters
autonomous-system number
Autonomous system (AS) numbers for BGP peers that will belong to the confederation. The configurable range of
values is from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes an autonomous system from the confederation.
Examples
The following example configures autonomous systems 65520, 65521, and 65522 to belong to a single confederation under
the identifier 100.
History
Release version Command history
configure terminal
Enters global configuration mode.
Syntax
configure terminal
Modes
Privileged EXEC mode
History
Release version Command history
connector
Accesses connector configuration mode for the Ethernet port.
Syntax
connector slot/port
Parameters
slot/port
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
Modes
Hardware configuration mode
Usage Guidelines
In connector configuration mode, you can break out the port into four 10G ports.
Examples
The following example shows the accessing of the connector configuration mode.
History
Release version Command history
continue
Configures a route-map instance number that goes in a continue statement in a route-map instance.
Syntax
continue number
no continue number
Parameters
number
Route-map instance number. Range is from 1 through 4294967295.
Modes
Global configuration mode
Usage Guidelines
Use the no continue number command to disable the instance number.
Examples
Typical command example:
History
Release version Command history
copy
Copies configuration data.
Syntax
copy source_file destination_file
Parameters
source_file
The source file to be copied. Specify one of the following parameters:
default-config
The default configuration.
default-profile
The default profile configuration.
flash://filename
A file in the local flash memory.
ftp://username:password@host_ip_address/path
A file on a remote host. Transfer protocol is FTP.
running-config
The running configuration.
scp://username:password@host_ip_address/path
A file on a remote host. Transfer protocol is SCP.
sftp://username:password@host_ip_address/path
A file on a remote host. Transfer protocol is SFTP.
startup-config
The startup configuration.
support
The support data.
support-interactive
The interactive mode.
tftp://username:password@host_ip_address/path
A file on a remote host. Transfer protocol is TFTP.
usb://path
A file on an attached USB device.
user-defined-profilepath
The user defined profile configuration.
destination_file
The destination file. Specify one of the following parameters:
default-config
The default configuration.
flash://filename
A file in the local flash memory.
ftp://username:password@host_ip_address//path
A file on a remote host. Transfer protocol is FTP.
scp://username:password@host_ip_address//path
A file on a remote host. Transfer protocol is SCP.
sftp://username:password@host_ip_address/path
A file on a remote host. Transfer protocol is SFTP.
startup-config
The startup configuration.
tftp://username:password@host_ip_address/path
A file on a remote host. Transfer protocol is TFTP.
usb://path
A file on an attached USB device.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to back up and restore configuration files with various protocols.
The special characters of dollar sign "$" and exclamation point "!" can be used as part of the password variable, provided they
are paired with the correct escape characters. The "$" must be paired with two backslashes "\\". For example, if your password
choice was "$password" on a remote server, you must use "username:\\$password@1.1.1.1" for the copy command. The
exclamation point must be paired with a single backslash in the copy command, such as "username:\!password@1.1.1.1".
Examples
To save the running configuration to a file:
To overwrite the startup configuration with a configuration file saved on an attached USB device:
History
Release version Command history
crypto ca authenticate
Downloads the certification authority (CA) certificate for a trustpoint from a remote certificate server for authentication purposes.
Syntax
crypto ca authenticate trustpointCA_name { directory remote_dir_name | file cert_file | host host_address | password
host_user_password | protocol { FTP | SCP } | user host_login }
Parameters
trustpointCA_name
Specifies a trustpoint name. The trustpoint name can range from 1 through 64 characters in length.
directory remote_dir_name
Specifies the directory where the certification file resides.
file cert_file
Specifies the name of the certification file in Privacy Enhanced Mail (PEM) format.
host host_address
Specifies the remote certificate server in hostname or IP address format.
password host_user_password
Specifies the password for the user name on the host server.
NOTE
For security purposes, it is recommended that the password is not listed in the command line; the user will be
prompted to enter the password.
protocol
Specifies the protocol for accessing the certification file.
FTP
Specifies using File Transfer Protocol.
SCP
Specifies using Secure Copy Protocol.
user host_login
Specifies the user name for login to the host server.
Modes
Privileged EXEC mode
Usage Guidelines
The CA certificate downloaded from the trusted CA is used to sign the certificate signing request (CSR) and generate the
identity certificate.
Before issuing the crypto ca authenticate command for a trustpoint, the trustpoint must be created by using the crypto ca
trustpoint command.
The trustpoint_CAname name needs to be the same as that of the trust point created by the crypto ca trustpoint command.
Examples
The following example shows how to authenticate the certificate authority certificate for a trustpoint named t1.
device# crypto ca authenticate t1 protocol SCP host 10.70.12.102 user fvt directory /users/home/crypto
file cacert.pem
Password: **********
History
Release version Command history
crypto ca enroll
Enrolls a trustpoint by generating the certificate signing request (CSR) and exporting it to the remote certificate authority (CA)
server.
Syntax
crypto ca enroll trustpointCA_name { common common_name | country country | directory remote_dir_name | host
host_address | locality locality | organization organization | orgunit orgunit | password host_user_password | protocol
{ FTP | SCP } | state state | user host_login }
Parameters
trustpointCA_name
Specifies a trustpoint name. The trustpoint name can range from 1 through 64 characters in length.
common common_name
Specifies the common name used to connect to the device through HTTPS. Enter a Fully Qualified Domain Name
(FQDN) or IP address. If a FQDN is used, you need to configure a domain name and name server on the device. The
common name can range from 1 through 253 characters in length.
country country
Specifes the two-letter country code for generating the CSR.
directory remote_dir_name
Specifies the remote directory to which the CSR is exported.
host host_address
Specifies the remote certificate server in hostname or IP address format.
locality locality
Specifies the locality name for generating the CSR.
organization organization
Specifies the organization name for generating the CSR.
orgunit orgunit
Specifies the organization subunit name for generating the CSR.
password host_user_password
Specifies the password for the user name on the host server.
NOTE
For security purposes, it is recommended that the password is not listed in the command line; the user will be
prompted to enter the password.
protocol
Specifies the protocol to use for exporting the certification file.
FTP
Specifies using File Transfer Protocol.
SCP
Specifies using Secure Copy Protocol.
state state
Specifies the state name for generating the CSR.
user host_login
Specifies the user name for login to the host server.
Modes
Privileged EXEC mode
Usage Guidelines
Before issuing the crypto ca enroll command for a trustpoint, the trustpoint must be created by using the crypto ca trustpoint
command.
Examples
The following example shows how to enroll a trustpoint named t1 on a certificate authority server that is identified by the IP
address 10.70.12.102.
device# crypto ca enroll t1 country US state CA locality SJ organization BRC orgunit SFI common
myhost.example.com protocol SCP host 10.70.12.102 user fvt directory /proj/crypto
Password: **********
History
Release version Command history
crypto ca import
Imports an identity certificate for HTTPS security configuration.
Syntax
crypto ca import trustpointCA_name certificate { directory remote_dir_name | file cert_file | host host_address | password
host_user_password | protocol { FTP | SCP } | user host_login }
Parameters
trustpointCA_name
Specifies a trustpoint name. The trustpoint name can range from 1 through 64 characters in length.
certificate
Causes the import of an identity certificate.
directory remote_dir_name
Specifies the directory where the certification file resides.
file cert_file
Specifies the name of the certification file.
host host_address
Specifies the host name or IP address of the remote certificate server.
password host_user_password
Specifies the password for the user name on the host server.
NOTE
For security purposes, it is recommended that the password is not listed in the command line; the user will be
prompted to enter the password.
protocol
Specifies the protocol for importing the certification file.
FTP
Specifies using File Transfer Protocol.
SCP
Specifies using Secure Copy Protocol.
user host_login
Specifies the user name for login to the host server.
Modes
Privileged EXEC mode
Usage Guidelines
Before issuing the crypto ca import command for a trustpoint, the trustpoint must be created by using the crypto ca trustpoint
command.
Examples
The following example shows how to import an identity certificate file for a trustpoint named t1 from a remote certificate server
identified by the IP address 10.70.12.102.
device# crypto ca import t1 certificate protocol SCP host 10.70.12.102 user fvt directory /users/crypto
file cacert.pem
Password: **********
History
Release version Command history
crypto ca trustpoint
Creates a trustpoint for HTTPS security configuration and enters configuration mode for the trustpoint.
Syntax
crypto ca trustpoint trustpointCA_name
Parameters
trustpointCA_name
Specifies a trustpoint name. The trustpoint name can range from 1 through 64 characters in length.
Modes
Global configuration mode
Usage Guidelines
The no version of the command removes the trustpoint configuration.
Examples
The following example shows how to create a trustpoint named t1 and enter configuration mode for the trustpoint.
The following example shows how to remove the t1 trustpoint configuration from the device.
History
Release version Command history
crypto key
Generates a cryptographic key pair for use in security protocol exchanges for applications.
Syntax
crypto key label key_label { dsa | ecdsa | rsa } [ modulus key_size ]
Parameters
label key_label
Specifies the cryptographic keypair label in alphanumeric characters.
dsa
Generates a Digital Signature Algorithm (DSA) keypair.
ecdsa
Generates an Elliptic Curve Digital Signature Algorithm (ECDSA) keypair.
rsa
Generates a Rivest, Shamir and Adelman (RSA) keypair.
modulus key_size
Specifies the key size. The corresponding key sizes supported for each keypair type are:
• RSA: 1024 or 2048 bits
• DSA: 1024 bits
• ECDSA: 256, 384, or 521 bits
Modes
Global configuration mode
Usage Guidelines
You must sign and encrypt or decrypt the key pair before you obtain a certificate for your device.
Examples
The following example shows how to generate an RSA keypair labeled k1 with a key size of 2048 bits.
History
Release version Command history
dampening
Sets dampening parameters for the route in BGP address-family mode.
Syntax
dampening { half-life reuse suppress max-suppress-time | route-map route-map-name }
no dampening
Parameters
half-life
Number of minutes after which the route penalty becomes half its value. Range is from 1 through 45. Default is 15.
reuse
Minimum penalty below which the route becomes usable again. Range is from 1 through 20000. Default is 750.
suppress
Maximum penalty above which the route is suppressed by the device. Range is from 1 through 20000. Default is
2000.
max-suppress-time
Maximum number of minutes a route can be suppressed by the device. Range is from 1 through 255. Default is 40.
route-map
Enables selection of dampening values established in a route map by means of the route-map command.
route-map-name
Name of the configured route map.
Modes
BGP address-family IPv4 unicast configuration mode
BGP address-family IPv6 unicast configuration mode
Usage Guidelines
Use dampening without operands to set default values for all dampening parameters.
To use the dampening values established in a route map, configure the route map first, and then enter the route-map
command, followed by the name of the configured route map.
Examples
The following example enables default dampening as an IPv4 address-family function.
The following example changes all the dampening values as an IPv6 address-family function.
History
Release version Command history
database-overflow-interval (OSPFv2)
Configures frequency for monitoring database overflow.
Syntax
database-overflow-interval interval
no database-overflow-interval
Parameters
interval
Time interval at which the device checks to see if the overflow condition has been eliminated. Valid values range from
0 through 86400 seconds. The default is 0 seconds.
Modes
OSPF router configuration mode
OSPF router VRF configuration mode
Usage Guidelines
This command specifies how long a device that has entered the OverflowState waits before resuming normal operation of
external LSAs. However, if the external link state database (LSDB) is still full, the device lapses back into OverflowState. If the
configured value of the database overflow interval is zero, then the device never leaves the database overflow condition.
When the maximum size of the LSDB is reached (this is a configurable value in the external-lsdb-limit CLI), the device enters
OverflowState. In this state, the device flushes all non-default AS-external-LSAs that the device had originated. The devie also
stops originating any non-default external LSAs. Non-default external LSAs are still accepted if there is space in the database
after flushing. If no space exists, the Non-default external LSAs are dropped and not acknowledged.
If the device enters OverflowState, you must reboot before the device leaves this state.
Examples
The following example configures a database-overflow interval of 60 seconds.
History
Release version Command history
database-overflow-interval (OSPFv3)
Configures frequency for monitoring database overflow.
Syntax
database-overflow-interval interval
no database-overflow-interval
Parameters
interval
Time interval at which the device checks to see if the overflow condition has been eliminated. Valid values range from
0 through 86400 seconds (24 hours). The default is 10 seconds.
Modes
OSPFv3 router configuration mode
OSPFv3 router VRF configuration mode
Usage Guidelines
This command specifies how long after a router that has entered the OverflowState before it can resume normal operation of
external LSAs. However, if the external link state database (LSDB) is still full, the router lapses back into OverflowState.
When the maximum size of the LSDB is reached (this is a configurable value in the external-lsdb-limit CLI), the router enters
OverflowState. In this state, the router flushes all non-default AS-external-LSAs that the router had originated. The router also
stops originating any non-default external LSAs. Non-default external LSAs are still accepted if there is space in the database
after flushing. If no space exists, the Non-default external LSAs are dropped and not acknowledged.
If the router enters OverflowState, you must reboot before the router leaves this state.
Examples
The following example configures a database-overflow interval of 120 seconds.
History
Release version Command history
Syntax
debug access-list-log buffer { circular | linear } packet-count count-value
Parameters
circular
Specifies circular buffer type.
linear
Specifies linear buffer type.
packet-count count-value
Specifies a value from 64 through 2056.
clear
Clears the buffer contents.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example clears the buffer.
History
Release version Command history
Syntax
debug arp packet buffer all
debug arp packet buffer { circular | linear } packet-count num-packets [ vrf vrf-name ]
debug arp packet buffer interface { ethernet slot / port | port-channel number | ve ve-id } [ rx | tx ]
no debug arp packet buffer interface { ethernet slot / port | port-channel number | ve ve-id } [ rx | tx ]
Parameters
all
Specifies all ARP-packet buffers.
circular
Specifies circular buffer type.
linear
Specifies linear buffer type.
packet-count num-packets
Specifies a value from 64 through 2056.
clear
Clears the buffer contents.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
interface
Specifies an Ethernet or VE interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel interface. The range is from 1 through 6144.
ve ve-id
Specifies a virtual ethernet (VE) interface.
rx
Specifies whether to capture only transmitted packets.
tx
Specifies whether to capture received packets.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
If neither rx nor tx are specified, both transmitted and received packets are captures.
To disable ARP packet capture on a specified interface, use the no debug dhcp packet buffer interface command.
To disable ARP packet capture on all interfaces, use the no debug dhcp packet buffer all command.
Examples
The following command enables ARP packet capture for transmitting data on Ethernet interface 0/5.
History
Release version Command history
Syntax
debug dhcp packet buffer all
debug dhcp packet buffer { circular | linear } packet-count num-packets [ vrf vrf-name ]
debug dhcp packet buffer interface { ethernet slot / port | port-channel number } [ rx | tx ]
no debug dhcp packet buffer interface { ethernet slot / port | port-channel number } [ rx | tx ]
Command Default
The buffer wraps around to overwrite earlier captures (circular).
Parameters
all
Captures DHCP packets on all interfaces.
circular
Buffer wraps around to overwrite earlier captures.
linear
Buffer does not wrap around to overwrite earlier captures.
packet-count num-packets
Specifies a value from 64 through 2056.
vrf vrf-name
Specifies a VRF.
clear
Clears the packet buffer.
interface
Represents an Ethernet or port-channel interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel interface. The range is from 1 through 6144.
rx
Specifies whether to capture only transmitted packets.
tx
Specifies whether to capture received packets.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
This command configures the capturing buffer behavior by allowing captures to wrap and overwrite earlier captures or stop
capturing when a packet-count limit is reached. The current buffer content is cleared when the configuration changes.
Use a no form of this command to disable DHCP debugging. You can specify an interface or all interfaces.
Examples
The following example configures a buffer to capture 510 maximum packets in a circular fashion.
History
Release version Command history
Syntax
debug dot1x packet { all | interface ethernet slot/port } [ detail ] [ both | rx | tx ]
Parameters
all
Causes the display of information for all interfaces.
interface
Causes the display of information for a specific interface.
ethernet slot/port
Specifies an Ethernet interface in slot and port number format; when the device does not contain slots, the
slot number must be 0.
detail
Causes the display of detailed information.
both
Causes the display of information about received and transmitted packets.
rx
Causes the display of information about only received packets.
tx
Causes the display of information about only transmitted packets.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
The no form of the command disables the display of processing information related to IEEE 802.1X port-based access control.
Examples
The following example shows how to display detailed processing information related to IEEE 802.1X port-based access control
for all interfaces.
The follow example shows how to disable the display of processing information related to IEEE 802.1X port-based access
control for port 0/1.
History
Release version Command history
debug ip bgp
Displays information related to the processing of BGP4, with a variety of options.
Syntax
debug ip bgp { cli | dampening | events | general | graceful-restart | ip-prefix ip-addr/mask-len | ip-prefix-list name |
keepalives | route-map name | route-selection | traces | updates [ rx | tx ] } [ all-vrfs | vrf vrf-name ]
no debug ip bgp
Parameters
cli
Displays information about BGP CLI
dampening
Displays BGP4 dampening.
events
Displays all BGP4 events.
general
Displays BGP4 common events.
graceful-restart
Displays BGP graceful restart events.
ip-prefix
Displays information filtered by IP prefix.
ip-addr
IPv4 address in dotted-decimal notation.
mask-len
IPv4 mask length in CIDR notation.
ip-prefix-list
Displays information filtered by IP prefix list.
name
Name of IP prefix list.
keepalives
Displays BGP4 keepalives.
route-map
Displays configured route map tags.
name
Name of route map.
route-selection
Displays BGP4 route selection.
traces
Displays BGP traces.
updates
Displays BGP4 updates.
rx
Displays BGP4 received updates.
tx
Displays BGP4 transmitted updates
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
If you want to see BGP4 keepalives for a specific neighbor, you must first specify the neighbor using the debug ip bgp
neighbor command. Only keepalive traces for the specified neighbor will appear in the debugging message.
Examples
The following example sets debugging on BGP4 events.
The following example specifies that BGP4 keepalives for a specified neighbor appear in debugging messages.
The following example sets debugging on BGP4 events for VRF instance "red".
History
Release version Command history
Syntax
debug ip bgp neighbor ip-addr [ all-vrfs | vrf vrf-name ]
Parameters
ip-addr
IPv4 address in dotted-decimal notation.
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example sets debugging on information related to the processing of BGP4 for a specific neighbor.
The following example specifies that BGP4 keepalives for a specified neighbor appear in debugging messages.
The following example sets debugging on information related to the processing of BGP4 for a specific neighbor for VRF
instance "red".
The following example sets debugging information related to the processing of BGP4 for a specific neighbor for all VRFs.
History
Release version Command history
debug ip igmp
Enables or disables debugging for IGMP information.
Syntax
debug ip igmp { all | errors | group A.B.C.D | packet | rx | tx | interface ethernet | port-channel | tunnel | vlan vlan_id }
no debug ip igmp
Parameters
all
Enables all debugs.
errors
Enables only error type debugs, such as memory allocation failures etc.
group A.B.C.D
Specifies the group address, as a subnet number in dotted decimal format (for example, 10.0.0.1), as the allowable
range of addresses included in the multicast group.
packet
Enables debug for query/reports per the chosen option.
rx
Specifies only ingressing flow debugs to be captured in traces.
tx
Specifies only egressing packet flows to be captured in traces.
interface
Specifies the interface (ethernet, port-channel, tunnel) to be monitored.
vlan
Specifies the VLAN to me monitored.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
When debugging is enabled, all of the IGMP packets received and sent and IGMP-host related events are displayed.
History
Release version Command history
Syntax
debug ipv6 bgp ipv6-prefix ipv6-address /mask [ all-vrfs | vrf vrf-name ]
Parameters
ipv6-prefix
Displays information filtered by IPv6 prefix.
ipv6-address /mask
Specifies an IPv6 address and network mask.
name
Specifies a prefix list name.
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance
ipv6-prefix-list
Displays information filtered by IPv6 prefix list.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example enables debugging for IPv6 prefix list "myv6list" for VRF instance "red".
The following example enables debugging for a specified IPv6 address for all VRFs.
History
Release version Command history
Syntax
debug ipv6 bgp neighbor ipv6-addr [ all-vrfs | vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor.
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example sets debugging for a neighbor.
The following example specifies that BGP keepalives for a specified neighbor appear in debugging messages.
The following example sets debugging for a neighbor for VRF instance "red".
The following example sets debugging for a neighbor for all VRFs.
History
Release version Command history
debug lacp
Enables or disables debugging for the Link Aggregation Control Protocol (LACP).
Syntax
debug lacp { all | cli | event | pdu [ rx { all | interface ethernet slot/port | tx { all | sync | timer | trace level number }
no debug lacp
Command Default
LACP debugging is disabled.
Parameters
all
Turns on all debugging.
cli
Turns on command line interface debugging.
event
Turns on event debugging.
pdu
Echo PDU content to the console.
rx all
Turns on debugging for received LACP packets on all interfaces.
rx interface
Turns on debugging for received LACP packets on the specified interface.
interface
Specifies the interface to be monitored.
ethernet
Represents a valid, physical Ethernet interface.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
tx all
Turns on debugging for transmitted LACP packets on all interfaces.
tx interface
Turns on debugging for transmitted LACP packets on the specified interface.
sync
Echo synchronization to consoles.
timer
Echo timer expiration to console.
Modes
Privileged EXEC mode
Usage Guidelines
Enter terminal monitor to display debugging outputs on a particular cmsh session.
Examples
To enable debugging of LACP PDUs for transmitted and received packets on all interfaces:
History
Release version Command history
Syntax
debug lldp dump { all | [ ethernet slot/port ] [ both ] | [ detail [ both | rx | tx ] }
Command Default
LLDP debugging is disabled.
Parameters
all
Dumps all information to the console.
ethernet
Represents a valid, physical Ethernet port.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
both
Turns on debugging for both transmit and receive packets.
detail
Turns on debugging with detailed information.
both
Turns on detailed debugging for both transmit and receive packets.
rx
Turns on detailed debugging for only received LLDP packets.
tx
Turns on detailed debugging for only transmitted LLDP packets.
Modes
Privileged EXEC mode
Examples
Typical use of this command.
History
Release version Command history
Syntax
debug lldp packet { all { both | rx | tx } | ethernet slot/port { both | rx | tx } } | [ detail ]
Command Default
LLDP debugging is disabled.
Parameters
all
Turns on LLDP packet debugging on all interfaces.
ethernet
Represents a valid, physical Ethernet port.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
both
Turns on debugging for both transmit and receive packets.
rx
Turns on detailed debugging for only received LLDP packets.
tx
Turns on detailed debugging for only transmitted LLDP packets.
detail
Turns on debugging with detailed information.
Modes
Privileged EXEC mode
Usage Guidelines
Enter terminal monitor to display debugging outputs on a particular cmsh session.
Examples
To enable debugging of LLDP for both received and transmitted packets on all interfaces:
To enable debugging of LLDP for both received and transmitted packets on Ethernet interface 0/1:
History
Release version Command history
debug spanning-tree
Enables debugging for the Spanning Tree Protocol (STP).
Syntax
debug spanning-tree { all | bpdu [ rx | tx [ all | [ interface { ethernet slot/port | port-channel number }
no debug spanning-tree { all | bpdu [ rx | tx [ all | [ interface { ethernet slot/port | port-channel number }
Command Default
STP debugging is disabled.
Parameters
all
Turns on spanning tree packet debugging on all interfaces.
bpdu
Turns on Bridge Protocol Data Unit debugging.
rx
Turns on debugging for only received spanning-tree packets.
tx
Turns on debugging for only transmitted spanning-tree packets.
interface
Specifies an interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel. The number of available channels ranges from 1 through 6144.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
To enable debugging of spanning-tree for both Rx and Tx on Ethernet interface 0/1:
History
Release version Command history
default-information-originate (BGP)
Configures the device to originate and advertise a default BGP route.
Syntax
default-information-originate
no default-information-originate
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command disables the advertisement of a default route.
Examples
The following example originates and advertises a default BGP4 route.
The following example originates and advertises a default BGP4+ route for VRF "red".
History
Release version Command history
default-information-originate (OSPFv2)
Controls distribution of default information to an OSPFv2 device.
Syntax
default-information-originate [ always ] [ metric metric ] [ metric-type { type1 | type2 } ] [ route-map name ]
no default-information-originate
Command Default
The default route is not advertised into the OSPFv2 domain.
Parameters
always
Always advertises the default route. If the route table manager does not have a default route, the router advertises the
route as pointing to itself.
metric metric
specifies the cost for reaching the rest of the world through this route. If you omit this parameter and do not specify a
value using the default-metric router configuration command, a default metric value of 1 is used. Valid values range
from 1 through 65535.
metric-type
Specifies how the cost of a neighbor metric is determined. The default is type1. However, this default can be changed
with the metric-type command.
type1
Type 1 external route.
type2
Type 1 external route,
route-map name
Specifies that the default route is generated if the route map is satisfied. This parameter overrides other options. If the
set metric and set metric-type commands are specified in the route-map, the command-line values of metric and
metric-type if specified, are “ignored” for clarification.
Modes
OSPF router configuration mode
Usage Guidelines
This configuration provides criteria for the redistribution of any default routes found in the route table manager (RTM), whether
static or learned from another protocol, to its neighbors.
The corresponding route-map should be created before configuring the route-map option, along with the default-information-
originate command. If the corresponding route-map is not created beforehand, an error message is displayed stating that the
route-map must be created.
The route-map option cannot be used with a non-default address in the match conditions. The default route LSA is not
generated if a default route is not present in the routing table and a match ip address condition for an existing non-default route
is configured in the route-map. The match ip address command in the route-map is a no-op operation for the default
information originate command.
Examples
The following example creates and advertises a default route with a metric of 30 and a type 1 external route.
History
Release version Command history
default-information-originate (OSPFv3)
Controls distribution of default information to an OSPFv3 device.
Syntax
default-information-originate [ always ] [ metric metric ] [ metric-type { type1 | type2 } ]
no default-information-originate
Command Default
The default route is not advertised into the OSPFv3 domain.
Parameters
always
Always advertises the default route. If the route table manager (RTM) does not have a default route, the router
advertises the route as pointing to itself.
metric metric
Used for generating the default route, this parameter specifies the cost for reaching the rest of the world through this
route. If you omit this parameter, the value of the default-metric command is used for the route. Valid values range
from 1 through 65535.
metric-type
Specifies the external link type associated with the default route advertised into the OSPF routing domain.
type1
The metric of a neighbor is the cost between itself and the router plus the cost of using this router for routing
to the rest of the world.
The default is type1.
type2
The metric of a neighbor is the total cost from the redistributing routing to the rest of the world.
Modes
OSPFv3 router configuration mode
Usage Guidelines
This configuration provides criteria for the redistribution of any default routes found in the RTM (whether static or learned from
another protocol) to its neighbors.
Examples
The following example specifies a metric of 20 for the default route redistributed into the OSPFv3 routing domain and an
external metric type of Type 2.
History
Release version Command history
default-local-preference
Enables setting of a local preference value to indicate a degree of preference for a route relative to that of other routes.
Syntax
default-local-preference num
no default-local-preference
Parameters
num
Local preference value. Range is from 0 through 65535. The default is 100.
Modes
BGP configuration mode
Usage Guidelines
Local preference indicates a degree of preference for a route relative to that of other routes. BGP4 neighbors can send the local
preference value as an attribute of a route in an UPDATE message.
Examples
The following example sets the local preference value to 200.
History
Release version Command history
default-metric (BGP)
Changes the default metric used for redistribution.
Syntax
default-metric value
no default-metric
Parameters
value
Metric value. Range is from 0 through 4294967295. The default is 1.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example changes the default metric used for redistribution to 100.
History
Release version Command history
default-metric (OSPF)
Sets the default metric value for the OSPFv2 or OSPFv3 routing protocol.
Syntax
default-metric metric
no default-metric
Parameters
metric
OSPF routing protocol metric value. Valid values range from 1 through 65535. The default is 10.
Modes
OSPF router configuration mode
Usage Guidelines
This command overwrites any incompatible metrics that may exist when OSPFv2 or OSPFv3 redistributes routes. Therefore,
setting the default metric ensures that neighbors will use correct cost and router computation.
Examples
The following example sets the default metric to 20 for OSPF.
History
Release version Command history
default-passive-interface
Marks all OSPFv2 and OSPFv3 interfaces passive by default.
Syntax
default-passive-interface
no default-passive-interface
Modes
OSPF router configuration mode
Usage Guidelines
When you configure the interfaces as passive, the interfaces drop all the OSPFv2 and OSPFv3 control packets.
You can use the ip ospf active and ip ospf passive commands in interface subconfiguration mode to change active/passive
state on specific OSPFv2 interfaces. You can use the ipv6 ospf active and ipv6 ospf passive commands in interface
subconfiguration mode to change the active and passive state on specific OSPFv3 interfaces.
Examples
The following example marks all OSPFv2 interfaces as passive.
History
Release version Command history
delay
For an implementation of an event-handler profile, specifies a delay from when a trigger is received until execution of the event-
handler action.
Syntax
delay seconds
no delay
Command Default
There is no delay from when a trigger is received until execution of the event-handler action.
Parameters
seconds
Specifies the number of seconds from when a trigger is received until the execution of the specified action begins.
Valid values are 0 or a positive integer.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command resets the delay setting to the default 0 seconds.
Examples
The following example specifies a delay of 60 seconds.
History
Release version Command history
delay-link-event
Configures the port transition hold timer to set a delay in the sending of port up or down port events, or both, to Layer 2
protocols.
Syntax
delay-link-event multiple-iteration { down | up | both }
no delay-link-event
Command Default
The sending of an up or down port event is not delayed.
Parameters
multiple-iteration
Specifies the number of times that the polling iteration occurs. Enter an integer from 1 to 200.
The polling iteration is 50 ms. The delay time is the multiple-iteration times 50 ms.
both
Sets the delay for the port down and up events.
down
Sets the delay for the port down event.
up
Sets the delay for the port up event.
Modes
Interface Ethernet configuration mode.
Usage Guidelines
Use the no form of the command to remove the delay from the port events on the interface.
While link down events are reported immediately in the Syslog, their effect on higher level protocols such as OSPF is delayed
according to how the hold timer is configured. When configured, the timer affects the physical link events. However, the resulting
logical link events are also delayed.
NOTE
All LAG member ports must have the same delayed-link-event
configuration.
NOTE
The delayed-link-event configuration is applicable only on a physical interface. It is not valid on a VLAN, VE, LAG, or
loopback interfaces.
NOTE
The port transition hold timer does not take effect when the interface is administratively shut
down.
Examples
The following example configures Ethernet interface 0/2 to delay transmission of port down events to Layer 2 protocols.
History
Release version Command history
delay-request-min-interval
Configures on a slave port the minimum interval allowed between Precision Time Protocol (PTP) Delay-Request messages sent
on the port.
Syntax
delay-request-min-interval seconds
no delay-request-min-interval
Parameters
seconds
Interval between PTP Delay-Request messages, in log seconds. Range is -4 through 2. The default is -1 (2 packets/
second).
Modes
PTP configuration mode
Usage Guidelines
The inputs for interval represent base 2 exponents, where the packet rate is 1/(2log seconds).
Configuring this interval on an edge port overrides the switch (global) default.
ATTENTION
Do not configure a rate slower than the default on links between Extreme SLX-OS
devices.
Examples
To configure a PTP Delay-Request minimum interval of 2 on an Ethernet interface:
History
Release version Command history
delete
Deletes a user-generated file from the flash memory.
Syntax
delete file
Parameters
file
The name of the file to be deleted.
Modes
Privileged EXEC mode
Usage Guidelines
The delete operation is final; there is no mechanism to restore the file.
System configuration files cannot be deleted. If you try to delete a system configuration file, an appropriate message is
displayed.
Examples
To delete a user-generated copy of a configuration file:
History
Release version Command history
deny inner-gtp-https
Enables the dropping—from ingress traffic—of GPRS Tunneling Protocol (GTP) frames that encapsulate HTTPS packets.
Syntax
deny inner-gtp-https
no deny inner-gtp-https
Command Default
Such filtering is not enabled.
Modes
Interface configuration mode
Usage Guidelines
This feature must be implemented per physical interface.
If this feature filtering is enabled, common practice is to forward the filtered traffic by using a Network Packet Broker (NPB)
route-map.
Examples
The following example enables dropping GTP frames that encapsulate HTTPS packets.
The following example restores the default setting of not dropping HTTPS packets transported within GTP frames.
History
Release version Command history
deploy
Deploys the MCT cluster or cluster client to bring the MCT device to operational mode.
Syntax
deploy
no deploy
Modes
Cluster and cluster client configuration mode
Usage Guidelines
Before deploying a cluster, the cluster client must be configured.
Before deploying a cluster client, the client interface and ESI settings must be configured under the client configuration.
The client will not operate in MCT mode unless the remote client is also deployed.
The no form of the command undeploys the cluster or the client cluster.
When the client is undeployed, all MAC addresses are removed locally and a withdraw message is sent to the MCT peer to
remove all associated client MAC addresses.
Examples
The following example shows the deployment of a cluster.
History
Release version Command history
Syntax
description description-text
no description
Command Default
No description is defined.
Parameters
description-text
Characters describing the event-handler profile. The string can be 1 through 128 ASCII characters in length. Do not
use the ? character. If you need to use ! or \, precede each with \.
Modes
Event-handler configuration mode
Usage Guidelines
An event-handler profile supports only one description.
To change a description, you do not need to first delete the existing description. Just create a new description.
Examples
The following example defines a description for eventHandler1.
History
Release version Command history
description (interfaces)
Specifies a string describing an interface.
Syntax
description line
Parameters
line
Specifies characters describing the interface. The string must be between 1 and 63 ASCII characters in length.
Modes
Interface subtype configuration mode
Examples
To set the string describing internal Ethernet interface 0/2:
History
Release version Command history
description (LLDP)
Specifies a string that contains the LLDP description.
Syntax
description string
Parameters
string
Characters describing LLDP. The string must be between 1 and 50 ASCII characters in length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
The LLDP description can also be configured for a specific LLDP profile. When you apply an LLDP profile on an interface using
the lldp profile command, it overrides the global configuration. If a profile is not present, then the default global profile is used
until you create a valid profile.
Examples
To set the strings describing LLDP:
To set the strings describing LLDP for a specific LLDP profile, test2, enter the following:
History
Release version Command history
description (STP)
Describes an xSTP configuration.
Syntax
description description
no description
Parameters
description
Characters describing the xSTP configuration. The string must be between 1 and 64 ASCII characters in length.
Modes
xSTP configuration mode
Usage Guidelines
Enter no description to remove the description.
Examples
To specify the bridge priority:
History
Release version Command history
Syntax
description description-text
description
Command Default
TVF domains have no description.
Parameters
description-text
Describes a TVF domain.
Modes
TVF-domain configuration mode
Usage Guidelines
To remove a description, enter the command with no description-text.
To modify a description, enter the full description description-text command. You do not need to first remove the previous
description.
Examples
The following example creates a TVF domain and then adds a description.
The following example displays current TVF domains and their descriptions, accesses a TVF domain, changes its description,
and then displays the modifed description.
History
Release version Command history
description (VRRP)
Describes a Virtual Router Redundancy Protocol (VRRP) or a VRRP extended (VRRP-E) interface.
Syntax
description description
no description
Parameters
description
Characters describing the VRRP-E interface. The string must be between 1 and 64 ASCII characters in length.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command can be used in both VRRP and VRRP-E. Enter no description to remove the description.
Examples
To describe the VRRP-E group 10 interface:
History
Release version Command history
designated-forwarder-hold-time
Configures the time in seconds to wait before electing a designated forwarder.
Syntax
designated-forwarder-hold-time seconds
designated-forwarder-hold-time
Command Default
The default setting is three seconds.
Parameters
seconds
Specifies the hold time in seconds. Enter an integer from 1 to 60.
Modes
Cluster configuration mode
Usage Guidelines
Use the no form of the command to reset the default setting of three seconds.
The designated forwarder is a leaf node in a set of multi-homing nodes connected to the same Ethernet segment that is
responsible for sending BUM traffic to a client for a particular VLAN ID on an Ethernet segment.
DF election is not triggered unless at least one remote client is configured. When a client goes up or down, DF election is
triggered as soon as the Ethernet route acknowledgment from remote peer is received.
When a client is deployed locally or remotely, or the BGP session comes up, the DF timer does not start and DF election is not
performed until the timer expired.
Examples
The following example configures a 20-second hold time for DF election.
History
Release version Command history
destination
Designates the destination interface for the snooping data for flow-based SPAN.
Syntax
destination dest_ifname
no destination dest_ifname
Parameters
dest_ifname
The name of the destination interface.
Modes
Monitor session mode
Usage Guidelines
Use the no destination dest_ifname command to delete the destination interface.
Examples
This example configures the IP address Ethernet 0/1 as the destination address.
History
Release version Command history
df-load-balance
Enables designated forwarder (DF) load balancing.
Syntax
df-load-balance
no df-load-balance
Command Default
By default, DF load balancing is disabled.
Modes
Cluster configuration mode
Usage Guidelines
Use the no form of the command to disable DF load balancing.
One leaf node is the DF for the VLAN on the Ethernet segment (ES).
When DF load balancing is disabled, DF election is triggered only when the current DF leaf node goes down or its client
interface is down. When a non-DF leaf node goes down or a new node joins the ES, DF election is not triggered.
When DF load balancing is enabled, the DF election is triggered in the following scenarios:
• A client is deployed locally or remotely.
• The BGP cluster control protocol (CCP) session comes up.
• Remote CCEP goes up or down.
Examples
The following example enables the load balancing of the designated forwarder.
History
Release version Command history
Syntax
dhcp ztp cancel
Modes
Privileged EXEC mode
Usage Guidelines
NOTE
If you need to interrupt the ZTP operation when in progress using the dhcp ztp cancel command, you may notice a
one minute delay in canceling.
Once canceled, the ZTP session stops retry, irrespective of whether the process succeeds or fails. If firmware download
completes successfully, the device returns to the normal mode. The following limitations apply:
• If firmware download has not started, you will need to reboot the switch manually to bring the switch back to normal
mode.
• If firmware download has already started, you must wait for firmware download to complete before running any other
CLI, power cycling the switch, starting a new firmware download, or starting a new ZTP session.
• If firmware download completes and the switch fails to reboot, you must reboot the switch manually to bring the switch
back to normal mode.
Examples
The following example cancels the ZTP after device bootup.
If you force the cancellation of ZTP while in progress, the following output displays.
History
Release version Command history
Syntax
dhcp ztp log
Command Default
Modes
Privileged EXEC mode
Usage Guidelines
The progress log displays if Zero Touch Provisioning is enabled.
Examples
The following log displays if ZTP cancels successfully.
If the device has the same image as the ZTP configuration file, the following output displays:
History
Release version Command history
diag burninerrclear
Clears the error logs, generated by system-verification failures, that are stored in nonvolatile memory.
Syntax
diag burninerrclear
Command Default
No test is executed.
Modes
Offline diagnostic mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
ATTENTION
Do not abort testing. This test must be allowed to run to completion.
To check the logs and error messages that are generated during system verification, use the following commands:
Examples
The following example shows the output of this test.
<---output truncated--->
History
Release version Command history
diag portledtest
Executes portLedTest to test the LEDs on a single port or all ports on the device.
Syntax
diag portledtest [ port { all | number } ] [ off | on }
Command Default
If no parameter is specified, the default setting is as follows: diag portledtest port all on
Parameters
port
Specifies a single port or all ports.
all
Specifies all ports.
number
Specifies a single port.
off
Turns off the LEDs.
on
Turns on the LEDs.
Modes
Offline diagnostic mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
ATTENTION
Do not abort testing. This test must be allowed to run to completion.
IMPORTANT
Remove or unplug all inserted transceiver or DAC modules prior to testing, to avoid LED errors.
It is recommended that you turn off all LEDs prior to making a visual check. Use the reload command to power cycle the device
after testing.
The SLX 9240 has four LEDs per 40/100 gigabit port (ports 1 through 32).
The SLX 9140 has one LED per 10/25 gigabit port (ports 1 through 48), and four LEDs per 40 or 100 gigabit port (ports 49
through 54).
Examples
The following example tests all ports for the "off" condition.
History
Release version Command history
diag portloopbacktest
Executes portLoopbackTest to test a single port or all ports on the device.
Syntax
diag portloopbacktest [ port { all | number } [ lbmode { 0 | 1 } ] [ nframes number ] [ spdmode { high | low } ] ]
Command Default
The default settings are as shown in Parameters.
Parameters
port
Specifies a single port or all ports.
all
Specifies all ports. This is the default.
number
Specifies a single port.
lbmode
Specifies loopback test mode.
0
Tests the internal looback for inner Serializer/Deserializer (SerDes) lanes. This is the default.
1
Tests the external loopback for a single loopback module.
nframes number
Specifies the number of frames to be sent or received. Range is from 100 through 1000. The default is 100
spdmode
Specifies the port speed. Values for high and low are assigned according to the port and platform type.
high
Specifies 100 G mode for ports 1 through 32 on the SLX 9240. Specifies 25 G mode for ports 1 through
48 and 100 G mode for ports 49 through 54 on the SLX 9140. This is the default.
low
Specifies 40 G mode for ports 1 through 32 on the SLX 9240. Specifies 10 G mode for ports 1 through 48
and 40 G mode for ports 49 through 54 on the SLX 9140.
Modes
Offline diagnostic mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
ATTENTION
Do not abort testing. This test must be allowed to run to completion.
NOTE
For external loopback testing (lbmode = 1), ensure that ports to be tested are connected with SFPs or loopback plugs.
Examples
The following example shows a default test on a SLX 9240 (internal loopback mode 0. all ports at 10 G).
The following example shows a test on a SLX 9240 with loopback mode 1 and all ports at 40 G.
The following example tests a SLX 9240 with loopback mode 0 (the default) and all ports at 100 G.
The following example tests a SLX 9240with a single port at 10 G (the default)
The following example tests a SLX 9240 with loopback mode 1 and all ports at 10 G (the default)
The following example tests a SLX 9240 on port 27 with loopback mode 1 and a default speed of 25 G.
The following example tests a SLX 9140 in loopback mode 0 with all ports at 25 G.
The following example tests a SLX 9140 with loopback mode 0 and ports 49 through 54 at 100 G.
The following example tests a SLX 9140 in loopback mode 1 for ports 49 through 54 at 100 G. (Ranging is currently not
supported.)
The following example tests a SLX 9140 in loopback mode 0 on port 3, with port speed set to high and the number of frames
set to 200.
The following example tests a SLX 9140 in loopback mode 0 on port 3, with port speed set to low.
The following example tests a SLX 9140 on port 22, with loopback mode set to 1 and port speed set to low.
The following example tests a SLX 9140 on ports 49 through 54, with loopback mode set to 1 and port speed set to low.
The following example tests a SLX 9140 on ports 49 through 54, with loopback mode set to 1 and port speed set to high.
The following example tests a SLX 9240 on ports 49 through 54, with loopback mode set to 1 and port speed set to high.
History
Release version Command history
diag setcycle
Specifies the parameters for the system-verification test suite.
Syntax
diag setcycle { default | [ lbmode { 0 | 1 } [ num_of_runs number ] [ pled_passes number ] [tbr_passes number ]
[ plb_nframes number ] }
Command Default
At least one parameter is expected.
Parameters
default
Restores default parameters for the next system-verification test.
lbmode
Specifies the loopback test mode.
0
Tests the internal looback for inner Serializer/Deserializer (SerDes) lanes. This is the default.
1
Tests the external looback for a single loopback modules.
num_of_runs number
Specifies the number of verification passes. Range is 1 through 25. The default is 1.
pled_passes number
Specifies the number of portLedTest passes. Range is 1 through 10. The default is 1.
tbr_passes number
Specifies the number of turboRamTest passes. Range is 1 through 10. The default is 1.
plb_nframes number
Specifies the number of portLoopbackTest frames at the default speed. The default number of frames is 100.
Modes
Offline diagnostic mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
Use the show diag setcycle command to confirm the results of this command.
Examples
To set the parameters to defaults for the next system-verification test to be run:
To set the loopback mode for the next system-verification test to be run to the nondefault setting:
History
Release version Command history
diag systemverification
Executes a system-verification test suite.
Syntax
diag systemverification
Command Default
No parameters are used.
Modes
Offline diagnostics mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
This is an "all-in-one" test for quick system checks. The tests are based on the parameters set by the diag setcycle command.
Tests include turboRamTest, portLedTest, and portLoopBackTest. Tests may take a while time to complete.
ATTENTION
Do not abort testing. This test must be allowed to run to completion. After this test completes, you must power-cycle
the switch by means of the reload command before running additional offline diagnostic tests.
NOTE
For external loopback testing (lbmode = 1), ensure that ports to be tested are connected with SFPs or loopback plugs.
Examples
The following example illustrates the execution of this test.
====================
date: Thu Feb 17 14:57:12 UTC 2000
systemverification on round 1
% Info: This test should be run to completion. Please do not abort while it is executing.
Running turboramtest...
loop#1: PASS
memt -s 500 : PASSED
loop#1: PASS
memt -s 300 -a 1: PASSED
memtester.sh : PASSED
% Info: This test should be run to completion. Please do not abort while it is executing.
Running portledtest...
0xFB800300: 0xFFFFFFFF
0xFB800304: 0x14FFFFFF
0xFB800308: 0x13121110
0xFB80030C: 0x18171615
<---output truncated--->
-- Done --
xp80FirmwareB0-2016-0502-1906.bin loaded
[All LED on]
-- Done --
% Info: This test should be run to completion. Please do not abort while it is executing.
Running portloopbacktest...
Port type='MAC_MODE_4X10GB' link 'Up', Rx=100
port loopback test on port 1 PASSED
Port type='MAC_MODE_4X10GB' link 'Up', Rx=100
port loopback test on port 2 PASSED
<---output truncated--->
History
Release version Command history
diag turboramtest
Executes turboRamTest on the device to check DDR SDRAM.
Syntax
diag turboramtest [ passcnt count ]
Command Default
If passcnt is not specified, only one test is executed.
Parameters
passcnt count
Specifies the number of test loops to be run. Range is 1 though 10.
Modes
Privileged EXEC mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
ATTENTION
Do not abort testing. This test must be allowed to run to completion.
Examples
The following example executes the default number of test loops (1).
History
Release version Command history
dir
Lists the contents of the device flash memory.
Syntax
dir
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Examples
The following example lists the contents of the flash memory.
device# dir
total 4136
drwxr-xr-x 2 root root 4096 Feb 13 08:18 .
drwxr-xr-x 3 root root 4096 Mar 31 2000 ..
-rw-r--r-- 1 root root 12946 Jan 9 16:35 bfd-mib.cfg
-rw-r--r-- 1 root root 12738 Dec 16 12:51 default_config
-rw-r--r-- 1 root sys 495 Jan 30 04:12 defaultconfig.cluster
-rw-r--r-- 1 root root 446 Jan 31 15:08 defaultconfig.standalone
-rw-r--r-- 1 root root 49534 Jan 24 16:13 ipv4_64-way-ecmp_unid.cfg
-rw-r--r-- 1 root root 187126 Dec 7 13:54 ipv4_bfd_unid_200ospf_250
bgp.cfg
-rw-r--r-- 1 root root 132842 Dec 8 17:03 ipv4_bfd_unid_250static.c
fg
-rw-r--r-- 1 root root 105355 Jan 27 15:17 ipv4_bgp-peer-group-scale
-250_unid.cfg
-rw-r--r-- 1 root root 85734 Jan 25 15:43 ipv4_bgp-ribin-ribout-sca
le-3.2M-9.6M_unid.cfg
-rw-r--r-- 1 root root 85779 Jan 26 11:33 ipv4_bgp-ribin-ribout-sca
le-320k-3.8M_unid.cfg
-rw-r--r-- 1 root root 85754 Jan 26 14:38 ipv4_bgp-ribin-ribout-sca
le-320k-320k_unid.cfg
-rw-r--r-- 1 root root 49460 Jan 20 12:22 ipv4_ebgp-scale-256_unid.
cfg
-rw-r--r-- 1 root root 49460 Jan 21 19:25 ipv4_hw-route-scale-48k_u
nid.cfg
-rw-r--r-- 1 root root 97274 Dec 23 11:32 ipv4_static-128-vrf_unid.
cfg
-rw-r--r-- 1 root root 149596 Dec 21 14:56 ipv4_static-64-way-ecmp_u
nid.cfg
-rw-r--r-- 1 root root 288612 Dec 13 11:50 ipv4_unid_1kvrf.cfg
-rw-r--r-- 1 root root 401259 Dec 16 12:34 ipv4_unid_static_route_sc
ale_12k
-rw-r--r-- 1 root root 23583 Dec 19 19:39 ipv6_64-way-ecmp_unid.cfg
-rw-r--r-- 1 root root 173679 Dec 8 14:47 ipv6_bfd_unid_200ospf.cfg
-rw-r--r-- 1 root root 173560 Dec 8 14:31 ipv6_bfd_unid_250bgp.cfg
-rw-r--r-- 1 root root 134777 Dec 14 15:07 ipv6_bfd_unid_250static.c
fg
-rw-r--r-- 1 root root 58256 Jan 11 11:48 ipv6_bgp-64-way-ecmp_unid
.cfg
-rw-r--r-- 1 root root 31238 Jan 11 14:45 ipv6_bgp-ribin-10k-ribout
-100k_unid.cfg
-rw-r--r-- 1 root root 36536 Jan 11 16:45 ipv6_bgp-ribin-32k-ribout
-1M_unid.cfg
-rw-r--r-- 1 root root 58187 Jan 10 17:14 ipv6_bgp_unid_256.cfg
-rw-r--r-- 1 root root 217061 Jan 12 15:27 ipv6_intf-scale-2k_unid.c
fg
-rw-r--r-- 1 root root 346540 Jan 17 16:22 ipv6_ipv6-addr-scale_unid
.cfg
-rw-r--r-- 1 root root 232616 Dec 7 16:56 ipv6_ospf_bgp_bfd_250.cfg
-rw-r--r-- 1 root root 13013 Dec 19 17:20 ipv6_rib_fib_unid_4k.cfg
-rw-r--r-- 1 root root 227795 Jan 13 14:55 ipv6_sec-addr-scale-255_u
nid.cfg
-rw-r--r-- 1 root root 60434 Jan 3 17:43 ipv6_static-128-vrf_unid.
cfg
-rw-r--r-- 1 root root 61359 Dec 21 15:43 ipv6_static-64-way-ecmp_u
nid.cfg
-rw-r--r-- 1 root root 129253 Dec 16 16:04 ipv6_unid_static_route_sc
ale_3k
-rw-r--r-- 1 root root 279380 Jan 19 15:25 ipv6_ve-vrf-scale_unid.cf
g
-rw-r--r-- 1 root root 446 Feb 8 14:38 startup-config
History
Release version Command history
disable (LLDP)
Disables Link Layer Discovery Protocol (LLDP) globally without changing any other aspect of the LLDP configuration.
Syntax
disable
no disable
Command Default
LLDP is enabled globally by default.
Modes
Protocol LLDP configuration mode
Usage Guidelines
Enter the no disable to re-enable LLDP.
Examples
The following example disables LLDP.
History
Release version Command history
distance (BGP)
Changes the default administrative distances for eBGP, iBGP, and local BGP.
Syntax
distance external-distance internal-distance local-distance
no distance
Parameters
external-distance
eBGP distance. Range is from 1 through 255.
internal-distance
iBGP distance. Range is from 1 through 255.
local-distance
Local BGP4 and BGP4+ distance. Range is from 1 through 255.
Modes
BGP configuration mode
Usage Guidelines
To select one route over another according to the source of the route information, the device can use the administrative
distances assigned to the sources. The administrative distance is a protocol-independent metric that IP devices use to compare
routes from different sources. Lower administrative distances are preferred over higher ones.
Examples
The following example configures the device to change the administrative distance.
History
Release version Command history
distance (OSPF)
Configures an administrative distance value for OSPFv2 and OSPFv3 routes.
Syntax
distance { external | inter-area | intra-area | route-map } distance
no distance
Parameters
external
Sets the distance for routes learned by redistribution from other routing domains.
inter-area
Sets the distance for all routes from one area to another area.
intra-area
Sets the distance for all routes within an area.
route-map
Sets the distance based on route maps within an area.
distance
Administrative distance value assigned to OSPF routes. Valid values range from 1 through 255. The default is 110.
Modes
OSPF router configuration mode
Usage Guidelines
You can configure a unique administrative distance for each type of OSPF route.
The distances you specify influence the choice of routes when the device has multiple routes from different protocols for the
same network. The device prefers the route with the lower administrative distance. However, an OSPFv2 or OSPFv3 intra-area
route is always preferred over an OSPFv2 or OSPFv3 inter-area route, even if the intra-area route’s distance is greater than the
inter-area route’s distance.
Examples
The following example sets the distance value for all external routes to 125.
The following example sets the distance value for intra-area routes to 80.
The following example sets the distance value for inter-area routes to 90.
History
Release version Command history
Syntax
distribute-list prefix-list list-name in
no distribute-list prefix-list
Command Default
Prefix lists are not applied to OSPFv3 for IPv6 routing updates.
Parameters
list-name
Name of a prefix-list. The list defines which OSPFv3 networks are to be accepted in incoming routing updates.
in
Applies the prefix list to incoming routing updates on the specified interface.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The no form of the command removes the prefix list.
Examples
The following example configures a distribution list that applies the filterOspfRoutes prefix list globally.
History
Release version Command history
distribute-list route-map
Creates a route-map distribution list.
Syntax
distribute-list route-map map in
no distribute-list route-map
Parameters
map
Specifies a route map.
in
Creates a distribution list for an inbound route map.
Modes
OSPF router configuration mode
Usage Guidelines
The distribution list can filter Link State Advertisements (LSAs) received from other OSPF devices before adding the
corresponding routes to the routing table.
Examples
The following example creates a distribution list using a route map named filter1 that has already been configured.
History
Release version Command history
domain
In PTP configuration mode, specifies a Precision Time Protocol clock domain.
Syntax
domain domain_id
no domain
Command Default
See the Usage Guidelines.
Parameters
domain_id
Specifies a nondefault PTP clock domain. Range is from 0 through 255. The default is 0. See the Usage Guidelines.
Modes
PTP configuration mode
Usage Guidelines
Only a single domain can be specified, and only clocks in the same domain can communicate with each other.
Use the no form of this command to revert to domain ID 0.
Examples
To specify a nondefault clock domain:
History
Release version Command history
dot1x authentication
Enables 802.1x authentication on a port.
Syntax
dot1x authentication
no dot1x authentication
Command Default
802.1x authentication is disabled.
Modes
Interface configuration mode
Usage Guidelines
NOTE
To activate authentication on an 802.1x-enabled interface, port control must be configured. You can configure port
control by using the dot1x port-control auto command in interface configuration mode.
Use the no form of the command to disable 802.1x authentication on the port and remove the configuration from 802.1x
management configuration.
Examples
The following example enables 802.1x authentication on Ethernet port 0/1.
History
Release version Command history
dot1x enable
Enables 802.1X port authentication globally.
Syntax
dot1x enable
Command Default
802.1x port authentication is not enabled.
Modes
Global configuration mode
Usage Guidelines
NOTE
802.1x port authentication is not supported by Link Aggregation Group (LAG) or interfaces that participate in a LAG.
Examples
The following example enables 802.1X authentication globally on all interfaces.
History
Release version Command history
dot1x port-control
Controls the port authorization state and configures the port control type to activate authentication on an 802.1X-enabled
interface.
Syntax
dot1x port-control { auto | force-authorized | force-unauthorized }
Command Default
By default, the port state is authorized.
Parameters
auto
Allows a client on an 802.1X-enabled interface to negotiate authentication. The port is placed in the unauthorized state
until authentication takes places between the client and the authentication server. When authentication is enabled by
using the dot1x authentication command and the client is authenticated by the authentication server, the port state
changes to the authorized. The controlled port remains in the authorized state until the client logs off.
force-authorized
Unconditionally places the controlled port in the authorized state, allowing all traffic to pass between the client and the
authenticator. This also allows connection from multiple clients.
force-unauthorized
Unconditionally places the controlled port in the unauthorized state, denying any traffic to pass between the client and
the authenticator.
Modes
Interface configuration mode
Usage Guidelines
Before activating authentication by specifying the auto option, you must remove any static ACLs or static VLANs configured on
the port.
802.1x port authentication is not supported by Link Aggregation Group (LAG) or interfaces that participate in a LAG.
The no form of the command resets the port control type to the default state.
Examples
The following example configures the interface to unconditionally place the port in the unauthorized state until authentication
takes place between the client and authentication server. Once the client passes authentication, the port becomes authorized.
The following example configures the interface to unconditionally place the controlled port in the authorized state.
The following example configures the interface to unconditionally place the controlled port in the unauthorized state.
History
Release version Command history
dot1x quiet-period
Configures the interval that the device remains idle between a failed authentication attempt and a subsequent reauthentication
attempt.
Syntax
dot1x quiet-period seconds
no dot1x quiet-period
Command Default
The default quiet period is 60 seconds.
Parameters
seconds
Specifies the time between a failed authentication attempt and a subsequent reauthentication attempt. Valid values
range from 1 through 65535 seconds.
Modes
Interface configuration mode
Usage Guidelines
Changing the quiet-period interval to a number lower than the default can result in a faster response time.
Examples
The following example shows how to set the quiet time to 200 seconds.
History
Release version Command history
dot1x reauthenticate
Enables 802.1X reauthentication on a specific interface.
Syntax
dot1x reauthenticate interface ethernet slot/port
Parameters
interface ethernet slot/port
Specifies enabling reauthentication on an Ethernet interface. The interface is specified in slot and port number format;
when the device does not contain slots, the slot number must be 0.
Modes
Privileged EXEC mode
Examples
The following example enables reauthentication of a client connected to Ethernet interface 0/1.
History
Release version Command history
dot1x reauthentication
Enables periodic reauthentication of clients connected to an 802.1X-enabled interface.
Syntax
dot1x reauthentication
no dot1x reauthentication
Command Default
Periodic reauthentication is disabled.
Modes
Interface configuration mode
Usage Guidelines
When periodic reauthentication is enabled by using the dot1x reauthentication command, the device reauthenticates clients
every 3,600 seconds by default.
The reauthentication interval is configurable using the dot1x timeout command. The reauthentication interval configured by
using the dot1x timeout command takes precedence.
Examples
The following example enables 802.1x reauthentication of clients connected to Ethernet interface 0/1.
History
Release version Command history
dot1x reauthMax
Configures the maximum number of times that a port attempts 802.1x reauthentication before the port changes to the
unauthorized state.
Syntax
dot1x reauthMax number
no dot1x reauthMax
Command Default
By default, a port makes two 802.1x reauthentication attempts before changing to the unauthorized state,
Parameters
number
Specifies the maximum number of reauthentication attempts before the port goes to the unauthorized state. The range
is from 1 through 10.
Modes
Interface configuration mode
Usage Guidelines
The no dot1x reauthMax command restores the default setting.
Examples
The following example sets the maximum number of reauthentication attempts to 5 for Ethernet interface 0/1.
History
Release version Command history
Syntax
dot1x test eapol-capable interface ethernet slot/port
Parameters
interface ethernet slot/port
Specifies an Ethernet inteface for the readiness check. The interface is specified in slot and port number format; when
the device does not contain slots, the slot number must be 0.
Modes
Privileged EXEC mode
Usage Guidelines
This command monitors 802.1x activity on all the switch ports and displays information about the devices connected to the
ports that support 802.1x. You can use this command to determine if the devices connected to the switch ports are 802.1x-
capable. When you configure the dot1x test eapol-capable command on an 802.1x-enabled port, and the link comes up, the
port queries the connected client about its 802.1x capability. When the client responds with a notification packet, it is
designated as 802.1x-capable.
The readiness check can be sent on a port that handles multiple hosts (for example, a PC that is connected to an IP phone). The
readiness check is not available on a port that is configured by using the dot1x port-control force-unauthorized command.
The readiness check is typically used before 802.1x is enabled on the switch.
802.1x authentication cannot be initiated while the 802.1x readiness test is in progress.
The 802.1x readiness test cannot be initiated while 802.1x authentication is active.
802.1x readiness can be checked on a per-interface basis. It is not possible to do an 802.1x readiness check for all interfaces
at once.
Examples
The following example configures readiness check on an Ethernet interface (0/1), to determine if the devices connected to the
port are 802.1x-capable.
History
Release version Command history
Syntax
dot1x test timeout timeout
Command Default
The default timeout period for the 802.1X readiness test is 10 seconds.
Parameters
timeout
Specifies the readiness test timeout period in seconds. The valid range is from 1 through 65535.
Modes
Global configuration mode
Examples
The following example shows how to set the timeout period for the 802.1X readiness test to 30 seconds.
History
Release version Command history
dot1x timeout
Configures parameters for the 802.1x timeout period for client reauthentication and Extensible Authentication Protocol (EAP)
retransmissions.
Syntax
dot1x timeout { re-authperiod seconds | supp-timeout seconds | tx-period seconds }
Command Default
Timeout parameters are not applied to the device.
Parameters
re-authperiod seconds
Specifies the interval at which clients connected to 802.1X authentication enabled ports are periodically
reauthenticated. When periodic reauthentication is enabled using the dot1x reauthentication command, the device
reauthenticates the clients every 3,600 seconds by default. The re-authperiod option allows you to specify an
alternate time interval between reauthentication attempts. The reauthentication interval configured using the dot1x
timeout re-authperiod command takes precedence.
supp-timeout seconds
Specifies the EAP response timeout for 802.1x authentication. By default, when the device relays an EAP-Request
frame from the RADIUS server to the client, it expects to receive a response from the client within 30 seconds. If the
client does not respond within the allotted time, the device retransmits the EAP-Request frame to the client. The
timeout value for retransmission of EAP-Request frames to the client can be configured using the supp-timeout
seconds parameters.
tx-period seconds
Specifies the EAP request retransmission interval, in seconds. The valid range is from 1 through 65535 seconds. The
default value is 30 seconds.
By default, when the device does not receive an EAP response or identity frame from a client, the device waits 30
seconds, then retransmits the EAP request or identity frame. You can optionally change the amount of time the device
waits before retransmitting the EAP request or identity frame to the client. When the client does not send back an EAP
response or identity frame within 60 seconds, the device transmits another EAP request or identity frame.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables the 802.1x timeout period configuration.
Examples
The following example sets to 25 seconds, the time between reauthorization attempts on Ethernet interface 0/1.
The following example sets to 45 seconds, the switch-to-client retransmission time for the EAP request frame on Ethernet
interface 0/1.
The following example sets to 34 seconds, the waiting period (before retransmitting the request) for a response to an EAP
request or identity frame from the client on Ethernet interface 0/1.
History
Release version Command history
duplicate-mac-timer (EVPN)
Configures a duplicate MAC detection timer for the detection of continuous MAC moves for an Ethernet VPN (EVPN) instance.
Syntax
duplicate-mac-timer interval max-count interval
Parameters
interval
Specifies the duplicate MAC detection timer interval in seconds. Valid values range from 5 through 300. The default is
5.
max-count value
Specifies the maximum threshold of MAC moves that can occur within the configured time interval before the MAC
address is treated as a duplicate address and further advertisements for that MAC address are blocked. Valid values
range from 3 through 10. The default is 3.
Modes
EVPN instance configuration mode
Usage Guidelines
The no form of the command restores the default values.
Examples
The following example sets the duplicate MAC detection timer interval to 180 and the maximum count to 5 for the default
EVPN instance.
The following example restores the default duplicate MAC detection timer and maximum count values.
History
Release version Command history
Syntax
efa debug clear-config [ --device string | --help | --password string | --username string ]
Command Default
This command has no defaults.
Parameters
--device string
Specifies a comma-separated list of device IP addresses or hostnames.
--help
Provides help for command options.
--password string
Clears the password for a comma-separated list of device IP addresses or hostnames.
--username string
Clears the username for a comma-separated list of device IP addresses or hostnames.
Modes
TPVM configuration mode
Examples
This example clears all EFA configured parameters for three devices.
History
Release version Command history
efa deploy
Deploys the EFA application.
Syntax
efa deploy [ --help | --password string | --username string ]
Command Default
This command has no defaults.
Parameters
--help
Provides help for command options.
--password string
Specifies a password.
--username string
Specifies a username.
Modes
TPVM configuration mode
Usage Guidelines
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
ATTENTION
This command causes TPVM to reboot.
The username and password are optional. The defaults "root" and "fibranne" are used if not specified.
Examples
This example deploys EFA.
History
Release version Command history
Syntax
efa device credentials update [ --device string | --help | --password string| --username string ]
Command Default
This command has no defaults.
Parameters
--device string
Specifies a comma-separated list of device IP addresses or hostnames.
--help
Provides help for command options.
--password string
Specifies the password for a comma-separated list of device IP addresses or hostnames.
--username string
Specifies the username for a comma-separated list of device IP addresses or hostnames.
Modes
TPVM configuration mode
Usage Guidelines
The keywords are required. Otherwise an error is thrown, as shown below.
Error: Required flag(s) "device", "password", "username" have/has not been set
Examples
This example updates credentials for all devices in the fabric.
History
Release version Command history
Syntax
efa execution show [ --id string ] | limit int32 [ --status [ all | failed | succeeded ]
Parameters
--id string
Filters execution according to the execution ID.
--limit int32
Limits the number of executions to be listed, where int32 is an unsigned integer (default is 10).
--status
Specifies whether the status of execution shows failed or succeeded.
all
Specifies all executions. This is the default, returning both succeeded and failed executions.
failed
Specifies failed executions.
succeeded
Specifies succeded executions.
Modes
TPVM configuration mode
Usage Guidelines
Examples
This is example output without any arguments.
+--------------------------------------+---------------+----------------------+---------------------------
+---------------------------+
id: 68fec530-b7da-4606-a7a9-b4648019dbfe
command: configure add
parameters: {spines: leaves:[“10.24.73.204”,”1.24.73.205”]}
status: Failed
duration: 768ms
errors: “No Spine devices”
History
The efa execution show command displays the following information.
Syntax
efa fabric configure { --leaf list-of-leaf-ips --spine list-of-spine-ips } [ --persist | --force ] [ --username string --password
string ]
efa fabric configure { --rack pair-of-rack-ips } [ --persist | --force ] [ --username string --password string ]
Command Default
No devices are added, deleted, or configured by default. See the Usage Guidelines.
Parameters
--leaf list-of-leaf-ips
Specifies a comma-separated list of leaf management IP addresses in an IP Clos topology.
--rack pair-of-rack-ips
Specifies a comma-separated list of rack IP addresses in a non-Clos topology, taking a pair of IP addresses of the
nodes that form an MCT pair.
--spine list-of-spine-ips
Specifies a comma-separated list of spine management IP addresses in an IP Clos topology.
--force
Replaces any conflicting configurations needed for fabric formation on the switch with the one inferred by the
application. This involves overwriting the following: ASNs based on a fabric template; IP addresses of physical,
loopback, and VE interfaces; overlay gateway configuration; EVPN instance; and MCT cluster configuration.
--persist
Executes copy running-config startup-config on all leaf and spine devices.
username string
Specifies a username. The default credentials used by the application are "admin" and "password". This option can be
used to override the default credentials. The credentials apply for all devices that are provided as part of the command.
In case the devices have different credentials, they can be added by means of a separate command.
password string
Specifies a password.
Modes
TPVM configuration mode
Usage Guidelines
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
Up to four rack pairs are supported in a non-Clos topology.
Examples
This IP Clos example adds leaf and spine nodes to the fabric and resolves conflicting configurations on the switch.
This non-Clos example configures a rack in the fabric and replaces conflicting configurations.
History
Release version Command history
Syntax
efa fabric deconfigure { --device list-of-device-ips } [ --persist ] [ --username string --password string ]
efa fabric deconfigure { --rack pair-of-rack-ips } [ --persist ] [ --username string --password string ]
Command Default
No devices are deleted by default.
Parameters
--device list-of-device-ips
Specifies a comma-separated ist of device IP addresses in an IP Clos topology.
--no-device-cleanup
Do not clean up the configurations on the devices. See the Usage Guidelines.
--rack pair-of-rack-ips
Specifies a comma-separated ist of rack IP addresses in a non-Clos topology.
--persist
Executes copy running-config startup-config on all leaf and spine devices.
username string
Specifies a username. The default credentials used by the application are "admin" and "password" . This option can be
used to override the default credentials. The credentials apply for all devices that are provided as part of the command.
In case the devices have different credentials, they can be added by means of a separate command.
password string
Specifies a password.
Modes
TPVM configuration mode
Usage Guidelines
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
ATTENTION
Exercise the --no-device-cleanup option with caution. Use it only when configuration and deconfiguration commands
are failing. This command can be used to clean up the devices from the database. No BGP or fabric link
configurations are deleted from the neighboring switches.
Examples
This example deletes racks from the fabric and resolves conflicting configurations on the switch.
History
Release version Command history
Syntax
efa fabric setting show [ --advanced ]
Parameters
--advanced
Displays advanced fabric parameters.
Modes
TPVM configuration mode
Command Output
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
Examples
This is example output for basic parameters in an IP Clos topology.
This is example output for advanced parameters, showing rack peer group configurations for a non-Clos topology.
History
Release version Command history
Syntax
efa fabric setting update {--allow-as-in string |--anycast-mac-address string |--arp-aging-timeout string |--bfd-multiplier
string |--bfd-rx string |--bfd-tx string |--bgp-multihop string |--configure-overlay-gateway string } |control-ve string|
control-vlan string |--duplicate-mac-timer string |--duplicate-mac-timer-max-count string |--help | --ip-mtu string |--
ipv6-anycast-mac-address value |--leaf-asn-block string |--leaf-peer-group string |--loopback-ip-range string | --
loopback-port-number string |--mac-aging-conversation-timeout string |--mac-aging-timeout string |--mac-move-
limit string |--max-paths string | --mct-port-channel string |--mctlink-ip-range string |--mtu string |--p2p-ip-type string
|--p2p-link-range string |--spine-asn-block string |--spine-peer-group string |--vni-auto-map string |--vteploopback-
port-number string |--l3-backup-ip-rangestring |--rack-asn-blockstring |--rack-peer-ebgp-groupstring |--rack-peer-
overlay-evpn-groupstring |--fabric-typestring}
Command Default
No command defaults apply.
Parameters
--allow-as-in string
Disables the AS_PATH check of the routes learned from the AS. Range is from 1 through 10.
--anycast-mac-address string
Specifies an IPv4 anycast MAC address in HHHH.HHHH.HHHH format.
--arp-aging-timeout string
Specifies how long an ARP entry stays in the cache. Range is from 60 through 100000 seconds.
--bfd-multiplier string
Specifies a multiplier for BFD detection time. Range is from 3 through 50.
--bfd-rx string
Specifies the BFD desired minimum receive interval in milliseconds. Range is from 50 through 30000.
--bfd-tx string
Specifies the BFD desired minimum transmit interval in milliseconds. Range is from 50 through 30000.
--bgp-multihop string
Specifies EBGP neighbors to allow when they are not on directly connected networks. Range is from 1 through 255.
--configure-overlay-gateway string
Specifies whether an overlay gateway is enabled or not. Options are "yes" or "no".
--control-ve string
Specifies a VLAN. Range is from 1 through 4090.
--control-vlan string
Specifies a VLAN. Range is from 1 through 4090.
--duplicate-mac-timer string
Specifies duplicate MAC timer.
--duplicate-mac-timer-max-count string
Specifies duplicate MAC timer max count.
--fabric-type
Specifies a fabric type. Options are "clos" and "non-clos".
--help
Specifies help for options for this command.
--ip-mtu string
Specifies an IPv4 or IPv6 MTU size in bytes for an SLX device. Range is from 1300 through 9194.
--ipv6-anycast-mac-address string
Specifies an IPv6 anycast MAC address in HHHH.HHHH.HHHH format.
--l3-backup-ip-range string
Specifies a range of Layer 3 backup IP addresses.
--leaf-asn-block string
Specifies a leaf ASN range, in comma-separated format.
--leaf-peer-group string
Specifies the name of a leaf peer group. Range is from 1 through 63 ASCII characters.
--loopback-ip-range string
Specifies a range of loopback IP addresses.
--loopback-port-number string
Specifies a loopback port number. Range is from 1 through 255.
--mac-aging-conversation-timeout string
Specifies the MAC conversational aging time in seconds. Range is from 60 through 100000. The default is 0.
--mac-aging-timeout string
Specifies the MAC aging time in seconds. Range is from 60 through 100000. The default is 0.
--mac-move-limit string
Specifies the MAC move detection limit. Range is from 5 through 500.
--max-paths string
Specifies the maximum number of paths for packet forwarding. Range is from 1 through 64.
--mct-port-channel string
Specifies a port-channel interface number. Range is from 1 through 1024.
--mctlink-ip-range string
Specifies a range of IP addresses.
--mtu string
Specifies the MTU size in bytes. Range is from 1548 through 9216.
--p2p-ip-type string
Specifies the IP type as numbered or unnumbered.
--rack-asn-block string
Specifies a rack ASN range, as a single AS or as comma-separated AS values.
--rack-peer-ebgp-group string
Specifies a rack peer EBGP group.
--rack-peer-overlay-evpn-group string
Specifies a rack peer overlay EVPN group.
--spine-asn-block string
Specifies a spine ASN range, as a single AS or as comma-separated AS values.
--spine-peer-group string
Specifies the name of a spine peer group. Range is from 1 through 63 ASCII characters.
--vni-auto-map string
Specifies whether VNI automapping used or not. Options are "yes" or "no".
--vtep-loopback-port-number string
Specifies a VTEP loopback port number. Range is from 1 through 255.
Modes
TPVM configuration mode
Usage Guidelines
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
Examples
This example specifies a range of leaf switches.
History
Release version Command history
Command Default
If not specified, the default (clos) supports IP Clos networks.
Parameters
--fabric-type
Specifies the IP Fabric as Clos or non-Clos.
clos
Supports an IP Clos network.
non-clos
Supports a non-Clos network.
Modes
TPVM configuration mode
Usage Guidelines
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
Examples
This example specifies a non-Clos IP Fabric.
History
Release version Command history
Syntax
efa fabric show
Modes
TPVM configuration mode
Examples
This example displays rack and device information for a non-Clos topology.
History
Release version Command history
efa supportsave
Creates a supportSave .zip package that contains the EFA database and execution logs.
Syntax
efa supportsave
Command Default
supportSave is not configured by default.
Modes
TPVM configuration mode
Usage Guidelines
This command is executed in TPVM configuration mode on one of the SLX switches within the fabric.
Examples
This example creates a supportSave .zip package that contains the EFA database and execution logs on the switch.
$ efa supportsave
History
Release version Command history
enable (PTP)
Enables or disables Precision Time Protocol (PTP) at the switch or interface level in global PTP configuration mode.
Syntax
enable
no enable
Modes
Global PTP configuration mode
Usage Guidelines
At the switch level:
• The default state is disabled. When it is enabled by the enable command in PTP configuration mode, the PTP feature
is enabled on the switch. A PTP-aware switch functions as a boundary clock device, whereas a PTP-unaware switch
functions as a Layer 2 switch.
• When PTP is disabled, the switch behaves as a PTP-unaware device, and PTP frames that are received are discarded.
• PTP can run on a fabric that consists of both PTP-aware and PTP-unaware switches. When a PTP-unaware switch is
present, the end system in the communication path of these devices does not receive the level of clock accuracy
supported by this feature.
• The no form of this command at the switch level disables existing PTP configurations and reverts to PTP-unaware
mode.
Examples
To enter PTP configuration mode and enable PTP on the switch:
History
Release version Command history
encoding (Telemetry)
Designates the encoding format for telemetry streaming.
Syntax
encoding { gpb | json }
Command Default
Encoding is set to Google protobuf (GPB).
Parameters
gpb
Designates GPB encoding for telemetry streaming.
json
Designates JavaScript Object Notation (JSON) encoding for telemetry streaming.
Modes
Telemetry collector configuration mode
Usage Guidelines
This command designates the encoding format for telemetry streaming.
Examples
Example of setting the encoding format to JSON.
History
Release version Command history
encryption-level
Configures the encryption level to use for communication with the Remote Authentication Dial-In User Service (RADIUS) server.
Syntax
encryption-level encryption_level_value
no encryption-level
Command Default
The default value is 7. A value of 7 specifies that the key is stored in encrypted format.
Parameters
encryption_level_value
Specifies the encryption level value for shared-secret key operation. Valid values are 0 and 7. A value of 0 specifies
that the key is stored in cleartext format. A value of 7 specifies that the key is stored in encrypted format. The default
value is 7.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the default value.
NOTE
Before downgrading to a software version that does not support the encryption-level command, set the encryption
level value to 0; otherwise, the firmware download displays an error requesting that the encryption level value is set to
0.
Examples
The following example shows how to specify an encryption level of 0 so that the shared secret key is stored in cleartext format.
History
Release version Command history
endpoint-tracking enable
Enables endpoint tracking on a Layer 2 (switchport) interface.
Syntax
endpoint-tracking enable
no endpoint-tracking enable
Command Default
Endpoint tracking is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
The interface must be configured as a Layer 2 (switchport) interface.
Use the endpoint-tracking timeout reauth-period command to configure the reauthentication timer.
Examples
The following example configures endpoint tracking configured on an interface configured as a switchport.
History
Release version Command history
Syntax
endpoint-tracking timeout reauth-period seconds
Command Default
The endpoint tracking reauthentication timer is disabled.
Parameters
seconds
Specifies an integer from 300 to 86400. The default is 300.
Modes
Interface subtype configuration mode
Usage Guidelines
The interface must be configured as a Layer 2 (switchport) interface.
If you enter this command when endpoint tracking is disabled, the timer is configured but endpoint tracking remains disabled.
You must enter the endpoint-tracking enable command to enable endpoint tracking.
Examples
The following example configures endpoint tracking configured on an interface configured as a switchport, and configures the
reauthentication timer.
History
Release version Command history
enforce-first-as
Enforces the use of the first autonomous system (AS) path for external BGP (eBGP) routes.
Syntax
enforce-first-as
no enforce-first-as
Modes
BGP configuration mode
Usage Guidelines
This command causes the device to discard updates received from eBGP peers that do not list their AS number as the first AS
path segment in the AS_PATH attribute of the incoming route.
Examples
The following example configures the device to enforce the use of the first AS path.
History
Release version Command history
error-disable-timeout enable
Enables the timer to bring the interface out of the error-disabled state.
Syntax
error-disable-timeout enable
Modes
Spanning tree configuration mode
Usage Guidelines
When the Spanning Tree Protocol (STP) Bridge Protocol Data Unit (BPDU) guard disables a port, the port remains in the
disabled state unless the port is enabled manually. This command allows you to enable the interface from the disabled state.
Examples
To bring the interface out of the disabled state:
History
Release version Command history
error-disable-timeout interval
Sets the timeout interval for errors on an interface.
Syntax
error-disable-timeout interval seconds
no error-disable-timeout interval
Command Default
300 seconds
Parameters
seconds
Specifies the time for the interface to time out. Valid values range from 10 through 1000000 seconds.
Modes
Spanning tree configuration mode
Usage Guidelines
Enter no error-disable-timeout interval to return to the default setting.
Examples
Follow these examples to set the timeout interval.
History
Release version Command history
Syntax
esi auto lacp
Modes
Cluster client configuration mode
Usage Guidelines
Use the no form of the command to delete the ESI setting.
ESI is generated when the partner LACP MAC and port key is learned.
Examples
The following example shows the setting of the ESI for the cluster client.
History
Release version Command history
event-handler
Creates or accesses an event-handler profile, which can execute a Python script when a specified trigger occurs.
Syntax
event-handler event-handler-name [ action python-script file-name ]
no event-handler event-handler-name
Command Default
No event-handler profile is enabled.
Parameters
event-handler-name
Specifies the name of the event-handler profile. Valid values can have from 1 through 32 characters. The first
character must be alphabetic.
description description-text
Specifies a string describing the event-handler profile. The string can be 1 through 128 ASCII characters in length. Do
not use the ? character. If you need to use ! or \, precede each with \.
trigger trigger-id
Defines an event-handler trigger and specifies an ID number for the trigger. Valid values are 1 through 100, and must
be unique per event-handler profile. When the trigger-condition occurs, a Python script is run.
raslog raslog-id
Specifies a RASlog message ID as the trigger.
pattern posix-ext-regex
Specifies a POSIX extended regular expression to search for a match within the specified RASlog
message ID. For examples, refer to the "trigger" topic.
Modes
Global configuration mode
Event-handler configuration mode for an existing event handler. (There is no need to enter the exit command to return to global
configuration mode.)
Usage Guidelines
You can create multiple event-handler profiles.
You can optionally specify a description, a trigger, or the Python script with this command; or specify them later.
An event-handler command creates or accesses an event-handler profile and can also define one of the following parameters:
• Description
• One trigger
• The Python-script action that runs on any trigger
You can also define the above parameters—including one or more triggers—from event-handler configuration mode.
Examples
The following example creates an event-handler profile and accesses its configuration mode.
History
Release version Command history
Syntax
event-handler abort action event-handler-name
Parameters
event-handler-name
Specifies the name of the event-handler profile. Valid values can have from 1 through 32 characters. The first
character must be alphabetic.
Modes
Privileged EXEC mode
Examples
The following command successfully aborted event-handler action "eh1".
History
Release version Command history
event-handler activate
Activates an event handler and accesses event-handler activation mode, from which you can enter advanced configuration
commands. You can also append the advanced commands to event-handler activate.
Syntax
event-handler activate event-handler-name
event-handler activate event-handler-name [ action-timeout minutes ] [ delay seconds ] [ iterations num-iterations ] [ interval
seconds ] [ trigger-mode mode ] [ trigger-function { OR | AND [ time-window seconds ] } ]
Command Default
No event handler is activated on the device.
Parameters
event-handler-name
Specifies the name of the event-handler profile. Valid values can have from 1 through 32 characters. The first
character must be alphabetic.
action-timeout minutes
Specifies the number of minutes to wait for an action-script to complete execution. If you specify "0", no timeout is set.
Valid timeout values are any positive integer.
delay seconds
Specifies a number of seconds from when a trigger is received until the execution of the specified action begins. Valid
values are 0 or a positive integer.
iterations num-iterations
Specifies the number of times an event-handler action is run, when triggered. Valid values are any positive integer. The
default value is 1.
interval seconds
Specifies the number of seconds between iterations of an event-handler action, if triggered. Valid values are 0 or a
positive integer. The default is 0.
trigger-mode mode
Specifies if an event-handler action can be triggered only once or more than once. The default is each time the trigger
condition occurs, the event-handler action is launched.
each-instance
The event-handler action is launched on each trigger instance received.
on-first-instance
As long as the device is running, the event-handler action is launched only once. Following a device restart,
the event-handler action can be triggered again.
only-once
For the duration of a device's configuration, the event-handler action is launched only once.
trigger-function
For an implementation of an event-handler profile, if multiple triggers are defined for an event-handler action, specifies
if the action runs only if all of the triggers occur; or if one is sufficient.
OR
The event-handler action runs if any of the triggers occur.
AND
The event-handler action runs only if all of the triggers occur.
time-window seconds
In seconds, specify the time window within which all of the triggers must occur in order that the
event-handler action runs. Once all triggers have been received and on each subsequent trigger
received, the action will be launched when the time difference between the latest trigger and the
oldest trigger is less than or equal to the configured time-window.
Modes
Global configuration mode
Event-handler activation mode for an existing event handler. (There is no need to enter the exit command.)
Usage Guidelines
You can activate up to 10 different event-handler profiles on a device.
A Python event-handler script runs only if all of the following occur:
• Using the copy command, copy the Python file to the flash:// location on the device.
• Using the event-handler command, create an event-handler profile.
• In configuration mode for that profile:
– Using the trigger command, create one or more triggers.
– Using the action command, specify the Python script that will be triggered.
• Using the event-handler activate command, activate an instance of the event handler.
• The trigger event occurs.
For additional usage guidelines regarding the advanced configuration commands, see the following topics:
• action-timeout
• delay
• iterations
• interval
• trigger-mode
• trigger-function
Following an initial triggering of an event-handler action, any subsequent trigger launches the action an additional time if the
following conditions are true:
• The trigger-mode parameter is set to the default each-instance.
• The subsequent trigger occurs within the specified time-window.
To inactivate an event-handler instance on a device, use the no form of this command. If an event-handler Python script is
running, it is executed to completion before inactivation of the event handler.
Examples
This example activates eventHandler1 on the device.
History
Release version Command history
evpn
Specifies an EVPN instance and enables EVPN instance configuration mode.
Syntax
evpn instance
no evpn instance
Command Default
This mode is disabled.
Modes
Global configuration mode
Parameters
instance
EVPN instance. Range is from 1 through 64 ASCII letters and numbers.
Usage Guidelines
Use the no form of this command to remove the EVPN instance.
Examples
The following example specifies an EVPN instance and enables EVPN instance configuration mode.
History
Release version Command history
evpn irb ve
Specifies an Ethernet VPN (EVPN) integrated routing and bridging (IRB) virtual Ethernet (VE) interface in a VRF for routing.
Syntax
evpn irb ve VE
no evpn irb ve VE
Command Default
This feature is not enabled.
Parameters
VE
VE interface number. Range is from 1 through 4096.
Modes
VRF configuration mode
Usage Guidelines
The IRB interface is the VE interface that is used for routing after tunnel termination. The IRB interface must belong to the
tenant VRF and be administratively up. It is not necessary to configure an IP address on the IRB interface.
Use the no form of this command to delete the VE interface.
Examples
The following example specifies an EVPN IRB VE interface.
History
Release version Command history
extend bridge-domain
Configures a switchport bridge domain (BD) or range of BDs for the tunnels to the containing site in VXLAN overlay gateway
site configurations.
Syntax
extend bridge-domain { add | remove } bd_id
no extend bridge-domain
Parameters
add
Specifies a BD ID or range of BD IDs to be added to a tunnel.
remove
Specifies a BD ID or range of BD IDs to be removed from a tunnel.
bd_id
A BD ID or range of BD IDs. See the Usage Guidelines.
Modes
VXLAN overlay gateway site configuration mode
Usage Guidelines
The VXLAN Network Identifier (VNI) classification is derived from the "map vlan" configuration of the parent overlay gateway.
This command results in the provisioning or unprovisioning of the VLANs. Use the no extend vlan vlan_id command to
unprovision a VLAN.
All of the VLAN IDs that are specified must be VLANs that have been mapped by means of the map vlan vlan_id vni vni
command on the parent overlay gateway, unless automatic VNI mapping has been enabled by means of the map vlan vni auto
command.
Use the no attach vlan vlan_id command to remove all switchport configurations from the tunnels to the containing site.
Examples
Use the no attach vlan vlan_id command to remove all switchport configurations from the tunnels to the containing
The following example configures a switchport VLAN and range of VLANs.
History
Release version Command history
extend vlan
Configures switchport VLANs for the tunnels to the containing site in VXLAN overlay gateway site configurations.
Syntax
extend vlan { add | remove } vlan_id
no extend vlan
Parameters
add
Specifies a VLAN ID or range of VLAN IDs to be added to a tunnel.
remove
Specifies a VLAN ID or range of VLAN IDs to be removed from a tunnel.
vlan_id
A VLAN ID or range of VLAN IDs. See the Usage Guidelines.
Modes
VXLAN overlay gateway site configuration mode
Usage Guidelines
The VXLAN Network Identifier (VNI) classification is derived from the "map vlan" configuration of the parent overlay gateway.
This command results in the provisioning or unprovisioning of the VLANs. Use the no extend vlan vlan_id command to
unprovision a VLAN.
All of the VLAN IDs that are specified must be VLANs that have been mapped by means of the map vlan vlan_id vni vni
command on the parent overlay gateway, unless automatic VNI mapping has been enabled by means of the map vlan vni auto
command.
Examples
The following example configures a switchport VLAN and range of VLANs.
History
Release version Command history
external-lsdb-limit (OSPFv2)
Configures the maximum size of the external link state database (LSDB).
Syntax
external-lsdb-limit value
no external-lsdb-limit
Parameters
value
Maximum size of the external LSDB. Valid values range from 1 through 14913080. The default is 14913080.
Modes
OSPF router configuration mode
Usage Guidelines
If you change the value, make sure to save the running-config file and reload the software. The change does not take effect until
you reload or reboot the software.
Examples
The following example sets the limit of the LSDB to 20000.
History
Release version Command history
external-lsdb-limit (OSPFv3)
Configures the maximum size of the external link state database (LSDB).
Syntax
external-lsdb-limit value
no external-lsdb-limit
Parameters
value
Maximum size of the external LSDB. Valid values range from 1 through 250000. The default is 250000.
Modes
OSPFv3 router configuration mode
Usage Guidelines
If you change the value, you must save the running-config file and reload the software. The change does not take effect until
you reload or reboot the software.
Examples
The following example sets the limit of the external LSDB to 15000.
History
Release version Command history
fast-external-fallover
Resets the session if a link to an eBGP peer goes down.
Syntax
fast-external-fallover
no fast-external-fallover
Modes
BGP configuration mode
Usage Guidelines
Use this command to terminate and reset external BGP sessions of a directly adjacent peer if the link to the peer goes down,
without waiting for the timer, set by the BGP timers command, to expire. This can improve BGP conversion time, but can also
lead to instability in the BGP routing table as a result of a flapping interface.
The no form of the command disables BGP fast external fallover.
Examples
The following example configures the device to reset the session if a link to an eBGP peer goes down.
History
Release version Command history
fec mode
Configures settings for forward error correction (FEC) on an interface.
Syntax
fec mode { auto | disabled | FC-FEC | RS-FEC }
Command Default
FEC mode is auto.
Parameters
auto
Specifies autonegotiaion mode.
disabled
Disables FEC.
FC-FEC
Specifies FEC for Fibre Channel support.
RS-FEC
Specifies Reed-Solomon FEC.
Modes
Interface configuration mode
Usage Guidelines
FC-FEC mode can be applied only on 25G interfaces.
Links belonging to physical ports with different FEC configurations can form LAGs, or port-channels. However, in the case of a
mismatch in the FEC status of the peer ports, the link will not come up.
When a port is administratively down, the current FEC status may not be displayed correctly.
Examples
The following example configures FC-FEC mode on a 25G interface.
History
Release version Command history
firmware activate
Activates the firmware that was downloaded with firmware download noactivate command.
Syntax
firmware activate
Command Default
Activation of the firmware is performed manually by default after a download.
Modes
Privileged EXEC mode
Usage Guidelines
By default, the firmware download command downloads the firmware to the system, reboots the system, and commits the
firmware automatically. You can specify the noactivate parameter to download the firmware to the system without activating it
(the node is not rebooted). The user can run the firmware activate command later to activate the firmware.
Examples
To activate firmware on the device:
History
Release version Command history
firmware commit
Commits a firmware upgrade.
Syntax
firmware commit
Modes
Privileged EXEC mode
Usage Guidelines
The firmware download command updates the secondary partitions only. When the firmware download command completes
successfully and the device reboots, the system swaps partitions. The primary partition (with the previous firmware) becomes
the secondary partition, and the secondary partition (with the new firmware) becomes the primary partition.
By default, firmware download automatically commits the firmware after the device reboots. If you disable auto-commit mode
when running firmware download, you must execute firmware commit to commit the new firmware to the secondary partition.
You must run the firmware download command with the nocommit parameter set for the following firmware commit operation
to succeed.
Examples
To commit the firmware:
History
Release version Command history
firmware download
Downloads the firmware on the local device.
Syntax
firmware download { default-config | ftp | scp | sftp | tftp | usb | interactive } [ manual ] [ nocommit ] [ noreboot ] [ noactivate ]
[ coldboot ] host { hostname | host_ip_address } user username password password directory directory [ file file_name ]
[ use-vrf vrf-name] ]
Command Default
By default, firmware download downloads the firmware to the system, reboots the system, and commits the firmware
automatically. The user can specify noactivate to download the firmware to the system without activating it (the node is not
rebooted). You can run the firmware activate command later to activate the firmware.
Parameters
default-config
Sets the configuration back to default .
interactive
Runs firmware download in interactive mode. You are prompted for input.
manual
Updates a single management module in a chassis with two management modules. You must log in to the
management module through its dedicated management IP address. This parameter is ignored when issued on a
Top-of-Rack (ToR) device or in a chassis with only one management module.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary
partition. You must execute the firmware commit command manually to propagate the new image to the secondary
partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device manually.
noactivate
Downloads the firmware to the system without activating it, so the node is not automatically rebooted. You can run the
firmware activate command later to activate the firmware.
coldboot
Downloads the firmware to the system and reboots both the active and standby MMs.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file, release.plist, is used.
user username
Specifies the user login name for the host.
password password
Specifies the account password.
use-vrf vrf-id
Use this option to specify the name of the VRF where the host is located. If this option is not set, mgmt-vrf is used by
default.
Modes
Privileged EXEC mode
Usage Guidelines
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
Examples
Example of firmware download without options (ISSU):
This command will use the ISSU protocol to upgrade the system. It will cause a WARM reboot and will
require that existing telnet, secure telnet or SSH sessions be restarted.
This command will cause a cold/disruptive reboot and will require that existing telnet, secure telnet
or SSH sessions be restarted.
This command will cause a cold/disruptive reboot and will require that existing telnet, secure telnet
or SSH sessions be restarted.
History
Release version Command history
Syntax
firmware download ftp [ coldboot ] [ manual ] [ noactivate ] [ nocommit ] [ noreboot ] host { hostname | host_ip_address }
use-vrf vrf-name user username password password directory directory [ file file_name ]
Command Default
By default, downloads the firmware to the system, reboots the system, and commits the firmware automatically. The user can
specify noactivatefirmware download to download the firmware to the system without activating it (the node is not rebooted).
The user can run firmware activate later to activate the firmware.
Parameters
coldboot
Downloads the firmware to the system and reboots both the device.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file, release.plist, is used.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
manual
Updates a single management module in a chassis with two management modules. You must log in to the
management module through its dedicated management IP address. This parameter is ignored when issued on a
compact device or in a chassis with only one management module.
noactivate
Performs a firmware download without activation on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary
partition. You must execute the firmware commit command manually to propagate the new image to the secondary
partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device manually. If auto-
commit mode was disabled, you must perform a manual firmware commit operation after the device comes back up.
password password
Specifies the account password.
use-vrf vrf-name
Specifies a VRF.
user username
Specifies the user login name for the host.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host.
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
Examples
This example downloads firmware by means of FTP and specifies a path to the directory where the firmware is located. A user
login name is specified for the host and an account password is specified.
History
Release version Command history
Syntax
firmware download interactive
Command Default
By default, firmware download downloads the firmware to the system, reboots the system, and commits the firmware
automatically.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You can run this command
interactively or provide the parameters on the command line.
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
Examples
To perform a firmware download in interactive mode using default parameters:
This command will cause a cold/disruptive reboot and will require that existing telnet, secure telnet
or SSH sessions be restarted.
History
Release version Command history
Syntax
firmware download scp [ coldboot ] [ manual ] [ nocommit ] [ noreboot ] host { hostname | host_ip_address } user username
password password directory directory [ file file_name ] [ noactivate ] [ use-vrf vrf-name]
Command Default
A filename is optional. If no filename is specified, release.plist, is used.
Parameters
coldboot
Downloads the firmware to the system and reboots the device.
manual
Performs a firmware download on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary
partition. You must execute the firmware commit command manually to propagate the new image to the secondary
partition. (Skips auto-commit after firmware download.)
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device manually. If auto-
commit mode was disabled, you must perform a manual firmware commit operation after the device comes back up.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
user username
Specifies the user login name for the host.
password password
Specifies the account password.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Specifies the firmware .plist file. This parameter is optional.
noactivate
Performs a firmware download without activation on the local device.
use-vrf vrf-id
Use this option to specify the name of the VRF where the host is located. If this option is not set, mgmt-vrf is used by
default.
Modes
Privileged EXEC mode.
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You can run this command
interactively or provide the parameters on the command line.
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
If the firmware download is interrupted because of an unexpected reboot as a result of a software error or power failure, the
command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before starting another
firmware download.
Examples
This example downloads firmware by means of SCP and specifies a path to the directory where the firmware is located. A user
login name is specified for the host and an account password is specified.
History
Release version Command history
Syntax
firmware download sftp [ coldboot ] directory directory [ manual ] [ nocommit ] [ noreboot ] host { hostname |
host_ip_address } user username password password directory directory [ file file_name ] [ noactivate ] [ use-vrf vrf-
name]
Parameters
coldboot
Downloads the firmware to the system and reboots both the device.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file filename
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file, release.plist, is used.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
manual
Performs a firmware download on the local switch.
noactivate
Performs a firmware download without activation on the local switch.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary
partition. You must execute the firmware commit command manually to propagate the new image to the secondary
partition. (Skips auto-commit after firmware download.)
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the switch manually. If auto-
commit mode was disabled, you must perform a manual firmware commit operation after the switch comes back up.
password password
Specifies the account password.
user username
Specifies the user login name for the host.
use-vrf vrf-id
Use this option to specify the name of the VRF where the host is located. If this option is not set, mgmt-vrf is used by
default.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You can run this command
interactively or provide the parameters on the command line.
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
If the firmware download is interrupted because of an unexpected reboot as a result of a software error or power failure, the
command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before starting another
firmware download.
Examples
This example downloads firmware by means of SFTP and specifies a path to the directory where the firmware is located. A user
login name is specified for the host and an account password is specified.
History
Release version Command history
Syntax
firmware download tftp [ coldboot ] directory directory [ manual ] [ nocommit ] [ noreboot ] host { hostname |
host_ip_address } user username password password directory directory [ file file_name ] [ noactivate ] [ use-vrf vrf-
name]
Parameters
coldboot
Downloads the firmware to the system and reboots both the active and standby MMs.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file filename
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file, release.plist, is used.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
manual
Performs a firmware download on the local device.
noactivate
Performs a firmware download without activation on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary
partition. You must execute the firmware commit command manually to propagate the new image to the secondary
partition. (Skips auto-commit after firmware download.)
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device manually. If auto-
commit mode was disabled, you must perform a manual firmware commit operation after the device comes back up.
password password
Specifies the account password.
user username
Specifies the user login name for the host.
use-vrf vrf-id
Use this option to specify the name of the VRF where the host is located. If this option is not set, mgmt-vrf is used by
default.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You can run this command
interactively or provide the parameters on the command line.
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
If the firmware download is interrupted because of an unexpected reboot as a result of a software error or power failure, the
command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before starting another
firmware download.
Examples
This example downloads firmware by means of TFTP and specifies a path to the directory where the firmware is located. The
host is specified by IP address and a firmware .plist file is specified.
History
Release version Command history
Syntax
firmware download usb [ coldboot ] [ noactivate ] [ nocommit ] [ noreboot ] [ manual ] directory directory
Command Default
By default, the firmware download process reboots the system and activates the new image. Finally, the process performs a
firmware commit operation to copy the new image to the other partition.
Parameters
coldboot
Downloads the firmware to the system and reboots both the active and standby MMs. Caution: Do not use this option
unless instructed to do so by Extreme Technical Support.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
manual
Updates a single management module in a chassis with two management modules. You must log in to the
management module through its dedicated management IP address. This parameter is ignored when issued on a
Top-of-Rack (ToR) device or in a chassis with only one management module.
noactivate
Performs a firmware download without activation on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only to the primary
partition. You must execute the firmware commit command manually to propagate the new image to the secondary
partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device manually. If auto-
commit mode was disabled, you must perform a manual firmware commit operation after the device comes back up.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You can run this command
interactively or provide the parameters on the command line.
You can use one of the following options for firmware upgrade/downgrade; ISSU, coldboot, or default-config.
By default, if you enter the firmware download command without any options, the command invokes ISSU to upgrade the entire
system. ISSU involves an High Availability failover of the active management module and is non-disruptive. In contrast, both of
the coldboot and default-config options involve system reboots and are disruptive to traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to the default settings during
the firmware upgrade process.
If the firmware download command is interrupted because of an unexpected reboot, such as a result of a software error or
power failure, the command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before
beginning another firmware download.
If the firmware download is interrupted because of an unexpected reboot as a result of a software error or power failure, the
command automatically recovers the corrupted secondary partition. Wait for the recovery to complete before starting another
firmware download.
Examples
To download firmware from an attached USB device using the command line:
History
Release version Command history
firmware recover
Recovers the previous firmware version on the device if a firmware upgrade was unsuccessful.
Syntax
firmware recover
Modes
Privileged EXEC mode
Usage Guidelines
This command reverts the operation that was performed using the firmware download "noactivate" option.
If you invoke a noactivate firmware download, the firmware is loaded to the secondary node without swapping partitions. If
firmware recover is executed, it performs a forceful commit.
Examples
To recover firmware on the device:
History
Release version Command history
firmware restore
Swaps the partition and reboots the device.
Syntax
firmware restore
Modes
Privileged EXEC mode
Usage Guidelines
CAUTION
Do not use this command unless instructed by Extreme Technical Support.
Use this command to restore the previously active firmware image. You can run this command only if auto-commit mode was
disabled during the firmware download. After a firmware download and a reboot (with auto-commit mode disabled), the
downloaded firmware becomes active. If you do not want to commit the firmware, use the firmware restore command.
This command reboots the device and reactivates the previous firmware. After reboot, all primary and secondary partitions
restore the previous firmware image.
This command causes the device to boot up with its older firmware. Later, the image in the primary partition is automatically
committed to the secondary partition.
The firmware download command must have been run with the nocommit parameter for the firmware restore operation to
succeed.
Examples
The following example restores the previous firmware.
History
Release version Command history
flow
In a UDA profile, specifies the expected packet structure.
Syntax
flow header0 header0-type [ header1 header1-type [ header2 header2-type [ header3 header3-type [ header4 header4-
type [ header5 header5-type [ header6 header6-type [ header7 header7-type ] ] ] ] ] ] ]
no flow header0 header0-type [ header1 header1-type [ header2 header2-type [ header3 header3-type [ header4 header4-
type [ header5 header5-type [ header6 header6-type [ header7 header7-type ] ] ] ] ] ] ]
Command Default
In a UDA profile, no expected packet-header types are defined.
Parameters
header0,1,2,3,4,5,6,7 header0,1,2,3,4,5,6,7-type
Specifies expected packet header-types. For supported values, refer to the Usage Guidelines.
Modes
UDA-profile configuration mode
Usage Guidelines
Ths command is supported only in NPB system mode.
To modify a flow, delete the current flow and define a new one.
Examples
The following example configures a UDA profile, creates a flow, and specifies header types and fields.
History
Release version Command history
forward-delay
Specifies the time an interface spends in each of the listening and learning states.
Syntax
forward-delay seconds
no forward-delay
Command Default
15 seconds
Parameters
seconds
Specifies the time that an interface spends in the Spanning Tree Protocol (STP) learning and listening states. Valid
values range from 4 through 30 seconds.
Modes
Spanning tree configuration mode
Usage Guidelines
This command specifies how long the listening and learning states last before the interface begins the forwarding of all
spanning-tree instances.
When you change the spanning-tree forward-delay time, it affects all spanning-tree instances. When configuring the forward-
delay, the following relationship should be kept:
Examples
To configure the forward-delay time to 18 seconds:
History
Release version Command history
Syntax
graceful-restart
no graceful-restart
Command Default
This feature is disabled.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
Use this command under BGP address-family L2VPN EVPN configuration mode to enable or disable the graceful-restart
capability for all BGP neighbors in the address family. When this command is enabled, graceful-restart capability is negotiated
with neighbors in the BGP OPEN message when a session is established. If the neighbor advertises support for graceful
restart, that function is activated for that neighbor session. Otherwise, graceful restart is not activated for that session, even
though it is enabled locally.
BGP EVPN GR helper is supported. However, BGP EVPN GR router restart is not supported.
If the graceful-restart capability is enabled after a BGP session has been established, the neighbor session must be cleared for
graceful restart to take effect.
The no form of the command disables the BGP graceful-restart capability globally for all BGP neighbors in the address family.
Examples
The following example enables the BGP graceful restart capability.
History
Release version Command history
graceful-shutdown
Gracefully shuts down all BGP neighbors.
Syntax
graceful-shutdown seconds [ community value [ local-preference value ] | local-preference value [ community value ] |
route-map route-map-name ]
no graceful-shutdown seconds [ community value [ local-preference value ] | local-preference value [ community value ] |
route-map route-map-name ]
Command Default
Default graceful shutdown parameters are applied.
Parameters
seconds
Specifies the number of seconds in which the BGP graceful shutdown will occur. Valid values range from 30 through
600 seconds.
community value
Sets the community attribute for graceful shutdown. Valid values range from 1 through 4294967295.
local-preference value
Sets the local preference attribute for graceful shutdown. Valid values range from 0 through 4294967295.
route-map route-map-name
Specifies the route map for graceful shutdown attributes.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command de-activates graceful shutdown.
Examples
The following example gracefully shuts down all BGP neighbors and sets the graceful shutdown timer to 180 seconds.
The following example gracefully shuts down all BGP neighbors and sets the graceful shutdown timer to 600 seconds. The
route map “myroutemap” is specified for graceful shutdown attributes.
The following example gracefully shuts down all BGP neighbors and sets the graceful shutdown timer to 600 seconds. The
community attribute is set to 10.
History
Release version Command history
gtp-de-encapsulation
Enables the GPRS Tunneling Protocol (GTP) de-encapsulation feature on an interface.
Syntax
gtp-de-encapsulation
no gtp-de-encapsulation
Command Default
GTP de-encapsulation is not configured.
Modes
Physical interface configuration mode
Usage Guidelines
This feature is relevant only under NPB system mode, and supports only the GTPv1-U protocol.
When GTP de-encapsulation is performed on a frame, only one C-tag is retained in the L2 header. Other tags—802.1BR, VN-
Tag, S-Tag, and Outer C-Tag—are dropped from the L2 header.
If GTP de-encapsulation is applied to a frame, VLAN-header modification settings are ignored on that frame.
The final Frame Check Sequence (FCS) is updated with a recalculated CRC.
Examples
The following example enables the GTP de-encapsulation feature on an interface.
History
Release version Command history
hardware
Accesses hardware configuration mode to access the connector, port-group, and profile configuration modes.
Syntax
hardware
Modes
Global configuration mode
Examples
The following example shows the accessing of hardware configuration mode.
History
Release version Command history
hello (LLDP)
Sets the interval between LLDP hello messages
Syntax
hello seconds
no hello
Command Default
30 seconds
Parameters
seconds
Valid values range from 4 through 180 seconds.
Modes
Protocol LLDP configuration mode
Usage Guidelines
The LLDP hello messages can also be configured for a specific LLDP profile. When you apply an LLDP profile on an interface
using the lldp profile command, it overrides the global configuration. If a profile is not present, then the default global profile is
used until you create a valid profile.
Examples
The following example sets the time interval to 10 seconds between the transmissions.
The following example sets the time interval to 8 seconds between the transmissions for a specific LLDP profile.
History
Release version Command history
hello-time
Sets the interval between the hello Bridge Protocol Data Units (BPDUs) sent on an interface.
Syntax
hello-time seconds
no hello-time
Command Default
2 seconds
Parameters
seconds
Specifies the time interval between the hello BPDUs sent on an interface. Valid values range from 1 through 10
seconds.
Modes
Spanning tree configuration mode
Usage Guidelines
This command configures the spanning-tree bridge hello time, which determines how often the device broadcasts hello
messages to other devices.
If the VLAN parameter is not provided, the hello-time value is applied globally for all per-VLAN instances. But for the VLANs
which have been configured explicitly, the per-VLAN configuration takes precedence over the global configuration. When
configuring the hello-time, the max-age command setting must be greater than the hello-time setting. The following
relationship should be kept:
Examples
The following example configures spanning tree bridge hello time to 5 seconds.
History
Release version Command history
hold-time
Sets the time that a previously down backup VRRP router, which also must have a higher priority than the current master VRRP
router, will wait before assuming mastership of the virtual router.
Syntax
hold-time range
Command Default
0 seconds
Parameters
range
A value between 1 and 3600 seconds that specifies the time a formerly down backup router waits before assuming
mastership of the virtual router.
Modes
Virtual-router-group configuration mode
Usage Guidelines
The hold-time must be set to a number greater than the default of 0 seconds for this command to take effect.
This command can be used for both VRRP and VRRP-E.
Examples
The following example sets the hold time to 60 seconds for backup routers in a specific virtual router.
History
Release version Command history
host
Configures a Host IPv4 and IPv6 management IP address and default gateway.
Syntax
host ipv4 [ address ipv4-address | gateway gateway-address ]
Parameters
ipv4
Specifies Host IPv4 management IP or gateway.
ipv6
Specifies Host IPv6 management IP or gateway.
address ipv4-address/ipv6-address/prefix
Specifies IPv4 or IPv6 address for the Host management interface.
gateway ipv4-address/ipv6-gateway-address
Specifies IPv4 or IPv6 gateway for the Host management interface.
Modes
Privileged EXEC mode
Examples
The following example creates a Host IPv4 management IP address and default gateway.
History
Release version Command history
Syntax
host-table aging-mode conversational
Command Default
Conversational ARP/ND is enabled.
Modes
Global configuration mode
Usage Guidelines
You can change the aging-time value from the 300 second default—either before or during enablement—by entering the host-
table aging-time conversational command.
If conversational ARP/ND is not enabled, make sure that the software ARP/ND cache size is less than the hardware profile limit.
Upon disablement, the conversational ARP/ND timers no longer apply: All current entries become permanent as do all new
entries.
Examples
The following example enables conversational ARP/ND.
History
Release version Command history
Syntax
host-table aging-time conversational seconds
Command Default
If conversational ARP/ND is enabled (by entering the host-table aging-mode conversational command), the default aging-
time value is 300 seconds.
Parameters
seconds
Specifes the aging-time value for conversational ARP/ND. Values range from 60 through 100000 seconds. The
default is 300.
Modes
Global configuration mode
Usage Guidelines
You can modify the aging-time value either before or after enabling conversational ARP/ND.
Pre-existing entries age out using the old configured value. A changed age-time configuration applies only entries added
following the change.
To restore the default aging-time value of 300 seconds, enter the no form of this command.
Examples
The following example sets the aging-time value to 600 seconds and then enables conversational ARP/ND.
History
Release version Command history
http server
Configures HTTP or HTTPS service on a device.
Syntax
http server use-vrf vrf-name [ secure-and-plain ] [ shutdown ]
Parameters
use-vrf vrf-name
Specifies a user-defined VRF.
secure-and-plain
Allows the enabling or disabling of both HTTP and HTTPS simultaneously. The HTTPS certificate must be installed
for this option to function correctly.
shutdown
Disables HTTP or HTTPS service.
Modes
Global configuration mode
Usage Guidelines
Use the http server command with the use-vrf parameter to enable HTTP or HTTPS service and associate it with the specified
VRF. The use-vrf parameter configures HTTP or HTTPS service for the specified VRF only. Service for that VRF is enabled or
disabled with no effect on service for other VRFs.
Use the http server command with the use-vrf and secure-and-plain parameters to enable both HTTP and HTTPS service for
the specified VRF. The secure-and-plain parameter allows you to enable HTTP and HTTPS simultaneously. Without this
option, you may only enable HTTP or HTTPS, but not both.
Use the http server command with the use-vrf and shutdown parameters to disable HTTP or HTTPS service for the specified
VRF. When both HTTP and HTTPS are enabled, executing the http server command with the use-vrf and shutdown
parameters disables both HTTP and HTTPS at the same time.
Use the no http server command with the use-vrf parameter to disable HTTP or HTTPS service and remove its association
with the specified VRF. You can disable service for any VRF, including the management VRF. Disabling service for the
management VRF is allowed, but removing the server's association with the management VRF is not allowed.
Use the no http server command with the use-vrf and secure-and-plain parameters to disable HTTP and run HTTPS alone.
This form of the command removes the secure-and-plain option from the running configuration.
Use the http server command with the shutdown parameter to disable HTTP or HTTPS service on the management VRF. Use
the no http server command with the shutdown parameter to re-enable HTTP or HTTPS service on management VRF.
HTTPS crypto certificates are required to enable HTTPS mode. HTTPS crypto certificates determine whether the service is
HTTP or HTTPS.
Examples
The following example creates and enables HTTP or HTTPS service on a device and specifies using a user-defined VRF
(myvrf).
The following example creates and enables both HTTP and HTTPS service on a device for a user-defined VRF.
When both HTTP and HTTPS service are enabled, the following command disables HTTP and runs HTTPS alone.
The following example disables HTTP or HTTPS service (or both HTTP and HTTPS services when both are enabled) on a
device for a user-defined VRF.
The following example enables HTTP or HTTPS service on an device for a user-defined VRF when service is disabled.
The following example disables HTTP or HTTPS service on a device for a user-defined VRF and removes its association with
that VRF.
The following example disables HTTP or HTTPS service on a device for the management VRF.
The following example enables HTTP or HTTPS service on a device for the management VRF.
History
Release version Command history
insight enable
Configures a port-channel as an insight interface.
Syntax
insight enable
no insight enable
Command Default
The insight interface is down until it is added to a port-channel by means of this command.
Modes
Interface configuration mode
Usage Guidelines
Use the no form of this command to disable an insight interface on the port-channel.
Examples
This example uses the insight enable command to enable an insight interface on a port-channel.
Use the show interface port-channel and show port-channel commands to confirm the configuration.
History
Release version Command history
install-igp-cost
Configures the device to use the IGP cost instead of the default BGP Multi-Exit Discriminator (MED) value as the route cost
when the route is added to the Routing Table Manager (RTM).
Syntax
install-igp-cost
no install-igp-cost
Modes
BGP configuration mode
Usage Guidelines
By default, BGP uses the BGP MED value as the route cost when the route is added to the RTM. Use this command to change
the default to the IGP cost.
The no form of the command restores the defaults.
Examples
The following example configures the device to compare MEDs.
History
Release version Command history
instance
Maps a VLAN to a Multiple Spanning Tree Protocol (MSTP) instance. You can group a set of VLANs to an instance.
Syntax
instance instance_id [ vlan vlan_id | priority priority_id ]
no instance
Command Default
The priority value is 32768.
Parameters
instance_id
Specifies the MSTP instance. Valid values range from 1 through 31.
vlan vlan_id
Specifies the VLAN to map an MSTP instance. Refer to the Usage Guidelines.
priority priority_id
Specifies the priority for the specified instance. Valid values range from 0 through 61440. The priority values
can be set only in increments of 4096.
Modes
Spanning tree MSTP configuration mode
Usage Guidelines
The following rules apply:
• VLANs must be created before mapping to instances.
• The VLAN instance mapping is removed from the configuration if the underlying VLANs are deleted.
Enter no instance to remove the VLAN mapping from the MSTP instance.
CAUTION
This command can be used only after the VLAN is
defined.
Examples
The following example maps a VLAN to an MTSP instance.
History
Release version Command history
interface (telemetry)
Specifies monitored interfaces for telemetry profile-types.
Syntax
interface { ethernet | port-channel } all
Command Default
No interfaces are defined and the profile is inactive.
Parameters
ethernet
Specifies ethernet interfaces.
port-channel
(Supported only for the interface and pbr profile types) Specifies port-channel interfaces.
all
Monitors all device interfaces.
add
Adds interfaces for monitoring.
except
Monitors all interfaces except for the ones specified.
remove
Removes the specified interfaces from monitoring.
none
Monitors no interfaces.
interfaces (ethernet)
Specifies physical interfaces, up to 1000 characters. The supported options are:
• slot/port, for example, 0/1
• slot/port1-port2, for example, 0/1-5
• slot/port1:breakout1-breakout2, for example, 0/4:3-4
interfaces (port-channel)
(Supported only for the interface and pbr profile types) Specifies port-channel interfaces. The supported options are:
• number, for example, 10
• number-number, for example, 5-8
Modes
Telemetry profile configuration mode
Usage Guidelines
(For the enhanced-queue-discard-pkts, interface, lldp, pbr, and queue profile types) Without this parameter configured, the
profile has no effect. Other profile types do not support the interface command.
To specify a combination of interfaces and interface ranges, separate them with commas.
To specify both ethernet and port-channel interfaces, use both an interface ethernet and an interface port-channel command.
Examples
The following example adds a range of ports and a port for monitoring.
History
Release version Command history
interface ethernet
Configures an Ethernet interface
Syntax
interface ethernet { slot/port }
Command Default
No Ethernet interface is configured.
Parameters
slot/port
Specifies a slot and port. Slot must be 0 for devices that do not contain line cards.
Modes
Global configuration mode
Examples
To configure interface Ethernet 0/1 on a device that does not contain line cards:
History
Release version Command history
interface loopback
Configures a loopback interface.
Syntax
interface loopback port_number
Command Default
A loopback interface is not configured.
Parameters
port_number
Specifies the port number for the loopback interface. Range is 1 through 255.
Modes
Global configuration mode
Usage Guidelines
A loopback is a logical interface traditionally used to ensure stable routing operations.
Use the no form of this command to remove the specified loopback interface.
Use the no form of this command with a port parameter to remove the specified loopback interface.
Examples
The following example creates a loopback interface with a port number of 25.
History
Release version Command history
interface management
Accesses management interface configuration mode for the specified management interface.
Syntax
interface management 0
Parameters
0
Accesses the configuration mode for management interface 0.
Modes
Global configuration mode
Usage Guidelines
The mode allows you to configure the parameters of the specified management interface.
Examples
The following example accesses the interface management mode for management interface 0.
History
Release version Command history
interface port-channel
Configures a port-channel interface.
Syntax
interface port-channel number
Command Default
No port-channel interface is configured.
Parameters
number
Specifies a port-channel. Range is from 1 through 1024.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to disable the interface.
Examples
To configure a port-channel interface:
History
Release version Command history
interface ve
Configures a virtual Ethernet (VE) interface.
Syntax
interface ve vlan_id
no interface ve vlan_id
Parameters
vlan_id
Specifies the corresponding VLAN that must already be created before the VE interface can be created. Refer to the
Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Before you can configure a VE interface, you must create a corresponding VLAN. The VE interface must use the corresponding
VLAN ID.
Examples
The following example shows the steps needed to create a VE interface with the VLAN ID of 56. This example assumes that
VLAN 56 has already been created.
History
Release version Command history
interval
For an implementation of an event-handler profile, specifies the number of seconds between iterations of an event-handler
action, if triggered.
Syntax
interval seconds
no interval
Command Default
Iterations occur with no interval between them.
Parameters
seconds
Specifies the number of seconds between iterations of an event-handler action, if triggered. Valid values are 0 or a
positive integer.
Modes
Event-handler activation mode
Usage Guidelines
The interval command is effective only if the iterations value is non-zero.
The no form of this command resets the interval setting to the default 0 seconds.
Examples
The following example sets the number of iterations to 3 and specifies an interval of 10 seconds between each iteration.
History
Release version Command history
interval (telemetry)
Configures the interval delay for telemetry data streaming.
Syntax
interval seconds
no interval
Command Default
For the interface profile-type, the default value is 30 seconds.
For the system-utilization and the pbr profile-types, the default value is 60 seconds.
Parameters
seconds
Specifies the streaming interval. The range of values, in five-second increments:
• For the interface profile-type, from 10 through 3600 seconds.
• For the system-utilization profile-type, from 60 through 14400 seconds.
• For the pbr profile-type and the queue profile-types, from 240 through 2400 seconds.
Modes
Telemetry profile configuration mode
Usage Guidelines
To reset the interval to the default value, use the no interval command.
Examples
Typical command execution.
History
Release version Command history
ip access-group (general)
Applies rules specified in an IPv4 access control list (ACL) to traffic entering or exiting an interface.
Syntax
ip access-group ACLname { in | out } [ switched | routed ]
Parameters
ACLname
Specifies the name of the standard or extended IPv4 ACL.
in
Applies the ACL to incoming switched and routed traffic.
out
Applies the ACL to outgoing routed traffic.
switched
Filters only switched traffic. This parameter is not valid for the management interface.
routed
Filters only routed traffic. This parameter is not valid for the management interface.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to apply an IPv4 ACL to one of the following interface types:
• User interfaces
– (Ingress only) Physical Ethernet interfaces
– (Ingress only) Logical interfaces (LAGs)
– Virtual Ethernet interfaces (VEs)
• The management interface
You can apply a maximum of two ACLs to the management interface, as follows:
• One ingress IPv4 ACL
• One ingress IPv6 ACL
You can apply an ACL to multiple interfaces. And you can apply an ACL twice—ingress and egress—to a given user interface.
Examples
The following example applies an ingress IP ACL on an Ethernet interface:
History
Release version Command history
ip access-group (overlay)
Applies rules specified in an IPv4 ACL to traffic entering or traversing a tunnel.
Syntax
ip access-group ACLname
no ip access-group ACLname
Parameters
ACLname
Specifies the name of the standard or extended IPv4 ACL.
Modes
Overlay transit configuration mode
Usage Guidelines
This command is supported in overlay-policy maps applied both for overlay transit and for overlay gateway.
Examples
The following example configures an IP ACL and an overlay class map. Then the policy map is created and a stanza (#10) is
added. This stanza uses the class map "tunnel-group-1" to identify the gateway and specifies the IP ACL "test" on the flows
within the tunnel. Finally there is a creation of the overlay gateway "gw2" and the overlay policy is applied, using the overlay-
service-policy in command . The policy map can also applied to the overlay-transit (using the same command).
History
Release version Command history
ip access-list
Creates a standard or extended IPv4 access control list (ACL). In ACLs, you can define rules that permit or deny network traffic
based on criteria that you specify.
Syntax
ip access-list { standard | extended } ACLname
Parameters
standard | extended
Specifies one of the following types of access lists:
standard
Contains rules that permit or deny traffic based on source addresses that you specify. The rules are applicable
to all ports of the specified addresses.
extended
Contains rules that permit or deny traffic according to source and destination addresses, as well as other
parameters. For example, you can also filter by port, protocol (TCP or UDP), and TCP flags.
ACLname
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63 characters in length,
and must begin with an alphanumeric character. No special characters are allowed, except for the underscore and
hyphen.
Modes
Global configuration mode
Usage Guidelines
An ACL name can be up to 63 characters long, and must begin with a–z, A–Z or 0–9. You can also use underscore (_) or
hyphen (-) in an ACL name, but not as the first character.
After you create an ACL, use the seq command to create filtering rules for that ACL.
To delete an ACL, use the no form of this command. You can delete an ACL only after you first remove it from all interfaces to
which it is applied, using a no access-group command.
Examples
The following example creates an IPv4 standard ACL.
History
Release version Command history
ip address
Configures an IP address on an interface.
Syntax
ip address ip-address/mask [ secondary ] [ ospf-ignore ] [ospf-active ]
no ip address [ ip-address/mask ]
Parameters
ip-address
Specifies the IP address.
mask
Specifies the mask for the associated IP subnet. Dotted-decimal notation is not supported. For non-loopback
interfaces, valid values are from 1 through 31. For loopback interfaces, the only valid value is 32.
secondary
Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is
the primary IP address.
ospf-ignore
Disables adjacency formation with OSPF neighbors and disables advertisement of the interface to OSPF.
ospf-passive
Disables adjacency formation with OSPF neighbors but does not disable advertisement of the interface to OSPF.
Modes
Interface configuration mode
Management interface configuration mode
Usage Guidelines
• Use this command to configure a primary or secondary IP address for a specific interface. You can also use this
command to prevent OSPF from running on specified subnets. Multiple primary IP addresses are supported on an
interface.
• You can use this command to configure a primary or secondary IP address for a management interface.
• For a management interface, only one primary IP address is supported. Secondary IP addresses are not supported.
• A primary IP address cannot overlap with a previously configured IP subnet.
• A primary IP address must be configured before you configure a secondary IP address in the same subnet.
• To remove the configured static or DHCP address, enter no ip address.
• The no form of the command removes a specific IP address from the interface.
Examples
The following example configures a primary IP address on a specified Ethernet interface.
History
Release version Command history
ip address (VXLAN)
Specifies the destination IPv4 address of a tunnel in VXLAN overlay gateway site configurations.
Syntax
ip address IPv4_address
no ip address [ IPv4_address ]
Parameters
IPv4_address
IPv4 address of the destination tunnel.
Modes
VXLAN overlay gateway site configuration mode
Usage Guidelines
The tunnel mode and the source IP address are derived from the parent overlay gateway.
To change an IP addresses, you must first remove the existing address, by means of the no ip address IPv4_address or the no
ip address commands. This also deletes all tunnels to the site.
Only one IPv4 address is allowed. The following IPv4 addresses are not allowed:
• Broadcast addresses (0.0.0.0 through 0.255.255.255)
• Localhost loopback addresses (127.0.0.0 through 127.255.255.255)
• Multicast addresses (224.0.0.0 through 239.255.255.255)
• Reserved addresses (240.0.0.0 through 255.255.,255.255)
Examples
To specify an IPv4 address of a destination tunnel:
History
Release version Command history
ip anycast-address
Configures an anycast-gateway IPv4 address on an interface, which uses the gateway IPv4 address for the host.
Syntax
ip anycast-address { IPv4-address/ mask }
no ip anycast-address
Command Default
No address is configured.
Parameters
IPv4-address / mask
IPv4 address and mask.
Modes
interface configuration mode on a virtual Ethernet (VE) interface.
Usage Guidelines
An IPv4 and IPv6 anycast MAC address cannot be configured as the same MAC address.
Use the no form of this command to delete the configured IPv4 anycast address from the interface.
Examples
To configure an IPv4 address and mask on a virtual Ethernet (VE) interface:
History
Release version Command history
ip arp-aging-timeout
Sets how long a dynamic Address Resolution Protocol (ARP) entry stays in the ARP cache. The aging timer is reset each time
an ARP reply is received.
Syntax
ip arp-aging-timeout value
no ip arp-aging-timeout
Command Default
ARP aging timeout is globally enabled and set to 25 minutes.
Parameters
value
Specifies how long an ARP entry stays in the ARP cache. Values range from 0 through 240 minutes.
Modes
Interface subtype configuration mode
Usage Guidelines
When the device places an entry in the ARP cache, the device also starts an aging timer for the entry. The aging timer ensures
that the ARP cache does not retain learned entries that are no longer valid. An entry can become invalid when the device with
the MAC address of the entry is no longer on the network.
Aging out affects dynamic (learned) entries only. Static entries do not age out.
You can modify the ARP aging timeout only at the interface level, but not at the global level.
The no form of the command restores the default aging timeout of 25 minutes.
Examples
The following command sets the ARP aging timeout to 100 minutes on an interface.
The following command restores the ARP aging timeout to the default value of 25 minutes on an interface.
History
Release version Command history
ip arp inspection
Enables Dynamic ARP Inspection (DAI) on a VLAN.
Syntax
ip arp inspection
no ip arp inspection
Command Default
DAI is disabled.
Modes
VLAN configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC addresses are accepted only if
all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
Examples
The following example applies ARP_ACL_01 to VLAN 200 and enables DAI.
History
Release version Command history
Syntax
ip arp inspection filter ACL-name
Command Default
No ARP ACL is applied.
Parameters
ACL-name
Specifies which ACL is applied to the VLAN.
Modes
VLAN configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC addresses are accepted only if
all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
The no form of the command removes the current ARP ACL from the VLAN.
Examples
The following example applies an ARP ACL named ARP_ACL_01 to VLAN 200.
History
Release version Command history
Syntax
ip arp inspection trust
Command Default
The interface is untrusted.
Modes
Interface subtype configuration mode
Usage Guidelines
This command is supported only on Layer 2 physical or port-channel interfaces.
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC addresses are accepted only if
all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
Examples
The following example configures an Ethernet interface as trusted.
History
Release version Command history
ip arp learn-any
Enables address-resolution protocol (ARP) learning from any ARP request.
Syntax
ip arp learn-any
no ip arp learn-any
Command Default
Default ARP learning
Modes
VE configuration mode
Usage Guidelines
This command is effective only on a Layer 3 interface.
This command enables learning from any ARP request (not necessarily targeted to my ip address).
Examples
The following example enables learn-any on VE 100.
History
Release version Command history
ip as-path access-list
Configures an AS-path access control list (ACL), specifies the community name, and whether to permit or deny traffic.
Syntax
ip as-path access-list string { deny regular-expression | permit regular-expression } [ seq seq-value ]
Parameters
string
Specifies an ACL name, from 1 to 32 ASCII characters in length.
deny regular-expression
Denies a matching pattern based on a regular expression, a string inside quotes.
permit regular-expression
Permits a matching pattern based on a regular expression, a string inside quotes.
seq seq-value
Specifies a sequence value. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
Regular expressions must be enclosed in quotes.
Examples
The following example creates an AS-path ACL that permits a matching pattern and specifies a regular expression.
History
Release version Command history
ip community-list extended
Configures a community access control list (ACL), specifies the community name, and whether to permit or deny traffic,
including through the use of a regular expression.
Syntax
ip community-list extended community-list-name { deny string | permit string } [ seq seq ]
Parameters
community-list-name
Specifies an ACL, from 1 through 32 ASCII characters in length.
deny regular-expression
Denies a matching pattern based on a regular expression, a string inside quotes.
permit regular-expression
Permits a matching pattern based on a regular expression, a string inside quotes.
seq seq-value
Specifies a sequence value. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
Unlike a standard community list, this command does accept a regular expression as long as the string is enclosed in quotes.
Examples
The following example creates an extended community list.
History
Release version Command history
ip community-list standard
Configures a community access control list (ACL), specifies the community number or type, and whether to permit or deny
traffic.
Syntax
ip community-list standard community-list-name { deny [ community-number | AA:NN ] | permit community-number } [ seq
seq-value ] [ internet | local-as | no-advertise | no-export ]
ip community-list standard community-list-name { deny | permit } { community-number | AA:NN | internet | local-as | no-
advertise | no-export }
ip community-list standard community-list-name seq seq-value { deny | permit } { community-number | AA:NN | internet |
local-as | no-advertise | no-export }
Parameters
community-list-name
Range is from 1 through 32 ASCII characters.
deny
Denies a matching pattern based on a regular expression.
permit
Permits a matching pattern based on a regular expression.
community-number
Specifies a community number. Range is from 1 through 4294967295.
AA : NN
Specifies an autonomous system number and network number, configured as 2-byte numbers separated by a colon.
internet
Specifies the Internet community.
no-export
Specifies a community of sub-ASs within a confederation. Routes with this community can be exported to other sub-
ASs in the same confederation but not outside the confederation to other ASs or otherwise sent to EBGP neighbors.
local-as
Specifies a local sub-AS within the confederation. Routes with this community can be advertised only within the local
sub-AS.
no-advertise
Specifies that routes with this community cannot be advertised to any other BGP4 devices at all.
seq seq-value
Speccifies a sequence value. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
A standard community list does not accept a regular expression.
There are two ways to delete a filter from the list. The first is by sequence number parameter no ip community-list standard
community-list-name seq seq-value. The second is executing the syntax no ip community-list standard community-list-
name , resulting in all filters within the community list, as well as the community list container, being removed from the
configuration database.
Examples
The following example creates a standard community list.
History
Release version Command history
Syntax
ip dhcp relay address ip-addr [ use-vrf vrf-name ]
Parameters
ip-addr
IPv4 address of the DHCP server where the DHCP client requests are to be forwarded.
use-vrf
Use this option if the VRF where the DHCP server is located is different from the VRF of the interface where the client
is connected.
vrf-name
VRF name.
Modes
Interface configuration mode
Usage Guidelines
This command uses the IPv4 address of the DHCP server where the DHCP client requests are to be forwarded.
Enter the command while in interface configuration mode for a VE or Ethernet interface where you want to configure the IP
DHCP Relay. Configure up to sixteen DHCP server IP addresses per interface.
Use the no version of this command to remove the IP DHCP relay from the interface. If the use-vrf option is not used, it is
assumed that the DHCP server and interface where the client is connected are on the same VRF.
Examples
The following example configures an IP DHCP Relay address on a Ve interface.
History
Release version Command history
Syntax
ip dhcp relay gateway address ip-addr
Parameters
ip-addr
IPv4 gateway address of the DHCP server where the DHCP client requests are to be forwarded.
Modes
Interface configuration mode
Usage Guidelines
Use this command to configure the IP DHCP Relay on the switch Layer 3 gateway interface using the IPv4 address of the
DHCP server where the DHCP client requests are to be forwarded.
Use the noversion of this command to remove the IP DHCP Relay from the interface.
Examples
To configure an IP DHCP Relay address on an interface:
History
Release version Command history
Syntax
ip dhcp relay information option
Command Default
DHCP Relay Agent Information Option 82 is not enabled.
Modes
VLAN configuration mode
Usage Guidelines
Use the no form of this command to disable DHCP Relay Agent Information Option 82.
Examples
The following example enables DHCP Relay Agent Information Option 82 on a VLAN.
The following example disables DHCP Relay Agent Information Option 82 on a VLAN.
History
Release version Command history
ip dns
Configures the Domain Name System (DNS) domain name and the primary and secondary name server IP addresses.
Syntax
ip dns { domain-name domain-name | name-server ip-address-of-name-server }
Parameters
domain-name domain-name
Specifies the DNS domain name.
name-server ip-address-of-name-server
Specifies the IP address of the name server. IPv6 and IPv4 addresses are supported.
Modes
Global configuration mode
Usage Guidelines
• Your first run of ip dns name-server specifies the default IP gateway address. Your second run of ip dns name-server
specifies the secondary IP gateway address.
• Name servers can only be entered or removed one at a time. The newly entered name server will append to the
existing name server.
• The no form of the command with the domain-name parameter disables IP directed broadcasts for a specific domain.
• The no form of the command with the name-server parameter deletes a name server definition.
Examples
The following example configures the DNS domain name and the primary name server IP address.
History
Release version Command history
ip icmp rate-limiting
Limits the rate at which IPv4 Internet Control Message Protocol (ICMP) messages are sent on a network.
Syntax
ip icmp rate-limiting milliseconds
no ip icmp rate-limiting
Command Default
This command is enabled on the management port, but is disabled on the front-end ports.
Parameters
milliseconds
Time interval per ICMP packet in milliseconds. The range is from 0 through 4294967295. The default is 1000.
Modes
Interface configuration mode
Usage Guidelines
This is an interface-specific configuration.
The no form of the command will revert to the default setting. Set the interval to 0 to disable IPv4 ICMP rate-limiting.
Examples
The following example enables IPv4 ICMP rate-limiting on an Ethernet interface.
History
Release version Command history
ip icmp redirect
Enables IPv4 Internet Control Message Protocol (ICMP) Redirect messages, which request that packets be sent on an
alternative route.
Syntax
ip icmp redirect
no ip icmp redirect
Command Default
This command is enabled on both the management port and on the front-end ports.
Modes
Interface configuration mode
Usage Guidelines
This is an interface-specific configuration.
Examples
The following example enables IPv4 ICMP Redirect messages on an Ethernet interface.
History
Release version Command history
Syntax
ip igmp snooping enable
Modes
VLAN configuration mode
Usage Guidelines
IGMP snooping allows a network device to listen in on the IGMP conversation between hosts and routers. By listening to these
conversations, the switch maintains a map of which links need which IP multicast streams. Multicasts may be filtered from the
links which do not need them.
Enter no ip igmp snooping enable to disable snooping for a specific VLAN.
Examples
To enable IGMP on a VLAN:
History
Release version Command history
Syntax
ip igmp snooping fast-leave
Command Default
This command is disabled.
Modes
VLAN configuration mode.
Usage Guidelines
Enter no ip igmp snooping fast-leave to disable this function.
Examples
To enable snooping fast-leave for a specific VLAN:
device(config)# vlan 1
device(config-vlan-1)# ip igmp snooping fast-leave
History
Release version Command history
Syntax
ip igmp snooping last-member-query-count value
Command Default
The default value is 2.
Parameters
value
Range is from 2 through 10. The default is 2.
Modes
VLAN configuration mode
Usage Guidelines
The IGMP snooping query maximum response time is the length of time in seconds that the device will wait for an IGMP (V1 or
V2) response from an interface before concluding that the group member on that interface is down and removing it from the
group.
Examples
The following example sets the IGMP snooping last member query count.
History
Release version Command history
Syntax
ip igmp snooping last-member-query-interval value
Command Default
The default is 1000 ms.
Parameters
value
Sets the value in milliseconds. The range is 100 to 25500 milliseconds.
Modes
VLAN configuration mode
Usage Guidelines
When a leave is received, a group-specific query is sent. Last member query interval configuration controls the time interval
between last member queries sent.
Examples
The following example sets the IGMP snooping last member query interval.
History
Release version Command history
Syntax
ip igmp snooping mrouter interface { ethernet slot/port | port-channel interface number }
Parameters
ethernetslot/port
Specifies a valid port number.
port-channel number
Specifies the interface is a port-channel. Valid values range from 1 through 6144.
Modes
VLAN configuration mode
Usage Guidelines
A multicast router interface faces toward a multicast router or other Internet Group Management Protocol (IGMP) querier.
Examples
The following example configures a VLAN port member to be a multicast router interface.
History
Release version Command history
Syntax
ip igmp snooping querier enable
Command Default
IGMP snooping querier is disabled.
Modes
VLAN configuration mode
Usage Guidelines
Enter no ip igmp snooping querier enable to disable the IGMP snooping querier.
Examples
The following example enables the IGMP snooping querier on the VLAN.
History
Release version Command history
Syntax
ip igmp snooping query-interval seconds
Command Default
The default is 125 seconds.
Parameters
seconds
Sets the IGMP snooping query interval in seconds. The range is from 1 through 18000 seconds.
Modes
VLAN configuration mode
Usage Guidelines
The ip igmp snooping query-interval command allows you to modify the query interval, which specifies how often a device
enabled for active IGMP snooping sends group membership queries.
Examples
The following example sets the IGMP snooping query interval.
History
Release version Command history
Syntax
ip igmp snooping query-max-response-time seconds
Command Default
The default is 10 seconds.
Parameters
seconds
Specifies the IGMP snooping query maximum response time in seconds. The range is 1 to 25 seconds.
Modes
VLAN configuration mode
Usage Guidelines
The IGMP snooping query maximum response time is the length of time in seconds that the device will wait for an IGMP (V1 or
V2) response from an interface before concluding that the group member on that interface is down and removing it from the
group.
Examples
The following example sets the IGMP snooping query max response time.
History
Release version Command history
Syntax
ip igmp snooping restrict-unknown-multicast
Command Default
IGMP snooping restrict-unknown-multicast is enabled.
Modes
VLAN configuration mode
Usage Guidelines
The hardware profile ipv4-v6-mcast must be enabled, by means of the hardware-profile command.
Using the no ip igmp snooping restrict-unknown-multicast command will flood multicast traffic to all members of the VLAN.
Examples
To stop the flooding of unknown multicast traffic for a VLAN enter the following commands:
History
Release version Command history
Syntax
ip igmp snooping robustness-variable value
Command Default
See parameters.
Parameters
value
The number of general IGMP snooping queries sent before a multicast address is aged out. The range is from 2
through 10. The default is 2.
Modes
VLAN configuration mode
Usage Guidelines
This value determines the number of general IGMP snooping queries that are sent before a multicast address is aged out for
lack of a response. Use this command to configure the robustness variable. This command is supported on port-channel, and
VLAN interfaces.
The no form of the command restores the robustness variable value to 2 (the default).
Examples
The following example changes the robustness variable on a VLAN to 7.
History
Release version Command history
Syntax
ip igmp snooping startup-query-count value
Command Default
See Parameters.
Parameters
value
The number of queries sent at startup. The range is from 1 through 10. The default is 2.
Modes
VLAN configuration mode
Usage Guidelines
This command is useful when the IGMP querier starts the first time. This command is supported on port-channel and VLAN
interfaces.
Examples
The following example changes the IGMP startup query count on a VLAN from the default to 3.
History
Release version Command history
Syntax
ip igmp snooping startup-query-interval seconds
Command Default
See Parameters.
Parameters
seconds
The response time in seconds. Range is from 1 through 450. The default is 31.
Modes
VLAN configuration mode
Usage Guidelines
This command is useful when the IGMP querier starts the first time. This command is supported on port-channel and VLAN
interfaces.
The no form of the command restores the startup query interval to the default.
Examples
The following example sets the IGMP startup query interval for a VLAN to 200 seconds.
History
Release version Command history
Syntax
ip igmp snooping static-group { ip-address } {interface ethernet/port-channel }
Parameters
ip-address
Specifies the multicast address to be joined in the A.B.C.D format.
interface
Specifies the interface.
ethernet/port-channel
Specifies the interface type.
Modes
VLAN configuration mode
Usage Guidelines
A snooping-enabled VLAN cannot forward multicast traffic to ports that do not receive IGMP membership reports. If clients
cannot send reports, you can configure a static group which applies to specific ports. The static group allows packets to be
forwarded to the static group ports even though they have no client membership reports.
Examples
The following example sets the IGMP snooping static-group.
History
Release version Command history
ip interface
Configures a loopback or a virtual Ethernet (VE) interface as a Layer 3 interface for a VXLAN overlay gateway.
Syntax
ip interface { loopback loopback_id| ve ve_id vrrp-extended-group vrrp_id}
Command Default
This feature is not enabled.
Parameters
loopbackloopback_id
Specifies a loopback interface. Range is from 1 through 255.
veve_id
Specifies a VE interface. Range is from 1 through 4096.
vrrp-extended-groupvr_id
Specifies a virftual router identifier (VRID) for VRRP-E. Range is from 1 through 255.
Modes
VXLAN overlay gateway configuration mode.
Usage Guidelines
Use the no form of this command to delete a Layer 3 interface.
Examples
The following example configures a loopback interface as a Layer 3 interface.
The following example configures a VE interface as a Layer 3 interface and specifies a VRRP-E router ID.
History
Release version Command history
ip mtu
Sets the IP Maximum Transmission Unit (MTU) on an interface or globally.
Syntax
ip mtu size
no ip mtu
Command Default
The default IP MTU size is 1500 bytes.
Parameters
size
Specifies the size of an interface IP MTU. Values range from 1300 through 9194 bytes.
Modes
Global configuration mode
Usage Guidelines
This command can be executed both globally and on an interface. If it is executed globally, interface configurations take
precedence over the global configuration.
If the interface is part of a VE, change the IPv4 MTU only at the VE interface and not at the physical port. All member ports of a
VE inherit the VE-interface IPv4 MTU value.
The no form of the command reverts the MTU size to the default value.
Examples
The following example sets the IP MTU to 2000 bytes globally.
The following example sets the IP MTU to 2000 bytes on the specified Ethernet interface.
History
Release version Command history
ip ospf active
Sets a specific OSPF interface to active.
Syntax
ip ospf active
Modes
Interface subtype configuration mode
Usage Guidelines
Use the ip ospf active command on each interface participating in adjacency formation. This command overrides the global
passive setting on that interface, and enables transmission of OSPF control packets.
Examples
The following example sets a specific OSPFv2 Ethernet interface to active.
History
Release version Command history
ip ospf area
Enables OSPFv2 on an interface.
Syntax
ip ospf area area-id | ip-addr
no ip ospf area
Parameters
area-id
Area ID in decimal format. Valid values range from 1 through 2147483647.
ip-addr
Area ID in IP address format.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command disables OSPFv2 on the interface.
Examples
The following example enables a configured OSPFv2 area named 1 on a specific OSPFv2 virtual Ethernet (VE) interface.
History
Release version Command history
ip ospf auth-change-wait-time
Configures authentication-change hold time.
Syntax
ip ospf auth-change-wait-time wait-time
no ip ospf auth-change-wait-time
Parameters
wait-time
Time before an authentication change takes place. Valid values range from 0 to 14400 seconds. The default is 300
seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the authentication change hold time for the interface to which you are connected.
OSPFv2 provides graceful authentication change for the following types of authentication changes:
Changing authentication methods from one of the following to another of the following:
• Simple text password
• MD5 authentication
• No authentication
The no form of the command resets the wait time to the default of 300 seconds.
Examples
The following example sets the wait time to 400 seconds on a specific OSPF virtual Ethernet (VE) interface.
History
Release version Command history
ip ospf authentication-key
Configures simple password-based authentication for OSPF.
Syntax
ip ospf authentication-key password
no ip ospf authentication-key
Command Default
Authentication is disabled.
Parameters
password
OSPF processes password as a plain text password.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset simple password-based authentication on the OSPFv2 interface to which you are connected.
The no form of the command disables OSPFv2 authentication.
Examples
The following example configures an authentication key for an OSPF virtual Ethernet (VE) interface.
History
Release version Command history
ip ospf bfd
Enables Bidirectional Forwarding Detection (BFD) on a specific OSPFv2 interface.
Syntax
ip ospf bfd
no ip ospf bfd
Modes
Interface subtype configuration mode
Usage Guidelines
BFD sessions are initiated only if BFD is also enabled globally using the bfd command in OSPF router configuration mode. If
BFD is disabled using the no bfd command in OSPF router configuration mode, BFD sessions on specific OSPFv2 interfaces
are deregistered.
The no form of the command removes all BFD sessions from a specified interface.
Examples
The following example enables BFD on an OSPF Ethernet interface.
The following example disables BFD on an OSPF virtual Ethernet (VE) interface.
History
Release version Command history
ip ospf cost
Configures cost for a specific interface.
Syntax
ip ospf cost value
no ip ospf cost
Parameters
value
Cost value. Valid values range from 1 through 65535. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
If the cost is not configured with this command, OSPFv2 calculates the value from the reference and interface bandwidths.
Examples
The following example sets the cost to 520 on a specific Loopback interface.
History
Release version Command history
ip ospf database-filter
Configures filters for different types of outgoing Link State Advertisements (LSAs).
Syntax
ip ospf database-filter { all-external | all-summary-external { allow-default-and-type-4 | allow-default-out | out } }
Command Default
All filters are disabled.
Parameters
all-external
Blocks all external LSAs.
all-summary-external
Blocks all summary (Type 3) and external (type 5) LSAs.
allow-default-and-type-4
Allows default-route LSAs and Type 4 LSAs, but block all other LSAs.
allow-default-out
Allows default-route LSAs, but block all other LSAs.
out
Filters outgoing LSAs.
all-out
Blocks all LSAs.
Modes
Interface subtype configuration mode
Usage Guidelines
By default, the device floods all outbound LSAs on all the OSPF interfaces within an area. You can configure a filter to block
outbound LSAs on an OSPF interface. This feature is particularly useful when you want to block LSAs from some, but not all, of
the interfaces attached to the area. When enabled, this command blocks the specified outgoing LSAs on the interface. Some
cases where you might want to enable filters are:
• To control the information being advertised to the network.
• To use a passive router for debugging only.
NOTE
You cannot block LSAs on virtual links.
Examples
The following example applies a filter to block flooding of all LSAs on a specific OSPF Ethernet interface.
History
Release version Command history
ip ospf dead-interval
Configures the neighbor dead interval, which is the number of seconds that a neighbor router waits for a hello packet from the
device before declaring the router down.
Syntax
ip ospf dead-interval interval
no ip ospf dead-interval
Parameters
interval
Dead interval in seconds. Valid values range from 3 through 65535 seconds. The default is 40.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the dead interval, the hello interval is automatically changed to a value that is one fourth that of the new dead
interval, unless the hello interval is also explicitly configured using the ip ospf hello-interval command.
The running-config command displays only explicitly configured values of the hello interval, which means that a value that was
automatically changed as the result of a dead-interval change is not displayed.
Examples
The following example sets the dead interval to 200 on a specific OSPFv2 virtual Ethernet (VE) interface.
History
Release version Command history
ip ospf hello-interval
Configures the hello interval, which is the length of time between the transmission of hello packets that this interface sends to
neighbor routers.
Syntax
ip ospf hello-interval interval
no ip ospf hello-interval
Parameters
interval
Hello interval in seconds. Valid values range from 1 through 65535. The default is 10 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the hello interval, the dead interval is automatically changed to a value that is four times that of the new hello
interval, unless the dead interval is also explicitly configured using the ip ospf dead-interval command.
The running-config command displays only explicitly configured values of the dead interval, which means that a value that was
automatically changed as the result of a hello-interval change is not displayed.
Examples
The following example sets the hello interval to 50 on a specific OSPFv2 virtual Ethernet (VE) interface:
History
Release version Command history
ip ospf md5-authentication
Configures MD5 password and authentication change hold time.
Syntax
ip ospf md5-authentication { key-activation-wait-time wait-time | key-id id key password }
Parameters
key-activation-wait-time wait-time
Sets the time that OSPFv2 waits before activating a new MD5 key. This parameter provides a graceful transition from
one MD5 key to another without disturbing the network. All new packets transmitted after the wait time ends use the
newly configured MD5 Key. OSPFv2 packets that contain the old MD5 key are accepted for up to five minutes after
the new MD5 key is in operation. Valid values range from 0 to 14400 seconds.
key-id
Sets MD5 key.
id
Identifies the MD5 key ID. Valid values range from 1 and 255.
key password
Specifies the MD5 authentication ID and sets a password.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the MD5 password and/or authentication change hold time on the interface to which you are
connected.
By default, the authentication key is encrypted. If you want the authentication key to be in clear text, insert a 0 between
authentication-key and string. The software adds a prefix to the authentication key string in the configuration. For example, the
following portion of the code has the encrypted code "2".
Examples
The following example sets the time that OSPFv2 waits before activating a new MD5 key to 240 seconds on an Ethernet
interface.
The following example sets the MD5 key ID to 22 and a password “myospfpassword” on an Ethernet interface.
History
Release version Command history
ip ospf mtu-ignore
Enables or disables maximum transmission unit (MTU) match checking.
Syntax
ip ospf mtu-ignore
no ip ospf mtu-ignore
Modes
Interface subtype configuration mode
Usage Guidelines
In default operation, the IP MTU on both sides of an OSPFv2 link must be the same, and a check of the MTU is performed
when Hello packets are first exchanged.
Examples
The following example disables MTU-match checking on a specific OSPFv2 Ethernet interface.
The following example enables MTU-match checking on a specific OSPFv2 Ethernet interface.
History
Release version Command history
ip ospf network
Configures the network type for the interface. Point-to-point can support unnumbered links, which requires less processing by
OSPF.
Syntax
ip ospf network { broadcast | non-broadcast | point-to-point }
no ip ospf network
Command Default
Network type is broadcast.
Parameters
broadcast
Network type is broadcast.
non-broadcast
Network type is non-broadcast. An interface can be configured to send OSPF traffic to its neighbor as unicast packets
rather than multicast packets.
point-to-point
Network type is point-to-point.
Modes
Interface subtype configuration mode
Usage Guidelines
On a non-broadcast interface, the devices at either end of the interface must configure non-broadcast interface type and the
neighbor IP address. There is no restriction on the number of devices sharing a non-broadcast interface.
To configure an OSPF interface as a non-broadcast interface, the feature must be enabled on a physical interface or a VE,
following the ip ospf area statement, and then specify the IP address of the neighbor in the OSPF configuration. The non-
broadcast interface configuration must be done on the OSPF devices at either end of the link.
Examples
The following example configures an OSPFv2 point-to-point link on a specific OSPFv2 Ethernet interface.
The following example configures an OSPFv2 broadcast link on a specific OSPFv2 Ethernet interface.
History
Release version Command history
ip ospf passive
Sets a specific OSPFv2interface to passive.
Syntax
ip ospf passive
no ip ospf passive
Command Default
All OSPF interfaces are active.
Modes
Interface subtype configuration mode
Usage Guidelines
Passive interfaces accept and process all OSPF protocol traffic, but they do not send any traffic.
Examples
The following example sets a specific OSPFv2 Ethernet interface to passive.
History
Release version Command history
ip ospf priority
Configures priority for designated router (DR) election.
Syntax
ip ospf priority value
no ip ospf priority
Parameters
value
Priority value. Valid values range from 0 through 255. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
The OSPFv2 router assigned the highest priority becomes the designated router, and the OSPFv2 router with the second-
highest priority becomes the backup router.
Examples
The following example sets a priority of 10 for the OSPFv2 router that is connected to an OSPFv2 Virtual Ethernet (VE)
interface.
History
Release version Command history
ip ospf retransmit-interval
Configures the retransmit interval. The retransmit interval is the time between Link-State Advertisement (LSA) retransmissions
to adjacent routers for a given interface.
Syntax
ip ospf retransmit-interval interval
no ip ospf retransmit-interval
Parameters
interval
Retransmit interval in seconds. Valid values range from 0 through 3600 seconds. The default is 5 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command resets the retransmit interval to its default.
Examples
The following example sets the retransmit interval to 8 for all OSPFv2 devices on a specific OSPFv2 Ethernet interface.
History
Release version Command history
ip ospf transmit-delay
Configures transmit delay for link-update packets. The transmit delay is the estimated time required for OSPFv2 to send link-
state update packets on the interface to which you are connected.
Syntax
ip ospf transmit-delay value
no ip ospf transmit-delay
Parameters
value
Transmit delay in seconds. Valid values range from 0 through 3600 seconds. The default is 1 second.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example sets a transmit delay of 25 seconds for devices on a specific OSPFv2 Ethernet interface.
History
Release version Command history
ip policy route-map
Enables the IP route map.
Syntax
ip policy route-map map-name
Command Default
The IP route map is not enabled.
Parameters
map-name
Specifies the name of the IP route map.
Modes
Route map configuration mode
Usage Guidelines
The no form of the command disables the IP route map.
Examples
The following example enables the IP route map on a specific interface.
History
Release version Command history
ip port (telemetry)
Specifies the IPv4 or IPv6 address and port of a telemetry collector.
Syntax
ip ip-address port port-number
no ip
no ipv6
Command Default
No IPv4 or IPv6 address is designated.
Parameters
ip-address
Specifies the IPv4 address of a telemetry collector.
port port-number
Specifies a valid port number.
ipv6-address
Specifies the IPv6 address of a telemetry collector.
Modes
Telemetry-collector configuration mode
Usage Guidelines
To remove the IPv4 or IPv6 configuration from the collector, use the relevant no command.
Examples
The following example specifies an IPv4 address and port for the telemetry collector.
The following example specifies an IPv6 address and port for the telemetry collector.
History
Release version Command history
ip prefix-list
Command for adding and deleting a filter from a standard community.
Syntax
ip prefix-list name { seq sequence-number [ deny ip-prefix/prefix-length | permit ip-prefix/prefix-length ] ge ge-value [ le le-
value ] }
no ip prefix-list name
Parameters
seq sequence-number
Specifies an IPv4 prefix list sequence number. If you do not specify a sequence number, the software numbers them
in increments of 5, beginning with prefix list entry 5. The device interprets the prefix list entries in numerical order,
beginning with the lowest sequence number.
name
Permitted values are between 1 and 32 characters. Although the first character must be alphabetic, the others can be
alphanumeric, underscores (_) or minus signs (-).
deny ip-prefix/prefix-length
Denies a packet that contains a route specified in the prefix list. The prefix list matches only on the specified prefix/
prefix length, unless you use the ge ge-value or le le-value parameters.
permit ip-prefix/prefix-length
Permits a packet that contains a route specified in the prefix list. The prefix list matches only on the specified prefix/
prefix length, unless you use the ge ge-value or le le-value parameters.
ge ge-value
If you specify only ge ge-value, then the range is from ge-value to 32.
le-valuele le-value
If you specify only le le-value, then the range is from le-value to the prefix-length parameter.
Modes
Global configuration mode
Usage Guidelines
Enter no ip prefix-list name to disable this feature.
The ge-value or le-value you specify must meet the following condition for prefix-length:
If you do not specify le-value ge ge-value or le le-value, the prefix list matches only on the exact prefix you specify with the ip-
prefix/prefix-length parameter.
You are allowed to insert and delete rules anywhere in the ACL, but updates are not allowed. You can delete and add a new rule
at the same location to simulate an update of an already existing rule.
A list rule added without a sequence number is allocated a sequence number. The allocated sequence number will be N greater
than the largest sequence number of all the rules in the list where N is the increment value of 5. The rule add operation will fail if
the allocated sequence number is not in the allowed sequence number range.
You are not allowed to delete a prefix list if it is actively being used by a client (such as a routing protocol).
Examples
This example denies routes on 1.2.0.0/8, where the subnet mask length must be greater than or equal to 20 and less than or
equal to 28, and permits routes on 10.1.0.0/16.
History
Release version Command history
ip proxy-arp
Enables Proxy Address Resolution Protocol (APR) on an interface.
Syntax
ip proxy-arp
no ip proxy-arp
Command Default
Proxy ARP is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Proxy ARP enables a device to answer ARP requests from devices in one network on behalf of devices in another network.
Because ARP requests are MAC-layer broadcasts, they reach only the devices that are directly connected to the sender of the
ARP request. Therefore, ARP requests do not cross routers.
Examples
The following example enables Proxy ARP on a specified interface.
History
Release version Command history
ip receive access-group
Applies an IPv4 access control list (ACL) at global configuration level. Such receive-path ACLs filter incoming route-processor
traffic according to rules that you create, but do not filter data-path traffic.
Syntax
ip receive access-group acl-name in
Command Default
No receive-path ACLs are applied.
Parameters
acl-name
Specifies the name of the standard or extended IP access list.
in
Specifies ingress traffic.
Modes
Global configuration mode
Usage Guidelines
For both interface ACLs and receive-path ACLs, you use identical commands to create the ACLs. You also use identical
commands to define permit/deny/hard-drop rules in the ACLs. The only variance is the command you use to apply the ACL:
• To apply an interface ACL, from an interface-subtype configuration mode you use the { ip | ipv6 | mac } access-group
command.
• To apply a receive-path ACL, from global configuration mode you use the { ip | ipv6 } receive access-group
command.
Examples
The following example creates an IPv4 extended ACL, defines rules in the ACL, and applies it as a receive-path ACL.
device(conf-ipacl-ext)# exit
device(config)# ip receive access-group ipv4-receive-acl-example in
History
Release version Command history
ip route
Adds a static route to the IP routing table.
Syntax
ip route dest-ip-addr [ next-hop-vrf next-vrf-name ] next-hop-address [ metric ] [ distance distance ] [ tag tag-number ]
ip route dest-ip-addr { ethernet slot/port | ve ve-number} [ metric ] [ distance distance ] [ tag tag-number ]
no ip route dest-ip-addr { ethernet slot/port | ve ve-number } [ metric ] [ distance distance ] [ tag tag-number ]
Parameters
next-hop-vrf vrf-name
Specifies the name of the non-default VRF to be used as the next-hop gateway.
dest-ip-addr
Specifies the destination IPv4 address and mask in the format A.B.C.D/L (where "L" is the prefix length of the mask).
next-hop-addr
Specifies the IPv4 address of the next hop.
ethernet slot/port
Specifies the destination Ethernet port. Slot number must be 0 if the device does not contain slots.
next-hop-vrf next-vrf-name
VRF name of next hop.
ve vlan-id
Specifies the outgoing interface type as VE.
null 0
Configures the Layer 3 switch to drop IP packets to a specific network or host address by configuring a "null"
(sometimes called "null0") static route for the address.
metric
Specifies the cost metric of the route. Valid values range from 1 through 16. The default is 1.
distance distance
Specifies the administrative distance of the route. When comparing otherwise equal routes to a destination, supported
devices prefer lower administrative distances over higher ones. Valid values range from 1 through 254. The default is
1.
tag tag-number
Specifies the tag value of the route to use for route filtering with a route map. Valid values range from 0 through
4294967295. The default is 0.
Modes
Global configuration mode or VRF IPv4 address-family configuration mode
Usage Guidelines
The no form of the command followed by the route identifier removes a static route.
If you do not want to specify a next-hop IP address, you can instead specify a physical or virtual interface on the device. If you
specify an Ethernet port, the device forwards packets destined for the static route’s destination network to the specified
interface. Conceptually, this feature makes the destination network like a directly connected network, associated with a
supported-device interface.
NOTE
When you configure an interface as the next hop, an extra ARP entry is created for the destination IP
address.
For a default route, use the following as the destination IP address 0.0.0.0/0.
You can create a null route for traffic that should not be forwarded. To create a null route, use the key phrase null 0 as the next
hop.
Examples
The following example configures a static route to 10.95.7.0 addresses, using 10.95.6.157 as the next-hop gateway.
The following example configures a static route with an Ethernet interface as the destination.
The following example configures a null static route to drop packets destined for network 10.157.22.x.
History
Release version Command history
Syntax
ip route static bfd dest-ip-address source-ip-address [ interval transmit-time min-rx receive-time multiplier number ]
Command Default
BFD is not configured for an IP static route.
Parameters
dest-ip-address
Specifies the destination IP address.
source-ip-address
Specifies the source IP address.
interval transmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers. Valid values range from 50
through 30000. The default is 500.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers. Valid values range
from 50 through 30000. The default is 500.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer before BFD
determines that the connection to that peer is not operational. Valid values range from 3 through 50. The default is 3.
Modes
Address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The interval transmit-time and min-rx receive-time parameters are the intervals desired by the local device. The actual values in
use will be the negotiated values.
For single-hop static BFD sessions, timeout values are optional because all required information is available from the outgoing
interface. For multihop BFD sessions, if the configured interval and min-rx parameters conflict with those of an existing
session, the lower values are used.
If you configure a neighbor IP address and a source IP address that already exist in BFD, BFD overwrites the existing interval
values and multiplier for the IP addresses with the new values, on behalf of the static module.
Static BFD can be configured without configuring a static route to configure a BFD session. This is especially useful on BFD
neighbors when they have reachability from other neighbors via OSPF or BGP. You must configure different BFD sessions for
each ECMP path with the corresponding interface IP as the source IP address.
The no form of the command removes the configured BFD IP static route.
Examples
The following example configures a BFD session on an IP static route.
The following example configures a BFD session on an IP static route in a nondefault VRF instance.
History
Release version Command history
Syntax
ip route static bfd holdover-interval time
Parameters
time
Specifies BFD holdover interval in seconds. Valid values range from 1 through 30. The default is 0.
Modes
Address-family IPv4 unicast VRF configuration mode
Global configuration mode
Usage Guidelines
If the BFD session is restored within the specified time interval, no down notification is sent.
Use the ip route static bfd holdover-interval command in global configuration mode to set the BFD holdover interval globally
for static routes.
The no form of the command removes the configured BFD holdover interval from the configuration, and reverts to the default
value of 0.
Examples
The following example sets the BFD holdover interval globally for IP static routes to 15.
The following example removes the configured BFD holdover interval for IP static routes.
The following example sets the BFD holdover interval in a nondefault VRF instance.
History
Release version Command history
ip router-id
Changes the router ID that is already in configured.
Syntax
ip router-id A.B.C.D
no ip router-id A.B.C.D
Parameters
A.B.C.D
Specifies the IPv4 address that you want as the router ID.
Modes
Global configuration mode
Usage Guidelines
Though a device has IP addresses assigned to various interfaces, some routing protocols identify the device by the router ID
rather than the IP addresses assigned to the interfaces connected by the protocol.
The no form of the command removes the configured router ID and restores the default router ID.
Examples
The following example specifies the router ID as 192.158.1.2.
History
Release version Command history
ip vrrp-extended auth-type
Configures the type of authentication used on a Virtual Router Redundancy Protocol Extended (VRRP-E) interface.
Syntax
ip vrrp-extended auth-type md5-auth auth-text
Command Default
No authentication is configured for a VRRP-E interface.
Parameters
auth-type
Authentication type used to verify the password.
md5-auth auth-text
Configures MD5 authentication on the interface. The maximum length of the text string is 64 characters.
Modes
Virtual Ethernet (ve) interface configuration mode
Usage Guidelines
This configuration is for virtual Ethernet (ve) interfaces only.
If the md5-auth option is configured, syslog and SNMP traps are generated if a packet is being dropped due to MD5
authentication failure. Using MD5 authentication implies that the software does not need to run checksum verification on the
receiving device and can rely on the authentication code (message digest 5 algorithm) to verify the integrity of the VRRP-E
message header.
The no form of this command removes the VRRP-E authentication from the interface.
Examples
The following example configures MD5 authentication on Virtual Ethernet interface 20.
History
Release version Command history
Syntax
ipv6 access-group ACLname { in | out } [ switched | routed ]
Parameters
ACLname
Specifies the name of the standard or extended IPv6 access list.
in
Applies the ACL to incoming switched and routed traffic.
out
Applies the ACL to outgoing routed traffic.
switched
Filter only switched traffic. This parameter is not valid for the management interface.
routed
Filter only routed traffic. This parameter is not valid for the management interface.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to apply an IPv6 ACL to one of the following interface types:
• User interfaces
– (Ingress only) Physical Ethernet interfaces
– (Ingress only) Logical interfaces (LAGs)
– Virtual Ethernet interfaces (VEs)
• The management interface
You can apply a maximum of two ACLs to the management interface, as follows:
• One ingress IPv4 ACL
• One ingress IPv6 ACL
You can apply an ACL to multiple interfaces. And you can apply an ACL twice—ingress and egress—to a given user interface.
Examples
The following example applies an IPv6 ACL on an Ethernet interface to incoming traffic.
History
Release version Command history
Syntax
ipv6 access-group ACLname
Parameters
ACLname
Specifies the name of the standard or extended IPv6 access list.
Modes
Overlay gateway configuration mode
Usage Guidelines
This command is supported in overlay-policy maps applied for overlay gateway.
Examples
The following example configures an IPv6 ACL and an overlay class map. Then the policy map is created and a stanza (#10) is
added. This stanza uses the class map "tunnel-group-1" to identify the gateway and specifies the IPv6 ACL "fooIpv6" on the
flows within the tunnel. Finally there is a creation of the overlay gateway "gw2" and the overlay policy is applied, using the
overlay-service-policy in command . The policy map can also applied to the overlay-transit (using the same command).
History
Release version Command history
ipv6 access-list
Creates a standard or extended IPv6 access control list (ACL). In ACLs, you can define rules that permit or deny network traffic
based on criteria that you specify.
Syntax
ipv6 access-list { standard | extended } ACLname
Parameters
standard | extended
Specifies one of the following types of access lists:
standard
Contains rules that permit or deny traffic based on source addresses that you specify. The rules are applicable
to all ports of the specified addresses.
extended
Contains rules that permit or deny traffic according to source and destination addresses, as well as other
parameters. For example, you can also filter by port, protocol (TCP or UDP), and TCP flags.
ACLname
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63 characters in length,
and must begin with an alphanumeric character. No special characters are allowed, except for the underscore and
hyphen.
Modes
Global configuration mode
Usage Guidelines
An ACL name can be up to 63 characters long, and must begin with a–z, A–Z or 0–9. You can also use underscore (_) or
hyphen (-) in an ACL name, but not as the first character.
After you create an ACL, use the seq command to create filtering rules for that ACL.
To delete an ACL, use a no access-list command. You can delete an ACL only after you first remove it from all interfaces to
which it is applied, using a no access-group command.
ATTENTION
When this command is used for VXLAN overlay gateway services, the mask for destination and source IP addresses
must not exceed 64.
Examples
The following example creates an IPv6 standard ACL:
device# configure
device(config)# ipv6 access-list standard stdV6ACL1
device# configure
device(config)# ipv6 access-list extended ipv6_acl_1
device# configure
device(config)# ipv6 access-list standard stdV6ACL1
device(conf-ipv6-std)# seq 10 permit 2001:db8:85a3:0:0:8a2e:370:7334
device(conf-ipv6-std)# seq 11 deny any
device# configure
device(config)# no ipv6 access-list standard stdV6ACL1
History
Release version Command history
ipv6 address
Configure an IPv6 address for an interface.
Syntax
ipv6 address pv6-prefix//prefix-length [ secondary ] [ anycast | eui-64 ]
Parameters
ipv6-address
Specifies the IPv6 address.
ipv6-prefix
Specifies the IPv6 prefix address in this format: X:X::X:X/M.
prefix-length
A decimal value specifying the length of the IPv6 prefix.
secondary
Specifies that the address is a secondary address. A maximum of 253 secondary addresses can be configured.
anycast
Configures an address as an anycast address.
eui-64
Configures the global address with an EUI-64 interface ID in the low-order 64 bits. The interface ID is automatically
constructed in IEEE EUI-64 format using the interface's MAC address.
Modes
Interface configuration mode
Usage Guidelines
A secondary address cannot be configured on an interface unless the primary address is configured first.
The primary address cannot be deleted on an interface unless the secondary addresses are deleted first.
Examples
This example shows how to configure a primary, secondary global, or unique local IPv6 unicast address, including a manually
configured interface ID:
This example shows how to remove the IPv6 unicast address, including a manually configured interface ID from an interface:
History
Release version Command history
ipv6 anycast-address
Configures an anycast-gateway IPv6 address on an interface, which uses the gateway IPv6 address for the host.
Syntax
ipv6 anycast-address { IPv6-address/ mask }
no ipv6 anycast-address
Command Default
No address is configured.
Parameters
IPv6-address / mask
IPv6 address and mask.
Modes
interface configuration mode on a virtual Ethernet (VE) interface.
Usage Guidelines
An IPv4 and IPv6 anycast MAC address cannot be configured as the same MAC address.
Use the no form of this command to delete the configured IPv6 anycast address from the interface.
Examples
To configure an IPv6 address and mask on a virtual Ethernet (VE) interface:
History
Release version Command history
ipv6 anycast-gateway-mac
Configures an IPv6 anycast-gateway MAC address, which is used as a gateway MAC address for hosts.
Syntax
ipv6 anycast-gateway-mac { default-mac | MAC-address }
no ipv6 anycast-gateway-mac
Command Default
The default IPv6 MAC address is used.
Parameters
default-mac
Specifies the default IPv6 MAC address, 02e0.5200.0200.
MAC-address
A user-specified IPv6 MAC address.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to delete a configured MAC address and revert to the default.
The default MAC address is obtained from a range of locally administered MAC addresses, and it is assumed not to conflict
with other MAC addresses.
Examples
To enable configuration of a default IPv6 anycast-gateway MAC address:
History
Release version Command history
Syntax
ipv6 dhcp relay address ipv6-addr [interface interface-type interface-name] [ use-vrf vrf-name ]
no ipv6 dhcp relay address ipv6-addr [interface interface-type interface-name] [ use-vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of the DHCP server where the DHCP client requests are to be forwarded.
interface
This parameter specifies the outgoing interface, used when the relay address is a link-local or multicast address
interface-type
The type of interface - Ethernet or VE.
interface-name
The interface name or Ve ID.
use-vrf
Use this option if the VRF where the DHCP server is located is different from the VRF of the interface where the client
is connected.
vrf-name
VRF name.
Modes
Interface subtype configuration mode
Usage Guidelines
This command uses the IPv6 address of the DHCP server where the DHCP client requests are to be forwarded. You can
configure the address on a virtual Ethernet (VE) or an Ethernet interface. You can configure up to 16 relay destination addresses
on an interface.
Enter the command while in interface subtype configuration mode for a VE or Ethernet interface where you want to configure
the IPv6 DHCP Relay. Use the no version of this command to remove the IPv6 DHCP Relay from the interface. If the use-vrf
option is not used, it is assumed that the DHCP server and interface where the client is connected are on the same VRF.
If the relay address is a link local address or a multicast address, an outgoing interface must be configured for IPv6 relay to
function. In instances where the server address is relayed to a different VRF compared to a client connected interface VRF, in
addition to the relay address, you must also specify the user-vrf, otherwise IPv6 relay may not function correctly. IPv6 route
leaking is also required for IPv6 reachability.
The no form of the command deletes the IPv6 DHCP Relay address from the interface.
Examples
The following example configures an IPv6 DHCP Relay address on a Ve interface.
History
Release version Command history
ipv6 dns
Configures the DNS domain name and the primary and secondary name-server IPv6 addresses.
Syntax
ipv6 dns { domain-name domain_name | name-server name_server }
Parameters
domain-name domain_name
Specifies the DNS domain name.
name-server name_server
Specifies the IPv6 address of the primary and secondary name servers. Both the IPv6 and IPv4 addresses are
supported.
Modes
Global configuration mode
Usage Guidelines
Your first run of ipv6 dns name-server specifies the default IP gateway address. Your second run of ipv6 dns name-server
specifies the secondary IP gateway address.
Name servers can only be entered or removed one at a time. The newly entered name server will append to the existing name
server.
To disable IP directed broadcasts for a specific domain, enter no ipv6 dns domain-name domain_name.
Examples
The following example configures DNS.
History
Release version Command history
Syntax
ipv6 icmpv6 rate-limiting milliseconds
Command Default
This command is enabled on the management port and on the front-end ports.
Parameters
milliseconds
Time interval per ICMP packet. The range is from 1 through 4294967295 milliseconds. The default is 1000
milliseconds.
Modes
Interface configuration mode
Usage Guidelines
This is an interface-specific configuration.
The no form of this command reverts the rate limiting to the default settings.
Examples
The following example enables IPv6 ICMP rate-limiting on an Ethernet interface.
History
Release version Command history
Syntax
ipv6 mld snooping enable
Command Default
IPv6 MLDv1 snooping is disabled.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to disable IPv6 MLDv1 snooping globally.
Examples
To enable IPv6 MLDv1 snooping globally:
device(config)# vlan 1
device(config-vlan-1)# ipv6 mld snooping enable
History
Release version Command history
Syntax
ipv6 mld snooping fast-leave
Command Default
This feature is disabled.
Modes
VLAN configuration mode
Usage Guidelines
This command minimizes the leave latency of group memberships on an interface, as the device does not send group-specific
queries. As a result, the group entry is removed from the multicast routing table as soon as a group leave message is received.
Use the no form of this command to restore the default.
Examples
To configure the immediate-leave feature on a VLAN:
device(config)# vlan 1
device(config-vlan-1)# ipv6 mld snooping fast-leave
History
Release version Command history
Syntax
ipv6 mld last-member-query-count value
Parameters
value
The range is from 1 through 10. The default is 2.
Modes
VLAN configuration mode
Usage Guidelines
The last-member query count is the number of times, separated by the last-member query-response interval, that an MLD
query is sent in response to a host leave message from the last known active host on the subnet. Use the no form of this
command to restore the default.
Examples
To change the IPv6 MLDv1 snooping last-member query count from the default on a VLAN.
device(config)# vlan 1
device(config-vlan-1)# ipv6 mld last-member-query-count 3
History
Release version Command history
Syntax
ipv6 mld snooping last-member-query-interval msec
Parameters
msec
The range is from 100 through 2500 milliseconds. The default is 1000.
Modes
VLAN configuration mode
Usage Guidelines
The last-member query interval is the interval for the response to a query sent after a host leave message is received from the
last known active host on the subnet. The group is deleted if no reports are received in this interval. This interval adjusts the
speed at which messages are transmitted on the subnet. Smaller values detect the loss of a group member faster. Use the no
form of this command to restore the default.
Examples
To configure IPv6 MLDv1 snooping last-member query interval on a VLAN:
device(config)# vlan 1
switch(config-vlan-1)# ipv6 mld snooping last-member-query-interval 25
History
Release version Command history
Syntax
ipv6 mld snooping mrouter interface { ethernetinterface name | port-channel number}
Parameters
ethernetinterface name
Specifies the Ethernet interface name.
port-channelnumber
Specifies the port-channel number.
Modes
VLAN configuration mode
Usage Guidelines
Use the no form of this command to disable the VLAN port member from being an mrouter port.
Examples
To configure a VLAN port member to be an mrouter port:
switch(config)# vlan 1
switch(config-vlan-1)# ipv6 mld snooping interface ethernet 0/1
History
Release version Command history
Syntax
ipv6 mld snooping querier enable
Modes
VLAN configuration mode
Usage Guidelines
Use the no form of this command to deactivate this functionality.
Examples
To enable MLD snooping querier functionality on a VLAN:
device(config)# vlan 1
device(config-vlan-1)# ipv6 mld snooping querier enable
History
Release version Command history
Syntax
ipv6 mld snooping robustness-variable value
Parameters
value
The range is from 2 through 10. The default is 2.
Modes
VLAN configuration mode
Usage Guidelines
This value determines the number of general MLD snooping queries that are sent before a multicast address is aged out for
lack of a response. Use the no form of this command to restore the default.
Examples
To change the robustness variable from the default on a VLAN:
device(config)# vlan 1
device(config-vlan-1)# ipv6 mld snooping robustness-variable 7
History
Release version Command history
Syntax
ipv6 mld snooping static-group interface group-ipv6-addressinterfaceinterface
Parameters
group-ipv6-address
A multicast address to be joined.
interface
An Ethernet or port-channel interface.
Modes
VLAN configuration mode
Usage Guidelines
Use the no form of this command to remove the static-group configuration on an interface for a VLAN.
Examples
To configure multicast static IPv6 groups on an Ethernet interface for a VLAN:
device(config)# vlan 1
device(config-vlan-1)# ipv6 mld static-group ff1e::1 interface ethernet 0/1
History
Release version Command history
Syntax
ipv6 mld snooping startup-query-count value
Parameters
value
The range is from 1 through 10. The default is 1.
Modes
VLAN configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
To change the startup query count on a VLAN:
device(config)# vlan 1
device(config-Vlan-1)# ipv6 mld startup-query-count 5
History
Release version Command history
Syntax
ipv6 mld snooping startup-query-interval value
Command Default
This feature is disabled.
Parameters
value
The range is from 1 through 450. The default is 1.
Modes
VLAN configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
To change the startup query interval on a VLAN:
device(config)# vlan 1
switch(config-vlan-1)# ipv6 mld startup-query-interval 4
History
Release version Command history
ipv6 mtu
Sets the IPv6 maximum transmission unit (MTU) on a specified interface.
Syntax
ipv6 mtu size
no ipv6 mtu
Command Default
IPv6 MTU size is 1500 bytes.
Parameters
size
Specifies the size of an interface IPv6 MTU. The range is from 1300 through 9194 bytes.
Modes
Interface configuration mode
Usage Guidelines
If the interface is part of a VE, change the IPv6 MTU only at the VE interface and not at the physical port. All member ports of a
VE inherit the VE-interface IPv6 MTU value.
Use the no ipv6 mtu command to revert the IPv6 MTU size to the default value.
Examples
On a specified Ethernet interface, the following example sets the IPv6 MTU to 2000 bytes.
History
Release version Command history
Syntax
ipv6 nd cache expire seconds
Command Default
Default expiration time is 1500 seconds.
Parameters
seconds
Specifies how long an entry stays in the Neighbor Discovery cache. The range is from 30 through 14400 seconds.
The default is 1500.
Modes
Interface subtype configuration mode
Usage Guidelines
Cache entries expire and are deleted if they remain in a "stale" state as defined by seconds.
You can modify the ND expiration time only at the interface level, but not at the global level.
The no form of this command restores the default aging timeout of 1500 seconds.
Examples
The following example sets the Neighbor Discovery expiration time to 2500 seconds on an Ethernet interface:
History
Release version Command history
Syntax
ipv6 ospf active
Modes
Interface subtype configuration mode
Usage Guidelines
Use the ipv6 ospf active command on each interface participating in adjacency formation. This command overrides the global
passive setting on that interface, and enables transmission of OSPFv3 control packets.
Examples
The following example sets a specific OSPFv3 Ethernet interface to active.
History
Release version Command history
Syntax
ipv6 ospf area area-id | ip-addr
Parameters
area-id
Area ID in dotted decimal or decimal format.
ip-addr
Area ID in IP address format.
Modes
Interface subtype configuration mode
Usage Guidelines
This command enables an OSPFv3 area on the interface to which you are connected.
Examples
The following example enables a configured OSPFv3 area named 0 on a specific OSPFv3 Loopback interface.
History
Release version Command history
Syntax
ipv6 ospf authentication ipsec key-add-remove-interval interval
Parameters
key-add-remove-interval interval
Specifies the OSPFv3 authentication key add-remove interval. Valid values range from decimal numbers 0 through
14400. The default is 300.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command removes IPsec authentication from the interface.
Examples
The following example enables IPsec on a specified OSPFv3 Looback interface.
The following example sets the OSPFv3 authentication key add-remove interval to 480.
History
Release version Command history
Syntax
ipv6 ospf authentication ipsec disable
Modes
Interface subtype configuration mode
Usage Guidelines
When this command is used, packets that are sent out will not be IPSec encapsulated and the received packets which are IPSec
encapsulated will be dropped.
The no form of the command re-enables IPSec on the interface if IPsec is already configured on the interface.
Examples
The following example disables IPsec on a specific OSPFv3 interface where IPsec is already enabled.
History
Release version Command history
Syntax
ipv6 ospf authentication spi spi { ah | esp null } { hmac-md5 | hmac-sha1 } key key }
Parameters
spi
SPI value. Valid values range from decimal numbers 512 through 4294967295.
ah
Specifies Authentication Header (AH) as the protocol to provide packet-level security.
esp
Specifies Encapsulating Security Payload (ESP) as the protocol to provide packet-level security.
null
Specifies that the ESP payload is not encrypted.
hmac-md5
Enables Hashed Message Authentication Code (HMAC) Message Digest 5 (MD5) authentication on the OSPFv3
interface.
hmac-sha1
Enables HMAC Secure Hash Algorithm 1 (SHA-1) authentication on the OSPFv3 interface.
key
Number used in the calculation of the message digest.
key
The 40 hexadecimal character key.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no ipv6 ospf authentication spi spi to remove the SPI value from the interface.
Examples
The following example enables ESP and HMAC-SHA-1 on a specified OSPFv3 Ethernet interface.
The following example enables AH and HMAC-MD5 on a specified OSPFv3 virtual Ethernet (VE) interface.
History
Release version Command history
Syntax
ipv6 ospf bfd
Modes
Interface subtype configuration mode
Usage Guidelines
BFD sessions are initiated only if BFD is also enabled globally using the bfd command in OSPFv3 router configuration mode.
If BFD is disabled using the no bfd command in OSPFv3 router configuration mode, BFD sessions on specific interfaces are
deregistered.
The no form of the command removes all BFD sessions from a specified interface.
Examples
The following example enables BFD on an Ethernet interface.
The following example disables BFD on an OSPFv3 virtual Ethernet (VE) interface.
History
Release version Command history
Syntax
ipv6 ospf cost value
Parameters
value
Cost value. Valid values range from 1 through 65535. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the OSPFv3 cost on the interface. If the cost is not configured with this command, OSPFv3
calculates the value from the reference and interface bandwidths.
Examples
The following example sets the cost to 620 on a specific OSPFv3 Virtual Ethernet (VE) interface.
History
Release version Command history
Syntax
ipv6 ospf dead-interval interval
Parameters
interval
Dead interval in seconds. Valid values range from 3 through 65535 seconds. The default is 40.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the dead interval, the hello interval is automatically changed to a value that is one fourth that of the new dead
interval, unless the hello interval is also explicitly configured using the ipv6 ospf hello-interval command.
The running-config command displays only explicitly configured values of the hello interval, which means that a value that was
automatically changed as the result of a dead-interval change is not displayed.
Examples
The following example sets the dead interval to 80 on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf hello-interval interval
Parameters
interval
Hello interval in seconds. Valid values range from 1 through 65535 seconds. The default is 10 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the hello interval, the dead interval is automatically changed to a value that is four times that of the new hello
interval, unless the dead interval is also explicitly configured using the ipv6 ospf dead-interval command.
The running-config command displays only explicitly configured values of the dead interval, which means that a value that was
automatically changed as the result of a hello interval change is not displayed.
Examples
The following example sets the hello interval to 20 on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf hello-jitter interval
Parameters
jitter
Allowed interval between hello packets.Valid values range from 1 through 50 percent (%). The default is 10%.
Modes
Interface subtype configuration mode
Usage Guidelines
The hello interval can vary from the configured hello-interval to a maximum of percentage value of configured jitter.
Examples
The following example sets the hello jitter to 20 on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf instance instanceID
Parameters
instanceID
Instance identification number. Valid values range from 0 through 255.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example sets the number of IPv6 OSPF instances to 35 on a specific Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf mtu-ignore
Modes
Interface subtype configuration mode
Usage Guidelines
In default operation, the IP MTU on both sides of an OSPFv3 link must be the same, and a check of the MTU is performed
when Hello packets are first exchanged.
Examples
The following example disables MTU-match checking on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf network { broadcast | point-to-point }
Command Default
Network type is broadcast.
Parameters
broadcast
Network type is broadcast, such as Ethernet.
point-to-point
Network type is point-to-point.
Modes
Interface subtype configuration mode
Usage Guidelines
Point-to-point can support unnumbered links, which requires less processing by OSPFv3.
NOTE
The network type non-broadcast is not supported at this time.
Examples
The following example configures an OSPFv3 point-to-point link on a specific OSPFv3 Ethernet interface.
The following example configures an OSPFv3 broadcast link on a specific OSPFv3 Loopback interface.
History
Release version Command history
Syntax
ipv6 ospf passive
Modes
Interface subtype configuration mode
Usage Guidelines
The ipv6 ospf passive command disables transmission of OSPFv3 control packets on that interface. OSPFv3 control packets
received on a passive interface are discarded.
Examples
The following example sets a specific OSPFv3 virtual Ethernet (VE) interface to passive.
History
Release version Command history
Syntax
ipv6 ospf priority value
Parameters
value
Priority value. Valid values range from 0 through 255. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
The OSPFv3 router assigned the highest priority becomes the designated router, and the OSPFv3 router with the second-
highest priority becomes the backup router.
Examples
The following example sets a priority of 4 for the OSPFv3 router that is connected to an OSPFv3 Virtual Ethernet (VE)
interface.
History
Release version Command history
Syntax
ipv6 ospf retransmit-interval interval
Parameters
interval
Retransmit interval in seconds. Valid values range from 0 through 3600 seconds. The default is 5.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command resets the retransmit interval to its default.
Examples
The following example sets the retransmit interval to 8 for all OSPFv3 devices on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf suppress-linklsa
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the defaults where link LSA advertisements are not suppressed.
Examples
The following example suppresses link LSAs from being advertised on devices on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 ospf transmit-delay value
Parameters
value
Transmit delay in seconds. Valid values range from 0 through 3600 seconds. The default is 1 second.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example sets a transmit delay of 25 seconds for devices on a specific OSPFv3 Ethernet interface.
History
Release version Command history
Syntax
ipv6 policy route-map map-name
Command Default
The IPv6 route map is not enabled.
Parameters
map-name
Specifies the name of the route map.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables the IPv6 route map.
Examples
The following example enables the IPv6 route map on a specific interface.
History
Release version Command history
ipv6 prefix-list
Configures an IPv6 prefix list for basic traffic filtering
Syntax
ipv6 prefix-list name deny ipv6-prefix/prefix-length [ ge ge-value ] [ le le-value ]
ipv6 prefix-list name seq instance-number {deny ge ge-value le le-value | permit ge ge-value le le-value }
Parameters
name
Specifies the prefix list name.
deny ip-prefix/prefix-length
Denies a route specified in the prefix list. The prefix list matches only on the specified prefix/prefix length, unless you
use the ge ge-value or le le-value parameters.
ge ge-value
Specifies minimum prefix length to be matched. The range is from ge-value to 128.
le le-value
Specifies maximum prefix length to be matched. The range is from the le-value to the prefix-length parameter.
permit ip-prefix/prefix-length
Permits a route specified in the prefix list. The prefix list matches only on the specified prefix/prefix length, unless you
use the ge ge-value or le le-value parameters.
seq
Specifies an IPv6 prefix list sequence number of entry.
instance
Specifies an IPv6 prefix list instance number.
Modes
Global configuration mode
Usage Guidelines
An IPv6 prefix list is composed of one or more conditional statements that execute a permit or deny action if a route matches a
specified prefix. In prefix lists with multiple statements, you can specify a sequence number for each statement. The specified
sequence number determines the order in which the statement appears in the prefix.
You can configure an IPv6 prefix list on a global basis, then use it as input to other commands or processes, such as route
aggregation, route redistribution, route distribution, route maps, and so on. When a device interface sends or receives an IPv6
packet, it applies the statements within the IPv6 prefix list in their order of appearance to the packet. As soon as a match occurs,
the device takes the specified action (permit or deny the packet) and stops further comparison for that packet.
You can use permit statements in the prefix list to specify the traffic that you want to send to the other feature. If you use deny
statements, the traffic specified by the deny statements is not supplied to the other feature. You can configure up to one
hundred IPv6 prefix lists.
You must specify the ipv6-prefix parameter in hexadecimal using 16-bit values between colons as documented in RFC 4291.
You must specify the prefix-length parameter as a decimal value. A slash mark (/) must follow the ipv6-prefix parameter and
precede the prefix-length parameter.
The ge-value or le-value you specify must meet the following condition for prefix-length:
Examples
The following example creates a prefix-list that allows routes with the prefix 2001:db8::/32 .
History
Release version Command history
Syntax
ipv6 protocol vrrp
Command Default
IPv6 VRRPv3 is not enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of this command globally disables VRRPv3.
Examples
To enable IPv6 VRRPv3 globally:
History
Release version Command history
Syntax
ipv6 protocol vrrp-extended
Command Default
IPv6 VRRP-Ev3 is disabled.
Modes
Global configuration mode
Usage Guidelines
The no form of this command globally disables IPv6 VRRP-Ev3.
Examples
To enable IPv6 VRRP-Ev3 globally:
History
Release version Command history
Syntax
ipv6 receive access-group acl-name in
Command Default
No receive-path ACLs are applied.
Parameters
acl-name
Specifies the name of the standard or extended IP access list.
in
Specifies ingress traffic.
Modes
Global configuration mode
Usage Guidelines
For both interface ACLs and receive-path ACLs, you use identical commands to create the ACLs. You also use identical
commands to define permit/deny rules in the ACLs. The only variance is the command you use to apply the ACL:
• To apply an interface ACL, from an interface-subtype configuration mode you use the { ip | ipv6 | mac } access-group
command.
• To apply a receive-path ACL, from global configuration mode you use the { ip | ipv6 } receive access-group
command.
Examples
The following example creates an IPv6 extended ACL, defines rules in the ACL, and applies it as a receive-path ACL.
device(conf-ipacl-ext)# exit
device(config)# ipv6 receive access-group ipv6-receive-acl-example in
History
Release version Command history
ipv6 route
Configures an IPv6 static route.
Syntax
ipv6 route dest-ipv6-prefix/prefix-length next-hop-ipv6-address [ metric ] [ distance number ] [ tag tag-number ]
ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-address [ ve ve-id ] [ metric ] [ distance number ] [ tag tag-
number ]
Command Default
No IPv6 static route is configured by default.
Parameters
dest-ipv6-prefix
Destination IPv6 prefix in hexadecimal with 16-bit values between colons, as specified in RFC 2373.
prefix-length
A decimal value specifying the length of the IPv6 address prefix.
next-hop-ipv6-address
IPv6 address of the next-hop gateway.
link-local-next-hop-ipv6-address
IPv6 address of the link-local next-hop gateway.
ethernet slot/port
Specifies the Ethernet slot and port. The slot number must be 0 if the device has no slots.
ve ve-id
Specifies the virtual Ethernet (VE) interface.
metric
Specifies a value that the Layer 3 switch uses to compare this route to other static routes in the IPv6 static route table
that have the same destination. The metric applies only to routes that the Layer 3 switch has already placed in the IPv6
static route table. Two or more routes to the same destination with the same metric will load share (as in ECMP load
sharing). The range is from 1 through 16. The default is 1.
distance number
Specifies an administrative distance. The range is from 1 through 254. The default is 1. This is a value that the Layer 3
switch uses to compare this route with routes from other sources that have the same destination. By default, static
routes take precedence over routes learned by routing protocols. To choose a dynamic route over a static route,
configure the static route with a higher administrative distance than the dynamic route. A distance of 255 is considered
unreachable.
tag
Specifies a tag value for the route. The route tag can be used for route redistribution to routing protocols by means of
route maps (as in IPv4 static route redistribution).
tag-number
A number from 0 through 4294967295. The default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command with the same parameters to remove the IPv6 static route.
Examples
The following example creates an IPv6 static route for a destination network with the prefix 2001:DB8::0/64 and a next-hop
gateway with the global address 2001:DB8:0:ee44::1.
History
Release version Command history
Syntax
ipv6 route ipv6-prefix/prefix-length next-hop-vrf vrf_name next-hop-ipv6-address [ metric ] [ distance number ] [ tag tag-
number ]
Command Default
No IPv6 static route is configured by default.
Parameters
dest-ipv6-prefix
Destination IPv6 prefix in hexadecimal with 16-bit values between colons, as specified in RFC 2373.
prefix-length
A decimal value specifying the length of the IPv6 address prefix.
next-hop-ipv6-address
IPv6 address of the next-hop gateway.
metric
Specifies a value that the Layer 3 switch uses to compare this route to other static routes in the IPv6 static route table
that have the same destination. The metric applies only to routes that the Layer 3 switch has already placed in the IPv6
static route table. Two or more routes to the same destination with the same metric will load share (as in ECMP load
sharing). The range is from 1 through 16. The default is 1.
distance number
Specifies an administrative distance. The range is from 1 through 254. The default is 1. This is a value that the Layer 3
switch uses to compare this route with routes from other route sources that have the same destination. By default,
static routes take precedence over routes learned by routing protocols. To choose a dynamic route over a static route,
configure the static route with a higher administrative distance than the dynamic route. A distance of 255 is considered
unreachable.
tag
Specifies a tag value for the route. The route tag can be used for route redistribution to routing protocols by means of
route maps (as in IPv4 static route redistribution).
tag-number
A number from 0 through 4294967295. The default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command with the same parameters to remove the IPv6 static route.
Examples
The following example creates an IPv6 static route to IPv6 2001:DB8::0/64 destinations through the VRF named "partners"
and the next-hop router with the IPv6 address 2001:DB8:0:ee44::1.
History
Release version Command history
Syntax
ipv6 route dest-ipv6-prefix/prefix-length null 0 [ metric ] [ distance number ] [ tag tag-number ]
Command Default
No IPv6 static route is configured by default.
Parameters
dest-ipv6-prefix
Destination IPv6 prefix in hexadecimal with 16-bit values between colons, as specified in RFC 2373.
prefix-length
A decimal value specifying the length of the IPv6 address prefix.
next-hop-ipv6-address
IPv6 address of the next-hop gateway.
null 0
Causes packets to the selected destination to be dropped by shunting them to the "null 0" interface. (This is the only
available option.)
ethernet slot/port
Specifies the Ethernet slot and port. The slot number must be 0 for devices that do no have slots.
metric
Specifies a value that the Layer 3 switch uses to compare this route to other static routes in the IPv6 static route table
that have the same destination. The metric applies only to routes that the Layer 3 switch has already placed in the IPv6
static route table. Two or more routes to the same destination with the same metric will load share (as in ECMP load
sharing). The range is from 1 through 16. The default is 1.
distance number
Specifies an administrative distance. The range is from 1 through 254. The default is 1. This is a value that the Layer 3
switch uses to compare this route with routes from other route sources that have the same destination. By default,
static routes take precedence over routes learned by routing protocols. To choose a dynamic route over a static route,
configure the static route with a higher administrative distance than the dynamic route. A distance of 255 is considered
unreachable.
tag
Specifies a tag value for the route. The route tag can be used for route redistribution to routing protocols by means of
route maps (as in IPv4 static route redistribution).
tag-number
A number from 0 through 4294967295. The default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command with the same parameters to remove the null route.
Examples
The following example creates a primary route to all 2001 : DB8 : : 0/64 destinations through virtual interface (ve) 3. The
primary route has the default cost metric of 1. The example also creates an alternative null route with a higher cost metric (2) to
drop packets when the primary route is not available.
History
Release version Command history
Syntax
ipv6 route static bfd dest-ipv6-address source-ipv6-address [ interface-type interface-name | null interface-name ] [ interval
transmit-time min-rx receive-time multiplier number ]
Command Default
BFD is not configured for an IPv6 static route.
Parameters
dest-ipv6-address
Specifies the IPv6 address of the BFD neighbor.
source-ipv6-address
Specifies the source IPv6 address.
interface-type
The type of interface, such as Ethernet or VE.
interface-name
The interface number or VLAN ID.
null interface-name
Drops packets with this destination.
interval transmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers. Valid values range from 50
through 30000. The default is 500.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers. Valid values range
from 50 through 30000. The default is 500.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer before BFD
determines that the connection to that peer is not operational. Valid values range from 3 through 50. The default is 3.
Modes
Address-family IPv6 unicast VRF configuration mode
Usage Guidelines
The interval transmit-time and min-rx receive-time variables are the intervals desired by the local device. The actual values in
use will be the negotiated values.
For single-hop static BFD sessions, timeout values are optional because all required information is available from the outgoing
interface. For multihop BFD sessions, if the configured interval and min-rx parameters conflict with those of an existing
session, the lower values are used.
If you configure a neighbor IPv6 address and a source IPv6 address that already exist in BFD, BFD overwrites the existing
interval values and multiplier for the IPv6 addresses with the new values, on behalf of the static module.
Static BFD can be configured without configuring a static route to configure a BFD session. This is especially useful on BFD
neighbors when they have reachability from other neighbors via OSPF or BGP. You must configure different BFD sessions for
each ECMP path with the corresponding interface IP as the source IPv6 address.
For IPv6 static BFD sessions, if the BFD neighbor is link-local, the source IPv6 address must also be link-local.
If an IPv6 BFD session is running for a link-local BFD neighbor, the interface-type and interface-name parameters are
mandatory because the link-local address can be the same on multiple interfaces.
The no form of the command removes the configured BFD IPv6 static route.
Examples
The following example configures a BFD session on an IPv6 static route, specifying a VE interface.
The following example configures a BFD session on an IPv6 static route in a nondefault VRF instance.
History
Release version Command history
Syntax
ipv6 route static bfd holdover-interval time
Parameters
time
Specifies BFD holdover interval in seconds. Valid values range from 1 through 30. The default is 0.
Modes
Address-family IPv6 unicast VRF configuration mode
Global configuration mode
Usage Guidelines
If the BFD session is restored within the specified time interval, no down notification is sent.
Use the ipv6 route static bfd holdover-interval command in global configuration mode to set the BFD holdover interval
globally for static routes.
The no form of the command removes the configured BFD holdover interval from the configuration, and reverts to the default
value of 0.
Examples
The following example sets the BFD holdover interval globally for IPv6 static routes to 25.
The following example removes the configured BFD holdover interval for IPv6 static routes for a nondefault VRF instance.
History
Release version Command history
Syntax
ipv6 router ospf [ vrf name ]
Parameters
vrf name
Specifies a nondefault VRF.
Modes
Global configuration mode
Usage Guidelines
If you save the configuration to the startup-config file after disabling OSPFv3, all OSPFv3 configuration information is removed
from the startup-config file.
Use this command to enable the OSPFv3 routing protocol and enter OSPFv3 router or OSPFv3 router VRFconfiguration
mode. OSPFv3 maintains multiple instances of the routing protocol to exchange route information among various VRF
instances.
The no form of the command deletes all current OSPFv3 configurations and blocks any further OSPFv3 configuration.
Examples
The following example enables OSPFv3 on a default VRF and enters OSPFv3 router configuration mode.
History
Release version Command history
Syntax
ipv6 vrrp-extended auth-type md5-auth auth-text
Command Default
No authentication is configured for a VRRP-E interface.
Parameters
md5-auth auth-text
Configures MD5 authentication on the interface. The maximum length of the text string is 64 characters.
Modes
Virtual Ethernet (ve) interface configuration mode
Usage Guidelines
This configuration is for virtual Ethernet (ve) interfaces only.
If the md5-auth option is configured, syslog and SNMP traps are generated if a packet is being dropped due to MD5
authentication failure. Using MD5 authentication implies that the software does not need to run checksum verification on the
receiving device and can rely on the authentication code (message digest 5 algorithm) to verify the integrity of the VRRP-E
message header.
The no form of this command removes the VRRP-E authentication from the interface.
Examples
The following example configures MD5 authentication on Virtual Ethernet interface 20.
History
Release version Command history
ipv6 vrrp-extended-group
Configures an IPv6 VRRP-Ev3 group and enters into the VRRP-E configuration mode.
Syntax
ipv6 vrrp-extended-group group-ID
Parameters
group-ID
A number from 1 through 255 that you assign to the VRRP-Ev3 group.
Modes
Virtual Ethernet (VE) interface configuration mode
Usage Guidelines
Enter no ipv6 vrrp-extended-group group-ID to remove the specific IPv6 VRRP-Ev3 group. If you remove a group, you
cannot retrieve it. You would have to redo the configuration procedure.
This configuration is for virtual Ethernet (VE) interfaces only. IPv6 VRRP-Ev3 must be enabled on the device before the IPv6
VRRP-E group is configured.
Examples
The following example shows how to assign the VE interface with a VLAN number of 2019 to the VRRP-Ev3 group with the ID
of 19.
History
Release version Command history
ipv6 vrrp-group
Configures an IPv6 VRRPv3 group and enters into the virtual router configuration mode.
Syntax
ipv6 vrrp-group group-ID
Parameters
group-ID
A value from 1 through 255 that you assign to the VRRPv3 group.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no ipv6 vrrp-group group-ID to remove a specific IPv6 VRRPv3 group. If you remove a group, you cannot retrieve it. You
would have to redo the configuration procedure.
IPv6 VRRPv3 must be enabled on the device before the IPv6 VRRP group is configured.
Examples
The following example shows how to assign an Ethernet interface to the VRRPv3 group with the ID of 18.
History
Release version Command history
ipv6 vrrp-suppress-interface-ra
Suppresses interface router advertisement (RA) when VRRPv3 is configured on an interface.
Syntax
ipv6 vrrp-suppress-interface-ra
no ipv6 vrrp-suppress-interface-ra
Command Default
Interface RA is enabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no ipv6 vrrp-suppress-interface-ra to remove the suppression of interface RA.
Router advertisements are sent by the VRRP master device and contain the link-local virtual IP address and the virtual MAC
address. For network security reasons, if you do not want the MAC addresses of interfaces to be viewed, you can disable RA
messages.
Examples
This example suppresses interface RA on a virtual Ethernet (VE) interface:
History
Release version Command history
iterations
For an implementation of an event-handler profile, specifies the number of times an event-handler action is run, when triggered.
Syntax
iterations num-iterations
no iterations
Command Default
When the trigger condition occurs, the event-handler actions runs once.
Parameters
num-iterations
Specifies the number of times an event-handler action is run, when triggered. Valid values are any positive integer.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command resets the iterations setting to the default 1 iteration.
Examples
The following example specifies 5 iterations.
History
Release version Command history
Syntax
key shared_secret
no key
Command Default
The default value is "sharedsecret".
Parameters
shared_secret
Specifies a text string to use as the shared secret between the device and the RADIUS server. The valid string length is
from 8 through 40 characters. The default string is "sharedsecret". The exclamation mark (!) is supported for RADIUS
servers, and you can specify the shared secret string in either double quotation marks or by using the escape character
(\); for example, "secret!key" or secret\!key.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The key command does not support configuration of an empty string.
The no form of the command restores the default value.
Examples
The following example shows how to configure the text string "new#radius*secret" as the shared secret to use between the
device and the RADIUS server.
History
Release version Command history
key-add-remove-interval
Alters the timing of the authentication key add-remove interval.
Syntax
key-add-remove-interval interval
no key-add-remove-interval interval
Parameters
interval
Specifies the add-remove interval in seconds. Valid values range from 0 through 14400. The default is 300 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The no form of the command resets the add-remove interval to the default value of 300 seconds.
Examples
The following example sets the key add-remove interval to 240 seconds.
History
Release version Command history
key-rollover-interval
Alters the timing of the existing configuration changeover.
Syntax
key-rollover-interval interval
no key-rollover-interval interval
Parameters
interval
Specifies the key-rollover-interval in seconds. Valid values range from 0 through 14400. The default is 300 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
In order to have consistent security parameters, rekeying should be done on all nodes at the same time. Use the key-rollover-
interval command to facilitate this. The key rollover timer waits for a specified period of time before switching to the new set of
keys. Use this command to ensure that all the nodes switch to the new set of keys at the same time.
The no form of the command resets the rollover interval to the default value of 300 seconds.
Examples
The following example sets the key rollover interval to 420 seconds.
The following example re-sets the key rollover interval to the default value.
History
Release version Command history
keypair
Associates a cryptograhic keypair with a trustpoint for security protocol exchanges for applications.
Syntax
keypair key_label
no keypair
Parameters
key_label
Specifies a keypair label.
Modes
Trustpoint configuration mode
Usage Guidelines
Use the no form of the command to remove the trustpoint keypair configuration.
Examples
The following example shows how to associate the keypair labeled k1 with a trustpoint named t1.
History
Release version Command history
lacp default-up
Activates an Link Aggregation Control Protocol (LACP) link in the absence of PDUs.
Syntax
lacp default-up
no lacp default-up
Modes
Interface subtype configuration mode
Usage Guidelines
This command forces the port to activate an LACP link if there are no PDUs available on the interface port.
Examples
The following example activates an LACP link in the absence of PDUs on an Ethernet interface.
History
Release version Command history
lacp port-priority
Configures the Link Aggregation Control Protocol (LACP) port priority of a member port of a port-channel.
Syntax
lacp port-priority value
no lacp port-priority
Parameters
value
Specifies the priority. Valid values range from 1 through 65535. A lower number takes priority over a higher number.
The default value is 32768.
Modes
Interface subtype configuration mode.
Usage Guidelines
An LACP port priority is configured on each port using LACP. The port priority determines which ports should be put in standby
mode when there is a hardware limitation that prevents all compatible ports from aggregating.
A link with higher priority (smaller in value) gets preference over a link with lower priority (greater in value).
Examples
The following example sets the LACP port priority to 1000 for an Ethernet interface.
History
Release version Command history
lacp system-priority
Sets the Link Aggregation Control Protocol (LACP) system priority. The LACP priority determines which system is responsible
for resolving conflicts in the choice of aggregation groups.
Syntax
lacp system-priority value
no lacp system-priority
Command Default
The default value is 32768.
Parameters
value
Specifies the value of the LACP system priority. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
Lower numerical values have higher priorities.
Enter no lacp system-priority to reset the system priority to the default value.
Examples
The following example sets the LACP system priority value to 68.
History
Release version Command history
lacp timeout
Sets the timeout value used by the Link Aggregation Control Protocol (LACP) to exchange packets on an interface before
invalidating a received data unit (DU).
Syntax
lacp timeout { long | short }
no lacp timeout
Command Default
For trunks, the default value is the short timeout.
Parameters
long
Specifies that a long-timeout value of 30 seconds will be used. With this value, the port waits three times this long (90
seconds) before invalidating the information received earlier on this PDU.
short
Specifies that a short-timeout value of one second will be used. With this value, the port waits three times this long
(three seconds) before invalidating the information received earlier on this PDU.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set the timeout value based on how frequently you think the switch will receive LACP PDUs from the
partner device.
Examples
The following example sets the LACP long-timeout value on an Ethernet interface.
History
Release version Command history
ldap-server host
Configures an LDAP-server host.
Syntax
ldap-server host { ipaddr | FQDN } [ use-vrf vrf-name ]
Command Default
• Timeout: 5 seconds
• Port: 389
• Retries: 5
Parameters
ipaddr | FQDN
Specifies the IPv4 address or Fully Qualified Domain name of the Active Directory (AD) server. IPv6 is supported for
Windows 2008 AD server only. The maximum supported length for the LDAP host name is 40 characters.
use-vrf vrf-name
Specifies a VRF though which to communicate with the LDAP server. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Use this command to set up a connection to the Lightweight Directory Access Protocol (LDAP) server host or modify an
existing configuration. A maximum of 5 LDAP servers can be configured on a device.
Enter no ldap-server host to delete the server configuration.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
Examples
The following example adds an LDAP server on port 489 with retries set to three and the timeout set to 5 seconds.
History
Release version Command history
ldap-server maprole
Maps an Active Directory (AD) group to a device role.
Syntax
ldap-server maprole group group_name role role_name
Parameters
group group_name
The name of the AD group.
role role_name
The name of the device role.
Modes
Global configuration mode
Usage Guidelines
Enter no ldap-server maprolegroup group_name without the role role_name parameter to remove the mapping of the AD
group to a role.
Examples
To map the AD group "Administrator" to the device role "admin":
History
Release version Command history
license eula
Enables the user to accept or decline the EULA for a licensed feature set.
Syntax
license eula { accept feature | decline feature }
Command Default
This command is executed on the local switch.
Parameters
accept
Specifies that the user wants to use the feature without an installed license.
feature
Specifies the displayed license feature name.
decline
Specifies that the user no longer wants to use the unlicensed feature set.
Modes
Privileged EXEC mode.
Usage Guidelines
When the license eula accept command is entered, you are agreeing to purchase a license within a specific timeframe. You can
begin using the features immediately. Use the show license command to display the Advanced Features Self Authenticated
Upgrade (SAU) license when the EULA is accepted. The Advanced Features SAU license is supported on the SLX 9140 and
SLX 9240 devices.
NOTE
The Network Packet Broker (NPB) feature functionality is part of the Advanced Features SAU license.
When the license eula decline command is entered, you are no longer able to use the licensed features. Before you can decline
the licensed features, all configuration settings related to the feature must be restored to default settings.
Examples
The following example shows how to accept the EULA for the Advanced Features SAU license.
The following example displays removing the Advanced Features SAU license.
The following CLI message is displayed when you attempt to configure a feature that requires a SAU license, and you have not
accepted the EULA and there is no SAU license installed for that feature.
History
Release version Command history
Syntax
line vty exec-timeout timeout
Command Default
If no value is specified, the timeout value is 10 minutes.
Parameters
timeout
Specifies the CLI session timeout period in minutes. The timeout value specifies the amount of time a CLI session can
be idle before it logs you out. Valid values range from 0 through 136. The default is 10.
Modes
Global configuration mode
Usage Guidelines
The line vty exec timeout command is a recurrent command, applying to all login sessions. The terminal timeout command
applies only to the current session.
Even if other keys are pressed during the timeout period, the only keystroke that prevents logout is Enter.
To restore the default timeout value of 10 minutes, enter no line vty exec-timeout.
Examples
The following example sets the terminal timeout to 60 minutes.
History
Release version Command history
link-fault-signaling rx
Enables or disables ingress link-fault signaling (LFS) at device or interface level.
Syntax
link-fault-signaling rx { off | on }
no link-fault-signaling
Command Default
LFS is enabled.
Parameters
off
Disables ingress LFS at device or interface level.
on
Enables ingress LFS at device or interface level.
Modes
Global configuration mode
Usage Guidelines
This command is supported both in default system mode and network packet broker (NPB) mode.
When LFS is on, if there is an ingress link fault, the affected interface is brought down. When LFS is off, if the PHY-MAC link is
up, the interface stays up—even if there is an ingress link fault.
You cannot override the egress LFS setting. If there is an egress link fault, the affected interface is brought down.
You can configure LFS settings both globally and at interface-level. Local LFS settings override the global setting.
Examples
The following example changes the global ingress LFS setting from on to off.
The following example resets the global ingress LFS setting to the default on.
The following example sets an interface ingress LFS setting to off, overriding the global setting.
The following example sets an interface ingress LFS setting to configured on, overriding the global setting.
The following example sets an interface ingress LFS setting to default on—but able to be overridden by a global link-fault-
signaling rx off.
History
Release version Command history
lldp profile
Applies a Link Layer Discovery Protocol (LLDP) profile to an interface.
Syntax
lldp profile name
no lldp profile
Command Default
LLDP profile name.
Parameters
name
Specifies the profile name. Valid profile name length is between 1 and 32 characters.
Modes
Interface subtype configuration mode
Usage Guidelines
You must use the lldp profile command to create an LLDP profile before you can apply the profile to the interface. Only one
LLDP profile can exist at any time for a particular interface. When this command is not present, the parameters defined in the
global LLDP configuration are used.
Examples
To apply an LLDP profile called test on an specific Ethernet interface:
History
Release version Command history
Syntax
load-balance { dst-mac-vid | src-mac-vid | src-dst-mac-vid | src-dst-ip | src-dst-ip-mac-vid | src-dst-ip-port | src-dst-ip-
mac-vid-port }
no load-balance
Command Default
The default setting is src-dst-ip-mac-vid-port.
Parameters
dst-mac-vid
Specifies that the distribution is based on the destination MAC address and outer VLAN ID (VID).
src-mac-vid
Specifies that the distribution is based on the source MAC address and VID.
src-dst-mac-vid
Specifies that the distribution is based on the the source and destination MAC addresses and VID.
src-dst-ip
Specifies that the distribution is based on the the source and destination IPv4 or IPv6 addresses.
src-dst-ip-mac-vid
Specifies that the distribution is based on the source and destination IPv4 or IPv6 and MAC addresses; and the VID.
src-dst-ip-port
Specifies that the distribution is based on the source and destination IPv4 or IPv6 addresses and TCP port.
src-dst-ip-mac-vid-port
Specifies that the distribution is based on the source and destination IPv4 or IPv6 and MAC addresses, VID, and port.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to return to the default setting.
Examples
The following example specifies destination MAC address and VID-based load balancing.
History
Release version Command history
Syntax
load-balance { dst-mac-vid | src-mac-vid | src-dst-mac-vid | src-dst-ip | src-dst-ip-mac-vid | src-dst-ip-port | src-dst-ip-
mac-vid-port }
no load-balance
Command Default
The default setting is src-dst-ip-mac-vid-port.
Parameters
dst-mac-vid
(Not supported in NPB mode) Specifies that the distribution is based on the destination MAC address and outer VLAN
ID (VID).
src-mac-vid
(Not supported in NPB mode) Specifies that the distribution is based on the source MAC address and VID.
src-dst-mac-vid
Specifies that the distribution is based on the source and destination MAC addresses; and VID.
src-dst-ip
Specifies that the distribution is based on the source and destination IPv4 or IPv6 address.
src-dst-ip-mac-vid
Specifies that the distribution is based on the source and destination IPv4 or IPv6 addresses, MAC address, and VID.
src-dst-ip-port
Specifies that the distribution is based on the source and destination IPv4 or IPv6 addresses and TCP or UDP
destination port.
src-dst-ip-mac-vid-port
Specifies that the distribution is based on the source and destination IPv4 or IPv6, MAC address, VID, and TCP or
UDP destination port.
Modes
Global configuration mode
Usage Guidelines
The only type of load balancing supported in NPB mode is symmetric load-balance hashing.
Examples
The following example specifies that the distribution is based on source and destination MAC addresses and VLAN ID.
History
Release version Command history
17s.1.00 The default system mode version of this command was introduced.
17s.1.02 The Network Packet Broker (NPB) version of this command was introduced.
local-as
Specifies the BGP autonomous system number (ASN) where the device resides.
Syntax
local-as num
no local-as num
Parameters
num
The local ASN. The range is from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
ASNs in the range from 64512 through 65535 are private numbers that are not advertised to the external community.
The no form of the command removes the ASN from the device.
Examples
The following example assigns a separate local AS number.
History
Release version Command history
log (OSPFv2)
Controls the generation of OSPFv2 logs.
Syntax
log { adjacency [ dr-only ] | all | bad-packet [ checksum ] | database | retransmit }
Command Default
Only OSPFv2 messages indicating possible system errors are logged.
Parameters
adjacency
Specifies the logging of essential OSPFv2 neighbor state changes.
dr-only
Specifies the logging of essential OSPF neighbor state changes where the interface state is designated router
(DR).
all
Specifies the logging of all syslog messages.
bad-packet
Specifies the logging of bad OSPFv2 packets.
checksum
Specifies all OSPFv2 packets that have checksum errors.
database
Specifies the logging of OSPFv2 LSA-related information.
retransmit
Specifies the logging of OSPFv2 retransmission activities.
Modes
OSPF router configuration mode
Usage Guidelines
If this command is not enabled only OSPFv2 messages indicating possible system errors are logged.
A limitation with the dr-only sub-option is that when a DR/BDR election is underway, OSPF neighbor state changes pertaining
to non-DR/BDR routers are not logged. Logging resumes once a DR is elected on that network.
Examples
The following example enables the logging of all OSPFv2-related syslog events.
History
Release version Command history
log (OSPFv3)
Controls the generation of OSPFv3 logs.
Syntax
log { adjacency [ dr-only ] | all | bad-packet [ checksum ] | database | retransmit }
Command Default
Only OSPFv3 messages indicating possible system errors are logged.
Parameters
adjacency
Specifies the logging of essential OSPFv3 neighbor state changes.
dr-only
Specifies the logging only of designated router (DR) interface adjacency changes.
all
Specifies the logging of all syslog messages.
bad-packet
Specifies the logging of bad OSPFv3 packets.
checksum
Specifies all OSPFv3 packets that have checksum errors.
database
Specifies the logging of OSPFv3 LSA-related information.
retransmit
Specifies the logging of OSPFv3 retransmission activities.
Modes
OSPFv3 router configuration mode
Usage Guidelines
If this command is not enabled, only OSPFv3 messages indicating possible system errors are logged.
Examples
The following example enables the logging of all OSPFv3-related syslog events.
History
Release version Command history
log-dampening-debug
Logs dampening debug messages.
Syntax
log-dampening-debug
no log-dampening-debug
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disables the logging of dampening debug messages.
Examples
The following example logs dampening debug messages.
History
Release version Command history
log-shell
Controls the remote logging of SLXVM Linux shell command activities.
Syntax
log-shell start | status | stop
Command Default
By default, supported devices log the SLXVM Linux shell access and all commands executed at the SLXVM Linux shell locally.
Parameters
start
Restarts remote logging.
status
Checks the remote logging status.
stop
Disables remote logging.
Modes
Privileged EXEC
Usage Guidelines
Changes of the log-shell stop and log-shell start commands are applicable only on new SLXVM Linux shell sessions.
If you configure a remote Syslog server, the same logs can be seen on this server.
When you disable remote logging, local logging of user activities continues.
Examples
The following example disables remote logging.
History
Release version Command history
Syntax
logging auditlog class class
Command Default
CONFIGURATION, FIRMWARE, and SECURITY audit log classes are enabled.
Parameters
class
Specifies the class name of the audit log. Valid classes are CONFIGURATION, FIRMWARE, and SECURITY.
Modes
Global configuration mode
Usage Guidelines
The total message storage available is 2048 messages.
Enter no logging auditlog class class to disable the audit logging for the specified class.
Examples
To enable a specific audit log class:
History
Release version Command history
Syntax
logging raslog console severity
Command Default
Severity level is INFO.
Parameters
severity
Specifies the minimum severity level of the message to pass through the filter. Valid values consist of one of the
following: INFO, WARNING, ERROR, or CRITICAL. Input values are case-sensitive.
Modes
Global configuration mode
Usage Guidelines
The total message storage available is 2048 messages.
Examples
To reset the RASLog severity levels to the default value.
History
Release version Command history
Syntax
logging raslog console { start | stop [ minutes ] }
Command Default
RASlog messages display on the console
Parameters
start
Initiates RASLog messages.
stop minutes
Stops RASLog messages for a designated number of minutes.
Modes
Privileged EXEC mode
Usage Guidelines
When stopping or starting RASLog messages, the commands are not configuration commands and therefore are not
persistent.
If the command logging raslog console stop minutes is invoked before the previous time value expires, the latest CLI duration
applies.
Examples
To stop RASLog messages for 1 minute:
History
Release version Command history
logging syslog-client
Configure various parameters used by syslog clients.
Syntax
logging syslog-client localip { CHASSIS_IP }
Parameters
CHASSIS_IP
Uses the Chassis IP address as source IP address in the IP header of syslog messages generated by this device.
Modes
Global configuration mode
Examples
Example command for using the chassis IP as the source IP in the IP header of syslog messages, generated by this device.
History
Release version Command history
Syntax
logging syslog-facility local log_level
Command Default
Syslog level is LOG_LOCAL7.
Parameters
log_level
Specifies the syslog facility level. Valid log levels include the following: LOG_LOCAL0, LOG_LOCAL1,
LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6, LOG_LOCAL7
Modes
Global configuration mode
Usage Guidelines
Use this command to configure the log level for all error log entries to forward to one or more specified syslog servers. You can
configure up to four syslog servers.
Examples
To configure the syslog facility level:
History
Release version Command history
logging syslog-server
Configures a switch to forward system messages to specified syslog servers.
Syntax
logging syslog-server ip_address [ secure ] [ port port-num ] [ use-vrf vrf-name ]
Parameters
ip_address
Specifies the IP address of the syslog server in IPv4 or IPv6 format.
secure
Configures a secure default (port 514) or specified nondefault syslog server port. A secure port number with default
values is not shown in the Extreme SLX-OS database.
port port-num
Specifies a nondefault port. The port range is from 1 through 65535.
use-vrf vrf-name
Specifies a VRF through which to communicate with the server. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Use this command to configure a switch to forward all error log entries to the one or more specified servers. You can configure
up to four servers.
A secure port number with default values is not shown in the database.
The certutil import syslogca command is required for secure syslog to be fully functional.
You can configure up to four syslog servers; this includes all VRFs. You must execute the command for each server.
Use the no logging syslog-server command with the optional use-vrf keyword to remove the specified IP address VRF.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
Examples
To configure a server IPv4 address to which system messages are sent on a user-specified VRF:
To configure a server IPv4 address and specify a VRF with a secure nondefault port, and confirm the configuration:
History
Release version Command history
logical-interface
Creates a logical interface to an Ethernet or port-channel interface, and binds a logical interface to a bridge domain.
Syntax
logical-interface { ethernet 0/port | port-channel num }
Command Default
No interface is bound to the bridge domain.
Parameters
ethernet o/port
Specifies the port number for the Ethernet interface.
port-channel num
Specifies an instance ID for a port-channel logical interface.
Modes
Interface subtype configuration mode
Usage Guidelines
The attachment circuit end-points (logical interfaces) bound to a bridge domain can be either regular Ethernet interfaces or LAG
trunks (port channels).
A logical interface with a VLAN must be created by using the logical-interface command in interface configuration mode
before it can be bound to a bridge domain.
The no version of the command removes the logical interface from the bridge domain configuration.
Examples
The following example shows how to create a logical Ethernet interface instance ID (0/5.10) and bind to bridge domain 4.
The following example shows how to bind a logical port-channel interface instance ID (2.200) to bridge domain 4.
The following example shows the error message that displays when an attempt is made to bind a logical interface that was not
previously created, to a bridge domain.
The following example shows the error message that displays when an attempt is made to bind a logical interface that is
previously bound to another bridge domain.
History
Release version Command history
loopback phy
Implements internal loopback on a physical or port-channel interface.
Syntax
loopback phy
no loopback phy
Command Default
Internal loopback is not implemented.
Modes
Ethernet interface configuration mode
Usage Guidelines
To disable internal loopback on an interface, use the no form of this command.
Examples
The following example implements internal loopback on a physical interface.
History
Release version Command history
Syntax
mac access-group ACLname { in | out } [ switched | routed ]
Parameters
ACLname
Specifies the name of the standard or extended MAC access list.
in
Specifies to filter inbound packets only.
out
Specifies to filter outbound packets only.
switched
Filter only switched traffic. This parameter is not valid for the management interface.
routed
Filter only routed traffic. This parameter is not valid for the management interface.
Modes
Interface-subtype configuration mode
Usage Guidelines
You can apply a maximum of six ACLs to a user interface, as follows:
• One ingress MAC ACL—if the interface is in switchport mode
• (VLANs only) One egress MAC ACL—if the interface is in switchport mode
• One ingress IPv4 ACL
• (VEs only) One egress IPv4 ACL
• One ingress IPv6 ACL
• (VEs only) One egress IPv6 ACL
You can apply an ACL to multiple interfaces. And you can apply an ACL twice—ingress and egress—to a given user interface.
Examples
The following example applies a MAC ACL to filter inbound packets only, on a specified Ethernet interface.
The following example removes a MAC ACL from a specified port-channel interface.
History
Release version Command history
Syntax
mac access-group ACLname
Parameters
ACLname
Specifies the name of the standard or extended MAC access list.
Modes
Overlay gateway configuration mode
Usage Guidelines
This command is supported in overlay-policy maps applied for overlay gateway.
Examples
The following example configures a MAC ACL and an overlay class map. Then the policy map is created and a stanza (#10) is
added. This stanza uses the class map "tunnel-group-1" to identify the gateway and specifies the MAC ACL "fooL2" on the
flows within the tunnel. Finally there is a creation of the overlay gateway "gw2" and the overlay policy is applied, using the
overlay-service-policy in command . The policy map can also applied to the overlay-transit (using the same command).
History
Release version Command history
Syntax
mac access-list extended ACL-name
Parameters
ACL-name
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63 characters in length,
and must begin with an alphanumeric character. No special characters are allowed, except for the underscore (_) and
hyphen (-).
Modes
Global configuration mode
Usage Guidelines
If the ACL is already created, this command puts the device in MAC extended ACL configuration mode.
An extended ACL contains rules that permit or deny traffic according to source and destination addresses, as well as other
parameters. Extended ACLs allow you to filter traffic based on the following:
• Source MAC address
• Destination MAC address
• EtherType
You can apply MAC extended ACLs to VLANs and to Layer 2 interfaces.
The no form of the command removes a MAC extended ACL from an interface.
Examples
The following example creates a MAC extended ACL named mac1.
History
Release version Command history
Syntax
mac access-list standard ACLname
Parameters
ACLname
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63 characters in length,
and must begin with an alphanumeric character. No special characters are allowed, except for the underscore and
hyphen.
Modes
Global configuration mode
Usage Guidelines
Use this command to create a standard MAC access list. If ACL is already created, this command puts the device in the
standard MAC access-list configuration mode.
To remove a MAC ACL from an interface, enter the no form of this command.
Examples
The following command creates a MAC standard ACL named mac1.
History
Release version Command history
mac-address-table
Sets the aging time, sets mac-move parameters, enables conversational MAC learning, and adds static addresses to the MAC
address table.
Syntax
mac-address-table aging-time aging-time
no mac-address-table aging-time
Command Default
Aging time is 1800 seconds.
Parameters
aging-time aging-time
Specifies the time in seconds that a learned MAC address will persist after the last update. If the aging time is set to
zero (0), it means that aging is disabled. Otherwise, values range from 60 through 100000. The default is 1800
seconds.
conversational conversational-aging-time
Configures an aging time for conversational MAC addresses learned by destination address (DA). If the aging
time is set to zero (0), it means that aging is disabled. Otherwise, values range from 60 through 100000. The
default is 300 seconds.
learning-mode conversational
Enables conversational MAC learning, rather than the default dynamic learning mode.
mac-move
Configures MAC-move detection.
detect
Enables MAC-move detection.
limit max-mac-moves
Specifies the MAC-move limit. Thre range is 5 through 500 moves. The default is 20 moves.
slot
Specifies a valid slot number. The slot must be 0 for devices that do not support line cards.
port
Specifies a valid port number.
logical-interface logical-interface
Specifies a logical interface. Logical interfaces are the attachment circuit end-points bound to a bridge domain.
port-channel number
Specifies the port-channel number. Valid values range from 1 through 63.
vlan vlan-id
Specifies an active VLAN. Values range from 1 through 4090.
Modes
Global configuration mode
Usage Guidelines
The vlan keyword is mandatory because the switch only supports independent VLAN learning (IVL).
To restore the default MAC aging time of 1800 seconds, use the no mac-address-table aging-time option.
To restore the default conversational MAC aging time of 300 seconds, use the no mac-address-table aging-time
conversational option.
To disable conversational MAC learning and restore default dynamic MAC learning, use the no mac-address-table learning-
mode conversational option.
To restore the default MAC-move limit of 20 moves, use the no mac-address-table mac-move limit option.
To delete a static MAC address for forwarding to a physical interface, use the no mac-address-table static mac-addr forward
ethernet slot/port vlan vlan-id option.
To delete a static MAC address for forwarding to a logical interface, use the no mac-address-table static mac-addr forward
logical-interface ethernet logical-interface vlan vlan-id option.
To delete a static MAC address for forwarding to a port-channel interface, use the no mac-address-table static mac-addr
forward port-channel port-channel-number vlan option.
Examples
The following example adds a static address to the MAC address table, with forwarding to a physical interface.
The following example adds a static address to the MAC address table, with forwarding to a logical interface.
The following example sets the aging time for conversational MAC addresses to 600 seconds.
The following example restores aging time to its default value of 1800 seconds.
The following example deletes a static MAC address forwarding on a physical interface.
History
Release version Command history
Syntax
mac-address-table mac-move detect
Command Default
This feature is disabled.
Modes
Global configuration mode
Usage Guidelines
MAC address moves are often caused by loops, overloading control-plane resources. When this feature is enabled, the default
number of MAC-moves that are detected is 20. This limit can be changed by means of the mac-address-table mac-move
limit command.
Examples
The following example enables MAC-move detection on the switch.
History
Release version Command history
Syntax
mac-address-table mac-move limit move_threshold
Command Default
When MAC-address-move detection is enabled, by means of the mac-address-table mac-move detect command, and
move_threshold is not specified, the default for move_threshold is 20.
Parameters
move_threshold
Specifies the number of MAC-address moves (in any 10-second window) above which the repeated-MAC-moves
feature is triggered. Range is from 5 through 500. The default is 20.
Modes
Global configuration mode
Usage Guidelines
The no form of this command sets move_threshold to 20, which triggers the feature from the first MAC-address move.
Examples
The following example sets the number of MAC-moves detected without triggering MAC-address-move resolution to 10.
History
Release version Command history
map
Specifies the map to be used for the group of remark values in the default policer remarking profile.
Syntax
map remark-value-group map-name
Command Default
The police-remark-profile command has been executed. Then, the action command has been executed, specifying a
classification type of color-and-cos, color-and-traffic-class, or color-and-dscp.
Parameters
remark-value-group
Specifies the group of remark values to which the specified map applies. Choices include:
• cos-dscp
• cos-mutation
• cos-traffic-class
• dscp-cos
• dscp-traffic-class
• dscp-mutation
• traffic-class-cos
• traffic-class-dscp
• traffic-class-mutation
map-name
Specifies the map.
Modes
Policer remarking profile configuration mode
Usage Guidelines
Use this command after executing the police-remark-profile command and after executing the action command, specifying a
classification type of color-and-cos, color-and-traffic-class, or color-and-dscp. Then, issue the map command to specify the
map used to modify the remark values in the default policer remark profile.
Examples
The following is an example of executing the action command to specify the color-and-cos classification type for exceeding
traffic. Then, the example shows using the map command to specify the maps to be included in the default policer remark
profile for cos remarking for exceeding traffic. ("cm1," "ct1," and "cd1" are map names).
The following is an example of executing the action command to specify the color-and-dscp classification type for conforming
traffic. Then, the example shows using the map command to specify the maps to be included in the default policer remark
profile for dscp remarking for conforming traffic. ("dm1," "dc1," and "dt1" are map names).
The following is an example of executing the action command to specify the color-and-traffic-class classification type for
exceeding traffic. Then, the example shows using the map command to specify the maps to be included in the default policer
remark profile for traffic-class remarking for exceeding traffic. ("tm2," "tc2," and "td2" are map names).
History
Release version Command history
Syntax
map bridge-domain { vlan_id | vni vni }
Command Default
No bridge domain is mapped.
Parameters
vlan_id
Specifies a VLAN or range of VLANs. Range is from 1 through 4096.
vni vni
Specifies a VNI or range of VNIs. Range is from 1 through 16777215.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
Use the no form of this command to remove the mapping.
Examples
To map a BD to a VNI:
History
Release version Command history
map cos
Maps an ingress CoS value to an outbound CoS, DSCP, or Traffic-class value for a QoS CoS-mutation, CoS-to-DSCP, or CoS-
to-traffic class map.
Syntax
map cos cos-value to { cos cos-out } | { dscp dscp-out } | { traffic-class tc-value }
Command Default
The default values for QoS CoS-mutation, CoS-to-DSCP, or CoS-to-traffic class mapping.
Parameters
cos-value
Specifies the ingress CoS value. Enter an integer from 0 to 7.
cos cos-out
Specifies the outbound CoS value. Enter an integer from 0 to 7.
dscp dscp-out
Specifies the outbound DSCP value or range. Enter an integer from 0 to 63.
traffic-class tc-value
Specifies the outbound Traffic Class value. Enter an integer from 0 to 7.
Modes
CoS mutation configuration mode
Usage Guidelines
Use the no form of the command to reset the default values.
Examples
In CoS mutation configuration mode, the following example maps an ingress CoS value to an egress CoS value.
In CoS DSCP configuration mode, the following example maps an ingress CoS value to an egress DSCP value.
In CoS traffic configuration mode, the following example maps the ingress CoS values to a traffic class.
History
Release version Command history
map dscp
Maps an ingress DSCP value to an outbound CoS, DSCP, or Traffic-class value for a QoS DSCP-to-CoS, DSCP-mutation, or
DSCP-to-traffic class map.
Syntax
map dscp dscp-value to { cos cos-value } | { dscp dscp-out } | { traffic-class tc-value }
Command Default
The default values for DSCP to CoS, DSCP mutation, or DSCP to traffic class mapping.
Parameters
dscp-value
Specifies the ingress DSCP value or range. Enter an integer from 0 to 63.
cos cos-value
Specifies the outbound CoS value. Enter an integer from 0 to 7.
dscp dscp-out
Specifies the outbound DSCP value or range. Enter an integer from 0 to 63.
traffic-class tc-value
Specifies the outbound Traffic Class value. Enter an integer from 0 to 7.
Modes
DSCP CoS configuration mode
Usage Guidelines
Use the no form of the command to reset the default values.
Examples
In DSCP COS configuration mode, the following example maps an ingress DSCP value to an egress CoS value.
In DSCP mutation configuration mode, the following example maps the ingress DSCP values to an egress DSCP value.
In DSCP traffic configuration mode, the following example maps the ingress DSCP values to a traffic class.
History
Release version Command history
map traffic-class
Maps an ingress traffic class to an outbound traffic class, CoS, or DSCP value for a QoS traffic class-to-CoS, traffic class-to-
DSCP, or traffic-class-mutation map.
Syntax
map traffic-class traffic-class-value to { cos cos-value } | { dscp dscp-out } | { traffic-class tc-out }
Command Default
The default values for traffic class-to-CoS, traffic class-to-DSCP, or traffic-class-mutation mapping.
Parameters
traffic-class-value
Specifies the ingress traffic class value. Enter an integer from 0 to 7.
cos cos-value
Specifies the outbound CoS value. Enter an integer from 0 to 7.
dscp dscp-out
Specifies the outbound DSCP value or range. Enter an integer from 0 to 63.
traffic-class tc-out
Specifies the outbound Traffic Class value. Enter an integer from 0 to 7.
Modes
Traffic-class CoS configuration mode
Usage Guidelines
Use the no form of the command to reset the default values.
Examples
In traffic-class CoS configuration mode, the following example maps an ingress traffic-class value to an egress CoS value.
In traffic-class DSCP configuration mode, the following example maps the ingress traffic-class value to a DSCP value.
In traffic-class mutation configuration mode, the following example maps the ingress traffic-class values to an egress traffic-
class value.
History
Release version Command history
Syntax
map vlan [ vlan_id ] {vni } [ vni ]
Parameters
vlan_id
A single VLAN ID or range of VLAN IDs. The range is from 1 through 4096. See the Usage Guidelines.
vni
Specifies the VNI (VXLAN Network Identifier) token.
vni
A single VXLAN VNI or range of VXLAN VNIs. The range is from 1 through 16777215. See the Usage
Guidelines.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
Note the following conditions: [
• Before using this command, first set the VXLAN overlay gateway to layer2-extension, by means of the type
command, and configure the appropriate VLANs to be used by the gateway.
• Before mapping VLANs to VNIs manually, you cannot have automatic mapping configured (by means of the map vlan
vni auto command).
• You cannot map one VLAN to multiple VNIs. Similarly, you cannot map a single VNI to multiple VLANs. For example,
the VLAN-to-VNI mapping should be one to one.
• A single VLAN ID and a range of VLAN IDs can both be specified in a single command as follows: x,y-z. The same
applies to VNIs.
• When using ranges, you must ensure that the number of values in a VLAN ID range corresponds to the number of
values in a VNI range.
• The no forms of this command are allowed only if no VLANs are referenced by means of the extend vlan command
(under a submode of the site command). For example, VLANs extended to a site should have a VNI mapping.
• The no map vlan vni auto command disables the automatic assignment of VNIs. It is not allowed if manual VLAN-to-
VNI mappings have been configured. For example, "auto" VLAN-to-VNI mapping and "explicit" VLAN-to-VNI
mapping are mutually exclusive.
• The no map vlan vlan_id command removes the VNI mappings for one or more VLANs.
• You cannot delete a VLAN (by means of the no interface vlan command) that is referenced by means of the map vlan
vni command.
Examples
The following example configures a manual mapping of VLANs to VNIs in "gateway1".
overlay-gateway gateway1
type layer2-extension mode vxlan-ipv4
map vlan 10 vni 5000
map vlan 20 vni 5001
map vlan 21 vni 5002
map vlan 22 vni 6000
History
Release version Command history
Syntax
map vni { auto }
Command Default
This feature is not enabled.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
Use the no form of this command to undo the automatic mapping.
Examples
The following example configures the automatic mapping of VLANs/BDs) to VNIs.
History
Release version Command history
master-vlan (STP)
Selects a master VLAN for a topology group.
Syntax
master-vlan vlan_id
Command Default
The master VLAN is not configured.
Parameters
vlan_id
The master VLAN ID.
Modes
Topology group configuration mode.
Usage Guidelines
To configure a master VLAN, the VLAN must already be configured. The master VLAN contains the STP settings for all the
VLANs in the STP per VLAN group. An STP group can have only one master VLAN. If you add a new master VLAN to an STP
group that already has a master VLAN, the new master VLAN replaces the older master VLAN.
If you remove the master VLAN (by entering the no master-vlan command), the software selects the new master VLAN from
member VLANs. A new candidate master VLAN will be in configured as a member VLAN so that the first added member
VLAN will be a new candidate master VLAN. Once you save and reload, a member VLAN with the youngest VLAN ID will be
the new candidate master.
Examples
The following example adds the member VLANs to the STP topology group.
History
Release version Command history
match access-group
Matches an ACL to a class map.
Syntax
match access-group name
Parameters
name
The ACL name.
Modes
Class map configuration mode
Usage Guidelines
class-map
Examples
The following example matches an ACL to a class map.
History
Release version Command history
match as-path
Matches an AS-path access list name in a route-map instance.
Syntax
match as-path name
no match as-path
Parameters
name
Name of an AS-path access list. Range is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Enter no match as-path name to disable this feature.
You can configure up to five match AS-Path directives within a single stanza.
Examples
Typical command example:
History
Release version Command history
match community
Configures matching based on a community access list for a route-map instance.
Syntax
match community name
Parameters
name
Name of a community access list. The format is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Enter no match community name to disable matching based on a community list.
Examples
The following example shows how to configure matching based on a community access list named ABCPath for a route map
named myroutes.
History
Release version Command history
match extcommunity
Matches an extended community list in a route-map instance.
Syntax
match extcommunity number
no match extcommunity
Command Default
BGP extended community access list names are not matched.
Parameters
name
Extended community list number. Values range from 1 through 99.
Modes
Route-map configuration mode
Usage Guidelines
You can configure up to five match extcommunity directives within a single stanza.
The no form of the command removes the community match statement from the configuration file.
Examples
The following example configures a route map that matches on extended community ACL 1.
History
Release version Command history
match interface
Matches interface conditions in a route-map instance.
Syntax
match interface { ethernet 0/port | loopback number | port-channel number | ve vlan_id }
no match interface
Parameters
ethernet 0/port
Specifies the Ethernet interface. Enter a valid port number, must be 0 if the switch does not contain slots.
loopback number
Specifies a loopback port number. The range is from 1 through 255.
port-channel number
Specifies a port-channel interface. The range is from 1 through 6144.
ve vlan_id
Specifies the VLAN number. (Refer to the Usage Guidelines.) The range is from 1 through 4095.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to configure the interface match clause in a route-map instance. A maximum of seven interfaces is
supported.
There is no restriction on the number or type of each interface specified, as long as the total is less than or equal to seven.
Examples
The following example configures a route-map that matches on an interface.
History
Release version Command history
Syntax
match ip address acl acl-name
Parameters
acl-name
Specifies an IPv4 ACL name unique among all ACLs (Layer 2 and Layer 3). The name can from 1 through 63
characters in length and must begin with an alphanumeric character. No special characters are allowed, except for the
underscore and hyphen.
Modes
Route-map configuration mode
Usage Guidelines
An NPB route-map stanza can contain only one match { ip | ipv6 | mac | uda } address acl statement.
The absence of a match statement is treated as "match any"; all traffic is forwarded according to the set statement.
Examples
The following example creates an IPv4 ACL that permits traffic from a specific source IP and then includes that ACL in a route-
map stanza.
History
Release version Command history
Syntax
match ip address prefix-list prefix-list-name
Command Default
No routes are distributed based on destination network number.
Parameters
prefix-list-name
Specifies the name of an IP prefix list. Range is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
You can configure up to five match address prefix-list directives within a single stanza.
Use the no form of this command to remove the match.
Examples
The following example matches IP routes that have addresses specified by the prefix list named “myprefixlist”.
History
Release version Command history
Syntax
match ip next-hop prefix-list name
no match ip next-hop
Parameters
prefix-list name
Specifies a IP prefix list. Values range from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify an IP next-hop match clause in a route-map instance.
You can configure up to five match next-hop prefix-list directives within a single stanza.
The no form of the command removes the match ip next-hop prefix-list prefix-list-nameentry.
Examples
The following example matches IP routes that have the next hop specified by the prefix list named “myprefixlist”.
History
Release version Command history
Syntax
match ip route-source prefix-list name
no match ip route-source
Parameters
prefix-list name
Specifies a IP prefix list. Values range from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify an IP route-source match clause in a route-map instance.
You can configure up to five match route-source prefix-list directives within a single stanza.
The no form of the command removes the match ip route-source prefix-list prefix-list-name entry.
Examples
The following example matches IPv6 routes that have the route source specified by the prefix list named “myprefixlist”.
History
Release version Command history
Syntax
match ipv6 address acl acl-name
Parameters
acl-name
Specifies an IPv6 ACL name unique among all ACLs (Layer 2 and Layer 3). The name can from 1 through 63
characters in length and and must begin with an alphanumeric character. No special characters are allowed, except for
the underscore and hyphen.
Modes
Route-map configuration mode
Usage Guidelines
This command is supported only under Network Packet Broker (NPB).
A route-map stanza can contain only one match { ip | ipv6 | mac |uda } address acl statement.
The absence of a match statement is treated as "match any"; all traffic is forwarded according to the set statement.
Examples
The following example creates an IPv6 ACL that permits traffic from specific sources and denies traffic from another source.
The example then includes that ACL in a route-map stanza.
History
Release version Command history
Syntax
match ipv6 address prefix-list prefix-list-name
Command Default
No routes are distributed based on destination network number.
Parameters
prefix-list-name
Specifies the name of an IPv6 prefix list. Range is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
You can configure up to five match address prefix-list directives within a single stanza.
Use the no form of this command to remove the match.
Examples
The following example matches IPv6 routes that have addresses specified by the prefix list named “myprefixlist”.
History
Release version Command history
Syntax
match ipv6 next-hop prefix-list name
Parameters
prefix-list name
Specifies a IPv6 prefix list. Values range from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify an IPv6 next-hop match clause in a route-map instance.
You can configure up to five match next-hop prefix-list directives within a single stanza.
The no form of the command removes the match ipv6 next-hop prefix-list prefix-list-name entry.
Examples
The following example matches IPv6 routes that have the next hop specified by the prefix list named “myprefixlist”.
History
Release version Command history
Syntax
match ipv6 route-source prefix-list name
Parameters
prefix-list name
Specifies an IPv6 prefix list. Range is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify an IPv6 route-source match clause in a route-map instance.
You can configure up to five match route-source prefix-list directives within a single stanza.
The no form of the command removes match ipv6 route-source prefix-list prefix-list-name entry.
Examples
The following example matches IPv6 routes that have the route source specified by the prefix list named “myprefixlist”.
History
Release version Command history
Syntax
match mac address acl acl-name
Parameters
acl-name
Specifies a Layer 2 ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63 characters in
length, and must begin with an alphanumeric character. No special characters are allowed, except for the underscore
and hyphen.
Modes
Route-map configuration mode
Usage Guidelines
A route-map stanza can contain only one match { ip | ipv6 | mac | uda } address acl statement.
The absence of a match statement is treated as "match any"; all traffic is forwarded according to the set statement.
Examples
The following example creates a Layer 2 (MAC) ACL that permits traffic from specific sources and denies traffic from another
source. The example then includes that ACL in a route-map stanza.
History
Release version Command history
match metric
Matches a route metric in a route-map instance.
Syntax
match metric value
no match metric
Parameters
value
Matches a route metric in a route-map instance. Values range from 0 through 4294967295.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify a route-map metric in route-map instance.
Examples
The following example configures a metric that matches on a specified value.
History
Release version Command history
match protocol
Matches routes on protocol types and subtypes in a route-map instance.
Syntax
match protocol { [static] | [ bgp [external | internal]] }
no match protocol
Parameters
bgp external
Matches EBGP routes.
bgp internal
Matches IBGP routes.
static-network
Matches BGP static routes. This is applicable only for BGP outbound policy.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify a route-map protocol in route-map instance.
Examples
The following example configures a protocol for matching route map.
History
Release version Command history
match route-type
Matches a route type in a route-map instance.
Syntax
match route-type [ internal | type-1 | type-2 ]
no match route-type
Parameters
route-type
Matches a route type in a route-map instance.
internal
Internal route type
type-1
OSPF external route type 1
type-2
OSPF external route type 2
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify a route-type in route-map instance.
Examples
Typical command example
History
Release version Command history
match tag
Matches a route tag in a route-map instance.
Syntax
match tag value
no match tag
Parameters
value
Specifies a route tag and route tag value. The range of valid values is from 0 through 4294967295.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify a route tag in route-map instance.
Examples
Typical command example
History
Release version Command history
Syntax
match uda address acl acl-name
Parameters
acl-name
Specifies a UDA ACL name unique among all ACLs (Layer 2, Layer 3, and UDA). The name can from 1 through 63
characters in length and must begin with an alphanumeric character. No special characters are allowed, except for the
underscore and hyphen.
Modes
Route-map configuration mode
Usage Guidelines
This command is supported only in NPB system mode.
A route-map stanza can contain only one match { ip | ipv6 | mac | uda } address acl statement.
The absence of a match statement is treated as "match any"; all traffic is forwarded according to the set statement.
Examples
The following example creates a UDA ACL and then includes that ACL in a route-map stanza.
History
Release version Command history
match vrf
Specifies a non-default VRF in a route-map instance.
Syntax
match vrf name
no match tag
Parameters
vrf name
Specifies a non-default VRF. Valid values range from 0 through 4294967295.
Modes
Route-map configuration mode
Usage Guidelines
Use this command to specify a non-default VRF in a route-map instance.
Examples
Typical command example
History
Release version Command history
max-age
Sets the interval time in seconds between messages that the spanning tree receives from the interface.
Syntax
max-age seconds
no max-age
Command Default
20 seconds.
Parameters
seconds
Configures the STP interface maximum age. Valid values range from 6 through 40.
Modes
Spanning tree configuration mode
Usage Guidelines
Use this command to control the maximum length of time that passes before an interface saves its configuration Bridge
Protocol Data Unit (BPDU) information.
If the vlan parameter is not provided, the seconds value is applied globally for all per-VLAN instances. However, for VLANs that
have been configured explicitly, the per-VLAN configuration takes precedence over the global configuration.
When configuring the maximum age, the max-age command setting must be greater than the hello-time command setting.
The following relationship should be kept:
Examples
History
Release version Command history
maxas-limit
Imposes a limit on the number of autonomous systems in the AS-PATH attribute.
Syntax
maxas-limit in num
no maxas-limit in
Parameters
in
Allows an AS-PATH attribute from any neighbor to impose a limit on the number of autonomous systems.
num
Specifies a value. Valid values range from 0 through 300. The default is 300.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the default of 300.
Examples
The following example sets the limit on the number of BGP4 autonomous systems in the AS-PATH attribute to 100.
History
Release version Command history
maximum-paths (BGP)
Sets the maximum number of BGP4 and BGP4+ shared paths.
Syntax
maximum-paths num | use-load-sharing
no maximum-paths
Parameters
num
Specifies the maximum number of paths across which the device balances traffic to a given BGP destination. Valid
values range is from 1 through 64. The default is 1.
use-load-sharing
Uses the maximum IP ECMP path value supported (64) without enabling BGP level ECMP.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use this command to change the maximum number of BGP4 shared paths, either by setting a value or using the maximum IP
ECMP path value supported (64) without enabling BGP level ECMP.
If the configured num value is less than the possible number of ECMP paths available, BGP routes may not take the same
number of ECMP paths. The set of ECMP paths may not be the same for different prefixes.
Examples
The following example sets the maximum number of BGP4 shared paths to 8.
The following example sets the maximum number of BGP4+ shared paths to 64 without enabling BGP level ECMP.
The following example sets the maximum number of BGP shared paths to 2 in a nondefault VRF instance in the IPv6 address
family.
History
Release version Command history
Syntax
maximum-paths { ebgp num | ibgp num }
no maximum-paths
Parameters
ebgp
Specifies eBGP routes or paths.
ibgp
Specifies iBGP routes or paths.
num
The number of equal-cost multipath routes or paths that are selected. Range is from 1 through 64. 1 disables equal-
cost multipath.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Enhancements to BGP load sharing support the load sharing of BGP4 and BGP4+ routes in IP Equal-Cost Multipath (ECMP),
even if the BGP multipath load-sharing feature is not enabled by means of the use-load-sharing option for the maximum-
paths command. You can set separate values for IGMP and ECMP load sharing. Use this command to specify the number of
equal-cost multipath eBGP or iBGP routes or paths that are selected.
Examples
The following example sets the number of equal-cost multipath eBGP routes or paths that will be selected to 6 in the IPv4
address family.
The following example sets the number of equal-cost multipath iBGP routes or paths that will be selected to 4 in the IPv6
address family.
The following example sets the number of equal-cost multipath eBGP routes or paths that will be selected to 3 for the IPv4
address family for VRF instance "red".
History
Release version Command history
maximum-paths (OSPF)
Changes the maximum number of OSPF shared paths.
Syntax
maximum-paths num
no maximum-paths
Parameters
num
Maximum number of paths across which the device balances traffic to a given OSPF destination. The range is from 1
through 64. The default is 8.
Modes
OSPF router configuration mode
OSPFv3 router configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example sets the maximum number of shared paths to 22.
History
Release version Command history
max-metric router-lsa
Advertises the maximum metric value in different Link State Advertisements (LSAs).
Syntax
max-metric router-lsa [ all-vrfs ] [ all-lsas | external-lsa metric-value | link { all | ptp | stub | transit } | summary-lsa metric-
value | on-startup { time | wait-for-bgp [ all-lsas | summary-lsa metric-value | external-lsa metric-value | link { all | ptp |
stub | transit } ] } ]
no max-metric router-lsa [ all-vrfs ] [ all-lsas | external-lsa | link { all | ptp | stub | transit } | summary-lsa | on-startup { time |
wait-for-bgp [ all-lsas | link [ all ] ] } ]
Parameters
all-vrfs
Applies the configuration change to all instances of OSPF.
all-lsas
Sets the summary-lsa and external-lsa optional parameters to the corresponding default max-metric value. For a
non-default instance of OSPF, only the summary-lsa and external-lsa parameters are set.
external-lsa metric-value
Modifies the metric of all external type 5 LSAs to equal the specified value or a default value. The range for metric
value is 1 to 16777214 (0x00001 - 0x00FFFFFE), and the default is 16711680 (0x00FF0000).
link
Specifies the types of links for which the maximum metric is advertised. By default, the maximum metric is advertised
only for transit links.
all
Advertises the maximum metric in Router LSAs for all supported link types.
ptp
Advertises the maximum metric in Router LSAs for point-to-point links.
stub
Advertises the maximum metric in Router LSAs for stub links.
transit
Advertises the maximum metric in Router LSAs for transit links. This is the default link type.
summary-lsa metric-value
Modifies the metric of all summary type 3 and type 4 LSAs to equal the specified value or a default value. The range
for metric value is 1 to 16777215 (0x00001 - 0x00FFFFFE), and the default is 16711680 (0x00FF0000).
on-startup
Applies the configuration change at the next OSPF startup.
time
Sets the time (in seconds) for which the specified links in Router LSAs are advertised when the metric is set to
the maximum value of 0xFFFF. The range for time is 5 to 86,400.
wait-for-bgp
Indicates that OSPF should wait for either 600 seconds or until BGP has finished route table convergence,
whichever happens first, before advertising the links with the normal metric.
Modes
OSPF router configuration mode
Usage Guidelines
When this command is used, the router configures the maximum value of the metric for routes and links advertised in various
types of LSAs. Because the route metric is set to its maximum value, neighbors will not route traffic through this router except to
directly connected networks. Thus, the device becomes a stub router, which is desirable when you want:
• Graceful removal of the router from the network for maintenance.
• Graceful introduction of a new router into the network.
• To avoid forwarding traffic through a router that is in critical condition.
Enter no max-metric router-lsa all-lsas to disable advertising the maximum metric value in different LSAs.
Examples
The following example advertises the maximum metric value using the all-lsas option.
History
Release version Command history
Syntax
max-metric router-lsa [ all-lsas | external-lsa metric-value | include-stub | on-startup { time | wait-for-bgp } | summary-lsa
metric-value ]
Parameters
all-lsas
Sets the summary-lsa and external-lsa optional parameters to the corresponding default max-metric value. For a
non-default instance of OSPFv3, only the summary-lsa and external-lsa parameters are set.
external-lsa metric-value
Configures the maximum metric value for all external type-5 and type-7 LSAs. The range for metric value is 1 to
16777215 (0x00001 - 0x00FFFFFE).
include-stub
Specifies the advertisement of the maximum metric value for point-to-point and broadcast stub links in the intra-area-
prefix LSA..
on-startup
Applies the configuration change at the next OSPF startup.
time
Sets the time (in seconds) for which the specified links in Router LSAs are advertised when the metric is set to
the maximum value of 0xFFFF. The range for time is 5 to 86400.
wait-for-bgp
Specifies that OSPFv3 should wait until BGP has finished route table convergence before advertising the
links with the normal metric, or for no more than 600 seconds.
summary-lsa metric-value
Configures the maximum metric value for all summary type 3 and type 4 LSAs. The range for metric value is 1 to
16777215 (0x00001 - 0x00FFFFFE).
Modes
OSPFv3 router configuration mode
Usage Guidelines
When this command is used, the router configures the maximum value of the metric for routes and links advertised in various
types of LSAs. Because the route metric is set to its maximum value, neighbors will not route traffic through this router except to
directly connected networks. Thus, the device becomes a stub router, which is desirable when you want:
• Graceful removal of the router from the network for maintenance.
Enter no max-metric router-lsa to disable advertising the maximum metric value in different LSAs.
Examples
The following example configures an OSPFv3 device to advertise a maximum metric and sets the maximum metric value for all
external type-5 and type-7 LSAs to 1000.
The following example configures an OSPFv3 device to advertise a maximum metric and specifies the advertisement of the
maximum metric value for point-to-point and broadcast stub links in the intra-area-prefix LSA.
The following example configures an OSPFv3 device to advertise a maximum metric until BGP routing tables converge or until
the default timer of 600 seconds expires.
The following example configures an OSPFv3 device to advertise a maximum metric and sets the maximum metric value for all
summary type-3 and type-4 LSAs to 100.
History
Release version Command history
max-route
Specifies the maximum number of routes allowed in the routing table per VRF instance, for an IPv4 or IPv6 VRF address
family.
Syntax
max-route value
Command Default
If this command is not configured, the maximum allowed number of routes, 4294967295 (see Parameters), is applied. This
number does not appear in a running configuration.
Parameters
value
The maximum allowed number of routes. Range is from 1 through 4294967295.
Modes
VRF address-family IPv4 and IPv6 configuration modes
Examples
To configure the maximum number of allowed routes to 3600 for VRF "myvrf" for an IPv4 address family:
History
Release version Command history
med-missing-as-worst
Configures the device to favor a route that has a Multi-Exit Discriminator (MED) over a route that does not have one.
Syntax
med-missing-as-worst
no med-missing-as-worst
Modes
BGP configuration mode
Usage Guidelines
When MEDs are compared, by default the device favors a low MED over a higher one. Because the device assigns a value of 0
to a route path MED if the MED value is missing, the default MED comparison results in the device favoring the route paths that
do not have MEDs.
The no form of the command restores the default where a device does not favor a route that has a MED over other routes.
Examples
The following example configures the device to favor a route containing a MED.
History
Release version Command history
member-vlan (STP)
Adds member VLANs to an STP topology group.
Syntax
member-vlan { add | remove } vlan_id
Command Default
The topology group has no member VLANs.
Parameters
add
Add a VLAN to the topology group.
remove
Remove a VLAN from the topology group.
vlan_id
Adds a member VLAN ID to the STP topology group. This can be a single VLAN or a range of VLANs. For example:
2, 4-7, 8, 9-22, 55-66. The maximum input is 253 characters.
Modes
Topology group configuration mode.
Usage Guidelines
The VLAN(s) must be configured before adding to the topology group.
You must first add a master VLAN to the topology group.
All the VLANs in the member group inherit the STP settings of the master VLAN in the group.
Examples
The following example adds the member VLANs to the STP topology group.
History
Release version Command history
metric-type
Configures the default metric type for external routes.
Syntax
metric-type { type1 | type2 }
Command Default
Type 1.
Parameters
type1
The metric of a neighbor is the cost between itself and the device plus the cost of using this device for routing to the
rest of the world.
type2
The metric of a neighbor is the total cost from the redistributing device to the rest of the world.
Modes
OSPF router configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example sets the default metric type for external routes to type 2.
History
Release version Command history
minimum-links
Configures the minimum bandwidth or number of links to be running to allow the port-channel to function.
Syntax
minimum-links num-of-links
no minimum-links
Command Default
Number of links is 1.
Parameters
num-of-links
The number of links. Valid values range from 1 through 64.
Modes
Port-channel interface configuration mode
Usage Guidelines
Use this command to allow a port-channel to operate at a certain minimum bandwidth all the time. If the bandwidth of the port-
channel drops below that minimum number, then the port-channel is declared operationally DOWN even though it has
operationally UP members.
Examples
The following example sets the minimum number of links to 16 on a specific port-channel interface.
History
Release version Command history
mode (LLDP)
Sets the LLDP mode on the device.
Syntax
mode { tx | rx }
Command Default
Both transmit and receive modes are enabled.
Parameters
tx
Specifies to enable only the transmit mode.
rx
Specifies to enable only the receive mode.
Modes
Protocol LLDP configuration mode
Examples
To enable only the transmit mode:
History
Release version Command history
monitor session
Enables a Port Mirroring session for monitoring traffic.
Syntax
monitor session session_number
Parameters
session_number
Specifies a session identification number. Valid values range from 1 through 512.
Modes
Global configuration mode
Usage Guidelines
Enter no monitor session to delete the port mirroring session.
Examples
To enable session 22 for monitoring traffic:
History
Release version Command history
mtu
Configures the size—in bytes—of the maximum transmission unit (MTU) for an Layer 2 packet on a physical or LAG (port-
channel) interface bound to one more VLANs.
Syntax
mtu number
no mtu
Command Default
The default is 1548 bytes.
Parameters
number
Size of the Layer 2 MTU in bytes. Range is from 1548 through 9216.
Modes
Global configuration mode
Usage Guidelines
This command can be executed both globally and on an interface. If it is executed globally, interface configurations take
precedence over the global configuration.
There are no restrictions on the number of MTU profiles within a broadcast domain. Each port, whether physical or LAG, can
have a different MTU value. For physical ports, the MTU is configured on the router port's internal VLAN ID (IVID), which is
allocated when the router port is configured. For LAG ports, the Layer 2 MTU is configured on the VLAN to which a virtual
Ethernet (VE) interface is bound.
Examples
To configure a nondefault Layer 2 MTU globally:
History
Release version Command history
multipath
Changes load sharing to apply to only iBGP or eBGP paths, or to support load sharing among paths from different neighboring
autonomous systems.
Syntax
multipath { ebgp | ibgp | multi-as }
Parameters
ebgp
Enables load sharing of eBGP paths only.
ibgp
Enables load sharing of iBGP paths only.
multi-as
Enables load sharing of paths from different neighboring autonomous systems.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
By default, when BGP load sharing is enabled, both iBGP and eBGP paths are eligible for load sharing, while paths from
different neighboring autonomous systems are not.
Examples
The following example changes load sharing to apply to iBGP paths in the IPv4 address family.
The following example enables load sharing of paths from different neighboring autonomous systems in the IPv6 address
family.
The following example changes load sharing to apply to eBGP paths in IPv4 VRF instance "red":
History
Release version Command history
multiplier (LLDP)
Sets the number of consecutive misses of hello messages before LLDP declares the neighbor as dead.
Syntax
multiplier value
no multiplier
Command Default
Multiplier default value is 4.
Parameters
value
Specifies a multiplier value to use. Valid values range from 2 through 10.
Modes
Protocol LLDP and profile configuration modes
Usage Guidelines
The LLDP multipler can also be configured for a specific LLDP profile. When you apply an LLDP profile on an interface using
the lldp profile command, it overrides the global configuration. If a profile is not present, then the default global profile is used
until you create a valid profile.
Examples
To set the number of consecutive misses:
device(conf-lldp)# multiplier 2
History
Release version Command history
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } activate
Command Default
Enabling address exchange for the IPv4 address family is enabled. Enabling address exchange for the IPv6 address family is
disabled.
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command disables the exchange of an address with a BGP neighbor or peer group.
Examples
The following example establishes a BGP session with a neighbor with the IPv6 address 2001:2018:8192::125.
The following example establishes a BGP EVPN session with a neighbor with the IP address 10.1.1.1.
History
Release version Command history
neighbor advertisement-interval
Enables changes to the interval over which a specified neighbor or peer group holds route updates before forwarding them.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } advertisement-interval seconds
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
seconds
Range is from 0 through 3600. The default is 0.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command restores the default interval.
Examples
The following example changes the BGP4 advertisement interval from the default to 60 seconds.
The following example changes the BGP4+ advertisement interval from the default for VRF instance "red".
History
Release version Command history
neighbor allowas-in
Disables the AS_PATH check function for routes learned from a specified neighbor so that BGP does not reject routes that
contain the recipient BGP speaker's AS number.
Syntax
neighbor {ip-address | ipv6-address | peer-group-name } allowas-in number
Command Default
The AS_PATH check function is enabled and any route whose path contains the speaker's AS number is rejected as a loop.
Parameters
ip-address
Specifies the IP address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
number
Specifies the number of times that the AS path of a received route may contain the recipient BGP speaker's AS
number and still be accepted. Valid values are 1 through 10.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
If the AS_PATH check function is disabled after a BGP session has been established, the neighbor session must be cleared for
this change to take effect.
The no form of the command re-enables the AS_PATH check function.
Examples
The following example specifies that the AS path of a received route may contain the recipient BGP4+ speaker's AS number
three times and still be accepted.
device#configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv6 unicast
device(config-bgp-ipv6u)# neighbor 2001:2018:8192::125 allowas-in 3
%Warning: Please clear the neighbor session for the parameter change to take effect!
The following example specifies for VRF instance "red" that the BGP4+ AS path of a received route may contain the recipient
BGP speaker's AS number three times and still be accepted.
device#configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv6 unicast vrf red
device(config-bgp-ipv6u-vrf)# neighbor 2001:2018:8192::124 allowas-in 3
%Warning: Please clear the neighbor session for the parameter change to take effect!
History
Release version Command history
neighbor as-override
Replaces the autonomous system number (ASN) of the originating device with the ASN of the sending BGP device.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } as-override
Command Default
The ASN is not replaced.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
BGP loop prevention verifies the ASN in the AS path. If the receiving router sees its own ASN in the AS path of the received
BGP packet, the packet is dropped. The receiving router assumes that the packet originated from its own AS and has reached
the place of origination. This can be a significant problem if the same ASN is used among various sites, preventing sites with
identical ASNs from being linked by another ASN. In this case, routing updates are dropped when another site receives them.
Examples
The following example replaces the ASN globally.
The following example replaces the BGP4+ ASN for VRF instance "red".
History
Release version Command history
neighbor bfd
Enables Bidirectional Forwarding Detection (BFD) sessions for specified Border Gateway Protocol (BGP) neighbors or peer
groups.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } bfd [ holdover-interval time | interval transmit-time min-rx receive-
time multiplier number ]
no neighbor { ip-address | ipv6-address | peer-group-name } bfd [ holdover-interval time | interval transmit-time min-rx
receive-time multiplier number ]
Command Default
BFD sessions are not enabled on specific BGP neighbors or peer groups.
Parameters
ip-address
Specifies the IP address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
holdover-interval time
Specifies the holdover interval, in seconds, for which BFD session down notifications are delayed before notification
that a BFD session is down. Valid values range from 1 through 30.
interval transmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer before BFD
determines that the connection to that peer is not operational. Valid values range from 3 through 50.
Modes
BGP configuration mode
Usage Guidelines
Before using the holdover-interval, interval, min-rx, and multiplier parameters, you must first enable BFD using the neighbor
{ ip-address | ipv6-address | peer-group-name } bfd command.
For single-hop BFD sessions, BFD considers the interval values that are configured on the interface, but not the nondefault
values that are configured with this global command.
The no form of the command removes the BFD for BGP configuration for BGP neighbors or peer groups.
Examples
The following example configures BFD for a specified peer group and sets the BFD holdover interval to 18.
The following example configures BFD for a specified peer group and sets the BFD holdover interval 12 for VRF instance
“green”.
The following example configures BFD for a BGP neighbor with the IP address 10.10.1.1 and sets the BFD session timer
values.
History
Release version Command history
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } capability as4 [ disable | enable ]
Command Default
4-byte ASNs are disabled by default.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor .
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
disable
Disables 4-byte numbering.
enable
Enables 4-byte numbering.
Modes
BGP configuration mode
Usage Guidelines
4-byte ASNs are first considered at the neighbor, then at the peer group, and finally at the global level.
The disable keyword or the no form of the command removes all neighbor capability for 4-byte ASNs.
Examples
The following example enables 4-byte ASNs for a specified neighbor.
History
Release version Command history
Syntax
neighbor { ip_address | ipv6_address | peer-group-name } capability orf prefixlist [ receive | send ]
Command Default
ORF capabilities are not advertised to a peer device.
Parameters
ip_address
Specifies the IPv4 address of the neighbor.
ipv6_address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
receive
Enables the ORF prefix list capability in receive mode.
send
Enables the ORF prefix list capability in send mode.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command disables ORF capabilities.
Examples
The following example advertises the ORF send capability to a neighbor with the IP address 10.11.12.13.
The following example advertises the ORF receive capability to a neighbor with the IPv6 address 2001:2018:8192::125 for
VRF instance "red".
History
Release version Command history
neighbor default-originate
Configures the device to send the default route 0.0.0.0 to a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } default-originate
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command configures the device to stop sending the default route.
Examples
The following example sends the default route to the BGP4 neighbor 10.11.12.13.
History
Release version Command history
neighbor description
Specifies a name for a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } description string
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
description string
Specifies the name of the neighbor, an alphanumeric string up to 220 characters long.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command removes the name.
Examples
The following example specifies a BGP4 neighbor name.
The following example specifies a BGP4+ neighbor name for VRF instance "red".
History
Release version Command history
neighbor ebgp-btsh
Enables BGP time to live (TTL) security hack protection (BTSH) for eBGP.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } ebgp-btsh
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
Modes
BGP configuration mode
Usage Guidelines
To maximize the effectiveness of this feature, the neighbor ebgp-btsh command should be executed on each participating
device. The neighbor ebgp-btsh command is supported for both directly connected peering sessions and multihop eBGP
peering sessions. For directly connected neighbors, when the neighbor ebgp-btsh command is used, the device expects BGP
control packets received from the neighbor to have a TTL value of either 254 or 255. For multihop peers, when the neighbor
ebgp-btsh command is used, the device expects the TTL for BGP control packets received from the neighbor to be greater
than or equal to 255 minus the configured number of hops to the neighbor.
Examples
The following example enables GTSM between a device and a neighbor with the IP address 10.10.10.1.
The following example enables GTSM between a device and a neighbor with the IPv6 address 2001:2018:8192::125.
History
Release version Command history
neighbor ebgp-multihop
Allows eBGP neighbors that are not on directly connected networks and sets an optional maximum hop count.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } ebgp-multihop [ max-hop-count ]
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
max-hop-count
Maximum hop count (optional). Range is from 1 through 255.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command disables this feature.
Examples
The following example enables eBGP multihop and sets the maximum hop count to 20.
The following example enables BGP4+ eBGP multihop for VRF instance "red" and sets the maximum hop count to 40.
History
Release version Command history
neighbor enable-peer-as-check
Enables the outbound AS_PATH check function so that a BGP sender speaker does not send routes with an AS path that
contains the ASN of the receiving speaker.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } enable-peer-as-check
Command Default
Disabled.
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
When the neighbor enable-peer-as-check command is used for a BGP address family, a neighbor reset is required.
Examples
The following example enables the outbound AS_PATH check function for the BGP IPv4 unicast address family.
The following example enables the outbound AS_PATH check function for the BGP IPv6 unicast address family.
The following example enables the outbound AS_PATH check function for the L2VPN EVPN unicast address family.
History
Release version Command history
neighbor encapsulation
Sets the encapsulation type for an IPv4 neighbor, IPv6 neighbor, or a peer group.
Syntax
neighbor { IPv4-address | IPv6-address | peer-group-name } { nsh | vxlan }
Command Default
MPLS encapsulation type.
Parameters
IPV4-address
Specifies an IPv4 address.
IPV6-address
Specifies an IPv6 address.
peer-group-name
Specifies a peer group.
nsh
Specifies NSH encapsulation.
vxlan
Specifies VXLAN encapsulation.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example specifies the VXLAN encapsulation for an IPv4 neighbor.
History
Release version Command history
neighbor enforce-first-as
Ensures that a device requires the first ASN listed in the AS_SEQUENCE field of an AS path-update message from eBGP
neighbors to be the ASN of the neighbor that sent the update.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } enforce-first-as [ disable | enable ]
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
disable
Disables this feature.
enable
Enables this feature.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example enables the enforce-first-as feature for a specified neighbor.
The following example enables the enforce-first-as feature for a BGP4+ specified neighbor for VRF instance "red".
History
Release version Command history
neighbor filter-list
Specifies a filter list to be applied to updates from or to the specified neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } filter-list ip-prefix-list-name { in | out }
Command Default
No filter list is applied.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
ip-prefix-list-name
Name of the filter list. The name must be between 1 and 63 ASCII characters in length.
in
Specifies that the list is applied on updates received from the neighbor.
out
Specifies that the list is applied on updates sent to the neighbor.
Modes
BGP address-family IPv4 unicast configuration mode
Examples
The following example specifies that filter list “myfilterlist” be applied to updates to a neighbor with the IP address 10.11.12.13
for the default VRF.
The following example specifies that filter list “2” be applied to updates from a neighbor with the IPv6 address
2001:2018:8192::125 for the default VRF.
The following example specifies that filter list “2” be applied to updates from a neighbor with the IPv6 address
2001:2018:8192::125 for VRF instance "red".
History
Release version Command history
neighbor graceful-shutdown
Configures graceful shutdown of a link to a BGP neighbor or peer group.
Syntax
neighbor [ ipv4-address | ipv6-address | peer-group-name ] graceful-shutdown seconds { community value [ local-
preference value ] | local-preference value } [ route-map route-map-name ]
Command Default
BGP graceful shutdown is disabled.
Parameters
ipv4-address
Specifies a neighbor in IPv4 address format.
ipv6-address
Specifies a neighbor in IPv6 address format.
peer-group-name
Specifies a neighbor as a peer group name (that is configured by using the neighbor peer-group-name command).
graceful-shutdown seconds
Specifies the number of seconds to elapse before graceful shutdown occurs. The range is from 30 through 600.
community value
Specifies the community attribute for BGP graceful shutdown. The range is from 1 through 4294967295.
local-preference value
Specifies the local preference attribute for BGP graceful shutdown. The range is from 0 through 4294967295.
route-map route-map-name
Specifies the route map to apply for BGP graceful shutdown.
Modes
BGP configuration mode
Usage Guidelines
NOTE
neighbor send-community configuration enables sending community attribute information to a BGP peer. Before the
graceful shutdown community attribute can be sent, the send community must be negotiated by using the neighbor
send-community command specifying the both option.
When a neighbor address is not specified, this command configures graceful shutdown for all neighbors on the device.
When a route map is not specified, the default GRACEFUL_SHUTDOWN parameters are applied.
NOTE
Modifications made to the specified route map during the graceful-shutdown period, which is specified using the
graceful-shutdown parameter, are not effective for graceful shutdown advertisement routes.
The no form of the command removes the specified BGP graceful shutdown configuration.
Examples
The following example shows how to configure BGP graceful shutdown for a neighbor (10.11.22.23) and set the shutdown to
occur after 580 seconds.
The following example shows how to configure BGP graceful shutdown for a peer group named grp-1 and set the shutdown to
occur after 620 seconds.
The following example shows how to configure BGP graceful shutdown for a neighbor (10.11.22.23) and apply the attributes
of a route map named myroutemap to the shutdown which is set to occur after 600 seconds.
The following example shows how to configure BGP graceful shutdown for a neighbor (10.11.22.23) with community attribute
20. The shutdown which is set to occur after 600 seconds.
History
Release version Command history
neighbor local-as
Causes the device to prepend the local autonomous system number (ASN) automatically to routes received from an eBGP
peer.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } local-as num [ no-prepend ]
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Local ASN. Range is from 1 through 4294967295.
no-prepend
Causes the device to stop prepending the selected ASN.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command removes the local ASN.
Examples
The following example ensures that a device prepends the local ASN.
The following example stops the device from prepending the selected ASN.
History
Release version Command history
neighbor maxas-limit in
Causes the device to discard routes received in UPDATE messages if those routes exceed a maximum AS path length.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } maxas-limit in { num | disable }
Command Default
Routes received in UPDATE messages are not discarded.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Maximum length of the AS path. Range is from 0 through 300. The default is 300.
disable
Prevents a neighbor from inheriting the configuration from the peer group or global configuration and instead uses the
default system value.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example changes the length of the maximum allowed AS path length from the default.
The following example prevents a neighbor from inheriting the configuration from the peer group or global configuration and
instead use the default system value.
History
Release version Command history
neighbor maximum-prefix
Specifies the maximum number of IP network prefixes (routes) that can be learned from a specified neighbor or peer group.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } maximum-prefix num [ threshold ] [ teardown ]
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Maximum number of IP prefixes that can be learned. Range is from 1 through 2147483647.
threshold
Specifies the percentage of the value specified by num that causes a syslog message to be generated. Range is from
1 through 100.
teardown
Tears down the neighbor session if the maximum number of IP prefixes is exceeded.
Modes
BGP address-family IPv4 unicast configuration mode
BGP address-family IPv6 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example sets the maximum number of prefixes that will be accepted from the neighbor with the IP address
10.11.12.13 to 100000, and sets the threshold value to 80%.
The following example, for VRF instance "red," sets the maximum number of prefixes that will be accepted from the neighbor
with the IPv6 address 2001:2018:8192::125 to 100000, and sets the threshold value to 90%.
History
Release version Command history
neighbor next-hop-self
Causes the device to list itself as the next hop in updates that are sent to the specified neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } next-hop-self [ always ]
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
always
Enables this feature for route reflector (RR) routes.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command disables this feature.
Examples
The following example causes all updates destined for the neighbor with the IP address 10.11.12.13 to advertise this device as
the next hop.
The following example, for VRF instance "red," causes all updates destined for the neighbor with the IPv6 address
2001:2018:8192::125 to advertise this device as the next hop.
History
Release version Command history
neighbor next-hop-unchanged
Enables BGP to keep the original next-hop while advertising routes to eBGP neighbors.
Syntax
neighbor { IPv4-address | IPv6-address | peer-group-name } next-hop-unchanged
Command Default
This functionality is not enabled.
Parameters
IPV4-address
Specifies an IPv4 address.
IPV6-address
Specifies an IPv6 address.
peer-group-name
Specifies a peer group.
Modes
Address-family L2VPN EVPN configuration mode
Usage Guidelines
Use the no form of this command to disable this functionality.
Examples
To enable BGHP to keep the original next-hop for IPv4, IPv6, and a peer group:
History
Release version Command history
neighbor password
Specifies an MD5 password for securing sessions between the device and a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } password string
Command Default
No password is set.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
string
Password of up to 63 characters in length that can contain any alphanumeric character.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes the configured password.
Examples
The following example specifies a password for securing sessions with a specified neighbor.
The following example, for VRF instance "red," specifies a password for securing sessions with a specified neighbor.
History
Release version Command history
neighbor peer-group
Configures a BGP neighbor to be a member of a peer group.
Syntax
neighbor { ip-address | ipv6-address } peer-group string
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group string
Specifies the name of a BGP peer group. The name can be up to 63 characters in length and can be composed of any
alphanumeric character.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes a neighbor from the peer group.
Examples
The following example assigns a specified neighbor to a peer group called “mypeergroup1”.
The following example, for VRF instance "red," assigns a specified neighbor to a peer group called "mypeergroup1".
History
Release version Command history
neighbor prefix-list
Filters the outgoing and incoming route updates to or from a particular BGP neighbor according to IP address and mask length.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } prefix-list string { in | out }
Command Default
No prefix-list is applied.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
string
Name of the prefix list. Range is from 1 through 63 ASCII characters.
in
Applies the filter in incoming routes.
out
Applies the filter in outgoing routes.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example applies the prefix list "myprefixlist" to incoming advertisements to neighbor 10.11.12.13.
The following example applies the prefix list "myprefixlist" to outgoing advertisements to neighbor 2001:2018:8192::125.
The following example applies the prefix list "myprefixlist" to outgoing advertisements to neighbor 2001:2018:8192::125 for
VRF instance "red," .
History
Release version Command history
neighbor remote-as
Specifies the autonomous system (AS) in which a remote neighbor resides.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } remote-as num
Command Default
No AS is specified.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Remote AS number (ASN). Valid values range from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes the neighbor from the AS.
Examples
The following example specifies AS 100 for a neighbor.
History
Release version Command history
neighbor remove-private-as
Configures a device to remove private autonomous system numbers (ASNs) from UPDATE messages that the device sends to
a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } remove-private-as
Command Default
Private ASNs are not removed from UPDATE messages sent to the neighbor.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
The device will remove ASNs 64512 through 65535 (the well-known BGP4 private ASNs) from the AS-path attribute in
UPDATE messages that the device sends to a neighbor.
The no form of the command restores the default so that private ASNs are not removed from UPDATE messages sent to a
neighbor by a device.
Examples
The following example removes private ASNs globally.
The following example removes private ASNs for VRF instance "red".
History
Release version Command history
neighbor route-map
Filters the outgoing and incoming route updates to or from a particular BGP neighbor according to a set of attributes defined in
a route map.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } route-map { in string | out string }
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
in
Applies the filter on incoming routes.
string
Name of the route map. Range is from 1 through 63 ASCII characters.
out
Applies the filter on outgoing routes.
Modes
BGP address-family IPv4 unicast configuration mode
BGP address-family IPv6 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example applies a route map named "myroutemap" to an outgoing route from 10.11.12.13.
The following example applies a route map named "myroutemap" to an incoming route from 2001:2018:8192::125.
History
Release version Command history
neighbor route-reflector-client
Configures a neighbor to be a route-reflector client.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } route-reflector-client
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use this command on a host device to configure a neighbor to be a route-reflector client. Once configured, the host device
from which the configuration is made acts as a route-reflector server.
Examples
The following example configures a neighbor to be a route-reflector client.
The following example configures a neighbor to be a route-reflector client for VRF instance "red".
History
Release version Command history
neighbor send-community
Enables sending the community attribute in updates to the specified BGP neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } send-community [ both | extended | standard ]
Command Default
The device does not send community attributes.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
both
Sends both standard and extended attributes.
extended
Sends extended attributes.
standard
Sends standard attributes.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Usage Guidelines
If the send-community attribute is enabled after a BGP session has been established, the neighbor session must be cleared for
this change to take effect.
Examples
The following example sends standard community attributes to a neighbor.
The following example sends extended community attributes to a neighbor for VRF instance "red".
History
Release version Command history
neighbor shutdown
Causes a device to shut down the session administratively with its BGP neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } shutdown [ generate-rib-out ]
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
generate-rib-out
When a peer is put into the shutdown state, Routing Information Base (RIB) outbound routes are not produced for that
peer. Use this option to produce those routes.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
Shutting down a session lets you configure the neighbor and save the configuration without the need to establish a session with
that neighbor.
Examples
The following example a device to shut down the session administratively with its neighbor.
The following example causes a device to shut down the session administratively with its neighbor and generate RIB outbound
routes for VRF instance "red".
History
Release version Command history
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } soft-reconfiguration inbound
no neighbor { ip-address | ipv6-address | peer-group-name } soft-reconfiguration inbound
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
If you request a soft reset of inbound routes, the software compares the policies against the stored route updates, instead of
requesting the neighbor’s BGP4 or BGP4+ route table or resetting the session with the neighbor.
Examples
The following example globally stores route updates from a BGP4 neighbor.
The following example stores route updates from a BGP4+ neighbor for VRF instance "red".
History
Release version Command history
neighbor static-network-edge
Overrides the default BGP4 behavior and advertises the network to a neighbor or peer group only when the corresponding
route is installed as a forward route in the routing table.
Syntax
neighbor { ip-address | peer-group-name } static-network-edge
Parameters
ip-address
IPv4 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
A BGP static network is always advertised to neighbors or a peer group, and if the corresponding route is not present in the
routing table, BGP installs the null0 route. This command overrides the default behavior. This command is not supported for
BGP4+.
Examples
The following example globally overrides the default BGP4 behavior.
The following example overrides the default BGP4 behavior for VRF instance "red".
History
Release version Command history
neighbor timers
Specifies how frequently a device sends KEEPALIVE messages to its BGP neighbors, as well as how long the device waits for
KEEPALIVE or UPDATE messages before concluding that a neighbor is dead.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } timers keep-alive keepalive_interval hold-time holdtime_interval
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
keep-alive keepalive_interval
Frequency (in seconds) with which a device sends keepalive messages to a peer. Range is from 0 through 65535
seconds. The default is 60.
hold-time holdtime_interval
Interval in seconds that a device waits to receive a keepalive message from a peer before declaring that peer dead.
Range is from 0 through 65535 seconds. The default is 180.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command restores the defaults.
Examples
The following example sets the keepalive timer for a device to 120 seconds and the hold-timer to 360 seconds.
The following example sets the keepalive timer to 120 seconds and the hold-timer to 360 seconds for VRF instance "red" .
History
Release version Command history
neighbor unsuppress-map
Removes route suppression from BGP neighbor routes when those routes have been suppressed as a result of aggregation. All
routes matching route-map rules are unsuppressed.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } unsuppress-map string
Command Default
Route suppression is not removed.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
string
Name of the route map. Range is from 1 through 63 ASCII characters.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following BGP4 example removes route suppression for the default VRF.
The following BGP4+ example removes route suppression for VRF instance "red".
History
Release version Command history
neighbor update-source
Configures the BGP device to communicate with a neighbor through a specified interface.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } update-source { ip-address | ethernet slot / port | loopback num|
ve-interface vlan_id }
no neighbor { ip-address | ipv6-address | peer-group-name } update-source { ip-address | ethernet slot / port | loopback num
| ve-interface vlan_id }
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
ip-address
IP address of the update source.
ethernet
Specifies an ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
loopback num
Specifies a loopback interface.
ve-interface vlan_id
Specifies a virtual Ethernet VLAN interface.
Modes
BGP configuration mode
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example configures the device to communicate with a neighbor through the specified IPv4 address and Ethernet
interface 0/2.
History
Release version Command history
neighbor weight
Specifies a weight that the device will add to routes that are received from the specified BGP neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } weight num
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor
peer-group-name
Name of the peer group.
num
Value from 1 through 65535. The default is 0.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
BGP prefers larger weights over smaller weights.
Examples
The following example changes the weight from the default.
The following example changes the weight from the default for VRF instance "red".
History
Release version Command history
network
Configures the device to advertise a BGP network.
Syntax
network network/mask [ backdoor | route-map map-name | weight num ]
Command Default
No network is advertised.
Parameters
network/mask
Network and mask in CIDR notation.
backdoor
Changes administrative distance of the route to this network from the eBGP administrative distance (the default is 20)
to the local BGP weight (the default is 200), tagging the route as a backdoor route.
route-map map-name
Specifies a route map with which to set or change BGP attributes for the network to be advertised. Range is from 1
through 63 ASCII characters.
weight num
Specifies a weight to be added to routes to this network. Range is 0 through 65535. The default is 0.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command disables this feature.
Examples
The following example imports the IP prefix 10.1.1.1/32 into the BGP4 database and specifies a route map called
“myroutemap”.
The following example imports the IPv6 prefix 2001:db8::/32 into the BGP4+ database and sets a weight of 300.
History
Release version Command history
next-hop-enable-default
Configures the device to use the BGP default route as the next hop.
Syntax
next-hop-enable-default
no next-hop-enable-default
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command removes the default route as the next hop.
Examples
The following example configures the device to use the default route as the next hop.
The following example configures the device to use the default route as the next hop.
History
Release version Command history
next-hop-recursion
Enables BGP recursive next-hop lookups.
Syntax
next-hop-recursion
no next-hop-recursion
Command Default
BGP recursive next-hop lookups are not enabled.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
If the BGP next hop is not the immediate next hop, a recursive route lookup in the IP routing information base (RIB) is needed.
With recursion, a second routing lookup is required to resolve the exit path for destination traffic. Use this command to enable
recursive next-hop lookups.
Examples
The following example enables recursive next-hop lookups for BGP4.
History
Release version Command history
Syntax
npb policy route-map route-map-name
Command Default
No route map is applied as NPB policy.
Parameters
route-map-name
Specifies the route map. Values range from 1 through 63 ASCII characters.
Modes
Interface sub-type configuration mode
Usage Guidelines
This command is supported only for NPB. If the system mode is currently default, set it to NPB, using the system-mode
command.
The no form of this command removes a route map previously applied for NPB policy.
Examples
The following example applies a route map to a physical interface.
History
Release version Command history
ntp authentication-key
Creates an authentication key to associate with the NTP server, thereby enabling NTP authentication.
Syntax
ntp authentication-key key-id {md5 md5-string | sha1 sha1-string}encryption-level enc_value
Command Default
NTP authentication is disabled by default.
Parameters
key-id
Specifies an ID for an authentication key. The range is from 1 through 65535.
md5 md5-string
Specifies a string for the MD5 message-digest algorithm. The string can be a maximum of 15 ASCII characters.
encryption-level enc_value
Defines the level of encryption for the NTP authentication key. The valid values are 0 and 7. The value 0 is clear text
format and the value 7 is fully encrypted format. The default value is 7.
sha1 sha1-string
Specifies a string for SHA1 encryption. The string can be a maximum of 15 ASCII characters.
Modes
Global configuration mode
Usage Guidelines
This command adds an NTP authentication key to a list of authentication keys in the database. The key is shared by the client
(device) and an external NTP server.
The maximum number of configurable NTP authentication keys is five. You cannot configure a duplicate key ID with a different
key string. Use the no ntp authentication-key key-id command to remove the specified authentication key.
Authentication key must be created before associating the key with any server. Refer to the ntp server command for information
on how to create this association.
Before downgrading the firmware to a version that does not support the encryption-level option, the encryption-level should be
set to 0.
Examples
To create an authentication key with an ID of 33, an MD5 string called check, and an encryption level of 0 :
device# configure
device(config)# ntp authentication-key 33 md5 check encryption-level 0
History
Release version Command history
ntp server
Specifies or adds an NTP server IP address and optionally associates an authentication key to the server.
Syntax
ntp server ip-address [ key key-id ] [ use-vrf vrf-name ]
Command Default
The NTP server list is LOCL (no NTP server configured).
Parameters
ip-address
Specifies the NTP server IPv4 IP address (dot-decimal notation) or the IPv6 IP address (hexadecimal colon-separated
notation).
key key-id
Associates a key from the key list to the specified server. The range for a key ID is from 1 through 65535.
use-vrf vrf-name
Specifies a VRF through which to communicate with the NTP server. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Use this command to add an NTP server IPv4 or IPv6 address to a list of server IP addresses, or to associate an existing
authentication key with an NTP server IP address.
Use the no ntp server ip-address command to remove the specified NTP server IP address. Removing the current active NTP
server resets the NTPstatus to "LOCL" until a new, active server is selected.
Use the no ntp server ip-address key key-id command to remove the key from the specified NTP IP address.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
Examples
To associate a configured key ID of 15 to an NTP server on the management VRF:
To remove an NTP server from the current list of NTP servers on the management VRF:
History
Release version Command history
ntp source-ip
Configures the source IP address to be used to access the NTP server.
Syntax
ntp source-ip chassis-ip ip_address
no ntp source-ip
Command Default
The NTP source IP is not configured.
Parameters
chassis-ip ip_address
Uses the IP address of the chassis for the NTP server.
Modes
Global configuration mode
Usage Guidelines
Use the no ntp source-ip command to remove the configuration.
Examples
Typical command example:
History
Release version Command history
oscmd
Runs commands or scripts supported by the Linux OS directly from the SLX-OS CLI.
Syntax
oscmd { Linux-command | script-name }
Parameters
Linux-command
Specifies the Linux command that you want to run.
script-name
Specifies the script that you want to run.
Modes
Privileged EXEC mode
Usage Guidelines
This command is only available for users with admin-level permissions.
After writing and testing a user-defined script file, you can copy it to the Extreme device. Imported scripts are stored in
the /var/config/vcs/scripts directory.
You can also create scripts from the Linux shell using the "vi" editor. The newly-created scripts must exist in the /fabos/
users/admin directory.
Although as an SLX-OS admin you have permissions to run the following commands from the Linux shell, you do not have
permissions to run them—from the SLX-OS CLI—appended to the oscmd command.
• bash
• script
• vi
• vim
Examples
In the following example, the Linux ps -ef command lists the process status from the CLI.
...
In the following example, "my_script" is the name of a user-defined script that is downloaded by using the copy command or
exists in the /fabos/users/admin directory; and is executable under the Linux OS .
History
Release version Command history
overlay-class-map
Specifies an overlay class map and enters overlay-class-map configuration mode
Syntax
overlay-class-map class-map-name
no overlay-class-map class-map-name
Command Default
No overlay class map is created.
Parameters
class-map-name
Name of an overlay class map. The map name is restricted to 63 characters. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Enter no overlay-class-mapclass-map-name while in global configuration mode to remove the overlay class map.
The following rules govern overlay policy maps:
• An overlay policy map name must begin with a–z, A–Z or 0–9. Underscore and hyphen can also be used, except as
the first character, and the name length can not exceed 63 characters.
• The overlay policy must contain an overlay-class-map directive that contains the information necessary to identify the
tunnel or tunnels on which the policy is to apply.
• The overlay policy must contain at least one statement for matching the inner flow (achieved through ACL matching)
and the action to take on the matching flow. The supported actions are any existing ACL security action (permit or
deny), as well as any desired flow-based QoS result (for example, sampling or mirroring).
• Forward referencing of ACLs or service-policy maps is not allowed. The user must first define the objects to be
contained in the policy map (ACLs or Qos service maps) before referencing them in an overlay policy map. The
forward referencing of an object causes an error to be returned during such a configuration.
Examples
The following creates an overlay class map and place the system into overlay classmap configuration mode.
Once the map is created, criteria must be matched by means of the seq command, as in the following example.
History
Release version Command history
overlay-gateway
Creates a VXLAN overlay gateway instance and enables VXLAN overlay gateway configuration mode.
Syntax
overlay-gateway name
no overlay-gateway name
Command Default
The default VXLAN overlay gateway setting for type is layer2-extension.
Parameters
name
Specifies a name for the VXLAN overlay gateway. Only one gateway instance can be configured. The name is an
alphanumeric, 32-character-maximum string that can also contain hyphens and underscores.
Modes
Global configuration mode
Usage Guidelines
Use this command to create a VXLAN overlay gateway instance with the given name. An overlay network is a virtual network
that is built on top of existing network Layer 2 and Layer 3 technologies. The objectives of setting up a gateway are:
• Configuring the source IP address
• Configuring the VLAN or VLANs
• Configuring MAC addresses to export to the VXLAN domain
• Enabling statistics collection for VLAN domains
• Enabling SPAN
One you create the gateway instance, you enter VXLAN overlay gateway configuration mode, where you can configure other
properties for this gateway. The key commands available in this mode are summarized below:
TABLE 4 Key commands available in VXLAN overlay gateway configuration mode (continued)
Command Description
site Configures a remote Layer 2 extension site in a VXLAN overlay
gateway context.
type Specifies whether a VXLAN overlay gateway uses NSX Controller
integration or Layer 2 extension.
Only one VXLAN overlay gateway instance can be configured per system.
Use the no overlay-gateway command to delete the VXLAN overlay gateway instance from the cluster. All tunnels for the
gateway are also deleted. There are no other no forms of this command.
By default, a VXLAN overlay gateway instance is inactive. To activate an instance, first configure its other properties, and then
enter the activate command.
Examples
The following example creates a VXLAN overlay gateway instance named "gateway1" and enter VXLAN overlay gateway
configuration mode.
History
Release version Command history
overlay-policy-map
Configures an overlay policy map containing a class map so that you can apply policer and QoS attributes to a particular
interface.
Syntax
overlay-policy-map policy-mapname
no overlay-policy-map policy-mapname
Command Default
No overlay policy map is created.
Parameters
policy-mapname
Name of an overlay policy map.
Modes
Global configuration mode
Usage Guidelines
When you execute the overlay-policy-map command, the system is placed in config-overlay-policy-map configuration mode
for the configured map. At this point, you can add a class map containing policing parameters to the policy map. (Refer to the
description of the class command.)
This command creates a policer policy map to apply policer and QoS attributes to a particular interface. The class map can be
associated with specific policing and QoS parameters.
Associate the policy map to the interface for the inbound direction by means of the overlay-service-policy command.
Enter no overlay-policy-map policy-mapname while in global configuration mode to remove the policy map.
Examples
The following example creates an overlay policy map and places the system into overlay policymap configuration mode so that
you can add a class map.
Once the map is created, you must attach the overlay policy map and QoS actions, security ACLs, or both, by means of the seq
and ip access-group commands, as in the following example.
History
Release version Command history
overlay-service-policy
Binds an overlay policy map to an overlay gateway or overlay transit instance.
Syntax
overlay-service-policy { in } policy-mapname
no overlay-service-policy{ in } policy-mapname
Command Default
No overlay policy map is bound.
Parameters
in
Specifies that the policy be applied on ingress traffic (required).
policy-mapname
Name of an overlay policer policy map.
Modes
Overlay gateway instance configuration mode
Usage Guidelines
Only ingress policies are supported.
Examples
The following example binds a policy map to an overlay gateway instance.
The following example binds a policy map to an overlay transit instance on a spine node.
The following example unbinds the policy map from the above instance.
History
Release version Command history
overlay-transit
Creates a VXLAN overlay transit instance.
Syntax
overlay-trnasit name
no overlay-transit name
Command Default
This feature is not enables.
Parameters
name
Specifies a name for the VXLAN overlay transit instance. Only one gateway instance can be configured. The name is
an alphanumeric, 32-character-maximum string that can also contain hyphens and underscores.
Modes
Global configuration mode
Usage Guidelines
Use this command to create a VXLAN overlay transit instance on a spine node. From there the overlay-service-policy
command is available, through which the user can enter VXLAN overlay service policy configuration mode.
Examples
The following example creates a VXLAN overlay transit instance named "myOTinstance" and enables VXLAN overlay gateway
configuration mode.
History
Release version Command history
owner
Allows owner preemption and tracked interface priority configuration for a virtual router designated as the Virtual Router
Redundancy Protocol (VRRP) owner.
Syntax
owner priority value
Command Default
The VRRP owner priority is set to 255 and interface tracking priorities are set individually.
Parameters
priority value
Enables owner preemption by setting the priority of the VRRP owner device to be less than the default value. Value
can be from 1 to 254.
track-priority value
Sets the owner track priority value if the tracked port fails. The tracked interface value configured for the owner device
overrides any configured individual tracked interface priorities. Value can be from 1 to 254. Default is 2.
Modes
Virtual-router-group configuration mode
Usage Guidelines
VRRP owner preemption allows a lower device priority to be set and if a backup VRRP device has a higher priority, the backup
device assumes the master VRRP role and the current owner device becomes a backup device. If an owner track priority is
configured, the backup device priority must be higher than the combination of the owner priority and the current tracked
interface priorities.
The no owner priority command disables owner preemption and reverts the priority value to 255.
The no owner track-priority command removes the owner track priority, allowing individual interface track priorities to be used.
Examples
The following example configures the VRRP owner device priority to 200 and the tracked interface priority to 20.
History
Release version Command history
password-attributes
Configures global password attributes.
Syntax
password-attributes { [ max-retry maxretry ] [ min-length minlen ] [ max-lockout-duration duration ] [ admin-lockout |
character-restriction { [ lower numlower ] [ numeric numdigits ] [ special-char numsplchars ] [ upper numupper ] } }
Command Default
The default for min-length is 8. All other defaults are 0.
Parameters
admin-lockout
Enables lockout for admin role accounts.
character-restriction
Configures the restriction on various types of characters.
lower numlower
Specifies the minimum number of lowercase alphabetic characters that must occur in the password. Values
range from 0 through 32 characters. The default value is 0.
numeric numdigits
Specifies the minimum number of numeric characters that must occur in the password. Values range from 0
through 32 characters. The default is 0.
special-char numsplchars
Specifies the number of punctuation characters that must occur in the password. All printable,
nonalphanumeric punctuation characters, except colon (:) are allowed. Values range from 0 through 32
characters. The default value is 0.
upper numupper
Specifies the minimum number of uppercase alphabetic characters that must occur in the password. Values
range from 0 through 32 characters. The default value is 0.
max-retry maxretry
Specifies the number of failed password logins permitted before a user is locked out. Values range from 0 through 16
attempted logins. The default value is 0.
min-length minlen
Specifies the minimum length of the password. Valid values range from 8 through 32 characters. The default is 8
characters.
max-lockout-duration duration
Specifies the maximum number of minutes after which the user account is unlocked. Range is from 0 through 99999.
The default is 0, representing an infinite duration.
Modes
Global configuration mode
Usage Guidelines
To reset password attributes to their default values, enter the no form of this command.
Examples
The following example configures global password attributes and verifies the configuration.
device#configure terminal
device(config)# password-attributes max-retry 4
device(config)# password-attributes character-restriction lower 2
device(config)# password-attributes character-restriction upper 1 numeric 1 special-char 1
device(config)# exit
device# show running-config password-attributes
password-attributes max-retry 4
password-attributes character-restriction upper 1
password-attributes character-restriction lower 2
password-attributes character-restriction numeric 1
password-attributes character-restriction special-char 1
The following example resets the character restriction attributes and verifies the configuration.
device#configure terminal
device(config)# no password-attributes character-restriction lower
device(config)# no password-attributes character-restriction upper
device(config)# exit
device# show running-config password-attributes
password-attributes max-retry 4
password-attributes character-restriction numeric 1
password-attributes character-restriction special-char 1
device#configure terminal
device(config)# no password-attributes
device(config)# exit
device# show running-config password-attributes
% No entries found.
The following example sets the maximum number of retries to 3 and enables lockout policy for admin role accounts.
device#configure terminal
device(config)# password-attributes max-retry 3 admin-lockout
The following example specifies that the user account be unlocked after 5 minutes and enables lockout policy for admin role
accounts.
device#configure terminal
device(config)# password-attributes max-lockout-duration 5 admin-lockout
History
Release version Command history
pbf destination
Creates a policy-based forwarding (PBF) destination and accesses PBF-destination configuration mode.
Syntax
pbf destination pbf-destination-id
Command Default
No PBF destinations are defined.
Parameters
pbf-destination-id
Specifies a policy-based forwarding (PBF) destination. ID values range from 1 through 8192.
Modes
Global configuration mode
Usage Guidelines
The use-case for this command is under Network Packet Broker (NPB) system mode.
The PBF-destination ID must be unique across all devices managed on the Extreme Visibility Manager instance.
Examples
The following example defines a PBF destination and accesses PBF-destination configuration mode.
History
Release version Command history
pbf destination-group
Creates a policy-based forwarding (PBF) destination-group and accesses PBF destination-group configuration mode.
Syntax
pbf destination-group pbf-dest-group-id
Command Default
No PBF destination-groups are defined.
Parameters
pbf-dest-group-id
Specifies a policy-based forwarding (PBF)-destination group. Values range from 1 through 8192.
Modes
Global configuration mode
Usage Guidelines
The use-case for this command is under Network Packet Broker (NPB) system mode.
Examples
The following example creates or accesses a PBF distribution group and adds destinations to it.
History
Release version Command history
peer (MCT)
Configures the IP address for the MCT cluster peer.
Syntax
peer ip-address
no peer ip-address
Parameters
ip-address
Specifies the IP address for the cluster peer. The peer IP address is the remote MCT node IP address.
Modes
Cluster configuration mode.
Usage Guidelines
Configure a corresponding neighbor in BGP EVPN address family for the peer. If the peer is already configured as a neighbor,
when you deploy and undeploy the cluster, the BGP neighbor resets to renegotiate its capability.
If the peer already exists for other address family, clear the IP BGP peer session.
The no peer command causes a controlled failover and the target node is removed permanently from the cluster. Primary and
secondary controlled failover is supported, as is primary and secondary uncontrolled failover (on loss of heartbeat).
If, for example, Node A is aware of its peer, Node B, and Node B is not aware of Node A, then Node A becomes the principal
node. This can happen if the no peer command is executed on only a single node in the cluster.
Examples
The following example shows the configuring of the cluster peer IP address.
History
Release version Command history
peer-interface
Configures the Ethernet or port channel interface to reach the MCT cluster peer.
Syntax
peer-interface Ethernet 0/port | port-channel ID
no peer-interface
Parameters
Ethernet 0/port
Specifies the Ethernet port for the cluster peer.
port-channel ID
Specifies the port channel interface for the cluster peer.
Modes
Cluster configuration mode.
Usage Guidelines
The no form of the command deletes the peer interface configuration.
The peer interface must be a Layer 2 interface. When it is configured, it is an internal switch port.
You must configure the peer interface before deploying the cluster configuration.
You cannot change the peer interface when the cluster is deployed.
Examples
The following example shows the configuring of the cluster peer interface.
History
Release version Command history
permit ip host
Creates a rule in an Address Resolution Protocol (ARP) ACL that permits ARP messages from a host specified by both IP and
MAC addresses.
Syntax
permit ip host sender-ip mac host sender-mac-address
Command Default
No permit rules are defined.
Parameters
sender-ip
Specifies the sender IP address.
mac host sender-mac-address
Specifies the sender MAC address, in hexadecimal format.
Modes
ARP ACL configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC addresses are accepted only if
all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
The no form of the command removes the permit rule from the ACL.
Examples
The following example defines a permit ip host rule in an ARP ACL, applies the ACL to a VLAN, and enables DAI on that
VLAN.
The following example creates a permit ip host rule within the arp access-list command.
History
Release version Command history
police cir
Configures the committed information rate, committed burst size, exceeded information rate, and the exceeded burst size for
the class map.
Syntax
police cir cir-bps [ cbs bytes ] [ eir bps [ ebs bytes ] ] [classification-type classification-type-name ] [ remark-profile profile-
name]
Parameters
cir-bps
Specifies the committed information rate in bits per second. Enter an integer from 18000 to 300000000000.
cbs bytes
Specifies the committed burst size in bytes. Enter an integer from 1250 to 37500000000.
eir bps
Specifies the exceeded information rate in bits per second. Enter an integer from 0 to 300000000000.
ebs bytes
Specifies the exceeded burst size in bytes. Enter an integer from 1250 to 37500000000.
classification-type classification-type-name
Specifies the name of the classification type for remarking. Choices include the following:
• color-and-cos
• color-and-dscp
• color-and-traffic-class
remark-profile profile-name
Specifies the remark profile that contains the parameters used for remarking.
Modes
Policy-map class configuration mode
Usage Guidelines
Use the no version of this command to remove the parameter from the class map.
Only the police cir command is mandatory for configuring a class map.
If the optional parameters for a class map are not set, they are treated as disabled. To delete parameters for a class-map, you
must delete all policer parameters while in the policy-map class configuration mode using the no police cir command.
Examples
The following example sets the committed information rate (cir), committed burst size (cbs), exceeded information rate (eir), and
the exceeded burst size (ebs).
History
Release version Command history
police-remark-profile
Allows you to modify the default profile used for policer remarking. Only the default profile is supported.
Syntax
police-remark-profile profile-name
Command Default
The existing settings in the default profile.
Parameters
profile-name
The name of the profile. For policing remarking, only default is supported.
Modes
Global configuration mode
Usage Guidelines
You can edit the default profile, but you cannot delete it. The attributes in the default remark profile are those that were specified
during the latest modification. If the remark profile has never been modified, then the options are those that were specified in the
default remark profile provided during initialization.
After you execute the police-remark-profile command, you use the action, set, and map commands to modify the settings in
the policer remark profile.
Examples
The following is an example of executing the police-remark-profile command to begin the process of modifying the default
policer remark profile. The example also shows using the action command to specify the color classification type for
conforming traffic. Then, the example shows using the set command to specify the settings for the remark values in the default
policer remark profile.
The following is an example of executing the police-remark-profile command to begin the process of modifying the default
policer remark profile. The example also shows using the action command to specify the color-and-cos classification type for
exceed traffic. Then, the example shows using the map command to specify the maps to be included in the default policer
remark profile for cos remarking for exceeding traffic. ("cm1," "ct1," and "cd1" are map names).
History
Release version Command history
policy-map
Configures a policy map containing a class map so that you can apply policer and QoS attributes to a particular interface.
Syntax
policy-map policy-mapname
no policy-map policy-mapname
Command Default
No policy map is created.
Parameters
policy-mapname
Name of police policy map
Modes
Global configuration mode
Usage Guidelines
When you launch the policy-map command, the system is placed in config-policymap mode for the configured map. At
this point, you can add a class map containing policing parameters to the policy map. (Refer to the description of the class
command.)
This command creates a policer policy map to apply policer and QoS attributes to a particular interface. The class map can be
associated with specific policing and QoS parameters.
Associate the policy map to the interface for inbound or outbound direction with the service-policy command.
Enter no policy-map policy-mapname while in global configuration mode to remove the policy map.
Examples
Create a policy map and place system into config-policymap mode so that you can add a class map.
History
Release version Command history
port
Defines the TCP connection port of the LDAP host.
Syntax
port { portnum }
no port
Command Default
The default port is 389.
Parameters
portnum
Specifies the TCP port used to connect the AD server for authentication. The port range is from 1 through 65535.
Modes
LDAP host configuration mode.
Usage Guidelines
Use the no form of this command to remove the port.
Examples
To add an LDAP server on port 3890:
History
Release version Command history
port-channel path-cost
Sets the port channel path cost behavior.
Syntax
port-channel path-cost [ custom | standard ]
Command Default
Path cost is standard.
Parameters
custom
Specifies to use the custom behavior, which sets the path cost changes according to the port-channel’s bandwidth.
standard
Specifies to use the standard behavior, which sets that the path cost does not change according to port-channel’s
bandwidth.
Modes
Spanning tree configuration mode
Examples
To set the behavior for the path cost to custom:
History
Release version Command history
preempt-mode
Enables or disables preempt mode for a VRRP or VRRP Extended (VRRP-E) router session.
Syntax
preempt-mode
no preempt-mode
Command Default
Enabled for VRRP; Disabled for VRRP-E.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command is for VRRP and VRRP-E.
When set, the highest-priority backup router will always be the master if the owner is not available. If not set, a higher priority
backup will not preempt a lower-priority master.
Examples
To turn on preempt mode for a virtual-router-group 1 session:
History
Release version Command history
priority
Sets the priority of a physical router in a VRRP router group.
Syntax
priority range
Command Default
The default priority is 100.
Parameters
range
The priority of a physical router in a virtual router group. Higher numbers have priority over lower numbers. Valid values
range from 1 to 254.
Modes
Virtual-router-group configuration mode
Usage Guidelines
You can perform this command for VRRP or VRRP-E.
When set, the highest priority backup router will always be the master. (For VRRP, however, the owner is always the master if it is
available.) If not set, a higher priority backup will not preempt a lower priority backup that is acting as master.
For an owner router in VRRP, the priority automatically becomes 255 if the virtual IP address of the virtual router and the real IP
address of the owner are the same.
Examples
To set the priority to 110 for the VRRP virtual group 1:
History
Release version Command history
priority1
In PTP configuration mode, specifies a nondefault clock Priority1 value for selecting the Precision Time Protocol best master
clock (BMC).
Syntax
priority1 priority
no priority1
Command Default
See the Usage Guidelines.
Parameters
priority
The clock Priority1 value used by the Best Master Clock Algorithm (BMCA). Range is from 0 through 255. The default
is 255. See the Usage Guidelines.
Modes
PTP configuration mode
Usage Guidelines
The value for this setting influences whether the node can be elected a grandmaster (GM) clock or not. In practical deployments,
the default value (255) is recommended. The GM clock, if present, takes over.
Use the no form of this command to revert to the default Priority1 value.
Examples
To change the value of the BMCA Priority1 field from the default:
History
Release version Command history
priority2
In PTP configuration mode, specifies a nondefault clock Priority2 value for selecting the Precision Time Protocol best master
clock (BMC).
Syntax
priority2 priority
no priority2
Command Default
See the Usage Guidelines.
Parameters
priority
The clock Priority2 value used by the Best Master Clock Algorithm (BMCA). Range is from 0 through 255. The default
is 255.
Modes
PTP configuration mode
Usage Guidelines
The Priority2 value is used by the BMCA to decide between two devices that are otherwise equally matched with respect to
default selection criteria (such as clock quality, clock class, and clock stability).
Use the no form of this command to revert to the default Priority2 value.
Examples
To change the value of the BMCA Priority2 field from the default:
History
Release version Command history
priority-group-table
Configures the CEE priority group table mapping for the Priority Group ID (PGID).
Syntax
priority-group-table pgid weight weight pfc { on | off }
no priority-group-table pgid
Command Default
See the following table for the default settings for each PGID.
15.0 - N
15.1 - N
15.2 - N
15.3 - N
15.4 - N
15.5 - N
15.6 - N
15.7 - N
0 0 N
1 40 Y
2 60 N
3 0 N
4 0 N
5 0 N
6 0 N
7 0 N
Parameters
pgid
Specifies the PGID.
weight weight
Specifies the DWRR weight which is the percentage of bandwidth. Enter an integer from 1 to 100.
pfc
Specifies the priority flow control setting.
off
Disables priority flow control.
on
Enables priority flow control.
Modes
CEE map configuration mode
Usage Guidelines
Use the no form of the command to reset the default settings for the specified PGID.
When any of the PGID 0 through 7 is activated, a bandwidth percentage must be specified. The bandwidth percentage is the
percentage of the link bandwidth that the Priority Group should receive during periods of link oversubscription after all Strict
Priority Group have been serviced and is used to derive DWRR weight.
Relative priority between Priority Groups is exactly the ordering of entries listed in the table in the Command Default, with PGID
15.0 being highest priority and PGID 15.7 being lowest priority.
Congestion control configuration is partially specified by enabling or disabling PFC because the set of priorities mapped to the
Priority Group is not known. The CEE Priority Table configuration through the priority-table command completes the PFC
configuration.
Examples
The following example configures PGID 0.
History
Release version Command history
priority-table
Maps the priority (CoS) to the CEE priority group.
Syntax
priority-table PGID_CoS0 PGID_CoS1 PGID_CoS2 PGID_CoS3 PGID_CoS4 PGID_CoS5 PGID_CoS6 PGID_CoS7
no priority-table
Command Default
The mapping of all CoS priorities is to priority group (PGID) 2.
Parameters
PGID_CoS0
Specifies the PGID that maps to COS 0.
PGID_CoS1
Specifies the PGID that maps to COS 1.
PGID_CoS2
Specifies the PGID that maps to COS 2.
PGID_CoS3
Specifies the PGID that maps to COS 3.
PGID_CoS4
Specifies the PGID that maps to COS 4.
PGID_CoS5
Specifies the PGID that maps to COS 5.
PGID_CoS6
Specifies the PGID that maps to COS 6.
PGID_CoS7
Specifies the PGID that maps to COS 7.
Modes
CEE-map configuration mode
Usage Guidelines
Use the no form to reset the default setting of PGID 2.
The PFC configuration is completed when the CEE Priority Table defining which CoS maps to a PGID is combined with the
CEE Priority Group Table configuration indicating whether PFC is enabled or disabled for the Priority Group.
Examples
The following example configures the priority-table map.
History
Release version Command history
profile (LLDP)
Creates an LLDP profile.
Syntax
profile name
no profile name
Parameters
name
Assigns a name to the profile. The name must be between 1 and 32 ASCII characters in length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
When you apply an LLDP profile on an interface using the lldp profile command, it overrides the global configuration. If a profile
is not present, then the default global profile is used until you create a valid profile. SLX 9240 supports 128 active profiles and
SLX 9140 supports 72 active profiles.
Examples
The following example creates a profile named test.
History
Release version Command history
profile (telemetry)
Designates telemetry profiles for telemetry collectors.
Syntax
profile enhanced-queue-discard-pkts-profile default_enhanced_queue_discard_pkts_statistics
Command Default
No profile is designated.
Parameters
enhanced-queue-discard-pkts-profile default_enhanced_queue_discard_pkts_statistics
Specifies profile default_enhanced_queue_discard_pkts_statistics of the enhanced-queue-discard-pkts-profile
profile type—for tracking discarded-packet statistics.
event-profile default_event_statistics
Specifies profile default_event_statistics of the event profile type—for tracking event statistics.
interface-profile default_interface_statistics
Specifies profile default_interface_statistics of the interface-profile profile type—for tracking interface statistics.
lldp-profile default_lldp_statistics
Specifies profile default_lldp_statistics of the lldp profile type—for tracking LLDP statistics.
pbr default_pbr_statistics
Specifies profile default_lldp_statistics of the pbr profile type—for tracking policy-based routing (PBR) statistics.
queue-profile default_queue_statistics
Specifies profile default_queue_statistics of the queue-profile profile type—for tracking queue statistics.
system-profile default_system_utilization_statistics
Specifies profile default_system_utilization_statistics of the system-profile profile type—for tracking system
utilization statistics.
Modes
Telemetry-collector configuration mode
Usage Guidelines
You can apply multiple telemetry profiles to a collector.
Examples
The following example assigns two profiles to a collector.
History
Release version Command history
profile ipv6-lookup
Specifies the IPv6 address lookup-mode.
Syntax
profile ipv6-lookup { default | network-id }
Command Default
The default IPv6 address lookup mode is by host ID.
Parameters
default
Resets the IPv6 address lookup-mode to host ID (bits 64–127 of the IPv6 address).
network-id
Changes the IPv6 address lookup-mode to network ID (bits 0–63 of the IPv6 address).
Modes
Hardware configuration mode
Usage Guidelines
ATTENTION
This is a disruptive command. In order for the last update of the profile configuration to take effect on a device, you
must run the copy running-config startup-config command followed by the reload system command.
Each forwarded frame has a token with a 100-byte header buffer for storing header data. Fields copied into this token header-
buffer are available for lookup (to make forwarding decisions). Because of this small buffer size, copying the entire 128-bit SIP
and DIP addresses is not supported. You can configure the IPv6 lookup profile, specifying which half of SIP and DIP addresses
are copied into the buffer:
• (Default) Host ID (bits 64-127)
• Network ID (bits 0-63)
The software does not prevent you from specifying a full 128-bit IPV6 address while configuring an IPv6 ACL. However, only
the half configured in the IPv6 lookup profile is matched.
Before you change lookup-profile, you need to evaluate the impact of the change on current IPv6 ACLs.
Examples
The following example changes the IPv6 lookup-profile from the default host-ID (bits 64-127) mode to network-id (bits 0-63)
mode.
History
Release version Command history
profile overlay-visibility
Configures hardware profile settings related to overlay visibility.
Syntax
profile overlay-visibility { default | endpoint | endpoint-vni| tunnel-vni| vni}
Command Default
Default hardware profile settings are configured.
Parameters
default
Configures a match on outer source IP and destination IP addresses.
endpoint
Configures a match on outer source IP or destination IP addresses.
endpoint-vni
Configures a match on outer source IP address and virtual network identifier (VNI), or destination IP address and VNI.
tunnel-vni
Configures a match on outer source IP address, destination IP address, and VNI.
vni
Configures a match on VNI only.
Modes
Hardware configuration mode
Usage Guidelines
The overlay visibility profile must be set to the appropriate classification method. If the class map rules do not match the
visibility profile that is selected, the classification is not programmed into the hardware when applied within the context of an
overlay transit service.
Use the show hardware profile overlay-visibility command, with the keywords as shown above, to confirm the settings of the
profile overlay-visibility command.
Examples
The following example sets the overlay visibility profile to match on the VNI only.
History
Release version Command history
profile route-table
Optimizes hardware forwarding resources for route tables.
Syntax
profile route-table { default | ipv4-max-arp | ipv6-max-nd | multicast | multicast-snoop | user-defined } [ maximum_paths
{ 8 | 16 | 32 | 64 } ]
Command Default
The default hardware profiles are enabled.
Parameters
default
Optimizes IPv4/IPv6 resources for dual-stack operations.
ipv4-max-arp
Optimizes resources for IPv4 unicast with maximum ARP.
ipv6-max-nd
Optimizes resources for IP unicast and IPV6 routing with maximum ND.
multicast
Optimizes resources for IP unicast dual stack and IPv4 mulitcast.
multicast-snoop
Optimizes resources for IP unicast dual stack and multicast snooping.
user-defined
Optimizes resources for the user-defined profile.
maximum_paths
Specifies 8, 16, 32, or 64 as the maximum number of load-sharing paths.
Modes
Hardware configuration mode
Usage Guidelines
ATTENTION
This is a disruptive command. In order for the last update of the profile configuration to take effect on a device, you
must run the copy running-config startup-config command followed by the reload system command.
This configuration command configures the route-table hardware forwarding resource allocation to optimize the specified
protocol functionality.
The maximum-path variable is optional. If skipped, the maximum-path remains unchanged. This parameter is not supported for
the user-defined subtype.
The detailed layout of user-defined profile is not configured through the CLI interface. Instead, you must lay out the profile
details in an .xml file that will be pre-loaded onto the switch to a pre-defined location and consumed by platform/ASIC modules
as the device boots up.
The device boots up in pre-defined default hardware profile and with no user-defined profile. The default version of user-
defined profile that comes with the release package is present on the device. Follow the suggested procedure to create and
deploy user-defined profile. You can use it as a template to compile your own based on your needs.
Use the copy user-defined-profile file-url command to upload your version of the user-defined profile to the device. The
default user-defined profile that comes with the release package is always available.
The locations for user-defined profile and the default template from the release package are:
• /var/config/profile/user-defined
• /var/config/profile/default-profile
As the device boots up, if the hardware profile is specified to be user-defined, then the software loads the profile from this
location to initialize ASIC resource allocation.
Examples
To optimize route profiles with a maximum of 16 paths for IIPv4 unicast with maximum ARP:
History
Release version Command history
profile tcam
Optimizes hardware resources for ternary content-addressable memory (TCAM) profiles.
Syntax
profile tcam{ default | l2-l3iacl | l2-l3iqos| l3-acl |l3-iacl-l2-eacl | l3-iacl-l2-iqos |l3-iqos-l2-iacl | user-defined }
Command Default
The default hardware profiles are enabled.
Parameters
default
Optimizes resources with basic support for all applications.
l2-l3iacl
Optimizes resources for ingress L2 and ingress IPv4, and IPv6 ACLs. Valid for the SLX 9240.
l2-l3iqos
Optimizes resources for ingress L2, IPv4, and IPv6 QoS. Valid for the SLX 9240.
l3-acl
Optimizes resources for ingress, egress IPv4, and IPv6 ACLs. Valid for the SLX 9240.
l3-iacl-l2-eacl
Optimizes resources for ingress IPv4, IPv6 ACL, and egress L2 ACLs. Valid for the SLX 9240.
l3-iacl-l2-iqos
Optimizes resources for ingress IPv4, IPv6 ACL, and ingress L2 QoS. Valid for the SLX 9240.
l3-iqos-l2-iacl
Optimizes resources for ingress IPv4, IPv6 Qos, and ingress L2 ACLs. Valid for the SLX 9240.
default
Optimizes resources with basic support for all applications.
l2-acl-l3-iacl
Optimizes resources for ingress, egress L2 ACL & ingress IPv4, IPv6 ACL. Valid for the SLX 9140.
l2-iacl-l3-acl
Optimizes resources for ingress L2 ACL & ingress, egress IPv4, IPv6 ACL. Valid for the SLX 9140.
l2-l3-iacl-l2-iqos
Optimizes resources for ingress L2, IPv4, IPv6 ACL & ingress L2 QoS. Valid for the SLX 9140.
l2-l3-iqos-l2-iacl
Optimizes resources for ingress L2, IPv4, IPv6 Qos & ingress L2 ACL. Valid for the SLX 9140.
l2-l3-iqos-l3-iacl
Optimizes resources for ingress L2, IPv4, IPv6 Qos & ingress IPv4, IPv6 ACL. Valid for the SLX 9140.
l2-l3-iqos-l2-eacl
Optimizes resources for ingress L2, IPv4, IPv6 Qos & egress L2 ACL. Valid for the SLX 9140.
l2-l3-iqos-l3-eacl
Optimizes resources for ingress L2, IPv4, IPv6 Qos & egress IPv4, IPv6 ACL. Valid for the SLX 9140.
app-tele-l3-iqos-l2-iacl
Optimizes resources for ingress application telemetry, IPv4, IPv6 QOS & L2 ACL. Valid for the SLX 9140.
app-tele-l3-iqos-l3-iacl
Optimizes resources for ingress application telemetry, IPv4, IPv6 QOS & IPv4, IPv6 ACL. Valid for the SLX 9140.
The profile is as follows.
user-defined
Optimizes resources for user-defined profiles.
Modes
Hardware configuration mode
Usage Guidelines
ATTENTION
This is a disruptive command. In order for the last update of the profile configuration to take effect on a device, you
must run the copy running-config startup-config command followed by the reload system command.
The detailed layout of user-defined profile is not configured through the CLI interface. Instead, you must lay out the profile
details in an .xml file that will be pre-loaded onto the switch to a pre-defined location and consumed by platform/ASIC modules
as the device boots up.
The device boots up in pre-defined default hardware profile and with no user-defined profile. The default version of user-
defined profile that comes with the release package is present on the device. Follow the suggested procedure to create and
deploy user-defined profile. You can use it as a template to compile your own based on your needs.
Use the copy user-defined-profile file-url command to upload your version of the user-defined profile to the device. The
default user-defined profile that comes with the release package is always available.
The locations for user-defined profile and the default template from the release package are:
• /var/config/profile/user-defined
• /var/config/profile/default-profile
As the device boots up, if the hardware profile is specified to be user-defined, then the software loads the profile from this
location to initialize ASIC resource allocation.
Examples
To optimize TCAM resources for multicast:
To optimize TCAM resources for Application Telemetry enables the profile to support IPv4, IPv6 QoS, and Layer 2 ACLs:
protocol
Configures the authentication protocol to use for communication with the Remote Authentication Dial-In User Service (RADIUS)
server.
Syntax
protocol { chap | pap | peap }
no protocol
Command Default
The default protocol is Challenge Handshake Authentication Protocol (CHAP).
Parameters
chap
Specifies using CHAP for communication with the RADIUS server.
pap
Specifies using Password Authentication Protocol (PAP) for communication with the RADIUS server.
peap
Specifies using Protected Extensible Authentication Protocol (PEAP) for communication with the RADIUS server.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to configure PAP as the authentication protocol for communication with the RADIUS server.
History
Release version Command history
protocol lldp
Enters the Link Layer Discovery Protocol (LLDP) configuration mode.
Syntax
protocol lldp
no protocol lldp
Command Default
LLDP protocols are enabled.
Modes
Global configuration mode
Usage Guidelines
Enter no protocol lldp to restore the default settings.
Examples
To enter LLDP mode:
History
Release version Command history
protocol ptp
Enters Precision Time Protocol (PTP) configuration mode.
Syntax
protocol ptp
no protocol ptp
Command Default
PTP is disabled.
Modes
Global configuration mode
Usage Guidelines
In PTP configuration mode, the user can enable or disable PTP, specify clock-quality parameters used by the the Best Master
Clock Algorithm (BMCA), and specify the transmission frequency of messages used to update the PTP clock.
This command is not allowed on interfaces that are part of a port channel.
The no form of this command at the switch (global) level deletes PTP configurations and reverts to the default (factory shipped)
configuration. Interface-level configurations are not affected.
The no form of this command at the interface level removes PTP configurations from the interface.
Examples
To enter PTP configuration mode at the switch level:
To disable PTP at the switch level and set all parameters previously entered under this mode to the default:
To disable PTP configuration mode at the interface level and set all parameters previously entered under this mode to the
default:
History
Release version Command history
protocol spanning-tree
Designates the context for spanning tree.
Syntax
protocol spanning-tree { mstp | rstp | stp | pvst | rpvst }
no protocol spanning-tree
Command Default
STP is not enabled. STP is not required in a loop-free topology.
Parameters
mstp
Specifies the Multiple Spanning Tree Protocol (MSTP).
rstp
Specifies the Rapid Spanning Tree (RSTP).
stp
Specifies the Spanning Tree Protocol (STP).
pvst
Specifies Per-VLAN Spanning Tree Protocol Plus (PVST+).
rpvst
Specifies Rapid Per-VLAN Spanning Tree Protocol Plus (R-PVST+).
Modes
Global configuration mode
Usage Guidelines
Consider enabling STP to detect or avoid loops. You must turn off one form of STP before turning on another form.
Packet drops or packet flooding may occur if you do not enable xSTP on all devices connected on both sides of parallel links.
Enter no protocol spanning-tree to delete the context and all the configurations defined within the context or protocol for the
interface.
Examples
To enable the Spanning Tree Protocol:
History
Release version Command history
protocol vrrp
Globally enables Virtual Router Redundancy Protocol (VRRP).
Syntax
protocol vrrp
no protocol vrrp
Command Default
VRRP is not enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of this command globally disables VRRP.
Examples
To enable VRRP:
History
Release version Command history
protocol vrrp-extended
Globally enables VRRP-Extended.
Syntax
protocol vrrp-extended
no protocol vrrp-extended
Command Default
Disabled
Modes
Global configuration mode
Usage Guidelines
The no protocol vrrp-extended command globally disables VRRP-E.
Examples
To enable VRRP-Extended:
History
Release version Command history
ptp-vlan
Configures the VLAN used to transmit Precision Time Protocol (PTP) frames on a switch port.
Syntax
ptp-vlan vlan-id
no ptp-vlan
Command Default
See the Usage Guidelines.
Parameters
vlan-id
A valid VLAN ID.
Modes
PTP configuration mode
Usage Guidelines
If a VLAN is not specified, the default VLAN is the access VLAN on an access port, and the native VLAN on a trunk port.
If the VLAN specified is not one of the configured VLANs on the switch port, PTP frames are not sent.
If the STP state for the specified VLAN is blocked, PTP frames are not sent.
Examples
To configure PTP VLAN 100 on a trunk port:
History
Release version Command history
pw-profile
Creates a pseudowire (PW) profile that can be shared across multiple Virtual Private LAN Services (VPLS) bridge domains.
Syntax
pw-profile [pw-profile-name [ mtu mtu-value ] [ mtu-enforce { false | true } ] [ vc-mode { raw | raw-passthrough | tag } ]
Command Default
No PW profile is configured.
Parameters
pw-profile-name
Specifies the name of a PW profile.
mtu mtu-value
Specifies the maximum transmission unit (MTU) for the PW profile. The range is from 64 through 15966.
mtu-enforce
Configures MTU enforcement check during PW signaling.
false
Enables the MTU enforcement check.
true
Disables the MTU enforcement check.
vc-mode
Configures the virtual connection (VC) mode for the profile:
raw
Specifies using raw mode. At VC label imposition, when a tagged packet is received on a tagged AC
endpoint, the VLAN tag is removed before it is sent out on the wire. When an untagged packet is received on
an untagged AC endpoint it is encapsulated as is and sent out on the wire.
raw-passthrough
Specifies using raw-passthrough mode which enables interoperation with third-party devices. When all
endpoints are configured as tagged endpoints, raw passthrough mode behaves the same way as tagged
mode. When all endpoints are configured as untagged endpoints, raw-passthrough mode behaves the same
way as raw mode. Select the raw-passthrough option, when all endpoints are configured as untagged
endpoints (even when peer devices signal the PW VC mode as raw).
tag
Specifies using tag mode. At VC label imposition, when a tagged packet is received on a tagged AC endpoint,
the packet is encapsulated as is and sent out on the wire. When an untagged packet is received on an
untagged AC endpoint, a dummy tag is added and it is sent out on the wire.
Modes
Global configuration mode.
Usage Guidelines
You can configure up to 64 PW profiles.
Examples
The following example shows how to create a PW profile named test specifying that the VC mode for the profile is raw-
passthrough.
History
Release version Command history
python
Launches an interactive Python shell, with an option to launch a Python script.
Syntax
python [ python-statement | python-script-filename ] [ script-arguments ]
Parameters
python-statement
Must be a valid python interpreter argument.
python-script-filename
Runs a Python script file. Valid values range from 4 through 32 characters (including the .py extension). The first
character must be alphabetic.
script-arguments
Passes one or more arguments defined in the script.
Modes
Privileged EXEC mode
Usage Guidelines
This command is available only to users with admin-level permissions.
Entering python python-statement launches an interactive Python shell and runs a valid python-statement that you enter. For
example, entering python -h invokes the Python shell and displays Python options and arguments.
Entering python python-script-filename launches an interactive Python shell and runs the Python file. (To make a Python file
available to this command, copy the Python file to the flash:// location on the device, using the copy command.)
Note the following divergence between SLX-OS CLI syntax and Python syntax:
• Although in general, SLX-OS CLI syntax is not case-sensitive, Extreme convention is to use lower-case.
• Python syntax is case sensitive.
To exit the Python environment and return to the SLX-OS CLI, enter either:
• exit()
• Ctrl-D
Examples
The following example launches the Python shell and then both assigns an SLX CLI operational command to a Python variable
and runs that command.
device# python
Python 3.3.2 (default, Apr 11 2014, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_show_users = CLI('show users')
!Command: show users
!Time: Tue Aug 9 09:09:39 2016
**USER SESSIONS**
Username Role Host IP Device Time Logged In
jdoe admin 10.11.12.13 Cli 2016-08-09 09:06:46
admin admin 127.1.0.1 Cli 18640
**LOCKED USERS**
Username
no locked users
>>>
The following example (partial) launches the Python shell to run a Python script-file.
NOTE
For an annotated text of this script, refer to the Extreme SLX-OS Management Configuration Guide under "Python
Event-Management and Scripting" and "Python scripts and run-logs."
vlan 1
!
vlan dot1q tag native
!Command: config
vlan 101-105
!Time: Mon Aug 22 18:33:03 2016
vlan 1
!
vlan 101
!
vlan 102
!
vlan 103
!
vlan 104
!
vlan 105
!
vlan dot1q tag native
interface Port-channel 1
description Insight port-channel on MM1
shutdown
!
interface Port-channel 2
description Insight port-channel on MM2
shutdown
!
!Command: config
int po 10
switchport
switchport mode trunk
switchport trunk allowed vlan add 101-105
switchport trunk tag native-vlan ; no shut
!Time: Mon Aug 22 18:33:03 2016
interface Port-channel 1
description Insight port-channel on MM1
shutdown
!
interface Port-channel 2
description Insight port-channel on MM2
shutdown
!
interface Port-channel 10
switchport
switchport mode trunk
switchport trunk allowed vlan add 101-105
!Command: config
int eth 0/4
channel-group 10 mode active type standard
no shut
!Time: Mon Aug 22 18:33:04 2016
!Command: config
int eth 0/5
channel-group 10 mode active type standard
no shut
!Time: Mon Aug 22 18:33:04 2016
<output truncated>
The following example launches the Python shell to test an event-handler script-file.
NOTE
For more information, refer to the "Python Event-Management and Scripting" > "Guidelines for writing Python scripts"
topic in the Extreme SLX-OS Management Configuration Guide.
History
Release version Command history
qos cos
Changes the interface default Class of Service (CoS) value.
Syntax
qos cos cos_value
Command Default
The default is 0.
Parameters
value
Specifies the CoS value. Enter an integer from 0 through 6.
Modes
Interface subtype configuration mode
Usage Guidelines
When Interface ingress QoS Trust is in the un-trusted mode, then the Interface Default CoS value is applied to all ingress traffic
for user priority mapping. When the interface ingress QoS Trust is in the CoS mode, then the Interface Default CoS value is
applied to all nonpriority tagged ingress traffic for user priority mapping.
If the interface is QoS trusted, the CoS value of the interface is used to assign a CoS value to all untagged packets entering the
interface.
QoS Trust is implicitly turned on when the QoS CoS-Mutation map is applied to interfaces, and is implicitly turned off when the
QoS CoS-Mutation map is removed.
Examples
To set the CoS value to 2 on a specific Ethernet interface:
History
Release version Command history
qos cos-mutation
Applies a user configured QoS CoS-to-CoS mutation map to an interface.
Syntax
qos cos-mutation cos_map_name
Parameters
cos_map_name
The name of the CoS mutation map.
Modes
Interface configuration mode
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress, mutation mapping occurs
before traffic classification and all other actions.
Examples
Follow this example to apply a QoS CoS-to-CoS mutation map to a specific Ethernet interface:
History
Release version Command history
qos cos-traffic-class
Applies a Quality of Service (QoS) CoS-to-traffic class mutation map on an interface.
Syntax
qos cos-traffic-class cos_map_name
Command Default
No explicit QoS CoS-to-traffic class mutation map is applied; the inbound CoS equals the outbound CoS.
Parameters
cos_tc_map_name
The name of the CoS-to-traffic class mutation map.
Modes
Interface configuration mode.
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress, mutation mapping occurs
before traffic classification and all other actions.
Examples
To activate a QoS CoS-to-traffic class mutation map named cosMutMap on a specific Ethernet interface:
To activate a QoS CoS-to-traffic class mutation map from a specific port channel interface:
History
Release version Command history
qos cpu
Accesses Quality of Service (QoS) central processing unit (CPU) configuration mode to configure the frame rate on the CPU
queues mapped to the protocols for the device.
Syntax
qos cpu
no qos cpu
Modes
Global configuration mode
Usage Guidelines
The no form of the command resets the default frame rate for all CPU queues.
Examples
The following example accesses QoS CPU configuration mode.
History
Release version Command history
Syntax
qos drop-monitor enable
Command Default
QoS drop monitoring is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
The drop-polling interval is 60 seconds. If drops occur during this interval, a RASlog message is generated.
Examples
The following example enables RASlog drop monitioring for ingress port drops and egress queue drops.
History
Release version Command history
qos dscp-cos
Applies a user configured QoS DSCP-to-CoS mutation map to an interface.
Syntax
qos dscp-cos dscp_cos_map_name
Command Default
No explicit QoS DSCP-to-CoS mutation map is applied.
Parameters
dscp_cos_map_name
Name of DSCP-to-COS mutation map
Modes
Interface subtype configuration mode
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress, mutation mapping occurs
before traffic classification and all other actions.
The dscp-cos map needs to applied on the ingress interface. It is effective only when the dscp-traffic-class and dscp-mutation
maps are also applied to same interface.
Examples
Follow this example to apply a user configured QoS DSCP-to-COS mutation map named dscpMap to a specific Ethernet
interface.
Follow this example to apply a user configured QoS DSCP-to-COS mutation map named dscpMap to a specific port channel
interface.
History
Release version Command history
qos dscp-mutation
Applies a configured QoS DSCP mutation map to an interface.
Syntax
qos dscp-mutation dscp_map_name
Command Default
No explicit user configured QoS DSCP-to-DSCP mutation map is applied; the inbound DSCP equals the outbound DSCP.
Parameters
dscp_map_name
The name of the DSCP mutation map
Modes
Interface subtype configuration mode
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress, mutation mapping occurs
before traffic classification and all other actions.
The dscp-mutation map needs to applied on the ingress interface. It is effective only when the dscp-cos and dscp-traffic-class
maps are also applied to same interface.
Examples
Follow this example to apply a QoS DSCP-to-DSCP mutation map to a specific Ethernet interface:
History
Release version Command history
qos dscp-traffic-class
Applies a user configured QoS DSCP-to-traffic- class mutation map to an interface.
Syntax
qos dscp-traffic-class dscp_tc_name
Command Default
No explicit user configured QoS DSCP-to-traffic class map is enabled on the interface.
Parameters
dscp_tc_name
Name of DSCP-to-traffic class map
Modes
Interface configuration mode
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress, mutation mapping occurs
before traffic classification and all other actions.
The dscp-traffic-class map needs to applied on the ingress interface. It is effective only when the dscp-cos and dscp-mutation
maps are also applied to same interface.
Examples
Follow this example to apply a QoS DSCP-to-traffic class mutation map to a specific Ethernet interface
Follow this example to apply a QoS DSCP-to-traffic class mutation map to a specific port channel interface
History
Release version Command history
qos flowcontrol
Activates and configures QoS flow control.
Syntax
qos flowcontrol tx { on | off } rx { on | off }
no qos flowcontrol
Command Default
By default, QoS flow control is disabled for both directions.
Parameters
tx { on | off }
Activates or deactivates the transmission portion of flow control.
rx { on | off }
Activates or deactivates the receiving portion of flow control.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no qos flowcontrol to deactivate flow control on a specific interface.
When a receiving device is congested, it communicates with the transmitting device by sending a PAUSE frame that instructs
the device to stop data transmission for a specified period of time. This feature is available per port in all front ports and applies
to all the traffic on the link. However, the SLX-OS devices support the receive direction only. These devices supports pause flow
control and priority flow control.
Examples
The following example activates both the transmitting and receiving portions of flow control on the Ethernet interface:
History
Release version Command history
Syntax
qos map cos-dcsp name
Parameters
name
Specifies the name of CoS-to-DSCP map.
Modes
Global configuration mode
Usage Guidelines
This map can be used in a remarking profile only. It cannot be applied directly to an interface.
Examples
The following example creates a QoS CoS-to-DSCP map.
History
Release version Command history
Syntax
qos map cos-mutation name
Parameters
name
Specifies a unique name across all CoS-to-CoS mutation QoS maps defined within the system. If the named CoS-to-
CoS mutation QoS map does not exist, then it is created. If the named CoS-to-CoS mutation QoS map already exists,
then it is updated and new mapping is automatically propagated to all interfaces bound to the QoS map.
Modes
Global configuration mode
Usage Guidelines
Use the no of this command to delete the QoS CoS-to-CoS mutation map.
Both cos-mutation and cos-traffic class maps must be applied on a port, otherwise the map configuration is not active. If you
want to have a user-defined cos-mutation configuration and default cos-traffic class configuration on a port, you must explicitly
apply the default cos-traffic class map on a port, otherwise the cos-mutation configuration is not active.
Examples
The following example creates a CoS-to-CoS QoS mutation map.
History
Release version Command history
Syntax
qos map cos-traffic-class name
Command Default
If CoS-to-traffic class mutation map is not defined, the default CoS-to-traffic class map is used, which is a one-to-one map for
each priority.
Parameters
name
Specifies a unique name for the CoS-to-traffic class mutation QoS map. If the named map does not exist, then it is
created. If the map already exists, then it is updated and new mapping is automatically propagated to all interfaces
bound to the map.
Modes
Global configuration mode
Usage Guidelines
A CoS-to-traffic class mutation map takes an inbound CoS value and maps it to an outbound traffic class (priority queue) value.
The inbound CoS value is the user priority after any interface ingress QoS trust and Interface default CoS policy have been
applied.
Both cos-mutation and cos-traffic class maps must be applied on a port, otherwise the map configuration is not active. If you
want to have a user-defined cos-mutation configuration and default cos-traffic class configuration on a port, you must explicitly
apply the default cos-traffic class map on a port, otherwise the cos-mutation configuration is not active.
Enter no form of the command to delete the named QoS CoS-to-traffic class mutation map.
Examples
To create a QoS CoS-to-traffic class mutation map use the following command
To delete a QoS CoS-to-traffic class mutation map that is bound to an interface follow this example.
History
Release version Command history
Syntax
qos map dscp-cos name
Parameters
name
Name of DSCP-to-CoS map
Modes
Global configuration mode
Usage Guidelines
This command remaps the incoming DSCP values of the ingress packet to egress CoS 802.1P values.
All DSCP map types must be applied on a port, otherwise the map configuration is not active. If you want to have default
configuration on a port for one of the Layer 3 maps, you must explicitly apply the default configuration of the Layer 3 map type.
Examples
The following example creates a QoS DSCP-to-CoS map.
History
Release version Command history
Syntax
qos map dscp-mutation name
Parameters
name
Specifies the name of the DSCP mutation map.
Modes
Global configuration mode
Usage Guidelines
After you create the DSCP mutation map, you can map ingress DSCP values to egress DSCP values using the map dscp
command.
All DSCP map types must be applied on a port, otherwise the map configuration is not active. If you want to have default
configuration on a port for one of the Layer 3 maps, you must explicitly apply the default configuration of the Layer 3 map type.
Examples
The following example creates a QoS DSCP mutation map.
History
Release version Command history
Syntax
qos map dscp-traffic-class name
Command Default
DSCP-to-traffic class mutation is not enabled.
Parameters
name
Name of the QoS DSCP-to-traffic class map.
Modes
Global configuration mode
Usage Guidelines
After you configure the QoS DSCP-to-Traffic-Class map, you can map the ingress DSCP values to a traffic class value using
the map command.
All DSCP map types must be applied on a port, otherwise the map configuration is not active. If you want to have default
configuration on a port for one of the Layer 3 maps, you must explicitly apply the default configuration of the Layer 3 map type.
Enter no qos dscp-traffic-class name while in the interface mode to remove the map from that interface.
Examples
The following example creates a QoS DSCP-to-traffic class map.
History
Release version Command history
Syntax
qos map traffic-class-cos name
Command Default
If a QoS traffic class-to-CoS mutation map is not defined, the default traffic class-to-CoS map is used, which is a one-to-one
map for each priority.
Parameters
name
Specifies a unique name for the QoS traffic class-to-CoS mutation map.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to delete the map.
This map can only be used in a remark profile and cannot be applied on interface.
Examples
The following example creates a QoS traffic class-to-CoS mutation map.
History
Release version Command history
Syntax
qos map traffic-class-dscp name
Parameters
name
Specifies the name of the QoS traffic-class-to-DSCP map.
Modes
Global configuration mode
Usage Guidelines
After you configure the QoS traffic-class-to-DSCP map, you can map the ingress traffic class values to a DSCP value using the
map traffic-class command.
This map can be used in a remarking profile only. It cannot be applied directly to an interface.
Examples
The following example creates a QoS traffic-class-to-DSCP map.
History
Release version Command history
Syntax
qos map traffic-class-mutation name
Parameters
name
Specifies the name of the traffic-class mutation map.
Modes
Global configuration mode
Usage Guidelines
After you create the traffic-class mutation map, you can map ingress traffic-class values to egress traffic-class values using the
map traffic-class command.
This map can only be used in a remark profile and cannot be applied on interface.
Examples
The following example creates a QoS traffic-class mutation map.
History
Release version Command history
Syntax
qos random-detect traffic-class value red-profile-id profile-ID value
Command Default
Port CoS priority value is not mapped to the RED profile.
Parameters
value
Class of Service (COS) value. Valid values range from 0 through 7.
profile-ID value
Random Error Detection value. Valid values range from 1 through 384.
Modes
Interface subtype configuration mode
Usage Guidelines
The RED profile is defined by the qos red-profile command.
Enter no qos random-detect traffic-class value while in the interface mode to remove the DSCP-to-Traffic-Class map from the
interface.
Examples
The following example maps the profile to CoS priority 7 on a Ethernet interface:
The following example removes the previously created profile from the interface:
History
Release version Command history
Syntax
qos red-profile profile-ID min-threshold percentage max-threshold percentage drop-probability percentage
Parameters
profile-ID
Specifies the profile ID. Enter an integer from 1 through 384.
min-threshold percentage
Specifies the minimum threshold in percentage of queue size for randomly dropping packets. Enter an integer from 0
through 100.
max-threshold percentage
Specifies the maximum threshold in percentage of queue size when packets are dropped with 100% probability. Enter
an integer from 0 through 100.
drop-probability percentage
Specifies the probability in percentage that packets will be dropped when minimum threshold is reached. Enter an
integer from 0 through 100.
Modes
Global configuration mode
Usage Guidelines
Enter qos random-detect cos command while in configuration mode for a specific interface to map the profile to a CoS priority
for a port.
Enter no qos random-detect cos command in the interface mode to remove the profile from the interface. You must remove
the profile from interface before you can remove the profile itself.
Examples
The following example creates a RED profile.
History
Release version Command history
qos service-policy
Applies a policy map to all inbound traffic.
Syntax
qos service-policy in service_policy_name
Parameters
in
Applies the service policy to inbound traffic.
service_policy_name
The name of the policy map.
Modes
Global configuration mode.
Usage Guidelines
The policy map has been preconfigured.
Examples
This example binds a service policy to inbound traffic at the system level.
History
Release version Command history
qos trust
Configures QoS CoS or DSCP trust on an interface.
Syntax
qos trust { cos | dscp }
Command Default
Both CoS and DSCP trust are disabled on the interface.
Parameters
cos
Enables CoS trust on the interface to honor the incoming CoS value of the ingress packet.
dscp
Enables DSCP trust on the interface to honor the incoming IP DSCP settings for deciding the queue priority value of
the ingress packet.
Modes
Interface type configuration mode
Usage Guidelines
Use the no form of this command to disable CoS or DSCP trust on the interface.
When DSCP trust is not enabled, the DSCP value in the packet is ignored.
When Layer 2 maps are active on an interface, CoS on this interface is trusted implicitly.
Examples
The following example enables CoS trust on an interface.
History
Release version Command history
Syntax
qos tx-queue limit queue-limit
Command Default
The default limit is 512 Kbytes.
Parameters
queue-limit
Specifies the egress queue limit in Kbytes. Enter an integer from 128 to 8000.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to reset the default limit of 512 Kbytes.
The size of the shared buffer pool on the ExtremeSwitching SLX 9140 is 14,615 pages and the ExtremeSwitching SLX 9240
is 37,143 pages, where each page is a size of 256 bytes.
When setting the TX-queue limit, the queue limit is set to one of the following values (the next higher value above the configured
value). For example, if you configure the value to 512 Kbytes, the queue limit is set to 748288 bytes on the SLX 9140 or
570368 bytes on the SLX 9240.
Examples
The following example limits the buffer usage for egress lossy unicast queues to 256 Kbytes.
History
Release version Command history
Syntax
qos tx-queue scheduler strict-priority traffic_class dwrr dwrr_weight
Command Default
The SP value for the egress queue traffic class scheduler is not configured.
Parameters
traffic_class
There are eight traffic class values:
0
No strict priority queue.
1
Traffic class 7 strict priority queue.
2
Traffic class 6 through 7 strict priority queues.
3
Traffic class 5 through 7 strict priority queues.
4
Traffic class 4 through 7 strict priority queues.
5
Traffic class 3 through 7 strict priority queues.
6
Traffic class 2 through 7 strict priority queues.
7
Traffic class 1 through 7 strict priority queues.
dwrr dwrr_weight
Configure the DWRR queue weights. There are eight entries for this parameter with each entry representing a
percentage. Tthe total of all the entries cannot exceed 100%. Each entry position represents a specific traffic class:
1
Traffic class 0 DWRR weight.
2
Traffic class 1 DWRR weight.
3
Traffic class 2 DWRR weight.
4
Traffic class 3 DWRR weight.
5
Traffic class 4 DWRR weight.
6
Traffic class 5 DWRR weight.
7
Traffic class 6 DWRR weight.
8
Traffic class 7 DWRR weight.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to remove the SP value for the egress queue traffic class scheduler.
Examples
The following example assigns traffic classes 6 through 7 to a SP queue and assign DWRR weights.
History
Release version Command history
queue
Selects the CPU queue and accesses Quality of Service (QoS) central processing unit (CPU) queue configuration mode to
configure the queue rate.
Syntax
queue queue-number
no queue
Parameters
queue-number
Specifies the number of the queue. The number of queues is dependent on the device. For the SLX 9140 or SLX
9240 device, enter an integer from 0 through 31.
Modes
QoS CPU configuration mode
Usage Guidelines
Use the show qos cpu queue info command to display the mapping of all CPU queues to the protocols.
The no form of the command removes the queue from the QoS CPU configuration and resets the queue to its default frame
rate value.
Examples
The following example selects queue 2 and accesses QoS CPU queue configuration mode for its rate configuration.
History
Release version Command history
Syntax
radius-server host { ip-address | host_name } [ use-vrf [ vrf-name ] ]
Command Default
A RADIUS server is not configured.
Parameters
ip-address
Specifies the RADIUS server host in IP address format. Both IPv4 or IPv6 address formats are supported.
host_name
Specifies the RADIUS server host in hostname format. A hostname can be up to 40 characters in length.
use-vrf
(Optional) Specifies using a specific VRF for communication with the RADIUS server and enters configuration mode
for the RADIUS server host VRF.
vrf-name
(Optional) Specifies a VRF. By default and when a VRF is not specified, the management VRF (mgmt-vrf) is
used for communication with the RADIUS server.
Modes
Global configuration mode
Usage Guidelines
When a RADIUS server with the specified IP address or hostname does not exist, it is added to the server list. When the
RADIUS server already exists, this command modifies the configuration.
NOTE
When only one RADIUS is configured, you can remove the RADIUS server configuration only when both login (EXEC)
and command accounting are disabled.
Examples
The following example shows how to configure a RADIUS server on a device. The IP address of the RADIUS server is
10.24.65.6.
The following example shows how to configure a RADIUS server (with an IP address 10.24.65.6) and specify using the green-
vrf for communication with this server. Specifying the use-vrf option enters configuration mode for the RADIUS server host
VRF.
History
Release version Command history
rate-limit
Sets the rate limit for the central processing unit (CPU) queue.
Syntax
rate-limit fps
no rate-limit
Command Default
The default value is dependent on the CPU queue. Refer to the table in the Usage Guidelines.
Parameters
fps
Specifies the rate as frames per second (FPS). Enter an integer from 0 through 10000.
Modes
QoS CPU queue configuration mode
Usage Guidelines
Use the show qos cpu queue info command to view the frames per second for each queue and the mapping of the queue to
the protocol.
If you enter a frame rate that exceeds the unused credits displayed by the show qos cpu queue info command, an error
message is displayed. You must reduce the rate for another queue to increase the available unused credits.
Some protocol CPU queues have a maximum rate, as listed in the following table.
Use the no form of the command to reset the default rate limit for the queue.
Examples
The following example configures the rate limit for the specified CPU queue.
History
Release version Command history
rd (EVPN VLAN/BD)
Configures a Virtual Private Network (VPN) route distinguisher for a VLAN/bridge domain (BD) in an Ethernet VPN (EVPN)
default instance.
Syntax
rd { admin-value:arbitrary-value | IP-address:arbitrary-value }
Parameters
admin-value
The administrative number assigned to the route. This can be a local ASN number or an IP address. The ASN number
can be either a 2-byte number (from 0 through 65535) or a 4-byte number (from 0 through 4294967295).
arbitrary-value
An arbitrary number you choose. The range of valid values is from 0 through 65535 if the ASN is is an IP address or
a 2 byte ASN. The range is 0 through 4294967295 if the ASN is a 4 byte ASN.
IP-address
An IPv4 or IPv6 address.
Modes
EVPN instance configuration mode
Usage Guidelines
Examples
The following example configures an RD and assigns the local ASN number 200:1.
History
Release version Command history
redistribute
Configures the device to redistribute IPv4 and IPv6 routes from one routing domain to another.
Syntax
redistribute ospf [ match { external1 | external2 | internal } | metric num | metric-type { type1 | type2 } | route-map string ]
no redistribute ospf [ match { external1 | external2 | internal } | metric num | metric-type { type1 | type2 } | route-map string ]
Command Default
The device does not redistribute routing information.
Parameters
match
Specifies the type of route.
external1
Specifies OSPF Type 1 external routes.
external2
Specifies OSPF Type 2 external routes.
internal
Specifies OSPF internal routes.
metric num
Specifies a metric for redistributed routes. Range is from 1 through 65535 in OSPFv2 and OSPFv3 configuration
mode. Range is from 1 through 4261412863 in BGP address-family IPv4/IPv6 unicast configuration mode.
metric-type
Specifies the external link type associated with the default route advertised into the OSPF routing domain.
type1
Specifies a type 1 external route.
type2
Specifies a type 2 external route.
route-map string
Specifies a route map to be consulted before a route is added to the routing table.
ospf
Specifies the OSPF protocol.
source-protocol
Specifies the source protocol from which routes are being redistributed. It can be one of the following keywords: bgp,
connected, or static.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Routes can be filtered by means of an associated route map before they are distributed.
The metric-type { type1 | type2 } option is only available in OSPFv3 router and OSPFv3 router VRF configuration mode.
The match, metric, and metric-type options are not available in OSPF VRF configuration mode.
The default-metric command does not apply to the redistribution of directly connected routes. Use a route map to change the
default metric for directly connected routes.
Examples
The following example redistributes OSPF external type 1 routes with a metric of 200 in BGP address-family IPv4 unicast
configuration mode.
The following example redistributes OSPFv3 external type 2 routes in BGP address-family IPv6 unicast configuration mode.
The following example redistributes static routes into BGP4 and specifies a metric of 200.
The following example redistributes BGP routes and specifies that route-map "rm7" be consulted in OSPF VRF configuration
mode.
The following example redistributes OSPF routes and specifies a type1 external route in OSPFv3 VRF configuration mode.
History
Release version Command history
region
Assigns a name to a Multiple Spanning Tree Protocol (MSTP) region.
Syntax
region region-name
no region
Parameters
region-name
Assigns a name to an MSTP region.
Modes
Spanning tree MSTP configuration mode
Usage Guidelines
The region-name string must be between 1 and 32 ASCII characters in length, and is case-sensitive.
Examples
To assign a name to an MSTP region named region-1:
History
Release version Command history
reload
Reboots the standby or chassis or triggers a power-cycle of the switch and automatically reboot the switch into offline
diagnostic mode.
Syntax
reload { diag-mode | system }
Parameters
diag-mode
Power-cycle the switch and automatically reboot the switch into offline diagnostic mode.
system
Reboots the chassis.
Modes
Privileged EXEC mode
Usage Guidelines
The diagnostic functionalities are provided in offline diagnostic mode by DiagOS. The offline diagnostic utility, DiagOS, runs in a
separate mode and context from SLX-OS. To enter offline diagnostic mode from the SLX-OS command prompt, enter the
reload diag-mode command in privileged EXEC mode.
After the reload diag-mode command is executed, the offline diagnostic mode is preserved persistently on the switch for the
subsequent reboots and power-cycles. To exit offline diagnostic mode and return to SLX-OS mode, enter the reload slxos-
mode command from the offline diagnostic prompt as follows:
All reboot operations are disruptive, and the commands prompt for confirmation before executing. When you reboot a device, all
traffic to and from it stops. All ports on that device remain inactive until the device comes back online.
The reload system command performs a cold reboot that powers off and restarts the entire chassis. All session connections
must be restarted. If the power-on self-test (POST) is enabled, POST is executed when the system comes back up.
NOTE
Do not use the reload command without either the diag-mode or system parameter.
Examples
The following example performs a cold reboot of the device.
The following example power-cycles the switch and automatically reboots the switch into offline diagnostic mode.
Are you sure you want to proceed to reboot the switch [y/n]? y
History
Release version Command history
reload (DiagOS)
Triggers a power cycle of the switch.
Syntax
reload [ diag | slxos-mode ]
Command Default
The default without an option is reload, which has the same effect as reload diag.
Parameters
diag
Power-cycles the switch and reboots back to offline diagnostics mode.
slxos-mode
Power-cycles the switch and reboots to SLX-OS mode.
Modes
Offline diagnostic mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
Use the reload slxos-mode command to power cycle the switch and return to SLX-OS mode once the offline diagnostic testing
is completed. Otherwise, use reload diag command to power cycle the switch after each test. Power cycling is required to clean
up the system before the next test case can be run.
ATTENTION
Wait for the system to reload automatically, as this process can take some time to complete.
Examples
The following example power cycles the system and re-enters SLX-OS mode.
History
Release version Command history
remap lossless-priority
Configures the Class of Service (CoS) to be remapped for the lossless priority.
Syntax
remap lossless-priority priority CoS-value
Command Default
The default CoS value is 0.
Parameters
priority CoS-value
Specifies the CoS value. Enter an integer from 0 to 6.
Modes
CEE map configuration mode
Usage Guidelines
Use the no form for this command to reset the default CoS value of 0.
Examples
The following example configure the lossless priority to 2.
History
Release version Command history
remove destination
Removes one or more destinations from a policy-based forwarding (PBF) destination-group.
Syntax
remove destination destination-id
Command Default
Destinations that were added are contained in the PBF destination group.
Parameters
destination-id
Specifies one or more PBF destination IDs. You can specify one ID, a range (example: 3-5), a comma-separated list
(example: 1,3,5,6), or combine IDs, ranges, and lists (example: 1-5,6,8).
Modes
PBF destination-group configuration mode
Usage Guidelines
To remove all destinations from a PBF destination-group, you can also use the no add destination command.
Examples
The following example add a range of destinations to a PBF destination-group and then removes specific destinations.
History
Release version Command history
rename
Renames a file in the device flash memory.
Syntax
rename current_name new_name
Parameters
current_name
Specifies the file name you want to change.
new_name
Specifies the new file name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
System configuration files cannot be renamed. If you try to rename a system file, a warning message is displayed.
Examples
The following example renames a file in the flash memory.
History
Release version Command history
resequence access-list
Reassigns sequence numbers to entries of an existing MAC, IPv4, or IPv6 access list.
Syntax
resequence access-list { ip | ipv6 | mac } name seq_num increment
Parameters
ip | ipv6 | mac
Specifies the Layer 2 or Layer 3 ACL bound to an interface.
name
Specifies the name of a standard or an extended ACL. A maximum of 63 characters is allowed.
seq_num
Specifies the starting sequence number in the ACL. Valid values range from 1 through 4294967290.
increment
Specifies a value to increment the sequence number between rules. Valid values range from 1 through 4294967290.
Modes
Privileged EXEC mode
Usage Guidelines
Reordering the sequence numbers is useful when you need to insert rules into an existing ACL and there are not enough
sequence numbers available. When all sequence numbers between rules are exhausted, this feature allows the reassigning of
new sequence numbers to entries of an existing access list.
Examples
The following example reorders the rules in a MAC ACL.
Syntax
resource-monitor cpu enable [ action { raslog | streaming | both } ] [ threshold percentage ]
Command Default
Default action is to set to generate RASlog messages when CPU usage exceeds the threshold of 90%.
Parameters
action { raslog | streaming | both }
Action to take when CPU usage exceeds threshold. Valid output options are RASlog, streaming, or both.
threshold percentage
Threshold for high CPU usage. The range of valid values is from 70 through 90 percent.
Modes
Configuration mode
Usage Guidelines
This is a node-specific command.
The no form of the command disables the CPU utilization monitoring.
Examples
The following example disables the CPU utilization monitoring service.
The following example re-enables the CPU utilization monitoring service if it has been disabled.
History
Release version Command history
Syntax
resource-monitor memory enable [ action { raslog | streaming | both } ] [ threshold percentage ]
Command Default
Default action is to set to generate RASlog messages when memory usage exceeds the threshold of 90%.
Parameters
action { raslog | streaming | both }
Action to take when memory usage exceeds threshold. Valid output options are RASlog, streaming, or both.
threshold percentage
Threshold for high memory usage. The range of valid values is from 70 through 90 percent.
Modes
Configuration mode
Usage Guidelines
This is a node-specific command.
The no form of the command disables the memory utilization monitoring.
Examples
The following example disables the memory utilization monitoring service.
The following example re-enables the memory utilization monitoring service if it has been disabled.
History
Release version Command history
Syntax
resource-monitor process memory alarm alarm_threshold [ critical critical_threshold ] [ enable ]
Command Default
This command is enabled by default.
Parameters
alarm alarm_threshold
Specifies the alarm threshold, crossing which, specific RASlog is generated. Valid values range between 500 to 599
MB. The default is 500.
enable
Enables the pre-process memory monitoring service.
critical critical_threshold
Specifies the critical threshold, crossing which, specific RASlog is generated. Valid values range between 600 to 699
MB. The default is 600.
Modes
Global configuration mode
Usage Guidelines
This is a node-specific command. When the alarm threshold is reached, it generates the RASlog message SRM-1003. When
the critical threshold is reached, it generates the RASlog message SRM-1004.
The no form of the command disables the pre-process memory monitoring on CPU.
Examples
The following example enables the pre-process memory monitoring service and sets an alarm threshold of 550 MB and a
critical threshold of 620 MB.
History
Release version Command history
Syntax
retain route-target all
Command Default
This functionality is disabled.
Modes
Address-family L2VPN EVPN configuration mode
Usage Guidelines
Use the no form of this command to disable this functionality.
Examples
To retain all EVPN routes:
History
Release version Command history
retries
Configures the number of retries allowed to establish a connection with the Remote Authentication Dial-In User Service
(RADIUS) server.
Syntax
retries num
no retries
Command Default
The number of retries allowed is 5.
Parameters
num
Specifies the number of retries allowed to connect to a RADIUS server. The range is from 0 through 100. The default
value is 5.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no retries command restores the default value.
Examples
The following example shows how to set the number of retries allowed (to establish a connection with the RADIUS server) to
10.
History
Release version Command history
retries (Telemetry)
Defines the number of retry attempts allowed to contact the LDAP host.
Syntax
retries { num }
no retries
Command Default
The retry value 5.
Parameters
retries
Specifies the number of retries for the server connection. The range is 0 through 100.
Modes
LDAP host configuration mode.
Usage Guidelines
Use the no form of this command to remove the retry value.
Examples
To add an LDAP server with retries set to three:
History
Release version Command history
revision
Assigns a version number to the Multiple Spanning Tree Protocol (MSTP) configuration.
Syntax
revision number
no revision
Command Default
The default is 0.
Parameters
number
Specifies the revision or version number of the MSTP region. Valid values range from 0 through 255.
Modes
]Spanning tree MSTP configuration mode
Usage Guidelines
Enter no revision to return to the default setting.
Examples
To set the configuration revision to 1:
History
Release version Command history
rfc1583-compatibility (OSPF)
Configures compatibility with RFC 1583.
Syntax
rfc1583-compatibility
no rfc1583-compatibility
Command Default
OSPF is compatible with RFC 1583 (OSPFv2).
Modes
OSPF router configuration mode
Usage Guidelines
OSPF is compatible with RFC 1583 (OSPFv2) and maintains a single best route to an autonomous system (AS) boundary
router in the OSPF routing table. Disabling this compatibility causes the OSPF routing table to maintain multiple intra-AS paths,
which helps prevent routing loops.
Examples
The following example disables compatibility with RFC 1583.
History
Release version Command history
rib-route-limit
Limits the maximum number of BGP Routing Information Base (RIB) routes that can be installed in the Routing Table Manager
(RTM).
Syntax
rib-route-limit num
no rib-route-limit
Command Default
Any number of RIB routes can be installed in the RTM.
Parameters
num
Decimal value for the maximum number of RIB routes to be installed in the RTM. Valid values range from 1 through
4294967295.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
This command controls the number of routes installed by BGP, irrespective of whether those BGP routes are the preferred
routes in the system. BGP locally tracks the number of routes installed and the number of routes withdrawn from RIB. If the total
number of routes installed exceeds the value specified by num, routes will not be installed.
If num is increased, route calculation is automatically triggered.
The no form of the command removes the configured maximum number of RIB routes allowed.
Examples
The following example configures the device to limit the maximum number of BGP4 RIB routes that can be installed in the
RTM.
The following example configures the device to limit the maximum number of BGP4+ RIB routes that can be installed in the
RTM in VRF instance "red".
History
Release version Command history
rmon alarm
Sets the RMON alarm conditions.
Syntax
rmon alarm index snmp_oid interval seconds [ absolute | delta ] rising-threshold value event number [ falling-threshold value
event number [ owner name ]
Command Default
No alarms are configured.
Parameters
index
Specifies the RMON alarm index. Valid values range from 1 through 65535.
snmp_oid
Specifies the MIB object to monitor. The variable must be in the SNMP OID format, for example,
1.3.6.1.2.1.16.1.1.1.5.65535, where 65535 is rmon collection stats index on a given interface. The object type must
be a counter32.
interval seconds
Specifies the RMON alarm sample interval in seconds. Valid values range from 1 through 2147483648.
absolute
Sets the sample type as absolute.
delta
Sets the sample type as delta.
rising-threshold value
Specifies the RMON alarm rising threshold. Valid values range from 0 through 4294967295.
event number
Specifies the event for the rising alarm. Valid values range from 1 through 65535.
falling-threshold value
Specifies the RMON alarm falling threshold. Valid values range from 0 through 4294967295.
event number
Specifies the event for the rising alarm. Valid values range from 1 through 65535.
owner name
Specifies the identity of the owner. The maximum number of characters is 15.
Modes
Global configuration mode
Usage Guidelines
Enter no rmon alarm to disable the alarm conditions.
Examples
To set RMON alarm conditions:
History
Release version Command history
Syntax
rmon collection history number [ buckets bucket_number | interval seconds | owner name ]
Command Default
RMON history collection is not enabled.
Parameters
number
Specifies the RMON collection control index value. Valid values range from 1 through 65535.
buckets bucket_number
Specifies the maximum number of buckets for the RMON collection history. Valid values range from 1 through
65535.
interval seconds
Specifies the alarm sample interval in seconds. Valid values range from 1 through 3600. The default value is 1800.
owner name
Specifies the identity of the owner. The maximum number of characters is 15.
Modes
Interface subtype configuration mode
Usage Guidelines
This command collects periodic statistical samples of Ethernet group statistics on a specific interface for later retrieval.
Enter no rmon collection history number to disable the history of statistics collection.
Examples
To collect RMON statistics, with an RMON collection control index value of 5 for the owner named admin, on a specific
Ethernet interface:
History
Release version Command history
Syntax
rmon collection stats number [ owner name ]
Command Default
RMON statistic collection is not enabled.
Parameters
number
Specifies the RMON collection control index value. Valid values range from 1 through 65535.
owner name
Specifies the identity of the owner.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no rmon collection stats number to disable the collection of statistics.
Examples
The following example shows how to collect RMON statistics, with an RMON collection control index value of 2 for the owner
named admin, on a specific Ethernet interface:
History
Release version Command history
rmon event
Adds or removes an event in the RMON event table associated to the RMON alarm number.
Syntax
rmon event index [ description word | log | owner name | trap word ]
Command Default
No events are configured.
Parameters
index
Specifies the RMON event number. Valid values range from 1 through 65535.
description word
Specifies a description of the event.
log
Generates an RMON log when an event is triggered.
owner name
Specifies the owner of the event. The name string must be between 1 and 15 characters in length.
trap word
Specifies the SNMP community or string name to identify this trap.
Modes
Global configuration mode
Usage Guidelines
Enter no rmon event to remove the event configuration.
Examples
To configure an RMON event:
History
Release version Command history
role name
Creates or modifies a non-default role.
Syntax
role name role_name [ desc description ]
Parameters
role_name
Specifies the name of the role.
desc description
Specifies an optional role description.
Modes
Global configuration mode
Usage Guidelines
For each role that you create, you define one or more rules. Each user is associated with one—and only one—role.
Role names are from 4 through 32 characters, must begin with a letter, and can contain alphanumeric characters and
underscores. The name cannot be same as that of an existing user.
The description field supports up to 64 characters and can include any printable ASCII character, except for the following
characters: single quotation mark (‘), double quotation mark ("), exclamation point (!), colon (:), and semi-colon (;). If the
description contains spaces, enclose the text in double quotation marks.
The maximum number of roles supported is 64, including the user and admin default roles.
Examples
The following example creates a role.
History
Release version Command history
Syntax
root access console
Modes
Global configuration mode
Usage Guidelines
The no root access console allows root access to the device through all terminals (SSH, Telnet, and console).
Examples
Typical command output:
History
Release version Command history
root enable
Enables root access to the device following a firmware configuration.
Syntax
root enable
no root enable
Modes
Global configuration mode
Usage Guidelines
The no root enable command disables root access to the device.
Examples
Typical command output:
History
Release version Command history
Syntax
route-map name { permit | deny } stanza
Parameters
name
Specifies the name of the route map. Names range from 1 through 63 ASCII characters in length.
permit
Allows a matching pattern.
deny
Disallows a matching pattern.
stanza
Specifies the stanza ID. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
This command is used with the match and set commands.
The continue command configures the route map to continue to evaluate and run match statements after a successful match
occurs. The continue statement proceeds to the route map with the specified sequence number. If no sequence number is
specified, the statement proceeds to the route map with the next sequence number (as an "implied" continue).
Examples
The following example configures a route map that allows a matching pattern.
History
Release version Command history
route-map (NPB)
Creates a route map; for an existing route map, adds a stanza.
Syntax
route-map name { permit | deny } stanza
Parameters
name
Specifies the name of the route map. Names range from 1 through 63 ASCII characters in length.
permit
Enables the set statement within the specified stanza, as specified in the Usage Guidelines.
deny
Disables the set statement within the specified stanza, as specified in the Usage Guidelines.
stanza
Specifies the stanza ID. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
The following table describes the interactions between route-map permit and deny stanzas and permit and deny rules in ACLs
applied to those stanzas by match { mac | ip | ipv4 | uda } address acl statements.
Permit Deny Packets that match a deny keyword are denied from using the stanza set statement:
Examples
The following example enables the NPB route map for an Ethernet interface so that all ingress traffic from interface Ethernet
0/1 exits from port-channel 100. The absence of a match statement is treated as "match any"; all traffic is forwarded according
to the set statement.
The following example configures ingress traffic from Ethernet 0/1 and port-channel 100 to egress Ethernet 0/5.
The following example replicates traffic entering an interface to multiple egress interfaces.
The following two-stanza route-map forwards frames according to the following conditions: Stanza 10 examines whether a
frame matches the specified ACL; a match forwards the frame to port 0/21. If 0/21 is not up, the frame is forwarded to port-
channel 666. If the Stanza 10 conditions are not met, Stanza 20 is examined. Because there is no match statement, it is
considered a “match any”. All such traffic is forwarded to TVF domain 100—if it contains at least one interface and at least one
of its member ports is up. If TVF 100 is not up, traffic is forwarded to interface 0/21, if up.
The following NPB-grid example creates destination 5 within destination group 99. It then configures ingress traffic from
Ethernet 0/1 and port-channel 100 to destination group 99.
History
Release version Command history
Syntax
route-target { both | import } auto [ admin-value:arbitrary-value ]
Command Default
Disabled.
Parameters
both auto
Specifies auto-generation of the import and export route-target community attributes.
export auto
Specifies auto-generation of the export route-target community attribute.
import auto
Specifies auto-generation of the import route-target community attribute.
admin-value
The administrative number assigned to the route. This can be a local ASN number or an IP address. The ASN number
can be either a 2-byte number (from 0 through 65535) or a 4-byte number (from 0 through 4294967295).
arbitrary-value
An arbitrary number you choose. The range of valid values is from 0 through 65535 if the ASN is is an IP address or
a 2 byte ASN. The range is 0 through 4294967295 if the ASN is a 4 byte ASN.
Modes
EVPN instance configuration mode
Usage Guidelines
The no form of this command removes configured route target parameters.
Examples
The following example configures auto-generation of the import and export route-target community attributes for EVPN
VLAN/BD 200.
History
Release version Command history
router bgp
Enables BGP routing.
Syntax
router bgp
Command Default
BGP routing is not enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of the command disables BGP routing.
Examples
The following example enables BGP routing.
History
Release version Command history
router ospf
Enables and configures the Open Shortest Path First version 2 (OSPFv2) routing protocol.
Syntax
router ospf [ vrf name ]
no router ospf
Parameters
vrf name
Specifies a nondefault VRF.
Modes
Global configuration mode
Usage Guidelines
Use this command to enable the OSPFv2 routing protocol and enter OSPF router or OSPF router VRFconfiguration mode.
OSPFv2 maintains multiple instances of the routing protocol to exchange route information among various VRF instances.
The no form of the command deletes all current OSPF configuration and blocks any further OSPFv2 configuration.
Examples
The following example enables OSPFv2 on a default VRF and enters OSPF VRF router configuration mode.
History
Release version Command history
router-interface
Attaches (binds) a router interface to a VLAN, creating a Layer 3 interface.
Syntax
router-interface ve vlan_ID
no router-interface ve
Command Default
A router interface is not configured.
Parameters
ve vlan_ID
Specifies a VLAN ID.
Modes
VLAN configuration mode
Usage Guidelines
Only one router VE interface can be mapped to a VLAN.
Use the no form of the command to remove the router interface from the VLAN.
Examples
To attach a router interface to a Layer 2 VLAN:
device(config)# vlan 2
device(config-vlan-2)# router-interface ve 2
device(config)# vlan 2
device(config-vlan-2)# no router-interface ve
History
Release version Command history
rule
Creates role-based access permissions (RBAC) associated with a role.
Syntax
rule index [ action { accept | reject } ] [ operation { read-only | read-write } ] role role_name command command_name
no rule index
Command Default
The default for action is accept. The default for operation is read-write.
Parameters
index
Specifies a numeric identifier for the rule. Valid values range from 1 through 512.
role role_name
Specifies the name of the role for which the rule is defined.
command command_name
Specifies the command for which access is defined. Separate commands with a space. To display a list of supported
commands, type a question mark (?).
Modes
Global configuration mode
Usage Guidelines
For each role that you create, you define one or more rules. Each account is associated with one—and only one—role.
When you create a rule, the index, role, and command operands are mandatory; the action and operation operands are
optional.
When you modify a rule, all operands except index and role are optional.
Examples
The following example creates rules enabling the NetworkSecurityAdmin role to create user accounts.
History
Release version Command history
Syntax
seq seq-value { deny | permit } uda-value-0 mask-0 uda-value-1 mask-1 uda-value-2 mask-2 uda-value-3 mask-3
[ count ] [ log ]
no seq seq-value
{ deny | permit } uda-value-0 mask-0 uda-value-1 mask-1 uda-value-2 mask-2 uda-value-3 mask-3 [ count ] [ log ]
no { deny | permit } uda-value-0 mask-0 uda-value-1 mask-1 uda-value-2 mask-2 uda-value-3 mask-3 [ count ] [ log ]
Command Default
The concluding, default rule is deny.
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list.
seq-value
Valid values range from 1 through 65535.
deny
Specifies rules to deny traffic.
permit
Specifies rules to permit traffic.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule.
Modes
UDA configuration mode
Usage Guidelines
Ths command is supported only in NPB system mode.
Examples
The following example creates a UDA and defines a permit rule.
History
Release version Command history
Syntax
seq seq_num { match any [ [ source src_ip ] [ destination dst_ip ] | [ endpoint endpoint_ip ] ] | [ type vxlan [ vni value ] ] }
no seq seq_num
no { match any [ [ source src_ip ] [ destination dst_ip ] | [ endpoint endpoint_ip ] ] | [ type vxlan [ vni value ] ] }
Command Default
No classification is applied.
Parameters
seq seq_num
Inserts a tunnel identifier in the class map at a certain position. Range is from 0 through 4294967290.
match any
Applies the specified flow filters to all active tunnels in the system.
endpoint endpoint_ip
Specifies the IP address assigned to the tunneling endpoint within the system for filtering.
type vxlan
Specifies VXLAN tunnel type.
vni value
Specifies the VXLAN Network Identifier (VNI) to match against, and optionally also specify a VNI mask to use to filter a
range of contiguous VNI values.
Modes
Overlay class map configuration mode
Usage Guidelines
Use the no forms of this command to delete the matching filter from the ACL..
A tunnel can be identified by the outer packet IP header. The user can specify either the source or the destination or both as a
tunnel identifier. If both are not specified, an implicit "match any" is made for the missing option.
The user can specify the IP address assigned to the tunneling endpoint within the system for filtering. If the IP address of the
specified endpoint occurs as either a source or a destination in the outbound packet, this is considered an overlay class map
"hit."
Examples
The following example specifies a sequence number.
The following example applies the flow filter to all active tunnels in the system.
History
Release version Command history
Syntax
seq seq-value { permit | deny | hard-drop } ip-protocol { S_IPaddress mask | host S_IPaddress | any } [ source-operator
[ S_port-numbers ] ] { D_IPaddress mask | host D_IPaddress | any } [ dscp DSCPvalue ] [ destination-operator [ D_port-
numbers ] ] [ TCP-flags ] [ vlan vlanID ] [ count ] [ log ]
no seq seq-value
{ permit | deny | hard-drop } ip-protocol { S_IPaddress mask | host S_IPaddress | any } [ source-operator [ S_port-numbers ] ]
{ D_IPaddress mask | host D_IPaddress | any } [ dscp DSCPvalue ] [ destination-operator [ D_port-numbers ] ] [ TCP-
flags ] [ count ] [ vlan vlanID ] [ log ]
no { permit | deny | hard-drop } ip-protocol { S_IPaddress mask | host S_IPaddress | any } [ source-operator [ S_port-
numbers ] ] { D_IPaddress mask | host D_IPaddress | any } [ dscp DSCPvalue ] [ destination-operator [ D_port-
numbers ] ] [ TCP-flags ] [ vlan vlanID ] [ count ] [ log ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list and a sequence number is automatically assigned to it.
seq-value
Valid values range from 1 through 4294967290.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a permit for this address in a
preceding rule.
ip-protocol
Indicates the type of IP packet you are filtering. The options are as follows:
<0-255>
Protocol number custom value from 0 through 255.
icmp
Internet Control Message Protocol
ip
Any IP protocol
tcp
(Ignored for ACLs in overlay-transit policy maps) (Supported only if the containing ACL is applied to incoming
traffic) Transmission Control Protocol
udp
User Datagram Protocol
S_IPaddress
Specifies a source address for which you want to filter the subnet.
mask
Defines a mask, whose effect is to specify a subnet that includes the source address that you specified. For
options to specify the mask, see the Usage Guidelines.
host
Specifies a source address.
S_IPaddress
The source address.
any
Specifies all source addresses.
eq
The policy applies to the TCP or UDP port name or number you enter after eq.
gt
(Not supported for IPv4 ACLs in overlay-transit policy maps) The policy applies to TCP or UDP port
numbers equal to or greater than the port number or the numeric equivalent of the port name you enter after
gt.
lt
(Not supported for IPv4 ACLs in overlay-transit policy maps) The policy applies to TCP or UDP port
numbers that are equal to or less than the port number or the numeric equivalent of the port name you enter
after lt.
neq
(Not supported for IPv4 ACLs in overlay-transit policy maps) The policy applies to all TCP or UDP port
numbers except the port number or port name you enter after neq.
range
(Not supported for IPv4 ACLs in overlay-transit policy maps) The policy applies to all TCP or UDP port
numbers that are between the first TCP or UDP port name or number and the second one you enter
following the range keyword. The range includes the port names or numbers you enter. For example, to apply
the policy to all ports between and including 23 (Telnet) and 53 (DNS), enter the following: range 23 53 (two
values separated by a space). The first port number in the range must be lower than the last number in the
range.
D_IPaddress
Specifies a destination address for which you want to filter the sub-net.
mask
Defines a mask, whose effect is to specify a subnet that includes the destination address that you specified.
For options to specify the mask, see the Usage Guidelines.
host
Specifies a destination address.
D_IPaddress
The destination address.
any
Specifies all destination addresses.
dscp
Matches DSCPvalue against the DSCP value of the packet.
DSCPvalue
From 0 through 63.
vlan vlanID
(Ignored for ACLs in overlay-transit policy maps) Specifies a VLAN interface to which the ACL is bound.
TCP-flags
If you specify tcp ip-protocol, one or more of the following flags are available:
ack
Filters packets for which the ack (acknowledge) flag is set.
fin
Filters packets for which the fin (finish) flag is set.
rst
Filters packets for which the rst (reset) flag is set.
sync
Filters packets for which the syn (synchronize) flag is set.
urg
Filters packets for which the urg (urgent) flag is set.
push
Filters packets for which the psh (push) flag is set.
count
Enables statistics for the rule. If a rule that includes count is duplicated in both a security ACL and an overlay-gateway
policy-map ACL, the counter is enabled only for the security ACL.
log
(Ignored for ACLs in overlay-transit policy maps) Enables inbound logging for the rule. In addition, the ACL log buffer
must be enabled, using the debug access-list-log buffer command.
Modes
ACL configuration mode
Usage Guidelines
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When creating rules, specifying
sequence values determines the order of rule processing. If you do not specify a sequence value, the rule is added to the end of
the list.
For ACLs in overlay-transit policy maps, the only mask supported is all bits set (indicating exact host match). So there is no
advantage to defining a mask.
All parameters—including masks—are supported for ACLs in overlay-gateway policy maps. For IPv4 ACLs in overlay-transit
policy maps, refer to the "Parameters" section.
If you are defining rules for a QoS ACL, be aware of the following considerations for ACLs implemented under flow-based QoS.
(For details, refer to the Extreme SLX-OS QoS and Traffic Management Configuration Guide for SLX 9140 and SLX 9240.)
• Because ACLs applied for QoS use implement a unified counter for all rules in an ACL, rule-level count keywords are
ignored.
• The deny keyword functions as a PASS THROUGH: For a match, QoS action defined for that class is not applied.
For both interface ACLs and receive-path ACLs, you use identical commands to create the ACLs. You also use identical
commands to define permit/deny rules in the ACLs. The only variance is the command you use to apply the ACL:
• To apply an interface ACL, from an interface-subtype configuration mode you use the { ip | ipv6 | mac } access-group
command.
• To apply a receive-path ACL, from global configuration mode, you use the { ip | ipv6 } receive access-group
command.
All parameters are supported for ACLs in overlay-gateway policy maps. For IPv4 ACLs in overlay-transit policy maps, refer to
the "Parameters" section.
Examples
The following example creates an IPv4 extended ACL and defines rules.
The following example creates an IPv4 extended ACL, defines rules in the ACL, and applies it as a receive-path ACL.
History
Release version Command history
Syntax
seq seq-value { permit | deny | hard-drop } { S_IPaddress mask | host S_IPaddress | any } [ count ] [ log ]
no seq seq-value
{ permit | deny | hard-drop } { S_IPaddress mask | host S_IPaddress | any } [ count ] [ log ]
no { permit | deny | hard-drop } { S_IPaddress mask | host S_IPaddress | any } [ count ] [ log ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list and a sequence number is automatically assigned to it.
seq-value
Valid values range from 1 through 4294967290.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a permit for this address in a
preceding rule.
S_IPaddress
Specifies a source address for which you want to filter the subnet.
mask
Defines a mask, whose effect is to specify a subnet that includes the source address that you specified. For
options to specify the mask, see the Usage Guidelines.
host
Specifies a source address.
S_IPaddress
The source address.
any
Specifies all source addresses.
count
Enables statistics for the rule. If a rule that includes count is duplicated in both a security ACL and an overlay-gateway
policy-map ACL, the counter is enabled only for the security ACL.
log
(Ignored for ACLs in overlay-transit policy maps) Enables inbound logging for the rule. In addition, the ACL log buffer
must be enabled, using the debug access-list-log buffer command.
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source addresses. You can also enable counters and logging.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When creating rules, specifying
sequence values determines the order of rule processing. If you do not specify a sequence value, the rule is added to the end of
the list.
For ACLs in overlay-transit policy maps, the only mask supported is all bits set (indicating exact host match). So there is no
advantage to defining a mask.
All parameters—including masks—are supported for ACLs in overlay-gateway policy maps. For IPv4 ACLs in overlay-transit
policy maps, refer to the "Parameters" section.
If you are defining rules for a QoS ACL, be aware of the following considerations for ACLs implemented under flow-based QoS.
(For details, refer to the Extreme SLX-OS QoS and Traffic Management Configuration Guide for SLX 9140 and SLX 9240.)
• Do not include the count keyword in ACLs intended for flow-based QoS implementation, because such ACLs
automatically share a common counter.
• The deny keyword functions as a PASS THROUGH: For a match, QoS action defined for that class is not applied.
Examples
The following example shows how to create a IPv4 standard ACL, define rules for it, and apply the ACL to an interface:
device# configure
device(config)# ip access-list standard stdACL3
device(conf-ipacl-std)# seq 5 permit host 10.20.33.4
device(conf-ipacl-std)# seq 15 deny any
device(conf-ipacl-std)# exit
device(config)# interface ethernet 0/5
device(conf-if-eth-0/5)# ipv4 access-group stdACL3 in
History
Release version Command history
Syntax
seq seq-value { permit | deny | hard-drop } ip-protocol { any | S_IPaddress / prefix_len | host S_IPaddress } [ source-operator
[ S_port-numbers ] ] { any | D_IPaddress / prefix_len | host D_IPaddress } [ destination-operator [ D_port-numbers ] ]
[ dscp DSCPvalue ] [ tcp/udp-flags ] [ vlan vlanID ] [ count ] [ log ]
no seq seq-value
{ permit | deny | hard-drop } ip-protocol { any | S_IPaddress / prefix_len | host S_IPaddress } [ source-operator [ S_port-
numbers ] ] { any | D_IPaddress / prefix_len | host D_IPaddress } [ destination-operator [ D_port-numbers ] ] [ dscp
DSCPvalue ] [ tcp/udp-flags ] [ vlan vlanID ] [ count ] [ log ]
no { permit | deny | hard-drop } ip-protocol { any | S_IPaddress / prefix_len | host S_IPaddress } [ source-operator [ S_port-
numbers ] ] { any | D_IPaddress / prefix_len | host D_IPaddress } [ destination-operator [ D_port-numbers ] ] [ dscp
DSCPvalue ] ] [ tcp/udp-flags ] [ vlan vlanID ] [ count ] [ log ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list.
seq-value
Valid values range from 1 through 4294967290.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a permit for this address in a
preceding rule.
ip-protocol
Indicates the type of IP packet you are filtering. The options are as follows:
<0-255>
Protocol number custom value from 0 through 255.
ipv6-icmp
Internet Control Message Protocol
ipv6
Any IP protocol
tcp
Transmission Control Protocol
udp
User Datagram Protocol
any
Specifies all source addresses.
S_IPaddress
Specifies a source address for which you want to filter the subnet. For options to abbreviate the address, see the
Usage Guidelines.
prefix_len
Indicates how many of the high-order, contiguous bits of the address comprise the IPv6 prefix.
host
Specifies a source address.
S_IPaddress
The specific address. For options to abbreviate the address, see the Usage Guidelines.
source-operator
If you specified tcp or udp ip-protocol, the following optional operators are available:
eq
The policy applies to the TCP or UDP port name or number you enter after eq.
gt
The policy applies to TCP or UDP port numbers equal to or greater than the port number or the numeric
equivalent of the port name you enter after gt.
lt
The policy applies to TCP or UDP port numbers that are equal to or less than the port number or the numeric
equivalent of the port name you enter after lt.
neq
The policy applies to all TCP or UDP port numbers except the port number or port name you enter after neq.
range
The policy applies to all TCP or UDP port numbers that are between the first TCP or UDP port name or
number and the second one you enter following the range keyword. The range includes the port names or
numbers you enter. For example, to apply the policy to all ports between and including 23 (Telnet) and 53
(DNS), enter the following: range 23 53 (two values separated by a space). The first port number in the range
must be lower than the last number in the range.
S_port-numbers
(Valid only when ip-protocol is UDP or TCP) Specify one or more port numbers.
any
Specifies all destination addresses.
D_IPaddress
Specifies a destination address for which you want to filter the subnet. For options to abbreviate the address, see the
Usage Guidelines.
prefix_len
Indicates how many of the high-order, contiguous bits of the address comprise the IPv6 prefix.
host
Specifies a destination address.
D_IPaddress
The destination address. For options to abbreviate the address, see the Usage Guidelines.
destination-operator
Specifies one of the following destination operators:
eq
The policy applies to the TCP or UDP port name or number you enter after eq.
gt
The policy applies to TCP or UDP port numbers equal to or greater than the port number or the numeric
equivalent of the port name you enter after gt.
lt
The policy applies to TCP or UDP port numbers that are equal to or less than the port number or the numeric
equivalent of the port name you enter after lt.
neq
The policy applies to all TCP or UDP port numbers except the port number or port name you enter after neq.
range
The policy applies to all TCP or UDP port numbers that are between the first TCP or UDP port name or
number and the second one you enter following the range keyword. The range includes the port names or
numbers you enter. For example, to apply the policy to all ports between and including 23 (Telnet) and 53
(DNS), enter the following: range 23 53. The first port number in the range must be lower than the last
number in the range.
D_port_numbers
(Valid only when ip-protocol is UDP or TCP) Specify one or more destination port numbers.
dscp
Matches DSCPvalue against the DSCP value of the packet.
DSCPvalue
From 0 through 63.
vlan vlanID
Specifies a VLAN interface to which the ACL is bound.
tcp/udp-flags
If you specify tcp or udp ip-protocol, one or more of the following flags are available:
ack
Filters packets for which the ack (acknowledge) flag is set.
fin
Filters packets for which the fin (finish) flag is set.
rst
Filters packets for which the rst (reset) flag is set.
sync
Filters packets for which the syn (synchronize) flag is set.
urg
Filters packets for which the urg (urgent) flag is set.
push
Filters packets for which the psh (push) flag is set.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the debug access-list-log
buffer command.
Modes
ACL configuration mode
Usage Guidelines
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When creating rules, specifying
sequence values determines the order of rule processing. If you do not specify a sequence value, the rule is added at the end of
the list and a sequence number is automatically assigned to it.
You can abbreviate an IPv6 address by using one or more of the following rules:
• Remove one or more leading zeros from one or more groups of hexadecimal digits; this is usually done to either all or
none of the leading zeros. (For example, convert the group 0042 to 42.)
• Omit consecutive sections of zeros, using a double colon (::) to denote the omitted sections. The double colon may
only be used once in any given address, as the address would be indeterminate if the double colon were used multiple
times. A double colon may not be used to denote an omitted single section of zeros. (For example, 2001:db8::1:2 is
valid, but 2001:db8::1::2 or 2001:db8::1:1:1:1:1 are not permitted.)
All parameters are supported for ACLs in overlay-gateway policy maps. Overlay-transit policy maps do not support MAC ACLs
or IPv6 ACLs.
Examples
The following example creates an IPv6 extended ACL, defines a rule for it, and applies the ACL to an interface.
device# configure
device(config)# ipv6 access-list extended ip_acl_1
device(conf-ip6acl-ext)# seq 10 deny ipv6 2001:2002:1234:1::/64 2001:1001:1234:1::/64 count
device(conf-ip6acl-ext)# exit
device(config)# interface ethernet 0/5
device(conf-if-eth-0/5)# ipv6 access-group ip_acl_1 in
The following example creates an IPv6 extended ACL, defines rules in the ACL, and applies it as a receive-path ACL (rACL).
History
Release version Command history
Syntax
seq seq-value { deny | permit | hard-drop } { any | A:B:C:D:E:F:H:I / prefix_len | host S_IPaddress } [ count ] [ log ]
no seq seq-value
{ deny | permit | hard-drop } { any | A:B:C:D:E:F:H:I / prefix_len | host SIP_address | SIP_addressmask } [ count ] [ log ]
no { deny | permit | hard-drop } { any | A:B:C:D:E:F:H:I / prefix_len | host SIP_address | SIP_addressmask } [ count ] [ log ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list and a sequence number is automatically assigned to it.
seq-value
Valid values range from 1 through 4294967290.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a permit for this address in a
preceding rule.
any
Specifies all source addresses.
S_IPaddress
Specify a source address for which you want to filter the subnet. For options to abbreviate the address, see the Usage
Guidelines.
prefix_len
Indicates how many of the high-order, contiguous bits of the address comprise the IPv6 prefix.
host
Specifies a source address.
SIP_address
The source address. For options to abbreviate the address, see the Usage Guidelines.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the debug access-list-log
buffer command.
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source addresses. You can also enable counters and logging.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When creating rules, specifying
sequence values determines the order of rule processing. If you do not specify a sequence value, the rule is added to the end of
the list.
You can abbreviate an IPv6 address by using one or more of the following rules:
• Remove one or more leading zeros from one or more groups of hexadecimal digits; this is usually done to either all or
none of the leading zeros. (For example, convert the group 0042 to 42.)
• Omit consecutive sections of zeros, using a double colon (::) to denote the omitted sections. The double colon may
only be used once in any given address, as the address would be indeterminate if the double colon were used multiple
times. A double colon may not be used to denote an omitted single section of zeros. (For example, 2001:db8::1:2 is
valid, but 2001:db8::1::2 or 2001:db8::1:1:1:1:1 are not permitted.)
All parameters are supported for ACLs in overlay-gateway policy maps. Overlay-transit policy maps do not support MAC ACLs
or IPv6 ACLs.
Examples
The following example shows how to create an IPv6 standard ACL and define rules for it.
History
Release version Command history
Syntax
[ seq seq-value ] { deny | hard-drop } { any | SMAC_address mask | host SMAC_address } { any | host DMAC_address |
DMAC_address mask } [ vlan { all | vlanID } ] [ custom-EtherType | arp [ arp-guard ] | cfm | ipv4 | ipv6 ] [ pcp pcp-match-
value ] [ count ] [ log ] [ mirror ]
seq seq-value { permit | deny | hard-drop } { any | SMAC_address mask | host SMAC_address } { any | host DMAC_address |
DMAC_address mask } [ custom-EtherType | arp | ipv4 | ipv6 ] [ pcp pcp-match-value ] [ vlan vlanID ] [ count ] [ log ]
no seq seq-value
{ permit | deny | hard-drop } { any | SMAC_address mask | host SMAC_address } { any | host DMAC_address |
DMAC_address mask } [ custom-EtherType | arp | ipv4 | ipv6 ] [ pcp pcp-match-value ] [ vlan vlanID ] [ count ] [ log ]
no permit { any | SMAC_address mask | host SMAC_address } { any | host DMAC_address | DMAC_address mask }
[ custom-EtherType | arp | ipv4 | ipv6 ] [ vlan vlanID ] [ pcp pcp-match-value ] [ count ] [ log ]
no { deny | hard-drop } { any | SMAC_address mask | host SMAC_address } { any | host DMAC_address | DMAC_address
mask } [ custom-EtherType | arp | ipv4 | ipv6 ] [ vlan vlanID ] [ pcp pcp-match-value ] [ count ] [ log ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list and a sequence number is automatically assigned to it.
seq-value
Valid values range from 1 through 4294967290.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a permit for this address in a
preceding rule.
any
Specifies all source MAC addresses.
SMAC_address
Specifies a source MAC address and a comparison mask.
mask
Specify the mask using F's and zeros. For example, to match on the first two bytes of the address
aabb.ccdd.eeff, use the mask ffff.0000.0000. In this case, the clause matches all MAC addresses that
contain "aabb" as the first two bytes and any values in the remaining bytes.
host
Specifies a source MAC address.
SMAC_address
Use the format HHHH.HHHH.HHHH.
any
Specifies all destination MAC addresses.
DMAC_address
Specifies a destination MAC address and a comparison mask.
mask
Specifies the mask using F's and zeros. For example, to match on the first two bytes of the address
aabb.ccdd.eeff, use the mask ffff.0000.0000. In this case, the clause matches all MAC addresses that
contain "aabb" as the first two bytes and any values in the remaining bytes.
host
Specifies a destination MAC address.
DMAC_address
Use the format HHHH.HHHH.HHHH.
custom-EtherType
Specifies a custom EtherType value for which to set the permit or deny conditions. Valid values range from 1536
through 65535.
arp
Specifies to permit or deny the ARP protocol (0x0806).
arp-guard
Enables ARP Guard.
ipv4
Specifies to permit or deny the IPv4 protocol (0x0800).
ipv6
Specifies to permit or deny the IPv6 protocol (0x86dd).
vlan vlanID
Specifies a VLAN interface to which the ACL is bound.
pcp pcp-match-value
Filters by PCP priority value. Permitted values are 0 through 7.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the debug access-list-log
buffer command.
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source and destination MAC addresses and protocol type.
You can also enable counters and logging per rule.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When creating rules, specifying
sequence values determines the order of rule processing. If you do not specify a sequence value, the rule is added to the end of
the list.
Although in an extended-ACL rule you can specify mirror and log, only one of the two is processed, as follows:
• In a permit rule, the order of precedence is mirror > log.
• In a deny or hard-drop rule, the order of precedence is log > mirror.
All parameters are supported for ACLs in overlay-gateway policy maps. Overlay-transit policy maps do not support MAC ACLs
or IPv6 ACLs.
To delete a rule from an ACL, do the relevant of the following:
• If you know the rule number, enter no seq seq-value.
• If you do not know the rule number, type no and then enter the full syntax without seq-value .
Examples
The following example creates a rule in a MAC extended ACL to deny IPv4 traffic from the source MAC address
0022.3333.4444 to the destination MAC address 0022.3333.5555 and to enable the counting of packets.
History
Release version Command history
Syntax
seq seq-value { deny | permit | hard-drop } { any | SMAC_address mask | host SMAC_address } [count ] [ log ]
no seq seq-value
{ deny | permit | hard-drop } { any | SMAC_address mask | host SMAC_address } [count ] [ log ]
no seq { deny | permit | hard-drop } { any | SMAC_address mask | host SMAC_address } [count ] [ log ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq seq-value, the rule is added
at the end of the list and a sequence number is automatically assigned to it.
seq-value
Valid values range from 1 through 4294967290.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a permit for this address in a
preceding rule.
any
Specifies all source MAC addresses.
SMAC_address
Specifies a source MAC address and a comparison mask.
mask
Specify the mask using F's and zeros. For example, to match on the first two bytes of the address
aabb.ccdd.eeff, use the mask ffff.0000.0000. In this case, the clause matches all MAC addresses that
contain "aabb" as the first two bytes and any values in the remaining bytes.
host
Specifies a source MAC address.
SMAC_address
Use the format HHHH.HHHH.HHHH.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the debug access-list-log
buffer command.
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source MAC address. You can also enable counters and
logging.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When creating rules, specifying
sequence values determines the order of rule processing. If you do not specify a sequence value, the rule is added to the end of
the list.
All parameters are supported for ACLs in overlay-gateway policy maps. Overlay-transit policy maps do not support MAC ACLs
or IPv6 ACLs.
Examples
The following command creates statistic-enabled rules in a MAC standard ACL.
The following command deletes a rule in a MAC standard ACL, by specifying the seq number.
History
Release version Command history
seq overlay-class
Creates a stanza within an overlay policy and defines the classification method to be used to identify the desired tunnel.
Syntax
seq seq_num overlay-class name
no seq seq_num
Command Default
No stanza is created.
Parameters
seq seq_num
Inserts a new stanza and classification within the overlay policy map. Range is from 0 through 4294967290.
name
Identifies the tunnel on which to perform specific actions or flows.
Modes
Overlay policy map configuration mode
Usage Guidelines
If a sequence value is not specified, the defined stanza is assigned the next highest available sequence value.
The overlay class map name must already exist and be provisioned, or else an error is returned.
Use the no form of this command to delete the matching stanza from the policy. To delete the stanza and all associated flows
and actions, the user must simply use the no form. The classification map name is not required, because a stanza can include
only one overlay class map directive.
Examples
The following example inserts a new stanza and classification within an overlay policy map.
The following example deletes the matching stanza from the policy.
History
Release version Command history
service password-encryption
Enables a global password encryption policy that overrides username encryption settings.
Syntax
service password-encryption
no service password-encryption
Command Default
Global password encryption policy is enabled.
Modes
Global configuration mode
Usage Guidelines
If global password encryption policy is enabled, it overrides username encryption settings.
To disable global password encryption policy, enter the no form of this command.
Even if global password encryption policy is disabled, the following username syntax does encrypt that user's password:
encryption-level 7.
Examples
The following example enables global password encryption policy.
History
Release version Command history
service-policy
Binds a policy map to inbound traffic on an interface.
Syntax
service-policy policy-mapname
no service-policy policy-mapname
Command Default
No service policy is created.
Parameters
in
Binds the policy map to inbound traffic.
out
Binds the policy map to outbound traffic.
policy-mapname
Name of the policy map.
Modes
Interface configuration mode
Usage Guidelines
This command applies a policy-map containing a class-map with specific policer parameters and match criteria to a switch
interface. The policy map must be configured before you can apply it (refer to the description of the policy-map command).
Examples
The following binds a service policy for inbound traffic on a specific Ethernet interface.
The following removes a service policy for inbound traffic from a specific Ethernet interface.
History
Release version Command history
set (policer)
Establishes a new setting in the default policer remark profile for the specified remark values.
Syntax
set remark-value value-setting
Command Default
The police-remark-profile command has been executed. Then, the action command has been executed, specifying the color
classification type.
Parameters
remark-value
Specifies which remark value is to be modified.
value-setting
Specifies the value to be set for the specified remark value.
Modes
Policer remarking profile configuration mode
Usage Guidelines
Use this command after executing the police-remark-profile command and after executing the action command, specifying
color as the classification type. You issue the set command to specify remark values in the default policer remark profile for cos,
traffic-class, and dscp.
Examples
The following is an example of executing the set command to specify the settings in the default policer remark profile for the
remark values for conforming traffic.
History
Release version Command history
set as-path
Sets a prepended string or a tag for an AS-path attribute in a route-map instance.
Syntax
set as-path { prepend string | tag }
Parameters
prepend
Prepends the string to the AS-path.
string
AS numbers. Range is from 1 through 4294967295.
tag
Converts the tag of a route into an autonomous system path.
Modes
Route-map configuration mode
Examples
The following example a prepended string or a tag for an AS-path attribute in a route-map instance.
History
Release version Command history
set automatic-tag
Sets the route-map tag value.
Syntax
set automatic-tag value
Parameters
value
The value for the computed tag.
Modes
Global configuration mode
Examples
The following example sets a route-map tag value of 5.
History
Release version Command history
set comm-list
Sets a community list for deletion in a route-map instance.
Syntax
set comm-list name
Parameters
name
Community list name. Range is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Use the no version of this command to disable this feature.
Examples
The following example sets a community list for deletion in a route-map instance.
History
Release version Command history
set community
Sets a BGP community attribute in a route-map instance.
Syntax
set community [ community-number | additive | internet | local-as | no-advertise | no-export | none]
Parameters
community-number
BGP community number, in two format options:(1) Range is from 1 through 4294967295.(2) Format is AA:NN,
where AA is the AS number, and NN is a locally significant number.
additive
Add to the existing community.
internet
Send to internet (well-known community).
local-as
Do not send outside local AS (well-known community).
no-advertise
Do not advertise to any peer (well-known community).
no-export
Do not export to next AS (well-known community).
none
Sets no community attribute.
Modes
Route-map configuration mode
Examples
The following example sets a BGP community attribute that does not export to the next AS in a route-map instance.
History
Release version Command history
set dampening
Sets a BGP route-flap dampening penalty in a route-map instance.
Syntax
set dampening { half-life number | reuse number | suppressnumber | max-suppressionnumber }
Command Default
The default is 15.
Parameters
half-life number
Half-life in minutes for the penalty. Range is from 1 through 45.
reuse number
Route that is unsuppressed if the penalty for a flapping route decreases enough to fall below this value. The process of
unsuppressing routes occurs at 10-second increments. Range is from 1 through 20000.
suppress number
Value at which to start suppressing a route. Range is from 1 through 20000.
max-suppression number
Maximum duration in minutes to suppress a stable route. Range is from 1 through 255.
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command removes the penalty.
Examples
The following example sets a maximum duration of 25 minutes for a BGP route-flap dampening penalty in a route-map
instance.
History
Release version Command history
set distance
Sets the administrative distance for matching OSPF routes in route-map instance.
Syntax
set distance value
no set distance
Parameters
value
Administrative distance for the route. Range is from 1 through 254.
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command removes the configuration.
Examples
The following example sets an administrative distance of 50 for matching OSPF routes in a route-map instance.
History
Release version Command history
set extcommunity
Sets an extended BGP community attribute in a route-map instance.
Syntax
set extcommunity { rt extcommunity value | soo extcommunity value }
no set extcommunity
Command Default
No extended BGP community attribute is set.
Parameters
rt
Specifies the route target (RT) extended community attribute.
soo
Specifies the site of origin (SOO) extended community attribute.
extcommunity value
Specifies the value. The value can be one of the following:
ASN:nn—autonomous-system-number:network-number
Autonomous system (AS) number and network number.
IPAddress:nn—ip-address:network-number
IP address and network number.
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command deletes an extended community set statement from the configuration file.
Examples
The following example sets the route target to extended community attribute 1:1 for routes that are permitted by the route map.
The following example sets the site of origin to extended community attribute 2:2 for routes that are permitted by the route
map.
History
Release version Command history
Syntax
[ precedence precedence-value ] set interface { ethernet slot / port | port-channel number | pbf-destination-group pbf-dest-
group-id } [ strip-vlan outer ] [ add-vlan outer vlan-id ]
no precedence precedence-value
no set interface { ethernet slot / port | port-channel number | pbf-destination-group pbf-dest-group-id } [ strip-vlan outer ]
[ add-vlan outer vlan-id ]
Parameters
precedence
(Optional) Enables you to assign a precedence number to the set statement. If you do not specify precedence
precedence-value, the statement is added at the end of the route map and a precedence number is automatically
assigned to it.
precedence-value
Values range from 1 through 65535.
null0
(Not implemented under NPB) Specifies the Null0 interface, dropping the packet.
port-channel number
Specifies a port-channel interface.
pbf-destination-group pbf-dest-group-id
Specifies a policy-based forwarding (PBF) destination-group ID. Values range from 1 through 8192.
strip-vlan outer
Removes outer VLAN headers from the egressing packet.
Modes
Route-map configuration mode
Usage Guidelines
This command is supported only under NPB system mode. If the system mode is default, set it to NPB, using the system-
mode command.
The order of the set statements in a route-map is critical: In general, a match followed by a valid set interface or set next-hop-
tvf-domain statement stops further processing. Specifying precedence values determines the order of statement processing. If
you do not specify precedence values, they are automatically assigned as follows: The first set statement is assigned
"precedence 10", the second is assigned "precedence 20", and so forth.
To display policy-map set-statement precedence values, run the show running-config route-map command. The results will
make it easier for you to add additional set statements in the required order.
Adding a VLAN tag enables you to mark network traffic for custom processing downstream, such as application-specific
filtering on an interconnected packet broker or special handling by the analytics application.
You cannot have both set interface {ethernet | port-channel } and set interface pbf-destination-group commands in a stanza.
To delete a set interface statement from a route map, perform one of the following actions:
• If you know the precedence number, enter no precedence precedence-value.
• If you do not know the precedence number, type no followed by the full syntax without precedence precedence-value.
Examples
The following example configures ingress traffic from Ethernet 0/1 and port-channel 100 to egress Ethernet 0/5.
The following NPB-grid example creates destination 5 within destination group 99. It then configures ingress traffic from
Ethernet 0/1 and port-channel 100 to destination group 99.
History
Release version Command history
Syntax
[ precedence precedence-value ] set interface { ethernet slot / port | port-channel number } [ type-fabric ]
Parameters
precedence
(Optional) Enables you to assign a precedence number to the set statement. If you do not specify precedence
precedence-value, the statement is added at the end of the route map and a precedence number is automatically
assigned to it.
precedence-value
Values range from 1 through 65535.
port-channel number
Specifies a port-channel interface.
type-fabric
For an edge destination, do not specify this keyword. Not specifying type-fabric strips the internal encapsulation and
presents the original frame to the end user. You typically include the type-fabric keyword for traffic destined to a
distributor.
Modes
PBF-destination configuration mode
Usage Guidelines
This use-case for this command is under NPB system mode. If the system mode is default, set it to NPB, using the system-
mode command.
The set statement with the smallest precedence number is the preferred path to the destination and is selected if available. The
next set statement becomes active only if the preferred destination is down. If the preferred destination recovers, it again
becomes the active path.
To delete a set interface statement from a destination, perform one of the following actions:
• If you know the precedence number, enter no precedence precedence-value.
• If you do not know the precedence number, type no followed by the full syntax without precedence precedence-value.
Examples
The following example configures "edge" interfaces for a PBF destination.
History
Release version Command history
set local-preference
Specifies a preference value for the autonomous system path.
Syntax
set local-preference number
no set local-preference
Parameters
number
The route distance value range is from 0 through 4294967295.
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command removes the attribute.
Examples
The following example specifies a preference value of 8675309 for the autonomous system path.
History
Release version Command history
set metric
Configures the route metric set clause in a route-map instance.
Syntax
set metric { add | assign | sub } value
Parameters
add
Adds the value to the current route metric.
assign
Replaces the current route metric with this value.
sub
Subtracts the value from the current route metric.
value
Specifies a value. Valid values range from 0 through 4294967295.
none
Removes the current route metric.
Modes
Route-map configuration mode
Examples
The following example adds a value of 256 to the current route metric in a route-map instance.
History
Release version Command history
set metric-type
Sets a variety of metric types for destination routing in a route-map instance.
Syntax
set metric-type [ type-1 | type-2 ]
Parameters
type-1
OSPF external type-1 metric
type-2
OSPF external type-2 metric
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command removes the configuration.
Examples
The following example sets a variety of metric types for destination routing in a route-map instance.
History
Release version Command history
set next-hop-tvf-domain
Specifies a Transparent VLAN Flooding (TVF) domain as the next hop for a Network Packet Broker (NPB) route map to support
replication of traffic to multiple interfaces.
Syntax
[ precedence precedence-value ] set next-hop-tvf-domain tvf-domain-ID [ strip-vlan outer ] [ add-vlan outer vlan-id ]
no precedence precedence-value
Command Default
TVF domain as the route map next hop is not configured.
Parameters
precedence
(Optional) Enables you to assign a precedence number to the set statement. If you do not specify precedence
precedence-value, the statement is added at the end of the route map and a precedence number is automatically
assigned to it.
precedence-value
Values range from 1 through 65535.
tvf-domain-ID
Specifies the ID of the TVF domain. Values are from 1 through 4096.
strip-vlan outer
Removes outer VLAN headers from the egressing packet.
Modes
Route map configuration mode
Usage Guidelines
This command is supported only under NPB system mode. If the system mode is default, set it to NPB, using the system-
mode command.
For load-balanced output when flooding, make sure that the TVF domain includes a port-channel.
The order of the set statements in a route-map is critical: In general, a match followed by a valid set interface or set next-hop-
tvf-domain statement stops further processing. Specifying precedence values determines the order of statement processing. If
you do not specify precedence values, they are automatically assigned as follows: The first set statement is assigned
"precedence 10", the second is assigned "precedence 20", and so forth.
To display policy-map set-statement precedence values, run the show running-config route-map command. The results will
make it easier for you to add additional set statements in the needed order.
To delete a set next-hop-tvf-domain statement from a route map, perform one of the following actions:
• If you know the precedence number, enter no precedence precedence-value.
• If you do not know the precedence number, type no followed by the full syntax without precedence precedence-value.
Examples
The following example configures—in a route map—a specified TVF domain as the next hop.
History
Release version Command history
set origin
Sets a BGP origin code in a route-map instance.
Syntax
set origin [ igp | incomplete ]
Parameters
igp
Local IGP
incomplete
Unknown heritage
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command removes the configuration.
Examples
The following example sets a BGP origin code in a route-map instance.
History
Release version Command history
set tag
Sets the route tag value in a route-map instance.
Syntax
set tag value
Parameters
value
The tag clause value for the route-map. Range is from 0 through 4294967295.
Modes
Privileged EXEC mode
Usage Guidelines
The no form of this command disables this feature.
Examples
The following example sets a route tag value in a route-map instance.
History
Release version Command history
set weight
Sets a BGP weight for the routing table in a route-map instance.
Syntax
set weight number
Parameters
number
Specifies a weight value. Valid values range 0 through 65535.
Modes
Route-map configuration mode
Examples
The following example sets a BGP weight for the routing table in a route-map instance.
History
Release version Command history
sflow collector
Configures the forwarding of sFLow datagrams to collectors.
Syntax
sflow collector { IPv4address | IPv6address } { port_num } [ use-vrf vrf-name ]
Parameters
IPv4address
Specifies an IPv4 address in dotted-decimal format for the collector.
IPv6address
Specifies an IPv6 address for the collector.
port_num
Specifies the port number to use for sendng data to the collector. Range is 1 through 65535. The default is 6343.
use-vrf vrf-name
Specifies a VRF through which to connect to the collector. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
You can only specify up to five sFlow collectors; this includes all VRFs.
Use the no form of this command to reset the specified collector address to a null value.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
Examples
To specify the sFlow collectors for an IPv4 address with the default port on the management VRF:
To specify the sFlow collectors for an IPv4 address with a nondefault port on a user-specified VRF:
To specify the sFlow collectors for an IPv6 address with a nondefault port on the management VRF:
History
Release version Command history
Syntax
sflow enable
no sflow enable
Command Default
sFlow is disabled on the system.
Modes
Global configuration mode
Usage Guidelines
This command is supported on physical ports only.
Examples
To enable sFlow globally:
History
Release version Command history
Syntax
sflow polling-interval interval_value
no sflow polling-interval
Parameters
interval_value
Specifies a value in seconds to set the polling interval. Valid values range from 1 through 65535 seconds.
Command Default
The default is 20.
Modes
Global configuration mode
Usage Guidelines
The interval is the maximum number of seconds between successive samples of counters to be sent to the collector.
Examples
To set the polling interval to 135 seconds:
History
Release version Command history
Syntax
sflow sample-rate samplerate
no sflow sample-rate
Command Default
The global default sampling rate: 2048 packets.
Parameters
samplerate
Specifies the sampling rate value in packets. Valid values range from 2 to 1044480 packets.
Modes
Global configuration mode
Usage Guidelines
Sample-rate is the average number of packets skipped before the sample is taken.
Examples
To change the sampling rate to 4096:
History
Release version Command history
sflow source-interface
Specifies the IPv4 or IPv6 address of either the Ethernet, Virtual Ethernet (ve), or loopback interface as the source of sFlow
packets.
Syntax
sflow source-interface { ethernet slot/port | loopback loopback_num | ve ve_interface }
no sflow source-interface
Command Default
sFlow uses the ethernet port by default.
Parameters
ethernet slot/port
Specifies an Ethernet slot and port. The valid slot value is 0.
loopback loopback_num
Specifies a loopback interface. Valid values range from 1 through 255.
ve ve-interface-number
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 255.
Modes
Global configuration mode
Usage Guidelines
The "no" form of the command is available once the source type has been specified.
Examples
To specify the Ethernet address as the source of sFlow packets:
device# config
device(config)# sflow source-interface ethernet 0/1
History
Release version Command history
shape
Specifies the shaping rate for a port to smooth out the traffic egressing an interface
Syntax
shape speed
Parameters
speed
The speed for the shape rate in Kbps. Range is from 50000 through 100000000 Kbps.
Modes
Policymap configuration mode
Usage Guidelines
This command is allowed only for the egress direction.
This command is mutually exclusive with respect to the scheduler and police commands.
Examples
The following example sets a shape-rate speed of 50000 Kbps.
History
Release version Command history
Syntax
The following statement displays a summary of ACL statuses on the device:
show access-list { ip | ipv6 | mac }
The following statement displays the status of an ACL on all device interfaces—applied to incoming or outgoing traffic:
show access-list { ip | ipv6 | mac } name { in | out }
The following statements display the statuses on an interface of all ACLs applied to incoming or outgoing traffic:
show access-list interface { ethernet slot / port | management port | port-channel index } in
show access-list { ip | ipv6 } name interface { ethernet slot / port | management port | port-channel index } in
The following statement displays the status of all receive ACLs (rACLs) applied to the device:
show access-list global in
The following statement displays details of a specified rACL applied to the device:
show access-list { ip | ipv6 } name global in
Parameters
ip
Specifies the IPv4 Layer 3 network protocol.
ipv6
Specifies the IPv6 Layer 3 network protocol.
mac
Specifies the medium access control (MAC) Layer 2 network protocol.
in
Specifies incoming binding direction.
out
Specifies outgoing binding direction.
name
Specifies the ACL name.
interface
Filters by interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
ve vlan_id
Specifies a virtual Ethernet (VE) interface.
vlan vlan_id
Specifies a VLAN interface.
management port
Specifies a management interface.
global
Specifies Level 3 receive ACLs (rACLs), which are applied at device-level, rather than at interface-level.
Modes
Privileged EXEC mode
Usage Guidelines
You can show information for a specified ACL or only for that ACL on a specified interface. You can also display information for
all ACLs bound to a specified physical interface, port-channel, VLAN or VE.
Command Output
The show access-list command displays the following information:
Examples
The following example displays the names of IPv4 ACLs applied to the device, interfaces to which they are applied, and the
incoming/outgoing direction.
The following example displays all interfaces on which an IPv4 ACL is applied in the outgoing direction.
The following example displays all interfaces on which an IPv6 ACL is applied in the incoming direction.
The following example displays all ACLs applied on a specified interface in the incoming direction.
History
Release version Command history
Syntax
show access-list-log buffer [ interface { ethernet slot / port | port-channel index } ]
Parameters
interface
Filters by interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
Modes
Privileged EXEC mode
Command Output
The show access-list log buffer command displays the following information:
Frames Logged on interface Accumulated number of packets matching ACL rules applied to the interface
Ethernet Src, Dst; Internet proto, Src, Dst Information for matched buffered packets for the specified source and destination addresses
Examples
Sample terminal output:
History
Release version Command history
Syntax
show access-list-log buffer config
Modes
Privileged EXEC mode
Command Output
The show access-list log buffer config command displays the following information:
Examples
The following example displays the configuration of the ACL buffer.
History
Release version Command history
show arp
Displays the Address Resolution Protocol (ARP) entries.
Syntax
show arp { ethernet slot / port | ve ve_id } [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
ve ve_id
Specifies a virtual Ethernet (VE) interface.
ip ip-address
Specifies a next-hop IP address.
dynamic
Displays all the dynamic ARP entries in the ARP table.
static
Displays all the static ARP entries in the ARP table.
summary
Displays a summary of the ARP table.
Modes
Privileged EXEC mode
Command Output
The show arp command displays the following information:
Examples
The following example displays the output of the basic show arp command.
History
Release version Command history
Syntax
show arp access-list [ acl-name ]
Parameters
acl-name
Specifies the name of an ARP ACL defined on the device.
Modes
Privileged EXEC mode
Examples
The following example displays the name and permit statements of an ARP ACL named "list1".
The following example displays the name and permit statements of all ARP ACLs.
History
Release version Command history
show bfd
Displays Bidirectional Forwarding Detection (BFD) information.
Syntax
show bfd
Modes
Privileged EXEC mode
Command Output
The show bfd command displays the following information:
Examples
The following example shows sample output from the show bfd command.
History
Release version Command history
Syntax
show bfd neighbors [ vrf vrfname [ details ] ]
Parameters
vrf vrfname
Specifies the name of a nondefault VRF instance.
details
Displays detailed neighbor information..
Modes
Privileged EXEC mode
Command Output
The show bfd neighbors command displays the following information:
OurAddr Specifies the source IPv4 and IPv6 address of the interface on which this BFD session is
running.
NeighAddr The IPv4 or IPv6 address of the remote neighbor.
State The current state of the BFD session:
• UP
• DOWN
• A.DOWN - The administrative down state.
• INIT - The initialization state.
• UNKNOWN - The current state is unknown.
Int Specifies the interface on which the BFD session is running.
Examples
The following example shows sample output from the show bfd neighbors command.
The following example shows sample output from the show bfd neighbors command when the vrf keyword is used.
The following example shows sample output from the show bfd neighbors command when the vrf and details keywords are
used.
History
Release version Command history
Syntax
show bfd neighbors application { bgp | ospf | ospf6 | static-ip | tunnel [ details ] }
Parameters
bgp
Specifies Border Gateway Protocol (BGP) sessions.
ospf
Specifies Open Shortest Path First (OSPF) sessions.
ospf6
Specifies Open Shortest Path First version 3 (OSPFv3) sessions.
static-ip
Specifies IP static route sessions.
tunnel
Specifies a tunnel interface.
details
Displays detailed neighbor session information.
Modes
Privileged EXEC mode
Command Output
The show bfd neighbors application command displays the following information:
OurAddr Specifies the source IP address of the interface on which this BFD session is running.
NeighAddr The IPv4 or IPv6 address of the remote neighbor.
State The current state of the BFD session:
• UP
• DOWN
• A.DOWN - The administrative down state.
• INIT - The initialization state.
• UNKNOWN - The current state is unknown.
Int Specifies the interface on which the BFD session is running.
Examples
The following example shows sample output from the show bfd neighbors application command when the ospf keyword is
used.
The following example shows sample output from the show bfd neighbors application command when the ospf and details
keywords are used.
History
Release version Command history
Syntax
show bfd neighbors dest-ip { ip-address | ipv6-address } [ details ]
show bfd neighbors dest-ip { ip-address | ipv6-address } interface { ethernet slot/port | loopback number | ve ve-interface-
number }
Parameters
ip-address
Specifies the IP address of the destination device.
ipv6-address
Specifies the IPv6 address of the destination device.
details
Displays detailed neighbor information about the destination device.
interface
Displays BFD neighbor interface information.
ethernet slot/port
Specifies an Ethernet slot and port. The slot number specified must be 0 if the switch does not contain slots.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
ve ve-interface-number
Specifies a virtual Ethernet (VE) interface.
Modes
Privileged EXEC mode
Command Output
The show bfd neighbors dest-ip command displays the following information:
OurAddr Specifies the source IP address of the interface on which this BFD session is running.
NeighAddr The IPv4 or IPv6 address of the remote neighbor.
State The current state of the BFD session:
• UP
• DOWN
• A.DOWN - The administrative down state.
• INIT - The initialization state.
• UNKNOWN - The current state is unknown.
Examples
The following example shows sample output from the show bfd neighbors dest-ip command.
The following example shows sample output from the show bfd neighbors dest-ip command when the details keyword is
used.
History
Release version Command history
Syntax
show bfd neighbors details
Modes
User EXEC mode
Command Output
The show bfd neighbors details command displays the following information:
OurAddr Specifies the source IPv4 and IPv6 address of the interface on which this BFD session is
running.
NeighAddr Specifies the IPv4 or IPv6 address of the remote neighbor.
State Specifies the current state of the BFD session:
• UP
• DOWN
• A.DOWN - The administrative down state.
• INIT - The initialization state.
• UNKNOWN - The current state is unknown.
Int Specifies the interface on which the BFD session is running.
Local:
State State of the local device.
Diag Value of the diagnostic field in the BFD control message as used by the device in the last
message sent.
Demand mode Value of the demand in the BFD control message as used by the device in the last message
received.
Poll Value of the poll in the BFD control message as used by the device in the last message sent or
received.
Received
State State of the remote device.
Diag Value of the diagnostic field in the BFD control message as used by the device in the last
message received.
Demand mode Value of the demand in the BFD control message as used by the device in the last message
received.
Poll Value of the poll in the BFD control message as used by the device in the last message
received.
Final Value of the final bit in the BFD control message as used by the device in the last message
received.
Local The local device
Examples
The following example shows sample output from the show bfd neighbors details command.
History
Release version Command history
Syntax
show bfd neighbors interface { ethernet slot/port | loopback number | tunnel number | ve ve-interface-number } [ details ]
Parameters
ethernet slot/port
Specifies an Ethernet slot and port. The slot number specified must be 0 if the switch does not contain slots.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
tunnel number
Specifies a tunnel interface. Valid values range from 1 through 100000.
ve ve-interface-number
Specifies a virtual Ethernet (VE) interface.
details
Specifies detailed information.
Modes
Privileged EXEC mode
Command Output
The show bfd neighbors interface command displays the following information:
OurAddr Specifies the source IP address of the interface on which this BFD session is running.
NeighAddr The IPv4 or IPv6 address of the remote neighbor.
State The current state of the BFD session:
• UP
• DOWN
• A.DOWN - The administrative down state.
• INIT - The initialization state.
• UNKNOWN - The current state is unknown.
Int Specifies the interface on which the BFD session is running.
Examples
The following example shows sample output from the show bfd neighbors interface command when the ve and details
keywords are used.
History
Release version Command history
Syntax
show bgp evpn neighbors [ ip-addr | ipv6-addr | routes-summary ]
Parameters
ip-addr
Specifies the IPv4 address of a neighbor.
ipv6-addr
Specifies the IPv6 address of a neighbor.
routes-summary
Displays routes received, routes accepted, number of routes advertised by peer, and so on.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to view configuration information and statistics for BGP EVPN neighbors of the device. Output shows all
configured parameters for the neighbors.
Examples
The following example shows sample output from the show bgp evpn neighbors command.
History
Release version Command history
Syntax
show bgp evpn neighbors { ip address | ipv6 address } advertised-routes [ detail [ type ] | type ]
Parameters
ip-addr
Specifies the IPv4 address of a neighbor.
ipv6-addr
Specifies the IPv6 address of a neighbor.
detail type
Specifies detailed information be given for the designated route type.
type
Specifies the type of route.
arp
Specifies Address Resolution Protocol (ARP) routes.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segment (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
nd
Specifies neighbor discovery (ND) routes.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn neighbors advertised-routes detail command.
History
Release version Command history
Syntax
show bgp evpn neighbors { ip address | ipv6 address } routes [ type ] | best [ type ] | detail [ type ] | not-installed-best [ type ] |
unreachable [ type ] ]
Parameters
type
Specifies the type of route.
arp
Specifies Address Resolution Protocol (ARP) routes.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
mac
Specifies MAC routes.
nd
Specifies neighbor discovery (ND) routes.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn neighbors routes best command.
The following example shows output for the show bgp evpn neighbors routes best command when the nd keyword is used.
History
Release version Command history
Syntax
show bgp evpn routes
Modes
Privileged EXEC mode
Examples
The following example shows routes in the VPN table.
History
Release version Command history
Syntax
show bgp evpn routes type igmp-join-sync
Parameters
brief
Displays summary information.
detail
Displays detailed information.
Modes
Privileged EXEC mode
Examples
The following example shows routes to join IGMP sync:
History
Release version Command history
Syntax
show bgp evpn routes type igmp-leave-sync
Parameters
brief
Displays summary information.
detail
Displays detailed information.
Modes
Privileged EXEC mode
Examples
The following example shows routes to leave IGMP sync:
History
Release version Command history
Syntax
show bgp evpn summary
Modes
Privileged EXEC mode
Examples
The following example displays summarized information for EVPN neighbors.
History
Release version Command history
show bridge-domain
Displays information about the bridge domains.
Syntax
show bridge-domain [id [ logical-interface ] ]
Parameters
id
Specifies a unique numeric bridge-domain identifier. On SLX 9140, the range is from 1 through 4096. On SLX
9240, the range is from 1 through 3566.
logical-interface
Displays the operational information for logical interfaces configured under the bridge domain.
id
Specifies a logical interface instance ID.
brief
Causes the display of summary bridge-domain information.
p2mp
Causes the display of multipoint service information.
p2p
Causes the display of multi-point cross-connect service information.
vc-peer
Causes the display of summary virtual connection (VC) peer information for the bridge domain.
Modes
Privileged EXEC mode.
Usage Guidelines
To display information about all bridge domains, specify the bridge-domain option without a bridge-domain identifier.
To display information about all logical interfaces configured under a specific bridge domain, specify the logical-interface
option without a logical-interface identifier.
Examples
The following example shows the information displayed by the show bridge-domain command.
The following example displays the logical interface information for the bridge domain.
The following example shows the information displayed by the show bridge-domain brief command.
History
Release version Command history
show capabilities
Displays whether a variety of network services are enabled ("true") or not ("false").
Syntax
show capabilities
Modes
Privileged EXEC mode
Usage Guidelines
?
Examples
The following example displays the status of all network services:
History
Release version Command history
Syntax
show capture packet config
Modes
Privileged EXEC mode
Examples
This example displays the Online Packet Capture configuration.
History
Release version Command history
Syntax
show capture packet interface ethernet slot / port
Parameters
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Examples
This example displays information about the captured frames.
History
Release version Command history
Syntax
show cee maps [ default ]
Parameters
default
The name of the only CEE map on the device.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example displays the CEE map.
History
Release version Command history
Syntax
show cert-util ldapca
Modes
Privileged EXEC mode
Examples
To display the LDAP certificate on the device:
History
Release version Command history
Syntax
show cert-util sshkey user user_id
Parameters
user user_id
The user ID to display.
Modes
Privileged EXEC mode
Examples
A typical output of this command:
History
Release version Command history
Syntax
show cert-util syslogca
Modes
Privileged EXEC mode
Examples
To display the syslog Certification Authority (CA) certificate on the device:
syslog CA
History
Release version Command history
show chassis
Displays the status for components in the chassis.
Syntax
show chassis
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local switch and is supported only on the local switch. The output of this command depends
on the platforms on which it is executed.
Pagination is not supported with this command. Use the "more" parameter to display the output one page at a time.
Examples
The following example displays chassis information on a SLX 9140.
FAN Unit: 1
Time Awake: 4 days
FAN Unit: 2
Time Awake: 4 days
FAN Unit: 3
Time Awake: 4 days
FAN Unit: 4
Time Awake: 4 days
FAN Unit: 5
Time Awake: 4 days
FAN Unit: 6
Time Awake: 4 days
CHASSIS/WWN Unit: 1
Power Consume Factor: 0
Factory Part Num: 84-1002952-01
Factory Serial Num: EXH3330M00M
Manufacture: Day: 5 Month: 8 Year: 2016
Update: Day: 24 Month: 7 Year: 2017
Time Alive: 262 days
Time Awake: 4 days
History
Release version Command history
show cipherset
Displays the current cipherset status for LDAP and SSH.
Syntax
show cipherset
Modes
Privileged EXEC mode
Examples
To display cipherset status on the device:
History
Release version Command history
show cli
Displays all the current CLI settings.
Syntax
show cli
Modes
Privileged EXEC mode
Examples
Typical command output display.
History
Release version Command history
show clock
Returns the local time, date, and time zone.
Syntax
show clock
Command Default
The local clock is used.
Modes
Privileged EXEC mode
Usage Guidelines
The command displays the current time for the device.
Examples
The following example shows the clock time.
History
Release version Command history
show cluster
Displays the MCT cluster information including client information.
Syntax
show cluster [ cluster-ID [ client client-ID] ]
Parameters
cluster-ID
Specifies the cluster ID to display its configuration, peer, and client information.
client client-ID
Displays the specified client ID information.
Modes
Privileged EXEC mode
Command Output
The show cluster command displays the following information:
When you display a specified client ID, the following information is displayed.
Examples
The following example shows the information of the cluster on the SLX-OS device.
Cluster MCT1 1
==============
Cluster State: Deploy
Client Isolation Mode: Strict
DF Hold Time: 3
Configured Member Vlan Range: 5, 100-1000
Active Member Vlan Range: 5,200,500-600, 800
Cluster Control Vlan: 4090
No. of Peers: 1
No. of Clients: 3
Peer Info:
----------
Peer IP: 10.10.10.20, State: Up
Client Info:
------------
Name Id ESI Interface Local/Remote State
access1 100 00.a1.b2.c3.d4.e5.f6.89.00 Eth 0/3 Up/UP
access2 200 00.11.22.33.44.55.66.77.88 po-chan-2 Dep/UnDep
access3 300 00.24.46.0e.cd.ab.66.16.00 Eth 0/8 Up/Down
History
Release version Command history
Syntax
show cluster management [ detail ]
Parameters
detail
Displays detailed information.
Modes
Privileged EXEC mode
Examples
The following example displays basic information regarding the IP-based management cluster.
History
Release version Command history
Syntax
show copy-support status
Modes
Privileged EXEC mode
Usage Guidelines
The status is indicated by the percentage of completion. NORMAL indicates process is proceeding or completed without errors.
FAULTY indicates a faulty blade.
Examples
To display the support upload status:
History
Release version Command history
show cpu-interface
Displays information about the CPU Ethernet interface.
Syntax
show cpu-interface { statistics interface backplane }
Modes
Privileged EXEC mode
Examples
To display information about the CPU Ethernet interface:
History
Release version Command history
show crypto ca
Displays cryptographic trustpoint configuration information.
Syntax
show crypto ca { trustpoint | certificates }
Parameters
trustpoint
Causes the display of trustpoint configuration information.
certificates
Causes the display of certificate information. Both Certificate Authority (CA) certificate and identity certificate
information is displayed.
Modes
Privileged EXEC mode
Usage Guidelines
Any keypair associated with a trustpoint is included in the trustpoint configuration information displayed by specifying the
trustpoint parameter.
Command Output
The show crypto ca command displays the following information:
Examples
The following example displays trustpoint configuration information.
Trustpoint: t1
CA certificate:
SHA1 Fingerprint=B7:5B:DB:9B:24:69:40:39:36:66:4D:59:2C:69:83:8E:93:CA:23:0C
Subject: C=US, ST=CA, L=SJ, O=BRC, OU=SFI, CN=10:00:00:27:F8:87:70:29
Issuer: C=US, ST=CA, L=SJ, O=BR, OU=SF, CN=SOUND/emailAddress=sravi
Not Before: Oct 6 23:44:27 2016 GMT
Not After : Oct 6 23:44:27 2017 GMT
purposes: sslserver
CA certificate:
SHA1 Fingerprint=76:5B:D4:2C:CB:54:FE:6B:C5:E0:E3:FD:11:B0:88:70:80:12:C6:63
Subject: C=US, ST=CA, L=SJ, O=BR, OU=SF, CN=SOUND/emailAddress=sravi
Issuer: C=US, ST=CA, L=SJ, O=BR, OU=SF, CN=SOUND/emailAddress=sravi
Not Before: Sep 19 20:56:49 2016 GMT
Not After : Oct 19 20:56:49 2016 GMT
purposes: sslserver
History
Release version Command history
Syntax
show crypto key mypubkey
Parameters
mypubkey
Causes the display of public key configuration information.
Modes
Privileged EXEC mode
Command Output
The show crypto key command displays the following information:
key type Cryptographic key type. Supported key types include RSA, DSA and ECDSA.
key label Cryptographic key label.
key size Cryptographic key size.
Examples
The following example displays public key configuration information.
History
Release version Command history
Syntax
show debug arp packet [ buffer ]
Parameters
buffer
Displays ARP packets saved in the relevant buffer.
Modes
Privileged EXEC mode
Command Output
The show debug arp packet command displays the following information:
Examples
The following example is a typical output of the show debug arp packet buffer option.
History
Release version Command history
Syntax
show debug dhcp packet
Modes
Privileged EXEC mode
Examples
device# show debug dhcp packet
% DHCP protocol RCV debug is enabled on interface Eth 0/18
% DHCP protocol TX debug is enabled on interface Eth 0/18
PCAP Buffer Configuration for Vrf ID 0: Buffer Type is Linear and BufferSize is 2056
History
Release version Command history
Syntax
show debug dhcp packet buffer
Modes
Privileged EXEC mode
Examples
The following command displays buffer content for all VRF IDs.
Seconds Elapsed : 0
BootP Flags : 8000
Client IP : 0.0.0.0
Your (client) IP : 10.10.10.30
Next Server IP : 20.20.20.20
Relay Agent IP : 10.10.10.10
Client MAC Add : 00:10:94:00:00:01
Server Host Name : Not Given
Boot File Name : Not Given
*********************************************
History
Release version Command history
Syntax
show debug ip bgp all
Modes
Privileged EXEC mode
Examples
device# show debug ip bgp all
History
Release version Command history
Syntax
show debug ip igmp
Modes
Privileged EXEC mode
Examples
The following displays example output
---------------------------------------
errors : off
group : off
packets : off
query : off
report : off
direction : none
vlan : none
l2_port : none
History
Release version Command history
Syntax
show debug ipv6 mld
Modes
Privileged EXEC mode
Examples
The following example displays the output of the show debug ipv6 mld command.
History
Release version Command history
Syntax
show debug ipv6 packet [ buffer [ all | interface [ ethernet slot/port| ve vlan_id ] [ rx | tx ]
Parameters
buffer
Specifies IPv6 packets.
all
Specifies all interfaces.
interface
Specifies an interface.
ethernet
Specifies an Ethernet port.
slot
Specifies a valid slot number. This must be 0 for devices that do not support line cards.
port
Specifies a valid port number.
vevlan_id
Specifies a virtual Ethernet interface.
Command Default
None
Modes
Privileged EXEC mode
Examples
To display the current PCAP configuration on the switch:
History
Release version Command history
Syntax
show debug lacp
Modes
Privileged EXEC mode
History
Release version Command history
Syntax
show debug lldp
Modes
Privileged EXEC mode
Examples
To display the status of LLDP debugging on the switch:
History
Release version Command history
Syntax
show debug spanning-tree
Modes
Privileged EXEC mode
History
Release version Command history
Syntax
show debug vrrp
Modes
Privileged EXEC mode
Usage Guidelines
This command is for VRRP and VRRP-E. You can modify or redirect the displayed information by using the default Linux
tokens (|, >).
Examples
If you run this command and the debug parameter has already been set to debug all VRRP events, the following is displayed:
History
Release version Command history
Syntax
show defaults threshold sfp type sfp-type
Parameters
sfp-type
The following SFP types are supported:
1GCOP
— 1G SFP Copper
1GLR
— 1G SFP LR
1GSR
— 1G SFP SR
10GER
— 10G SFP+ ER
10GLR
— 10G SFP+ LR
10GSR
— 10G SFP+ SR
10GUSR
— 10G SFP+ USR
10GZR
— 10G SFP+ ZR
25GSR
— 25G SFP+ SR
40GESR
— 40G QSFP+ eSR4 INT
40GLR
— 40G QSFP+ LR4
40GSR
— 40G QSFP+ SR4
40GSRINT
— 40G QSFP+ SR4 INT
100GCLR
— 100G QSFP28 CLR4
100GCWDM
— 100G QSFP28 CWDM4
100GLR
— 100G QSFP28 LR4
100GLRLT
— 100G QSFP28 LR4 Lite
100GPSM
— 100G QSFP28 PSM4
100GSR
— 100G QSFP28 SR4
Modes
Privileged EXEC mode
Usage Guidelines
You can modify these thresholds with the threshold-monitor sfp command.
Examples
The following example displays the default sfp thresholds for 1G SFP Copper.
History
Release version Command history
Syntax
show diag burninerrshow
Modes
Offline diagnostics mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
The log file is updated immediately by the system verification process when the diag systemverification command is executed.
Examples
The following example displays the output of this command.
History
Release version Command history
Syntax
show diag burninstatus
Modes
Offline diagnostics mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
The log file is updated immediately by the system verification process when the diag systemverification command is executed.
Examples
The follow example displays the output of this command.
<---output truncated--->
History
Release version Command history
Syntax
show diag revision
Modes
Offline diagnostics mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
Examples
The following example displays output from this command.
History
Release version Command history
Syntax
show diag setcycle
Modes
Offline diagnostics mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
Examples
The following example displays the output of this command.
History
Release version Command history
Syntax
show diag sysinfo
Modes
Offline diagnostics mode
Usage Guidelines
Refer to the "Diagnostic Commands" chapter in the Extreme SLX-OS Management Configuration Guide.
Examples
The following example displays system hardware information for a SLX 9240.
The following example displays system hardware information for a SLX 9140.
History
Release version Command history
show dot1x
Displays 802.1X-related information.
Syntax
show dot1x [ all ]
Parameters
all
Displays detailed 802.1X-related information for all ports on the device.
interface
Displays 802.1X-related status and configuration information for an interface.
ethernet slot/port
Specifies an Ethernet interface in slot number/port number format. When the device does not contain slots,
the slot number must be 0 .
diagnostics
Displays 802.1X-related diagnostics information for the authenticator associated with a port.
session-info
Displays all 802.1X-related statistical information for an established session.
statistics
Displays the 802.1X-related statistics of a specified interface.
Modes
Privileged EXEC mode
Command Output
The show dot1x command displays the following information:
802.1X Port-Based Authentication Configuration status (Enabled or Disabled) for 802.1x port based authentication.
PAE Capability Port Access Entity (PAE) role for the device. This is always "Authenticator Only".
Protocol Version Version of the 802.1X protocol in use on the device.
Auth Server Authentication server type; for example, RADIUS.
Readiness test timeout 802.1x readiness test timeout. The range is from 1 through 65535 seconds.
RADIUS Configuration
Position Position of the configured RADIUS server.
Server Address IP address of the RADIUS server.
Examples
The following example shows the overall state of 802.1X authentication on the system.
The following example shows detailed 802.1X authentication information for all of the ports.
RADIUS Configuration
--------------------
Position: 1
Server Address: 10.20.106.144
Port: 1812
Secret: testing123
Retry Interval: 4 seconds
Position: 2
Server Address: 10.20.106.189
Port: 1812
Secret: testing123
Retry Interval: 4 seconds
The following example shows information for all clients on the port.
The following example shows all diagnostics information for the authenticator associated with a port.
History
Release version Command history
Syntax
show environment fan
Modes
Privileged EXEC mode
Command Output
The show environment fan command displays the following information:
Examples
The following example displays fan status information:
History
Release version Command history
Syntax
show environment history
Modes
Privileged EXEC mode
Usage Guidelines
The history log records insertion and removal events for field-replaceable units (FRUs), such as blades, power supplies, fans,
and world wide name (WWN) or chassis ID (CID) cards. The type of FRU supported depends on the hardware platform.
Command Output
The show environment history command displays the following information:
Object type On standalone platforms: FAN, POWER SUPPLY, WWN (WWN card), or UNKNOWN.
Object number Displays the slot number for blades. Displays the unit number for all other object types.
Event type Displays Inserted, Removed, or Invalid.
Time of the event Displays the date in the following format: Day Month dd hh:mm:ss yyyy.
Factory Part Number Displays the part number (xx-yyyyyyy-zz) or Not available.
Factory Serial Number Displays the FRU serial number (xxxxxxxxxxxx) or Not available.
Examples
The following example displays the FRU history on a device.
Records: 8
History
Release version Command history
Syntax
show environment power
Modes
Privileged EXEC mode
Command Output
The show environment power command displays the following information:
Examples
The following example displays the power supply status.
History
Release version Command history
Syntax
show environment sensor
Modes
Privileged EXEC mode
Usage Guidelines
The command output displays the current temperature, fan, and power supply status readings from sensors located on the
switch. For an explanation of power supply status values, refer to the show environment power command.
Examples
The following example displays sensor readings on the device:
History
Release version Command history
Syntax
show environment temp
Modes
Privileged EXEC mode
Command Output
The show environment temp command displays the following information:
Examples
The following example displays temperature readings on a the device.
History
Release version Command history
Syntax
show event-handler activations
Modes
Privileged EXEC mode
Command Output
The show event-handler activations command displays the following information:
Examples
The following example displays event-handler operational data.
Event-handler : evh1
Last Trigger Activation Time: 2015-04-30 17:28:12
Total Trigger Activations: 25
Last Action Completion Time: 2015-04-30 17:28:57
Last Action Completion Status: Exit Code = 0
Total Action Completions: 25
Event-handler : evh2
Last Trigger Activation Time: 2015-04-28 22:02:51
Total Trigger Activations: 8
Last Action Completion Time: 2015-04-28 22:02:58
Last Action Completion Status: Exit Code = 0
Total Action Completions: 8
History
Release version Command history
show file
Displays the contents of a file in the local flash memory.
Syntax
show file filename
Parameters
filename
The name of the file to be displayed.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
Examples
The following example displays the contents of a file in the flash memory.
protocol lldp
!!
logging auditlog class CONFIGURATION
logging auditlog class FIRMWARE
logging auditlog class SECURITY
!
end
History
Release version Command history
show firmwaredownloadhistory
Displays the firmware download history for the device.
Syntax
show firmwaredownloadhistory
Modes
Privileged EXEC mode
Usage Guidelines
The log records the date and time of the firmware download, the device name, slot number (0), process ID, and firmware
version.
Examples
The following example displays the firmware download history.
History
Release version Command history
show firmwaredownloadstatus
Displays the firmware download activity log.
Syntax
show firmwaredownloadstatus [ brief ] [ summary ]
Parameters
brief
Displays only the last entry of the firmware download event log.
summary
Displays a high-level summary of the firmware download status.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display an event log that records the progress and status of events that occur during a firmware
download. The event log is created by the firmware download command and is retained until you issue another firmware
download command. A time stamp is associated with each event.
The output of show firmwaredownloadstatus and show firmwaredownloadstatus brief are equivalent.
Examples
The following example displays the firmware download event log.
The following example displays a high-level summary of the firmware download status.
History
Release version Command history
Syntax
show hardware profile [ current ]
show hardware profile route-table { default | ipv4-max-arp | ipv6-max-nd | multicast | multicast-snoop | user-defined }
( SLX 9140 ) show hardware profile tcam { default | l2-acl-l3-iacl | l2-iacl-l3-acl | l2-l3-iacl-l2-iqos | l2-l3-iqos-l2-eacl | l2-
l3-iqos-l2-iacl | l2-l3-iqos-l3-eacl | l2-l3-iqos-l3-iacl | user-defined }
( SLX 9240 ) show hardware profile tcam { default | l2-l3-iacl | l2-l3-iqos | l3-acl | l3-iacl-l2-eacl | l3-iacl-l2-iqos | l3-iqos-
l2-iacl | user-defined }
Parameters
current
Displays details of the current active profile.
ipv6-lookup
(NPB system-mode) Displays details of the IPv6 address lookup-mode.
default
Displays details of the default IPv6 address lookup-mode.
network-id
Displays details of the network-id IPv6 address lookup-mode.
overlay-visibility
(Default system-mode) Displays overlay-visibility profile information.
default
Matches on outer source IP and destination IP.
endpoint
Matches on outer source IP or destination IP.
endpoint-vni
Matches on outer source IP and VNI or destination IP and VNI.
tunnel-vni
Matches on outer source IP, destination IP, and VNI.
vni
Matches on VNI only.
route-table
(Default system-mode) Specifies hardware resources for route profiles.
default
Specifies IPv4/IPv6 resources for dual-stack operations.
ipv4-max-arp
Specifies resources for the maximum number of IPv4 ARP entries.
ipv6-max-nd
Specifies resources for the maximum number of IPv6 Neighbor Discovery entries.
multicast
Specifies resources for IP unicast dual-stack and IPv4 mulitcast.
multicast-snoop
Specifies resources for IP unicast dual-stack and multicast snooping.
user-defined
Specifies resources for a user-defined profile.
default
Specifies resources with basic support for all applications.
l2-acl-l3-iacl
Specifies resources for ingress and egress Layer 2 ACLs; and ingress IPv4 and IPv6 ACLs.
l2-iacl-l3-acl
Specifies resources for ingress Layer 2 ACLs; and ingress and egress IPv4 and IPv6 ACLs.
l2-l3-iacl-l2-iqos
Specifies resources for ingress Layer 2, IPv4, and IPv6 ACLs; and ingress Layer 2 QoS.
l2-l3-iqos-l2-eacl
Specifies resources for ingress Layer 2, IPv4, and IPv6 QoS; and egress Layer 2 ACLs.
l2-l3-iqos-l2-iacl
Specifies resources for ingress Layer 2, IPv4, and IPv6 QoS; and ingress Layer 2 ACLs.
l2-l3-iqos-l3-eacl
Specifies resources for ingress Layer 2, IPv4, and IPv6 QoS; and egress IPv4 and IPv6 ACLs.
l2-l3-iqos-l3-iacl
Specifies resources for ingress Layer 2, IPv4, and IPv6 QoS; and ingress IPv4 and IPv6 ACLs.
user-defined
Specifies resources for a user-defined TCAM profile.
default
Specifies resources with basic support for all applications.
l2-l3-iacl
Specifies resources for ingress Layer 2, IPv4, and IPv6 ACLs.
l2-l3-iqos
Specifies resources for ingress Layer 2, IPv4, and IPv6 QoS.
l3-acl
Specifies resources for ingress and egress IPv4 and IPv6 ACLs.
l3-iacl-l2-eacl
Specifies resources for egress Layer 2 ACLs; and ingress IPv4 and IPv6 ACLs.
l3-iacl-l2-iqos
Specifies resources for ingress Layer 2 QoS; and ingress IPv4 and IPv6 ACLs.
l3-iqos-l2-iacl
Specifies resources for ingress Layer 2 ACLs; and ingress IPv4 and IPv6 QoS.
user-defined
(Default system-mode only) Specifies resources for a user-defined TCAM profile.
Modes
Privileged EXEC mode
Usage Guidelines
Local hardware profile information can be obtained by means of the current keyword.
Route-table profiles are supported only in default system-mode, not in network packet broker (NPB) mode.
In NPB mode, the only TCAM profile supported is the default TCAM profile.
IPv6 address profiles are supported only NPB mode. For implementation details, refer to the profile ipv6-lookup topic.
Examples
(Default system-mode) The following example displays details of the current active profile.
The following example displays specific route-table information about resource allocation, facilitating management.
History
Release version Command history
Syntax
show hardware profile overlay-visibility { default | endpoint | endpoint-vni| tunnel-vni| vni}
Parameters
default
Displays a match on outer source IP and destination IP addresses.
endpoint
Displays a match on outer source IP or destination IP addresses.
endpoint-vni
Displays a match on outer source IP address and virtual network identifier (VNI), or destination IP address and VNI.
tunnel-vni
Displays a match on outer source IP address, destination IP address, and VNI.
vni
Displays a match on VNI only.
Modes
Privileged EXEC mode
Usage Guidelines
The options above are configured by the profile overlay-visibility command.
Examples
The following example displays a match on VNI only.
History
Release version Command history
show history
Displays the history of commands executed on the device during the current session.
Syntax
show history [ number ]
Parameters
number
Specifies the number of commands to display. Values range from 1 through 1000.
Modes
Privileged EXEC mode
Usage Guidelines
If you enter this command without specifying a number, up to 1000 commands are displayed.
Examples
The following command displays the four last commands entered.
History
Release version Command history
Syntax
show http server status
Modes
Privileged EXEC mode
Command Output
The show http server status command displays the following information:
Examples
The following example displays HTTP and HTTPS server status information.
History
Release version Command history
show inner-gtp-https
Displays a list of all interfaces on which the dropping of GPRS Tunneling Protocol (GTP) frames that encapsulate HTTPs
packets is enabled.
Syntax
show inner-gtp-https
Modes
Privileged EXEC mode
Examples
The following example indicates that this feature is enabled on an Ethernet interface.
History
Release version Command history
show interface
Displays the detailed interface configuration and capabilities of all interfaces or for a specified interface.
Syntax
show interface [ description ]
Parameters
description
For all device interfaces, displays a summary that includes the Description field.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel number. Depending on the platform, valid values range from 1 through 1024.
switchport
Specifies Layer 2 interfaces.
loopback number
Specifies a loopback interface.
trunk
Displays VLANs on the trunk.
Modes
Privileged EXEC mode
Command Output
The show interface ethernet command displays the following information:
Ethernet slot / port Displays the port state. The states are "admin down, line protocol is down (admin down)" or "up,
line protocol is up (connected)".
Hardware Displays the MAC address of the Ethernet interface.
Pluggable media Displays "present" or "not present".
Loopback Displays the loopback number and state and the line protocol state. The states are "Loopback
nn is up", "Loopback nn is admin down, line protocol is down (admin down). "
Hardware Displays "loopback".
Pluggable media Displays "present" or "not present".
Interface index Displays the interface index.
IP MTU Displays the maximum transmission unit (MTU), in bytes.
LineSpeed Actual Displays the actual line speed in Mb or "Nil".
LineSpeed Configured Displays "Auto" or a value in Mb.
Last clearing of show interface counters In days, hours, and minutes, displays how much time elapsed since the last counter clear.
Queueing strategy Displays "FIFO".
Primary Internet Address Displays the primary Internet address.
FEC Mode Displays the forward error correction (FEC) mode: "RS-FEC", "FC-FEC", "Auto-Negotiation" or
"disabled".
Examples
The following example displays detailed information for the Ethernet interface 0/1.
The following example displays a list of VLANs allowed on the trunk, per interface.
(Output truncated)
History
Release version Command history
Syntax
show interface port channel { number }
Parameters
number
Port-channel number. Range is from 1 through 1024.
Modes
Privileged EXEC mode
Examples
The following example displays the status of a port-channel.
History
Release version Command history
Syntax
show interface stats brief
show interface stats detail [ interface { ethernet slot / port | port-channel index } ]
Parameters
interface
Specifies what type of interface to display.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel number. Depending on the platform, valid values range from 1 through 1024.
Modes
Privileged EXEC mode
Examples
The following example displays detailed statistics for a specified Ethernet interface.
History
Release version Command history
Syntax
show interface status
Modes
Privileged EXEC mode
Command Output
The show interface status command displays the following information:
Examples
The following example displays the status of all device interfaces.
History
Release version Command history
show inventory
Displays the hardware inventory of the device.
Syntax
show inventory [ chassis | fan | module | powerSupply ]
Parameters
chassis
Displays information about the chassis.
fan
Displays information about the fan.
module
Displays information about the module.
powerSupply
Displays information about the power supply.
Modes
Privileged EXEC mode
Examples
The following is an example of typical command output.
History
Release version Command history
show ip anycast-gateway
Displays details for IPv4 anycast gateway for all or specified virtual Ethernet (VE) interfaces or VRF instances.
Syntax
show ip anycast-gateway [ interface VE | vrf VRF-name]
Parameters
interface VE
Specifies a VE interface.
vrf VRF-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
To display details for IPv4 anycast gateway for all VE interfaces:
History
Release version Command history
Syntax
show ip arp inspection [ vlan vlan-range ]
Parameters
vlan vlan-range
Specifies a VLAN, multiple VLANs (separated by commas with no spaces), a range of VLANs, or a combination of
specified VLANs and ranges of VLANs. Valid values are from 1 through 4090.
Modes
Privileged EXEC mode
Command Output
The show ip arp inspection command displays the following information:
Examples
The following example displays DAI information for all VLANs.
The following example displays DAI information for specified VLANs and a range of VLANs.
History
Release version Command history
Syntax
show ip arp inspection interfaces [ ethernet slot / port | port-channel index ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
Modes
Privileged EXEC mode
Usage Guidelines
On VLANs enabled for Dynamic ARP Inspection (DAI), interfaces not listed in the command output are untrusted.
Command Output
The show ip arp inspection interfaces command displays the following information:
Interface Displays a prefix specifying the interface type, followed by the interface identifier.
Trust State Displays "Trusted".
Examples
The following example displays all trusted interfaces.
The following example displays the trust state of Ethernet interface 0/1.
History
Release version Command history
Syntax
show ip arp inspection statistics [ vlan vlan-range ]
Parameters
vlan vlan-range
Specifies a VLAN, multiple VLANs (separated by commas with no spaces), a range of VLANs, or a combination of
specified VLANs and ranges of VLANs. Valid values are 1 through 4090.
Modes
Privileged EXEC mode
Command Output
The show ip arp inspection statistics command displays the following information:
Examples
The following example displays statistics for VLAN 400.
History
Release version Command history
Syntax
show ip arp suppression-cache [ summary ]
Parameters
summary
Specifies summary format.
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the beginning and
ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the beginning and ending
integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for example:
1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Command Output
The show ip arp suppression-cache command displays the following information:
Examples
The following example displays the results of the basic form of this command.
History
Release version Command history
Syntax
show ip arp suppression-statistics
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the beginning and
ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the beginning and ending
integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for example:
1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Command Output
The show ip arp suppression-statistics command displays the following information:
Examples
The following example displays the results of the basic form of this command.
History
Release version Command history
Syntax
show ip arp suppression-status
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the beginning and
ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the beginning and ending
integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for example:
1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Command Output
The show ip arp suppression-status command displays the following information:
Examples
The following example displays the results of the basic form of this command.
History
Release version Command history
show ip as-path-list
Displays the status of AS-path access control lists (ACLs).
Syntax
show ip as-path-list list_name
Parameters
list_name
Specifies the name of an Autonomous System (AS) ACL.
Modes
Privileged EXEC mode
Examples
The following example displays AS-path ACL status for a specified list.
History
Release version Command history
show ip bgp
Displays BGP4 route information.
Syntax
show ip bgp
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation, with optional mask.
/prefix
IPv4 mask length in CIDR notation.
longer-prefixes
Filters on prefixes equal to or greater than that specified by prefix.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays sample output from the show ip bgp command.
History
Release version Command history
Syntax
show ip bgp attribute-entries [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
The route-attribute entries table lists the sets of BGP4 attributes that are stored in device memory. Each set of attributes is
unique and can be associated with one or more routes. In fact, the device typically has fewer attribute entries than routes.
Examples
The following example show sample output for the show ip bgp attribute-entries command.
History
Release version Command history
Syntax
show ip bgp dampened-paths [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip bgp dampened-paths command.
History
Release version Command history
Syntax
show ip bgp filtered-routes [ detail ] [ ip-addr { / mask } [ longer-prefixes ] ] | as-path-access-list name | prefix-list name ]
[ vrf vrf-name ]
Parameters
detail
Optionally displays detailed route information.
ip-addr
IPv4 address of the destination network in dotted-decimal notation.
mask
(Optional) IPv4 mask of the destination network in CIDR notation.
longer-prefixes
Specifies all statistics for routes that match the specified route, or that have a longer prefix than the specified route.
as-path-access-list name
Specifies an AS-path ACL. The name must be between 1 and 32 ASCII characters in length.
prefix-list name
Specifies an IP prefix list. The name must be between 1 and 32 ASCII characters in length.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays BGP4 filtered routes.
History
Release version Command history
Syntax
show ip bgp flap-statistics
show ip bgp flap-statistics ip-addr { / mask } [ longer-prefixes [ vrf vrf-name ] | vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
IPv4 mask of a specified route in CIDR notation.
longer-prefixes
Displays statistics for routes that match the specified route or have a longer prefix than the specified route.
vrf vrf-name
Specifies a VRF instance.
neighbor
Displays flap statistics only for routes learned from the specified neighbor.
ip-addr
IPv4 address of the neighbor.
regular-expression
Specifies a regular expression in the display output on which to filter.
name
Name of an AS-path filter or regular expression.
Modes
Privileged EXEC mode
Examples
The following example displays flap statistics for a neighbor.
History
Release version Command history
Syntax
show ip bgp neighbors [ ip-addr ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
last-packet-with-error
Displays the last packet with an error.
route-summary
Displays routes received, routes accepted, number of routes advertised by peer, and so on.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Output for this command shows all configured parameters for the neighbors. Only parameters with values that differ from
default values are shown.
Examples
The following example shows sample output for the show ip bgp neighbors command.
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr advertised-routes [ detail | / mask-bits ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays details of advertised routes.
mask-bits
Number of mask bits in CIDR notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays the details of advertised routes.
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr flap-statistics [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows flap statistics.
device#
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr last-packet-with-error [ decode ] [ vrf vrf-name ]
Parameters
ip-addr
IP address of a neighbor in dotted-decimal notation.
decode
Decodes last packet that contained an error from any of a device's neighbors.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip bgp neighbors last-packet-with-error command when no
packet from a specified neighbor contained an error.
BGP Header
Marker: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
Message Length: (0x0013) 19
Message Type: (0x04) KEEPALIVE
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr received
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays detailed information for ORFs received from BGP4 neighbors of the device.
vrf vrf-name
Specifies a VRF instance.
prefix-filter
Displays the results for ORFs that are prefix-based.
Modes
Privileged EXEC mode
Examples
The following example displays output for the show ip bgp neighbors received command when the prefix-filter keyword is used.
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr received-routes [ detail ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays detailed route information.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays output for the show ip bgp neighbors received-routes command.
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr rib-out-routes ip-addr mask [ vrf vrf-name ]
show ip bgp neighbors ip-addr rib-out-routes detail ip-addr mask [ vrf vrf-name ]
Parameters
ip-addr
IP address of a neighbor in dotted-decimal notation.
mask
IP mask of the destination network in CIDR notation.
vrf vrf-name
Specifies a VRF instance.
detail
Displays detailed RIB route information.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip bgp neighbors rib-out-routes command.
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr routes
show ip bgp neighbors ip-addr routes { best | not-installed-best | unreachable } [ vrf vrf-name ]
show ip bgp neighbors ip-addr routes detail { best | not-installed-best | unreachable } [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
best
Displays routes received from the neighbor that are the best BGP4 routes to their destination.
not-installed-best
Displays routes received from the neighbor that are the best BGP4 routes to their destination but were not installed in
the route table because the device received better routes from other sources.
unreachable
Displays routes that are unreachable because the device does not have a valid RIP, OSPF, or static route to the next
hop.
detail
Specifies detailed information.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays sample output for the show ip bgp neighbors routes command when the best keyword is used.
History
Release version Command history
Syntax
show ip bgp neighbors ip-addr routes-summary [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays route summary information received in UPDATE messages.
History
Release version Command history
Syntax
show ip bgp peer-group peer-group-name [ vrf vrf-name ]
Parameters
peer-group-name
Specifies a peer group name.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Only the parameters that have values different from the defaults are listed.
Examples
The following example shows sample output from the show ip bgp peer-group command.
History
Release version Command history
Syntax
show ip bgp routes [ num | ip-address/prefix | age num | as-path-access-list name | best | cidr-only | community-access-list
name | community-reg-expression expression | detail | local | neighbor ip-addr | nexthop ip-addr | no-best | not-
installed-best | prefix-list string | regular-expression name | route-map name | summary | unreachable ] [ vrf vrf-name ]
Parameters
num
Table entry at which the display starts.
ip-address/prefix
Table entry at which the display starts.
age
Displays BGP4 route information that is filtered by age.
as-path-access-list name
Displays BGP4 route information that is filtered by autonomous system (AS)-path access control list (ACL). The name
must be between 1 and 32 ASCII characters in length.
best
Displays BGP4 route information that the device selected as best routes.
cidr-only
Displays BGP4 routes whose network masks do not match their class network length.
community-access-list name
Displays BGP4 route information for an AS-path community access list. The name must be between 1 and 32 ASCII
characters in length.
community-reg-expression expression
Displays BGP4 route information for an ordered community-list regular expression.
detail
Displays BGP4 detailed route information.
local
Displays BGP4 route information about selected local routes.
neighbor ip-addr
Displays BGP4 route information about selected BGP neighbors.
nexthop ip-addr
Displays BGP4 route information about routes that are received from the specified next hop.
no-best
Displays BGP4 route information that the device selected as not best routes.
not-installed-best
Displays BGP4 route information about best routes that are not installed.
prefix-list string
Displays BGP4 route information that is filtered by prefix list. The string must be between 1 and 32 ASCII characters in
length.
regular-expression name
Displays BGP4 route information about routes that are associated with the specified regular expression.
route-map name
Displays BGP4 route information about routes that use the specified route map.
summary
Displays BGP4 summary route information.
unreachable
Displays BGP4 route information about routes whose destinations are unreachable through any of the BGP4 paths in
the BGP4 route table.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample input from the show ip bgp routes command when an IP address is specified.
The following example shows sample input from the show ip bgp routes summary command.
History
Release version Command history
Syntax
show ip bgp routes community { num | internet | local-as | no-advertise | no-export } [ vrf vrf-name ]
Parameters
community
Displays routes filtered by a variety of communities.
num
Specific community member.
internet
Displays routes for the Internet community.
local-as
Displays routes for a local sub-AS within the confederation.
no-advertise
Displays routes with this community that cannot be advertised to any other BGP4 devices at all.
no-export
Displays routes for the community of sub-ASs within a confederation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows output from the show ip bgp routes community command when the internet keyword is used.
History
Release version Command history
Syntax
show ip bgp summary [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays summary BGP information.
BGP4 Summary
Router ID: 4.4.4.4 Local AS Number: 65300
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 2
Number of Neighbors Configured: 8, UP: 8
Number of Routes Installed: 80088, Uses 7688448 bytes
Number of Routes Advertising to All Neighbors: 70077 (10011 entries), Uses 600660 bytes
Number of Attribute Entries Installed: 16, Uses 1664 bytes
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
16.1.1.1 65200 ESTAB 2h26m 8s 10011 0 1 0
17.1.1.1 65200 ESTAB 2h26m 8s 10011 0 10010 0
18.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
19.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
20.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
21.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
22.1.1.1 65200 ESTAB 2h26m 2s 10011 0 10011 0
23.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
…
History
Release version Command history
show ip community-list
Displays the status of community lists.
Syntax
show ip community-list list_name
Parameters
list_name
Specifies a BGP community list.
Modes
Privileged EXEC mode
Examples
The following example displays information for a specified list.
History
Release version Command history
Syntax
show ip dhcp relay address interface [ ethernet slot/port| ve interface number ]
Parameters
ethernetslot/port
Interface name in slot/port format.
veinterface number
Interface name in slot/port format.
Modes
Privileged EXEC mode
Examples
The following example displays DHCP relay address(es) configured on interface 0/4:
History
Release version Command history
Syntax
show ip dhcp relay staistics
Modes
Privileged EXEC mode
Usage Guidelines
The show ip dhcp relay statistics command displays the following information about the IP DHCP Relay function for IP DHCP
Relay addresses configured on the switch:
• DHCP Server IP Address configured in the switch.
• Number of DHCP DISCOVERY, OFFER, REQUEST, ACK, NAK, DECLINE, and RELEASE packets received.
• Number of DHCP client packets received (on port 67) and relayed by the Relay Agent.
• Number of DHCP server packets received (on port 67) and relayed by the Relay Agent.
DHCP unicast packets are forwarded directly per route. These packets are not trapped to the switch. As a result, the DHCP
renewal Request/ACK and DHCP Release packets are not counted toward statistics.
Examples
To display general information about the DHCP relay function:
History
Release version Command history
Syntax
show ip igmp groups [ detail | interface | vlan vlan-id | client clientID | cluster clusterID ]
Parameters
detail
Displays detailed information.
interface
Specifies an interface type.
vlan vlan-id
Specifies a VLAN interface.
client clientID
Specifies a Multi-Chassis Trunk (MCT) client.
cluster clusterID
Specifies an MCT cluster.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the IGMP database, including configured entries for either all groups on all interfaces, or all groups
on specific interfaces, or specific groups on specific interfaces.
Examples
The following example displays the IP IGMP groups.
The following example displays the IP IGMP routes learned over an MCT cluster.
History
Release version Command history
Syntax
show ip igmp snooping [mrouter vlan vlan_id | vlan vlan_id ]
Parameters
mrouter vlan vlan_id
Specifies which VLAN interface to display the mrouter configuration related information.
vlan vlan_id
Specifies which VLAN interface to display the snooping configuration related information.
Modes
Privileged EXEC mode
Usage Guidelines
Use the show ip igmp snooping command to display IGMP snooping information, display multicast router port related
information for the specified VLAN, or to display snooping statistics for the specified VLAN in the IGMP protocol module.
Examples
The following example displays IGMP snooping information.
History
Release version Command history
Syntax
show ip igmp static-groups [ detail | interface ethernet / port-channel / ve | vlanvlan-id ]
Parameters
detail
Displays detailed information about the IP IGMP static groups.
interfaceethernet / port-channel / ve
Specifies the interface type.
vlan vlan-id
Specifies the VLAN-ID.
Modes
Privileged EXEC mode
Command Output
The show ip igmp static groups command displays the following information:
Examples
The following example displays information about the IP IGMP static groups.
History
Release version Command history
Syntax
show ip igmp statistics vlan vlan-id
Parameters
vlan-id
Specifies the VLAN-ID. The range is 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example displays the IP IGMP statistics on VLAN 1.
History
Release version Command history
show ip interface
Displays the IP address, status, and configuration for a specified interface.
Syntax
show ip interface { brief | ethernet slot/port | loopback number | port-channel port-number | ve vlan-id }
Parameters
brief
Specifies a brief summary of IP interface status and configuration.
ethernet slot/port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
port-channel port-number
Specifies a port channel interface. Valid values range from 1 through 1024.
ve vlan-id
Specifies a virtual Ethernet (VE) interface.
Modes
Privileged EXEC mode
Usage Guidelines
You can also display a brief summary of such information for all interfaces.
Examples
The following example displays information about all of the interfaces in the summary format.
The following example displays the IP interface status of a specified Ethernet port.
History
Release version Command history
Syntax
show ip interface brief
Modes
Privileged EXEC mode
Examples
The following is sample output.
The following Network Packet Broker (NPB) output indicates interfaces and port-channels configured for internal loopback.
History
Release version Command history
show ip ospf
Displays OSPF information.
Syntax
show ip ospf [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip ospf command.
History
Release version Command history
Syntax
show ip ospf area { A.B.C.D | decimal } database link-state [ adv-router router-id | advertise index | asbr { asbr-id | adv-router
router-id } | extensive | link-state-id id | network { net-id | adv-router router-id } | nssa { nssa-id | adv-router router-id } |
router { router-id | adv-router router-id } | self-originate | sequence-number num | summary { id | adv-router router-id } ]
[ vrf vrfname ]
Parameters
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format. Valid values range from 0 to 2147483647.
database link-state
Displays database link-state information.
adv-router router-id
Displays the link state for the advertising router that you specify.
advertise index
Displays the link state by Link State Advertisement (LSA) index.
asbr
Displays the link state for all autonomous system boundary router (ASBR) links.
asbr-id
Displays the state of a single ASBR link that you specify.
extensive
Displays detailed information for all entries in the OSPF database.
link-state-id id
Displays the link state by link-state ID.
network
Displays the link state by network link.
net-id
Displays the link state of a particular network link that you specify.
nssa
Displays the link state by not-so-stubby area (NSSA).
nssa-id
Displays the link state of a particular NSAA area that you specify.
router
Displays the link state by router link.
router-id
Displays the link state of a particular router link that you specify.
self-originate
Displays self-originated link states.
sequence-number num
Displays the link-state by sequence number that you specify.
summary
Displays the link state summary. Can specify link-state ID or advertising router ID.
id
Displays the link state for the advertising router that you specify.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show ip ospf area command.
Number of Areas is 1
History
Release version Command history
Syntax
show ip ospf border-routers [ A.B.C.D ] [ vrf vrfname ]
Parameters
A.B.C.D
Specifies the router ID in dotted decimal format.
Modes
Privileged EXEC mode
Examples
The following example displays information for all ABRs and ASBRs.
History
Release version Command history
Syntax
show ip ospf config [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip ospf config command.
History
Release version Command history
Syntax
show ip ospf database database-summary [ vrf vrfname ]
show ip ospf database external-link-state [ advertise index | extensive | link-state-id id | router-id router-id | sequence-
number num ] [ vrf vrfname ]
Parameters
database-summary
Displays how many link state advertisements (LSAs) of each type exist for each area, as well as total number of LSAs.
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
external-link-state
Displays information by external link state, based on the following parameters:
advertise index
Displays the hexadecimal data in the specified LSA packet. The index parameter identifies the LSA packet by
its position in the router’s External LSA table. To determine an LSA packet’s position in the table, enter the
show ip ospf external-link-state command.
extensive
Displays LSAs in decrypt format. Do not use this parameter in combination with other display parameters
because the entire database is displayed.
link-state-id id
Displays external LSAs for the LSA source that you specify.
router-id router-id
Displays external LSAs for the advertising router that you specify.
sequence-number num
Displays the External LSA entries for the hexadecimal LSA sequence number that you specify.
link-state
Displays the link state, based on the following parameters:
adv-router router-id
Displays the link state for the advertising router that you specify.
advertise index
Displays the hexadecimal data in the specified LSA packet. The index parameter identifies the LSA packet by
its position in the router’s external-LSA table. To determine an LSA packet’s position in the table, enter the
show ip ospf external-link-state command.
asbr
Displays autonomous system boundary router (ASBR) LSAs.
extensive
Displays LSAs in decrypt format. Do not use this parameter in combination with other display parameters
because the entire database is displayed.
link-state-id id
Displays LSAs for the LSA source that you specify.
network
Displays either all network LSAs or the LSAs for a network that you specify.
nssa
Displays either all NSSA LSAs or the LSAs for a not-so-stubby area (NSSA) that you specify.
router
Displays LSAs by router link.
router-id router-id
Displays LSAs for the advertising router that you specify.
self-originate
Displays self-originated LSAs.
sequence-number
Displays the LSA entries for the hexadecimal LSA sequence number that you specify.
summary
Displays summary information. You can specify link-state ID or advertising router ID.
adv-router router-id
Displays the link state for the advertising router that you specify.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show ip ospf database command.
The following example shows output for the show ip ospf database command when the database-summary keyword is used.
History
Release version Command history
Syntax
show ip ospf filtered-lsa area { ip-address | decimal } { in | out } [ vrf vrf-name ]
Parameters
ip-address
Specifies the IP address of an area.
decimal
Specifies an area address in decimal format. Valid values range from 0 through 2147483647.
in
Specifies the incoming direction.
out
Specifies the outgoing direction.
vrf vrf-name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays information about type 3 LSA filtering in the out direction for OSPFv2 area 0.
History
Release version Command history
Syntax
show ip ospf interface [ A.B.C.D | brief ] [ vrf vrf-name ]
show ip ospf interface [ ethernet slot/port | loopback number | ve vlan_id ] [ brief ] [ vrf vrf-name ]
Parameters
A.B.C.D
Specifies interface IP address in dotted decimal format.
brief
Displays summary information.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
ethernet slot/port
Specifies an Ethernet slot and port. The specified slot must be 0 if the switch does not contain slots.
loopback number
Specifies a loopback port number. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096
Modes
Privileged EXEC mode
Examples
The following example displays OSPF information about all enabled interfaces.
History
Release version Command history
Syntax
show ip ospf neighbor [ extensive ] [ ethernet slot/port | router-id A.B.C.D | ve vlan_id ] [ vrf vrf-name ]
Parameters
extensive
Displays detailed neighbor information.
ethernet slot/port
Specifies an Ethernet slot and port. The specified slot must be 0 if the switch does not contain slots.
router-id A.B.C.D
Displays neighbor information for the specified router ID (in dotted decimal format).
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF instance are shown in the
output.
Modes
Privileged EXEC mode
Examples
The following example displays information about OSPF neighbors.
History
Release version Command history
Syntax
show ip ospf redistribute route [ A.B.C.D:M ] [ vrf vrfname ]
Parameters
A.B.C.D:M
Specifies an IP address and mask for the output.
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows sample output for the show ip ospf redistribute route command.
History
Release version Command history
Syntax
show ip ospf routes [ A.B.C.D ] [ vrf vrfname ]
Parameters
A.B.C.D
Specifies a destination IP address in dotted decimal format.
vrf vrfname
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays all OSPF-calculated routes.
History
Release version Command history
Syntax
show ip ospf summary [ vrf vrfname ]
Parameters
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
device# show ip ospf summary
History
Release version Command history
Syntax
show ip ospf traffic
show ip ospf traffic [ ethernet slot/port | loopback number | ve vlan_id ] [ vrf vrf-name ]
Parameters
interface
Specifies an interface.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
vrf vrf-name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays all OSPF traffic.
History
Release version Command history
Syntax
show ip ospf virtual link [ index ] [ vrf vrfname ]
Parameters
index
Shows information about a specified virtual link.
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows information about all virtual links.
History
Release version Command history
Syntax
show ip ospf virtual neighbor [ index ] [ vrf vrfname ]
Parameters
index
Shows information about a specified virtual neighbor.
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows information about all virtual neighbors.
History
Release version Command history
show ip prefix-list
Displays the status of an IPv4 prefix list.
Syntax
show ip prefix-list name
Parameters
name
Name of an IPv4 prefix list.
Modes
Privileged EXEC mode
Examples
To display the status of the IPv4 prefix list "mylist":
ip extcommunity-list standard 10
seq 10 permit soo 4.3.2.1:987
History
Release version Command history
show ip route
Displays IP route information for IPv4 interfaces.
Syntax
show ip route [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies routes for a selected VRF instance.
A.B.C.D/M
Specifies the IPv4 address and optional mask.
longer
Specifies routes that match the prefix.
all
Specifies information for all configured IPv4 routes.
bgp
Specifies BGP route information.
connected
Specifies directly connected routes, such as local Layer 3 interfaces.
import
Specifies imported IPv4 routes.
src-vrf-name
Specifies a VRF instance from which routes are leaked.
nexthop
Specifies the configured next hop.
nexthopID
Valid values range from 0 through 4294967294.
ref-routes
Specifies all routes that point to the specified next-hop ID .
ospf
Specifies routes learned from the Open Shortest Path First (OSPF) protocol.
static
Specifies configured static routes.
summary
Specifies summary information for all routes.
system-summary
Specifies a system-level routing summary.
Modes
Privileged EXEC mode
Usage Guidelines
If leaked subnet routes are present, that information displays in the output.
To view the status of management routes, use the show ip route vrf command and enter mgmt-vrf as follows. You must enter
the name of the management VRF manually. Sample output is shown below.
0.0.0.0/0
*via 10.20.232.1, mgmt 1, [1/1], 11d23h, static, tag 0
10.20.232.0/21, attached
*via DIRECT, mgmt 1, [0/0], 11d23h, direct, tag 0
10.20.234.119/32, attached
*via DIRECT, mgmt 1, [0/0], 11d23h, local, tag 0
Examples
The following example displays sample output from the show ip route command.
2.4.0.2/31
via 2.6.0.2, Ve 2603, [20/0], 3m23s, eBgp, tag 0
2.6.0.0/29, attached
via DIRECT, Ve 2603, [0/0], 27m24s, direct, tag 0
2.6.0.3/32, attached
via DIRECT, Ve 2603, [0/0], 27m24s, local, tag 0
2.7.0.0/29
via 2.6.0.2, Ve 2603, [20/0], 27m4s, eBgp, tag 0
VRF-Name: default-vrf
Route count: 0 Max routes: Not Set (Route limit not exceeded)
0 connected, 0 static, 0 OSPF, 0 BGP
VRF-Name: mgmt-vrf
Route count: 3 Max routes: Not Set (Route limit not exceeded)
1 connected, 1 static, 0 OSPF, 0 BGP
VRF-Name: orange
Route count: 0 Max routes: Not Set (Route limit not exceeded)
0 connected, 0 static, 0 OSPF, 0 BGP
History
Release version Command history
show ip route-map
Displays the status of an IPv4 route map.
Syntax
show ip route-map namenumber
Parameters
name
Name of an IPv4 route map.
Modes
Privileged EXEC mode
Examples
The following example shows command output for all ip route-maps configured on the device.
History
Release version Command history
Syntax
show ipv6 anycast-gateway [ interface VE | vrf VRF-name]
Parameters
interface VE
Specifies a VE interface.
vrf VRF-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
To display details for IPv6 anycast gateway for all VE interfaces:
History
Release version Command history
Syntax
show ipv6 bgp
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation, with optional mask.
/prefix
IPv6 mask length in CIDR notation.
longer-prefixes
Filters on prefixes equal to or greater than that specified by prefix.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays sample output from the show ipv6 bgp command.
History
Release version Command history
Syntax
show ipv6 bgp attribute-entries [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Each set of attributes is unique and can be associated with one or more routes. The device typically has fewer attribute entries
than routes.
Examples
The following example show sample output for the show ipv6 bgp attribute-entries command.
History
Release version Command history
Syntax
show ipv6 bgp dampened-paths [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp dampened-paths command.
History
Release version Command history
Syntax
show ipv6 bgp filtered-routes [ detail ] [ ipv6-addr { / mask } [ longer-prefixes ] | as-path-access-list name | prefix-list
name ] [ vrf vrf-name ]
Parameters
detail
Optionally displays detailed route information.
ipv6-addr
IPv6 address of the destination network in dotted-decimal notation.
mask
IPv6 mask of the destination network in CIDR notation.
longer-prefixes
Specifies all statistics for routes that match the specified route, or that have a longer prefix than the specified route.
as-path-access-list name
Specifies an AS-path ACL. The name must be between 1 and 32 ASCII characters in length.
prefix-list name
Specifies an IP prefix list. The name must be between 1 and 32 ASCII characters in length.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays BGP4+ filtered routes.
History
Release version Command history
Syntax
show ipv6 bgp flap-statistics
show ipv6 bgp flap-statistics ipv6-addr { / mask } [ longer-prefixes [ vrf vrf-name ] | vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
IPv6 mask of a specified route in CIDR notation.
longer-prefixes
Displays statistics for routes that match the specified route or have a longer prefix than the specified route.
vrf vrf-name
Specifies a VRF instance.
neighbor
Displays flap statistics only for routes learned from the specified neighbor.
ip-addr
IPv6 address of the neighbor.
regular-expression
Specifies a regular expression in the display output on which to filter.
name
Name of an AS-path filter or regular expression.
Modes
Privileged EXEC mode
Examples
The following example displays flap statistics.
History
Release version Command history
Syntax
show ipv6 bgp neighbors [ ipv6-addr ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
last-packet-with-error
Displays the last packet with an error.
route-summary
Displays routes received, routes accepted, number of routes advertised by peer, and so on.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Output shows all configured parameters for the neighbors. Only the parameters whose values differ from defaults are shown.
Examples
The following example shows sample output from the show ipv6 bgp neighbors command.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr advertised-routes [ detail | / mask-bits ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
detail
Displays details of advertised routes.
mask-bits
Number of mask bits in CIDR notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays the details of advertised routes.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr flap-statistics [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp neighbors flap-statistics command.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr last-packet-with-error [ decode ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
decode
Decodes last packet that contained an error from any of a device's neighbors.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp neighbors last-packet-with-error command when no
packet from a specified neighbor contained an error.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr received
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
detail
Displays detailed information for ORFs received from BGP4+ neighbors of the device.
vrf vrf-name
Specifies a VRF instance.
prefix-filter
Displays the results for ORFs that are prefix-based.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp neighbors received command when the prefix-filter
keyword is used.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr received-routes [ detail ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays detailed route information.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays sample output for the show ipv6 bgp neighbors received-routes command.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr rib-out-routes ipv6-addr mask [ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr rib-out-routes detail ipv6-addr mask [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
detail
Displays detailed RIB route information.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp neighbors rib-out-routes command.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr routes [ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr routes [ best | not-installed-best | unreachable [ vrf vrf-name ] ]
show ipv6 bgp neighbors ipv6-addr routes detail [ best | not-installed-best | unreachable [ vrf vrf-name ] ]
show ipv6 bgp neighbors ipv6-addr routes detail [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
best
Displays routes received from the neighbor that are the best BGP4+ routes to their destination.
not-installed-best
Displays routes received from the neighbor that are the best BGP4+ routes to their destination but were not installed in
the route table because the device received better routes from other sources.
unreachable
Displays routes that are unreachable because the device does not have a valid OSPF or static route to the next hop.
vrf vrf-name
Specifies a VRF instance.
detail
Displays detailed information for the specified route types.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp neighbors routes command when the best keyword is
used.
History
Release version Command history
Syntax
show ipv6 bgp neighbors ipv6-addr routes-summary [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Command Output
The show ipv6 bgp neighbors routes-summary command displays the following information.
Examples
The following example shows sample output from the show ipv6 bgp neighbors routes-summary command.
History
Release version Command history
Syntax
show ipv6 bgp peer-group peer-group-name [ vrf vrf-name ]
Parameters
peer-group-name
Specifies a peer group name.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Only the parameters that have values different from their defaults are listed.
Examples
The following example shows sample output from the show ipv6 bgp peer-group command.
History
Release version Command history
Syntax
show ipv6 bgp routes [ num | ipv6-address/prefix | age num | as-path-access-list name | best | cidr-only | community-
access-list name | community-reg-expression expression | detail | local | neighbor ipv6-addr | nexthop ipv6-addr | no-
best | not-installed-best | prefix-list string | regular-expression name | route-map name | summary | unreachable ] [ vrf
vrf-name ]
Parameters
num
Table entry at which the display starts.
ipv6-address/prefix
Table entry at which the display starts.
age
Displays BGP4+ route information that is filtered by age.
as-path-access-list name
Displays BGP4+ route information that is filtered by autonomous system (AS)-path access control list (ACL). The
name must be between 1 and 32 ASCII characters in length.
best
Displays BGP4+ route information that the device selected as best routes.
cidr-only
Displays BGP4+ routes whose network masks do not match their class network length.
community-access-list name
Displays BGP4+ route information for an AS-path community access list. The name must be between 1 and 32 ASCII
characters in length.
community-reg-expression expression
Displays BGP4+ route information for an ordered community-list regular expression.
detail
Displays BGP4+ detailed route information.
local
Displays BGP4+ route information about selected local routes.
neighbor ip-addr
Displays BGP4+ route information about selected BGP neighbors.
nexthop ip-addr
Displays BGP4+ route information about routes that are received from the specified next hop.
no-best
Displays BGP4+ route information that the device selected as not best routes.
not-installed-best
Displays BGP4+ route information about best routes that are not installed.
prefix-list string
Displays BGP4+ route information that is filtered by prefix list. The string must be between 1 and 32 ASCII characters
in length.
regular-expression name
Displays BGP4+ route information about routes that are associated with the specified regular expression.
route-map name
Displays BGP4+ route information about routes that use the specified route map.
summary
Displays BGP4+ summary route information.
unreachable
Displays BGP4+ route information about routes whose destinations are unreachable through any of the BGP4+ paths
in the BGP4+ route table.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample input from the show ipv6 bgp routes command.
The following example shows sample input from the show ip bgp routes command when the summary keyword is used.
History
Release version Command history
Syntax
show ipv6 bgp routes community { num | internet | local-as | no-advertise | no-export } [ vrf vrf-name ]
Parameters
num
Specific community member.
internet
Displays routes for the Internet community.
local-as
Displays routes for a local sub-AS within the confederation.
no-advertise
Displays routes with this community that cannot be advertised to any other BGP4+ devices at all.
no-export
Displays routes for the community of sub-ASs within a confederation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows output from the show ipv6 bgp routes community command when the internet keyword is used.
History
Release version Command history
Syntax
show ipv6 bgp summary [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays summary BGP4+ information.
BGP4 Summary
Router ID: 30.1.1.8 Local AS Number: 4001183001
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 1
Number of Neighbors Configured: 3, UP: 3
Number of Routes Installed: 200, Uses 19200 bytes
Number of Routes Advertising to All Neighbors: 400 (200 entries), Uses 12000 bytes
Number of Attribute Entries Installed: 1, Uses 104 bytes
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
fd80:3001:4031:1::225
4031 ESTAB 8h12m 5s 200 0 0 0
fdcd:3001:3009:1::113
4001133001 ESTAB 8h 6m47s 0 0 200 0
fdcd:3001:3009:1::114
4001143001 ESTAB 6h40m33s 0 0 200 0
History
Release version Command history
Syntax
show ipv6 counters interface [ ethernet slot/plot | loopback loopback-number | ve ve-number ]
Parameters
interface
Specifies an interface.
ethernet slot/plot
Specifies physical Ethernet interface and a valid slot and port on it.
loopback loopback-number
Specifies the loopback interface.
ve ve-number
Specifies the virtual Ethernet (ve) number.
Modes
Privileged EXEC mode
Examples
The following is an example of the show ipv6 counters interface command output.
History
Release version Command history
Syntax
show ipv6 dhcp relay address interface [ ethernet slot/port | ve interface number ]
Parameters
ethernet
Specifies the ethernet interface.
slot
Specifies a valid slot number.
port
Specifies a valid port number.
ve
Specifies the Ve interface.
interface number
Specifies the Ve interface number.
Modes
Privileged EXEC mode
Examples
The following example displays IPv6 DHCP relay address(es) configured per interface.
History
Release version Command history
Syntax
show ipv6 dhcp relay statistics
Modes
Privileged EXEC mode
Usage Guidelines
The show ipv6 dhcp relay statistics command displays the following information about the IP DHCP Relay function for IP
DHCP Relay addresses configured on the device:
• Number of DHCP Error packets dropped.
• Number of DHCP SOLICIT, REQUEST, CONFIRM, RENEW, REBIND, RELEASE, DECLINE, INFORMATION-
REQUEST, RELAY-FORWARD, RELAY-REPLY packets received.
• Number of DHCP RELAY-FORWARD, REPLY packets sent.
Examples
To display statistics for the device:
Packets dropped : 0
Error : 0
Packets received : 0
SOLICIT : 0
REQUEST : 0
CONFIRM : 0
RENEW : 0
REBIND : 0
RELEASE : 0
DECLINE : 0
INFORMATION-REQUEST : 0
RELAY-FORWARD : 0
RELAY-REPLY : 0
Packets sent : 0
RELAY-FORWARD : 0
REPLY : 0
History
Release version Command history
Syntax
show ipv6 interface [ brief | ethernet slot/port | loopback loopback-port-number | ve ve_id ]
Parameters
brief
Displays brief interface information.
ethernet
Specifies Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots
port
Specifies a valid port number.
loopback loopback-port-number
Specifies the loopback interface. The range is from 1 to 255.
ve ve-id
Specifies the VE ID of a virtual Ethernet (VE) interface. The range is from 1 to 4096.
Modes
Privileged EXEC mode
Examples
The following example displays the output of the show ipv6 interface command with an Ethernet interface specified:
History
Release version Command history
Syntax
show ipv6 mld groups [ ipv6 address] [vlan-id ] | [summary ]
Parameters
ipv6 address
Specifies the multicast group address.
vlan-id
Specifies a VLAN ID.
summary
Displays summary information.
Modes
Privileged EXEC mode
Examples
To display information about all IPv6 MLDv1 groups:
To display information about an IPv6 MLDv1 group for a specific multicast address:
History
Release version Command history
Syntax
show ipv6 mld snooping [ vlan vlan-id ] [mrouter ]
Parameters
vlanvlan-id
Specifies a VLAN ID.
mrouter
Specifies all multicast router statistics.
Modes
Privileged EXEC mode
Examples
The following example displays the output for the show ipv6 mld snooping mrouter command.
The following example displays the output for the show ipv6 mld snooping command.
Group: ff1e::1
Member Ports: Eth 0/4
The following example displays the output for the show ipv6 mld snooping vlan 100 command.
Group: ff1e::1
Member Ports: Eth 0/4
History
Release version Command history
Syntax
show ipv6 mld statistics vlan vlan-id
Parameters
vlanvlan-id
Specifies the VLAN-ID.
Modes
Privileged EXEC mode
Examples
To display information about IPv6 MLDv1 statistics for a specific VLAN interface:
History
Release version Command history
show ipv6 nd
Displays the router advertisement information.
Syntax
show ipv6 nd
Parameters
interface
Specifies an interface.
vrf vrf-name
Specifies a VRF instance.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
ve ve-number
Specifies a virtual Ethernet (VE).
prefix
Displays prefix information.
Modes
Privileged EXEC mode
Examples
The following is an example of the show ipv6 nd command output for a specified port.
History
Release version Command history
Syntax
show ipv6 nd suppression-cache [ summary ]
Parameters
summary
Specifies summary format.
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the beginning and
ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the beginning and ending
integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for example:
1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Command Output
The show ipv6 nd suppression-cache command displays the following information:
Examples
The following example displays the results of the basic form of this command.
History
Release version Command history
Syntax
show ipv6 nd suppression-statistics
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the beginning and
ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Command Output
The show ipv6 nd suppression-statistics command displays the following information:
Examples
The following example displays the results of the basic form of this command.
History
Release version Command history
Syntax
show ipv6 nd suppression-status
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the beginning and
ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the beginning and ending
integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for example:
1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Command Output
The show ipv6 nd suppression-status command displays the following information:
Examples
The following example displays the results of the basic form of this command.
History
Release version Command history
Syntax
show ipv6 neighbor [ ipv6-address ] [ vrf vrf-name ]
Parameters
ipv6-address
Restricts the display to the entries for the specified IPv6 address. Specify this parameter in hexadecimal using 16-bit
values between colons, as documented in RFC 2373.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
static
Displays the static IPv6 neighbors.
dynamic
Displays the dynamic IPv6 neighbors .
summary
Displays the summary of IPv6 neighbors.
ve ve-num
Restricts the display to the entries for the specified VE interface. The range is from 1 to 4096.
vrf vrf-name
Displays the IPv6 neighbor information for the specified Virtual Routing/Forwarding (VRF) instance.
Modes
Privileged EXEC mode
Examples
The following example is output of the show ipv6 neighbor summary command.
The following example is output of the show ipv6 neighbor dynamic vrf command.
History
Release version Command history
Syntax
show ipv6 ospf [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf command.
History
Release version Command history
Syntax
show ipv6 ospf area [ A.B.C.D | decimal ] [ vrf vrfname ]
Parameters
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format. Valid values range from 0 to 2147483647.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf area command.
History
Release version Command history
Syntax
show ipv6 ospf database [ advrtr A.B.C.D | extensive | grace | link-id decimal | prefix ipv6-addr ] [ vrf vrfname ]
show ipv6 ospf database [ as-external | inter-prefix | inter-router | intra-prefix | link [ decimal ] | network | router | type-7 ]
[ advrtr A.B.C.D | link-id decimal ] [ vrf vrfname ]
show ipv6 ospf database scope { area { A.B.C.D | decimal } | as | link } [ vrf vrfname ]
Parameters
advrtr A.B.C.D
Displays LSAs by Advertising Router Id in dotted decimal format.
extensive
Displays detailed lists of LSA information.
grace
Displays grace LSA information.
link-id decimal
Link-state ID that differentiates LSAs. Valid values range from 1 through 4294967295.
prefix
Display LSAs that contain a prefix.
ipv6-addr
Specifies an IPv6 address.
as-external
Displays information about external LSAs.
inter-prefix
Displays information about inter area prefix LSAs.
inter-router
Displays information about inter area router LSAs.
intra-prefix
Displays information about intra area prefix LSAs.
link decimal
Displays information about the link LSAs.
network
Displays information about network LSAs.
router
Displays information about router LSAs.
type-7
Displays information about the not so stubby area (NSSA) external LSAs.
scope
Displays LSA information by LSA scope.
area
Displays LSAs by scope within a specified area.
as
Displays autonomous system (AS) LSAs by scope.
link
Displays link LSAs by scope.
summary
Displays LSA summary information.
all-vrfs
Specifies all VRFs.
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf databas command.
Area ID Type LSID Adv Rtr Seq(Hex) Age Cksum Len Sync
0 Link 6472 1.1.1.1 80000001 371 93e1 56 Yes
0 Link 6416 2.2.2.2 80000001 382 d73d 56 Yes
0 Rtr 0 2.2.2.2 80000003 341 bdfc 40 Yes
0 Rtr 0 1.1.1.1 80000002 341 f096 40 Yes
0 Net 6416 2.2.2.2 80000001 341 b536 32 Yes
0 Iap 192480 2.2.2.2 80000001 341 d8bf 44 Yes
History
Release version Command history
Syntax
show ipv6 ospf interface brief [ all-vrfs | vrf vrf-name ]
Parameters
brief
Displays summary information.
all-vrfs
Displays the information for all VRF instances.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are shown in the output.
ethernet slot/port
Specifies an Ethernet slot and port. The specified slot must be 0 if the switch does not contain slots.
loopback number
Specifies a loopback port number. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf interface command the brief keyword is used.
History
Release version Command history
Syntax
show ipv6 ospf memory [ vrf vrfname ]
Parameters
vrf vrfname
Displays the information for the specified VRF instance.
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf memory command.
History
Release version Command history
Syntax
show ipv6 ospf neighbor [ all-vrfs | vrf vrf-name ]
show ipv6 ospf neighbor interface [ ethernet slot/port | loopback number | ve vlan_id ]
show ipv6 ospf neighbor router-id A.B.C.D [ vrf vrf-name ]
Parameters
all-vrfs
Specifies all VRF instances.
vrf vrf-name
Specifies a non-default VRF instance.
detail
Specifies detailed neighbor information.
interface
Displays OSPFv3 interface information.
ethernet slot/port
Specifies an Ethernet slot and port. The specified slot must be 0 if the switch does not contain slots.
loopback number
Specifies a loopback port number. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
router-id A.B.C.D
Specifies neighbor information for the specified router ID (in dotted decimal format).
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf neighbor command when no arguments or keywords are
used.
History
Release version Command history
Syntax
show ipv6 ospf redistribute route A.B.C.D:M [ vrf vrf-name ]
Parameters
A.B.C.D:M
Specifies an IPv6 address.
vrf vrfname
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf redistribute route command when no arguments or keywords are
used.
History
Release version Command history
Syntax
show ipv6 ospf routes A.B.C.D:M [ vrf vrfname ]
Parameters
A.B.C.D:M
Specifies a destination IPv6 address.
vrf vrfname
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays OSPFv3-calculated routes.
History
Release version Command history
Syntax
show ipv6 ospf spf { node | table | tree } [ area { A.B.C.D | decimal } ] [ vrf vrfname ]
Parameters
node
Displays OSPFv3 node information.
table
Specifies a SPF table.
tree
Specifies a SPF tree.
area
Specifies an area.
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format.
vrf vrfname
Specifies an non-default VRF instance.
Examples
The following example shows sample output from the show ipv6 ospf spf command when the tree keyword is used.
The following example shows sample output from the show ipv6 ospf spf command when the table keyword is used.
History
Release version Command history
Syntax
show ipv6 ospf summary [ all-vrfs | vrf vrfname ]
Parameters
all-vrfs
Specifies all VRF instances.
vrf vrfname
Specifies a non-default VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf summary command when no arguments or keywords
are used.
History
Release version Command history
Syntax
show ipv6 ospf virtual-links brief [ vrf vrfname ]
Parameters
brief
Displays summary information.
vrf vrfname
Specifies a non-default VRF instance.
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf virtual-links command when no arguments or keywords are used:
History
Release version Command history
Syntax
show ipv6 ospf virtual-neighbor brief [ vrf vrfname ]
Parameters
brief
Displays summary information.
vrf vrfname
Specifies a nondefault VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf virtual-neighbor command when no arguments or
keywords are used.
History
Release version Command history
Syntax
show ipv6 prefix-list prefix-list-name
Parameters
prefix-list-name
Specifies an IPv6 prefix list name.
Modes
User EXEC mode
Usage Guidelines
The prefix-list-name parameter restricts the display to the specified prefix list. Specify the name of the prefix list that you want to
display.
Command Output
The show ipv6 prefix-list command displays the following information:
Examples
The following example shows how to display IPv6 prefix lists.
History
Release version Command history
Syntax
show ipv6 route [ all | bgp | connected | import source-name | nexthop nexthop-id [ ref-routes ] | ospf | static ] [ vrf vrf-name ]
Parameters
all
Specifies all routes.
bgp
Specifies BGP routes.
connected
Displays the directly connected routes.
import source-name
Specifies import routes and the source VRF name.
nexthop nexthop-id
Displays the route nexthop table.
ospf
Specifies OSPF routes.
ref-routes
Displays information for routes matching the next-hop ID.
static
Specifies static IPv6 routes.
summary
Displays the route summary.
system-summary
Displays the system-level summary for IPv6 routes.
vrf-name
The name of the VRF context.
Modes
Privileged EXEC mode
Examples
The following is an example of show ipv6 route command output.
History
Release version Command history
Syntax
show ipv6 static route [ ipv6prefix | vrf vrf-name ]
Parameters
ipv6prefix
The IPv6 prefix in the A:B::/length format.
vrf vrf-name
The name of the VRF context.
Modes
Privileged EXEC mode
Examples
The following example displays IPv6 static route information for the default VRF.
History
Release version Command history
Syntax
show ipv6 vrrp
Parameters
VRID
The virtual group ID about which to display information. The range is from 1 through 16.
detail
Displays all session information in detail, including session statistics.
summary
Displays session-information summaries.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance. For the default vrf, enter default-vrf.
all
Specifies all VRFs.
interface
Displays information for an interface that you specify.
ve vlan_id
Specifies the VE VLAN number.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display information about IPv6 VRRP and VRRP-E sessions, either in summary or full-detail format. You
can also specify a particular virtual group ID, or an interface for which to display VRRP output.
NOTE
IPv6 VRRP-E supports only the VE interface type.
To display information for IPv6 VRRP sessions using the default VRF, you can use the show ipv6 vrrp summary syntax (with
no additional parameters).
To display information for the default or a named VRF, you can use the show ipv6 vrrp summary vrf syntax with the vrf-name
option.
To display information about all VRFs, use the show ipv6 vrrp summary vrf all syntax.
Examples
The following example displays information about all IPv6 VRRP sessions on the device.
VRID 14
Interface: Ve 2018; Ifindex: 1207961570
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv6
Version: 3
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): fe80::1
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1000 milli sec (default: 1000 milli sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Statistics:
Advertisements: Rx: 0, Tx: 35
Neighbor Advertisements: Tx: 1
VRID 15
Interface: Ve 2019; Ifindex: 1207961571
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv6
Version: 3
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): fe80::1
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1000 milli sec (default: 1000 milli sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Statistics:
Advertisements: Rx: 0, Tx: 448
Neighbor Advertisements: Tx: 1
The following example displays IPv6 VRRP information in detail for a specific virtual group ID of 19, including session statistics.
The following example displays summary information for IPv6 VRRP statistics on the default VRF. (This command is equivalent
to show ipv6 vrrp summary vrf default-vrf.)
The following example displays summary information for IPv6 VRRP statistics on the VRF named red.
The following example displays summary information for IPv6 VRRP statistics on all VRFs.
The following example displays information for IPv6 VRRP-E tracked networks.
VRID 2
Interface: Ve 100; Ifindex: 1207959652
Mode: VRRPE
Admin Status: Enabled
Description :
Address family: IPv6
Version: 3
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 2001:2019:8192::1
Virtual MAC Address: 02e0.5225.1002
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: DISABLE (default: DISABLED)
Advertise-backup: DISABLE (default: DISABLED)
Backup Advertisement interval: 60 sec (default: 60 sec)
Short-path-forwarding: Disabled
Revert-Priority: unset; SPF Reverted: No
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Tracknetwork:
Network(s) Priority Status
========= ======== ==========
2001::/64 20 Up
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 132
Neighbor Advertisements : Tx: 66
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
VRRPE backup advt sent : 0
VRRPE backup advt recvd : 0
History
Release version Command history
Syntax
show lacp { counter [ port-channel ] | sys-id }
Parameters
counters
Displays LACP statistics for all port-channel interfaces.
port-channel
Displays counters for a specific port channel interface. Valid values range from 1 through 1024.
sys-id
Displays the system ID.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the LACP statistics for each port-channel interface for all port-channel interfaces or a single port-
channel interface, or by system ID.
Examples
The following example displays the local system ID.
History
Release version Command history
show license
Displays license information.
Syntax
show license [ eula | id ]
Command Default
Displays the licenses installed on the local switch.
Parameters
eula
Specifies the EULA statement.
id
Specifies the license ID and information.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display general license information, the license ID, and the EULA text.
The EULA text can be displayed using the show license eula command.
Examples
The following example displays the EULA text.
The following example displays the SAU license when the EULA is accepted.
===================================================
Chassis 10:00:C4:F5:7C:40:01:46
History
Release version Command history
show link-fault-signaling
Displays the global and interface link-fault signaling (LFS) statuses.
Syntax
show link-fault-signaling
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported both in default system mode and network packet broker (NPB) mode.
Because you cannot override the egress LFS setting, the global and interface "TX" values are always "ON". If there is an egress
link fault, the affected interface is always brought down.
Command Output
The show link-fault-signaling command displays the following information:
Global Link Fault Displays "RX ON" or "RX OFF" and "TX ON".
PORT # Displays the ethernet or port-channel interface.
LINK FAULT Displays "RX ON" or "RX OFF" and "TX ON". "(local)" indicates an interface-level LFS
configuration.
Examples
The following example displays sample results of the command.
(output
truncated)
History
Release version Command history
Syntax
show link-fault-signaling counters
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported both in default system mode and network packet broker (NPB) mode.
Command Output
The show link-fault-signaling counters command displays the following information:
Examples
The following example displays sample results of the command.
History
Release version Command history
show lldp
Displays Link Layer Discovery Protocol (LLDP) status information.
Syntax
show lldp
Modes
Privileged EXEC mode
Examples
The following example shows how to display LLDP configuration information.
History
Release version Command history
Syntax
show lldp interface [ ethernet slot/port ]
Parameters
ethernet
Use this parameter to specify an Ethernet interface, followed by the slot or port number.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If the ethernet slot/port parameter is not specified, this command displays the LLDP status information received on all the
interfaces.
Examples
To display the LLDP interface information for a specified ethernet interface, enter the following:
History
Release version Command history
Syntax
show lldp neighbors [ interface ethernet slot/port ] [detail]
Parameters
interface ethernet
Causes the display of LLDP information about an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
detail
Causes the display of detailed LLDP neighbor information.
Modes
Privileged EXEC mode
Examples
The following example shows how to display LLDP neighbor information for a specific interface (Ethernet 0/18).
Local Port Dead Interval Remaining Life Remote Port ID Remote Port Descr Chassis ID Tx Rx
System Name
Eth 0/18 120 115 Ethernet 0/25 Eth 0/25 768e.f807.6000 655 654
R6
The following example shows how to display detailed LLDP neighbor information for a specific interface (Ethernet 0/18).
MANDATORY TLVs
===============
Local Interface: Eth 0/18 (Local Interface MAC: 768e.f805.5816)
Remote Interface: Ethernet 0/25 (Remote Interface MAC: 768e.f807.610d)
Dead Interval: 120 secs
Remaining Life : 118 secs
Chassis ID: 768e.f807.6000
LLDP PDU Transmitted: 656 Received: 655
OPTIONAL TLVs
==============
Port Interface Description: Eth 0/25
System Name: R6
History
Release version Command history
Syntax
show lldp statistics [ interface ethernet slot/port ]
Parameters
ethernet
Use this parameter to specify an Ethernet interface, followed by the slot or port number.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify an interface, this command displays the LLDP statistics for all interfaces.
Examples
To display LLDP statistics on the specified interface:
History
Release version Command history
show mac-address-table
Displays MAC address table information.
Syntax
show mac-address-table
show mac-address-table cluster cluster-ID [ { client client-ID [ local | remote ] } | local | remote | { vlan vlan-ID [ client client-
ID ] } ]
show mac-address-table count [ bridge-domain id ]
show mac-address-table [ address mac-address ] [ aging-time] | [dynamic [address mac-address ] | [ interface ethernet0/
port | port-channel interface number] | vlan vlan id] ] [interface ethernet0/port | port-channel number ] [ mdb [ mac-address] |
client <client-name> | vlan <vlan-id>]] [static [address mac-address] | [interface ethernet0/port | port-channel number] |
[vlanvlan id]] [vlanvlan id]
Parameters
bridge-domain id
Specifies displaying information about MAC addresses learned under a bridge domain. When a bridge domain
identifier is not specified, information is displayed about MAC addresses learned under all bridge domains.
cluster cluster-ID
Specifies the MCT cluster ID.
client client-ID
Specifies the client ID.
local
Displays the local MAC addresses for the cluster or the specified client ID.
remote
Displays the remote MAC addresses for the cluster or the specified client ID.
vlan vlan-ID
Specifies the VLAN ID.
address MAC-address
Displays forwarding information for a 48-bit MAC address. The valid format is H.H.H (available in Privileged EXEC
mode only).
aging-time
Displays aging-time.
vlan vlan id
Specifies the VLAN interface. The VLAN ID range is from 1 - 4090.
tunnel tunnel id
Specifies the tunnel interface. The tunnel ID range is from 1 - 100000.
mdb MAC-address
Specifies the MDB information for the cluster client specific macs. The valid format is H.H.H (available in Privileged
EXEC mode only).
client client-name
Displays the client instance. Specify the client name with a maximum of 64 characters.
static address mac-address
Specifies the static MAC address for an ethernet interface, port-channel, or VLAN. The valid format is H.H.H (available
in Privileged EXEC mode only).
Modes
Privileged EXEC mode
Usage Guidelines
To display information about MAC addresses learned under all bridge domains, specify the bridge-domain option without a
bridge-domain identifier.
Command Output
The show mac-address-table command displays the following information:
Bridge domain
BD-Id Bridge domain identifier
Mac-address MAC address
Type MAC address type (Dynamic or static)
State State (Active or Inactive)
Ports Ethernet or port-channel interfaces
LIF Logical interface
peer-ip IP address of a remote VPLS peer
Examples
The following example shows how to display MAC table information for all bridge domains.
The following example shows the number of forwarding entries in the MAC address table for bridge domain 1.
The following example displays the MAC address table aging time.
The following command displays the MAC address table for an MCT cluster.
History
Release version Command history
Syntax
show mac-address-table endpoint-tracking { authenticated |authentication-failed } [ interface { ethernet interface | port-
channel number } ]
Parameters
authenticated
Displays authenticated MAC addresses that are learned.
authentication-failed
Displays nonauthenticated MAC addresses that are learned.
interface
Specifies an Ethernet or port-channel interface.
ethernetinterface
Specifies an Ethernet interface.
port-channelnumber
Specifies a port-channel.
Modes
Privileged EXEC mode
Usage Guidelines
If an interface is not specified, the status for all ports is displayed.
Examples
This example displays all ports where MAC authentication succeeds.
NOTE
"Pending" means that either (a) authentication is in process for the MAC, or (b) the RADIUS server is not reachable.
History
Release version Command history
show media
Displays the SFP information for all the interfaces present on a switch.
Syntax
show media
Modes
Privileged EXEC mode
Usage Guidelines
The command output will be several pages long.
The TX Power Field in the show media command is not supported by the 40-Gbps optics.
Examples
To display all SFP information:
History
Release version Command history
Syntax
show media interface { ethernet slot/port }
Parameters
ethernet slot/port
Specifies an Ethernet interface. The value for slot must be 0 for devices that do not support line cards.
Modes
Privileged EXEC mode
Examples
To display SPF information for an Ethernet interface:
History
Release version Command history
Syntax
show media optical-monitoring
Parameters
ethernet slot/port
Specifies an Ethernet interface. The value for slot must be 0 on devices that do not support line cards.
Modes
Privileged EXEC mode
Examples
The following displays sample output for all interfaces.
History
Release version Command history
show monitor
Displays the monitoring information for all Port Mirroring sessions or for a single session.
Syntax
show monitor [ session session_number ]
Parameters
session session_number
Specifies a session identification number. Valid values range from 0 through 511.
Modes
Privileged EXEC mode
Command Output
The show monitor command displays the following information:
Examples
To display monitoring information for all Port Mirroring sessions:
Session :1
Type :Remote source session
Description :Test monitor session
State :Enabled
Source interface :eth 0/1 (Up)
Destination interface :Vlan x
Direction :Rx
History
Release version Command history
show netconf
Displays the NETCONF session.
Syntax
show netconf
Modes
Privileged EXEC mode
Usage Guidelines
Because the text output is extensive, we recommend that you redirect the output to a text file.
Examples
Typical NETCONF session output.
History
Release version Command history
Syntax
show netconf capabilities
Modes
Privileged EXEC mode
Usage Guidelines
Because the text output is extensive, we recommend that you redirect the output to a text file.
Examples
Typical command example of output.
History
Release version Command history
Syntax
show netconf client-capabilities
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display client capabilities for all active NETCONF sessions. It always displays the session-ID, login name
of the user of the client session, the host IP address, and the time the user logged on. The application vendor name, application
product name and version number, and the identity of the client are also returned if these values are advertized by the client as
capabilities in the <hello> message to the server at the start of the session.
Command Output
The show netconf client-capabilities command displays the following information:
Examples
Typical command output example
Session Id : 10
User name : root
Vendor : Brocade
Product : Brocade Network Advisor
Version : 9.1.0 Build 123
Client user : admin-user
Host IP : 10.24.65.8
Login time : 2011-08-18T08:54:24Z
History
Release version Command history
Syntax
show netconf datastores
Modes
Privileged EXEC mode
Examples
Typical output example for this command.
History
Release version Command history
Syntax
show netconf files[ filename ]
Parameters
filename
The name of the NETCONF file to display.
Modes
Privileged EXEC mode
Examples
Typical command output example.
History
Release version Command history
Syntax
show netconf schemas
Modes
Privileged EXEC mode
Examples
Typical output example for this command.
History
Release version Command history
Syntax
show netconf sessions
Modes
Privileged EXEC mode
Examples
Typical output example for this command.
History
Release version Command history
Syntax
show netconf statistics
Modes
Privileged EXEC nmode
Examples
Typical output example for this command.
History
Release version Command history
Syntax
show netconf-state datastores
Modes
Privileged EXEC mode
Command Output
The show netconf-state datastores command displays the following information:
Examples
Typical command output example.
LOCKED LOCKED
BY LOCKED LOCK BY LOCKED LOCKED
NAME SESSION TIME ID SESSION TIME SELECT NODE
-----------------------------------------------------------------
running - -
startup - -
History
Release version Command history
Syntax
show notification stream ?
Modes
Privileged EXEC mode
Examples
Typical output example for this command.
History
Release version Command history
Syntax
show ntp status
Modes
User EXEC mode
Usage Guidelines
Use this command to display the active NTP server. If an NTP server is not configured, the command output displays the
server as "LOCL". Otherwise, the command displays the NTP server IP address.
Examples
To show the local device NTP status when an NTP server is not configured:
History
Release version Command history
show overlay-class-map
Displays configurations for all overlay class maps or a specified map.
Syntax
show overlay-class-map [ name ]
Parameters
name
Displays configurations for the specified overlay class map.
Modes
Privileged EXEC mode
Examples
To display configurations for a specified overlay class map:
History
Release version Command history
show overlay-policy-map
Displays configurations for all overlay policy maps or a specified map.
Syntax
show overlay-policy-map [ name ]
Parameters
name
Displays details for the specified overlay policy map.
Modes
Privileged EXEC mode
Examples
To display configurations for a specified overlay policy map:
History
Release version Command history
show overlay-service-policy
Displays currently active overlay service policy maps and they interfaces on which they are applied.
Syntax
show overlay-service-policy [ name ] [ detail ]
Parameters
name
Displays details for the specified overlay policy map.
detail
Displays details, including interfaces, on which one or all service policy maps are applied.
Modes
Privileged EXEC mode
Examples
To display all overlay service policy maps:
To display details, including interfaces, for a specified overlay service policy map:
History
Release version Command history
show packet-encap-processing
Displays information about the interfaces on which header processing is enabled.
Syntax
show packet-encap-processing
Modes
Privileged EXEC mode
Usage Guidelines
Ths command is relevant only in NPB system mode.
Command Output
The show packet-encap-processing command displays the following information:
Examples
The following example displays a typical run of show packet-encap-processing.
show packet-encap-processing
----------------------------------------------------------
Port Link Encapsulation Status
----------------------------------------------------------
eth 0/1 Down 802.1BR Stripping Active
eth 0/2 Down 802.1BR Stripping Active
eth 0/3 Down VN-Tag Stripping Active
eth 0/4 Up VN-Tag Stripping Active
eth 0/5 Up VXLAN Stripping Inactive
eth 0/6 Up VXLAN Stripping Inactive
History
Release version Command history
Syntax
show pbf destination [ destination-id ]
Parameters
destination-id
Specifies a PBF destination.
Modes
Privileged EXEC mode
Usage Guidelines
The use-case for this command is under Network Packet Broker (NPB) system mode.
Command Output
The show pbf destination command displays the following information:
Examples
The following example is typical output of the basic form of this command.
History
Release version Command history
Syntax
show pbf destination-group [ pbf-group-id ]
Parameters
pbf-group-id
Specifies a policy-based forwarding (PBF)-destination group. Values range from 1 through 8192.
Modes
Global configuration mode
Usage Guidelines
The use-case for this command is under Network Packet Broker (NPB) system mode.
Command Output
The show pbf destination-group command displays the following information:
Examples
The following example is typical output of the basic form of this command.
History
Release version Command history
show policy-map
Displays configured policy-maps and class-map Policer parameters applied to switch interfaces.
Syntax
show policy-map [ detail policyname | interface { ethernet 0/port | port-channel number } [ in | out ] ]
Parameters
details policyname
Displays the detail configuration of the policy-map along with binding information.
ethernet 0/port
Specifies the Ethernet interface port number.
port-channel number
Specifies the port channel number.
in
Inbound direction where the policy map is applied.
out
Outbound direction where the policy map is applied.
Modes
Global configuration mode
Interface configuration mode
Usage Guidelines
Use this command with a specific interface to display the policy map binding settings (policy map name and traffic direction),
police-priority-map applied, and class map policer parameters applied for that interface.
Use this command without identifying an interface and direction of traffic to display policy map binding for all interfaces on the
switch.
Command Output
The show policy-map command displays the following information:
Interface The interface for which rate limiting information is being displayed.
Direction The traffic direction for which rate limiting is applied.
police-priority-map Remarked priority map used for Policer application (802.1 p priority remarked map).
Conform The traffic in bytes that has been forwarded from this interface that is within the CIR bandwidth
limits.
Examples
To display policy-map binding and class map parameters applied to a specific interface:
Class-map: default
Police:
cir 5 bps cbs 5678 bytes eir 512000 bps ebs 4096 bytes
Police-priority-map: po-pr-map1
Conformed: 30720 bytes set-dscp 0 set-tc 0
Exceeded: 23424 bytes set-dscp 0 set-tc 0
Violated: 0 bytes
Total: 54144 bytes
History
Release version Command history
Syntax
show port port-channel ethernet slot / port
Parameters
slot
Specifies a valid slot. Must be 0.
port
Specifies a valid port.
Modes
Privileged EXEC mode
Examples
The following example displays the LACP attributes for an Ethernet interface:
History
Release version Command history
show port-channel
Displays the Link Aggregation Group (LAG) information for a port-channel.
Syntax
show port-channel [ channel-group-number | detail | load-balance | summary ]
Parameters
channel-group-number
Specifies a port-channel number to display. Range is from 1 through 1024.
detail
Displays detailed LAG information for a port-channel.
load-balance
Displays the load-balance or frame-distribution scheme among ports in the port-channel.
summary
Displays the summary information per channel-group.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the LAGs present on the system with details about the LACP counters on their member links.
LAG interfaces are called port-channels.
When using the show port-channel command, an asterisk in the command output designates that the designated port channel
is the primary link through which the BUM (broadcast, unknown unicast, and multicast) traffic flows.
Examples
The following example displays detailed port-channel information.
(members)
U - Up (port-channel) * - Primary link in port-
channel
S - Switched
M - Not in use. Min-links not met
===== =============== ========== ===============
Group Port-channel Protocol Member ports
===== =============== ========== ===============
1 Po 1 (D) None
History
Release version Command history
Syntax
show interface port channel [channel-group-number|detail|load-balance|summary ]
Parameters
channel-group-number
Specifies a LAG port channel-group number to display. The number of available channels range from 1 through
6144.
detail
Displays detailed LAG information for a port-channel.
load-balance
Displays detailed LAG information for a port-channel.
summary
Displays the summary information per channel-group.
Modes
Privileged EXEC
Usage Guidelines
Use this command to display the LAGs present on the system.
Examples
This example shows how to display detail information for a specific port channel:
History
Release version Command history
Syntax
show port-channel summary
Modes
EXEC
Command Output
The show port-channel summary command displays the following information:
Examples
This example shows how to display summary information for the port channels:
History
Release version Command history
show port-security
Displays the configuration information related to port security.
Syntax
show port-security [ addresses | interface ethernet slot/port ]
Parameters
addresses
Displays the secure MAC addresses configured on the device.
interface
Specifies an interface.
Modes
Privileged EXEC mode
Command Output
The show port-security command displays the following information:
Examples
To display the port MAC security configuration details across ports on the device, enter the following command:
To display the statistics of the port MAC security configured for an interface, enter the following command:
To list the secure MAC addresses configured on the device, enter the following command.
History
Release version Command history
Syntax
show process cpu [ summary ] [ history ] [ top ] [ all-partitions ]
Parameters
summary
Displays a summary view of cpu usage.
history
Displays the history of CPU usage.
top
Displays current CPU utilization.
all-partitions
Displays a summary view of all partitions.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
For an explanation of process states, refer to the UNIX manual page for the ps command.
Examples
To show the information for all processes:
History
Release version Command history
Syntax
show process info ]
Command Default
This command is executed on the local switch.
Modes
Privileged EXEC mode
Usage Guidelines
Pagination is not supported with this command. Use more in the terminal window to display the output one page at a time.
Examples
To display system processes hierarchically:
PID CMD
2 kthreadd
3 \_ migration/0
4 \_ ksoftirqd/0
5 \_ watchdog/0
6 \_ migration/1
7 \_ ksoftirqd/1
8 \_ watchdog/1
9 \_ migration/2
10 \_ ksoftirqd/2
11 \_ watchdog/2
12 \_ migration/3
13 \_ ksoftirqd/3
14 \_ watchdog/3
15 \_ migration/4
16 \_ ksoftirqd/4
17 \_ watchdog/4
18 \_ migration/5
19 \_ ksoftirqd/5
20 \_ watchdog/5
21 \_ migration/6
22 \_ ksoftirqd/6
[Output truncated]
History
Release version Command history
Syntax
show process memory [ summary ]
Parameters
summary
Displays a summary view of memory usage.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Examples
To show memory usage information by individual processes:
History
Release version Command history
Syntax
show ptp brief
Modes
Privileged EXEC mode
Command Output
The show ptp brief command displays the following information if the state is Disabled:
Examples
The following displays example output:
History
Release version Command history
Syntax
show ptp clock
Modes
Privileged EXEC mode
Examples
The following displays example output:
History
Release version Command history
Syntax
show ptp clock foreign-masters record
Modes
Privileged EXEC mode
Examples
The following displays example output:
History
Release version Command history
Syntax
show ptp corrections
Modes
Privileged EXEC mode
Examples
The following displays example output:
History
Release version Command history
Syntax
show ptp parent
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following displays example output:
Grandmaster Clock:
Grandmaster Clock Identity: 60:9c:9f:ff:fe:87:3b:00
Grandmaster Clock Quality:
Class: 248
Accuracy: 254
OffsetScaledLogVariance: 65535
Priority1: 100
Priority2: 255
History
Release version Command history
Syntax
show ptp port interface [ interface ]
Parameters
interface
Name of a PTP-enable interface.
Modes
Privileged EXEC mode
Usage Guidelines
For a port-channel interface, there is a maximum of two member interfaces for each remote node that is a member of the
Multi-Chassis Trunk (MCT).
A port type of "local" indicates that the PTP session is initiated locally. For a physical interface, the PTP port type is always set to
"local".
A port type of "remote" indicates that the PTP session is remotely initiated.
Examples
The following is example output for a port-channel interface:
History
Release version Command history
Syntax
show ptp time-property
Modes
Privileged EXEC mode
Examples
The following is example output:
History
Release version Command history
Syntax
show qos cpu queue { info | queue-number }
Parameters
info
Displays the protocol-to-CPU queue mapping. The information includes the frames per second (FPS) rate and priority.
queue-number
Specifies the CPU queue number to display its default and current FPS. Enter an integer from 0 through 31. You can
display an individual queue or a range of queues. To display a range of queues, insert a hyphen between the beginning
and ending integers (for example, 5-16). To display individual queues and ranges of queues, separate them by
commas (for example, 1,2,4-7,8,9-22,55-66). You can enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Command Output
The show qos cpu queue info command displays the following information:
The show qos cpu queue queue-number command displays the following information:
Examples
The following example displays all CPU queues on the device, including their associated protocols, current frame rates,
priorities, and unused credits.
The following example displays the specified CPU queues with their default and current FPS rates, and unused credits.
History
Release version Command history
Syntax
show qos flowcontrol interface [ ethernet 0/port | all | port-channel number ]
Parameters
ethernet 0/port
Specifies the Ethernet interface. Enter a valid port number.
all
Reports QoS flow control statistics for all interfaces within the system.
port-channel number
Specifies the port channel.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the runtime state retrieved frm the dataplane reflecting the operation of 802.3x pause or Priority
Flow Control (PFC) on an interface.
The administrative state for pause generation and reception or processing is presented for the interface (802.3x mode) or for
each CoS (PFC mode). TX_Pause frame generation statistics are always presented for the interface. The RX_Pause BitTimes is
presented for the interface (802.3x mode) or for each CoS (PFC mode). When PFC is deployed under the CEE Provisioning
model, then the command reports whether the Data Center Bridging eXchange protocol (DCBX) has overridden the user
configuration, for example when the DCBX detects a mis-configuration between CEE peers, it disables PFC operationally.
Examples
To display all of the configured flow control information for an Ethernet interface:
History
Release version Command history
Syntax
show qos interface all
Modes
Privileged EXEC mode
Usage Guidelines
Examples
To show QoS information for all interfaces, use the following command.
History
Release version Command history
Syntax
show qos interface ethernet 0/port
Parameters
port
Specifies a port number.
Modes
Privileged EXEC mode
Examples
The example displays the QoS configuration for a specific interface.
History
Release version Command history
Syntax
show qos interface port-channel port_channel_number
Parameters
port_channel_number
A specific port channel number.
Modes
Privileged EXEC mode
Examples
The following example displays information about a specific port channel interface.
History
Release version Command history
Syntax
show qos maps cos-traffic-class [ map-name ]
Parameters
map-name
Specifies the name of the CoS-to-traffic class map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all CoS-to-traffic class maps.
Examples
The following example displays a CoS-to-traffic class map.
History
Release version Command history
Syntax
show qos maps dscp-cos [ map-name ]
Parameters
map-name
Specifies the name of the DSCP-to-CoS mutation map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all DSCP-to-CoS mutation maps.
Examples
The following example displays a DSCP-to-CoS map applied to an interface.
History
Release version Command history
Syntax
show qos maps dscp-mutation [ map-name ]
Parameters
map-name
Specifies the name of the DSCP mutation map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all DSCP mutation maps.
Examples
The following example displays a DSCP mutation map and its applied interface.
History
Release version Command history
Syntax
show qos maps dscp-traffic-class [ map-name ]
Parameters
map-name
Specifies the name of the DSCP-to-traffic class map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all DSCP-to-traffic class maps.
Examples
The following example displays a DSCP-to-traffic class mutation map.
History
Release version Command history
Syntax
show qos maps traffic-class-cos [ map-name ]
Parameters
map-name
Specifies the name of a traffic class to CoS mutation map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all traffic class to CoS mutation maps.
Examples
The following example displays a traffic class to CoS mutation map.
History
Release version Command history
Syntax
show qos maps traffic-class-dscp [ map-name ]
Parameters
map-name
Specifies the name of a traffic class to DSCP mutation map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all traffic class to DSCP mutation maps.
Examples
The following example displays a traffic class to DSCP mutation map.
History
Release version Command history
Syntax
show qos maps traffic-class-mutation [ map-name ]
Parameters
map-name
Specifies the name of a traffic class mutation map.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify a map name, this command displays all traffic class mutation maps.
Examples
The following example displays a traffic class mutation map.
History
Release version Command history
Syntax
show qos red profiles
Modes
Privileged EXEC mode
Examples
The following example displays the applied RED profiles for a specific interface:
History
Release version Command history
Syntax
show qos red statistics interface interface-name
Parameters
interface interface-name
Specifies the interface.
Modes
Privileged EXEC
Examples
The following example displays the WRED statistics for an interface.
Traffic-class: 3, ProfileId: 10
Packets Dropped: Red: 0, Yellow: 0, Green: 0, Queue Drops: 0
Bytes Dropped: Red: 0, Yellow: 0, Green: 0, Queue Drops: 0
History
Release version Command history
Syntax
show qos tx-queue interface { ethernet slot/port }
Parameters
ethernet
Represents a valid, physical Ethernet interface.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Examples
To display the runtime egress queue state information retrieved from the dataplane:
History
Release version Command history
show rmon
Displays the current RMON status on the device.
Syntax
show rmon [ alarms [ number ] [ brief ] | events [ number ] [ brief ] | logs [ event_number ] | statistics [ number ] [ brief ] ]
Parameters
alarms
Specifies to display the RMON alarm table.
number
Specifies the alarm index identification number. Valid values range from 1 through 65535.
brief
Specifies to display a brief summary of the output.
events
Specifies to display the RMON events table.
number
Specifies the event index identification number. Valid values range from 1 through 65535.
brief
Specifies to display a brief summary of the output.
logs
Specifies to display the RMON log table.
event_number
Specifies the event log index identification number. Valid values range from 1 through 65535.
statistics
Specifies to display the statistics identification number.
number
Specifies the statistics identification number. Valid values range from 1 through 65535.
brief
Specifies a brief summary of the output.
Modes
Privileged EXEC mode
Examples
To display the RMON statistics:
event Index = 4
Description "My Description"
Event type Log & SnmpTrap
Event community name admin
Last Time Sent = 00:00:00
Owner admin
History
Release version Command history
Syntax
show rmon history [ statistics | history_index ]
Parameters
statistics
Displays a more detailed synopsis.
history_index
Specifies the RMON history identification number. Valid values range from 1 through 65535.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display a synopsis of the statistics collected by the rmon event and rmon alarm commands.
Examples
To display the RMON history:
History
Release version Command history
show route-map
Displays the route map configuration details.
Syntax
show route-map [ name ]
Parameters
name
Specifies a route-map.
ve ve-number
Specifies a Virtual Ethernet (VE) interface.
Modes
Privileged EXEC mode
Examples
The following command displays general route-map information.
The following command displays the configured routing attributes of a specific route map.
The following command displays route-map configuration details for a specific interface.
History
Release version Command history
show running-config
Displays the contents of the running configuration.
Syntax
show running-config
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the running configuration. This is the configuration that is currently active on the local device but
which is not saved persistently.
Examples
The following command example displays the contents of the running configuration.
History
Release version Command history
Syntax
show running-config aaa [ accounting [ commands | exec ] | authentication [ login ] ]
Parameters
accounting
Configures Login or Command accounting
commands
Enable/Disable Command accounting
exec
Enable/Disable Login accounting
authentication
Configures preferred order of Authentication output modifiers
login
Configures the order of sources for login (default = ‘local’)
Modes
Privileged EXEC mode
Usage Guidelines
Refer to the aaa authentication command for a description of the displayed attributes.
Examples
To display the authentication mode:
History
Release version Command history
Syntax
show running-config aaa accounting
Modes
Privileged EXEC mode
Usage Guidelines
Refer to the aaa authentication command for a description of the displayed attributes.
Examples
To displaying the authentication mode:
History
Release version Command history
Syntax
show running-config arp
show running-config arp access-list arp-acl-name [ permit ip host [ host-ip-address [ mac host [ host-mac-address ] ] ]
Parameters
ip-address
Specifies the IPv4 address of a static ARP.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
ve ve-id
Specifies a virtual ethernet (VE) interface.
access-list arp-acl-name
Specifies the name of an ARP ACL defined on the device.
host-ip-address
Specifies the IPv4 address.
Modes
Privileged EXEC mode
Examples
The following example displays a sample run of the show running-config arp command.
The following example displays a sample run of the show running-config arp access-list option.
History
Release version Command history
Syntax
show running-config event-handler [ event-handler-name ]
show running-config event-handler event-handler-name trigger [ trigger-id [ raslog raslog-id [ pattern posix-ext-regex ] ] ]
Parameters
event-handler-name
Specifies the name of the event-handler profile. Valid values can have from 1 through 32 characters. The first
character must be alphabetic.
action
Displays by Python script file-names.
description
Describes the event-handler profile. The string can be 1 through 128 characters in length.
trigger trigger-id
Specifies an event-handler trigger. When the trigger-condition occurs, a Python script is run.
raslog raslog-id
Specifies a RASlog message ID as the trigger.
pattern posix-ext-regex
Specifies a POSIX extended regular expression to search for a match within the specified RASlog
message ID. For examples, refer to the "trigger" topic.
Modes
Privileged EXEC mode
Command Output
The show running-config event-handler command displays the following information:
Examples
The following example displays the details of all triggers defined for a specified event-handler.
The following example displays the details of the action defined for a specified event-handler.
History
Release version Command history
Syntax
show running-config interface port-channel [ number ]
Parameters
number
Specifies a valid port-channel number.
Modes
privileged EXEC mode
Examples
The following example displays configuration information about all port channel interfaces.
History
Release version Command history
Syntax
show running-config ip access-list [ { standard | extended } [ ACL_name ] ]
Parameters
standard
Specifies the standard ACL type.
extended
Specifies the extended ACL type.
ACL_name
Specifies the ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Not specifying standard or extended displays a list of all IPv4 ACLs defined on the switch.
To display details of IPv4 ACLs bound to interfaces, use the show access-list ip command.
Examples
The following example displays the IPv4 ACLs defined on the switch.
History
Release version Command history
Parameters
access-group
Specifies an IPv4 ACL applied at device-level.
acl-name
Specifies an IPv4 standard or extended ACL.
Modes
Privileged EXEC mode
History
Release version Command history
Syntax
show running-config ip route [ static | static-route-dest ip-address/length | static-route-next-vrf-dest ip-address/length ]
Parameters
static
Displays information on IPv4 BFD static routes configured for the device.
static-route-dest ip-address/length
Displays information for the specified static route destination address. The IP address must be entered in the form
A.B.C.D/length, where length is the address prefix length.
static-route-next-vrf-dest ip-address/length
Displays configuration information for the specified next-hop VRF. The IP address must be entered in the form
A.B.C.D/length, where length is the address prefix length.
Modes
Privileged EXEC mode
The following example shows four IPv4 routes are active, including a route to a specific IP address, a route to a virtual interface,
a null route, and a route to a physical interface.
History
Release version Command history
Syntax
show running-config ipv6 access-list [ { standard | extended } [ acl-name [ seq [ seq-number [ rule-keyword ] ] ] ] ]
Parameters
access-list
Specifies the access-control list (ACL)
extended
Specifies the extended IP ACL.
standard
Specifies the standard IP ACL.
ipv6-acl-name
Specifies the IPv6 ACL name.
seq seq-number
Specifies a rule. Valid values range from 1 through 4294967290.
rule-keyword
Specifies a rule keyword or operator. For options, type ?.
import routes
Specifies import IPv6 routes.
nd
Displays neighbor discovery commands.
global-suppress-ra
Sets the suppress-ra option globally .
ra-dns-server
Sets the global DNS server option applied on all ND6.
ra-domain-name
Set the global domain name option that applied on all ND6 interfaces.
prefix-list
Specifies the prefix-list.
ge
Specifies the minimum IPv6 prefix length.
prefix-length
The IPv6 prefix length. The range is from 1 through 128.
le
Specifies the maximum IPv6 prefix length.
protocol
Set the global domain name option that applied on all ND6 interfaces.
vrrp
Specifies the Virtual Router Redundacy Protocol IPv6 (VRRPv3).
vrrp-extended
Specifies the Virtual Router Redundacy Protocol IPv6 Extended (VRRPv3-E).
receive
Specifies the receive ACL.
access-group
Specifies to bind or unbind the existing ACL.
route
Specifies the IPv6 unicast static route.
router
Specifies the IPv6 router.
ospf
Specifies the Open Shortest Path First (OSPF) version 3.
vrf
Specifies the VRF instance.
Modes
Privileged EXEC mode
Examples
The following is an example of the show running-config ipv6 command output.
History
Release version Command history
Syntax
show running-config ipv6 access-list [ { standard | extended } [ acl-name [ seq [ seq-number [ rule-keyword ] ] ] ] ]
Parameters
standard
Specifies the standard ACL type.
extended
Specifies the extended ACL type.
acl-name
Specifies the ACL name.
seq seq-number
Specifies a rule. Valid values range from 1 through 4294967290.
rule-keyword
Specifies a rule keyword or operator. For options, type ?.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Not specifying standard or extended displays a list of all IPv6 ACLs defined on the switch.
To display details of all IPv6 ACLs bound to interfaces, use the show access-list ipv6 command.
Examples
The following example displays all standard IPv6 ACLs defined on the device.
History
Release version Command history
Syntax
show running-config ldap-server [ host ipaddr | host-name ]
Parameters
host
Identifies the IPv4 address of the host.
ipaddress
IPv4 address of the host.
host-name
Name of the host.
Modes
Privileged EXEC mode
Usage Guidelines
LDAP server configuration is placed at the beginning of the running-config and is part of the global configuration of the device.
LDAP is enabled by default and no entry is shown in the running-config when set to default.
Examples
device# show running-config ldap-server host 10.24.65.6
ldap-server host 10.24.65.6 use-vrf mgmt-vrf
port 3890 retries 3 timeout 8 basedn security.example.com
device#
History
Release version Command history
Syntax
show running-config mac access-list [ { standard | extended } [ ACL_name ] ]
Parameters
standard
Specifies the standard ACL type.
extended
Specifies the extended ACL type.
ACL_name
Specifies the ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Not specifying standard or extended displays a list of all MAC ACLs defined on the switch.
To display details of all MAC ACLs bound to interfaces, use the show access-list mac command.
Examples
The following example displays all MAC ACLs defined on the switch.
History
Release version Command history
Syntax
show running-config password-attributes [ admin-lockout ] [ max-lockout-duration ] [ max-retry ] [ min-length ]
show running-config password-attributes character-restriction [ lower | numeric | special-char | upper ]
Parameters
admin-lockout
Displays lockout for admin role accounts.
max-retry
Displays the number of failed password logins permitted before a user is locked out. Values range from 0 through 16
attempted logins. The default value is 0.
min-length
Displays the minimum length of the password. Valid values range from 8 through 32 characters. The default is 8
characters.
max-lockout-duration
Displays the maximum number of minutes after which the user account is unlocked. Range is from 0 through 99999.
The default is 0, representing an infinite duration.
character-restriction
Displays the restriction on various types of characters.
lower
Displays the minimum number of lowercase alphabetic characters that must occur in the password. Values
range from 0 through 32 characters. The default value is 0.
numeric
Displays the minimum number of numeric characters that must occur in the password. Values range from 0
through 32 characters. The default is 0.
special-char
Displays the number of punctuation characters that must occur in the password. All printable,
nonalphanumeric punctuation characters, except colon (:) are allowed. Values range from 0 through 32
characters. The default value is 0.
upper
Displays the minimum number of uppercase alphabetic characters that must occur in the password. Values
range from 0 through 32 characters. The default value is 0.
Modes
Privileged EXEC mode
Usage Guidelines
The attributes are not displayed when they hold default values.
Examples
The following example displays all global password attributes.
password-attributes max-retry 4
password-attributes character-restriction upper 1
password-attributes character-restriction lower 2
password-attributes character-restriction numeric 1
password-attributes character-restriction special-char 1
password-attributes max-lockout-duration 5000
History
Release version Command history
Syntax
show running-config radius-server [ host { ip-address | hostname } ]
Parameters
host
Causes the display of running configuration information for a specific RADIUS server.
hostname
Specifies a specific RADIUS server in host name format.
ip-address
Specifies a specific RADIUS server in IP address format. Both IPv4 and IPv6 address formats are supported.
Modes
Privileged EXEC mode
Usage Guidelines
When the host option is omitted, the show running-config radius-server command displays information about all RADIUS
servers that are configured on the device.
Command Output
The show running-config radius-server command displays the following information:
Examples
device# show running-config radius-server
History
Release version Command history
Syntax
show running-config rmon [ alarm | event ]
Parameters
alarm
Displays the Remote Monitor alarm configuration.
event
Displays the Remote Monitor event configuration
Modes
Privileged EXEC mode
History
Release version Command history
Syntax
show running-config role [ name role_name [ desc ] ]
Parameters
name role_name
Displays roles defined for users.
desc
Displays role descriptions.
Modes
Privileged EXEC mode
Examples
The following example displays all roles configured on the device.
History
Release version Command history
Syntax
show running-config rule [ index ]
show running-config rule { action { reject | accept } | command command_name | operation { read-only | read-write } | role
role-name }
Parameters
index
Displays the rule with the specified index number. Values range from 1 through 512.
command command_name
Displays rule configuration for the specified command. To display a list of supported commands, type a question mark
(?). This list varies according to whether or not you specify a rule index.
role role-name
Displays rule configuration for the specified role.
Modes
Privileged EXEC mode
Examples
The following example displays the configured roles and their rules.
rule 30
action accept operation read-write role NetworkSecurityAdmin command role
History
Release version Command history
Syntax
show running-config snmp-server
Modes
Privileged EXEC mode
Examples
The following command shows the running configuration of the SNMP server on the switch.
History
Release version Command history
Syntax
show running-config ssh
Modes
Privileged EXEC mode
Examples
Typical command example:
History
Release version Command history
Syntax
show running-config ssh server
Modes
Privileged EXEC mode
Usage Guidelines
SSH server configuration is placed at the beginning of the running-config and is part of the global configuration of the device.
SSH is enabled by default and no entry is shown in the running-config when set to default.
Examples
When SSH service is shut down:
History
Release version Command history
Syntax
show running-config ssh server key-exchange
Modes
Privileged EXEC mode
Examples
Typical command output:
History
Release version Command history
Syntax
show running-config telemetry collector [ collector-name ]
Modes
Privileged EXEC mode
Parameters
collector-name
Specifies a telemetry collector.
Examples
The following example is the basic command.
History
Release version Command history
Syntax
show running-config telemetry profile [ enhanced-queue-discard-pkts | event | interface | lldp | pbr | queue | system-
utilization ]
Modes
Privileged EXEC mode
Parameters
enhanced-queue-discard-pkts
Displays a subset of the data highlighting discarded packet information.
event
Displays configuration information for the event profile-type.
interface
Displays configuration information for the interface profile-type.
lldp
Displays configuration information for the lldp profile-type.
pbr
Displays configuration information for the pbr (policy-based routing) profile-type.
queue
Displays configuration information for the current telemetry profile queue.
system-utilization
Displays configuration information for the system-utilization profile-type.
Command Output
The show running-config telemetry profile command displays the following information:
Examples
The following example is the basic command.
History
Release version Command history
Syntax
show running-config telemetry server
Parameters
use-vrf vrf-name
(Not supported) Specifies all VRFs or one VRF.
Modes
Privileged EXEC mode
Usage Guidelines
The basic command displays configuration information only for mgmt-vrf.
Examples
The following example is the basic command.
telemetry server
transport ssl
port <port_number>
activate
!
History
Release version Command history
Syntax
show running-config tvf-domain [ tvf-domain-id ]
Parameters
tvf-domain-id
Specifies the ID of the TVF domain. Valid values are from 1 through 4096. To specify a range of domains, insert a
hyphen (-) between the beginning and ending integers (for example, 5-16). To specify individual domains and ranges
of domains, separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas.
Modes
Privileged EXEC mode
Examples
The following command displays the names of all defined TVF domains.
History
Release version Command history
Syntax
show running-config username [ username ] [ access-time ] [ desc ] [ enable ] [ encryption-level ] [ expire ] [ password ]
[ role ]
Parameters
username
Displays the configuration of a specified username. The maximum number of characters is 40.
access-time
Displays access-time configuration.
desc
Displays the description of the user configuration.
enable
Displays the account enablement status.
encryption-level
Password encryption level. Values are 0 through 7. The default is 0.
expire
Date until the password remains valid in YYYY-MM-DD format. Valid year values range from 1902 through 2037. By
default, passwords do not expire.
password
Account password.
role
The role associated with the account.
Modes
Privileged EXEC mode
Usage Guidelines
To display details for one user only, specify username . Otherwise, this command displays all user accounts on the device.
Examples
The following example displays the user accounts on the device.
The following example displays the enabled status for a specific user account.
History
Release version Command history
show sflow
Displays sFlow configuration information and statistics.
Syntax
show sflow {interface ethernet slot / port | all }
Command Default
sFlow is disabled on all interfaces.
Parameters
all
Displays all sFlow information and statistics.
interface
Filters by interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Examples
The following example displays all sFlow statistics.
History
Release version Command history
Syntax
show span path session session-number
Parameters
session-number
Specifies the SPAN session.
Modes
Privileged EXEC mode
Examples
The following example displays the SPAN path information.
Session :1
Path :Eth 0/10 -> Eth 0/1 (ISL-exit port) -> Eth 0/16
History
Release version Command history
show spanning-tree
Displays Spanning Tree Protocol (STP) information.
Syntax
show spanning-tree [ brief | interface { ethernet slot/port | port-channel port_channel_number } | pvst | mst [ brief | detail |
instance instance_id | interface ] mst-config | vlan vlan_id ]
Parameters
brief
Display brief spanning tree information.
interface
Display iinformation about the spanning tree configuration on an interface.
ethernet slot/port
Display spanning tree information about a specific Ethernet interface.
port-channel port_channel_number
Display spanning tree information about a port channel interface.
pvst
Display PVST+ information.
mst
Display MSTP information.
detail
Display detailed MSTP tree information.
instance instance_id
Display MSTP information about a specivic instance.
mst-config
Display MSTP region configuration information.
vlan vlan_id
Display spanning tree information about a specific VLAN.
Modes
Privileged EXEC mode.
Usage Guidelines
The PVST+ and R-PVST+ protocols are supported. The PVST and R-PVST protocols—proprietary to Cisco—are not supported.
Examples
To display spanning tree information:
History
Release version Command history
Syntax
show ssh client status
Modes
Privileged EXEC mode
Examples
When SSH server is enabled:
History
Release version Command history
Syntax
show ssh server status
Modes
Privileged EXEC mode
Examples
When SSH server is enabled:
History
Release version Command history
show startup-config
Displays the contents of the startup configuration.
Syntax
show startup-config
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
Examples
The following example displays the contents of the startup configuration file.
History
Release version Command history
show startup-database
Displays the startup database information.
Syntax
show startup-database
Modes
Privileged EXEC mode
Usage Guidelines
Enter show startup-database ? to display the list of available database entries.
Examples
To display the logging configuration in the startup database:
History
Release version Command history
Syntax
show statistics access-list interface { ethernet slot / port | port-channel index | ve vlan_id | vlan vlan_id } { in | out }
show statistics access-list { ip | ipv6 } name interface [ ethernet slot / port | port-channel index | ve vlan_id ] { in | out }
show statistics access-list mac name interface [ ethernet slot / port | port-channel index | vlan vlan_id ] { in | out }
Parameters
interface
Filter by interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
ve vlan_id
Specifies a virtual Ethernet (VE) interface.
vlan vlan_id
Specifies a VLAN interface.
in | out
Specifies the ACL binding direction (incoming or outgoing).
ip | ipv6 | mac
Specifies the network protocol.
name
Specifies the ACL name.
global
Specifies IPv4 or IPv6 receive-path traffic.
Modes
Privileged EXEC mode
Usage Guidelines
Statistics are displayed only for rules that contain the count keyword.
Command Output
The show statistics access-list command displays the following information:
Uncount The counter resource is not allocated. This is typically seen if counting is not supported or if the
hardware resources limit is reached.
Unwritten The rule is inactive and is not programmed in the hardware. This is typically seen when the
hardware resources limit is reached.
Examples
The following example displays inbound ACL statistics for a named IPv4 ACL.
The following example displays inbound ACL statistics for a specified interface. The ACL named ipv6-std-acl is applied on
interface 0/1 to filter incoming routed traffic only.
The following example displays inbound statistics for all ACLs bound to a specified VE interface.
History
Release version Command history
Syntax
show statistics bridge-domain [ bd-id ]
Parameters
bd-id
Specifies the bridge domain ID.
Modes
Privileged EXEC mode
Usage Guidelines
show statistics bridge-domain bd- id
Command Output
The show statistics bridge-domain command displays the following information:
Field Description
Examples
The following example displays statistics for all bridge domains.
History
Release version Command history
Syntax
show statistics vlan vlan id
Parameters
vlan ID
The specific VLAN ID.
Modes
Privileged EXEC mode
Usage Guidelines
show statistics vlan vlan- id
Command Output
The show statistics vlan command displays the following information:
Field Description
Examples
The following example displays statistics for all ports and port channels on configured VLANs.
The following example displays statistics for all ports and port channels in the VLAN 10.
Vlan 10 Statistics
Interface RxPkts RxBytes TxPkts TxBytes
eth 0/1 821729 821729 95940360 95940360
eth 0/2 884484 885855 95969584 95484555
po 1 8884 8855 9684 9955
History
Release version Command history
show storm-control
Displays all BUM (broadcast, unknown unicast and multicast)-related configurations in the system.
Syntax
show storm-control [ broadcast | multicast | unknown-unicast ] [ interface { ethernet } 0/port ]
Parameters
storm-control
Displays all BUM-related configurations in the system.
broadcast
Displays all BUM-related configurations in the system for the broadcast traffic type.
multicast
Displays all BUM-related configurations in the system for the multicast traffic type.
unknown-unicast
Displays all BUM-related configurations in the system for the unknown-unicast traffic type.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display BUM storm-control-related configuration for the entire system, for specified traffic types, for
specified interfaces, or for specified traffic types on specified interface.
Examples
To display storm control information for broadcast traffic on an Ethernet interface:
To display storm control information for all broadcast traffic the system:
History
Release version Command history
show support
Displays a list of core files on the switch.
Syntax
show support
Command Default
Displays information for the local switch.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Pagination is not supported with this command. Use the More option to display the output one page at a time.
Examples
To display the core files:
History
Release version Command history
show system
Displays hardware and software system information.
Syntax
show system
Modes
Privileged EXEC mode
Examples
To display the system information:
-- UNIT 0 --
Unit Name : F115
Ethernet Port(s) : 54
Up Time : up 2 days 23:55
Current Time : 19:03:43 GMT
SLX-OS Version : 17s.1.00_bfd_fix
Jumbo Capable : yes
Burned In MAC : 60:9C:9F:B1:0B:AA
Management IP : 10.20.234.115
Management Port Status : UP
-- Power Supplies --
PS1 is OK
PS2 is faulty
-- Fan Status --
Fan 1 is Ok, speed is 5857 RPM
Fan 2 is Ok, speed is 5677 RPM
Fan 3 is Ok, speed is 5677 RPM
Fan 4 is Ok, speed is 5677 RPM
Fan 5 is Ok, speed is 5857 RPM
Fan 6 is Ok, speed is 5857 RPM
History
Release version Command history
Syntax
show system internal dcm { clients | last-config-time xpaths | memstat [ detail ] | message-stat all | object-stat all }
show system internal dcm message details config service service-number { off | on }
Parameters
clients
Displays connected clients.
last-config-time xpaths
Displays last configuration-time xpaths.
memstat
Displays DCM memory statistics.
detail
Displays detailed DCM memory statistics.
message-stat all
ATTENTION
Running this command can use significant system
resources.
object-stat all
Displays a summary of DCM object statuses.
off
Turns off the specified message-history dump.
on
Turns on the specified message-history dump.
service
Displays detailed or summary information for a DCM service.
details
Displays detailed information. If this option is not specified, displays summary information.
service-number
Specifies a service number.
vlan
Displays VLAN-related details.
port-vlans
Displays port-VLAN associations.
provisioned-vlans
Displays provisioned VLANs.
vlans-with-ivid
Displays VLANs associated with IVID.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following command displays DCM connected clients.
History
Release version Command history
Syntax
show system internal nsm { gvlan [ vlan-id ] | ivid [ vlan-id ] | vrbid }
Parameters
gvlan
Displays global-VLAN (GVLAN) information.
vlan-id
Displays GVLAN information for a specified VLAN.
ivid
Displays information for VLANs associated with IVIDs.
vlan-id
Displays GVLAN information for a specified VLAN.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example displays information for IVIDs provisioned to VLAN 1.
The following example is sample output for the show system internal nsm gvlan option.
History
Release version Command history
Syntax
show system internal nsx export-vlan-cache
Parameters
export-vlan-cache
Displays the export-VLAN cache.
locator-cache
Displays the physical-locator cache.
count
Displays only the number of cache entries.
lswitch-cache
Displays the logical-switch cache.
count
Display only the number of cache entries.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example shows a sample output of the show system internal nsx export-vlan-cache option.
The following example shows a sample output of the show system internal nsx lswitch-cache option.
The following example shows a sample output of the show system internal nsx locator-cache option.
History
Release version Command history
Syntax
show system internal ovsdb { monitors | schema }
show system internal ovsdb table name [ count | where column function value ]
Parameters
monitors
Specifies registered monitors.
schema
Specifies all ovsdb schemas and tables.
table name
Specifies an ovsdb table.
count
Specifies the number of rows.
where
Specifies a condition.
column
Specifies a table column.
function
Specifies a function, for example, =.
value
Specifies the column value.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Please work closely with Extreme Networks
technical support in running debug or show system internal commands and interpreting their results.
Examples
The following example shows a sample output of the show system internal ovsdb schema option.
The following example shows a sample output of the show system internal ovsdb table name where option.
History
Release version Command history
Syntax
show system monitor
Modes
Privileged EXEC mode
Examples
The following example displays the status of the local switch.
History
Release version Command history
Syntax
show telemetry client-cert
Modes
Privileged EXEC mode
Usage Guidelines
There is no display if there are no certificates configured.
Examples
Typical command example.
-----BEGIN CERTIFICATE-----
MIIC2jCCAcICAQEwDQYJKoZIhvcNAQEFBQAwMzELMAkGA1UEBhMCQ0ExEDAOBgNV
BAoMB0Jyb2NhZGUxEjAQBgNVBAMMCWxvY2FsaG9zdDAeFw0xNzAzMjExNzQ1NDNa
Fw0xODAzMjExNzQ1NDNaMDMxCzAJBgNVBAYTAkNBMRAwDgYDVQQKDAdCcm9jYWRl
MRIwEAYDVQQDDAlsb2NhbGhvc3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC+YG/CkiNm/BO+u1mYLKP8cpz/0O9CE+fusO0spXxjKfjPAvK7kiogxABm
bg9MQeWl4SbFa5x3q5uyZJxApJ+tAnnWZa+cbj5pmNsQFfIbFOwSAmFyhh/NIp7Y
/wApskKjnVsMFkarqX8W2xKxZreapZFMa9DGpOeh8Jo2yvcTAimFfSJ4nyKlCr1C
DuuaTSvAttC8Z9mEqD9TOaSYwQI0pnfVO+ySgY8ndqDXYdRvl+bV1taghlKOgxMY
J78lyZxYf6CIn22BAaz/f9a5ffS13Hh5Cmurj2dUmmqDE49p2KEVtXQ3D6nuopli
V49ok+z93/40Uq4OVJZJk5Kx8ZuxAgMBAAEwDQYJKoZIhvcNAQEFBQADggEBAI1d
1VkMH9i3SorPIHpbVqbeDe7LPdaFmrT0COr3AFUECw3gBj1Zy82Kp8XkIJJdVCu8
MNm3wTARqeNBY2c3luw6QeA6l4qRIVM4FqNj6rvtqtNZQ9EEKRRwAm0GSVp+uSvu
E88XSXO+r6N+SXQemRIyhNQ7LJq+cDEaP5WfNtKg+zj085Xd0qiB94BKFt5Q+xAa
B7lwuUvT7Yt92aUVXIaZ6aY5oMv4t7+lPBBKjg8cNeywDa9h3yVZYIzSggghu0qu
GZO57qUh5agxqKiEVf9Ya325u5gj73UJsKOSsyVA1HB8RsPEEdz8j8FBAqMNSTQj
8UDtUGpYiYlzyiBUELc=
-----END CERTIFICATE-----
History
Release version Command history
Syntax
show telemetry collector { summary | name collector-name }
Parameters
summary
Displays a summary of the Telemetry collectors.
name collector-name
Displays the information for the designated collector.
Modes
Privileged EXEC mode
Command Output
The show telemetry collector command displays the following information:
Examples
Typical summary output.
Activated Collectors:
----------------------
Name IP Address:Port Streaming/Connection Status
-------------------- ------------------- ---------------------------
Collector_3333 10.70.12.112:33333 starting_profiles
Collector_4444 10.70.12.112:44444 streaming
Collector_2345 10.70.12.112:33333 streaming_errored
History
Release version Command history
Syntax
show telemetry server status
Modes
Privileged EXEC mode
Command Output
The show telemetry server status command displays the following information:
Examples
Typical command output.
Telemetry Server running on IP 10.70.12.112 and port 33333, with transport as tcp.
Active Sessions:
----------------
Client Profiles Streamed Interval Uptime Last Streamed
------ ------------------- --------- ---------- ---------------
ClientIP1/Host1 default_interface_statistics 120 sec 02/15:32 2017-01-18::22:55:12
default_system_utilization_statistics 300 sec 04/05:44 2017-02-03::05:36:15
History
Release version Command history
Syntax
show telnet server status
Modes
Privileged EXEC mode
Examples
To display Telnet server status:
History
Release version Command history
Syntax
show threshold monitor [ interface all area | security area [ login-violation | telnet-violation ] | sfp all area [ current | rxp |
temperature | txp | voltage ]
Parameters
interface all area
Displays status of interface thresholds and alerts.
security area
Displays status of security thresholds and alerts.
login-violation
Displays status of login violations.
telnet-violation
Displays status of Telnet violations.
current
Amount of current supplied to the SFP transceiver.
rxp
Amount of incoming laser power, in microWatts (μW).
temperature
Temperature of the SFP, in degrees Celsius.
txp
Amount of outgoing laser power, in microWatts (μW).
voltage
Amount of voltage supplied to the SFP.
Modes
Privileged EXEC mode
Examples
device# show threshold monitor sfp all area temperature
Interface Type Area Value Status
Monitoring Status
--------------------------------------------------------------------------------------------------------
---------------
Eth 0/3 10GSR Temperature 26 Centigrade In Range
Monitoring
Eth 0/4 10GSR Temperature 24 Centigrade In Range
Monitoring
History
Release version Command history
show tpvm
Displays status of Third-Party Virtual Machine (TPVM) applications.
show tpvm [ disk { add name { disk_name | auto disk_size } | remove name { disk_name | auto }
Command Default
This feature is not enabled.
Parameters
install
Installs TPVM.
disk
Displays disk information.
disk_name
Specifies a disk.
all
Specifies all disks.
ip-address
Displays IPv4 and IPv6 addresses that are configured on TPVM. See the Usage Guidelines.
status
Displays TPVM information.
Modes
Privileged EXEC mode
Examples
To display the current status of TPVM or any errors:
History
Release version Command history
show tunnel
Displays information pertaining to a tunnel interface.
Syntax
show tunnel tunnel-id
show tunnel status {tunnel-id | dst-ip destination-ip | mode [ gre | vxlan ] | node-id node-id | overlay-gateway [ overlay-
gateway-name ] | src-ip source-ip }
Parameters
tunnel-id
Specifies the tunnel ID.
replicator
Displays tunnels to NSX replicators
node-id
Displays from specified nodes
statistics
Displays tunnel statistics.
dst-ipdestination-ip
Filters by tunnel destination IP address.
node-id node-id
Displays from specified nodes.
overlay-gateway [ overlay-gateway-name
Filters by overlay gateway name.
src-ip source-ip
Filters by tunnel source IP address.
Modes
Privileged EXEC Mode
Examples
This example displays tunnel information.
History
Release version Command history
Syntax
show tunnel statistics tunnel-Id mode [ gre | vxlan ]
Parameters
tunnel-Id
Filters by the tunnel ID.
mode
FIlters by tunnel mode.
gre
Specifies GRE tunnels.
node-id node-Id
Displays from the specified node ID.
overlay-gateway overlay-gatway-name
Filter by overlay gateway name.
src-ip source-ip
Filter by tunnel source IP address.
Modes
Privileged EXEC Mode
Examples
This example displays tunnel statistics filtered by the tunnel ID.
History
Release version Command history
show users
Displays the users logged in to the system and locked user accounts.
Syntax
show users
Modes
Privileged EXEC mode
Examples
The following example displays active user sessions and locked user accounts.
**LOCKED USERS**
testUser
History
Release version Command history
show version
Displays the current firmware version.
Syntax
show version [ all-partitions ] [ brief ]
Parameters
all-partitions
Displays firmware information for both the active and the standby partitions. For each module, both partitions are
displayed.
brief
Displays a brief version of the firmware information.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display firmware version information and build dates. The default command output includes the following
information:
• Network Operating System Version—The firmware version number
• Firmware name—The label of the firmware image
• Build Time—The build date and time of the firmware
• Install time—The date and time of the firmware installation
• Host Version—The Linux host version.
• Host Kernel—The Linux kernel version
• Control Processor—The control processor model and memory
Examples
To display the firmware version information for all partitions:
History
Release version Command history
show vlan
Displays information about one or more VLAN interfaces.
Syntax
show vlan [ vlan_id | brief [ provisioned | unprovisioned ] | classifier ]
Parameters
vlan_id
Specifies the VLAN interface to display.
brief
Displays VLAN information for all interfaces including static and dynamic.
classifier
Displays all VLAN classification information.
provisioned
Displays provisioned VLANs.
unprovisioned
Displays unprovisioned VLANs.
Modes
Privileged EXEC mode
Examples
The following example displays information about an 802.1Q VLAN:
The following example shows all VLANs that are configured, provisioned (active) and unprovisioned (inactive):
(T)-Transparent (t)-Tagged
(R)-RSPAN (c)-Converged
=========================================
300 vlan300 INACTIVE Eth 0/1(t)
5000(T) vlan5000 ACTIVE Eth 0/2(t) ctag 50, 60, 100-200
Eth 0/3(t) ctag 50, 60, 100-200
5500(T) vlan5500 ACTIVE Eth 0/4(t) ctag 1, 1002, 4093, 4095
5800 vlan5800 ACTIVE Eth 0/5(t) ctag 800
6000(T) vlan6000 ACTIVE Eth 0/1(t)
(t)-Tagged
(R)-RSPAN (c)-Converged
=========================================
1 default ACTIVE Eth 0/1(c)
5000 VLAN5000 ACTIVE Eth 0/1(t) ctag 100
Eth 0/2(u) ctag 200
Eth 0/3(u)
Eth 0/4(u) mac 0004.0004.0004
6000 VLAN6000 ACTIVE Eth 0/1(t) ctag 300
Eth 0/2(u) mac 0002.0002.0002
Eth 0/3(u) mac-group 1
Po 10(t) ctag 300
7000 VLAN7000 ACTIVE Eth 0/1 (t) ctag 400
Eth 0/2 (u) mac 0006.0006.0006
Eth 0/3 (u) mac-group 2
1002(F) VLAN1002 ACTIVE Eth 0/5(t)
Eth 0/6(t)
(R)-RSPAN (c)-Converged
======== ================ ======= ======
2000 VLAN2000 INACTIVE(unprovisioned)
4000 VLAN4000 INACTIVE(unprovisioned)
8000 VLAN8000 INACTIVE(unprovisioned)
History
Release version Command history
Syntax
show vlan brief [ provisioned | unprovisioned ]
Parameters
provisioned
Displays provisioned VLANs.
unprovisioned
Displays unprovisioned VLANs.
Modes
Privileged EXEC mode
Command Output
The show vlan brief command displays the following information:
Examples
The following example shows all VLANs that are configured, provisioned (active) and unprovisioned (inactive). VLAN 5800 was
assigned the name "marketing."
(T)-Transparent (t)-Tagged
(R)-RSPAN (c)-Converged
=========================================
300 vlan300 INACTIVE Eth 0/1(t)
5000(T) vlan5000 ACTIVE Eth 0/2(t) ctag 50, 60, 100-200
Eth 0/3(t) ctag 50, 60, 100-200
5500(T) vlan5500 ACTIVE Eth 0/4(t) ctag 1, 1002, 4093, 4095
5800 marketing ACTIVE Eth 0/5(t) ctag 800
6000(T) vlan6000 ACTIVE Eth 0/1(t))
History
Release version Command history
Syntax
show vlan classifier [ group number | interface group-number | interface port-channel number | rule number | interface
ethernet slot/port ]
Parameters
group number
Specifies the VLAN classifier group number. Valid values range from 1 through 16.
rule number
Specifies the VLAN classifier rule number. Valid values range from 1 through 256.
interface ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display information about all configured VLAN classifier groups or a specific VLAN interface group.
If a group ID is not specified, all configured VLAN classifier groups are shown. If a group ID is specified, a specific configured
VLAN classifier group is shown.
History
Release version Command history
Syntax
show vlan private-vlan
Modes
Privileged EXEC mode
Examples
Typical command output display:
History
Release version Command history
Syntax
show vlan rspan-vlan
Modes
Privileged EXEC mode
Examples
device# show vlan rspan-vlan
Total Number of VLANs configured : 3
Total Number of VLANs provisioned : 2
Total Number of VLANs unprovisioned : 1
VLAN Name State Ports Classification
============= =========== ====================== ============ ======
6000(R) VLAN6000 INACTIVE(member port down) Eth 0/2(t) ctag 121
6001(R) VLAN6001 INACTIVE(member port down) Eth 0/3(t) ctag 555
History
Release version Command history
show vrf
Displays Virtual Routing and Forwarding (VRF) configuration information.
Syntax
show vrf [ vrf-name | detail | interface interface ] ]
Parameters
vrf-name
Specifies a named VRF. For the default VRF, enter default-vrf.
detail
Displays detailed information for all VRFs configured.
interface interface
Displays VRF information for an interface.
Modes
Privileged EXEC mode
Examples
The following example displays basic information for the default VRF.
The following example indicates which VRFs are available on which interfaces.
History
Release version Command history
show vrrp
Displays information about IPv4 VRRP and VRRP-E sessions.
Syntax
show vrrp
Parameters
VRID
The virtual group ID about which to display information. The range is from 1 through 16.
detail
Displays all session information in detail, including session statistics.
summary
Displays session-information summaries.
interface
Displays information for an interface that you specify.
ve vlan_id
Specifies the VE VLAN number.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance. For the default vrf, enter default-vrf.
all
Specifies all VRFs.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display information about VRRP and VRRP-E sessions, either in summary or full-detail format. You can
also specify a particular virtual group ID or interface for which to display output.
This command is for VRRP and VRRP-E. VRRP-E supports only the VE interface type.
To display information for VRRP sessions using the default VRF, you can use the show vrrp summary command syntax (with
no additional parameters).
For the default or a named VRF, you can use the show vrrp summary vrf command syntax with the vrf-name option.
To display information for all VRFs, use the show vrrp summary vrf all command.
Examples
The following example shows all VRRP session information in detail, including session statistics.
VRID 14
Interface: Ve 2018; Ifindex: 1207961570
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 10.18.1.100
Virtual MAC Address: 0000.5e00.0112
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 49
Gratuitous ARP : Tx: 1
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
VRID 15
Interface: Ve 2019; Ifindex: 1207961571
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 10.19.1.100
Virtual MAC Address: 0000.5e00.0113
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 81
Gratuitous ARP : Tx: 1
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
The following example displays summary information for VRRP statistics on the VRF named Marketing.
The following example displays summary information for VRRP statistics on all VRFs.
The following example displays summary information for VRRP statistics on the default VRF. (This command is equivalent to
show vrrp summary.)
VRID 3
Interface: Ve 100; Ifindex: 1207959652
Mode: VRRPE
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 10.1.1.100
Virtual MAC Address: 02e0.523d.750a
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: DISABLE (default: DISABLED)
Advertise-backup: DISABLE (default: DISABLED)
Backup Advertisement interval: 60 sec (default: 60 sec)
Short-path-forwarding: Disabled
Revert-Priority: unset; SPF Reverted: No
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Tracknetwork:
Network(s) Priority Status
========= ======== ==========
10.20.1.0/24 50 Up
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 35
Neighbor Advertisements : Tx: 19
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
VRRPE backup advt sent : 0
VRRPE backup advt recvd : 0
The following example displays information about the configured values for the Owner Priority and Owner Track-Priority. In this
example, owner preemption is enabled because the value of owner priority is set to 250 (owner priority is 255 by default), and
interfaces are to be tracked on the owner device with a configured priority of 50 if the interface goes down.
VRID 1
Interface: Ve 100; Ifindex: 1207959652
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Initialize
Session Master IP Address:
Virtual IP(s): 10.1.1.100
Configured Priority: unset (default: 100); Current Priority: unset
Configured Owner Priority: 250; Owner Track-Priority: 50
Advertisement interval: 2 sec (default: 1 sec)
Preempt mode: DISABLE (default: DISABLED)
Advertise-backup: DISABLE (default: DISABLED)
Backup Advertisement interval: 60 sec (default: 60 sec)
Short-path-forwarding: Disabled
Revert Priority: unset; SPF reverted: No
Hold time: 0 sec (default: 0 sec)
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Statistics:
Advertisements: Rx: 0, Tx: 0
Gratuitous ARP: Tx: 0
History
Release version Command history
Syntax
shutdown
no shutdown
Command Default
The interface is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no shutdown to enable the interface.
If you use in-band management only, you may choose to shut down the management interface (which is considered out of
band). When the management interface is shut down, all services (such as ping, scp, telnet, ssh, snmp, firmwaredownload, and
supportsave) through the management interface IP. Management interface shutdown is a persistent configuration, meaning that
the interface remains down after a system reboot or failover.
Examples
The following example disables an Ethernet interface.
History
Release version Command history
shutdown (STP)
Disables Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), Per-
VLAN Spanning Tree+ (PVST+), or Rapid PVST+ (R-PVST+) globally.
Syntax
shutdown
no shutdown
Command Default
STP is not enabled as it is not required in a loop-free topology.
Modes
Any of the supported spanning tree configuration modes (STP, RSTP, MSTP, PVST+, R-PVST+
Usage Guidelines
Enter no shutdown to re-enable any of the supported versions of STP.
Examples
To disable RSTP globally:
History
Release version Command history
site
Creates a remote Layer 2 extension site in a VXLAN overlay gateway context and enables VXLAN overlay gateway site
configuration mode.
Syntax
site name
no site name
Parameters
name
Site identifier. An ASCII character string up to 63 characters long, including the alphabet, numbers 0 through 9,
hyphens (-), and underscores (_).
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
The VXLAN overlay gateway type must first be configured for Layer 2 extension, by means of the type layer2-extension
command.
A "site" represents a remote fabric or the other end of the VXLAN tunnel. A site is associated with a "container," as data structure
that includes the destination IPv4 address of the tunnel, the switchport VLANs, and the administrative state.
Use the no site command with a specified name to remove the tunnel that corresponds to the site. Once you create the site
instance, you enter VXLAN overlay gateway site configuration mode, where you can configure other properties for the site. The
key commands available in this mode are summarized below.
TABLE 7 Key commands available in VXLAN overlay gateway site configuration mode
Command Description
Examples
The following example creates a VXLAN overlay gateway site and enter VXLAN overlay gateway site configuration mode.
History
Release version Command history
Syntax
snmp-sever access-enable vrf { all | vrf 1 [vrf-2 ...vrf-4default-vrf mgmt-vrf]}
By default, the SNMP server access is enabled for all VRF instances.
Parameters
all
Enables SNMP access to all VRF instances.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove SNMP server access from all or listed VRF instances.
The maximum number of VRFs (including the default VRF and mgmt VRF) supported for this feature is 6 .
NOTE
• You cannot enable access to specific VRF instances in the default configuration.
• You cannot enable access to all VRF instances when a list of VRF instances are listed in an existing
configuration.
During a software upgrade, SNMP server access is enbled for all VRFs instances.
Examples
The following example enables SNMP server access for VRF 1
History
Release version Command history
snmp-server community
Sets the community string and associates it with the user-defined group name to restrict the access of MIB for SNMPv1 and
SNMPv2c requests.
Syntax
snmp-server community string [ groupname name ]
Parameters
string
Specifies the community name string. Enter an alphanumeric string with 2 to 16 characters.
groupname name
Specifies the group name associated with the community name.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove the community string or the group from the community.
Examples
The following example adds the community string named public and associates the group name named user with it.
History
Release version Command history
snmp-server contact
Sets the SNMP server contact string.
Syntax
snmp-server contact string [ location string ] [ sys-descr string ]
Command Default
The default contact string is Field Support.
The default system description string is "Extreme BR-SLX9140 Switch" or "Extreme BR-SLX9240 Switch".
Parameters
string
Specifies the server contact. Enter an alphanumeric string from 4 to 255 characters. You must enclose the text in
double quotes if the text contains spaces.
location string
Specifies the SNMP server location string. Enter an alphanumeric string from 4 to 255 characters. You must enclose
the text in double quotes if the text contains spaces.
sys-descr string
Specifies the Management Information Base (MIB-2) object identifier (OID) system description. Enter an alphanumeric
string from 4 to 255 characters. You must enclose the text in double quotes if the text contains spaces.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to reset the default value.
Examples
The following example sets the SNMP server contact string to "Operator 12345".
History
Release version Command history
snmp-server context
Maps the context name in an SNMPv3 packet protocol data unit (PDU) to the name of a Virtual routing and forwarding (VRF)
instance.
Syntax
snmp-server context context_name [ vrf-name vrf_name ]
Parameters
context_name
Specifies the context name that is passed in the SNMP PDU.
vrf-name vrf_name
Specifies the VRF instance that can be retrieved when an SNMP request is sent with the context name.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to delete the SNMP server context.
For SNMPv1 and SNMPv2, you must also map the context with the community string. The SNMP agent supports 256
contexts to support context-to-VRF mapping.
For SNMPv3, you only need to map the context with the VRF. The SNMPv3 request PDU itself provisions for the context. Only
one context is allowed for each VRF instance.
ATTENTION
SNMP SET requests work only on the default VRF.
Examples
The following example configures an SNMP server context to a VRF for SNMPv1 or SNMPv2.
The following example configures an SNMP server context to a VRF for SNMPv3.
History
Release version Command history
Syntax
snmp-server enable trap
Command Default
The SNMP server traps are enabled by default.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to disable the SNMP traps.
Examples
The following example disables the SNMP traps.
History
Release version Command history
Syntax
snmp-server engineid local engine_id
Command Default
A default engine ID is generated during system start up.
Modes
Global configuration mode
Usage Guidelines
A reboot is necessary for the configured engine ID to become active.
Use the no form of the command to remove the configured engine ID from database.
Examples
The following example configures an engine ID for the SNMP agent.
The following example removes the configured engine ID from the database.
History
Release version Command history
snmp-server group
Creates user-defined groups for SNMPv1/v2/v3 and configures read, write, and notify permissions to access the MIB view.
Syntax
snmp-server group groupname { v1 | v2c | v3 } [ read viewname ] [ write viewname ] [ notify viewname ]
no snmp-server group groupname { v1 | v2c | v3 } [ read viewname ] [ write viewname ] [ notify viewname ]
Parameters
groupname
Specifies the name of the SNMP group to be created.
v1 | v2c | v3
Specifies the version of SNMP.
read viewname
Specifies the name of the view that enables you to provide read access.
write viewname
Specifies the name of the view that enables you to provide both read and write access.
notify viewname
Specifies the name of the view that enables you to provide access to the MIB for trap or inform.
Modes
Global configuration mode
Usage Guidelines
Maximum number of SNMP groups supported is 10.
Examples
The following example creates SNMP server group entries for SNMPv3 user group.
History
Release version Command history
snmp-server host
Configures the SNMP trap server host attributes.
Syntax
snmp-server host { ipv4_host | ipv6_host | dns_host } community_string [ version { 1 | 2c } ] [ udp-port port ] [ severity-level |
{ none | debug | info | warning | error | critical } ] [ use-vrf vrf-name ]
no snmp-server host { ipv4_host | ipv6_host | dns_host } community_string [ version { 1 | 2c } ] [ udp-port port ] [ severity-
level | { none | debug | info | warning | error | critical } ] [ use-vrf vrf-name]
Parameters
{ ipv4_host | ipv6_host | dns_host }
Specifies the IP address of the host. IPv4, IPv6, and DNS hosts are supported.
community_string
Specifies the community string associated with the host entry. The number of characters available for the string ranges
from 1 through 64.
version { 1 | 2c }
Selects version 1 or 2c traps to be sent to the specified trap host.
udp-port port
Specifies the UDP port where SNMP traps will be received. Valid port IDs range from 0 through 65535. The default
port is 162.
use-vrf vrf-name
Specifies a VRF though which to communicate with the SNMP host. By default, all management services are enabled
on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
Modes
Global configuration mode
Usage Guidelines
This command sets the trap destination IP addresses and SNMP version, associates a community string with a trap host (for v1
and v2c) and specifies the UDP destination port where SNMP traps will be received.
To configure SNMP trap hosts associated with community strings, you must create the community string using the snmp-
server community command before configuring the host.
The host supports six communities and their associated trap recipients and trap recipient severity levels. The default value for
the trap recipient of each community is 0.0.0.0. The length of the community string should be between 2 and 64 characters.
The no snmp-server host host community-string string version 2c command brings version 2c down to version 1.
The no snmp-server host host community-string string command removes the SNMP server host from the device
configuration altogether.
Examples
The following example creates an entry for trap host 1050:0:0:0:5:600:300c:326b associated with community “public.” The
trap host receives traps from the configured device.
The following example creates an entry for trap host host1.example.com associated with community “public.” The trap host
receives traps from the configured device.
The following example associates “commaccess” as a read-only community and set 10.32.147.6 as a trap recipient with
SNMP version 2c on target port 162.
The following example creates a trap host (10.23.23.45) associated with the community “public”, which will receive all traps with
the severity level of Info.
History
Release version Command history
snmp-server location
Sets the SNMP server location string.
Syntax
snmp-server location string [ contact string ] [ sys-descr string ]
Command Default
The default location string is End User Premise.
The default system description string is "Extreme BR-SLX9140 Switch" or "Extreme BR-SLX9240 Switch".
Parameters
contact string
Specifies the server contact. Enter an alphanumeric string from 4 to 255 characters. You must enclose the text in
double quotes if the text contains spaces.
sys-descr string
Specifies the Management Information Base (MIB-2) object identifier (OID) system description. Enter an alphanumeric
string from 4 to 255 characters. You must enclose the text in double quotes if the text contains spaces.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to reset the default value.
Examples
The following example sets the SNMP server location string to "Building 3 Room 214".
History
Release version Command history
Syntax
snmp-server mib community-map community-name context context-name
Parameters
community-name
Specifies an SNMP community name.
context context-name
Specifies an SNMP context.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove a community string and its associated context name.
Any incoming SNMPv1/v2c requests with the specified community name uses the context name specified by this command.
The context name can be used in SNMP requests for "inetCidrRouteTable". One community can be mapped to only one
context. However, a single context can be mapped to multiple communities.
Before mapping the community to context, a valid context should be configured by using the snmp-server context command
and a valid community string should be configured by using the snmp-server community command.
Examples
The following example maps an SNMP community string to a context name.
The following example removes an SNMP community string and its associated context name.
History
Release version Command history
snmp-server sys-descr
Sets the Management Information Base (MIB-2) object identifier (OID) system description.
Syntax
snmp-server sys-descr string [ contact string ] [ location string ]
Command Default
The default system description string is "Extreme BR-SLX9140 Switch" or "Extreme BR-SLX9240 Switch".
The default contact string is Field Support.
Parameters
string
Specifies the system description. Enter an alphanumeric string from 4 to 255 characters. You must enclose the text in
double quotes if the text contains spaces.
contact string
Specifies the server contact. Enter an alphanumeric string from 4 to 255 characters. You must enclose the text in
double quotes if the text contains spaces.
location string
Specifies the SNMP server location string. Enter an alphanumeric string from 4 to 255 characters. You must enclose
the text in double quotes if the text contains spaces.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to reset the default value.
Examples
The following example sets the system description OID to "Extreme Cluster device".
History
Release version Command history
snmp-server user
Creates or changes the attributes of SNMPv3 users, and allows the SNMPv3 user to be associated with the user-defined group
name.
Syntax
snmp-server user username [ groupname group-name ] [ auth { md5 | sha | noauth } ] [ auth-password string [ encrypted ] ]
[ priv { DES | AES128 | nopriv } ] [ priv-password string [ encrypted ]
no snmp-server user username [ groupname group-name ] [ auth { md5 | sha | noauth } ] [ auth-password string
[ encrypted ] ] [ priv { DES | AES128 | nopriv } ] [ priv-password string [ encrypted ] ]
Parameters
username
The name of the user that connects to the agent. The name must be between 1 and 16 characters long.
groupname group-name
The name of the group to which the user is associated. The configured user is allowed to be associated with the user-
defined groups created using the snmp-server group command.
auth
Initiates an authentication level setting session. The default level is noauth .
noauth
Specifies "No Authentication Protocol".
md5
The HMAC-MD5-96 authentication level.
sha
The HMAC-SHA-96 authentication level.
auth-password string
A string that enables the agent to receive packets from the host. Passwords are plain text and must be added each
time for each configuration replay. The password must be between 1 and 32 characters long.
priv
Initiates a privacy authentication level setting session. The default level is nopriv .
DES
Specifies the DES privacy protocol.
AES128
Specifies the AES128 privacy protocol.
nopriv
Specifies "No Privacy Protocol".
priv-password string
Specifies a string (not to exceed 32 characters) that enables the host to encrypt the contents of the message that it
sends to the agent. Passwords are plain text and must be added each time for each configuration replay. The privacy
password alone cannot be configured. You configure the privacy password with the authentication password.
encrypted
Encrypts the input for auth/priv passwords. The encrypted key should be used only while entering the encrypted auth/
priv passwords.
Modes
Global configuration mode
Usage Guidelines
This command configures SNMPv3 users that can also be associated with a trap and inform response functionality. This
command also allows configured user to be associated with user-defined SNMP groups created using the snmp-server group
command. The maximum number of SNMP users that can be configured is 10. Optional encryption for auth-password and
priv-password is also provided.
When creating a new SNMPv3 user without group name, by default there is no group name mapped with the SNMPv3 user.
You must map the configured SNMPv3 user with any non-existing or existing group name available in the group CLI
configuration to contact the device through SNMPv3.
This command may not be successful where encrypted passwords are generated by third-party or open-source tools.
Examples
The following example configures a basic authentication policy.
The following example creates the SNMP users "user1" and "user2" associated with used-defined group "group1" under global
configuration mode.
History
Release version Command history
snmp-server v3host
Specifies the host recipient for SNMPv3 trap notification.
Syntax
snmp-server v3host { ipv4_host | ipv6_host | dns_host } user_name [ notifytype { traps | informs } ] [ engineid engine-id ]
[ udp-port port_number ] [ severity-level | { none | debug | info | warning | error | critical } ] [ use-vrf { vrf-name } ]
no snmp-server v3host { ipv4_host | ipv6_host | dns_host } user_name [ notifytype {traps | informs}] [ engineid engine-id ]
[ udp-port port_number ] [ severity-level | {none | debug | info | warning | error | critical } ] [ use-vrf { vrf-name } ]
Parameters
ipv4_host | ipv6_host | dns_host
Specifies the IP address of the host. IPv4, IPv6, and DNS hosts are supported.
user_name
Specifies the SNMPv3 user name to be associated with the SNMPv3 host entry.
engineID engine-id
Configures the remote engine ID to receive informs on a remote host.
udp-port port_number
Specifies the UDP port of the host. The default UDP port number is 162.
use-vrf vrf-name
Configures SNMP to use the specified VRF to communicate with the host. The default is mgmt-vrf.
Modes
Global configuration mode
Usage Guidelines
You can associate a global SNMPv3 host only with global SNMPv3 users and the local SNMPv3 host only with local SNMPv3
users. You cannot create a SNMPv3 host by associating with the local SNMPv3 users and vice versa.
Examples
The following example creates an entry for SNMPv3 trap IPv4 host 10.23.23.45 associated with SNMP user "snmpadmin1."
The following example creates an entry for SNMPv3 trap IPv6 host 1050:0:0:0:5:600:300c:326b associated with SNMP user
"snmpadmin2." The trap host receives SNMPv3 traps from the configured device.
The following example associates the default-vrf VRF for a trap host recipient.
History
Release version Command history
snmp-server view
Creates a view entry with MIB object IDs to be included or excluded for user access.
Syntax
snmp-server view view-name mib_tree { included | excluded }
Parameters
view-name
Specifies the alphanumeric name to identify the view. The name should not contain spaces.
mib_tree
Specifies the MIB object ID called Object Identifiers (OIDs) that represent the position of the object or sub-tree in the
MIB hierarchy.
included | excluded
Specifies whether the specified MIB object ID must be included in the view or excluded from the view.
Modes
Global configuration mode
Usage Guidelines
The maximum number of views supported with MIB tree entries is 10. Either a single view name associated with 10 different
MIB object IDs or 10 different view names associated with each one of the MIB object IDs is allowed.
Examples
The following example creates an SNMP view entry "view1" with excluded permission for the MIB object ID "1.3.6.1.2.1.1.3."
The following example creates an SNMP view entry "view2" with included permission for the MIB object ID "1.3.6.1."
The following example removes the SNMP view entry "view1" from the configuration list.
History
Release version Command history
Syntax
snmp trap link-status disable { ethernetslot/port | loopback port | port-channel channel | ve vlan-id }
no snmp trap link-status disable { ethernetslot/port | loopback port | port-channel channel | ve vlan-id }
By default, the SNMP trap for link-status is enabled for all interfaces.
Parameters
ethernet slot/port
Specifies a physical Ethernet interface and a valid slot and port number.
loopback port
Specifies a loopback interface and a valid port number.
port-channel channel
Specifies a port-channel.
ve vlan-id
Specifies a virtual interface.
Modes
Interface sub-mode
Usage Guidelines
Use the no form of this command to enable SNMP traps for the interface link-status change. Use the show running-config
interface command to view the SNMP traps link-status. SNMP traps are disabled for "Ethernet 0/1" and Ethernet 0/2" and by
default enabled for "Ethernet 0/3" and "Ethernet 0/4". SNMP traps are disabled for Port-channel 21 and 22 and by default
enabled for Port-channel 23. SNMP traps are disabled for Loopback 11 and 12 and by default enabled for loopback 13.
SNMP traps are disabled for VE 1 and 2 and by default enabled for VE 3.
Examples
The following example displays the SNMP traps are disabled for "Ethernet 0/1" and Ethernet 0/2". Enabled by default for
"Ethernet 0/3" and "Ethernet 0/4" :
The following example displays the SNMP traps are disabled for Port-channel 21 and 22. Enabled by default for Port-channel
23:
interface Port-channel 21
snmp trap link-status disable
shutdown
!
interface Port-channel 22
snmp trap link-status disable
shutdown
!
interface Port-channel 23
shutdown
!
The following example displays the SNMP traps are disabled for Loopback 11 and 12. Enabled by default for loopback 13:
interface Loopback 12
snmp trap link-status disable
shutdown
!
interface Loopback 13
shutdown
!
The following example displays the SNMP traps are disabled for VE 1 and 2. Enabled by default for VE 3:
interface Ve 2
snmp trap link-status disable
shutdown
!
interface Ve 3
shutdown
!
History
Release version Command history
source
Configures the monitoring session.
Syntax
source [ ethernet slot/port | destination | direction [ rx | tx | both ]
Parameters
ethernet
Represents a valid, physical Ethernet interface.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
destination
Use this parameter to specify the interface.
direction rx
Specifies to monitor the receiving traffic.
direction tx
Specifies to monitor the transmitting traffic
direction both
Specifies to monitor transmitting and receiving traffic.
Modes
Monitor session configuration mode
Usage Guidelines
Enter no source followed by the identifying parameters to delete the port mirroring connection for the specified interface.
Examples
To enable session 22 for monitoring traffic:
History
Release version Command history
source-ip
Configures the source IPv4 address of Precision Time Protocol (PTP) packets.
Syntax
source-ip IP-address
no source-ip
Command Default
See Parameters.
Parameters
ip-address
Source IPv4 address of PTP packets. The default is 0.0.0.0.
Modes
PTP configuration mode
Usage Guidelines
This command configures the source IPv4 address for all PTP packets, and is switch specific. The IPv4 address is required to
support unicast communication between master and slave clocks.
Use the no form of this command to revert to the default source IPv4 address.
Examples
To configure a nondefault source IPv4 address:
History
Release version Command history
span session
Configures the SPAN session.
Syntax
span session session_id
Parameters
session_id
Designates the session number for the flow-based SPAN session.
Modes
Policy class configuration mode
Usage Guidelines
Use the no span session session-id command to delete the session.
Examples
The following example configures a SPAN session.
History
Release version Command history
spanning-tree autoedge
Enables automatic edge detection.
Syntax
spanning-tree autoedge
no spanning-tree autoedge
Command Default
Auto detection is not enabled.
Modes
Interface configuration mode
Usage Guidelines
The port can become an edge port if no Bridge Protocol Data Unit (BPDU) is received.
Examples
To enable automatic edge detection:
History
Release version Command history
spanning-tree bpdu-mac
Sets the MAC address of the Bridge Protocol Data Unit (BPDU).
Syntax
spanning-tree bpdu-mac [ 0100.0ccc.cccd | 0304.0800.0700 ]
Parameters
0100.0ccc.cccd
Cisco Control Mac
0304.0800.0700
Brocade Control Mac
Modes
Interface configuration mode
Usage Guidelines
This command will only take effect when the protocol is PVST+ or R-PVST+.
The PVST+ and R-PVST+ protocols are supported. The PVST and R-PVST protocols—proprietary to Cisco—are not supported.
Examples
The following example sets the MAC address of the BPDU.
History
Release version Command history
spanning-tree cost
Changes an interface's spanning-tree port path cost.
Syntax
spanning-tree cost cost
Command Default
The default path cost is 200000000.
Parameters
cost
Specifies the path cost for the Spanning Tree Protocol (STP) calculations. Valid values range from 1 through
200000000.
Modes
Interface configuration mode
Usage Guidelines
Lower path cost indicates a greater chance of becoming root.
Examples
To set the port cost to 128:
History
Release version Command history
spanning-tree edgeport
Enables the edge port on an interface to allow the interface to quickly transition to the forwarding state.
Syntax
spanning-tree edgeport [ bpdu-guard ]
Command Default
Edge port is disabled.
Parameters
bpdu-guard
Guards the port against the reception of BPDUs.
Modes
Interface subtype configuration mode
Usage Guidelines
This command is only for RSTP and MSTP. Use the spanning-tree portfast command for STP.
Note the following details about edge ports and their behavior:
• A port can become an edge port if no BPDU is received.
• A port must become an edge port before it receives a BPDU.
• When an edge port receives a BPDU, it becomes a normal spanning-tree port and is no longer an edge port.
• Because ports directly connected to end stations cannot create bridging loops in the network, edge ports directly
transition to the forwarding state, and skip the listening and learning states.
Examples
To enable a port to quickly transition to the forwarding state:
History
Release version Command history
Syntax
spanning-tree guard root [ vlan vlan_id ]
Command Default
Guard root is disabled.
Parameters
vlan vlan_id
Specifies a VLAN.
Modes
Interface configuration mode
Usage Guidelines
Guard root protects the root bridge from malicious attacks and unintentional misconfigurations where a bridge device that is not
intended to be the root bridge becomes the root bridge. This causes severe bottlenecks in the data path. Guard root ensures
that the port on which it is enabled is a designated port. If the guard root enabled port receives a superior Bridge Protocol Data
Unit (BPDU), it goes to a discarding state.
If the VLAN parameter is not provided, the guard root functionality is applied globally for all per-VLAN instances. But for the
VLANs which have been configured explicitly, the per-VLAN configuration takes precedence over the global configuration.
The root port provides the best path from the switch to the root switch.
Examples
To enable guard root:
History
Release version Command history
spanning-tree link-type
Enables and disables the rapid transition for the Spanning Tree Protocol (STP).
Syntax
spanning-tree link-type [ point-to-point | shared ]
Command Default
Rapid transition is enabled for STP.
Parameters
point-to-point
Enables rapid transition.
shared
Disables rapid transition.
Modes
Interface subtype configuration mode
Usage Guidelines
This command overrides the default setting of the link type.
Examples
To specify the link type as shared:
History
Release version Command history
spanning-tree portfast
Enables the Port Fast feature on an interface to allow the interface to quickly transition to forwarding state.
Syntax
spanning-tree portfast [ bpdu-guard ]
Command Default
Port Fast is disabled.
Parameters
bpdu-guard
Guards the port against the reception of BPDUs.
Modes
Interface subtype configuration mode
Usage Guidelines
This command is applicable the only for the Spanning Tree Protocol (STP). Port Fast immediately puts the interface into the
forwarding state without having to wait for the standard forward time. Use the spanning-tree edgeport command for MSTP and
RSTP.
BPDU guard disables all portfast-enabled ports should they ever receive BPDU frames. It does not prevent transmitting of
BPDU frames.
If you enable spanning-tree portfast bpdu-guard on an interface and the interface receives a BPDU, the software disables the
interface and puts the interface in the ERR_DISABLE state.
Enable Port Fast on ports connected to host. Enabling Port Fast on interfaces connected to switches, bridges, hubs, and so on
can cause temporary bridging loops, in both trunking and nontrunking mode.
Examples
To enable a port to quickly transition to the forwarding state:
History
Release version Command history
spanning-tree priority
Changes an interface's spanning-tree port priority.
Syntax
spanning-tree priority priority
no spanning-tree priority
Command Default
The default value is 128.
Parameters
priority
Specifies the interface priority for the spanning tree. The range of valid values is from 0 through 240. Port priority is in
increments of 16.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no spanning-tree priority to return to the default setting.
Examples
To configure the port priority to 16:
History
Release version Command history
spanning-tree restricted-role
Restricts the role of the port from becoming a root port.
Syntax
spanning-tree restricted-role
no spanning-tree restricted-role
Command Default
The restricted role is disabled.
Modes
Interface configuration mode
Usage Guidelines
Enter no spanning-tree restricted-role to return to the default setting.
Examples
To configure the port from becoming a root port:
History
Release version Command history
spanning-tree restricted-tcn
Restricts the Topology Change Notification (TCN) Bridge Protocol Data Units (BPDUs) sent on the port.
Syntax
spanning-tree restricted-tcn
no spanning-tree restricted-tcn
Command Default
The restricted TCN is disabled.
Modes
Interface configuration mode
Usage Guidelines
Enter no spanning-tree restricted-tcn to disable this parameter.
Examples
To restrict the TCN on a specific interface:
History
Release version Command history
spanning-tree shutdown
Enables or disables spanning tree on the interface or VLAN.
Syntax
spanning-tree shutdown
no spanning-tree shutdown
Command Default
Spanning tree is disabled by default.
Modes
Interface (Ethernet or VLAN) configuration mode
Usage Guidelines
Enter no spanning-tree shutdown to enable spanning tree on the interface or VLAN.
Once all of the interfaces have been configured for a VLAN, you can enable Spanning Tree Protocol (STP) for all members of
the VLAN with a single command. Whichever protocol is currently selected is used by the VLAN. Only one type of STP can be
active at a time.
A physical interface (port) can be a member of multiple VLANs. For example, a physical port can be a member of VLAN 1002
and VLAN 55 simultaneously. In addition, VLAN 1002 can have STP enabled and VLAN 55 can have STP disabled
simultaneously.
Vlan 1002 can not be enabled with the spanning-tree shutdown command.
Examples
To disable spanning tree on a specific interface:
History
Release version Command history
speed (Ethernet)
Sets the speed negotiation value on an Ethernet interface.
Syntax
SLX 9140 (ports 1-48): speed { 1000 | 10000 | 25000 | auto}
Command Default
The default speed of the port.
SLX 9140: 10Gbps is the default speed of the first 48 ports. For the last 6 ports, the default speed is 100Gbps.
Parameters
1000
Forces the speed to 1 Gbps.
10000
Forces the speed to 10 Gbps.
25000
Forces the speed to 25 Gbps.
40000
Forces the speed to 40Gbps.
100000
Forces the speed to 100 Gbps.
auto
Allows the interface to configured the speed based on the detected optic type.
Modes
Interface subtype configuration mode
Usage Guidelines
SLX 9140 port management includes the following:
• Supports 54 ports in total. The first 48 ports support 10G and 25G speed (default is10G). Breakout is not supported.
• The last 6 ports support 40G and 100G (default 100G) and breakout is supported.
• Forward Error Correction (FEC) is supported for 25G and 100G speed.
Examples
The following example changes the speed to 100G.
History
Release version Command history
speed (LAG)
Sets the allowed speed of member links that can be added in the LAG. Member links with speed other than the configured
value will be administratively shut down.
Syntax
speed { 1000 | 10000 | 25000 | 40000 | 100000 }
Command Default
Speed is 100000
Parameters
1000
Forces the speed to 1 Gbps.
10000
Forces the speed to 10 Gbps.
25000
Forces the speed to 25 Gbps.
40000
Forces the speed to 40 Gbps.
100000
Forces the speed to 100 Gbps.
Modes
Port-channel interface configuration mode
Usage Guidelines
Configuring member ports with different speed under a LAG is allowed. However, the interfaces that come up with non-
matching port speed are brought down with speed mismatch exception.
Examples
The following example sets the speed on the LAG interface as 10 Gbps.
History
Release version Command history
ssh
Connects to a remote server by means of the Secure Shell (SSH) protocol.
Syntax
ssh {IP_address | hostname } [ -c | -l | -m | interface {ethernet slot/port | management | ve vlan-id } | vrf vrf-name ]}
Command Default
SSH connects to port 22.
Parameters
IP_address
Specifies the server IP address in IPv4 or IPv6 format.
hostname
Specifies the host name, a string from 1 through 253 characters.
-c
Specifies the encryption algorithm for the SSH session. This parameter is optional; if no encryption algorithm is
specified, the default (3des) is used. Supported algorithms include the following:
3des
Triple Data Encryption Standard (DES). This is the default setting.
aes128-cbc
AES 128-bits
aes192-cbc
AES 192-bits
aes256-cbc
AES 256-bits
-l username
Login name for the remote server. This parameter is optional. If you specify a user name, you will be prompted for a
password. If you do not specify a user name, the command assumes you are logging in as root and will prompt for the
root password.
-m
Specifies the HMAC (Hash-based Message Authentication Code) message encryption algorithm. This parameter is
optional; if no encryption algorithm is specified, the default (hmac-md5) is used. Supported algorithms include the
following:
hmac-md5
MD5 128-bits. This is the default setting.
hmac-md5-96
MD5 96-bits
hmac-sha1
SHA1 160-bits
hmac-sha1-96
SHA1 96-bits
interface
Specifies an interface.
ethernet slot/port
Specifies an Ethernet interface slot and port number. The v valid value is 0.
management
Specifies a management interface.
ve vlan-id
Range is from 1 through 4096.
vrf vrf-name
Specifies a VRF instance. See the Usage Guidelines.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to establish an encrypted SSH connection from a switch to a remote networking device. This
implementation is based on SSH v2.
To use the ssh command on the management VRF, use the vrf keyword and enter mgmt-vrf manually.
Examples
To connect to a remote device using an SSH connection with default settings:
To connect to a remote device using an SSH connection with the management VRF:
admin@127.2.1.8's password
History
Release version Command history
Syntax
ssh client cipher string
Parameters
string
The string name of the cipher, in a non-cbc or comma separated list of supported cipher algorithms such as 3des-
cbc,aes192-cbc,aes128-ctr,aes192-ctr, and so on.
Modes
Global configuration mode
Usage Guidelines
Use the no ssh client cipher command remove the cipher list from the ssh client.
Examples
Sets the SSH client's cipher list.
History
Release version Command history
Syntax
ssh client cipher non-cbc
Modes
Global configuration mode
Usage Guidelines
Use the no ssh client cipher non-cbc command remove the non-cbc cipher list from the ssh client.
Examples
Sets the SSH client's cipher list to non-cbc ciphers.
History
Release version Command history
Syntax
ssh client key-exchange diffie-hellman-group14-sha1
Command Default
This command is not configured by default.
Modes
Global configuration mode
Usage Guidelines
You can configure the SSH client key-exchange method to DH Group 14. When the ssh client key-exchange method is
configured to DH Group 14, the SSH connection from a remote SSH client is allowed only if the key-exchange method at the
client end is also configured to DH Group 14. Enter no ssh client key-exchange to restore ssh client key-exchange to the
default value.
For backward compatibility, the string "dh-group-14" is also acceptable in place of "diffie-hellman-group14-sha1"
Examples
To set ssh client key-exchange to DH Group 14:
History
Release version Command history
Syntax
ssh client mac string
Command Default
SSH server is enabled by default.
Parameters
string
The string name of the default MAC required. Your choices are hmac-md5, hmac-sha1, hmac-sha2-256, and hmac-
sha2-512. The default MACs supported in FIPS mode are hmac-sha1, hmac-sha2-256, and hmac-sha2-512.
Modes
Global configuration mode
Usage Guidelines
The MAC hmac-md5 is not supported in FIPS mode.
Examples
Typical command example:
History
Release version Command history
Syntax
ssh server cipher string
Parameters
string
The string name of the cipher, in a non-cbc or comma separated list of supported cipher algorithms such as 3des-
cbc,aes192-cbc,aes128-ctr,aes192-ctr, and so on.
Modes
Global configuration mode
Usage Guidelines
Use the no ssh server cipher command remove the cipher list from the ssh client.
Examples
Sets the SSH server's cipher list.
History
Release version Command history
Syntax
ssh server cipher non-cbc
Modes
Global configuration mode
Usage Guidelines
Use the no ssh server cipher non-cbc command remove the non-cbc cipher list from the ssh client.
Examples
Sets the SSH server's cipher list to non-cbc ciphers.
History
Release version Command history
Syntax
ssh server key { dsa | rsa [1024 | 2048 ] | ecdsa 256 }
Command Default
The default values of SSH keys are:
• DSA is active
• ECDSA value is 256
• RSA value is 2048
Parameters
dsa
Generates the DSA key.
ecdsa 256
Generates the ECDSA key at 256 bits.
Modes
Global configuration mode
Usage Guidelines
The no ssh server key command zeroizes the SSH keys on the device.
If you generate and delete SSH crypto keys, you must restart the SSH server using the no ssh server shutdown command to
enable the configuration.
Examples
This example generates a DSA key:
History
Release version Command history
Syntax
ssh server key-exchange diffie-hellman-group14-sha1
Command Default
This command is not configured by default.
Modes
Global configuration mode
Usage Guidelines
You can configure the SSH server key-exchange method to DH Group 14. When the SSH server key-exchange method is
configured to DH Group 14, the SSH connection from a remote SSH client is allowed only if the key-exchange method at the
client end is also configured to DH Group 14. Enter no ssh server key-exchange to restore SSH server key-exchange to the
default value.
For backward compatibility, the string "dh-group-14" is also acceptable in place of "diffie-hellman-group14-sha1"
Examples
To set SSH server key-exchange to DH Group 14:
History
Release version Command history
Syntax
ssh server mac string
Parameters
string
The string name of the default MAC required. Your choices are hmac-md5, hmac-sha1, hmac-sha2-256, and hmac-
sha2-512. The default MACs supported in FIPS mode are hmac-sha1, hmac-sha2-256, and hmac-sha2-512.
Modes
Global configuration mode
Usage Guidelines
The MAC hmac-md5 is not supported in FIPS mode.
Examples
Typical command example:
History
Release version Command history
Syntax
ssh server rekey-interval interval
Parameters
interval
The value for the rekey interval. Range is from 900 to 3600 seconds.
Modes
Global configuration mode
Usage Guidelines
Use the no ssh server rekey-interval command to reset the rekey-interval to the default value.
Examples
To set the SSH server rekey interval to 1200 seconds:
History
Release version Command history
Syntax
ssh server [ use-vrf vrf-name ] shutdown
Parameters
use-vrf vrf-name
Specifies a user-defined VRF, or built-in VRFs such as mgmt-vrf or default-vrf.
Modes
Global configuration mode
Usage Guidelines
Enter no ssh server shutdown to enable SSH service.
The use of the use-vrf keyword brings down the server only for the specified VRF. The user can shut down any server in any
VRF, including the management and default VRF.
When this command is executed and a VRF is not specified by means of the use-vrf keyword, the server is brought down only
in the management VRF ("mgmt-vrf") (the default VRF for this command).
Examples
To shut down SSH service on the management VRF:
History
Release version Command history
start-shell
Accesses the SLXVM Linux shell from the SLX-OS CLI.
Syntax
start-shell
Modes
Privileged EXEC mode
Usage Guidelines
This command is only available for users with admin-level permissions.
You can also run this command from Global configuration mode: device(config)# do start-shell.
Inside the SLXVM Linux shell, you can escalate your privileges to root access, by using the su root Linux command. Escalation
to root access is password protected.
Inside the SLXVM Linux shell, execution of root privilege commands using sudo is not supported.
The idle timeout of Linux shell sessions is five minutes, after which you are automatically logged out of the Linux shell and
returned to the SLX-OS CLI.
Examples
The following example accesses the SLXVM Linux shell from the SLX-OS CLI.
device# start-shell
Entering Linux shell for the user: admUser
[admUser@SLX]#
The following example escalates access from the default SLXVM Linux shell to root.
[admUser@SLX]# su root
Password:
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
In the following example, the Linux ps -ef command lists the process status.
[admUser@SLX]# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Jul24 ? 00:00:04 /sbin/init
root 2 0 0 Jul24 ? 00:00:00 [kthreadd]
root 3 2 0 Jul24 ? 00:00:00 [migration/0]
root 4 2 0 Jul24 ? 00:00:03 [ksoftirqd/0]
root 5 2 0 Jul24 ? 00:00:00 [migration/1]
root 6 2 0 Jul24 ? 00:00:03 [ksoftirqd/1]
root 7 2 0 Jul24 ? 00:00:00 [migration/2]
root 8 2 0 Jul24 ? 00:00:02 [ksoftirqd/2]
root 9 2 0 Jul24 ? 00:00:00 [migration/3]
root 10 2 0 Jul24 ? 00:00:02 [ksoftirqd/3]
root 11 2 0 Jul24 ? 00:00:00 [migration/4]
root 12 2 0 Jul24 ? 00:00:02 [ksoftirqd/4]
root 13 2 0 Jul24 ? 00:00:00 [migration/5]
root 14 2 0 Jul24 ? 00:00:03 [ksoftirqd/5]
root 27 2 0 Jul24 ? 00:00:00 [cpuset]
root 28 2 0 Jul24 ? 00:00:01 [khelper]
root 31 2 0 Jul24 ? 00:00:00 [netns]
root 34 2 0 Jul24 ? 00:00:00 [async/mgr]
root 270 2 0 Jul24 ? 00:00:00 [sync_supers]
root 272 2 0 Jul24 ? 00:00:00 [bdi-default]
...
The following example exits a root-level user to the SLXVM Linux shell.
[root@SLX]# exit
exit
[admUser@SLX]#
The following example exits from the SLXVM Linux shell to the SLX-OS CLI.
[admUser@SLX]# exit
exit
Exited from Linux shell
device#
History
Release version Command history
static-network
Configures a static BGP4 network, creating a stable network in the core.
Syntax
static-network network/mask [ distance num ]
Parameters
network/mask
Network and mask in CIDR notation.
distance num
Specifies an administrative distance value for this network. Valid values range from 1 through 255. The default is 200.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
While a route configured with this command will never flap unless it is deleted manually, a static BGP4 network will not interrupt
the normal BGP4 decision process on other learned routes that are installed in the Routing Table Manager (RTM).
Consequently, when there is a route that can be resolved, it will be installed into the RTM.
Examples
The following example configures a static network and sets an administrative distance of 300.
History
Release version Command history
Syntax
statistics
no statistics
Parameters
None
Command Default
Statistics are disabled.
Modes
Bridge-domain configuration mode.
Usage Guidelines
The no form of the command disables statistics on the bridge domain.
Examples
The following example shows how to enable ingress and egress statistics on bridge domain 2.
History
Release version Command history
statistics (VLAN)
Enables statistics on a VLAN.
Syntax
statistics
no statistics
Command Default
Statistics are disabled.
Parameters
None
Modes
VLAN configuration mode
Usage Guidelines
The no form of the command disables statistics on a VLAN.
Examples
The following example shows how to enable statistics on VLAN 10.
History
Release version Command history
statistics-enable
Enables statistics for a policy-based forwarding (PBF) destination
Syntax
statistics-enable
Command Default
Statistics are not maintained for the PBF destination.
Modes
PBF-destination configuration mode
Usage Guidelines
The use-case for this command is under Network Packet Broker (NPB) system-mode.
The software limits the number of statistics-enabled PBF destinations per NPB-grid to 2000.
Examples
The following example enables statistics for a PBF destination.
History
Release version Command history
storm-control ingress
Limits ingress traffic on a specified interface.
Syntax
storm-control ingress { broadcast | unknown-unicast | multicast } { limit-bps | limit-percent } rate [ { monitor | shutdown ] }
no storm-control ingress { broadcast | unknown-unicast | multicast } { limit-bps | limit-percent } rate [ { monitor | shutdown ] }
Parameters
broadcast
Specifies that the command will operate on broadcast traffic only.
unknown-unicast
Specifies that the command will operate on unknown-unicast traffic only.
multicast
Specifies that the command will operate on multicast traffic only.
limit-bps
Specifies that the value given to the rate parameter is in bits per second. If the traffic on the interface reaches this rate,
no more traffic (for the traffic type specified) is allowed on the interface.
limit-percent
Specifies that the value given to the rate parameter is in percentage of capacity of the interface. If the traffic on the
interface reaches this percentage of capacity, no more traffic (for the traffic type specified) is allowed on the interface.
rate
Specifies the amount of traffic allowed, either in bits per second or a percentage of the capacity of the
interface, depending on which parameter was chosen with the rate.
• Range if you are specifying rate in bps: 0 to 10000000000. Because each application-specific integrated circuit
(ASIC) may support different bit granularity, bit rates are rounded up to the next achievable rate.
• Range if you are specifying rate in percent of interface capacity: 0 to 100.
monitor
Specifies that, if a rate limit is reached within a five-second sampling period, a log message gets sent. A log message
is generated upon the first occurrence of such an event. Subsequent log messages are generated only at the end of
one complete sample interval in which no rate limits are reached.
shutdown
Specifies that, if a rate limit is exceeded within a five-second sampling period, the interface will be shut down. You must
manually re-enable the interface after a shutdown.
Modes
Interface configuration mode
Usage Guidelines
This command limits the amount of broadcast, unknown unicast, and multicast (BUM) ingress traffic on a specified interface.
The shutdown parameter monitors the status of the configured rate limit every five seconds, and if the maximum defined rate is
exceeded the corresponding interface is shut down until you re-enable it using the no shut command.
If you want to modify an active BUM storm control configuration, you must first disable it, then issue the storm-control ingress
command again with the new parameters.
Enter no storm-control ingress to disable BUM storm control for a particular traffic type on an interface.
Examples
To configure storm control on an Ethernet interface, with a rate limited to 1000000 bps:
History
Release version Command history
strip-802-1br
Removes 802.1BR headers from incoming packets, for forwarding to the next processing port—for further filtering and
forwarding.
Syntax
strip-802-1br
no strip-802-1br
Command Default
802.1BR header stripping is disabled.
Modes
Ethernet interface configuration mode
Usage Guidelines
This feature applies to both IPv4 and IPv6 traffic.
• The default header-mode—802.1BR—must be enabled. If VN-Tag header-mode is enabled, restore 802.1BR mode:
If a tunneled frame has an 802.1BR tag in the outer L2 header, VXLAN, NVGRE, ERSPAN, or L2-over-MPLS/pseudo-wire
header-stripping also deletes the 802.1BR tag. (802.1BR tags in the inner L2 header are not supported.)
If both MPLS and 802.1BR header-stripping are configured, MPLS is always implemented. However, details vary between IP-
over-MPLS and L2-over-MPLS regarding 802.1BR tags:
• Under IP-over-MPLS, only the MPLS labels are stripped; 802.1BR tags are not affected. The header diagram for this
case is as follows:
• Under L2-over-MPLS (pseudo-wire), both the outer L2 (with 802.1BR tag) and the MPLS header are stripped. The
header diagram for this case is as follows:
If interfaces with header-stripping enabled are included in a port-channel, the header stripping remains enabled, but only for
traffic entering those interfaces.
Examples
The following example enables 802.1BR header-stripping on the interface.
History
Release version Command history
strip-vn-tag
Removes Virtual NIC (VN)-tag headers from incoming packets, for forwarding to the next processing port—for further filtering
and forwarding.
Syntax
strip-vn-tag
no strip-vn-tag
Command Default
VN-tag header stripping is disabled.
Modes
Ethernet interface configuration mode
Usage Guidelines
This feature applies to both IPv4 and IPv6 traffic.
If a tunneled frame has a VN-Tag in the outer L2 header, VXLAN, NVGRE, ERSPAN, or L2-over-MPLS/pseudo-wire header-
stripping also deletes the VN-Tag. (VN-Tags in the inner L2 header are not supported.)
If both MPLS and VN-Tag header-stripping are configured, MPLS is always implemented. However, details vary between IP-
over-MPLS and L2-over-MPLS regarding VN-Tags:
• Under IP-over-MPLS, only the MPLS labels are stripped; VN-Tags are not affected. The header diagram for this case
is as follows:
• Under L2-over-MPLS (pseudo-wire), both the outer L2 (with VN-Tag) and the MPLS header are stripped. The header
diagram for this case is as follows:
If interfaces with header-stripping enabled are included in a port-channel, the header stripping remains enabled, but only for
traffic entering those interfaces.
Examples
The following example enables VN-tag header-stripping on the interface.
History
Release version Command history
strip-vxlan
Removes Virtual Extensible LAN (VXLAN) headers from incoming packets, for forwarding to the next processing port—for
further filtering and forwarding.
Syntax
strip-vxlan
no strip-vxlan
Command Default
VXLAN header-stripping is disabled.
Modes
Ethernet interface configuration mode
Usage Guidelines
This feature is relevant only under NPB system mode.
On an interface, you can enable both VXLAN and NVGRE header-stripping. (VXLAN and NVGRE are mutually exclusive flows.)
The final Frame Check Sequence (FCS) is updated with a recalculated CRC.
If interfaces with header-stripping enabled are included in a port-channel, the header stripping remains enabled, but only for
traffic entering those interfaces.
For tunneled frames, header-stripping affects only the outer, encapsulation headers. For example:
• If both ERSPAN and VXLAN header-stripping are configured on the ingress interface, only the ERSPAN headers are
stripped. The header diagram for this case is as follows:
• If both VXLAN and MPLS header-stripping are configured, only VXLAN headers are stripped. The header diagram for
this case is as follows:
Examples
The following example enables VXLAN header-stripping on the interface.
History
Release version Command history
summary-address (OSPFv2)
Configures route summarization for redistributed routes for an Autonomous System Boundary Router (ASBR).
Syntax
summary-address A.B.C.D E.F.G.H
no summary-address
Command Default
Summary addresses are not configured.
Parameters
A.B.C.D E.F.G.H
IP address and mask for the summary route representing all the redistributed routes in dotted decimal format.
Modes
OSPF router configuration mode
Usage Guidelines
Use this command to configure an ASBR to advertise one external route as an aggregate for all redistributed routes that are
covered by a specified address range. When you configure an address range, the range takes effect immediately. All the
imported routes are summarized according to the configured address range. Imported routes that have already been advertised
and that fall within the range are flushed out of the AS and a single route corresponding to the range is advertised.
If a route that falls within a configured address range is imported by the device, no action is taken if the device has already
advertised the aggregate route; otherwise the device advertises the aggregate route. If an imported route that falls within a
configured address range is removed by the device, no action is taken if there are other imported routes that fall within the same
address range; otherwise the aggregate route is flushed.
The device sets the forwarding address of the aggregate route to 0 and sets the tag to 0. If you delete an address range, the
advertised aggregate route is flushed and all imported routes that fall within the range are advertised individually. If an external
link-state-database-overflow condition occurs, all aggregate routes and other external routes are flushed out of the AS. When
the device exits the external LSDB overflow condition, all the imported routes are summarized according to the configured
address ranges.This parameter affects only imported, type 5 external routes.
Examples
The following example configures a summary address of 10.1.0.0 with a mask of 10.255.0.0. Summary address 10.1.0.0,
includes addresses 10.1.1.0, 10.1.2.0, 10.1.3.0, and so on. For all of these networks, only the address 10.1.0.0 is advertised
in external LSAs:
History
Release version Command history
summary-address (OSPFv3)
Configures route summarization for redistributed routes for an Autonomous System Boundary Router (ASBR).
Syntax
summary-address IPv6-addr/mask
no summary-address
Command Default
Summary addresses are not configured.
Parameters
A:B:C:D/LEN
IPv6 address and mask for the summary route representing all the redistributed routes in dotted decimal format.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command to configure an ASBR to advertise one external route as an aggregate for all redistributed routes that are
covered by a specified IPv6 address range. When you configure an address range, the range takes effect immediately. All the
imported routes are summarized according to the configured address range. Imported routes that have already been advertised
and that fall within the range are flushed out of the AS and a single route corresponding to the range is advertised.
If a route that falls within a configured address range is imported by the device, no action is taken if the device has already
advertised the aggregate route; otherwise the device advertises the aggregate route. If an imported route that falls within a
configured address range is removed by the device, no action is taken if there are other imported routes that fall within the same
address range; otherwise the aggregate route is flushed.
The device sets the forwarding address of the aggregate route to 0 and sets the tag to 0. If you delete an address range, the
advertised aggregate route is flushed and all imported routes that fall within the range are advertised individually. If an external
link-state-database-overflow condition occurs, all aggregate routes and other external routes are flushed out of the AS. When
the device exits the external LSDB overflow condition, all the imported routes are summarized according to the configured
address ranges.
Examples
The following example configures a summary address of 2001:db8::/24 for routes redistributed into OSPFv3. The summary
prefix 2001:db8::/24 includes addresses 2001:db8::/1 through 2001:db8::/24. Only the address 2001:db8::/24 is
advertised in an external link-state advertisement.
History
Release version Command history
suppress-arp
Enables Address Resolution Protocol (ARP) suppression on a current VLAN or bridge domain. ARP suppression can lessen
ARP-related traffic within an IP Fabric.
Syntax
suppress-arp
no suppress-arp
Command Default
ARP suppression is disabled.
Modes
VLAN configuration mode
Usage Guidelines
This feature is required, along with ND suppression, if static anycast gateway is supported in an IP Fabric.
Examples
The following example enables ARP suppression on a VLAN.
History
Release version Command history
suppress-nd
Enables Neighbor Discovery (ND) suppression on a VLAN or bridge domain. ND suppression can lessen the amount of ND
control traffic within an IP Fabric.
Syntax
suppress-nd
no suppress-nd
Command Default
ND suppression is disabled.
Modes
VLAN configuration mode
Usage Guidelines
This feature is required, along with ARP suppression, if static anycast gateway is supported in an IP Fabric.
Examples
The following example enables ND suppression on a specified VLAN.
History
Release version Command history
switch-attributes
Configures the chassis or host name for the device.
Syntax
switch-attributes { chassis-name chassis-name } | { host-name host-name }
Command Default
The default chassis name is SLX9140-0.
The default host name is SLX.
Parameters
chassis-name chassis-name
Specifies the chassis name. A chassis name can be from 1 through 30 characters long, must begin with a letter, and
can contain letters, numbers, and underscore characters.
host-name host-name
Specifies the host name and changes the CLI prompt. A host name can be from 1 through 30 characters long. It must
begin with a letter, and can contain letters, numbers, and underscore characters.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to reset the default settings.
We recommend that you customize the chassis name for each device. Some system logs identify the device by its chassis
name; if you assign a meaningful chassis name, logs are more useful.
Examples
The following example configures the chassis and host names.
History
Release version Command history
switchport
Puts the interface in Layer 2 mode and sets the switching characteristics of the Layer 2 interface.
Syntax
switchport
no switchport
Command Default
All Layer 2 interfaces are mapped to default VLAN 1 and the interface is set to access mode.
Modes
Interface subtype configuration mode
Usage Guidelines
For changing the interface configuration mode to trunk or changing the default VLAN mapping, use additional switchport
commands.
To redefine the switch from Layer 2 mode into Layer 3 mode, enter no switchport.
Examples
To put a specific Ethernet interface in Layer 2 mode:
History
Release version Command history
switchport access
Specifies the VLAN for Layer 2 switchport access mode.
Syntax
switchport access { vlan vlan_id }
Command Default
All Layer 2 interfaces are in access mode and belong to the VLAN ID 1.
Parameters
vlan vlan_id
Sets the port VLAN (PVID) to the specified vlan_id. Range is 1 through 4090.
Modes
Interface subtype configuration mode on edge ports
Usage Guidelines
In access mode, the interface only allows untagged and priority tagged packets.
Enter no switchport access vlan to set the PVID to the default VLAN 1.
Examples
To set the Layer 2 interface PVID to 100 on a specific Ethernet interface:
History
Release version Command history
switchport mode
Sets the mode of the Layer 2 interface.
Syntax
switchport mode { access | trunk }
Parameters
access
Sets the Layer 2 interface as access. Access mode assigns the port to a VLAN
trunk
Sets the Layer 2 interface as trunk. Trunk mode makes the port linkable to other switches and routers
Modes
Interface subtype configuration mode
Usage Guidelines
You must configure the same native VLAN on both ends of an 802.1 or classified VLAN trunk link. Failure to do so can cause
bridging loops and VLAN leaks.
Examples
To set the mode of a specific Ethernet interface to access :
History
Release version Command history
Syntax
switchport mode trunk-no-default-native
Modes
Interface subtype configuration mode
Usage Guidelines
By assigning this mode, the user can configure an untagged logical interface on the specified port. Any ingress tagged or
untagged packet is discarded until a switchport classification or native VLAN classification is configured. To disable this
functionality, simply issue the no switchport command, or enter a different switchport mode by using the switchport mode
access command or the switchport mode trunk command.
Before you change the switch port mode from switchport mode access with an explicit switchport access vlan to switchport
mode trunk-no-default-native, you must enter the no switchport command on the interface level, and then enter the
switchport command to set the interface as a switchport. Now you can configure the switchport mode trunk-no-default-native
command.
Port mode change is not allowed when port security is enabled on the interface.
This is the fundamental difference between this command and the switch mode trunk command, which implicitly creates VLAN
1 on the port.
The global command dot1q tag native-vlan does not affect the ingress or egress tagging behavior of the native VLAN
configured in this mode.
The following native VLAN commands that are supported in regular trunk mode are NOT supported in this mode:
• switchport trunk tag native-vlan
• switchport trunk native-vlan
Examples
Configure a trunk port without a default native VLAN, then explicitly configure the native VLAN.
History
Release version Command history
switchport port-security
Enables port security on an interface port.
Syntax
switchport port-security
no switchport port-security
Command Default
Port security is not enabled.
Modes
Interface configuration mode
Usage Guidelines
Port mode change is not allowed when port security is enabled on the interface.
Examples
The following example enables port MAC security on an interface:
History
Release version Command history
Syntax
switchport port-security mac-address address vlan vlan_id
Command Default
MAC address is not configured for port security.
Parameters
mac-address address
Specifies the MAC address.
vlan vlan_id
Specifies a VLAN.
Modes
Interface configuration mode
Usage Guidelines
Static MAC addresses cannot be configured on a secure port. They must be configured as secure MAC addresses on the
secure port.
When static MAC address is configured on an access secure port or trunk port, VLAN must be specified.
The no switchport port-security mac-adress command removes the specified MAC address.
Examples
The following example configures static MAC address for port security on an interface:
History
Release version Command history
Syntax
switchport port-security max value
Parameters
value
The maximum number of secure MAC addresses. Range is from 1 through 8192.
Command Default
The default value is 8192 MAC addresses.
Modes
Interface configuration mode
Usage Guidelines
The maximum MAC address limit for sticky MAC address and static MAC address depends on the device limit. For dynamically
learned MAC addresses, the maximum limit is 8192 per port.
Examples
The following example configures the maximum number of MAC addresses used for port MAC security on an interface port as
10:
History
Release version Command history
Syntax
switchport port-security shutdown-time time
Command Default
Auto recovery of ports is not enabled.
Parameters
time
The amount of time in minutes, the port waits before it recovers from forced port shutdown. Range is from 1 through
15.
Modes
Interface configuration mode
Usage Guidelines
The shutdown and no-shutdown processes initiated as part of the port violation action is independent of the shutdown process
explicitly initiated by an administrator on the same port on which port MAC security is enabled.
If a port security-based change occurs when a port is shut down, the shutdown timer is not triggered. Consequently, the user
must restore the full functionality of the port.
When port security violation causes a port to be shut down and the user manually changes the shutdown time, the shutdown
timer is reset and the timer starts with the new shutdown time.
Examples
The following example configures the auto recovery time as 4 minutes for ports that shuts down following a port security
violation on an interface.
History
Release version Command history
Syntax
switchport port-security sticky [ mac-address address vlan vlan_id ]
Command Default
Sticky MAC learning on the port is not enabled.
Parameters
mac-address address
Specifies the MAC address.
vlan vlan_id
Specifies a VLAN.
Modes
Interface configuration mode
Usage Guidelines
When sticky MAC learning is enabled on a secured port, the interface converts all the dynamic secure MAC addresses,
including those that were dynamically learned before sticky learning was enabled, to sticky secure MAC addresses. All the
subsequent sets of dynamically learned MAC addresses will also be converted to sticky secure MAC addresses.
Sticky MAC addresses persist even if the port goes down; or if the device reboots, provided the config is saved.
Examples
The following example enables sticky MAC learning on the port and configures port security with sticky MAC address:
History
Release version Command history
Syntax
switchport port-security violation { restrict | shutdown }
Command Default
The port shuts downs if port security violation occurs.
Parameters
restrict
Drops the packets that have unknown source addresses until you remove a sufficient number of secure MAC
addresses to keep the count within the maximum MAC limit allowed on the interface.
shutdown
Puts the interface into the error-disabled state.
Modes
Interface configuration mode
Usage Guidelines
If a MAC address already learned on a secured port ingresses on a non-secured port or through another secured port, it is not
considered security violation. In this scenario, MAC movement happens if it is a dynamically learned MAC address. If it is a
static MAC address or sticky MAC address, MAC movement does not happen, but the traffic is switched (flooded or forwarded)
based on the destination MAC address.
If the port shuts down after security violation, an administrator can explicitly bring up the interface or a shutdown timer can be
configured using the switchport port-security shutdown-time command. After the configured shutdown time, the interface
automatically comes up and the port security configuration remains configured on the port.
When the device reboots after port shutdown due to security violation, the ports come up in the shutdown state.
Examples
The following example configures the violation response action as shutdown for port security on an interface:
History
Release version Command history
Syntax
switchport trunk allowed { vlan | rspan-vlan } { add vlan_id { ctag { id | ctag - range } | all | except vlan_id | none | remove
vlan_id }
Parameters
add vlan_id
Adds a VLAN to transmit and receive through the Layer 2 interface. The VLAN can be an 802.1Q VLAN, an RSPAN
VLAN, or a transport VLAN.
all
Allows only 802.1Q VLANs to transmit and receive through the Layer 2 interface. This keyword does not apply to
classified or transport VLANs.
ctag
Specifies an incoming C-TAG or range of C-TAGs for classified or transport VLANs.
id
C-TAG ID.
range
Range of C-TAG IDs, for example, 100-200, or 10,20,100-200, applicable only if the VLAN is a transport
VLAN.
except vlan_id
Allows only 802.1Q VLANs except the specified VLAN ID to transmit and receive through the Layer 2 interface.
none
Allows only 802.1Q VLANs to transmit and receive through the Layer 2 interface. This keyword does not apply to
service or transport VFs.
rspan-vlan vlan_id
Selects a VLAN for Remote Switched Port Analyzer (RSPAN) traffic monitoring.
remove vlan_id
Removes a VLAN that transmits and receives through the Layer 2 interface.
Modes
Interface subtype configuration mode
Usage Guidelines
A transport VF C-TAG can be any VLAN ID that is not used in other classifications or as a 802.1Q VLAN.
Examples
To add the tagged VLAN 100 to a specific Ethernet interface:
An 802.1Q vlan specified as a user VLAN cannot be used as a C-TAG in a classified VLAN. The following show conflicts.
• Edge C-TAG 100 is already assigned to VLAN 5000 at the same port:
History
Release version Command history
Syntax
switchport trunk default-vlan vlan_id
Parameters
vlan_id
Adds a classified VLAN (VLAN ID > 4095) to transmit and receive through the Layer 2 interface.
Modes
Interface subtype configuration mode on a trunk port
Usage Guidelines
Enter no switchport trunk default-vlan vlan_id to remove the default VLAN configuration.
Examples
Classify all nonmatching traffic except native VLAN traffic to the transparent default VLAN:
History
Release version Command history
Syntax
switchport trunk native-vlan-untagged vlan_id
Parameters
vlan_id
Adds a classified VLAN (VLAN ID > 4095) to transmit and receive through the Layer 2 interface.
Modes
Interface subtype configuration mode on a trunk port
Usage Guidelines
This command is supported when the port is in no-default-vlan trunk mode, as enabled by means of the switchport mode
trunk-no-default-native command.
Port mode change is not allowed when port security is enabled on the interface.
Examples
Configure untagged native VLAN 5000, allow VLAN 6000, and make VLAN 7000 the default VLAN.
History
Release version Command history
Syntax
switchport trunk native-vlan-xtagged vlan_id [ ctag cvid ] egress { tagged | untagged | any }
Parameters
vlan_id
Adds a classified VLAN (VLAN ID > 4095) to transmit and receive through the Layer 2 interface.
ctag cvid
Sets an optional C-TAG (802.1Q VLAN ID) for a service or transport VF (VLAN ID > 4095).
egress
Enables the selection of required tagging options.
tagged
Specifies packets as tagged.
untagged
Specifies packets as untagged.
any
Specifies that packets preserve their ingress encapsulation.
Modes
Interface subtype configuration mode on a trunk port
Usage Guidelines
This command is supported when the port is in no-default-vlan trunk mode, as enabled by means of the switchport mode
trunk-no-default-native command.
Port mode change is not allowed when port security is enabled on the interface.
Examples
Configure transport VF 6000 that accepts C-TAG range 100 through 200 and a native VLAN that can be either tagged or
untagged.
History
Release version Command history
Syntax
switchport trunk tag native-vlan
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no switchport trunk tag native to untag native traffic for a specific interface.
Examples
To enable tagging for native traffic on a specific Ethernet interface:
History
Release version Command history
sync-interval
Configures the interval between Precision Time Protocol (PTP) synchronization (Sync) messages on an interface.
Syntax
sync-interval seconds
no sync-interval
Command Default
See Parameters.
Parameters
seconds
Interval between PTP Synch messages, in log seconds. Range is -4 through 2. The default is -1 (2 packets/second).
See the Usage Guidelines. Range is -4 through 2. The default is -1 (2 packets/second).
Modes
PTP configuration mode
Usage Guidelines
The inputs for interval represent base 2 exponents, where the packet rate is 1/(2log seconds).
Configuring this interval on an edge port overrides the switch (global) default.
ATTENTION
Do not configure a rate slower than the default on links between SLX-
OSdevices.
Examples
The following example configures a PTP Sync interval of 2 on an Ethernet interface.
The following example reverts to the default PTP Sync interval of -1.
History
Release version Command history
sysmon sfm-walk
Enables SFM walk.
Syntax
sysmon sfm-walk [ start | stop ]
Parameters
start
Enable SFM walk.
stop
Disables SFM walk.
Modes
Privileged EXEC mode
Usage Guidelines
By default, SFM walk is disabled.
Examples
device# sysmon sfm-walk start
History
Release version Command history
Syntax
system packet-timestamp egress { add | remove | replace }
Command Default
No processing is applied on the egress interface.
Parameters
add
Specifies that the time the packet ingresses the switch is appended to the end of the payload on the egress interface.
The timestamp is used to recalculate the frame check sequence (FCS) and is in 8-byte nanosecond format. See the
Usage Guidelines.
remove
Specifies that the timestamp in the ingress payload is removed on the egress interface.
replace
Specifies that the timestamp in the ingress payload is replaced by the timestamp on the egress interface.
Modes
Interface subtype configuration mode
Usage Guidelines
ATTENTION
The presence of the timestamp in the ingress payload is effectively indicated by the system packet-timestamp
ingress valid command. Hardware does not verify whether or not the timestamp is actually in the payload. If the use of
the above command specifies that the timestamp be present but the timestamp does not actually exist, hardware
overwrites or removes the last eight bytes of payload data.
Use the no form of this command to disable the processing of packets on the egress interface.
Examples
To specify that the timestamp indicating when the packet ingresses the switch is appended to the end of the payload on an
egress port-channel interface:
To specify that the timestamp indicating when the packet ingresses the switch is removed from the end of the payload on an
egress port-channel interface:
To specify that the timestamp indicating when the packet ingresses the switch is replaced by the timestamp on an egress port-
channel interface:
History
Release version Command history
Syntax
system packet-timestamp ingress valid
Command Default
By default, a timestamp is not appended.
Modes
Interface subtype configuration mode
Usage Guidelines
This is supported only on Layer 2 interfaces (nonswitch, switchport, port-channel).
ATTENTION
The presence of the timestamp in the ingress payload is effectively indicated by this command. Hardware does not
verify whether or not the timestamp is actually in the payload. If the use of this command specifies that the timestamp
is appended but the timestamp does not actually exist, then the hardware overwrites or removes the last eight bytes of
payload data.
Use the no form of this command to inform the SLX device that ingressing frames do not have appended timestamps.
Use the system packet-timestamp egress command to configure how the timestamp is processed at the egress interface.
Examples
To specify that a timestamp exists in all payloads that ingress a port-channel interface:
To specify that a timestamp does not exist in any payload that ingresses the interface:
History
Release version Command history
system-description
Sets the global system description specific to LLDP.
Syntax
system-description line
no system-description
Parameters
line
Specifies a description for the LLDP system. The string must be between 1 and 50 ASCII characters in length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
Enter no system-description to clear the global LLDP system description.
Examples
The following example sets the global system description specific to LLDP.
History
Release version Command history
system-mode
Sets the system mode.
Syntax
system-mode { default | npb }
Parameters
default
Specifies the default system mode.
npb
Specifies the Network Packet Broker (NPB) system mode.
Modes
Hardware configuration mode
Usage Guidelines
In NPB mode, Layer 2 and Layer 3 forwarding, protocols, and services such as SPAN and SFLOW are not supported. Extreme
recommends not to use any of these configurations in NPB mode. If these features are required, use default mode.
Examples
The following example indicates that the current mode is default. The value displayed within brackets ([ ]) is the current mode.
NOTE
The show running-config hardware command also displays the current mode.
The following example sets the NPB system mode and reloads the system.
History
Release version Command history
system-monitor
Manages the monitoring of FRUs and sets a variety of alerts when thresholds are exceeded.
Syntax
system-monitor { LineCard [ alert [ action [ all | email | none | raslog ] ] | state [ all | faulty | inserted | none | on | removed ] ] |
threshold [ down-threshold | marginal-threshold ] ] ] | cid-card [ alert [ action | state [ all | faulty | inserted | none | on |
removed ] ] | threshold [ down-threshold | marginal-threshold ] ] | compact-flash [ threshold [ down-threshold |
marginal-threshold ] ] | fan [ alert [ action | state [ all | faulty | inserted | none | on | removed ] ] | threshold [ down-
threshold | marginal-threshold ] ] | power [ alert [ action | state [ all | faulty | inserted | none | on | removed ] ] | threshold
[ down-threshold | marginal-threshold ] ] sfp [ alert [ action state ] ] temp [ threshold [ down-threshold | marginal-
threshold ] ] }
no system-monitor
Command Default
For system monitoring defaults, see the "System Monitor" chapter in the Extreme SLX-OS Monitoring Configuration Guide .
Parameters
LineCard
Specifies alerts and thresholds for line cards.
cid-card
Specifies alerts and thresholds for the chassis ID card.
compact-flash
Specifies thresholds for the compact flash device.
fan
Specifies alerts and thresholds for the fans.
power
Specifies alerts and thresholds for the power supplys.
sfp
Specifies alerts for the small form-factor pluggable devices.
temp
Specifies thresholds for the temperature sensors.
alert
Specifies whether an alert is sent when a threshold value is either above or below a threshold trigger.
action
Specifies the response type.
all
Specifies that e-mail and RASLog messaging are used.
email
Specifies that an e-mail message is sent.
none
Specifies that no message is sent.
raslog
Specifies RASLog messaging.
state
Specifies the hardware state to be monitored.
all
Specifies that all hardware states are monitored.
faulty
Specifies that hardware is monitored for faults.
inserted
Specifies that the insertion state of hardware is monitored.
none
Specifies that no hardware states are monitored.
on
Specifies that the hardware on/off state is monitored.
removed
Specifies that the removal of hardware is monitored.
threshold
Specifies the monitoring of thresholds
down-threshold
Specifies an integer value that, when exceeded, indicates when hardware is down.
marginal-threshold
Specifies an integer value that, when exceeded, indicates when hardware is operating marginally.
Modes
Global configuration mode
Usage Guidelines
Use this command to configure field-replaceable unit (FRU) monitoring and actions. Depending on these configuration settings,
a variety of actions are generated when there is a change in FRU state.
Examples
Typical command example that sets the
History
Release version Command history
system-monitor-mail
Configures Fabric Watch e-mail alerts on the device.
Syntax
system-monitor-mail { fru | interface | relay { host_ip | domain_name } | security | sfp } enable | email-id ]
no system-monitor-mail
Command Default
The default source is disabled.
Parameters
fru
Configures e-mail alerts for FRUs.
interface
Configures e-mail alerts for interfaces.
relay
Configures the relay host for e-mail to work in a non-DNS environment.
host_ip
Specifies the IPv4 address of the mail server.
domain_name
Specifies the domain that corresponds to the e-mail ID.
security
Configures e-mail alerts for security.
sfp
Configures e-mail alerts for SFPs.
enable
Enables or disables e-mail alerts for the above options.
email-id
Specifies the e-mail address to where the alert will be sent.
Modes
Global configuration mode
Usage Guidelines
For an e-mail alert to function correctly, add the IP addresses and host names to DNS in addition to configuring the domain
name and name servers. Both relay parameters (the host IP address and the domain name) must be configured in a non-DNS
environment. In a DNS environment, only the host IP address is required).
Examples
The following example creates a mapping.
History
Release version Command history
system-name
Sets the global system name specific to LLDP.
Syntax
system-name name
no system-name
Command Default
The host name from the device is used.
Parameters
name
Specifies a system name for the LLDP. The string must be between 1 and 32 ASCII characters in length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
Enter no system-name to delete the name.
Examples
The following example specifies a system name for the LLDP.
History
Release version Command history
table-map
Maps external entry attributes into the BGP routing table, ensuring that those attributes are preserved after being redistributed
into OSPF.
Syntax
table-map string
no table-map string
Parameters
string
Specifies a route map to be whose attributes are to be preserved. Valid values range from 1 through 63 ASCII
characters.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use this command only to set the tag values. Normally, a route map is applied on routes (and therefore the routes are updated)
before it is stored in the BGP routing table. Use the table-map command to begin the update before the routes are stored in the
IP routing table.
Route maps that contain set statements change values in routes when the routes are accepted by the route map. For inbound
route maps (route maps that filter routes received from neighbors), the routes are changed before they enter the BGP routing
table. For tag values, if you do not want the value to change until a route enters the IP routing table, you can use a table map to
change the value. A table map is a route map that you have associated with the IP routing table. The device applies the set
statements for tag values in the table map to routes before adding them to the routing table. To configure a table map, you first
configure the route map, then identify it as a table map. The table map does not require separate configuration. You can have
only one table map.
NOTE
Use table maps only for setting the tag value. Do not use table maps to set other attributes. To set other route
attributes, use route maps or filters. To create a route map and identify it as a table map, enter commands such those
shown in the first example below. These commands create a route map that uses an address filter. For routes that
match the IP prefix list filter, the route map changes the tag value to 100 and is then considered as a table map. This
route map is applied only to routes that the device places in the IP routing table. The route map is not applied to all
routes. The first example below assumes that IP prefix list p11 has already been configured.
Examples
The following example illustrates the execution of the table-map command.
The following example removes the table map for the default VRF.
The following example removes the table map for VRF “red”.
History
Release version Command history
tacacs-server
Configures a Terminal Access Controller Access-Control System plus (TACACS+) server.
Syntax
tacacs-server { host hostname [ use-vrf vrf-name ]
[ port portnum ]
[ key shared_secret ]
[ encryption-level value_level ]
[ timeout secs ]
[ retries num ]
Parameters
host hostname
Specifies the IP address or domain name of the TACACS+ server. IPv4 and IPv6 addresses are supported.
use-vrf vrf-name
Specifies a VRF though which to communicate with the TACACS+ server. See the Usage Guidelines.
port portnum
Specifies the authentication port. Valid values range from 0 through 65535. The default is 49.
key shared_secret
Specifies the text string that is used as the shared secret between the device and the TACACS+ server to make the
message exchange secure. The key must be between 8 and 40 characters in length. The default key is sharedsecret .
The exclamation mark (!) is supported both in RADIUS and TACACS+ servers, and you can specify the password in
either double quotes or the escape character (\), for example "secret!key" or secret\!key. The only other valid
characters are alphanumeric characters (such as a-z and 0-9) and underscores. No other special characters are
allowed.
encryption-level value_level
Designates the encryption level for the shared secret key operation. This operand supports JITC certification and
compliance. The valid values are 0 and 7, with 0 being clear text and 7 being the most heavily encrypted. The default
value is 7.
timeout secs
Specifies the time to wait for the TACACS+ server to respond. The default is 5 seconds.
retries num
Specifies the number of attempts allowed to connect to a TACACS+ server. The default is 5 attempts.
Modes
Global configuration mode
Usage Guidelines
If a TACACS+ server with the specified IP address or host name does not exist, it is added to the server list. If the TACACS+
server already exists, this command modifies the configuration. The key parameter does not support an empty string.
Executing the no form of the tacacs-server command attributes resets the specified attributes to their default values.
NOTE
Before downgrading to a software version that does not support the encryption-level keyword, set the value of this
keyword to 0. Otherwise, the firmware download will throw an error that requests this value be set to 0.
Before downgrading to a version that doesn’t support tacacs-server source-ip, you must remove the source-ip configuration
using no tacacs-server source-ip. Otherwise, the firmware download process throws an error requesting to reset the cipher.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
Examples
To configure an IPv4 TACACS+ server:
History
Release version Command history
telemetry client-cert
Generates the SSL certificate used by Telemetry server and client for a secure connection.
Syntax
telemetry client-cert { generate | delete }
Command Default
There is no SSL certificate.
Parameters
generate
Generates the certificate
delete
Deletes the certificate.
Modes
Privileged EXEC mode
Usage Guidelines
Use the telemetry client-cert delete to delete the SSL certificate for Telemetry server and clients.
Examples
Typical command execution example.
History
Release version Command history
telemetry collector
Activates telemetry-collector configuration mode.
Syntax
telemetry collector telemetry-collector
Command Default
Telemetry-collector configuration mode is deactivated.
Parameters
telemetry-collector
A unique name for a telemetry collector. The name can be a string of up to 32 characters, consisting of letters, digits,
and the underscore.
Modes
Global configuration mode
Usage Guidelines
Update operations are allowed only when telemetry collector is in deactivated (“no activate”) state.
Examples
Typical command example for activating telemetry-collector configuration mode.
History
Release version Command history
telemetry profile
Enters telemetry-profile configuration mode for a telemetry profile.
Syntax
telemetry profile enhanced-queue-discard-pkts default_enhanced_queue_discard_pkts_statistics
Command Default
The Telemetry profile configuration mode is deactivated.
Parameters
enhanced-queue-discard-pkts default_enhanced_queue_discard_pkts_statistics
Accesses configuration mode for profile default_enhanced_queue_discard_pkts_statistics of the enhanced-queue-
discard-pkts profile type—for tracking discarded-packet statistics.
event default_event_statistics
Accesses configuration mode for profile default_event_statistics of the event profile type—for tracking up/down
interface events
interface default_interface_statistics
Accesses configuration mode for profile default_interface_statistics of the interface profile type—for tracking interface
statistics.
lldp default_lldp_statistics
Accesses configuration mode for profile default_lldp_statistics of the lldp profile type—for tracking LLDP neighbor
information, including link states.
pbr default_pbr_statistics
Accesses configuration mode for profile default_pbr_statistics of the pbr profile type—for tracking policy-based
routing (PBR) statistics.
queue default_queue_statistics
Accesses configuration mode for profile default_queue_statistics of the queue profile type—for tracking queue
statistics.
system-utilization default_system_utilization_statistics
Accesses configuration mode for profile default_system_utilization_statistics of the system-utilization profile type—
for tracking system utilization statistics.
Modes
Global configuration mode
Usage Guidelines
The no option is not supported for this command.
• speed
• local-lag-id
• remote-lag-id
• link-state
• SW interrupt
• Idle state
• Steal time
• Up time
Examples
The following example enters telemetry-profile configuration mode for the default_interface_statistics profile.
History
Release version Command history
telemetry server
Enters telemetry-server configuration mode.
Syntax
telemetry server
Command Default
Telemetry-server configuration mode is not active.
Parameters
use-vrf vrf-name
(Not supported) Specifies a VRF.
Modes
Global configuration mode
Usage Guidelines
You use this command to configure gRPC-server telemetry streaming.
Update and No operations are available only when telemetry server is in deactivated (“no activate”) state.
Examples
The following example enters telemetry-server configuration mode and activates the internal gRPC telemetry-server on the
default port 50051.
History
Release version Command history
telnet
Establishes a Telnet session to a remote networking device.
Syntax
telnet IP_address [ port-number port_number ] [ vrf name ]
telnet hostname } [ port-number port_number ] [ interface { ethernet slot/port } | management | {ve number } ] [ vrf name ]
Command Default
The default port is 23.
Parameters
IP_address
The server IP address in either IPv4 or IPv6 format.
port-number port
Specifies the port number in the remote device to connect to. Range is from 0 through 65535. For the connection to
succeed, a TCP server must be listening for client connections at the specified port.
vrf vrf-name
Specifies a VRF instance. See the Usage Guidelines.
hostname
Specifies the host name which is a string between 1 and 63 ASCII characters in length.
port-number port
Specifies the port number in the remote device to connect to. Range is from 0 through 65535. For the
connection to succeed, a TCP server must be listening for client connections at the specified port.
interface
Specifies an interface.
ethernet slot/port
Specified the Ethernet interface slot and port number.
management
Specifies a management interface.
ve VE-id
Specifies the VE interface number.
Modes
Privileged EXEC mode
Usage Guidelines
You can override the default port. However, the device must be listening on this port for the connection to succeed.
Examples
The following example establishes a Telnet connection to a remote device.
History
Release version Command history
telnet server
Configures the Telnet server on the device.
Syntax
telnet server standby enable
Command Default
The Telnet service is enabled by default.
Parameters
standby enable
Enables the Telnet server on the standby switch.
use-vrf name
Specifies a user-defined VRF.
shutdown
Disables the Telnet server.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to disable Telnet service on the standby switch, or re-enable the Telnet service on the device.
If you include the VRF name, the Telnet server for the VRF is re-enabled.
Shutting down the Telnet service forcibly disconnects all Telnet sessions running on a device.
When you use the telnet server shutdown command without a user-defined VRF, the service is shut down on mgmt-vrf only.
Telnet services are associated and started on mgmt-vrf and default-vrf.
Telnet server can be enabled on a maximum number of six VRFs.
Examples
The following example shuts down the Telnet server on the device.
History
Release version Command history
terminal
Sets terminal parameters for the current session.
Syntax
terminal length lines
terminal monitor
terminal no length
terminal timeout seconds
Command Default
The terminal length is 24 lines.
Parameters
length number_of_lines
Specifies the number of lines to be displayed. Valid values range from 1 through 512. Specify 0 for infinite length.
monitor
Enables terminal monitoring.
timeout seconds
Specifies the timeout value in minutes. Enter an integer from 1 to 8192. Specify 0 to disable the timeout.
Modes
Privileged EXEC mode
Usage Guidelines
The timeout overrides the timeout configuration set by the line vty exec-timeout command, but only for the duration of the
current session. When the current session ends, the configured values apply for any subsequent sessions.
Even if other keys are pressed during the timeout period, the only keystroke that prevents logout is Enter.
Use the no form of the command to reset the default timeout or disable monitoring.
Use the terminal no length command to reset the default number of displayed lines.
Examples
The following example sets the display length to 30 lines.
The following example sets timeout length to 3600 seconds (60 minutes).
History
Release version Command history
threshold-monitor cpu
Configures monitoring of CPU usage of the system and alerts the user when configured thresholds are exceeded.
Syntax
threshold-monitor cpu { [ actions [ loginfo none | | raslog [ limit limit_when_reached | poll polling_interval | retry
number_of_retries ] ]}
no threshold-monitor cpu
Parameters
actions
Specifies the action to be taken when a threshold is exceeded.
loginfo
Collects diagnostic data along with RASLOG.
none
No action is taken.
raslog
Specifies RASLog messaging.
limit
Specifies the baseline CPU usage limit as a percentage of available resources.
limit_when_reached
When the limit set by this parameter is exceeded, a RASLog WARNING message is sent. When the usage
returns below the limit, a RASLog INFO message is sent. Valid values range from 0 through 80 percent. The
default is 70 percent.
poll
Specifies the polling interval in seconds.
polling_interval
The range is from 0 through 3600. The default is 120
retry
Specifies the number of polling retries before desired action is taken.
number_of_retries
Range is from 1 through 100. The default is 3.
Modes
Global configuration mode
Usage Guidelines
This command sends a RASLog WARNING message when configured thresholds are exceeded.
Examples
device# configure terminal
device(config)# threshold-monitor cpu actions rasloglimit 50 poll10
History
Release version Command history
threshold-monitor memory
Configures monitoring of the memory usage of the system and alerts the user when configured thresholds are exceeded.
Syntax
threshold-monitor memory { actions [ none|loginfo|raslog] |high-limit percent | limit percent | low-limit percent | poll
polling_interval | retry number_of_retries }
no threshold-monitor memory
Parameters
actions
Specifies the action to be taken when a threshold is exceeded.
none
No action is taken. This is the default.
loginfo
Collects diagnostic data along with RASLog.
raslog
Specifies RASLog messaging.
high-limit
Specifies an upper limit for memory usage as a percentage of available memory.
percent
This value must be greater than the value set by limit. When memory usage exceeds this limit, a RASLog
CRITICAL message is sent. Values range from 0 through 80 percent. The default is 70 percent.
limit
Specifies the baseline memory usage limit as a percentage of available resources.
percent
When this value is exceeded, a RASLog WARNING message is sent. When the usage returns below the value
set by limit , a RASLog INFO message is sent. Values range from 0 through 80 percent. The default is 60
percent.
low-limit
Specifies a lower limit for memory usage as percentage of available memory.
percent
This value must be smaller than the value set by limit. When memory usage exceeds or falls below this limit,
a RASLog INFO message is sent. The default is 40 percent.
poll
Specifies the polling interval in seconds.
polling_interval
The range is from 0 through 3600. The default is 120
retry
Specifies the number of polling retries before desired action is taken.
number_of_retries
Range is from 1 through 100. The default is 3.
Modes
Global configuration mode
Examples
device# configure terminal
device(config)# threshold-monitor memory actions none high-limit 80 low-limit 50 limit 70 retry 2 poll
30
History
Release version Command history
threshold-monitor sfp
Configures monitoring of SFP parameters.
Syntax
threshold-monitor sfp { [ apply policy_name | pause | policy policy_name ] type SFP_type area parameters alert [ above
[ highthresh-action [ [ all | lowthresh-action ] | email | none | raslog ] | lowthresh-action [ all | email none | raslog ] | below
[ highthresh-action [ all | email | none raslog ] | lowthresh-action [ all | email | none | raslog ] ] | threshold [ buffer | high-
threshold | low-threshold | timebase [ day | hour | minute | none ] ] ] }
no threshold-monitor sfp
Command Default
By default, SFP is not monitored.
Parameters
apply policy_name
Applies a custom policy that has been created by the policy operand.
pause
Pause monitoring.
policy
Specifies a policy name for monitoring by means of custom settings, rather than default settings. A policy name is
required before additional configurations can be made. This operation is not supported from a secondary node.
policy_name
Name of a custom policy configuration that can be saved and applied by means of the apply operand.
type
Specifies the SFP type. Possible completions are as follows:
1GLR
— SFP Type 1GLR
1GSR
— SFP Type 1GSR
10GLR
— SFP Type 10GLR
10GSR
— SFP Type 10GSR
10GUSR
— SFP Type 10GUSR
100GSR
— SFP Type 100GSR
QSFP
— SFP type QSFP
area
Specifies one of the following SFP parameters to be monitored. See Defaults, below.
Current
Measures the current supplied to the SFP transceiver.
RXP
Measures the incoming laser power, in microWatts (µW).
TXP
Measures the outgoing laser power, in µW).
Temperature
Measures the temperature of the SFP, in degrees Celsius.
Voltage
Measures the voltage supplied to the SFP.
alert
Specifies whether an alert is sent when a threshold value is either above or below a threshold trigger.
above
Enables setting a value for highthresh-action, which specifies the action to be taken when a high
threshold is exceeded.
below
Enables setting a value for highthresh-action and lowthresh-action, which specifies the action to be
taken when a low threshold is exceeded.
all
Specifies that email and RASLog messaging are used, and that Port Fencing is applied in the case
of highthresh-action only.
all
Specifies that email and RASLog messaging are used.
email
Specifies that an email message is sent.
none
Specifies that no alert is sent.
raslog
Specifies RASLog messaging.
limit
Specifies the percent of threshold usage, from 0 through 80. The default is 75.
poll
Specifies the polling interval in seconds, from 0 through 3600. The default is 120.
retry
Specifies the number of polling retries before desired action is taken, from 1 through 100. The
default is 3.
threshold
Specifies the values for high, low, buffer, and timebase thresholds. These values are used to trigger different alerts and
Port Fencing.
buffer
An integer value.
high-threshold
An integer value.
low-threshold
An integer value.
timebase
Calculates differences between current and previous data taken over a variety of intervals, for comparison
against the preset threshold boundary.
day
Calculates the difference between a current data value and that value a day ago.
hour
Calculates the difference between a current data value and that value an hour ago.
minute
Calculates the difference between a current data value and that value a minute ago.
none
Compares a data value to a threshold boundary level.
Modes
Global configuration mode
Examples
A typical command might look like this:
History
Release version Command history
timeout
Specifies the wait time allowed for a Remote Authentication Dial-In User Service (RADIUS) server response.
Syntax
timeout sec
no timeout
Command Default
The default wait time is 5 seconds.
Parameters
sec
Specifies the wait time (in seconds) allowed for a RADIUS server response. The range is from 1 through 60. The
default value is 5.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example shows how to configure a wait time (timeout value) of 10 seconds.
History
Release version Command history
timeout (Telemetry)
Defines the timeout value of the LDAP host.
Syntax
timeout { secs }
no timeout
Command Default
The timeout is 5 seconds.
Parameters
timeout
Specifies the wait time for a server to respond. The range is 1 through 60 seconds.
Modes
LDAP host configuration mode.
Usage Guidelines
Use the no form of this command to remove the timeout value.
Examples
To add an LDAP server with the timeout set to 8 seconds:
History
Release version Command history
timers (BGP)
Adjusts the interval at which BGP KEEPALIVE and HOLDTIME messages are sent.
Syntax
timers { keep-alive keepalive_interval hold-time holdtime_interval }
no timers
Parameters
keep-alive keepalive_interval
Frequency in seconds with which a device sends keepalive messages to a peer. Valid values range from 0 through
65535 seconds. The default is 60 seconds.
hold-time holdtime_interval
Interval in seconds that a device waits to receive a keepalive message from a peer before declaring that peer dead.
Valid values range from 0 through 65535 seconds. The default is 180 seconds.
Modes
BGP configuration mode
Usage Guidelines
The KEEPALIVE and HOLDTIME message interval is overwritten when the fast-external-failover command takes effect on a
down link to a peer.
You must enter a value for keep-alive before you can enter a value for hold-time. Both values must be entered. If you only want
to adjust the value of one parameter, enter the default value of the parameter that you do not want to adjust.
The no form of the command clears the configured timers and restores the defaults.
Examples
The following example sets the keepalive timer for a device to 120 seconds and the hold-timer to 360 seconds.
The following example sets the keepalive timer for a device to 0 seconds and the hold-timer to 0 seconds so that the device
waits indefinitely for messages from a neighbor without tearing down the session.
History
Release version Command history
timers (OSPFv2)
Configures Link State Advertisement (LSA) pacing and Shortest Path First (SPF) throttle timers.
Syntax
timers { lsa-group-pacing interval | throttle spf start hold max }
Parameters
lsa-group-pacing interval
Specifies the interval at which OSPF LSAs are collected into a group and refreshed, check-summed, or aged by the
OSPF process. Valid values range from 10 through 1800 seconds. The default is 240 seconds.
throttle spf
Specifies start, hold and maximum wait intervals for throttling SPF calculations for performance. The values you enter
are in milliseconds.
start
Initial SPF calculation delay. Valid values range from 0 through 60000 milliseconds. The default is 0.
hold
Minimum hold time between two consecutive SPF calculations. Valid values range from 0 through 60000
milliseconds. The default is 0.
max
Maximum wait time between two consecutive SPF calculations. Valid values range from 0 through 60000
milliseconds. The default is 0.
Modes
OSPF router configuration mode
OSPF VRF router configuration mode
Usage Guidelines
The device paces LSA refreshes by delaying the refreshes for a specified time interval instead of performing a refresh each time
an individual LSA refresh timer expires. The accumulated LSAs constitute a group, which the device refreshes and sends out
together in one or more packets.
The LSA pacing interval is inversely proportional to the number of LSAs the device is refreshing and aging. For example, if you
have a large database of 10,000 LSAs, decreasing the pacing interval enhances performance. If you have a small database of
about 100 LSAs, increasing the pacing interval to 10 to 20 minutes may enhance performance.
The no timers lsa-group-pacing command restores the pacing interval to its default value.
The no timers throttle spf command sets the SPF timers back to their defaults.
Examples
The following example sets the LSA group pacing interval to 30 seconds.
The following example sets the SPF delay to 10000 milliseconds, the hold time to 15000 milliseconds, and the maximum wait
time to 30000 milliseconds.
History
Release version Command history
timers (OSPFv3)
Configures Link State Advertisement (LSA) pacing and Shortest Path First (SPF) timers.
Syntax
timers {lsa-group-pacing interval | spf start hold }
Parameters
lsa-group-pacing interval
Specifies the interval at which OSPFv3 LSAs are collected into a group and refreshed, check-summed, or aged by the
OSPFv3 process. Valid values range from 10 through 1800 seconds. The default is 240 seconds.
spf
Specifies start and hold intervals for SPF calculations for performance. The values you enter are in milliseconds.
start
Initial SPF calculation delay. Valid values range from 0 through 65535 seconds.
hold
Minimum hold time between two consecutive SPF calculations. Valid values range from 0 through 65535
seconds.
Modes
OSPFv3 router configuration mode
OSPFv3 router VRF configuration mode
Usage Guidelines
The device paces LSA refreshes by delaying the refreshes for a specified time interval instead of performing a refresh each time
an individual LSA refresh timer expires. The accumulated LSAs constitute a group, which the device refreshes and sends out
together in one or more packets.
The LSA pacing interval is inversely proportional to the number of LSAs the device is refreshing and aging. For example, if you
have a large database of 10,000 LSAs, decreasing the pacing interval enhances performance. If you have a small database of
about 100 LSAs, increasing the pacing interval to 10 to 20 minutes may enhance performance.
The no timers lsa-group-pacing command restores the pacing interval to its default value.
The no timers spf command sets the SPF timers back to their defaults.
Examples
The following example sets the LSA group pacing interval to 30 seconds.
The following example sets the SPF delay time to 10 and the hold time to 20.
History
Release version Command history
topology-group
Configures the topology group.
Syntax
topology-group group-id
no topology-group group-id
Command Default
A topology group is not configured.
Parameters
group-id
Specifies the topology group ID. The ID ranges from 1 through 256.
Modes
Global configuration mode
Usage Guidelines
Each topology group contains a master VLAN and can contain one or more member VLANs and VLAN groups. You must
configure the master VLAN and member VLANs or member VLAN groups before you configure the topology group.
You can configure up to 30 topology groups. Each group can control up to 4096 VLANs. A VLAN cannot be controlled by
more than one topology group. The topology group must contain a master VLAN and can also contain individual member
VLANs, VLAN groups, or a combination of individual member VLANs and VLAN groups.
Examples
The following example configures the topology group with ID 2 and adds master VLAN and member VLANs.
History
Release version Command history
tpvm
Provides administrative support for Third-Party Virtual Machine (TPVM) applications.
tpvm disk { add name { disk_name | auto disk_size } | remove name { disk_name | auto } }
tpvm help
tpvm install
tpvm password
tpvm start
tpvm stop
tpvm uninstall
Command Default
This feature is not enabled.
Parameters
auto-boot disable
Prevents TPVM from starting at the next reboot of SLX-OS.
auto-boot enable
Starts TPVM at the next reboot of SLX-OS (without the need for the start keyword).
disk_name
Name of the disk to be added if the auto keyword is not specified.
auto
Assigns a disk name automatically. See the Usage Guidelines.
disk_size
Size of the disk (any positive integer). See the Usage Guidelines.
disk_name
Name of the additional disk to be removed. See the Usage Guidelines.
install
Installs TPVM.
password
Changes the root password on TPVM.
start
Starts TPVM.
stop
Stops TPVM.
uninstall
Uninstalls TPVM if it is already installed.
force
Clears installation or uninstallation errors, then tries to force an uninstallation.
Modes
Privileged EXEC mode
Usage Guidelines
The maximum number of disks is currently 3, and if the number of the allocated disks exceeds it, the disk add name
subcommand fails. In addition, the total disk capacity is limited to 25 Gbytes. If you exceed this limit when you create a disk, the
disk add name subcommand fails.
If the auto keyword is not used with the add_disk command, the name of the disk must be that of the next disk. For example, if
the last disk added to the system is vdb, the name of the next disk must be vdc.
You can add one of the following suffixes to specify disk size:
• b or B (bytes)
• k or K (kilobytes)
• m or M (megabytes)
• g or G (gigabytes)
The maximum number of disks supported is currently 3. if the number of allocated disks exceeds this number, the add_disk
keyword fails.
If the auto keyword is not used with the remove_disk command, the name of the disk must be that of the last disk added to the
system..
ATTENTION
If the disk is mounted, it must be unmounted before it is removed from the system. Otherwise, the next added disk will
be labeled incorrectly. If this happens, TPVM must be rebooted to recover.
The show ip-address subcommand requires the qemu-guest-agent package on TPVM. If that package is removed, this
subcommand fails.
Examples
To install TPVM if it is not already installed:
To start TPVM at the next reboot of SLX-OS (without the need for the start keyword):
NOTE
In this case, the tpvm start command is required to enable TPVM.
History
Release version Command history
traceroute
Traces the network path of packets as they are forwarded to a destination address.
Syntax
traceroute { IPv4_address | host-name | ipv6 [ dest-ipv6-address | host-name ] } [ interface ] [ maxttl value ] [ minttl value ]
[ src-addr src-addr ] [ timeout seconds ] [ vrf vrf-name ]
Parameters
IPv4_address
Specifies the IPv4 address of the destination device.
host-name
Specifies the hostname of the destination device.
ipv6 dest-ipv6-address
Specifies the IPv6 address of the destination device.
interface
Selects the output interface.
maxttl value
Maximum Time To Live value in a number of hops.
minttl value
Minimum Time To Live value in a number of hops.
src-addr address
Specifies the IPv4 or IPv6 address of the source device.
timeout seconds
The traceroute timeout value.
vrf vrf-name
Name of the VRF. If no VRF is specified, the default-vrf is used.
Modes
Privileged EXEC mode
Usage Guidelines
To use the traceroute command on the management VRF, enter mgmt-vrf. You must enter the name of the management VRF
manually.
Examples
The following example executes an IPv6 traceroute, with minimum and maximum TTL values.
History
Release version Command history
track (VRRP)
Enables VRRP tracking for a specified interface. VRRP Extended (VRRP-E) sessions can track a specified interface or a
network.
Syntax
track { ethernet slot/port | port-channel number } [ priority value ]
Command Default
The default priority value is 2.
Parameters
ethernet slot port
Specifies a valid, physical Ethernet subtype with appropriate slot and port number. The slot number must be 0 if the
switch does not contain slots.
port-channel number
Specifies the port-channel number. Valid values range from 1 through 6144.
priority value
The track priority is a number from 1 through 254, and is used when a tracked interface or network up or down event
is detected. For VRRP, if the tracked interface goes offline, the specified priority value is subtracted from the priority of
the current device. For VRRP-E, if the tracked interface or network goes offline, the current device priority is reduced
by the configured priority value. If the tracked interface or network comes online, the specified priority value is added to
the priority of the current device.
network
Enables tracking of a specified network. Network tracking is supported only on VRRP-E sessions.
ip-address
Specifies an IPv4 network address.
ipv6-address
Specifies an IPv6 network address.
mask
Specifies a mask for the associated IP or IPv6 subnet.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command can be used to track interfaces for VRRP or VRRP-E. Only VRRP-E sessions support network tracking.
For VRRP, the tracked interface can be any Ethernet or port-channel interface other than the one on which this command is
issued.
The networks to be tracked can be either present or absent from the Routing Information Base (RIB).
The maximum number of interfaces or networks you can track per virtual router is 16.
Enter no track with the specified interface or network to remove the tracked port or tracked network configuration.
Examples
To set the track port to 0/4 and the track priority to 60:
The following example shows how to configure network 10.1.1.0/24 to be tracked, and if the network goes down, the VRRP-E
device priority is lowered by a value of 20. The lower priority may trigger a switchover and a backup device with a higher priority
becomes the new master for VRRP-E group 1.
History
Release version Command history
transport
Specifies the transport protocol for gRPC-server telemetry streaming.
Syntax
transport { tcp | ssl }
Command Default
The transport protocol is set to TCP.
Parameters
tcp
Designates TCP for the transport protocol.
ssl
Designates SSL for the transport protocol. SSL provides encryption through TLS.
Modes
Telemetry-server configuration mode
Usage Guidelines
This command (and the SSL option) are available only for the gRPC-server implementation. They are not supported for the
external-collector telemetry implementation.
Examples
The following example enables SSL as the telemetry transport protocol.
History
Release version Command history
trigger
Defines event-handler triggers. When the trigger-condition occurs, a Python script is run.
Syntax
trigger trigger-id raslog raslog-id [ pattern posix-ext-regex ]
no trigger [ trigger-id ]
Command Default
No trigger is defined.
Parameters
trigger-id
Specifies an ID number for the trigger. Valid values are 1 through 100, and must be unique per event-handler profile.
raslog raslog-id
Specifies a RASlog message ID as the trigger.
pattern posix-ext-regex
Specifies a POSIX extended regular expression to search within the specified RASlog message ID.
Modes
Event-handler configuration mode
Usage Guidelines
You can create from 1 through 100 triggers per profile.
You can also define one trigger as part of the event-handler command.
To delete one or all triggers, use the no form of this command, as follows:
• To delete all triggers, enter no trigger.
• To delete a specific trigger, enter no trigger trigger-id
NOTE
You cannot delete the last remaining trigger from an activated event-handler
profile.
You can modify an existing trigger without deleting it and then re-creating it.
If the event-handler for which you are modifying triggers is active on the device, the changes take effect with no need to de-
activate and re-activate the event-handler.
Examples
The following example defines triggers in two event handlers.
The following example defines a trigger that uses POSIX extended REGEX to search for a match within a specified RASlog
message ID.
RASlog message NSM-1003 includes "interface interface-name is link down", indicating that an interface is offline because the
link is down. The REGEX searches within such a message for an interface from 0/1 through 0/9.
History
Release version Command history
trigger-function
For an implementation of an event-handler profile, if multiple triggers are defined for an event-handler action, specifies if the
action runs only if all of the triggers occur; or if one is sufficient.
Syntax
trigger-function { OR | AND { time-window seconds } }
no trigger-function
Command Default
The event-handler action runs if any of the triggers occur (OR).
Parameters
OR
The event-handler action runs if any of the triggers occur.
AND
The event-handler action runs only if all of the triggers occur.
time-window seconds
In seconds, specify the time window within which all of the triggers must occur in order that the event-handler
action runs.
Following an initial triggering of an event-handler action, any subsequent trigger launches the action an
additional time if the following conditions are true:
• The trigger-mode parameter is set to the default each-instance.
• The subsequent trigger occurs within the specified time-window.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command sets the trigger-function setting to the default OR option.
Examples
The following example determines that the event-handler action runs only if all of the triggers occur within 120 seconds.
History
Release version Command history
trigger-mode
For an implementation of an event-handler profile, specifies if recurring trigger conditions can launch an event-handler action
more than once.
Syntax
trigger-mode mode
no trigger-mode
Command Default
Each time the trigger condition occurs, the event-handler action is launched.
Parameters
mode
Specifies if an event-handler action can be triggered only once or more than once.
each-instance
The event-handler action is launched on each trigger instance received.
on-first-instance
As long as the device is running, the event-handler action is launched only once. Following a device restart,
the event-handler action can be triggered again.
only-once
For the duration of a device configuration, the event-handler action is launched only once.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command resets the trigger-mode setting to the default each-instance option.
Examples
The following example sets the trigger mode to on-first-instance.
History
Release version Command history
tvf-domain
Creates one or more Transparent VLAN Flooding (TVF) domains.
Syntax
tvf-domain tvf-domain-id
no tvf-domain tvf-domain-id
Parameters
tvf-domain-id
Specifies the ID of the TVF domain. Valid values are from 1 through 4096. To specify a range of domains, insert a
hyphen (-) between the beginning and ending integers (for example, 5-16). To specify individual domains and ranges
of domains, separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas.
Modes
Global configuration mode
Usage Guidelines
This command is available only in NPB system-mode.
TVF forwards packets without CPU intervention—such as MAC learning or MAC destination lookups—enabling line-rate traffic
forwarding.
Under Network Packet Brokering (NPB), TVF domains are required for the traffic replication feature.
Examples
The following example creates a TVF domain.
History
Release version Command history
tvf-domain (interface)
Assigns and removes Transparent VLAN Flooding (TVF) domains from a physical or port-channel interface.
Syntax
tvf-domain { add tvf-domain-id | all | except tvf-domain-id | none | remove tvf-domain-id }
Command Default
No TVF domains are assigned to the interface.
Parameters
add tvf-domain-id
Assigns one or more TVF domains to the interface. To specify a range of IDs, insert a hyphen between the beginning
and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with commas (for
example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
all
Assigns all defined TVF domains to the interface.
except tvf-domain-id
Assigns all TVF domains to the interface, except for those specified. To specify a range of IDs, insert a hyphen
between the beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate
them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253
characters.
none
Removes all TVF domains assigned to the interface.
remove tvf-domain-id
Removes one or more TVF domains from the interface. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs, separate them with
commas (for example: 1,5-7,55). Do not insert spaces after commas. You can enter a maximum of 253 characters.
Modes
Interface sub-type configuration mode
Usage Guidelines
Under Network Packet Brokering (NPB), TVF domains are required for the traffic replication feature.
This command is available only in NPB mode.
You can create as many as 4096 TVF domains. Domain members can be tagged and untagged ports. There is no software
limitation on the number of member ports.
Examples
The following example assigns a TVF domain that you create to a physical interface.
History
Release version Command history
type
Specifies whether a VXLAN overlay gateway uses hardware VXLAN tunnel endpoint (VTEP) or Layer 2 extension integration.
Syntax
type { layer2-extension }
Command Default
Layer 2 extension integration is the default behavior.
Parameters
layer2-extension
Specifies Layer 2 extension integration.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
There is no no form of this command. The overlay gateway must have a type.
Examples
The following example specifies Layer 2 extension:
History
Release version Command history
uda access-list
Creates a user-defined ACL (UDA). UDAs offer greater flexibility than other ACLs in defining deny and permit rules. This
flexibility is required for certain Network Packet Broker (NPB) scenarios.
Syntax
uda access-list extended acl-name
Command Default
No UDA is defined.
Parameters
extended
Specifies an extended ACL. Extended ACLs support source and destination addresses, as well as other parameters.
UDAs cannot be standard ACLs, which filter by source address only.
acl-name
Specifies an ACL name unique among all ACLs (Layer 2, Layer 3, and UDAs). The name can be up to 63 characters
in length, and must begin with an alphanumeric character. No special characters are allowed, except for the underscore
and hyphen.
Modes
Global configuration mode
Usage Guidelines
Ths command is supported only in NPB system mode.
A UDA starts functioning on an interface—for aggregation, replication, or forwarding—only if the following flow is implemented:
• Create a UDA profile, using the uda-key profile command.
• For the profile, specify the header types in the expected packet structure, using the flow command.
• For the profile, specify the header fields to match, using the uda-key command.
• Apply the profile to the interface, using the uda-profile-apply command.
• Create a UDA, using the uda access-list command.
• Create one or more permit or deny rules in the UDA, using the [ seq seq-value ] { deny | permit } command.
• Create a route-map, using the route-map command.
• Apply the UDA to the route-map, using the match uda address acl command.
• In the route-map, specify the egress interface, using the set interface or set next-hop-tvf-domain command.
• On a physical or port-channel interface, apply the route map to the ingress interface, using the npb policy route-map
command.
To delete a UDA that is not referenced by any route-map, use the no form of this command.
Examples
The following example creates a UDA.
History
Release version Command history
uda-key
In a user-defined ACL (UDA)-profile, specifies up to four header fields for matching.
Syntax
uda-key0 header{0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 } header-field
Command Default
No UDA key is specified.
Parameters
uda-key{0 | 1 | 2 | 3 }
Specifies 1 through 4 UDA keys. You assign a header type and field to each key.
header{0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 }
Specifies a header type defined in the flow command.
header-field
Specifies a supported field for one of the header types defined in the flow command. For fields supported for each
header type, refer to Usage Guidelines.
Modes
UDA-profile configuration mode
Usage Guidelines
Ths command is supported only in NPB system mode.
You are not required to specify all four UDA keys. Keys not specified are programmed as match always (don't care).
You can specify fields from a header type in more than one UDA key.
A UDA starts functioning on an interface—for aggregation, replication, or forwarding—only if the following flow is implemented:
• Create a UDA profile, using the uda-key profile command.
• For the profile, specify the header types in the expected packet structure, using the flow command.
• For the profile, specify the header fields to match, using the uda-key command.
• Apply the profile to the interface, using the uda-profile-apply command.
• Create a UDA, using the uda access-list command.
• Create one or more permit or deny rules in the UDA, using the [ seq seq-value ] { deny | permit } command.
• Create a route-map, using the route-map command.
• Apply the UDA to the route-map, using the match uda address acl command.
• In the route-map, specify the egress interface, using the set interface or set next-hop-tvf-domain command.
• On a physical or port-channel interface, apply the route map to the ingress interface, using the npb policy route-map
command.
The following tables display the fields supported for each header type:
DIP 32 Destination IP
SIP 32 Source IP
PROTOCOL 8 IP protocol
TOTAL_LENGTH 16 Total length
TOS 8 Type of service (DSCP & ECN)
ECN 2 ECN
DSCP 6 DSCP
TARGET_IP 32 Target IP
TARGET_HW_ADDR_16_47 32 Bits 16–47 of target HW address
TARGET_HW_ADDR_0_15 16 Bits 0–15 of target HW address
SENDER_IP_16_31 16 Bits 16–31 of sender IP
SENDER_IP_0_15 16 Bits 0–15 of sender IP
SENDER_HW_ADDR_32_47 16 Bits 32–47 of sender HW address
SENDER_HW_ADDR_0_31 32 Bits 0–31 of sender HW address
TYPE 8 Type
Examples
The following example configures a UDA profile, creates a flow, and specifies header types and fields.
History
Release version Command history
uda-key profile
Creates a user-defined ACL (UDA) profile, which specifies packet header fields for filtering.
Syntax
uda-key profile profile-name
Command Default
No UDA profile is defined.
Parameters
profile-name
Specifies a unique UDA-profile name. Valid names range from 1 through 63 characters.
Modes
Global configuration mode
Usage Guidelines
Ths command is supported only in NPB system mode.
A UDA starts functioning on an interface—for aggregation, replication, or forwarding—only if the following flow is implemented:
• Create a UDA profile, using the uda-key profile command.
• Configure the profile, using the flow and uda-key commands.
• Apply the profile to the interface, using the uda-profile-apply command.
• Create a UDA, using the uda access-list command.
• Create one or more permit or deny rules in the UDA, using the [ seq seq-value ] { deny | permit } command.
• Create a route-map, using the route-map command.
• Apply the UDA to the route-map, using the match uda address acl command.
• In the route-map, specify the egress interface, using the set interface or set next-hop-tvf-domain command.
• On a physical or port-channel interface, apply the route map to the ingress interface, using the npb policy route-map
command.
To delete a UDA profile that is not applied to any interfaces, use the no form of this command.
Examples
The following example defines a UDA profile.
History
Release version Command history
uda-profile-apply
Applies a UDA profile to an Ethernet or port-channel interface.
Syntax
uda-profile-apply profile-name
no uda-profile-apply profile-name
Command Default
No UDA profile is applied.
Parameters
profile-name
Specifies a unique UDA-profile name. Valid names range from 1 through 63 characters.
Modes
Ethernet interface configuration mode
Usage Guidelines
You can apply a UDA profile only to an Ethernet or to a port-channel interface.
It is not sufficient for a UDA to be applied to an interface—in a route-map. Unless a UDA-key profile is also applied to that
interface, traffic on that interface is programmed as match-always.
To remove a UDA profile from an interface, use the no form of this command.
Examples
The following example applies a UDA profile to an Ethernet interface.
History
Release version Command history
unlock username
Unlocks a locked user account.
Syntax
unlock username name
Parameters
name
Specifies the name of the user account.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to unlock a user who has been locked out because of unsuccessful login attempts. A user account is locked
by the system when the configured threshold for login retries has been reached.
Examples
The following example unlocks a user account.
History
Release version Command history
update-time
Configures the interval at which BGP next-hop tables are modified. BGP next-hop tables should always have IGP (non-BGP)
routes.
Syntax
update-time sec
no update-time sec
Parameters
sec
Update time in seconds. Range is from 0 through 30. Default is 5 seconds.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The update time determines how often the device computes the routes (next-hops). Lowering the value set by the update-time
command increases the convergence rate.
By default, the device updates the BGP4 next-hop tables and affected BGP4 routes five seconds following IGP route changes.
Setting the update time value to 0 permits fast BGP4 convergence for situations such as a link failure or IGP route changes,
starting the BGP4 route calculation in subsecond time.
NOTE
Use the advertisement-interval command to determine how often to advertise IGP routes to the BGP neighbor.
Examples
The following example sets the BGP4+ update-time interval to 30.
History
Release version Command history
usb
Enables or disables an attached USB device. The device is inaccessible until it is enabled.
Syntax
usb { on | off }
Parameters
on
Turns the USB device on.
off
Turns the USB device off.
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local device. A device reload will automatically turn the USB device off.
Examples
To enable a USB device attached to the local device:
device# usb on
History
Release version Command history
usb dir
Lists the contents of an attached USB device.
Syntax
usb dir
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local device. The USB device must be enabled before this function is available.
Examples
To list the contents of the USB device attached to the local device:
History
Release version Command history
usb remove
Removes a file from an attached USB device.
Syntax
usb remove directory directory file file
Parameters
directory directory
Specifies one the name of the directory where the file you want to remove is located. Valid USB storage directories
are /firmware, /firmwarekey, /support, and /config.
file file
Specifies the name of the file to be removed.
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local device. The USB device must be enabled before this function is available.
Examples
The following example removes a configuration file from a USB device attached to the local device.
History
Release version Command history
use-v2-checksum
Enables the v2 checksum computation method for a VRRPv3 IPv4 session.
Syntax
use-v2-checksum
no use-v2-checksum
Command Default
VRRPv3 uses the v3 checksum computation method.
Modes
Virtual-router-group configuration mode
Usage Guidelines
Some non-Extreme devices only use the v2 checksum computation method in VRRPv3. This command enables v2 checksum
computation method in VRRPv3 and provides interoperability with these non-Extreme devices.
The no form of this command enables the default v3 checksum computation method in VRRPv3 sessions.
Examples
The following example shows the v2 checksum computation method enabled for an VRRPv3 IPv4 session on an Extreme
device.
History
Release version Command history
Syntax
user username
no user username
Parameters
username
Specifies the account login name.
Modes
Alias configuration mode
Usage Guidelines
To delete all aliases defined for a specified user, enter the no form of this command.
Examples
The following example accesses user-alias configuration mode for the user jdoe, and defines a user-level alias named "sv" for
the show version command.
History
Release version Command history
username
Creates and configures a user account.
Syntax
username username password password role role_name [ access-time HHMM to HHMM ] [ desc description ] [ enable { true
| false } ] [ encryption-level { 0 | 7 } ] [ expire { never | YYYY-MM-DD } ]
no username name
Parameters
username
Specifies the account login name.
desc description
Specifies a description of the account (optional). The description can be up to 64 characters long, and can include any
printable ASCII character, except for the following characters: single quotation marks (‘), double quotation marks ("),
exclamation point (!), colon (:), and semi-colon (;). If the description contains spaces, enclose the text in double
quotation marks.
enable
Enables or disables the account.
true
(Default) Enables the account.
false
Disables the account. A user whose account is disabled cannot log in.
expire
Specifies the password expiration setting.
never
(Default) Does not specify a password expiration date.
YYYY-MM-DD
Specifies a password expiration date.
password password
Specifies the account password. To use the exclamation mark (!) character, either precede it with the escape character
(\)—secret\!password—or enclose the password within double quotes—"secret!password".
role role_name
Specifies the role assigned to the username account.
encryption-level { 0 | 7 }
Specifies the password encryption level. The values are 0 (clear text) and 7 (encrypted). Clear text (0) is the default. If
service password-encryption is enabled, it overrides a user-level setting.
Modes
Global configuration mode
Usage Guidelines
The username must be from 1 through 40 characters. It must begin with a letter or underscore and be comprised of only
letters, numbers, underscore and period. A username is case sensitive. It cannot be the same as that of an existing role.
When creating a username, you must specify a password and a role. When modifying a username, it is sufficient to enter
username username, followed by the new values.
If a user’s password, access time, or role is changed, any login sessions for that user are terminated.
To specify access-time, use the system time defined for the SLX-OS operating system. For the current system time, enter
show clock.
Examples
The following example configures a user account.
The following example modifies an existing user account, restricting the hours that an existing user may be logged in from
08:00 AM through 18:00 PM.
History
Release version Command history
virtual-ip
Configures a virtual IPv4 address or IPv6 address for the virtual router.
Syntax
virtual-ip { ipv4-address | ipv6-address }
Parameters
ipv4-address
Virtual IPv4 address of the virtual router.
ipv6-address
Virtual IPv6 address of the virtual router.
Modes
Virtual-router-group configuration mode
Usage Guidelines
The virtual IPv4 address or IPv6 address is the IP address that an end-host sets as its default gateway. The virtual IP address
must belong to the same subnet as the underlying interface. A maximum of 16 virtual IP addresses can be configured for
VRRP; only one virtual IP address can be configured for VRRP-E. The session is enabled as soon as the first virtual IP address
is configured.
You can perform this command for VRRP or VRRP-E. VRRPv3 introduced the ability to use an IPv6 address when an IPv6
VRRPv3 group is configured.
This command accepts both fe80/10 link local addresses or fe80/64 addresses as virtual-IP.
Enter the no virtual-ip command with a specified virtual IP address to delete the specified virtual IP address
Examples
To assign a virtual IP address of 192.53.5.1 to the VRRP virtual group 1:
To assign a virtual IPv6 address of 2001:2019:8192::1 to the VRRP-Ev3 virtual group 19:
History
Release version Command history
virtual-mac
Enables generation of a virtual MAC with 0 IP hash.
Syntax
virtual-mac virtual_mac_address
Parameters
virtual_mac_address
Specifies a virtual MAC address.
Modes
VRRP-Extended group configuration mode
Usage Guidelines
The distributed gateway functionality depends on VRRP-E for multi-homing. By default, the VRRP-E virtual MAC is derived as
02:e0:52:<2-byte-ip-hash>:<1-byte-vrid>. The gateway requires that the virtual MAC be a function of only VRID. The two-byte
hash of the virtual IP should be set to zeros, for example, 02e0.5200.00xx:100.
Examples
To enable the generation of a virtual MAC:
History
Release version Command history
vlan
Specifies a VLAN and enters VLAN configuration mode.
Syntax
vlan vlan_id
no vlan vlan_id
Command Default
No VLAN is configured.
Parameters
vlan_id
Specifies a VLAN ID. Range is from 1 through 4090.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to delete a VLAN.
Examples
To configure VLAN 10:
History
Release version Command history
vlan (EVPN)
Specifies a VLAN in Ethernet Private Virtual Network (EVPN) mode, enters EVPN VLAN configuration mode, and adds or
removes VLANs.
Syntax
vlan vlan_id [add|remove]
no vlan vlan_id ]
Command Default
No VLAN is configured.
Parameters
vlan_id
Specifies a VLAN ID for the EVPN instance. Range is from 1 through 4090.
add
Adds a VLAN ID or range of VLAN IDs to the EVPN instance. Range is from 1 through 4090.
add
Adds a VLAN ID or range of VLAN IDs to the EVPN instance. Range is from 1 through 4090.
Modes
EVPN instance configuration mode
Usage Guidelines
Use the no form of this command to delete a VLAN from the EVPN instance.
Examples
To configure VLAN 10 and enter EVPN VLAN configuration mode:
History
Release version Command history
Syntax
vlan dot1q tag native
Command Default
The native VLAN is enabled.
Modes
Global configuration mode
Usage Guidelines
Usually, you configure 802.1Q trunks with a native VLAN ID, which strips tagging from all packets on that VLAN.
To maintain the tagging on the native VLAN and drop untagged traffic, use the vlan dot1q tag native command. The switch will
tag the traffic received on the native VLAN and admit only 802.1Q-tagged frames.
Control traffic continues to be accepted as untagged on the native VLAN on a trunked port, even when the vlan dot1q tag
native command is enabled.
Enter no vlan dot1q tag native to disable dot1q (IEEE 802.1Q) tagging for all native VLANs on all trunked ports on the switch.
History
Release version Command history
vrf
Creates a Virtual Routing and Forwarding (VRF) instance and enters VRF configuration mode.
Syntax
vrf name
Parameters
name
Character string for the name of the VRF. The string can be up 24 characters long, but should not contain punctuation
or special characters.
Modes
Global configuration mode
Examples
To create the VRF instance "myvrf" and enter VRF configuration mode:
History
Release version Command history
vrf forwarding
Configures any port as a VRF port.
Syntax
vrf forwarding vrf_name
Parameters
vrf_name
The name of the VRF option for the port.
Command Default
By default, the out-of-band (OOB) management port (the eth0 interface) is part of the pre-defined VRF named mgmt-vrf.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of this command disables this VRF.
Examples
To enable the management VRF on an Ethernet interface and assign the interface to a subnet:
History
Release version Command history
vrf mgmt-vrf
Configures routes on a management VRF port.
Syntax
vrf mgmt-vrf
no vrf mgmt-vrf
Command Default
None
Modes
Global configuration mode
Usage Guidelines
The no form of this command disables the management VRF.
The management VRF is a dedicated, secure VRF instance that allows users to manage the router inband on switched virtual
interfaces (SVIs) and physical interfaces. The name of this VRF instance is "mgmt-vrf;" this instance cannot be deleted.
A management port is any port that is part of the management VRF. The OOB port cannot be removed from the management
VRF. In addition, Layer 3 virtual and physical ports (also known as front-end or inband ports) can be part of the management
VRF. Inband ports can be moved, by means of the CLI, into and out of the management VRF.
Examples
The following configures an IPv4 route subnet for the management VRF, enters address family IPv4 configuration mode, and
assigns the management VRF to an Ethernet interface.
History
Release version Command history
vrrp-extended-group
Configures a virtual-router-extended group and enters into the virtual router configuration mode..
Syntax
vrrp-extended-group group-ID
no vrrp-extended-group group-ID
Parameters
group-ID
A user-assigned number from 1 through 255 that you assign to the virtual router group.
Modes
Virtual Ethernet (ve) interface configuration mode
Usage Guidelines
This configuration is for virtual Ethernet (ve) interfaces only.
If you remove a group, you cannot retrieve it. You would have to redo the configuration procedure.
Examples
The following example shows how to assign the ve interface with a vlan number of 20 to the virtual router extended group with
the ID of 1. (First you must enable VRRP-E on the switch.)
History
Release version Command history
vrrp-group
Configures a virtual router group (VRRP) and enters into the virtual router configuration mode.
Syntax
vrrp-group group-ID [ version { 2 | 3 } ]
Command Default
VRRP version 2 is the default.
Parameters
group-ID
A value from 1 through 255 that you assign to the virtual router group.
version
Specifies in which version of VRRP the IPv4 VRRP group is to be configured.
2|3
Version 2 or version 3 of VRRP.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no vrrp-group group-ID to remove a specific VRRP group. If you remove a group, you cannot retrieve it. You would have
to redo the configuration procedure.
You can specify in which version of VRRP the VRRP group is configured using the version keyword and either 2 or 3 as the
version number. VRRPv3 supports both IPv4 and IPv6 addresses.
Examples
The following example shows how to assign an Ethernet interface to the virtual router group with the ID of 1. (First you must
enable VRRP on the switch.)
The following example shows how to assign an Ethernet interface to the virtual router group with the ID of 1 for VRRPv3. (First
you must enable VRRP on the switch.)
History
Release version Command history
write erase
Returns the switch to factory default state.
Syntax
write erase
Modes
Privileged EXEC mode
Usage Guidelines
This command can be used for device recovery or device configuration reset to the factory default state. Due to its disruptive
nature, this command prompts the user about the consequence of losing all current user configuration and resetting the switch
to the factory default state. It waits for the user's confirmation before proceeding.
Examples
The following command shows executing the write erase command.
History
Release version Command history