Extreme Ware Command Ref 73 e
Extreme Ware Command Ref 73 e
3e
Command Reference Guide
All other registered trademarks, trademarks and service marks are property of their respective owners.
2
Contents
Preface
enable license 68
history 69
reboot 70
show banner 71
show dns-client 72
show esrp-aware 73
show switch 74
traceroute 76
This preface provides an overview of this guide, describes guide conventions, and lists other
publications that may be useful.
Introduction
This guide provides the complete syntax for all the 7.3e commands available in the ExtremeWare®
software running on the Summit series “e” switches from Extreme Networks®.
This guide is intended for use as a reference by network administrators who are responsible for
installing and setting up network equipment. It assumes knowledge of the switch configuration. For
conceptual information and guidance on configuring Extreme Networks switches, see the ExtremeWare
7.3e User Guide.
Conventions
Table 1 andTable 2 list conventions that are used throughout this guide.
Command Titles
For clarity and brevity, the command titles omit variables, values, and optional arguments. The
complete command syntax is displayed directly below the command titles.
Related Publications
The publications related to this one are:
Documentation for Extreme Networks products is available on the World Wide Web at the following
location:
http://www.extremenetworks.com/
The following two ExtremeWare publications are available as PDF files that are designed to be used
online together:
The user guide PDF file provides links that connect you directly to relevant command information in
the command reference guide PDF file. This quick-referencing capability enables you to easily find
detailed information in the command reference guide for any command mentioned in the user guide.
To ensure that the quick-referencing feature functions properly, follow these steps:
1 Download both the user guide PDF file and the command reference guide PDF file to the same
destination directory on your computer.
2 You may open one or both PDF files and to enable cross-referenced linking between the user guide
and command reference guide; however, it is recommended that for ease of use, you keep both files
open concurrently on your computer desktop.
NOTE
If you activate a cross-referencing link from the ExtremeWare 7.3e User Guide PDF file to the command
reference PDF file when the command reference PDF file is closed (that is, not currently open on your
computer desktop), the system will close the user guide PDF file and open the command reference PDF
file. To keep both PDF files open when you activate a cross-reference link, open both PDF files before
using the link.
Introduction
This guide provides details of the command syntax for all ExtremeWare commands as of
ExtremeWare version 7.3e.
NOTE
ExtremeWare 7.3e only supports the Summit 200, Summit 300, and Summit 400 series of switches.
This guide does not provide feature descriptions, explanations of the technologies, or configuration
examples. For information about the various features and technologies supported by Extreme Networks
switches, see the ExtremeWare 7.3e User Guide. This guide does not replace the user guide; this guide
supplements the user guide.
Audience
This guide is intended for use by network administrators who are responsible for installing and setting
up network equipment. It assumes a basic working knowledge of the following:
• Local area networks (LANs)
• Ethernet concepts
• Ethernet switching and bridging concepts
• Routing concepts
• Internet Protocol (IP) concepts
• Routing Information Protocol (RIP) and Open Shortest Path First (OSPF) concepts
• IP Multicast concepts
• Distance Vector Multicast Routing Protocol (DVMRP) concepts
• Simple Network Management Protocol (SNMP)
This guide also assumes that you have read the ExtremeWare 7.3e User Guide.
NOTE
The ExtremeWare command line interface (CLI) supports only the US character set.
• Command Syntax—The actual syntax of the command. The syntax conventions (the use of braces or
curly brackets, for example) are defined in the section “Understanding the Command Syntax” on
page 37.
• Description—A brief (one sentence) summary of what the command does.
• Syntax Description—The definition of any keywords and options used in the command.
• Default—The defaults, if any, for this command. The default can be the default action of the
command if optional arguments are not provided, or it can be the default state of the switch (such as
for an enable/disable command).
• Usage Guidelines—Information to help you use the command. This may include prerequisites,
prohibitions, and related commands, as well as other information.
• Example—Examples of the command usage, including output, if relevant.
• History—The version of ExtremeWare in which the command was introduced, and version(s) where
it was modified, if appropriate.
You may see a variety of symbols shown as part of the command syntax. These symbols explain how to
enter the command, and you do not type them as part of the command itself. Table 3 summarizes
command syntax symbols.
Symbol Description
angle brackets < > Enclose a variable or value. You must specify the variable or value. For
example, in the syntax
configure vlan <vlan name> ipaddress <ip_address>
you must supply a VLAN name for <vlan name> and an address for
<ip_address> when entering the command. Do not type the angle
brackets.
square brackets [ ] Enclose a required value or list of required arguments. One or more
values or arguments can be specified. For example, in the syntax
use image [primary | secondary]
you must specify either the primary or secondary image when entering
the command. Do not type the square brackets.
vertical bar | Separates mutually exclusive items in a list, one of which must be
entered. For example, in the syntax
configure snmp community [read-only | read-write]
<string>
you must specify either the read or write community string in the
command. Do not type the vertical bar.
braces { } Enclose an optional value or a list of optional arguments. One or more
values or arguments can be specified. For example, in the syntax
reboot {<date> <time> | cancel}
you can specify either a particular date and time combination, or the
keyword cancel to cancel a previously scheduled reboot. If you do not
specify an argument, the command will prompt asking if you want to
reboot the switch now. Do not type the braces.
If the command is one where the next option is a named component, such as a VLAN, access profile, or
route map, the syntax helper will also list any currently configured names that might be used as the
next option. In situations where this list might be very long, the syntax helper will list only one line of
names, followed by an ellipses to indicate that there are more names than can be displayed.
The syntax helper also provides assistance if you have entered an incorrect command.
Abbreviated Syntax
Abbreviated syntax is the shortest unambiguous allowable abbreviation of a command or parameter.
Typically, this is the first three letters of the command. If you do not enter enough letters to allow the
switch to determine which command you mean, the syntax helper will provide a list of the options
based on the portion of the command you have entered.
NOTE
When using abbreviated syntax, you must enter enough characters to make the command unambiguous
and distinguishable to the switch.
Names
All named components of the switch configuration must have a unique name. Names must begin with
an alphabetical character and are delimited by whitespace, unless enclosed in quotation marks.
Command Shortcuts
All named components of the switch configuration must have a unique name. Components are named
using the create command. When you enter a command to configure a named component, you do not
need to use the keyword of the component. For example, to create a VLAN, you must enter a unique
VLAN name:
create vlan engineering
Once you have created the VLAN with a unique name, you can then eliminate the keyword vlan from
all other commands that require the name to be entered. For example, instead of entering the command
configure vlan engineering delete port 1-3,6
Many commands that accept the parameter <portlist>, also accept a VLAN identifier. When this
option is available in a command, it is run on all ports in the VLAN including all ports in a trunk.
You can add additional slot and port numbers to the list, separated by a comma:
port 1:1,1:8,1:10
You can add additional port numbers to the list, separated by a comma:
port 1-3,6,8
Many commands that accept the parameter <portlist>, also accept a VLAN identifier. When this
option is available in a command, it is run on all ports in the VLAN including all ports in a trunk.
Line-Editing Keys
Table 4 describes the line-editing keys available using the CLI.
Key(s) Description
Backspace Deletes character to left of cursor and shifts remainder of line to left.
Delete or [Ctrl] + D Deletes character under cursor and shifts remainder of line to left.
[Ctrl] + K Deletes characters from under cursor to end of line.
Insert Toggles on and off. When toggled on, inserts text and shifts previous
text to right.
Left Arrow Moves cursor to left.
Right Arrow Moves cursor to right.
Home or [Ctrl] + A Moves cursor to first character in line.
End or [Ctrl] + E Moves cursor to last character in line.
[Ctrl] + L Clears screen and movers cursor to beginning of line.
[Ctrl] + P or Displays previous command in command history buffer and places cursor
Up Arrow at end of command.
[Ctrl] + N or Displays next command in command history buffer and places cursor at
Down Arrow end of command.
[Ctrl] + U Clears all characters typed from cursor to beginning of line.
[Ctrl] + W Deletes previous word.
Command History
ExtremeWare “remembers” the last 49 commands you entered. You can display a list of these
commands by using the following command:
history
• Commands used for accessing and configuring the switch including how to set up user accounts,
passwords, date and time settings, and software licenses
• Commands used for configuring the Domain Name Service (DNS) client
• Commands used for checking basic switch connectivity
A user-level account has viewing access to all manageable parameters, with the exception of:
• User account database
• SNMP community strings
A user-level account can use the ping command to test device reachability and change the password
assigned to the account name.
An administrator-level account can view and change all switch parameters. It can also add and delete
users and change the password associated with any account name. The administrator can disconnect a
management session that has been established by way of a Telnet connection. If this happens, the user
logged on by way of the Telnet connection is notified that the session has been terminated.
The DNS client in ExtremeWare augments certain ExtremeWare commands to accept either IP addresses
or host names. For example, DNS can be used during a Telnet session when you are accessing a device
or when using the ping command to check the connectivity of a device.
The switch offers the following commands for checking basic connectivity:
• ping
• traceroute
The ping command enables you to send Internet Control Message Protocol (ICMP) echo messages to a
remote IP device. The traceroute command enables you to trace the routed path between the switch
and a destination endstation.
clear session
clear session <number>
Description
Terminates a Telnet session from the switch.
Syntax Description
Default
N/A.
Usage Guidelines
An administrator-level account can disconnect a management session that has been established by way
of a Telnet connection. You can determine the session number of the session you want to terminate by
using the show session command. The show session output displays information about current
Telnet sessions including:
• The session number
• The login date and time
• The user name
• The type of Telnet session
Depending on the software version running on your switch, additional session information may be
displayed. The session number is the first number displayed in the show session output.
Example
The following command terminates session 4 from the system:
clear session 4
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
configure account
configure account <user account> {encrypted} {<password>}
Description
Configures a user account password.
Syntax Description
Default
N/A.
Usage Guidelines
You must create a user account before you can configure a user account. Use the create account
command to create a user account.
You must have administrator privileges to change passwords for accounts other than your own. User
names and passwords are case-sensitive.
The encrypted option is used by the switch when generating an ASCII configuration file (using the
upload configuration command), and parsing a switch-generated configuration file (using the
download configuration command). Do not select the encrypted option in the CLI.
• The password cannot be specified on the command line. Instead, the switch will interactively prompt
you to enter the password, and will then prompt you to reenter the password to verify that you have
entered it correctly.
• Passwords must have a minimum of 1 character and can have a maximum of 30 characters.
Example
The following command defines a new password for the account admin:
configure account admin
Your keystrokes will not be echoed as you enter the new password. After you enter the password, the
switch will then prompt you to reenter it.
Reenter password:
Assuming you enter it successfully a second time, the password is now changed.
In ExtremeWare 4.1.19, the following command defines a new password, Extreme1, for the account
admin:
configure account admin Extreme1
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
configure banner
configure banner
Description
Configures the banner string that is displayed at the beginning of each login prompt of each session.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Press [Return] at the beginning of a line to terminate the command and apply the banner. To clear the
banner, press [Return] at the beginning of the first line.
You can enter up to 24 rows of 79-column text that is displayed before the login prompt of each session.
Example
The following command adds a banner, Welcome to the switch, before the login prompt:
configure banner [Return]
Welcome to the switch
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the network login banner that is displayed at the beginning of each login prompt of each
session.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
The network login banner and the switch banner cannot be used at the same time. If you configure a
Network Login banner, users do not see the normal banner. If no banner is configured, the Extreme logo
is displayed. The network login banner displays in HTML. No links or images are supported.
Press [Enter] to enter text on a new line. Press [Enter] twice to finish entering the network login banner.
You can enter up to 1024 characters in the banner.
Example
The following command adds the banner “Welcome to your switch” in 8 point purple Arial before the
login prompt:
configure banner netlogin [Enter]
<font face="Arial" size=8 color=534579></font>Welcome to your switch
[Enter]
[Enter]
History
This command was introduced in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a DNS name server to the available server list for the DNS client.
Syntax Description
Default
N/A.
Usage Guidelines
Eight DNS name servers can be configured.
Example
The following command specifies that the switch use the DNS server 10.1.2.1:
configure dns-client add 10.1.2.1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a domain name to the domain suffix list.
Syntax Description
Default
N/A.
Usage Guidelines
The domain suffix list can include up to six items. If the use of all previous names fails to resolve a
name, the most recently added entry on the domain suffix list will be the last name used during name
resolution. This command will not overwrite any exiting entries. If a null string is used as the last suffix
in the list, and all other lookups fail, the name resolver will attempt to look up the name with no suffix.
Example
The following command configures a domain name and adds it to the domain suffix list:
configure dns-client add domain-suffix xyz_inc.com
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a DNS name server to the available server list for the DNS client.
Syntax Description
Default
N/A.
Usage Guidelines
Up to three DNS name servers can be configured in ExtremeWare versions prior to 6.2.1. In
ExtremeWare 6.2.1 and later, eight DNS name servers can be configured.
Example
The following command specifies that the switch use the DNS server 10.1.2.1:
configure dns-client add name-server 10.1.2.1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the domain that the DNS client uses if a fully qualified domain name is not entered.
Syntax Description
Default
N/A.
Usage Guidelines
Sets the DNS client default domain name to domain_name. The default domain name will be used to
create a fully qualified host name when a domain name is not specified. For example, if the default
default domain name is set to “food.com” then when a command like “ping dog” is entered, the ping
will actually be executed as “ping dog.food.com”.
Example
The following command configures the default domain name for the server:
configure dns-client default-domain xyz_inc.com
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes a DNS name server from the available server list for the DNS client.
Syntax Description
Default
N/A.
Usage Guidelines
None
Example
The following command removes a DNS server from the list:
configure dns-client delete 10.1.2.1
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a domain name from the domain suffix list.
Syntax Description
Default
N/A.
Usage Guidelines
This command randomly removes an entry from the domain suffix list. If the deleted item was not the
last entry in the list, all items that had been added later are moved up in the list. If no entries in the list
match the domain name specified, an error message will be displayed.
Example
The following command deletes a domain name from the domain suffix list:
configure dns-client delete domain-suffix xyz_inc.com
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes a DNS name server from the available server list for the DNS client.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes a DNS server from the list:
configure dns-client delete name-server 10.1.2.1
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
configure idletimeouts
configure idletimeouts <minutes>
Description
Configures the time-out for idle HTTP, console, and Telnet sessions.
Syntax Description
Default
Default time-out is 20 minutes.
Usage Guidelines
This command configures the length of time the switch will wait before disconnecting idle HTTP,
console, or Telnet sessions. The idletimeouts feature must be enabled for this command to have an effect
(the idletimeouts feature is disabled by default).
Example
The following command sets the time-out for idle HTTP, login and console sessions to 10 minutes:
configure idletimeouts 10
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
configure time
configure time <date> <time>
Description
Configures the system date and time.
Syntax Description
Default
N/A.
Usage Guidelines
The format for the system date and time is as follows:
mm/dd/yyyy hh:mm:ss
The time uses a 24-hour clock format. The AM hours range from 1 through 11, and the PM hours range
from 12 through 23.
Example
The following command configures a system date of February 15, 2002 and a system time of 8:42 AM
and 55 seconds:
configure time 02/15/2002 08:42:55
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
configure timezone
configure timezone {name <std_timezone_ID>} <GMT_offset>
{autodst {name <dst_timezone_ID>} {<dst_offset>}
{begins [every <floatingday> | on <absoluteday>] {at <time_of_day>}
{ends [every <floatingday> | on <absoluteday>] {at <time_of_day>}}}
| noautodst}
Description
Configures the Greenwich Mean Time (GMT) offset and Daylight Saving Time (DST) preference.
Syntax Description
Default
Autodst, beginning every first Sunday in April, and ending every last Sunday in October.
Usage Guidelines
Network Time Protocol (NTP) server updates are distributed using GMT time. To properly display the
local time in logs and other timestamp information, the switch should be configured with the
appropriate offset to GMT based on geographic location.
Automatic DST changes can be enabled or disabled. The default configuration, where DST begins on the
first Sunday in April at 2:00 AM and ends the last Sunday in October at 2:00 AM, applies to most of
North America, and can be configured with the following syntax:
configure timezone <gmt_offst> autodst.
The starting and ending date and time for DST may be specified, as these vary in time zones around the
world.
• Use the every keyword to specify a year-after-year repeating set of dates (e.g. the last Sunday in
March every year)
• Use the on keyword to specify a non-repeating, specific date for the specified year. If you use this
option, you will need to specify the command again every year.
• The begins specification defaults to every first sunday april.
• The ends specification defaults to every last sunday october.
• The ends date may occur earlier in the year than the begins date. This will be the case for countries
in the Southern Hemisphere.
• If you specify only the starting or ending time (not both) the one you leave unspecified will be reset
to its default.
• The time_of_day specification defaults to 2:00
• The timezone IDs are optional. They are used only in the display of timezone configuration
information in the show switch command.
To disable automatic DST changes, re-specify the GMT offset using the noautodst option:
configure timezone <gmt_offst> noautodst.
NTP updates are distributed using GMT time. To properly display the local time in logs and other
timestamp information, the switch should be configured with the appropriate offset to GMT based on
geographical location. Table 5 describes the GMT offsets.
Example
The following command configures GMT offset for Mexico City, Mexico and disables automatic DST:
configure timezone -360 noautodst
The following four commands are equivalent, and configure the GMT offset and automatic DST
adjustment for the US Eastern timezone, with an optional timezone ID of EST:
configure timezone name EST -300 autodst name EDT 60 begins every first sunday april
at 2:00 ends every last sunday october at 2:00
configure timezone name EST -300 autodst name EDT 60 begins every 1 1 4 at 2:00 ends
every 5 1 10 at 2:00
The following command configures the GMT offset and automatic DST adjustment for the Middle
European timezone, with the optional timezone ID of MET:
configure timezone name MET 60 autodst name MDT begins every last sunday march at 1
ends every last sunday october at 1
The following command configures the GMT offset and automatic DST adjustment for New Zealand.
The ending date must be configured each year because it occurs on the first Sunday on or after March 5:
configure timezone name NZST 720 autodst name NZDT 60 begins every first sunday
october at 2 ends on 3/16/2002 at 2
History
This command was first available in ExtremeWare 7.1e.
Modified in ExtremeWare 7.2e to allow configuration of a beginning and ending time for the automatic
DST.
Platform Availability
This command is available on the “e” series platforms.
create account
create account [admin | user] <username> {encrypted} {<password>}
Description
Creates a new user account.
Syntax Description
Default
By default, the switch is configured with two accounts with the access levels shown in Table 6:
You can use the default names (admin and user), or you can create new names and passwords for the
accounts. Default accounts do not have passwords assigned to them.
Usage Guidelines
The switch can have a total of 16 user accounts. There must be one administrator account on the system.
You must have administrator privileges to change passwords for accounts other than your own. User
names and passwords are case-sensitive.
• User account names must have a minimum of 1 character and can have a maximum of 30 characters.
• Passwords must have a minimum of 0 characters and can have a maximum of 16 characters.
• Admin-level users and users with RADIUS command authorization can use the create account
command.
Example
The following command creates a new account named John2 with administrator privileges:
create account admin john2
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete account
delete account <username>
Description
Deletes a specified user account.
Syntax Description
Default
N/A.
Usage Guidelines
Use the show accounts command to determine which account you want to delete from the system. The
show accounts output displays the following information in a tabular format:
• The user name
• Access information associated with each user
• User login information
• Session information
Depending on the software version running on your switch and the type of switch you have, additional
account information may be displayed.
You must have administrator privileges to delete a user account. There must be one administrator
account on the system; the command will fail if an attempt is made to delete the last administrator
account on the system.
Do not delete the default administrator account. If you do, it is automatically restored, with no
password, the next time you download a configuration. To ensure security, change the password on the
default account, but do not delete it. The changed password will remain intact through configuration
uploads and downloads.
If you must delete the default account, first create another administrator-level account. Remember to
manually delete the default account again every time you download a configuration.
Example
The following command deletes account John2:
delete account john2
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable clipaging
disable clipaging
Description
Disables pausing at the end of each show screen.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
The command line interface (CLI) is designed for use in a VT100 environment. Most show command
output will pause when the display reaches the end of a page. This command disables the pause
mechanism and allows the display to print continuously to the screen.
NOTE
Press [q] and then press [Return] to force a pause when CLI paging is disabled.
To view the status of CLI paging on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for CLI
paging.
Example
The follow command disables clipaging and allows you to print continuously to the screen:
disable clipaging
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable idletimeouts
disable idletimeouts
Description
Disables the timer that disconnects idle sessions from the switch.
Syntax Description
This command has no arguments or variables.
Default
Enabled. Timeout 20 minutes.
Usage Guidelines
When idle time-outs are disabled, console sessions remain open until the switch is rebooted or you
logoff. Telnet sessions remain open until you close the Telnet client.
To view the status of idle time-outs on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for idle
time-outs.
Example
The following command disables the timer that disconnects all sessions to the switch:
disable idletimeouts
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
enable clipaging
enable clipaging
Description
Enables the pause mechanism and does not allow the display to print continuously to the screen.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
The command line interface (CLI) is designed for use in a VT100 environment. Most show command
output will pause when the display reaches the end of a page.
To view the status of CLI paging on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for CLI
paging.
If CLI paging is enabled and you use the show tech-support command to diagnose system technical
problems, the CLI paging feature is disabled.
Example
The following command enables clipaging and does not allow the display to print continuously to the
screen:
enable clipaging
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable idletimeouts
enable idletimeouts
Description
Enables a timer that disconnects Telnet and console sessions after 20 minutes of inactivity.
Syntax Description
This command has no arguments or variables.
Default
Enabled. Timeout 20 minutes.
Usage Guidelines
You can use this command to ensure that a Telnet, HTTP, or console session is disconnected if it has
been idle for the required length of time. This ensures that there are no hanging connections.
To view the status of idle time-outs on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for idle
time-outs.
Example
The following command enables a timer that disconnects any Telnet, HTTP, and console sessions after
20 minutes of inactivity:
enable idletimeouts
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable license
enable license [ advanced-edge ] <license_key>
Description
Enables a particular software feature license.
Syntax Description
Default
N/A.
Usage Guidelines
Specify license_key as an integer.
The unconfigure switch all command does not clear licensing information. This feature cannot be
disabled after the license has been enabled on the switch.
Depending on the software version running on your switch, and the type of switch you have, only the
license parameters applicable to your software or switch can be used.
To view the type of license you are currently running on the switch, use the show switch command.
The license key number is not displayed, but the type of license is displayed in the show switch
output. The type of license is displayed after the system name, system location, system contact, and
system MAC address.
Example
The following command enables a full L3 license on the switch:
enable license fullL3
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
history
history
Description
Displays a list of the previous 49 commands entered on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
ExtremeWare “remembers” the last 49 commands you entered on the switch. Use the history
command to display a list of these commands.
Example
The following command displays the previous 49 commands entered on the switch:
history
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
reboot
reboot {time <date> <time> | cancel}
Description
Reboots the switch at a specified date and time.
Syntax Description
Default
N/A.
Usage Guidelines
If you do not specify a reboot time, the switch will reboot immediately following the command, and
any previously scheduled reboots are cancelled. To cancel a previously scheduled reboot, use the
cancel option.
Example
The following command reboots the switch at 8:00 AM on April 15, 2002:
reboot 04/15/2002 08:00:00
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show banner
show banner
Description
Displays the user-configured banner string.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to view the banner that is displayed before the login prompt.
Example
The following command displays the switch banner:
show banner
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show dns-client
show dns-client
Description
Displays the DNS configuration.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays the DNS configuration:
show dns-client
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show esrp-aware
show esrp-aware [vlan <vlan name>]
Description
Displays ESRP awareness information.
Syntax Description
Default
Without the vlan option, the show command displays all VLAN interfaces receiving ESRP packets.
Usage Guidelines
The VLANs associated with the ports connecting an ESRP-aware switch to an ESRP-enabled switch
must be configured using an 802.1Q tag on the connecting port, or, if only a single VLAN is involved, as
untagged.
Example
The following command displays ESRP awareness information for a VLAN named esrpEn.
* Summit400-48t:8 # sh esrp-aware vlan "esrpEn"
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show switch
show switch
Description
Displays the current switch information.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Viewing statistics on a regular basis allows you to see how well your network is performing. If you
keep simple daily records, you will see trends emerging and notice problems arising before they cause
major network faults. This way, statistics can help you get the best out of your network.
This information may be useful for your technical support representative if you have a problem.
Depending on the software version running on your switch, additional or different switch information
may be displayed.
Example
The following command displays current switch information:
show switch
* Summit400-48t:2 # sh sw
SysName: Summit400-48t
SysLocation:
SysContact: [email protected], +1 888 257 3000
System MAC: 00:04:96:18:40:AF
* Summit400-48t:3 #
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
traceroute
traceroute <host name | ip_address> {from <source IP address>} {ttl
<number>} {port <port number>}
Description
Enables you to trace the routed path between the switch and a destination endstation.
Syntax Description
Default
N/A.
Usage Guidelines
To use the host name parameter, you must first configure DNS.
Example
The following command enables the traceroute function to a destination of 123.45.67.8:
traceroute 123.45.67.8
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
SNMP
Any network manager running the Simple Network Management Protocol (SNMP) can manage the
switch, if the Management Information Base (MIB) is installed correctly on the management station.
Each network manager provides its own user interface to the management facilities.
• Authorized trap receivers—An authorized trap receiver can be one or more network management
stations on your network. The switch sends SNMP traps to all trap receivers. Entries in this list can
be created, modified, and deleted using the RMON2 trapDestTable MIB variable, as described in
RFC 2021.
• Authorized managers—An authorized manager can be either a single network management station,
or a range of addresses (for example, a complete subnet) specified by a prefix and a mask. The
switch can have a maximum of eight authorized managers.
• Community strings—The community strings allow a simple method of authentication between the
switch and the remote Network Manager. The default read-only community string is public. The
default read-write community string is private. The community strings for all authorized trap
receivers must be configured on the switch for the trap receiver to receive switch-generated traps.
• System contact (optional)—The system contact is a text field that enables you to enter the name of
the person(s) responsible for managing the switch.
• System name—The system name is the name that you have assigned to this switch. The default
name is the model name of the switch (for example, Summit1).
• System location (optional)—Using the system location field, you can enter an optional location for
this switch.
• SNMP read access—The ability to read SNMP information can be restricted through the use of an
access profile. An access profile permits or denies a named list of IP addresses and subnet masks.
• SNMP read/write access—The ability to read and write SNMP information can be restricted through
the use of an access profile. An access profile permits or denies a named list of IP addresses and
subnet masks.
Telnet
Telnet allows you to access the switch remotely using TCP/IP through one of the switch ports or a
workstation with a Telnet facility. If you access the switch via Telnet, you will use the command line
interface (CLI) to manage the switch and modify switch configurations.
Description
Assigns an access profile that limits which stations have read-only access to the switch.
Syntax Description
Default
All users have access until an access profile is created and specified.
Usage Guidelines
The ability to read SNMP information can be restricted through the use of an access profile. An access
profile permits or denies a named list of IP addresses and subnet masks.
You must create and configure an access profile before you can use this command. You create an access
profile using the create access-profile command. You configure an access profile using the
configure access-profile add command.
Read community strings provide read-only access to the switch. The default read-only community
string is public. The community string for all authorized trap receivers must be configured on the
switch for the trap receiver to receive switch-generated traps. SNMP community strings can contain up
to 32 characters.
To view the SNMP read-only access communities configured on the switch, use the show management
command. The show management command displays information about the switch including the
encrypted names and the number of read-only communities configured on the switch.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
configure snmp access-profile readonly command, use the unconfigure management
command.
Example
The following command allows the user defined access profile admin read-only access to the switch:
configure snmp access-profile readonly admin
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Assigns an access profile that limits which stations have read/write access to the switch.
Syntax Description
Default
All users have access until an access profile is specified.
Usage Guidelines
The ability to read SNMP information can be restricted through the use of an access profile. An access
profile permits or denies a named list of IP addresses and subnet masks.
You must create and configure an access profile before you can use this command. You create an access
profile using the create access-profile command. You configure an access profile using the
configure access-profile command.
Read/write community strings provide read and write access to the switch. The default read/write
community string is private. The community string for all authorized trap receivers must be configured
on the switch for the trap receiver to receive switch-generated traps. SNMP community strings can
contain up to 32 characters.
To view the SNMP read/write access communities configured on the switch, use the show management
command. The show management command displays information about the switch including the names
and the number of read/write communities configured on the switch.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
configure snmp access-profile readwrite command, use the unconfigure management
command.
Example
The following command allows the user defined access profile management read/write access to the
switch:
configure snmp access-profile readwrite management
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds an SNMP read or read/write community string.
Syntax Description
Default
The default read-only community string is public. The default read/write community string is private.
Usage Guidelines
Community strings provide a simple method of authentication between a switch and a remote network
manager. Read community strings provide read-only access to the switch. The default read-only
community string is public. Read-write community strings provide read and write access to the switch.
The default read/write community string is private.
An authorized trap receiver must be configured to use the correct community strings on the switch for
the trap receiver to receive switch-generated traps. In some cases, it may be useful to allow multiple
community strings so that all switches and trap receivers are not forced to use identical community
strings. The configure snmp add community command allows you to add multiple community
strings in addition to the default community string.
To change the value of the default read/write and read-only community strings, use the configure
snmp add community command.
The encrypted option is intended for use by the switch when generating an ASCII configuration file
(using the upload configuration command), or parsing a switch-generated configuration (using the
download configuration command). Do not select the encrypted option in the CLI.
Example
The following command adds a read/write community string with the value extreme:
configure snmp add community readwrite extreme
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add support for encryption.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds the IP address of a trap receiver to the trap receiver list and specifies which SNMPv1/v2c traps
are to be sent.
Syntax Description
Default
Trap receivers are in enhanced mode by default, and the version is SNMPv2c by default.
Usage Guidelines
The IP address can be unicast, multicast, or broadcast.
An authorized trap receiver can be one or more network management stations on your network.
Authorized trap receivers must be configured on the switch for the trap receiver to receive
switch-generated traps. The switch sends SNMP traps to all trap receivers configured to receive the
specific trap group. If no trap groups are specified, all traps will be sent to the receiver. Entries in this
list can be created, modified, and deleted using the RMON2 trapDestTable MIB variable, as described in
RFC 2021.
Table 7 lists the currently defined SNMP trap groups. From time to time, new trap groups may be
added to this command.
To view the SNMP trap receivers configured on the switch, use the show management command. The
show management command displays information about the switch including the destination and
community of the SNMP trap receivers configured on the switch.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
configure snmp add trapreceiver command, use the unconfigure management command.
Example
The following command adds the IP address 10.101.0.100 as a trap receiver with community string
purple:
configure snmp add trapreceiver 10.101.0.100 community purple
The following command adds the IP address 10.101.0.105 as a trap receiver with community string
green, using port 3003:
configure snmp add trapreceiver 10.101.0.105 port 3003 community green
The following command adds the IP address 10.101.0.105 as a trap receiver with community string blue,
and IP address 10.101.0.25 as the source:
configure snmp add trapreceiver 10.101.0.105 community blue from 10.101.0.25
The following command adds port 9990 at the IP address 10.203.0.22 as a trap receiver with the
community string public, and the receiver should be sent standard traps for the trap groups for Extreme
Networks:
configure snmp add trapreceiver ipaddress 10.203.0.22 port 9990 community public mode
standard trap-group extreme-traps
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add support for SNMP Version 2 and the trap
groups.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the value of the default SNMP read or read/write community string.
Syntax Description
Default
The default read-only community string is public. The default read/write community string is private.
Usage Guidelines
This command has been superseded by the configure snmp add community command and can be
used only to modify the first read-only or read-write community string which, are normally the default
public and private community strings.
The community strings allow a simple method of authentication between the switch and the remote
network manager. There are two types of community strings on the switch. Read community strings
provide read-only access to the switch. The default read-only community string is public. Read-write
community strings provide read and write access to the switch. The default read/write community
string is private.
It is recommended that you change the values of the default read/write and read-only community
strings. You use the configure snmp community command to change the value of the default
community strings. An SNMP community string can contain up to 32 characters.
The encrypted option is intended for use by the switch when generating an ASCII configuration file
(using the upload configuration command), or parsing a switch-generated configuration (using the
download configuration command). Do not select the encrypted option in the CLI.
A total of sixteen community strings can be configured on the switch. You can add additional
community strings (in addition to the default community stings) using the configure snmp add
community command.
Example
The following command sets the read/write community string to extreme:
configure snmp community readwrite extreme
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add support for encryption.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes an SNMP read or read/write community string.
Syntax Description
Default
The default read-only community string is public. The default read/write community string is private.
Usage Guidelines
The community strings allow a simple method of authentication between the switch and the remote
network manager. There are two types of community strings on the switch. Read community strings
provide read-only access to the switch. The default read-only community string is public. read/write
community strings provide read and write access to the switch. The default read/write community
string is private. Sixteen read-only and sixteen read-write community strings can be configured on the
switch, including the defaults. The community string for all authorized trap receivers must be
configured on the switch for the trap receiver to receive switch-generated traps. SNMP community
strings can contain up to 32 characters.
It is recommended that you change the defaults of the read/write and read-only community strings.
Use the configure snmp add community command to configure an authorized SNMP management
station.
The encrypted option should only be used by the switch to generate an ASCII configuration (using the
upload configuration command), and parsing a switch-generated configuration (using the download
configuration command). Do not select the encrypted option in the CLI.
Example
The following command deletes a read/write community string named extreme:
configure snmp delete community readwrite extreme
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a specified trap receiver or all authorized trap receivers.
Syntax Description
Default
The default port number is 162.
Usage Guidelines
Use this command to delete a trap receiver of the specified IP address, or all authorized trap receivers.
This command deletes only the first SNMPv1/v2c trap receiver whose IP address and port number
match the specified value.
If a trap receiver has been added multiple times with different community strings, the community
option specifies that only the trap receiver entry with the specified community string should be
removed.
Example
The following command deletes the trap receiver 10.101.0.100 from the trap receiver list:
configure snmp delete trapreceiver 10.101.0.100
The following command deletes entries in the trap receiver list for 10.101.0.100, port 9990:
configure snmp delete trapreceiver 10.101.0.100 port 9990
Any entries for this IP address with a different community string will not be affected.
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the name of the system contact.
Syntax Description
Default
N/A.
Usage Guidelines
The system contact is a text field that enables you to enter the name of the person(s) responsible for
managing the switch. A maximum of 255 characters is allowed.
To view the name of the system contact listed on the switch, use the show switch command. The show
switch command displays switch statistics including the name of the system contact.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
configure snmp syscontact <alphanumeric string> command, use the unconfigure management
command.
Example
The following command defines FredJ as the system contact:
configure snmp syscontact fredj
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the location of the switch.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to indicate the location of the switch. A maximum of 255 characters is allowed.
To view the location of the switch on the switch, use the show switch command. The show switch
command displays switch statistics including the location of the switch.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
configure snmp syslocation <alphanumeric string> command, use the unconfigure
management command.
Example
The following command configures a switch location name on the system:
configure snmp syslocation englab
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the name of the switch.
Syntax Description
Default
The default sysname is the model name of the device (for example, Summit1).
Usage Guidelines
You can use this command to change the name of the switch. A maximum of 32 characters is allowed.
The sysname appears in the switch prompt.
To view the name of the system listed on the switch, use the show switch command. The show switch
command displays switch statistics including the name of the system.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
configure snmp sysname <alphanumeric string> command, use the unconfigure management
command.
Example
The following command names the switch:
configure snmp sysname engineeringlab
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Create (and modify) a group and its access rights.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
group name Specifies the group name to add or modify.
sec-model Specifies the security model to use.
snmpv1 Specifies the SNMPv1 security model.
snmpv2 Specifies the SNMPv2c security model.
usm Specifies the SNMPv3 User-based Security Model (USM).
sec-level Specifies the security level for the group.
noauth Specifies no authentication (and implies no privacy) for the security level.
authnopriv Specifies authentication and no privacy for the security level.
authpriv Specifies authentication and privacy for the security level.
read-view Specifies the read view name.
write-view Specifies the write view name.
notify-view Specifies the notify view name.
volatile Specifies volatile storage.
Default
The default values are:
• sec-model—USM
• sec-level—noauth
• read view name—defaultUserView
• write view name— “”
• notify view name—defaultUserView
• non-volatile storage
Usage Guidelines
Use this command to configure access rights for a group. All access groups are created with a unique
default context, “”, as that is the only supported context.
There are a number of default (permanent) groups already defined. These groups are: admin, initial,
initialmd5, initialsha, initialmd5Priv, initialshaPriv, v1v2c_ro, v1v2c_rw.
• The default groups defined (permanent) are v1v2c_ro for security names snmpv1 and snmpv2c,
v1v2c_rw for security names snmpv1 and snmpv2c, admin for security name admin, and initial for
security names initial, initialmd5, initialsha, initialmd5Priv and initialshaPriv.
• The default access defined (permanent) are admin, initial, v1v2c_ro, v1v2c_rw, and v1v2cNotifyGroup.
Example
In the following command, access for the group defaultROGroup is created with all the default values:
security model usm, security level noauth, read view defaultUserView, no write view, notify view
defaultUserView, and storage nonvolatile.
configure snmpv3 add access defaultROGroup
In the following command, access for the group defaultROGroup is created with the values: security
model USM, security level authnopriv, read view defaultAdminView, write view defaultAdminView, notify
view defaultAdminView, and storage nonvolatile.
configure snmpv3 add access defaultROGroup sec-model usm sec-level authnopriv
read-view defaultAdminView write-view defaultAdminView notify-view defaultAdminView
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add an SNMPv3 community entry.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
community index Specifies the row index in the snmpCommunityTable
community name Specifies the community name.
user name Specifies the USM user name.
transport tag Specifies the tag used to locate transport endpoints in SnmpTargetAddrTable.
When this community entry is used to authenticate v1/v2c messages, this tag
is used to verify the authenticity of the remote entity.
volatile Specifies volatile storage.
Default
N/A.
Usage Guidelines
Use this command to create or modify an SMMPv3 community in the community MIB.
Example
Use the following command to create an entry with the community index comm_index, community
name comm_public, and user (security) name v1v2c_user:
Use the following command to create an entry with the community index (hex) of 4:E, community name
(hex) of EA:12:CD:CF:AB:11:3C, user (security) name v1v2c_user, using transport tag 34872 and volatile
storage:
configure snmpv3 add community hex 4:E name hex EA:12:CD:CF:AB:11:3C user v1v2c_user
tag 34872 volatile
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add a filter to a filter profile.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
profile name Specifies the filter profile that the current filter is added to.
object identifier Specifies a MIB subtree.
subtree mask Specifies a hex octet string used to mask the subtree. For example, f7a
indicates 1.1.1.1.0.1.1.1.1.0.1.0.
included Specifies that the MIB subtree defined by <object identifier>/<mask> is to be
included.
excluded Specifies that the MIB subtree defined by <object identifier>/<mask> is to be
excluded.
volatile Specifies volatile storage.
Default
The default mask value is an empty string (all 1s). The other default value is non-volatile.
Usage Guidelines
Use this command to create a filter entry in the snmpNotifyFilterTable. Each filter includes or excludes a
portion of the MIB. Multiple filter entries comprise a filter profile that can eventually be associated with
a target address. Other commands are used to associate a filter profile with a parameter name, and the
parameter name with a target address.
This command can be used multiple times to configure the exact filter profile desired.
Example
Use the following command to add a filter to the filter profile prof1 that includes the MIB subtree
1.3.6.1.4.1/f0:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Associate a filter profile with a parameter name.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
profile name Specifies the filter profile name.
param name Specifies a parameter name to associate with the filter profile.
volatile Specifies volatile storage.
Default
The default storage type is non-volatile.
Usage Guidelines
Use this command to add an entry to the snmpNotifyFilterProfileTable. This table associates a filter
profile with a parameter name. The parameter name is associated with target addresses, and the filter
profile is associated with a series of filters, so, in effect, you are associating a series of filters with a
target address.
Example
Use the following command to associate the filter profile prof1 with the parameter name P1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add a user name (security name) to a group.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
group name Specifies the group name to add or modify.
user name Specifies the user name to add or modify.
sec-model Specifies the security model to use.
snmpv1 Specifies the SNMPv1 security model.
snmpv2 Specifies the SNMPv2c security model.
usm Specifies the SNMPv3 User-based Security Model (USM).
volatile Specifies volatile storage.
Default
The default values are:
• sec-model—USM
• non-volatile storage
Usage Guidelines
Use this command to associate a user name with a group.
As per the SNMPv3 RFC, a security name is model independent while a username is model dependent.
For simplicity, both are assumed to be same here. User names and security names are handled the same.
In other words, if a user is created with the user name username, the security name value is the same,
username.
Every group is uniquely identified by a security name and security model. So the same security name
can be associated to a group name but with different security models.
Example
Use the following command to associate the user userV1 to the group defaultRoGroup with SNMPv1
security:
configure snmpv3 add group defaultRoGroup user userV1 sec-model snmpv1
Use the following command to associate the user userv3 with security model USM and storage type
volatile to the access group defaultRoGroup:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add (and modify) a MIB view.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
view name Specifies the MIB view name to add or modify.
subtree Specifies a MIB subtree.
mask Specifies a hex octet string used to mask the subtree. For example, f7a
indicates 1.1.1.1.0.1.1.1.1.0.1.0.
included Specifies that the MIB subtree defined by <subtree>/<mask> is to be included.
excluded Specifies that the MIB subtree defined by <subtree>/<mask> is to be
excluded.
volatile Specifies volatile storage.
Default
The default mask value is an empty string (all 1s). The other default values are included and
non-volatile.
Usage Guidelines
Use this command to create a MIB view into a subtree of the MIB. If the view already exists, this
command modifies the view to additionally include or exclude the specified subtree.
In addition to the created MIB views, there are three default views. They are of storage type permanent
and cannot be deleted, but they can be modified. The default views are: defaultUserView,
defaultAdminView, and defaultNotifyView.
Example
Use the following command to create the MIB view allMIB with the subtree 1.3 included as non-volatile:
Use the following command to create the view extremeMib with the subtree 1.3.6.1.4.1.1916 included as
non-volatile:
Use the following command to create a view vrrpTrapNewMaster which excludes VRRP notification.1
and the entry is volatile.
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add an entry to the snmpNotifyTable.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
notify name Specifies the notify name to add.
tag Specifies a string identifier for the notifications to be sent to the target.
volatile Specifies volatile storage.
Default
The default storage type is non-volatile.
Usage Guidelines
Use this command to add an entry to the snmpNotifyTable. When a notification is to be sent, this table
is examined. For the target addresses that have been associated with the tags present in the table,
notifications will be sent, based on the filters also associated with the target addresses.
Example
Use the following command to send notification to addresses associated with the tag type1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add and configure an SNMPv3 target address and associate filtering, security, and notifications with
that address.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
addr name Specifies a string identifier for the target address.
param name Specifies the parameter name associated with the target.
ip address Specifies an SNMPv3 target IP address.
target-addr mask Specifies a hex octet string used to mask the target address. For example, f7a
indicates 1.1.1.1.0.1.1.1.1.0.1.0.
port Specifies a UDP port. Default is 162.
source ip address Specifies the IP address of a VLAN to be used as the source address for the
trap
tag Specifies a string identifier for the notifications to be sent to the target.
volatile Specifies volatile storage.
Default
The default values are:
• transport-port—port 162
• tag-list—the single tag defaultNotify, a pre-defined value in the snmpNotifyTable
• non-volatile storage
Usage Guidelines
Use this command to create an entry in the SNMPv3 snmpTargetAddressTable. The param parameter
associates the target address with an entry in the snmpTargetParamsTable, which specifies security and
storage parameters for messages to the target address, and an entry in the snmpNotifyFilterProfileTable,
which specifies filters to use for notifications to the target address.
Example
The following command specifies a target address of 10.203.0.22, port 9990, with the name A1, and
associates it with the security parameters and filter profile P1, and the notification tags type1 and type2:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add and configure SNMPv3 target parameters.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
param name Specifies the parameter name associated with the target.
user name Specifies a user.
mp-model Specifies a message processing model; choose from SNMPv1, SNMPv2, or
SNMPv3.
sec-model Specifies the security model to use.
snmpv1 Specifies the SNMPv1 security model.
snmpv2 Specifies the SNMPv2c security model.
usm Specifies the SNMPv3 User-based Security Model (USM).
sec-level Specifies the security level for the group.
noauth Specifies no authentication (and implies no privacy) for the security level.
authnopriv Specifies authentication and no privacy for the security level.
authpriv Specifies authentication and privacy for the security level.
volatile Specifies volatile storage.
Default
The default values are:
• sec-level—noauth
• non-volatile storage
Usage Guidelines
Use this command to create an entry in the SNMPv3 snmpTargetParamsTable. This table specifies the
message processing model, security level, security model, and the storage parameters for messages to
any target addresses associated with a particular parameter name.
To associate a target address with a parameter name, see the command “configure snmpv3 add
target-addr” on page 107.
Example
The following command specifies a target parameters entry named P1, a user name of guest, message
processing and security model of SNMPv2c, and a security level of no authentication:
configure snmpv3 add target-params P1 user guest mp-model snmpv2c sec-model snmpv2c
sec-level noauth
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Add (and modify) an SNMPv3 user.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
user name Specifies the user name to add or modify.
MD5 Specifies MD5 authentication.
SHA Specifies SHA authentication.
authentication Specifies the authentication password or hex string to use for generating the
authentication key for this user.
privacy Specifies the privacy password or hex string to use for generating the privacy
key for this user.
volatile Specifies volatile storage.
Default
The default values are:
• authentication—no authentication
• privacy—no privacy
• non-volatile storage
Usage Guidelines
Use this command to create or modify an SNMPv3 user configuration.
If hex is specified, supply a 16 octet hex string for MD5, or a 20 octet hex string for SHA.
You must specify authentication if you want to specify privacy. There is no support for privacy without
authentication.
The default user names are: admin, initial, initialmd5, initialsha, initialmd5Priv, initialshaPriv. The initial
password for admin is password. For the other default users, the initial password is the user name.
Example
Use the following command to configure the user guest on the local SNMP Engine with security level
noauth (no authentication and no privacy):
Use the following command to configure the user authMD5 to use MD5 authentication with the password
palertyu:·
Use the following command to configure the user authSHApriv to use SHA authentication with the hex
key shown below, the privacy password palertyu, and volatile storage:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Create a new user by cloning from an existing SNMPv3 user.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
user name Specifies the user name to add or to clone from.
Default
N/A.
Usage Guidelines
Use this command to create a new user by cloning an existing one. Once you have successfully cloned
the new user, you can modify its parameters using the following command:
configure snmpv3 add user {hex <hex value>} <user name> {authentication [md5 |
sha] [hex <hex octet> | <password>]} {privacy [hex <hex octet> | <password>]}
{volatile}
Users cloned from the default users will have the storage type of non-volatile. The default names are:
admin, initial, initialmd5, initialsha, initialmd5Priv, initialshaPriv.
Example
Use the following command to create a user cloneMD5 with same properties as the default user
initalmd5. All authorization and privacy keys will initially be the same as with the default user
initialmd5.
configure snmpv3 add user cloneMD5 clone-from initialmd5
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete access rights for a group.
Syntax Description
Default
The default values are:
• sec-model—USM
• sec-level—noauth
Usage Guidelines
Use this command to remove access rights for a group. Use the all-non-defaults keyword to delete
all the security groups, except for the default groups. The default groups are: admin, initial, v1v2c_ro,
v1v2c_rw.
Deleting an access will not implicitly remove the related group to user association from the
VACMSecurityToGroupTable. To remove the association, use the following command:
configure snmpv3 delete group {{hex} <group name>} user [all-non-defaults | {{hex}
<user name> sec-model {sec-model [snmpv1|snmpv2c|usm]}}]
Example
The following command deletes all entries with the group name userGroup:
The following command deletes the group userGroup with the security model snmpv1 and security level
of authentication and no privacy (authnopriv):
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete an SNMPv3 community entry.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
community index Specifies the row index in the snmpCommunityTable
community name Specifies the community name.
user name Specifies the USM user name.
all-non-defaults Specifies that all non-default community entries are to be removed.
Default
N/A.
Usage Guidelines
Use this command to delete an SMMPv3 community in the community MIB. The default entries are
public and private.
Example
Use the following command to delete an entry with the community index comm_index:
Use the following command to create an entry with the community name (hex) of
EA:12:CD:CF:AB:11:3C:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete a filter from a filter profile.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to delete a filter entry from the snmpNotifyFilterTable. Specify all to remove all
entries. Specify a profile name to delete all entries for that profile name. Specify a profile name and a
subtree to delete just those entries for that filter profile and subtree.
Example
Use the following command to delete the filters from the filter profile prof1 that reference the MIB
subtree 1.3.6.1.4.1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Remove the association of a filter profile with a parameter name.
Syntax Description
Default
The default storage type is non-volatile.
Usage Guidelines
Use this command to delete entries from the snmpNotifyFilterProfileTable. This table associates a filter
profile with a parameter name. Specify all to remove all entries. Specify a profile name to delete all
entries for that profile name. Specify a profile name and a parameter name to delete just those entries
for that filter profile and parameter name.
Example
Use the following command to delete the filter profile prof1 with the parameter name P1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete a user name (security name) from a group.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
group name Specifies the group name to add or modify.
all-non-defaults Specifies that all non-default (non-permanent) users are to be deleted from the
group.
user name Specifies the user name to add or modify.
sec-model Specifies the security model to use.
snmpv1 Specifies the SNMPv1 security model.
snmpv2 Specifies the SNMPv2c security model.
usm Specifies the SNMPv3 User-based Security Model (USM).
Default
The default values are:
• sec-model—USM
Usage Guidelines
Use this command to remove the associate of a user name with a group.
As per the SNMPv3 RFC, a security name is model independent while a username is model dependent.
For simplicity, both are assumed to be same here. User names and security names are handled the same.
In other words, if a user is created with the user name username, the security name value is the same,
username.
Every group is uniquely identified by a security name and security model. So the same security name
can be associated to a group name but with different security models.
The default users are: admin, initial, initialmd5, initialsha, initialmd5Priv, initialshaPriv.
Example
Use the following command to delete the user guest from the group UserGroup for the security model
snmpv2c:
configure snmpv3 delete group UserGroup user guest sec-model snmpv2c
Use the following command to delete the user guest from the group userGroup with the security model
USM:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete a MIB view.
Syntax Description
all-non-defaults Specifies that all non-default (non-permanent) MIB views are to be deleted.
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
view name Specifies the MIB view name to add or modify.
subtree Specifies a MIB subtree.
Default
N/A.
Usage Guidelines
Use this command to delete a MIB view. Views which are being used by security groups cannot be
deleted. Use the all-non-defaults keyword to delete all the MIB views (not being used by security
groups) except for the default views. The default views are: defaultUserView, defaultAdminView, and
defaultNotifyView.
Use the configure snmpv3 add mib-view command to remove a MIB view from its security group,
by specifying a different view.
Example
The following command deletes all views (only the permanent views will not be deleted):
configure snmpv3 delete mib-view all-non-defaults
The following command deletes all subtrees with the view name AdminView:
configure snmpv3 delete mib-view AdminView
The following command deletes the view AdminView with subtree 1.3.6.1.2.1.2
configure snmpv3 delete mib-view AdminView subtree 1.3.6.1.2.1.2
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete an entry from the snmpNotifyTable.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
notify name Specifies the notify name to add.
all-non-defaults Specifies that all non-default (non-permanent) notifications are to be deleted.
Default
N/A.
Usage Guidelines
Use this command to delete an entry from the snmpNotifyTable. When a notification is to be sent, this
table is examined. For the target addresses that have been associated with the tags present in the table,
notifications will be sent, based on the filters also associated with the target addresses.
Example
Use the following command to remove the N1 entry from the table:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete SNMPv3 target addresses.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
addr name Specifies a string identifier for the target address.
all Specifies all target addresses.
Default
N/A.
Usage Guidelines
Use this command to delete an entry in the SNMPv3 snmpTargetAddressTable.
Example
The following command deletes target address named A1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete SNMPv3 target parameters.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
param name Specifies the parameter name associated with the target.
Default
N/A.
Usage Guidelines
Use this command to delete an entry in the SNMPv3 snmpTargetParamsTable. This table specifies the
message processing model, security level, security model, and the storage parameters for messages to
any target addresses associated with a particular parameter name.
Example
The following command deletes a target parameters entry named P1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete an existing SNMPv3 user.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to delete an existing user.
Use the all-non-defaults keyword to delete all users, except for the default (permanent) users. The
default user names are: admin, initial, initialmd5, initialsha, initialmd5Priv, initialshaPriv.
Deleting a user will not implicitly remove the related group to user association from the
VACMSecurityToGroupTable. To remove the association, use the following command:
configure snmpv3 delete group {{hex} <group name>} user [all-non-defaults | {{hex}
<user name> {sec-model [snmpv1|snmpv2c|usm]}}]
Example
The following command deletes all non-default users:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the SNMPv3 Engine Boots value.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command if the Engine Boots value needs to be explicitly configured. Engine Boots and Engine
Time will be reset to zero if the Engine ID is changed. Engine Boots can be set to any desired value but
will latch on its maximum, 2147483647.
Example
The following command configures Engine Boots to 4096:
configure snmpv3 engine-boots 4096
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the SNMPv3 snmpEngineID.
Syntax Description
hex octet Specifies the colon delimited hex octet that serves as part of the
snmpEngineID (5-32 octets).
Default
The default snmpEngineID is the device MAC address.
Usage Guidelines
Use this command if the snmpEngineID needs to be explicitly configured. The first four octets of the ID
are fixed to 80:00:07:7C,which represents Extreme Networks Vendor ID. Once the snmpEngineID is
changed, default users will be reverted back to their original passwords/keys, while non-default users
will be reset to the security level of no authorization, no privacy.
Example
The following command configures the snmpEngineID to be 80:00:07:7C:00:0a:1c:3e:11:
configure snmpv3 engine-id 00:0a:1c:3e:11
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configure an entry in the extremeTargetAddrExtTable.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
addr name Specifies a string identifier for the target address.
enhanced Specifies enhanced traps, which contain extra varbinds at the end.
standard Specifies standard traps, which do not contrain the extra varbinds.
ignore-mp-model Sets the ignore message passing model flag
ignore-event-community Sets the use Event Community flag to false.
Default
The default values are:
• mode—enhanced
• ignore-mp-model—False, the mp-model is not ignored.
• ignore-event-community—False, the EventCommunity is not ignored.
Usage Guidelines
The command snmp add trapreceiver was retained when SNMPv3 support was added to
ExtremeWare. This command allows you to set trap receivers without using the details of SNMPv3.
However, when the command is executed, it internally sets a per-trap-receiver flag called
ignore-mp-model, and ignore-event-community. This command is never uploaded to the switch, but its
equivalent SNMPv3 command, configure snmpv3 add target-addr, is uploaded instead. The latter
has no tokens for ignore-mp-model or ignore-event-come. Therefore, upon downloading the configuration,
the setting for these objects is lost.
This separate command corresponds to a private SNMP table that was subsequently added. The table
contains three objects, ignoreMPModel, useEventCommunity, and Mode. This private table, the
extremeTargetAddrExtTable, is an extension to the standard snmpv3TargetAddrTable
Example
The following command that standard traps will be used:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an NTP server for the switch to obtain time information.
Syntax Description
Default
N/A.
Usage Guidelines
Queries are first sent to the primary server. If the primary server does not respond within 1 second, or if
it is not synchronized, the switch queries the second server. If the switch cannot obtain the time, it
restarts the query process. Otherwise, the switch waits for the sntp-client update interval before
querying again.
Example
The following command configures a primary NTP server:
configure sntp-client primary server 10.1.2.2
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the interval between polls for time information from SNTP servers.
Syntax Description
Default
64 seconds.
Usage Guidelines
None.
Example
The following command configures the interval timer:
configure sntp-client update-interval 30
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for user to enter username/password in the pop-up window.
Syntax Description
Default
30 seconds.
Usage Guidelines
The Show for this parameter is displayed by using the following command:
show management
Example
The following command configures the interval timer:
configure sntp-client update-interval 30
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
disable eapol-flooding
disable eapol-flooding
Description
Disables EAPOL flooding on the switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Per IEEE 802.1D, Summit “e’ series switches do not forward EAPOL frames. Also, if network login is
enabled, EAPOL flooding cannot be enabled.
Example
The following example disables EAPOL frame flooding on a Summit “e” series switch:
disable eapol-flooding
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables DHCP on a specified port in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
The DHCP server should be used with Network Login and not as a stand-alone DHCP server.
Example
The following command disables DHCP for port 9 in VLAN corp:
disable dhcp ports 9 vlan corp
History
This command was first available in ExtremeWare 7.1e.
Description
Selectively disables SNMP on the switch.
Syntax Description
snmp-v1v2c Disables SNMPv1/v2c access only; does not affect SNMPv3 access.
Default
Enabled.
Usage Guidelines
Disabling SNMP access does not affect the SNMP configuration (for example, community strings).
However, if you disable SNMP access, you will be unable to access the switch using SNMP.
By using the enable and disable commands you can enable all SNMP access, no SNMP access, or only
SNMPv3 access. You cannot enable only SNMPv1/v2c access. To enable SNMPv3 only access on the
switch, use the following commands:
Example
The following command disables all SNMP access on the switch:
disable snmp access
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add the snmp-v1v2c keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables SNMP GetNext responses for the dot1dTpFdbTable in the BRIDGE-MIB.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
SNMP Get responses are not affected by this command.
To view the configuration of the dot1dTpFdb table on the switch, use the show management command.
The show management command displays information about the switch including the enable/disable
state the dot1dTpFdb table.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
disable snmp dot1dTpFdbTable command, use the unconfigure management command.
Example
The following command disables the dot1dTPFdb table:
disable snmp dot1dTpFdbTable
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Prevents SNMP traps from being sent from the switch.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
This command does not clear the SNMP trap receivers that have been configured. The command
prevents SNMP traps from being sent from the switch even if trap receivers are configured.
Example
The following command prevents SNMP traps from being sent from the switch to the trap receivers:
disable snmp traps
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Prevents SNMP port up/down traps (also known as link up and link down traps) from being sent from
the switch for the indicated ports.
Syntax Description
all Specifies that no link up/down traps should be sent for all ports. This does not
include the management port which must be explicitly specified.
mgmt Specifies that no link up/down traps should be sent for the management port.
This option will only appear on platforms that have a management port, such
as the Summit 400.
<portlist> Specifies the list of ports.
Default
Enabled.
Usage Guidelines
This command is used to disable the sending of link up and link down traps for the specified ports. To
see which ports do not have such traps disabled, use the show management command.
Example
The following command will prevent link up or link down traps from being sent for any port on the
switch (except the management port if it has one).
disable snmp traps port-up-down all
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Prevents SNMP mac-security traps from being sent from the switch for all ports.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command should be used in conjunction with the configure ports <portlist> limit-learning command.
That command configures a limit on the number of MAC addresses that can be learned on a port(s).
After that limit has been reached on a particular port, a trap will be sent by the switch, if a new MAC
address appears on that port. In addition, a message will be generated in the syslog and the port will be
blackholed.
Example
The following command prevents SNMP mac-security traps from being sent from the switch.
disable snmp traps mac-security
History
This command was first available in ExtremeWare 7.0.0.
Platform Availability
This command is available on the “e” series platforms.
disable sntp-client
disable sntp-client
Description
Disables the SNTP client.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
SNTP can be used by the switch to update and synchronize its internal clock from a Network Time
Protocol (NTP) server. After the SNTP client has been enabled, the switch sends out a periodic query to
the indicated NTP server, or the switch listens to broadcast NTP updates. In addition, the switch
supports the configured setting for Greenwich Mean Time (GMT) offset and the use of Daylight Savings
Time (DST).
Example
The following command disables the SNTP client:
disable sntp-client
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable system-watchdog
disable system-watchdog
Description
Disables the system watchdog timer.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
The watchdog timer reboots the switch if the CPU becomes trapped in a processing loop. If the
watchdog timer is executed, the switch captures information on the cause of the reboot and posts it to
the system log.
Example
The following command disables the watchdog timer:
disable system-watchdog
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
disable telnet
disable telnet
Description
Disables Telnet services on the system.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
You must be logged in as an administrator to enable or disable Telnet.
Example
With administrator privilege, the following command disables Telnet services on the switch:
disable telnet
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable web
disable web
Description
Disables web access to the switch.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
You can use this command to disable web access to the switch. If you are using ExtremeWare Vista for
web access, you must create and configure an access profile before you can use this option. You create
an access profile using the create access-profile command. You configure an access profile using
one of the configure access-profile commands.
Example
The following command disables web access to the switch:
disable web
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable eapol-flooding
enable eapol-flooding
Description
Enables EAPOL flooding on the switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Per IEEE 802.1D, Summit “e’ series switches do not forward EAPOL frames. Also, if network login is
enabled, EAPOL flooding cannot be enabled. Also, if network login is enabled, EAPOL flooding cannot
be enabled. However, under certain conditions, you might opt to change this behavior to support an
upstream central authenticator by enabling the switch to flood the EAPOL frame on the VLAN
associated with the ingress port.
Example
The following example enables EAPOL frame flooding on a Summit “e” series switch:
enable eapol-flooding
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables DHCP on a specified port in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command enables DHCP for port 9 in VLAN corp:
enable dhcp ports 9 vlan corp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Turns on SNMP support for SNMPv3 and v1/v2c on the switch.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
To have access to the SNMP agent residing in the switch, at least one VLAN must have an IP address
assigned to it.
Any network manager running SNMP can manage the switch (for v1/v2c), provided the MIB is
installed correctly on the management station. Each network manager provides its own user interface to
the management facilities.
For SNMPv3, additional security keys are used to control access, so an SNMPv3 manager is required for
this type of access.
This command enables both v1/v2c and v3 access, so the switch can be accessed with either method.
Use the following commands to allow only v3 access:
Example
The following command enables all SNMP access for the switch:
enable snmp access
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables SNMP GetNext responses for the dot1dTpFdbTable in the BRIDGE-MIB.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
SNMP Get responses are not affected by this command.
To view the configuration of the dot1dTpFdb table on the switch, use the show management command.
The show management command displays information about the switch including the enable/disable
state the dot1dTpFdb table.
To restore defaults to all SNMP-related entries, including the SNMP parameters modified using the
enable snmp dot1dTpFdbTable command, use the unconfigure management command.
Example
The following command enables the dot1dTPFdb table:
enable snmp dot1dTpFdbTable
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Turns on SNMP trap support.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
An authorized trap receiver can be one or more network management stations on your network. The
switch sends SNMP traps to all trap receivers.
Example
The following command enables SNMP trap support on the switch:
enable snmp trap
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables SNMP port up/down traps (also known as link up and link down traps) for the indicated
ports.
Syntax Description
all Specifies that link up/down traps should be sent for all ports. This does not
include the management port which must be explicitly specified.
mgmt Specifies that link up/down traps should be sent for the management port.
This option only appears on platforms that have a management port, such as
the Summit 400.
<portlist> Specifies a list of ports.
Default
Enabled.
Usage Guidelines
This command is used to enable the sending of link up and link down traps for the specified ports. To
see which ports have such traps enabled, use the show management command.
Example
The following command will enable link up or link down traps on all ports of the switch (except the
management port if it has one).
enable snmp traps port-up-down all
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables SNMP mac-security traps for all ports to be sent by the switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command should be used in conjunction with the configure ports <portlist> limit-learning command.
That command configures a limit on the number of MAC addresses that can be learned on a port(s).
After that limit has been reached on a particular port, a trap will be sent by the switch, if a new MAC
address appears on that port. In addition, a message will be generated in the syslog and the port will be
blackholed.
Example
The following command allows SNMP mac-security traps to be sent from the switch.
enable snmp traps mac-security
History
This command was first available in ExtremeWare 7.0.0.
Platform Availability
This command is available on the “e” series platforms.
enable sntp-client
enable sntp-client
Description
Enables the SNTP client.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
SNTP can be used by the switch to update and synchronize its internal clock from a Network Time
Protocol (NTP) server. After the SNTP client has been enabled, the switch sends out a periodic query to
the indicated NTP server, or the switch listens to broadcast NTP updates. In addition, the switch
supports the configured setting for Greenwich Mean Time (GMT) offset and the use of Daylight Savings
Time (DST).
Example
The following command enables the SNTP client:
enable sntp-client
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable system-watchdog
enable system-watchdog
Description
Enables the system watchdog timer.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
The watchdog timer reboots the switch if the CPU becomes trapped in a processing loop. If the
watchdog timer is executed, the switch captures information on the cause of the reboot and posts it to
the system log.
Example
The following command enables the watchdog timer:
enable system-watchdog
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
enable telnet
enable telnet {access-profile [<access_profile> | none]} {port
<tcp_port_number>}
Description
Enables Telnet access to the switch.
Syntax Description
Default
Telnet is enabled with no access profile and uses TCP port number 23.
Usage Guidelines
You must be logged in as an administrator to enable Telnet.
If you are using IP without a BOOTP server, you must enter IP parameters for the switch for the Telnet
software to communicate with the device. To assign IP parameters to the switch, you must:
• Log in to the switch with administrator privileges.
• Assign an IP address and subnet mask to a VLAN.
The switch comes configured with a default VLAN named default. To use Telnet or an SNMP
network manager, you must have at least one VLAN on the switch, and it must be assigned an IP
address and subnet mask. IP addresses are always assigned to a VLAN. The switch can be assigned
multiple IP addresses.
• Use an access profile to restrict Telnet access. An access profile permits or denies a named list of IP
addresses and subnet masks. You must create and configure an access profile before you can use this
option. You create an access profile using the create access-profile command. You configure an
access profile using one of the configure access-profile commands.
• Use the none option to cancel a previously configured access-profile.
• Use the port option to specify a TCP port number.
Example
The following command applies the access profile managers to Telnet:
enable telnet access-profile managers
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable web
enable web {access-profile [<access_profile> | none]} {port
<tcp_port_number>}
Description
Enables ExtremeWare Vista web access to the switch.
Syntax Description
Default
Enabled, using TCP port 80.
Usage Guidelines
By default, web access is enabled on the switch.
• By default, web access has no access profile and uses TCP port number 80.
• Use an access profile to restrict ExtremeWare Vista web access. An access profile permits or denies a
named list of IP addresses and subnet masks. You must create and configure an access profile before
you can use this option. You create an access profile using the create access-profile command.
You configure an access profile using one of the configure access-profile commands. Apply an
access profile only when ExtremeWare Vista is enabled.
• Use the none option to cancel a previously configured access-profile.
• Use the port option to specify a TCP port number.
Example
The following command applies the access profile administrators to the web:
enable web access-profile administrators
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
exit
exit
Description
Logs out the session of a current user for CLI or Telnet.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to log out of a CLI or Telnet session.
Example
The following command logs out the session of a current user for CLI or Telnet:
exit
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
logout
logout
Description
Logs out the session of a current user for CLI or Telnet.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to log out of a CLI or Telnet session.
Example
The following command logs out the session of a current user for CLI or Telnet:
logout
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
quit
quit
Description
Logs out the session of a current user for CLI or Telnet.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to log out of a CLI or Telnet session.
Example
The following command logs out the session of a current user for CLI or Telnet:
quit
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show eapol-flooding
show eapol-flooding
Description
Displays the current EAPOL flooding state.
Syntax Description
This command has no arguments or variables.
Default
N/A
Usage Guidelines
Per IEEE 802.1D, Summit “e’ series switches do not forward EAPOL frames. Also, if network login is
enabled, EAPOL flooding cannot be enabled. Also, if network login is enabled, EAPOL flooding cannot
be enabled. However, under certain conditions, you might opt to change this behavior to support an
upstream central authenticator by enabling the switch to flood the EAPOL frame on the VLAN
associated with the ingress port.
Example
The following example displays EAPOL frame flooding on a Summit “e” series switch:
show eapol-flooding
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show management
show management
Description
Displays the SNMP settings configured on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines:
The following show management output is displayed:
• Enable/disable state for Telnet, SNMP, and web access
• SNMP community strings
• Authorized SNMP station list
• SNMP trap receiver list
• Login statistics
• Enable/disable state for SSH2 and access profile information
• RMON polling configuration
• The enable/disable state of the port-up-down traps
• The enable/disable state of the mac-limit traps
For ExtremeWare 7.2e and higher, the SNMP access display item will show the additional states of v1,
v2c disabled and v3 enabled. The flags field was enhanced to show the SNMP trap groups.
Example
The following command displays configured SNMP settings on the switch:
show management
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show odometer
show odometer
Description
Displays a counter for each component of a switch that shows how long it has been functioning since it
was manufactured.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
The output from this command displays how long each individual component in the whole switch has
been functioning since it is manufactured. This odometer counter will be kept in the EEPROM of each
monitored component. This means that even when the component is plugged into different chassis, the
odometer counter will be available in the new switch chassis.
Example
The following command displays how long each component of a switch has been functioning since it’s
manufacture date:
show odometer
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show session
show session
Description
Displays the currently active Telnet, console, and web sessions communicating with the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
The show session command displays the username and IP address of the incoming Telnet session,
whether a console session is currently active, and the login time.
The following table displays the show session command field definitions.
Field Definition
# Indicates session number.
Login Time Indicates login time of session.
User Indicates the user logged in for each session.
Type Indicates the type of session.
Auth Indicates how the user is logged in.
CLI Auth Indicates the type of authentication (RADIUS and TACAS) if enabled.
Location Indicates the location (IP address) from which the user logged in.
Example
The following command displays the active sessions on the switch:
show session
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays SNMPv3 access rights.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
group name Specifies the name of the group to display.
Default
N/A.
Usage Guidelines
The show snmpv3 access command displays the access rights of a group. If you do not specify a
group name, the command will display details for all the groups.
Example
The following command displays all the access details.·
The following command displays the access rights for the group group1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays information about the SNMPv3 contexts on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines:
This command displays the entries in the View-based Access Control Model (VACM) context table
(VACMContextTable).
Example
The following command displays information about the SNMPv3 contexts on the switch:
show snmpv3 context
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays SNMPv3 counters.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
The show snmpv3 counters command displays the following SNMPv3 counters:
• snmpUnknownSecurityModels
• snmpInvalidMessages
• snmpUnknownPDUHandlers
• usmStatsUnsupportedSecLevels
• usmStatsNotInTimeWindows
• usmStatsUnknownUserNames
• usmStatsUnknownEngineIDs
• usmStatsWrongDigests
• usmStatsDecryptionErrors
Issuing the command clear counters will resets all counters to zero.
Example
The following command displays all the SNMPv3 counters.·
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays information about the SNMPv3 engine on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines:
The following show engine-info output is displayed:
• EngineID—Either the ID auto generated from MAC address of switch, or the ID manually
configured.
• EngineBoots—Number of times the agent has been rebooted.
• EngineTime—Time since agent last rebooted, in centiseconds.
• Max. Message Size—Maximum SNMP Message size supported by the Engine (8192).
Example
The following command displays information about the SNMPv3 engine on the switch:
show snmpv3 engine-info
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Display the filters that belong a filter profile.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
profile name Specifies the filter profile to display.
object identifier Specifies a MIB subtree.
Default
N/A.
Usage Guidelines
Use this command to display entries from the snmpNotifyFilterTable. If you specify a profile name and
subtree, you will display only the entries with that profile name and subtree. If you specify only the
profile name, you will display all entries for that profile name. If you do not specify a profile name,
then all the entries are displayed.
Example
Use the following command to display the part of filter profile prof1 that includes the MIB subtree
1.3.6.1.4.1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Display the association between parameter names and filter profiles.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
profile name Specifies the filter profile name.
param name Specifies the parameter name.
Default
N/A.
Usage Guidelines
Use this command to display the snmpNotifyFilterProfileTable. This table associates a filter profile with
a parameter name. The parameter name is associated with target addresses, and the filter profile is
associated with a series of filters, so, in effect, you are associating a series of filters with a target address.
Example
Use the following command to display the entry with filter profile prof1 with the parameter name P1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the user name (security name) and security model association with a group name.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
group name Specifies the group name to display.
user name Specifies the user name to display.
Default
N/A.
Usage Guidelines
The show snmpv3 group command displays the details of a group with the given group name. If you
do not specify a group name, the command will display details for all the groups.
Example
The following command displays information about all groups for every security model and user name:
The following command shows information about the group testgroup and user name testuser:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays a MIB view.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
view name Specifies the name of the MIB view to display.
subtree Specifies the object identifier of the view to display.
Default
N/A.
Usage Guidelines
The show snmpv3 mib-view command displays a MIB view. If you do not specify a view name, the
command will display details for all the MIB views. If a subtree is not specified, then all subtrees
belonging to the view name will be displayed.
Example
The following command displays all the view details.·
The following command displays a view with the view name Roview and subtree 1.3.6.1.2.1.1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Display the notifications that are set. This command displays the snmpNotifyTable.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
param name Specifies the parameter name associated with the target.
Default
N/A.
Usage Guidelines
Use this command to display entries from the SNMPv3 snmpNotifyTable. This table lists the notify tags
that the agent will use to send notifications (traps).
Example
The following command displays the notify table entry for N1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Display information about SNMPv3 target addresses.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
addr name Specifies a string identifier for the target address.
Default
N/A.
Usage Guidelines
Use this command to display entries in the SNMPv3 snmpTargetAddressTable. If no target address is
specified, the entries for all the target addresses will be displayed.
Example
The following command displays the entry for the target address named A1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Display information about SNMPv3 target addresses enhanced or standard mode.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
addr name Specifies a string identifier for the target address.
Default
N/A.
Usage Guidelines
Use this command to display entries in the SNMPv3 extremeTargetAddressExtTable.
Example
The following command displays the entry for the target address named A1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Display the information about the options associated with the parameter name.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
param name Specifies the parameter name to display.
Default
N/A.
Usage Guidelines
Use this command to display entries from the SNMPv3 snmpTargetParamsTable. This table specifies the
message processing model, security level, security model, and the storage parameters for messages to
any target addresses associated with a particular parameter name.
Example
The following command displays the target parameter entry named P1:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays detailed information about the user.
Syntax Description
hex Specifies that the value to follow is to be supplied as a colon separated string
of hex octets.
user name Specifies the user name to display.
Default
N/A.
Usage Guidelines
The show snmpv3 user command displays the details of a user. If you do not specify a user name, the
command will display details for all the users. The authentication and privacy passwords and keys will
not be displayed.
The user entries in SNMPv3 are stored in the USMUserTable, so the entries are indexed by EngineID
and user name.
Example
The following command lists all user entries:
The following command lists details for the specified user, testuser:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show sntp-client
show sntp-client
Description
Displays the DNS configuration.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Displays configuration and statistics information of SNTP client.
Example
The following command displays the DNS configuration:
show sntp-client
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays DHCP address allocation information about VLANs.
Syntax Description
Default
Summary information for all VLANs on the device.
Usage Guidelines
Display the IP address, MAC address, and time assigned to each end device.
Example
The following command displays DHCP address allocation information about VLAN vlan1:
show vlan vlan1 dhcp-address-allocation
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays DHCP configuration information about VLANs.
Syntax Description
Default
Summary information for all VLANs on the device.
Usage Guidelines
Displays the DHCP configuration, including the DHCP range, DHCP lease timer, network login lease
timer, and DHCP-enabled ports.
Example
The following command displays DHCP configuration information about VLAN vlan1:
show vlan vlan1 dhcp-config
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
telnet
telnet [<ipaddress> | <hostname>] {<port_number>}
Description
Allows you to Telnet from the current command-line interface session to another host.
Syntax Description
Default
Enabled. If the TCP port number is not specified, the Telnet session defaults to port 23.
Usage Guidelines
Only VT100 emulation is supported.
Any workstation with a Telnet facility should be able to communicate with the switch over a TCP/IP
network.
Up to eight active Telnet sessions can access the switch concurrently. If idletimeouts are enabled, the
Telnet connection will time out after 20 minutes of inactivity. If a connection to a Telnet session is lost
inadvertently, the switch terminates the session within two hours.
Before you can start a Telnet session, you need to configure the switch IP parameters. To open a Telnet
connection, you must specify the host IP address or the host name of the device you wish to manage.
Check the user manual supplied with the Telnet facility if you are unsure of how to do this.
To view the status of Telnet on the switch, use the show management command. The show management
command displays information about the switch including the enable/disable state for Telnet.
Example
The following command configures Telnet communication with a host at IP address 123.45.67.8:
telnet 123.45.67.8
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure management
unconfigure management
Description
Restores default values to all SNMP-related entries.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command restores default values to all SNMP-related entries on the switch:
unconfigure management
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
By default, all ports on the switch are enabled. After you configure the ports to your specific needs, you
can select which ports are enabled or disabled.
Fast Ethernet ports can connect to either 10Base-T or 100Base-T networks. By default, the ports
autonegotiate (automatically determine) the port speed. You can also configure each port for a particular
speed (either 10 Mbps or 100 Mbps).
Gigabit Ethernet ports are statically set to 1 Gbps, and their speed cannot be modified.
The switch comes configured to use autonegotiation to determine the port speed and duplex setting for
each port. You can select to manually configure the duplex setting and the speed of 10/100/1000 Mbps
ports, and you can manually configure the duplex setting on Gigabit Ethernet ports.
All ports on the switch can be configured for half-duplex or full-duplex operation. The ports are
configured to autonegotiate the duplex setting, but you can manually configure the duplex setting for
your specific needs.
Load sharing with Extreme Network switches allows you to increase bandwidth and resilience between
switches by using a group of ports to carry traffic in parallel between switches. The sharing algorithm
allows the switch to use multiple ports as a single logical port. For example, VLANs see the
load-sharing group as a single logical port. The algorithm also guarantees packet sequencing between
clients.
If a port in a load-sharing group fails, traffic is redistributed to the remaining ports in the load-sharing
group. If the failed port becomes active again, traffic is redistributed to include that port.
Load sharing is most useful in cases where the traffic transmitted from the switch to the load-sharing
group is sourced from an equal or greater number of ports on the switch. For example, traffic
transmitted to a two-port load-sharing group should originate from a minimum of two other ports on
the same switch.
You can view port status on the switch using the show ports commands. These commands, when used
with specific keywords and parameters, allow you to view various issues such as real-time collision
statistics, link speed, and packet size.
Commands that require you to enter one or more port numbers use the parameter <portlist> in the
syntax. A <portlist> can be one or more port numbers. For a detailed explanation of port specification
“Switch Numerical Ranges” in Chapter 1.
Link Aggregation Control Protocol (LACP) is an extension to the existing sharing implementation. It
provides several features:
Description
Sets the maximum transmission unit (MTU) for the VLAN.
Syntax Description
number Specifies the IP MTU value. Range is from 1500 to 9194.
vlan name Specifies a VLAN name.
Default
The default IP MTU size is 1500.
Usage Guidelines
Use this command to enable jumbo frame support or for IP fragmentation with jumbo frames. Jumbo
frames are Ethernet frames that are larger than 1522 bytes, including 4 bytes used for CRC. Both
endstations involved in the transfer must be capable of supporting jumbo frames. The switch does not
perform IP fragmentation or participate in MTU negotiation on behalf of devices that do not support
jumbo frames.
When enabling jumbo frames and setting the MTU size for the VLAN, keep in mind that some network
interface cards (NICs) have a configured maximum MTU size that does not include the additional
4 bytes of CRC included in a jumbo frame configuration. Ensure that the NIC maximum MTU is at or
below the maximum MTU size configured on the switch. Frames that are larger than the MTU size
configured on the switch are dropped at the ingress port.
If you use IP fragmentation with jumbo frames and you want to set the MTU size greater than 1500, all
ports in the VLAN must have jumbo frames enabled.
Fragmentation is based on either the minimum value of the configured MPLS IP MTU size or the
configured IP MTU size for the egress VLAN.
Example
The following command sets the MTU size to 1500 for VLAN sales:
configure ip-mtu 1500 vlan sales
The following command increases the MTU size on the MPLS VLANs to accommodate the MPLS shim
header:
configure ip-mtu 1550 vlan vlan1
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Sets the maximum jumbo frame size for the switch chassis.
Syntax Description
number Specifies a maximum transmission unit (MTU) size for a jumbo frame.
Default
The default setting is 9216.
Usage Guidelines
Jumbo frames are used between endstations that support larger frame sizes for more efficient transfers
of bulk data. Both endstations involved in the transfer must be capable of supporting jumbo frames.
The number keyword describes the maximum jumbo frame size “on the wire,” and includes 4 bytes of
cyclic redundancy check (CRC) plus another 4 bytes if 802.1Q tagging is being used.
To enable jumbo frame support, you must configure the maximum transmission unit (MTU) size of a
jumbo frame that will be allowed by the switch.
Some network interface cards (NICs) have a configured maximum MTU size that does not include the
additional 4 bytes of CRC. Ensure that the NIC maximum MTU size is at or below the maximum MTU
size configured on the switch. Frames that are larger than the MTU size configured on the switch are
dropped at the ingress port.
You should enable jumbo frame support on the ports that are members of an MPLS VLAN. The jumbo
frame size should be set to accommodate the addition of a maximally-sized label stack. For example, a
jumbo frame size of at least 1530 bytes is needed to support a two-level label stack on a tagged Ethernet
port and a jumbo frame size of at least 1548 bytes is needed to support a TLS encapsulated MPLS
frame.
The MPLS module supports the MTU size configured using the configure jumbo-frame size
command.
Example
The following command configures the maximum MTU size of a jumbo frame size to 5500:
configure jumbo-frame size 5500
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is only available on the Summit 400-48t switch.
Description
Adds a particular mirroring filter definition on the switch.
Syntax Description
portnumber Specifies a port.
Default
N/A.
Usage Guidelines
For a detailed explanation of port specification, see “Switch Numerical Ranges” in Chapter 1.
You must enable port-mirroring using the enable mirroring command before you can configure the
mirroring filter definitions.
Up to eight mirroring definitions can be added. You can mirror traffic from a VLAN, a physical port, or
a specific VLAN/port combination.
Port-mirroring configures the switch to copy all traffic associated with one or more ports to a monitor
port on the switch. The monitor port can be connected to a network analyzer or RMON probe for
packet analysis. The switch uses a traffic filter that copies a group of traffic to the monitor port. The
traffic filter can be defined based on one of the following criteria:
• Physical port—All data that traverses the port, regardless of VLAN configuration, is copied to the
monitor port.
• VLAN—All data to and from a particular VLAN, regardless of the physical port configuration, is
copied to the monitor port.
• Virtual port—All data specific to a VLAN on a specific port is copied to the monitor port.
Up to eight mirroring filters and one monitor port can be configured on the switch. Once a port is
specified as a monitor port, it cannot be used for any other function. Frames that contain errors are not
mirrored.
In addition to the physical port, VLAN, and virtual port, the traffic filter can be defined based on the
following criteria:
• MAC source address/destination address—All data sent to or received from a particular source or
destination MAC address is copied to the monitor port.
For MAC mirroring to work correctly, the MAC address must already be present in the forwarding
database (FDB). You need to enable and configure FDB for MAC mirroring to work correctly. See “FDB
Commands” for more details.
Example
The following example sends all traffic coming into or out of a switch on port 1 and the VLAN default to
the mirror port:
configure mirroring add ports 1 vlan default
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add filtering for VLANs, MAC addresses, and
virtual ports.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a particular mirroring filter definition on the switch.
Syntax Description
portnumber Specifies a port.
Default
N/A.
Usage Guidelines
For a detailed explanation of port specification, see“Switch Numerical Ranges” in Chapter 1.
Example
The following example deletes the mirroring filter on a switch defined for port 1 on VLAN default:
configure mirroring delete ports 1 vlan default
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add support for VLANs and MAC addresses.
Platform Availability
This command is available on the “e” series platforms.
configure ports
configure ports [<portlist> vlan <vlan name> | all] [limit-learning
<number> | lock-learning | unlimited-learning | unlock-learning]
Description
Configures virtual ports for limited or locked MAC address learning.
Syntax Description
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies that all virtual ports should be configured as indicated.
vlan name Specifies the name of the VLAN.
limit-learning <number> Specifies a limit on the number of MAC addresses that can be dynamically
learned on the specified ports.
lock-learning Specifies that the current FDB entries for the specified ports should be made
permanent static, and no additional learning should be allowed.
unlimited-learning Specifies that there should not be a limit on MAC addresses that can be
learned.
unlock-learning Specifies that the port should be unlocked (allow unlimited, dynamic learning).
Default
Unlimited, unlocked learning.
Usage Guidelines
On a modular switch, <portlist> can be a list of slots and ports. On a stand-alone switch, <portlist>
can be one or more port numbers.
Limited learning. The limited learning feature allows you to limit the number of dynamically-learned
MAC addresses per VLAN. When the learned limit is reached, all new source MAC addresses are
blackholed at both the ingress and egress points. This prevent these MAC addresses from learning and
responding to Internet control message protocol (ICMP) and address resolution protocol (ARP) packets.
If the limit you configure is greater than the current number of learned entries, all the current learned
entries are purged.
Dynamically learned entries still get aged, and can be cleared. If entries are cleared or aged out after the
learning limit has been reached, new entries will then be able to be learned until the limit is reached
again.
Permanent static and permanent dynamic entries can still be added and deleted using the create
fdbentry and delete fdbentry commands. These override any dynamically learned entries.
For ports that have a learning limit in place, the following traffic will still flow to the port:
• Packets destined for permanent MACs and other non-blackholed MACs
• Broadcast traffic
• EDP traffic
Traffic from the permanent MAC and any other non-blackholed MACs will still flow from the virtual
port.
If you configure a MAC address limit on VLANS that have ESRP enabled, you should add an
additional back-to-back link (that has no MAC address limit on these ports) between the ESRP-enabled
switches. Doing so prevents ESRP PDU from being dropped due to MAC address limit settings.
Port lockdown. The port lockdown feature allows you to prevent any additional learning on the
virtual port, keeping existing learned entries intact. This is equivalent to making the
dynamically-learned entries permanent static, and setting the learning limit to zero. All new source
MAC addresses are blackholed.
Locked entries do not get aged, but can be deleted like any other permanent FDB entries. The maximum
number of permanent lockdown entries is 1024. Any FDB entries above will be flushed and blackholed
during lockdown.
For ports that have lockdown in effect, the following traffic will still flow to the port:
• Packets destined for the permanent MAC and other non-blackholed MACs
• Broadcast traffic
• EDP traffic
Traffic from the permanent MAC will still flow from the virtual port.
Once the port is locked down, all the entries become permanent and will be saved across reboot. When
you remove the lockdown using the unlock-learning option, the learning-limit is reset to unlimited, and
all associated entries in the FDB are flushed.
To verify the MAC security configuration for the specified VLAN or ports, use the following
commands:
show vlan <vlan name> security
show ports <portlist> info detail
Example
The following command limits the number of MAC addresses that can be learned on ports 1, 2, 3, and 6
in a VLAN named accounting, to 128 addresses:
configure ports 1, 2, 3, 6 vlan accounting learning-limit 128
The following command locks ports 4 and 5 of VLAN accounting, converting any FDB entries to static
entries, and prevents any additional address learning on these ports:
configure ports 4,5 vlan accounting lock-learning
The following command removes the learning limit from the specified ports:
configure ports 1, 2, vlan accounting unlimited-learning
The following command unlocks the FDB entries for the specified ports:
configure ports 4,5 vlan accounting unlock-learning
History
This command was first available in ExtremeWare 6.2 and added to the “e” series in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Manually configures port speed and duplex setting configuration on one or more ports on a switch.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5,.
all Specifies all configured ports on the switch...
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
speed [10] Specifies 10 Mbps ports.
speed [100] Specifies 100 Mbps ports.
speed [1000] Specifies 1000 Mbps ports.
duplex [half] Specifies half duplex; transmitting and receiving data one direction at a time.
duplex [full] Specifies full duplex; transmitting and receiving data at the same time.
Default
Auto on.
Usage Guidelines
On a Summit “e” series switch, <portlist> can be one or more port numbers. For a detailed
explanation of port specification, see“Switch Numerical Ranges” in Chapter 1.
You can manually configure the duplex setting and the speed of 10/100/1000 Mbps ports, and you can
manually configure the duplex setting on Gigabit Ethernet ports.
Fast Ethernet ports can connect to either 10BASE-T or 100BASE-T networks. By default, the ports
autonegotiate port speed. You can also configure each port for a particular speed (either 10 Mbps or 100
Mbps).
Gigabit Ethernet ports are statically set to 1 Gbps, and their speed cannot be modified.
All ports can be configured for half-duplex or full-duplex operation. By default, the ports autonegotiate
the duplex setting.
Example
The following example turns autonegotiation off for port 4 (a Gigabit Ethernet port):
configure ports 4 auto off duplex full
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the all and mgmt keywords.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables autonegotiation for the particular port type.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
all Specifies all configured ports on the switch. (6.1 and later) See “Usage
Guidelines” for more information.
Default
Auto on.
Usage Guidelines
On a Summit “e” series switches, <portlist> can be one or more port numbers. For a detailed
explanation of port specification, see “Switch Numerical Ranges” in Chapter 1.
The type of ports enabled for autonegotiation are 802.3u for 10/100/1000 Mbps ports or 802.3z for
Gigabit Ethernet ports.
Example
The following command configures the switch to autonegotiate for ports 4 and 6:
configure ports 4,6 auto on
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the all and mgmt keywords.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the autopolarity detection feature on the specified Ethernet ports.
Syntax Description
portlist Specifies one or more ports on the switch. May be in the form 1, 2, 3-5.
all Specifies all of the ports on the switch.
off Disables the autopolarity detection feature on the specified ports.
on Enables the autopolarity detection feature on the specified ports.
Default
The autopolarity detection feature is on.
Usage Guidelines
Use the all keyword to enable or disable the autopolarity detection feature on all of the Ethernet ports
on the Summit 200 and Summit 300 switches.
When autopolarity is disabled on one or more Ethernet ports, you can verify that status by using the
command:
show configuration
This command will list the ports for which the feature has been disabled.
To verify the current autopolarity status, use the show ports {mgmt | <portlist>| vlan <vlan
name>} info {detail} command.
Example
The following command disables the autopolarity detection feature on ports 3-5 on the Summit 200
switch:
configure ports 3-5 auto off
The following command enables the autopolarity detection feature on ports 3-5 on the Summit 200
switch:
History
This command was first available in ExtremeWare 6.2.2b108.
Platform Availability
This command is available on the Summit 200 series and Summit 300 switches only.
Description
Configures a user-defined string for a port or group of ports.
Syntax Description
portlist Specifies one or more ports numbers. May be in the form 1, 2, 3-5,.
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
alphanumeric string Specifies a user-defined display string.
Default
N/A.
Usage Guidelines
On a Summit “e” series switch, <portlist> can be one or more port numbers. For a detailed
explanation of port specification, see“Switch Numerical Ranges” in Chapter 1.
The display string can be up to 16 characters. Display strings do not need to be unique for each
port—you can assign the same string to multiple ports. For example, you could give all the ports that
connected to a particular department a common display string.
The string is displayed in certain commands such as the show ports info command.
Example
The following command configures the user-defined string corporate for port 1:
configure ports 1 display-string corporate
History
This command was first available in ExtremeWare 7.1e
This command was modified in ExtremeWare 7.2e to support the mgmt keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the Interpacket Gap for a 10 Gigabit port.
Syntax Description
byte_time Specifies the Interpacket Gap byte time.
Default
The default value of the byte time is 12.
Usage Guidelines
The standard compliant Interpacket Gap for 10 Gigabit Ethernet interfaces is 12. Some vendors'
10 Gigabit Ethernet interfaces drop packets when packets are transmitted using a value of 12. Thus, by
increasing the Interpacket Gap, packet transmission is slowed and packet loss can be minimized or
prevented. The Interpacket Gap value need not be modified when interconnecting Extreme Networks
switches over 10 Gigabit Ethernet links.
Example
The following command configures Interpacket Gap to 48:
configure port 75 interpacket-gap 48
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the Summit 400 switch.
Description
Configures the primary uplink port to use a preferred medium.
Syntax Description
nnn Specifies the port number. Valid port numbers are 1X to 4X for fiber and ports 1 to 4 for
copper.
copper Specifies that the switch should always use the 10/100/1000 connection whenever a link
is established, regardless whether a fiber link is also present.
fiber Specifies that the switch should always use the 1 Gigabit fiber connection whenever a link
is established, regardless whether a copper link is also present.
force Forces the switch to switchover to the selected media type immediately (if it has link).
This option is not available on the Summit 300-24.
Default
The default is determined at cable installation time.
Usage Guidelines
By specifying either copper or fiber, the switch starts the assignment with that medium and uses this
preferred medium the next time the switch is rebooted. However, when a failure occurs and the uplinks
are swapped, the switch continues to keep that uplink assignment until another failure occurs or until
the assignment is changed using the CLI. To require that the switch revert to the preferred-medium, use
the force option.
Examples
The following Summit 400-48t example, we establishes port 4 as the primary uplink and port 4X as the
redundant uplink port:
Port 4 becomes the primary uplink until a failure occurs on that link. At that time, port 4X becomes the
primary uplink and port 4 becomes the redundant port. This assignment stays in place until the next
failure.
In the following example, we force the switch to use the fiber port whenever it has a link:
In this example, port 3X becomes the primary uplink port until a failure occurs on the link. At that time,
port 3 becomes the primary uplink and port 3X becomes the redundant port. When port 3X
re-establishes the link, port 3X becomes the primary uplink port again.
History
This command was first available in ExtremeWare 7.2.e.
Platform Availability
This command is available on Summit 300-24 and Summit 400-48t switches only.
Description
Configures a software-controlled redundant port.
Syntax Description
portlist Specifies one or more primary ports numbers. May be in the form 1, 2, 3-5, 1:3.
portid Specifies a primary port using the display string configured for the port. If this option is
used to identify the port, the redundant port must also be specified using a port id (display
string).
Default
N/A.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
The first port list specifies the primary ports. The second port list specifies the redundant ports.
A software-controlled redundant port is configured to backup a specified primary port. The redundant
port tracks the link state of the associated primary port, and if the link on the primary port fails, the
redundant port establishes a link and becomes active. You can back up a specified Ethernet port with a
redundant, dedicated Ethernet port. You can also back up a load-shared group of Ethernet ports with a
set of load-shared redundant Ethernet ports. If a link in the active load-shared group fails, the entire
group fails over to the redundant group.
The following criteria must be considered when configuring a software-controlled redundant port:
• You can configure only one redundant port for each primary port.
• You must manually configure the primary and redundant ports identically in terms of VLANs, QoS
settings, access lists, and so on.
• Auto-negotiation must be enabled on both the primary and redundant port.
• Only one side of the link should be configured as redundant. For example, if ports 1 and 2 are
connected between switches A and B, only switch A should be configured with redundant ports.
• Software redundant ports are not supported on 1000BASE-T ports.
Software redundant port only cover failures where both the TX and RX paths fail. If a single strand of
fiber is pulled, the software redundant port cannot correctly recover from the failure.
Example
The following command configures a software-controlled redundant port:
configure ports 3 redundant 4
The following command configures a software-controlled redundant port using the port display strings
corp1 and corp5 to identify the ports:
configure ports corp1 redundant corp5
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the part of the packet examined by the switch when selecting the egress port for
transmitting load-sharing data.
Syntax Description
ip-dest Indicates that the switch should examine the IP destination address.
ip-source Indicates that the switch should examine the IP source address.
ip-source-dest Indicates that the switch should examine the IP source and destination
addresses.
mac-dest Indicates that the switch should examine the MAC destination address.
mac-source Indicates that the switch should examine the MAC source address.
mac-source-dest Indicates that the switch should examine the MAC source and destination
addresses.
Default
N/A.
Usage Guidelines
This feature is available using the address-based load-sharing algorithm only. The address-based
load-sharing algorithm uses addressing information to determine which physical port in the
load-sharing group to use for forwarding traffic out of the switch. Addressing information is based on
the packet protocol, as follows:
• IP packets—Uses the source and destination MAC and IP address.
• All other packets—Uses the source and destination MAC address.
To verify your configuration, use the show sharing address-based command. The show sharing
address-based output displays the addressed-based configurations on the switch.
Example
The following example configures the switch to examine the MAC source and destination address:
configure sharing address-based mac-source-dest
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the Extreme Discovery Protocol (EDP) on one or more ports.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
all Specifies all ports on the switch. See “Usage Guidelines” for more information.
Default
Enabled.
Usage Guidelines
On series “e” switches, a <portlist> can be one or more port numbers. For a detailed explanation of
port specification, see“Switch Numerical Ranges” in Chapter 1.
You can use the disable edp ports command to disable EDP on one or more ports when you no
longer need to locate neighbor Extreme Networks switches.
Example
The following command disables EDP on port 4 and port 6:
disable edp ports 4,6
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the all keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables jumbo frame support on a port.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5,.
all Specifies all ports on the switch.
Default
Disabled.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification,
see“Switch Numerical Ranges” in Chapter 1.
Use the disable jumbo-frame ports command when you no longer need jumbo frame support.
Example
The following command disables jumbo frame support on port 4:
disable jumbo-frame ports 4
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the detection of loops between ports.
Syntax Description
portlist Specifies one or more ports or slots and ports to be grouped to the master
port. On a modular switch, can be a list of slots and ports. On a stand-alone
switch, can be one or more port numbers. May be in the form 1, 2, 3-5, 1:*,
15,.
Default
Disabled.
Usage Guidelines
Each port may enable loop detection. This optional feature detects that a port has been looped back to
the local system. If a loopback is detected, the port is disabled. Note that loopbacks may exist between
different ports. The feature will disable any port that both has the feature enabled, and receives an
LACP message that was sent from the local system.
Example
The following example disables loopback detection on ports 9 through 12:
disable lbdetect port 9-12
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables MAC address learning on one or more ports for security purposes.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
Enabled.
Usage Guidelines
The <portlist> can be one or more port numbers.For a detailed explanation of port specification,
see“Switch Numerical Ranges” in Chapter 1.
If MAC address learning is disabled, only broadcast traffic, EDP traffic, and packets destined to a
permanent MAC address matching that port number, are forwarded.
Use this command in a secure environment where access is granted via permanent forwarding
databases (FDBs) per port.
Learning must be disabled to allow port flooding. See the enable flooding command for information
on enabling port flooding.
Example
The following command disables MAC address learning on port 4:
disable learning ports 4
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable mirroring
disable mirroring
Description
Disables port-mirroring.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Use the disable mirroring command to stop configured copied traffic associated with one or more
ports.
Example
The following command disables port-mirroring:
disable mirroring
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable ports
disable ports [<portlist> | all |{vlan} <vlan name>]
Description
Disables one or more ports on the switch.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
all Specifies all ports on the switch.
vlan name Specifies the name of a VLAN.
Default
Enabled.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Even though a port is disabled, the link remains enabled for diagnostic purposes. To enable or re-enable
a port, use the enable ports [<portlist> | all | {vlan} <vlan name>] command.
Example
The following command disables ports 3, 5, and 12 through 15:
disable ports 3,5,12-15
History
This command was first available in ExtremeWare 7.1e.
The all option was first available for the Summit 300-48 in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
disable sharing
disable sharing [<port>]
Description
Disables a load-sharing group of ports.
Syntax Description
port Specifies the master port of a load-sharing group.
Default
Disabled.
Usage Guidelines
This command increases bandwidth tracking and resiliency.
The <port> is the port configured as the load-sharing master port. For a detailed explanation of port
specification, see“Switch Numerical Ranges” in Chapter 1.
When sharing is disabled, the master port retains all configuration including VLAN membership.
Configuration for all other member ports is reset to default values. Member ports are removed from all
VLANs to prevent loops.
Example
The following command disables sharing on master logical port 9, which contains ports 9-12:
disable sharing 9
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable smartredundancy
disable smartredundancy [<portlist>]
Description
Disables the smart redundancy feature.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
Disabled.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Use with Extreme Networks switches that support privacy and backup uplinks.
When smartredundancy is disabled, the switch changes the active link only when the current active link
becomes inoperable.
Example
The following command disables the smart redundancy feature on ports 1-4:
disable smartredundancy 1-4
History
Platform Availability
This command is available on all platforms switches.
Description
Enables the Extreme Discovery Protocol (EDP) on one or more ports.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
all Specifies all ports on the switch.
Default
Enabled.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
The EDP is used to locate neighbor Extreme Networks switches and exchange information about switch
configuration. When running on a normal switch port, EDP is used to by the switches to exchange
topology information with each other. Information communicated using EDP includes the following:
• Switch MAC address (switch ID)
• Switch software version information
• Switch IP address
• Switch VLAN-IP information
• Switch port number
Example
The following command enables EDP on port 7:
enable edp ports 7
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables support on the physical ports that will carry jumbo frames.
For PoS modules, enables jumbo-frame support to specific PoS ports when jumbo-frame support
changes the negotiated maximum receive unit (MRU) size.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
all Specifies all ports on the switch.
Default
Disabled.
Usage Guidelines
Increases performance to back-end servers or allows for VMAN 802.1q encapsulations.
You must configure the maximum MTU size of a jumbo frame before you can use the enable
jumbo-frame ports command. Use the configure jumbo-frame size command to configure the
MTU size.
The <portlist> can be a list of slots and ports. The <portlist> can be one or more port numbers. For
a detailed explanation of port specification, see “Switch Numerical Ranges” in Chapter 1.
Example
The following command enables jumbo frame support on port 5:
enable jumbo-frame ports 5
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the system to detect loops between ports. If a port is looped, it disables the port. Every N
seconds, it re-enables the port and tries again, unless “none” is specified
Syntax Description
portlist Specifies one or more ports or slots and ports to be grouped to the master
port. On a modular switch, can be a list of slots and ports. On a stand-alone
switch, can be one or more port numbers. May be in the form 1, 2, 3-5, 1:*,
1:5.
retry-timeout Specifies a time in seconds to check for loops on the ports.
Default
Disabled.
Usage Guidelines
Each port may enable loop detection. This optional feature detects that a port has been looped back to
the local system. If a loopback is detected, the port is disabled. Note that loopbacks may exist between
different ports. The feature will disable any port that both has the feature enabled, and receives an
LACP message that was sent from the local system.
If no timeout is specified, the port is disabled permanently if there is a loop detected. Otherwise, the
port is periodically re-enabled, and tested for loops every N seconds.
Example
The following example enables loopback detection on ports 9 through 12:
enable lbdetect port 9-12
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Enables MAC address learning on one or more ports.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
Enabled.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Example
The following command enables MAC address learning on ports 7 and 8:
enable learning ports 7,8
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Dedicates a port on the switch to be the mirror output port.
Syntax Description
port Specifies the port to be the mirror output port.
tagged Configures the port as tagged.
Default
N/A.
Usage Guidelines
Port-mirroring configures the switch to copy all traffic associated with one port to a monitor port on the
switch. The monitor port can be connected to a network analyzer or RMON probe for packet analysis.
The switch uses a traffic filter that copies a group of traffic to the monitor port. The traffic filter can be
defined based on one of the following criteria:
• Physical port—All data that traverses the port, regardless of VLAN configuration, is copied to the
monitor port.
• VLAN—All data to and from a particular VLAN, regardless of the physical port configuration, is
copied to the monitor port.
• Virtual port—All data specific to a VLAN on a specific port is copied to the monitor port.
Up to eight mirroring filters and one monitor port can be configured on the switch. After a port has
been specified as a monitor port, it cannot be used for any other function. Frames that contain errors are
not mirrored.
• In addition to the physical port, VLAN, and virtual port, the traffic filter can be defined based on the
following criteria:
— MAC source address/destination address—All data sent to or received from a particular source
or destination MAC address is copied to the monitor port.
For MAC mirroring to work correctly, the MAC address must already be present in the forwarding
database (FDB).
Example
The following example selects port 3 as a tagged mirror port:
enable mirroring to port 3 tagged
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
enable ports
enable ports [<portlist> | all | {vlan} <vlan name>]
Description
Enables a port.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
all Specifies all ports on the switch.
vlan name Specifies the name of a VLAN.
Default
All ports are enabled.
Usage Guidelines
Use this command to enable the port(s) if you disabled the port(s) for security, administration, or
troubleshooting purposes.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification,
see“Switch Numerical Ranges” in Chapter 1.
Example
The following command enables ports 3, 5, and 12 through 15:
enable ports 3,5,12-15
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command enables the switch to configure static port load sharing or dynamic port load sharing.
When configuring dynamic port load sharing, LACP will be used to detect and set up for the remote
side’s load sharing capabilities.
Syntax Description
Default
Disabled
Usage Guidelines
For a detailed explanation of port specification, see “Switch Numerical Ranges” in Chapter 1.
Load sharing allows you to increase bandwidth and availability between switches by using a group of
ports to carry traffic in parallel between switches. The sharing algorithm allows the switch to use
multiple ports as a single logical port or a “master” port. For example, VLANs see the load-sharing
group as a single logical port. The algorithm also guarantees packet sequencing between clients.
If a port in a load-sharing group fails, traffic is redistributed to the remaining ports in the load-sharing
group. If the failed port becomes active again, traffic is redistributed to include that port.
Load sharing must be enabled on both ends of the link, or a network loop will result.
While LACP is based on industry standard, this feature is supported between Extreme Networks
switches only. However, it may be compatible with third-party “trunking” or sharing algorithms. Check
with an Extreme Networks technical representative for more information.
• When using load sharing, you should always reference the master logical port of the load-sharing
group when configuring or viewing VLANs. VLANs configured to use other ports in the
load-sharing group will have those ports deleted from the VLAN when load sharing becomes
enabled.
• A load-sharing group can include a maximum of eight ports.
• Dynamic load sharing (LACP) cannot be used for groups that span multiple modules.
• When using load sharing with the ESRP HA feature, configure all ports in the same load-sharing
group as host attach ports. When using load sharing with the ESRP don’t count feature, configure all
ports in the same load-sharing group as don’t count ports.
• Dynamic load sharing—A grouping of ports that will use IEEE 802.3ad load sharing to dynamically
determine if load sharing is possible, and will automatically configure load sharing when possible.
Uses Link Aggregation Control Protocol (LACP), part of the IEEE 802.3ad standard, to allow the
switch to dynamically reconfigure the sharing groups. The group is only enabled when LACP
detects that the other side is also using LACP, and wants these ports to be in a group
Load-sharing algorithms allow you to select the distribution technique used by the load-sharing group
to determine the output port selection. Algorithm selection is not intended for use in predictive traffic
engineering. You can only choose the algorithm used in static load sharing. There is no option to choose
an algorithm when you use dynamic load sharing.
• Address-based—Uses addressing information to determine which physical port in the load-sharing
group to use for forwarding traffic out of the switch. Addressing information is based on the packet
protocol, as follows:
— IP packets—Uses the source and destination MAC and IP addresses, and the TCP port number.
— All other packets—Uses the source and destination MAC address.
Using the round-robin algorithm, packet sequencing between clients is not guaranteed.
If you do not explicitly select an algorithm, the port-based scheme is used. However, the address-based
algorithm has a more even distribution and is the recommended choice.
Example
The following example defines a load-sharing group that contains ports 9 through 12, and uses the first
port in the group as the master logical port:
enable sharing 9 grouping 9-12
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable smartredundancy
enable smartredundancy <portlist>
Description
Enables the Smart Redundancy feature on the redundant Gigabit Ethernet port.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
Enabled.
Usage Guidelines
When the Smart Redundancy feature is enabled, the switch always uses the primary link when the
primary link is available.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Example
The following command enables the Smart Redundancy feature on port 4 on a switch:
enable smartredundancy 4
The following command enables the Smart Redundancy feature on slot 1, port 4 on a Summit 300-48
switch:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on all platforms.
restart ports
restart ports [<portlist>]
Description
Resets autonegotiation for one or more ports by resetting the physical link.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Example
The following command resets autonegotiation on port 4:
restart ports 4
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show edp
show edp {vlan <portlist><vlan name>}
Description
Displays connectivity and configuration information for neighboring Extreme Networks switches.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification,
see“Switch Numerical Ranges” in Chapter 1.
Use the show edp command to display neighboring switches and configurations. This is most effective
with Extreme Networks switches.
Example
The following command displays the connectivity and configuration of neighboring Extreme Networks
switches:
show edp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show mirroring
show mirroring
Description
Displays the port-mirroring configuration on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
You must configure mirroring on the switch to display mirroring statistics. Use the show mirroring
command to configure mirroring.
You can use this command to display mirroring statistics and determine if mirroring is enabled or
disabled on the switch.
To view the status of port-mirroring on the switch, use the show mirroring command. The show
mirroring command displays information about the enable/disable state for port-mirroring.
Example
The following command displays switch mirroring statistics:
show mirroring
Mirror port: 5 is up
port number 1 in all vlans
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays real-time collision statistics.
Syntax Description
mgmt Specifies the management port. This option is only available on switches with
a management port.Supported only for switches that provide a management
port, such as the Summit 400.
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
If you do not specify a port number or range of ports, collision statistics are displayed for all ports.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
This status information may be useful for your technical support representative if you have a network
problem.
Example
The following command displays real-time collision statistics on port 7:
show ports 7 collisions
15 R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
16 R 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
==============================================================================
Link Status: A-Active R-Ready D-Disabled NP-Not Present LB-Loopback
0->Clear Counters U->page up D->page down ESC->exit
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays port configuration statistics.
Syntax Description
mgmt Specifies the management port. This option is only available on switches with
a management port. Supported only for switches that provide a management
port, such as the Summit 400.
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
If you do not specify a port number or range of ports, configuration statistics are displayed for all ports.
This status information may be useful for your technical support representative if you have a network
problem.
Example
The following command displays the port configuration statistics for all ports on a switch:
show ports config
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays detailed system-related information.
Syntax Description
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
detail Specifies detailed port information.
Default
N/A.
Usage Guidelines
This command displays the following:
• Port number
• Diagnostics
• Port configuration
— Admin state
— Link state
— Link counter
— VLAN configuration
— STP configuration
— Trunking
— EDP
— Load balancing
— Learning
— Flooding
— QoS profiles
If you do not specify a port number or range of ports, detailed system-related information is displayed
for all ports. The data is displayed in a table format.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
This status information may be useful for your technical support representative if you have a network
problem.
• The detail parameter is used to provided more specific port information. The data is called out
with written explanations versus displayed in a table format.
• The detailed output displays a link filter counter. The link filter counter is calculated at the middle
layer on receiving an event. The link filter up indicates the number of link transitions from down to
up at the middle layer filter. The link filter down indicates the number of link transitions from up to
down at the middle layer filter.
Example
The following command displays port system-related information:
show ports info
Extremeware
Copyright (C) 1996-2004 Extreme Networks. All rights reserved.
===============================================================
(n) Ingress TOS Enabled, (o) Dot1p Vlan Priority Replacement Enabled
(P) Software Primary Port, (q) Background QOS Monitoring Enabled
(R) Software Redundant Port
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays a histogram of packet statistics.
Syntax Description
mgmt Specifies the management port Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
If you do not specify a port number or range of ports, a histogram is displayed for all ports.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification,
see“Switch Numerical Ranges” in Chapter 1.
This status information may be useful for your technical support representative if you have a network
problem.
Example
The following command displays packet statistics for ports 1 through 6:
show ports 1-6 packet
Receive Packet Statistics Sun Sep 12 14:48:59 2004
Port Link Packet Sizes
Status 0-64 65-127 128-255 256-511 512-1023 1024-1518 Jumbo
================================================================================
1 A 410465 3548292 97395 51257 7390 1547785 0
2 A 397578 1724578 94290 49422 10469 2491883 0
3 R 0 0 0 0 0 0 0
4 A 394646 2485133 102640 52893 5945 1537346 0
5 A 394141 2439441 89201 49095 4141 1532115 0
6 A 394741 2099487 67017 40001 4143 2540292 0
Sun Sep 12 14:48:40 2004=======================================================
=====Link Status: A-Active R-Ready D-Disabled NP-Not Present LB-Loopback
0->Clear Counters U->page up D->page down ESC->exit
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays detailed information about redundant ports.
Syntax Description
This command does not have any parameters or variables.
Default
N/A
Usage Guidelines
An asterisk appears when an individual link is active and an exclamation point when the link is
disabled.
Example
The following examples gives information about redundant ports:
Primary *5 Redundant 7
Primary *6 Redundant 25
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays port loadsharing groups.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
None.
Example
The following example shows all of the load sharing groups on the Summit 400:
* Summit400-48t:46 # show ports sharing
Load Sharing Monitor
Config Current Ld Share Ld Share Link Link
Master Master Type Group Status Ups
==========================================================
37 37 a 37 A 1
a 38 R 0
a 39 A 1
a 40 A 1
a 41 A 1
a 42 A 1
Link Status: (A) Active, (D) Disabled, (LB) Loopback, (ND) Not Distributing
(NP) Not Present, (R) Ready
The next example shows dynamic load sharing configured on a Summit 300-24:
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays real-time port utilization information.
Syntax Description
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
Use the [Spacebar] to toggle between packet, byte, and bandwidth utilization information.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification,
see“Switch Numerical Ranges” in Chapter 1.
If you do not specify a port number or range of ports, port utilization information is displayed for all
ports.
This status information may be useful for your technical support representative if you have a network
problem.
Example
The following command displays utilization statistics for port 1:
show ports 1 utilization
The following examples show the output from the show ports utilization command for all ports on the
switch. The three displays show the information presented when you use the spacebar to toggle
through the display types. The first display shows utilization in terms of packets:
Link Utilization Averages Wed Jan 23 21:29:45 2004
Port Link Receive Peak Rx Transmit Peak Transmit
Status packet/sec pkt/sec pkt/sec pkt/sec
=====================================================================================
1 A 43 255 4 14
2 R 0 0 0 0
3 R 0 0 0 0
4 R 0 0 0 0
5 R 0 0 0 0
6 R 0 0 0 0
7 R 0 0 0 0
8 R 0 0 0 0
================================================================================
Link Status: A-Active R-Ready D-Disabled NP-Not Present LB-Loopback
spacebar->toggle screen U->page up D->page down ESC->exit
===========================================================================
Link Status: A-Active R-Ready D-Disabled NP-Not Present
================================================================================
Link Status: A-Active R-Ready D-Disabled NP-Not Present
spacebar->toggle screen U->page up D->page down ESC->exit
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays port VLAN information.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
vlan_name Specifies to display VLAN information from the VLAN with this name.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays VLAN information for port 2:
show ports 2 vlan info
Port 2
Name VID Protocol Addr Flags Proto Ports
v1 4093 ------------------ -------- ANY 2/2
#
#
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays port VLAN statistics.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
vlan_name Specifies to display VLAN statistics from the VLAN with this name.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays VLAN information for the corp VLAN:
show ports vlan corp vlan stats
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the address-based load sharing configuration.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This feature is available using the address-based load-sharing algorithm only. The address-based
load-sharing algorithm uses addressing information to determine which physical port in the
load-sharing group to use for forwarding traffic out of the switch. Addressing information is based on
the packet protocol, as follows:
• IP packets—Uses the source and destination MAC and IP address, and the TCP port number.
• All other packets—Uses the source and destination MAC address.
To verify your configuration, use the show sharing address-based command. The show sharing
address-based output displays the addressed-based configurations on the switch.
Example
The following example displays the address-based load sharing configuration on the switch:
show sharing address-based
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Clears the user-defined display string from one or more ports.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
This command removes the display string that you configured using the configure ports
display-string command.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Example
The following command clears the user-defined display from port 4:
unconfigure ports 4 display-string
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Clears a previously configured software-controlled redundant port.
Syntax Description
portlist Specifies one or more ports or ports. Can be one or more port numbers. May
be in the form 1, 2, 3-5, 1:3.
portid Specifies a port using the display string configured for the port. Only one port
can be specified using this method.
Default
N/A.
Usage Guidelines
<portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
The <port id> is the display string configured for the port. Use the configure ports <portnumber>
display-string <string> command to configure a display string for the port.
The list of port numbers or the port display string specifies the redundant port(s).
Example
The following command unconfigures a software-controlled redundant port:
unconfigure ports 5 redundant
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on all platforms.
Description
Adds a MAC address as a potential member of a MAC-based VLAN.
Syntax Description
mac_address The MAC address to be added to the specified VLAN. Specified in the form
nn:nn:nn:nn:nn:nn.
any indicates that any MAC-address associated with the specified MAC group
may be a member.
group_number The group number that should be associated with the specified MAC address.
Specified as an integer
any indicates that this MAC address can be associated with any MAC group.
vlan name The name of the VLAN with which this MAC address should associated.
Default
N/A.
Usage Guidelines
The specified MAC address must be associated with an end station/host only, not a layer 2 repeater
device.
Adding a MAC address means that when the specified address is detected on a member port, as
specified by its group membership, it can participate in the VLAN.
At least one port must be enabled to use the MAC-based VLAN algorithm before any MAC addresses
can be added.
Example
Given ports enabled for MAC-based VLANs as follows:
enable mac-vlan mac-group any ports 16,17
enable mac-vlan mac-group 10 ports 11,12
The following command sets up the end-station with MAC address 00:00:00:00:00:01 to participate in
VLAN engineering via the MAC-enabled ports 16 or 17:
configure mac-vlan add mac-address 00:00:00:00:00:01 mac-group any vlan engineering
MAC address 00:00:00:00:00:01 cannot get access via ports 11 or 12 because it is not configured for
mac-group 10.
The following command sets up the endstation 00:00:00:00:00:02 to participate in VLAN engineering
through the ports in group 10 (ports 11 or 12) or through ports 16 or 17 (enabled for any mac-group):
configure mac-vlan add mac-address 00:00:00:00:00:02 mac-group 10 vlan engineering
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes a MAC address from any MAC-based VLANs with which it was associated.
Syntax Description
all Indicates that all MAC addresses should be removed from all VLANs.
mac_address The MAC address to be removed. Specified in the form
nn:nn:nn:nn:nn:nn.
any indicates that all MAC-addresses should be removed from all VLANs.
Default
NA.
Usage Guidelines
None.
Example
The following command removes the endstation with MAC address 00:00:00:00:00:02 from participating
in any MAC-based VLANs.
configure mac-vlan delete mac-address 00:00:00:00:00:02
The following commands remove the all MAC addresses from participating in any VLANs:
configure mac-vlan delete all
configure mac-vlan delete mac-address any
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a user-defined protocol filter.
Syntax Description
Default
N/A.
Usage Guidelines
A maximum of 15 protocol filters, each containing a maximum of six protocols, can be defined.
The protocol filter must already exist before you can use this command: use the create protocol
command to create the protocol filter.
On the “i” series platform, all fifteen protocol filters can be active and configured for use. On all other
platforms, no more than seven protocols can be active and configured for use.
Example
The following command configures a protocol named Fred by adding protocol type LLC SAP with a
value of FFEF:
configure protocol fred add llc feff
History
This command was first available in ExtremeWare 1.0.
Platform Availability
This command is available on the Summit 400-48t.
Description
Deletes the specified protocol type from a protocol filter.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes protocol type LLC SAP with a value of FFEF from protocol Fred:
configure protocol fred delete llc feff
History
This command was first available in ExtremeWare 1.0.
Platform Availability
This command is available on all platforms.
Description
Adds one or more ports in a VLAN.
Syntax Description
Default
Untagged.
Usage Guidelines
The VLAN must already exists before you can add (or delete) ports: use the create vlan command to
create the VLAN.
If the VLAN uses 802.1Q tagging, you can specify tagged or untagged port(s). If the VLAN is untagged,
the ports cannot be tagged.
Untagged ports can only be a member of a single VLAN. By default, they are members of the default
VLAN (named Default). In order to add untagged ports to a different VLAN, you must first remove
them from the default VLAN. You do not need to do this to add them to another VLAN as tagged
ports.
You must configure a loopback port with a unique loopback VLAN tag ID before adding rate-shaped
ports.
Example
The following command assigns tagged ports 1, 2, 3, and 6 to a VLAN named accounting:
configure vlan accounting add ports 1, 2, 3, 6 tagged
History
This command was first available in ExtremeWare 7.1e
This command was modified in ExtremeWare 7.2e to support rate limiting with the soft-rate-limit
keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes one or more ports in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes ports 1, 2, 3, and 6 from a VLAN named accounting:
configure accounting delete port 1, 2, 3, 6
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Assigns an IP address and an optional subnet mask to the VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
The VLAN must already exists before you can assign an IP address: use the create vlan command to
create the VLAN.
NOTE
If you plan to use the VLAN as a control VLAN for an EAPS domain, do NOT configure the VLAN with
an IP address.
Example
The following commands are equivalent; both assign an IP address of 10.12.123.1 to a VLAN named
accounting:
configure vlan accounting ipaddress 10.12.123.1/24
configure vlan accounting ipaddress 10.12.123.1 255.255.255.0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Renames a previously configured VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
You cannot change the name of the default VLAN “Default”
Example
The following command renames VLAN vlan1 to engineering:
configure vlan vlan1 name engineering
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Assigns a unique 802.1Q tag to the VLAN.
Syntax Description
Default
The default VLAN uses an 802.1Q tag (and an internal VLANid) of 1.
Usage Guidelines
If any of the ports in the VLAN will use an 802.1Q tag, a tag must be assigned to the VLAN. The valid
range is from 2 to 4,095 (tag 1 is assigned to the default VLAN).
The 802.1Q tag will also be used as the internal VLANid by the switch.
You can specify a value that is currently used as an internal VLANid on another VLAN; it will become
the VLANid for the VLAN you specify, and a new VLANid will be automatically assigned to the other
untagged VLAN.
Example
The following command assigns a tag (and internal VLANid) of 120 to a VLAN named accounting:
configure accounting tag 120
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
create protocol
create protocol <protocol_name>
Description
Creates a user-defined protocol filter.
Syntax Description
protocol_name Specifies a protocol filter name. The protocol filter name can have a maximum
of 31 characters.
Usage Guidelines
Protocol-based VLANs enable you to define packet filters that the switch can use as the matching
criteria to determine if a particular packet belongs to a particular VLAN.
After you create the protocol, you must configure it using the configure protocol command. To
assign it to a VLAN, use the configure vlan <vlan name> protocol command.
Example
The following command creates a protocol named fred:
create protocol fred
History
This command was first available in ExtremeWare 1.0.
Platform Availability
This command is available on the Summit 400-48t.
create vlan
create vlan <vlan name>
Description
Creates a named VLAN.
Syntax Description
Default
A VLAN named Default exists on all new or initialized Extreme switches:
• It initially contains all ports on a new or initialized switch, except for the management port(s), if
there are any.
• It has an 802.1Q tag of 1.
• The default VLAN is untagged on all ports.
• It uses protocol filter any.
An untagged VLAN named MacVlanDiscover exists on all new or initialized “e” series switches:
• It initially contains no ports.
• It does not initially use an 802.1Q tag, and is assigned the next available internal VLANid starting
with 4095.
A VLAN named Mgmt exists on switches that have management modules or management ports.
• It initially contains the management port(s) the switch.
• It is assigned the next available internal VLANid as an 802.1Q tag.
Usage Guidelines
A newly-created VLAN has no member ports, is untagged, and uses protocol filter “any” until you
configure it otherwise. Use the various configure vlan commands to configure the VLAN to your
needs.
Internal VLANids are assigned automatically using the next available VLANid starting from the high
end (4095) of the range.
By default the switch supports 1024 VLANs. The switch can support a maximum of 3000 VLANs if the
CPU-transmit-priority is set to normal, rather than high (the default). Use the configure
cpu-transmit-priority command to change the CPU transmit priority.
Each VLAN name can be up to 32 standard alphanumeric characters, but must begin with an
alphabetical letter. Quotation marks can be used to enclose a VLAN name that does not begin with an
alphabetical character, or that contains a space, comma, or other special character.
VLAN names are locally significant. That is, VLAN names used on one switch are only meaningful to
that switch. If another switch is connected to it, the VLAN names have no significance to the other
switch.
Example
The following command creates a VLAN named accounting:
create vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete vlan
delete vlan <vlan name>
Description
Deletes a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
If you delete a VLAN that has untagged port members, and you want those ports to be returned to the
default VLAN, you must add them back explicitly using the configure vlan add ports command.
NOTE
The default VLAN cannot be deleted.
Example
The following command deletes the VLAN accounting:
delete accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables a port from using the MAC-based VLAN algorithm.
Syntax Description
Default
N/A.
Usage Guidelines
Disabling a port removes it from the MacVlanDiscover VLAN. But does not automatically return it to
the default VLAN. If you need this port to be a member of the default VLAN, you must explicitly add it
back.
Example
The following command disables ports 16 and 17 from using the MAC-based VLAN algorithm:
disable mac-vlan port 16,17
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables a port to use the MAC-based VLAN algorithm.
Syntax Description
group_number A group number that should be associated with a specific set of ports.
Specified as an integer.
any indicates that these ports can be considered members of any MAC group.
portlist A list of ports. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
Enabling ports for MAC-based VLAN usage automatically adds them to the VLAN MacVlanDiscover as
untagged ports.
In order to enable ports as part of a MAC group, they cannot be untagged members of any other
VLAN. Before you can enable them, you must ensure that they have been removed from the default
VLAN (named Default).
Example
The following set of commands removes ports 16 and 17 from the default VLAN, and then enables
them for use with the MAC-based VLAN, associated with any MAC group:
configure default delete port 16, 17
enable mac-vlan mac-group any port 16,17
The following commands enable ports 11 and 12 for use with a MAC-based VLAN, associated with
MAC group 10:
configure default delete port 11, 12
enable mac-vlan mac-group 10 port 11,12
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show mac-vlan
show mac-vlan {configuration | database}
Description
Displays the MAC-based VLAN configuration and MAC address database content.
Syntax Description
Default
Shows both configuration and database information.
Usage Guidelines
Use the keyword configuration to display only the top section of this information. Use the database
keyword to display only the lower section.
Example
The following is an example of the show mac-vlan command:
Port Vlan Group State
11 MacVlanDiscover 10 Discover
12 MacVlanDiscover 10 Discover
16 MacVlanDiscover any Discover
17 MacVlanDiscover any Discover
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show protocol
show protocol {<protocol>}
Description
Displays protocol filter definitions.
Syntax Description
Default
Displays all protocol filters.
Usage Guidelines
Displays the defined protocol filter(s) with the types and values of its component protocols.
Example
The following is an example of the show protocol command:
Protocol Name Type Value
---------------- ----- ------
IP etype 0x0800
etype 0x0806
netbios llc 0xf0f0
llc 0xf0f1
decnet etype 0x6003
etype 0x6004
appletalk snap 0x809b
snap 0x80f3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show vlan
show vlan {<vlan name>} <vlan name>}
Description
Displays information about VLANs.
Syntax Description
Default
Summary information for all VLANs on the device.
Usage Guidelines
Unlike many other vlan-related commands, the keyword “vlan” is required in all forms of this
command except when requesting information for a specific vlan.
Use the command show vlan to display summary information for all VLANs. It shows various
configuration options as a series of “flags” (see the example below). VLAN and protocol names may be
abbreviated in this display.
Example
The following is an example of the show vlan command:
* Summit400-48t:68 # sh vlan
Name VID Protocol Addr Flags Proto Ports
Default 1 0.0.0.0 /BP -------------- ANY 0/0
MacVlanDiscover 4094 ------------------ -------- ANY 0/0
Mgmt 4093 ------------------ -------- ANY 0/1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes the IP address of the VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes the IP address from the VLAN accounting:
unconfigure vlan accounting ipaddress
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Entries are added into the FDB in the following two ways:
• The switch can learn entries. The system updates its FDB with the source MAC address from a
packet, the VLAN, and the port identifier on which the source packet is received.
• You can enter and update entries using a MIB browser, an SNMP network manager, or the CLI.
A QoS profile can be associated with a MAC address (and VLAN) of a device that will be dynamically
learned. The FDB treats the entry like a dynamic entry (it is learned, it can be aged out of the database,
and so on). The switch applies the QoS profile as soon as the FDB entry is learned.
clear fdb
clear fdb {<mac_address> | blackhole | ports <portlist> | vlan <vlan name>}
Description
Clears dynamic FDB entries that match the filter.
Syntax Description
Default
Clears all dynamic FDB entries.
Usage Guidelines
This command clears FDB entries based on the specified criteria. When no options are specified, the
command clears all dynamic FDB entries.
Example
The following command clears any FDB entries associated with ports 3-5:
clear fdb ports 3-5
The following command clears any FDB entries associated with VLAN corporate:
clear fdb vlan corporate
History
This command was available in ExtremeWare 7.1e.
The command was modified in ExtremeWare 7.2e to support the blackhole keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the FDB aging time for dynamic entries.
Syntax Description
seconds Specifies the aging time in seconds. Range is 15 through 1,000,000. A value
of 0 indicates that the entry should never be aged out.
Default
300 seconds.
Usage Guidelines
The range is 15 through 1,000,000 seconds.
If the aging time is set to zero, all aging entries in the database are defined as static, nonaging entries.
This means that they do not age out, but non-permanent static entries can be deleted if the switch is
reset.
Example
The following command sets the FDB aging time to 3,000 seconds:
configure fdb agingtime 3000
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Creates a blackhole FDB entry.
Syntax Description
Default
N/A.
Usage Guidelines
Blackhole entries are useful as a security measure or in special circumstances where packets with a
specific source or destination address must be discarded.
A blackhole entry configures the switch to discard packets with the specified MAC address. You can
specify whether the MAC address should match the source (ingress) MAC address, or the destination
(egress) MAC address, or both.
Blackhole entries are treated like permanent entries in the event of a switch reset or power off/on cycle.
Blackhole entries are never aged-out of the database. In the output from a show fdb command, entries
will have “p” flag (permanent) set, as well as the “b” (for ingress blackhole) and/or “B” (for egress
blackhole) flags set.
Example
The following example adds a blackhole entry to the FDB for MAC address is 00 E0 2B 12 34 56, in
VLAN marketing on port 4:
create fdbentry 00:E0:2B:12:34:56 vlan marketing both
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Creates a permanent dynamic FDB entry, and associates it with an ingress and/or egress QoS profile.
Syntax Description
Default
N/A.
Usage Guidelines
This command is used to associate QoS profiles with packets received from or destined for the specified
MAC address, while still allowing the FDB entry to be dynamically learned. The FDB entry is not
actually created until the MAC address is encountered as the source MAC address in a packet. Thus,
initially the entry may not appear in the show fdb output. Once the entry has been learned, it is created
as a permanent dynamic entry, designated by “dpm” in the flags field of the show fdb output.
A dynamic entry is flushed and relearned (updated) when any of the following take place:
• A VLAN is deleted.
• A VLAN identifier (VLANid) is changed.
• A port mode is changed (tagged/untagged).
• A port is deleted from a VLAN.
• A port is disabled.
• A port enters blocking state.
• A port QoS setting is changed.
• A port goes down (link down).
Using the any-mac keyword, you can enable traffic from a QoS VLAN to have higher priority than
802.1p traffic. Normally, an 802.1p packet has a higher priority over the VLAN classification. To use this
feature, you must create a wildcard permanent FDB entry named any-mac and apply the QoS profile to
the individual MAC entry.
You can use the show fdb permanent command to display permanent FDB entries, including their QoS
profile associations.
Example
The following example associates the QoS profile qp2 with a dynamic entry for MAC address
00:A0:23:12:34:56 on VLAN net34 that will be learned by the FDB:
create fdbentry 00:A0:23:12:34:56 vlan net34 dynamic ingress-qosprofile qp2
The following example associates the QoS profile qp5 with the wildcard permanent FDB entry any-mac
on VLAN v110:
History
This command was available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the any-mac option.
Platform Availability
This command is available on the “e” series platforms.
Description
Creates a permanent static FDB entry, and optionally associates it with an ingress and/or egress QoS
profile.
Syntax Description
Default
N/A.
Usage Guidelines
If more than one port number is associated with a permanent MAC entry, packets are multicast to the
multiple destinations.
Permanent entries are retained in the database if the switch is reset or a power off/on cycle occurs. A
permanent static entry can either be a unicast or multicast MAC address. The Summit 400 can support a
maximum of 64 permanent entries.
After they have been created, permanent static entries stay the same as when they were created. If the
same MAC address is encountered on another virtual port that is not included in the permanent MAC
entry, it is handled as a blackhole entry. The static entry is not updated when any of the following take
place:
• A VLAN is deleted.
• A VLAN identifier (VLANid) is changed.
• A port mode is changed (tagged/untagged).
• A port is deleted from a VLAN.
• A port is disabled.
• A port enters blocking state.
• A port QoS setting is changed.
• A port goes down (link down).
Permanent static entries are designated by “spm” in the flags field of the show fdb output. You can use
the show fdb permanent command to display permanent FDB entries, including their QoS profile
associations.
Example
The following example adds a permanent, static entry to the FDB for MAC address is 00 E0 2B 12 34 56,
in VLAN marketing on port 4:
create fdbentry 00:E0:2B:12:34:56 vlan marketing port 4
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete fdbentry
delete fdbentry [[<mac_address> | broadcast-mac] vlan <vlan name> | all]
Description
Deletes one or all permanent FDB entries.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following example deletes a permanent entry from the FDB:
delete fdbentry 00:E0:2B:12:34:56 vlan marketing
The following example deletes all permanent entry from the FDB:
delete fdbentry all
History
This command was available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2.e to support the broadcast-mac option.
Platform Availability
This command is available on the “e” series platforms.
show fdb
show fdb {<mac_address> | permanent | ports <portlist> | vlan <vlan name>}
Description
Displays FDB entries.
Syntax Description
mac_address Specifies a MAC address, using colon-separated bytes, for which FDB entries
should be displayed.
permanent Displays all permanent entries, including the ingress and egress QoS profiles.
portlist Displays the entries for one or more ports. May be in the form 1, 2, 3-5, 2:5,
2:6-2:8.
vlan name Displays the entries for a specific VLAN.
Default
All.
Usage Guidelines
Displays FDB entries as specified, or displays all FDB entries.
EQP The Ingress QoS profile assigned to the entry (appears only if the keyword
permanent is specified).
IQP The Egress QoS profile assigned to the entry (appears only if the keyword
permanent is specified).
Index The FDB hash index, in the format <bucket>-<entry>.
Mac The MAC address that defines the entry.
Vlan The VLAN for the entry.
Age The age of the entry, in seconds (does not appear if the keyword permanent
is specified).
Use The number of IP FDB entries that use this MAC address as a next hop or
last hop (does not appear if the keyword permanent is specified).
Example
The following command displays information about all the entries in the FDB:
show fdb
Flags: (B) Egress Blackhole, (b) Ingress Blackhole, (d) Dynamic, (s) Static
(p) Permanent, (m) MAC, (S) secure MAC, (l) lockdown MAC, (M) Mirror
(i) IP, (z) translation MAC, (Q) Questionable, (R) Remapped
Total: 33 Static: 16 Perm: 0 Locked: 0 Secure: 0 Dynamic: 17 Dropped: 0
Questionable: 0 Remapped: 0
FDB Aging time: 300 seconds
The following command displays information about the permanent entries in the FDB:
Flags: (B) Egress Blackhole, (b) Ingress Blackhole, (d) Dynamic, (s) Static
(p) Permanent, (m) MAC, (S) secure MAC, (l) lockdown MAC, (M) Mirror
(i) IP, (z) translation MAC, (Q) Questionable, (R) Remapped
[ ] : authorize port list
Total: 3 Secure: 0
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Qualify of Service (QoS) is a feature of ExtremeWare that allows you to specify different service levels
for outbound and inbound traffic. QoS is an effective control mechanism for networks that have
heterogeneous traffic patterns. Using QoS, you can specify the service that a traffic type receives.
Policy-based QoS allows you to protect bandwidth for important categories of applications or
specifically limit the bandwidth associated with less critical traffic. The switch contains separate
hardware queues on every physical port. Each hardware queue is programmed by ExtremeWare with
bandwidth management and prioritization parameters, defined as a QoS profile. The bandwidth
management and prioritization parameters that modify the forwarding behavior of the switch affect
how the switch transmits traffic for a given hardware queue on a physical port. Up to eight physical
queues per port are available.
To configure QoS, you define how your switch responds to different categories of traffic by creating and
configuring QoS profiles. The service that a particular type of traffic receives is determined by assigning
a QoS profile to a traffic grouping or classification. The building blocks are defined as follows:
• QoS profile—Defines bandwidth and prioritization parameters.
• Traffic grouping—A method of classifying or grouping traffic that has one or more attributes in
common.
• QoS policy—The combination that results from assigning a QoS profile to a traffic grouping.
QoS profiles are assigned to traffic groupings to modify switch-forwarding behavior. When assigned to
a traffic grouping, the combination of the traffic grouping and the QoS profile comprise an example of a
single policy that is part of Policy-Based QoS.
Extreme switch products support explicit Class of Service traffic groupings. This category of traffic
groupings describes what is sometimes referred to as explicit packet marking, and includes:
• IP DiffServ code points, formerly known as IP TOS bits
All Extreme switches support the standard 802.1p priority bits that are part of a tagged Ethernet packet.
Description
Configures the 802.1p priority value for traffic generated on the switch.
Syntax Description
Default
N/A.
Usage Guidelines
The 802.1p priority field is placed in the 802.1Q tag when a packet is generated by the switch. The
switch CPU generates traffic, for example, when ping packets are sent out by a user on the switch
console.
To configure which queue to use for traffic traveling across a VLAN, use the following command:
Example
The following command configures VLAN accounting to use priority 6 in its generated traffic:
configure vlan accounting priority 6
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the examination of the DiffServ field in an IP packet.
Syntax Description
portlist Specifies a list of ports to which the parameters apply. May be in the form 1,
2, 3-5.
all Specifies that DiffServ examination should be disabled for all ports.
Default
N/A.
Usage Guidelines
None.
Example
The following command disables DiffServ examination on selected ports:
disable diffserv examination ports 3,5,6
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the DiffServ field of an ingress IP packet to be examined in order to select a QoS profile.
Syntax Description
portlist Specifies a list of ports to which the parameters apply. May be in the form 1,
2, 3-5, 2:5, 2:6-2:8.
all Specifies that DiffServ examination should be enabled for all ports.
Default
Disabled.
Usage Guidelines
None.
Example
The following command enables DiffServ examination on selected ports:
enable diffserv examination ports 3,5,6
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays real-time QoS statistics for egress packets on one or more ports.
Syntax Description
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more ports. On the Summit 400, can be one or more port
numbers. May be in the form 1, 2, 3-5.
Default
Shows QoS statistics for all ports in egress.
Usage Guidelines
The Summit 400 has a hardware limitation that prevents changes to QoS by an ACL, or another means,
from being shown on the show ports qosmonitor command. This command only shows the original
QoS of the frame.
The real-time display scrolls through the given portlist to provide statistics. You can choose screens for
packet count and packets per second. The specific port being monitored is indicated by an asterisk (*)
appearing after the port number in the display.
Example
The following command shows the real-time QoS statistics related to the specified ports:
show ports 1-2, 49 qosmonitor
================================================================================
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show qosprofile
show qosprofile {<qosprofile>} {port <portlist>}
Description
Displays QoS information on the switch.
Syntax Description
Default
Displays QoS information for all profiles.
Usage Guidelines
Information displayed includes:
• QoS profile name
• Minimum bandwidth
• Maximum bandwidth
• Priority
• A list of all traffic groups to which the QoS profile is applied
Example
The following command shows the QoS information for the specified port:
show qosprofile 1:1
1:1:
Queue: Q0 using QP1 MinBw=0% MaxBw=100% Pri=2.
Q1 using QP2 MinBw=0% MaxBw=100% Pri=1.
Q2 using QP3 MinBw=0% MaxBw=100% Pri=4.
Q3 using QP4 MinBw=0% MaxBw=100% Pri=3.
Q4 using QP5 MinBw=0% MaxBw=100% Pri=4.
Q5 using QP6 MinBw=0% MaxBw=100% Pri=5.
Q6 using QP7 MinBw=0% MaxBw=100% Pri=6.
Q7 using QP8 MinBw=0% MaxBw=100% Pri=7.
History
This command was available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Removes the DiffServ examination code point from a port.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes DiffServ code-point examination from ports 5-8:
unconfigure diffserv examination ports 5-8
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
NAT is a feature that allows one set of IP addresses, typically private IP addresses, to be converted to
another set of IP addresses, typically public Internet IP addresses. This conversion is done transparently
by having a NAT device (any Extreme Networks switch using the “i” chipset) rewrite the source IP
address and layer 4 port of the packets.
You can configure NAT to conserve IP address space by mapping a large number of inside (private)
addresses to a much smaller number of outside (public) addresses.
In implementing NAT, you must configure at least two separate VLANs involved. One VLAN is
configured as inside, and corresponds to the private IP addresses you would like to translate into other
IP addresses. The other type of VLAN is configured as outside, which corresponds to the public
(probably Internet) IP addresses you want the inside addresses translated to. The mappings between
inside and outside IP addresses are done using rules that specify the IP subnets involved and the
algorithms used to translate the addresses.
NOTE
The NAT modes in ExtremeWare only support translating traffic that initiates from inside addresses.
NAT rules are associated with a single outside VLAN. Multiple rules per outside VLAN are allowed.
The rules take effect in the order they are displayed using the show command. Any number of inside
VLANs can use a single outside VLAN, assuming that you have created proper rules. Similarly, a single
inside VLAN can use any number of different outside VLANs, assuming that the rules and routing are
set up properly.
TCP and UDP layer 4 ports, in combination with the IP addresses, form a unique identifier which
allows hosts (as well as the NAT switch) to distinguish between separate conversations. NAT operates
by replacing the inside IP packet’s source IP and layer 4 port with an outside IP and layer 4 port. The
NAT switch maintains a connection table to map the return packets on the outside VLAN back into
their corresponding inside sessions.
clear nat
clear nat [connections | stats}
Description
Clears NAT connections or statistics.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command clears NAT connections:
clear nat connections
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a NAT translation rule that translates private IP addresses to public IP addresses on the outside
VLAN.
Syntax Description
vlan name Specifies the name of the outside VLAN to which this rule applies.
source_ipaddress/mask Specifies a subnet IP address (in the format x.x.x.x/mask where mask is the
number of bits in the subnet mask) that defines the source of the traffic to be
mapped.
l4-port Specifies a layer 4 port or port range. When used with a source IP address,
indicates that the rule applies only to traffic from the specified layer 4 port(s).
When used with a destination IP address, indicates that the rule applies only
to packets with the specified layer 4 port(s) as their destination.
port Specifies a port number in the range 1 to 65535.
any indicates that the rule should be applied to traffic to/from any layer 4 port.
dest_ipaddress/mask Specifies a subnet IP address (in the format x.x.x.x/mask where mask is the
number of bits in the subnet mask) used to determine the packets to which
this rule applies.
nat_ipaddress Specifies an IP address for the outside VLAN to which the source IP
addresses will be mapped. This can be specified as a subnet (IP address and
mask) or as an address range.
tcp Specifies only TCP traffic should be translated.
udp Specifies only UDP traffic should be translated.
both Specifies that both TCP and UDP traffic should be translated.
portmap Specifies that port-mapping mode should be used.
min Specifies a port number in the range 1 to 65535.The default setting is 1024.
max Specifies a port number in the range 1 to 65535. The default setting is 65535.
auto-constrain Specifies that each inside IP address should be restricted in the number of
simultaneous connections.
Default
N/A.
Usage Guidelines
Four different modes are used to determine how the outside IP addresses and layer 4 ports are
assigned:
• Static mapping
• Dynamic mapping
• Port-mapping
• Auto-constraining
When static mapping is used, each inside IP address uses a single outside IP address. The layer 4 ports
are not changed, and only the IP address is rewritten.
With dynamic mapping, the number of inside hosts can be greater than the number of outside hosts.
The outside IP addresses are allocated on a first-come, first-serve basis to the inside IP addresses. The
layer 4 ports are not changed. When the last session for a specific inside IP address closes, that outside
IP address can be used by other hosts.
The source IP address specifies private side IP addresses and the to IP address (the NAT address)
specifies the public side IP address. The addition of the destination optional keyword after the source
IP address and mask species that the NAT rule to be applied to only packets with a specific destination
IP address.
If the netmask for both the source and NAT addresses is /32, the switch will use static NAT translation.
If the netmask for both the source and NAT addresses are not both /32, the switch will use dynamic
NAT translation.
With static or dynamic translation rules, which do not rely on layer 4 ports, ICMP traffic is translated
and allowed to pass.
The addition of a layer 4 protocol name and the portmap keyword tells the switch to use portmap
mode. As each new connection is initiated from the inside, the NAT device picks the next available
source layer 4 port on the first available outside IP address. When all ports on a given IP address are in
use, the NAT device uses ports off of the next outside IP address.
Optionally, you may specify the range of layer 4 ports the switch chooses on the translated IP addresses.
The default setting for min is 1024. The default setting for max is 65535. There is a performance penalty
associated with specifying a specific port range other than the default.
ICMP traffic is not translated in portmap mode. You must add a dynamic NAT rule for the same IP
address range to allow for ICMP traffic.
The auto-constraining algorithm for port-mapping limits the number of outside layer 4 ports a single
inside host can use simultaneously. The limitation is based on the ratio of inside to outside IP addresses.
The outside IP address and layer 4 port space is evenly distributed to all possible inside hosts. This
guarantees that no single inside host can prevent other traffic from flowing through the NAT device.
Because of the large number of simultaneous requests that can be made from a web browser, it is not
recommended that this mode be used when a large number of inside hosts are being translated to a
small number of outside IP addresses.
ICMP traffic is not translated in auto-constrain mode. You must add a dynamic NAT rule for the same
IP address range to allow for ICMP traffic.
The addition of the l4-port optional keyword allows the NAT rule to be applied to only packets with a
specific layer 4 source or destination port. If you use the layer 4-port command after the source
IP/mask, the rule will only match if the port(s) specified are the source layer 4-ports. If you use the
l4-port command after the destination IP/mask, the rule will only match if the port(s) specified are the
destination layer 4 ports. Both options may be used together to further limit the rule. If you specify
layer 4 ports, ICMP traffic will not translated and allowed to pass.
Rules are processed in order, usually in the order in which they were added. When a single rule is
matched, no other rules are processed. You can view the rule order using the show nat rules
command.
Example
The following command defines a static translation rule that specifies that traffic coming from
192.168.1.12 be mapped to 216.52.8.32 on outside VLAN out_vlan_1:
configure nat add out_vlan_1 map source 192.168.1.12/32 to 216.52.8.32/32
The following command defines a dynamic translation rule that specifies that traffic coming from
subnet 192.168.1.0 should be mapped to IP addresses in the range of 216.52.8.1 to 216.52.8.31 on outside
VLAN out_vlan_1:
configure nat add out_vlan_1 map source 192.168.1.0/24 to 216.52.8.1 - 216.52.8.31
The following command defines a translation rule that specifies that TCP/UDP packets coming from
192.168.1.12 and destined for 192.168.5.20 be mapped to 216.52.8.32 on outside VLAN out_vlan_1:
configure nat add out_vlan_1 map source 192.168.1.12/32 destination 192.168.5.20 to
216.52.8.32/32
The following command defines a portmap translation rule that specifies that both TCP and UDP traffic
from subnet 102.168.2.0/25 be mapped to available layer 4 ports on the IP addresses in the subnet
216.52.8.32/28:
configure nat add out_vlan_2 map source 192.168.2.0/25 to 216.52.8.32 /28 both portmap
The following command defines a portmap translation rule that specifies that only TCP traffic from
subnet 102.168.2.0/25 be mapped to layer 4 ports in the range of 1024-8192 on the IP addresses in the
subnet 216.52.8.32/28:
configure nat add out_vlan_2 map source 192.168.2.128/25 to 216.52.8.64/28 tcp portmap
1024 - 8192
The following command specifies an auto constrain NAT translation rule that applies to both TCP and
UDP traffic:
configure nat add out_vlan_3 map source 192.168.3.0/24 to 216.52.8.64/32 both
auto-constrain
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a NAT translation rule.
Syntax Description
Default
N/A.
Usage Guidelines
To delete all NAT rules, use the all keyword. To delete a specific NAT rule, you must use exactly the
same parameters that you used to create the rule.
Example
The following command deletes a portmap translation rule:
configure nat delete out_vlan_2 map source 192.168.2.128/25 to 216.52.8.64/28 tcp
portmap 1024 - 8192
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for a TCP session that has been torn down or reset.
Syntax Description
seconds Specifies the number of seconds to wait before the session table entry times
out.
Default
Default timeout is 60 seconds.
Usage Guidelines
Setting the timeout to zero specifies that session table entries should not be timed-out. This is not
normally recommended as NAT resources will get used up.
Example
The following command configures the timeout for a reset or torn-down TCP session to 120 seconds:
configure nat finrst-timeout 120
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for an ICMP packet.
Syntax Description
seconds Specifies the number of seconds to wait before the session table entry times
out.
Default
Default timeout is 3 seconds.
Usage Guidelines
Setting the timeout to zero specifies that session table entries should not be timed-out. This is not
normally recommended as NAT resources will get used up.
Example
The following command configures the timeout for an ICMP packet to 5 seconds:
configure nat icmp-timeout 5
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for an entry with an unacknowledged TCP SYN state.
Syntax Description
seconds Specifies the number of seconds to wait before the session table entry times
out.
Default
Default timeout is 60 seconds.
Usage Guidelines
Setting the timeout to zero specifies that session table entries should not be timed-out. This is not
normally recommended as NAT resources will get used up.
Example
The following command configures the timeout for a session with an unacknowledged SYN packet to
120 seconds:
configure nat syn-timeout 120
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for a fully setup TCP SYN session.
Syntax Description
seconds Specifies the number of seconds to wait before the session table entry times
out.
Default
Default timeout is 120 seconds.
Usage Guidelines
Setting the timeout to zero specifies that session table entries should not be timed-out. This is not
normally recommended as NAT resources will get used up.
Example
The following command configures the timeout for a TCP session to 90 seconds:
configure nat tcp-timeout 90
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for any IP packet that is not TCP, UDP, or ICMP.
Syntax Description
seconds Specifies the number of seconds to wait before the session table entry times
out.
Default
Default timeout is 600 seconds.
Usage Guidelines
Setting the timeout to zero specifies that session table entries should not be timed-out. This is not
normally recommended as NAT resources will get used up.
Example
The following command configures the timeout for packets other than TCP, UDP, or ICMP to 240
seconds:
configure nat timeout 240
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout for a UDP session.
Syntax Description
seconds Specifies the number of seconds to wait before the session table entry times
out.
Default
Default timeout is 120 seconds.
Usage Guidelines
Setting the timeout to zero specifies that session table entries should not be timed-out. This is not
normally recommended as NAT resources will get used up.
Example
The following command configures the timeout for a UDP session to 90 seconds:
configure nat udp-timeout 90
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a VLAN to participate in NAT.
Syntax Description
Default
N/A.
Usage Guidelines
When a VLAN is configured to be inside, traffic from that VLAN is translated only if it has a matching
NAT rule. Any unmatched traffic will be routed normally and not be translated. When a VLAN is
configured to be outside, it routes all traffic.
Because all traffic runs through the central processing unit (CPU), it cannot run at line-rate.
Normally, outside traffic will be able to initiate connections to the internal private IP addresses. If you
want to prevent this, you can create IP and ICMP access-lists on the outside VLAN ports to deny traffic
destined for the inside IP addresses. There is a NAT performance penalty when you do this.
When a VLAN is configured to be none, all NAT functions are disabled and the VLAN operates
normally.
Example
The following command configures the VLAN out_vlan_1 as an outside VLAN for use with NAT:
configure nat vlan out_vlan_1 outside
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable nat
disable nat
Description
Disables network address translation on the switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following command disables NAT functionality on the switch:
disable nat
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable nat
enable nat
Description
Enables network address translation on the switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following command enables NAT functionality on the switch:
enable nat
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show nat
show nat {timeout | stats | connections | rules {vlan <outside_vlan>}}
Description
Displays NAT settings.
Syntax Description
Default
Displays all NAT settings.
Usage Guidelines
Use the keyword stats to display statistics for the NAT traffic, including:
• The number of rules
• The number of current connections
• The number of translated packets on the inside and outside VLANs
• Information on missed translations
Use the keyword connections to display the current NAT connection table, including source IP/layer 4
port mappings from inside to outside.
Use the keyword rules to display the NAT translation rules for the outside VLANs configured on the
switch. Rules are displayed in the order they are processed, starting with the first one. To display the
NAT rules for a specific VLAN, add the VLAN name.
Use the keyword timeout to display the NAT timeout settings configured on the switch.
Example
The following command shows the NAT translation rules configured for VLAN out_vlan_1:
show nat rules vlan out_vlan_1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
This chapter describes commands for configuring and managing the Event Management
System/Logging.
When an event occurs on a switch, the Event Management System (EMS) allows you to send messages
generated by these events to a specified log target. You can send messages to the memory buffer,
NVRAM, the console display, the current session, or to a syslog host. The log messages contain
configuration and fault information pertaining to the device. The log messages can be formatted to
contain various items of information, but typically a message will consist of:
• Timestamp: The timestamp records when the event occurred.
• Severity level:
— Critical: A desired switch function is inoperable. The switch may need to be reset.
— Error: A problem is interfering with normal operation.
— Warning: An abnormal condition exists that may lead to a function failure.
— Notice: A normal but significant condition has been detected; the system is functioning as
expected.
— Info: Actions and events that are consistent with expected behavior.
— Debug-Summary, Debug-Verbose, and Debug -Data: Information that is useful when performing
detailed trouble shooting procedures.
By default, log entries that are assigned a critical, error, or warning level are considered static entries
and remain in the NVRAM log target after a switch reboot.
• Component: The component refers to the specific functional area to which the error refers.
• Message: The message contains the log information with text that is specific to the problem.
The switch maintains a configurable number of messages in its internal (memory-buffer) log (1000 by
default). You can display a snapshot of the log at any time. In addition to viewing a snapshot of the log,
you can configure the system to maintain a running real-time display of log messages on the console
display or telnet session. In addition to maintaining an internal log, the switch supports remote logging
by way of the UNIX syslog host facility.
clear counters
clear counters
Description
Clears all switch statistics and port counters, including port packet statistics, bridging statistics, IP
statistics, log event counters, and MPLS statistics.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
You should view the switch statistics and port counters before you clear them. Use the show port
command to view port statistics. Use the show log counters command to show event statistics.
Viewing and maintaining statistics on a regular basis allows you to see how well your network is
performing. If you keep simple daily records, you will see trends emerging and notice problems arising
before they cause major network faults. By clearing the counters, you can see fresh statistics for the time
period you are monitoring.
Example
The following command clears all switch statistics and port counters:
clear counters
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
clear log
clear log {diag-status | static | messages [memory-buffer | nvram]}
Description
Clears the log database.
Syntax Description
Default
N/A.
Usage Guidelines
The switch log tracks configuration and fault information pertaining to the device.
By default, log entries that are sent to the NVRAM remain in the log after a switch reboot. The clear
log and clear log messages memory-buffer commands remove entries in the memory buffer target;
the clear log static and clear log messages nvram commands remove messages from the
NVRAM target as well as the memory buffer target.
When there is a hardware failure, a hardware error code might be saved to the FLASH or NVRAM
(depending on the switch configuration). Upon reboot, the switch will not try to bring up a card with
an error code, so it will be shown in a failed state. Use the clear log diag-status command to clear
the hardware error code, so the module can be brought up after the next reboot. This command clears
the state for all the modules.
Example
The following command clears all log messages, from the NVRAM:
clear log static
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Clears the incident counters for events.
Syntax Description
Default
If severity is not specified, then the event counters of any severity are cleared in the specified
component.
Usage Guidelines
This command sets the incident counters to zero for each event specified. To display event counters, use
the following command:
show log counters
See the command show log on page 360 for more information about severity levels.
To get a listing of the event conditions in the system, use the following command:
To get a listing of the components present in the system, use the following command:
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the real-time log display.
Syntax Description
severity Specifies a message severity. Severities include critical, error, warning, notice,
info, debug-summary, debug-verbose, and debug-data.
Default
If not specified, messages of all severities are displayed on the console display.
Usage Guidelines
You must enable the log display before messages are displayed on the log display. Use the enable log
display command to enable the log display. This allows you to configure the system to maintain a
running real-time display of log messages on the console.
This command is being replace by a command that has the ability to control logging to different targets
was introduced. The new command equivalent to configure log display is the following:
To display the current configuration of the log display, use the following command:
show log configuration target console-display
Example
The following command configures the system log to maintain a running real-time display of log
messages of critical severity:
configure log display critical
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a log filter by adding or deleting a specified set of events.
Syntax Description
Default
If the exclude keyword is not used, the events will be included by the filter. If severity is not
specified, then the filter will use the component default severity threshold (see the note on on page 321
when delete or exclude is specified).
Usage Guidelines
This command controls the incidents that pass a filter by adding, or deleting, a specified set of events. If
you want to configure a filter to include or exclude incidents based on event parameter values (for
example, MAC address) see the command configure log filter events match on page 323.
When the add keyword is used, the specified event name, or set of events described by component and
severity value, is added to the beginning of the filter item list maintained for this filter. The new filter
item either includes the events specified, or if the exclude keyword is present, excludes the events
specified.
The delete keyword is used to remove events from the filter item list that were previously added using
the add command. All filter items currently in the filter item list that are identical to, or a subset of, the
set of events specified in the delete command will be removed.
Event Filtering Process. From a logical standpoint, the filter associated with each enabled log target
is examined to determine whether a message should be logged to that particular target. The
determination is made for a given filter by comparing the incident with the most recently configured
filter item first. If the incident matches this filter item, the incident is either included or excluded,
depending on whether the exclude keyword was used. Subsequent filter items on the list are compared
if necessary. If the list of filter items has been exhausted with no match, the incident is excluded.
Severity Levels. When an individual event name is specified following the events keyword, no
severity value is needed since each event has pre-assigned severity. When a component, subcomponent,
or the all keyword is specified following the events keyword, a severity value is optional. If no
severity is specified, the severity used for each applicable subcomponent is obtained from the
pre-assigned severity threshold levels for those subcomponents. For example, if STP were specified as
the component, and no severity is specified for the add of an include item, then only messages with
severity of error and greater would be passed, since the threshold severity for the STP component is
error. If STP.InBPDU were specified as the component, and no severity is specified, then only messages
with severity of warning and greater would be passed, since the threshold severity for the STP.InPBDU
subcomponent is warning. Use the show log components command to see this information.
The severity keyword all can be used as a convenience when delete or exclude is specified. The use
of delete (or exclude) with severity all deletes (or excludes) previously added events of the same
component of all severity values.
NOTE
If no severity is specified when delete or exclude is specified, severity all is used
If the only keyword is present following the severity value, then only the events in the specified
component at that exact severity are included. Without the only keyword, events in the specified
component at that severity or more urgent are included. For example, using the option severity
warning implies critical, error, or warning events, whereas the option severity warning only implies
warning events only. Severity all only is not a valid choice.
Any EMS events with severity debug-summary, debug-verbose, or debug-data will not be logged
unless debug mode is enabled
Filter Optimization. Each time a configure log filter command is issued for a given filter name,
the events specified are compared against the current configuration of the filter to try to logically
simplify the configuration.
More Information. See the command show log on page 360 for more information about severity
levels.
To get a listing of the components present in the system, use the following command:
Example
The following command adds all events in the STP.InBPDU component at severity info to the filter
mySTPFilter:
configure log filter myStpFilter add events stp.inbpdu severity info
The following command adds events in the STP.OutBPDU component, at the pre-defined severity level
for that component, to the filter myStpFilter:
configure log filter myStpFilter add events stp.outbpdu
The following command excludes one particular event, STP.InBPDU.Drop, from the filter:
configure log filter myStpFilter add exclude events stp.inbpdu.drop
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a log filter by adding or deleting a specified set of events and specific set of match
parameter values.
Syntax Description
Default
If the exclude keyword is not used, the events will be included by the filter. If severity is not
specified, then the filter will use the component default severity threshold (see the note on on page 321
when delete or exclude is specified).
Usage Guidelines
This command controls the incidents that pass a filter by adding, or deleting, a specified set of events
that match a list of <type> <value> pairs. This command is an extension of the command configure
log filter events, and adds the ability to filter incidents based on matching specified event
parameter values to the event.
See the configure log filter events command on page 320 for more information on specifying and
using filters, on event conditions and components, on the details of the filtering process. The discussion
here is about the concepts of matching <type> <value> pairs to more narrowly define filters.
Types and Values. Each event in ExtremeWare is defined with a message format and zero or more
parameter types. The show log events detail command on page 373 can be used to display event
definitions (the event text and parameter types). The <value> depends on the parameter type specified.
As an example, an event may contain a physical port number, a source MAC address, and a destination
MAC address. To allow only those incidents with a specific source MAC address, use the following in
the command:
configure log filter myFilter add events bridge severity notice match source
mac-address 00:01:30:23:C1:00
The string type is used to match a specific string value of an event parameter, such as a user name. A
string can be specified as a simple regular expression.
Match Versus Strict-Match. The match and strict-match keywords control the filter behavior for
incidents whose event definition does not contain all the parameters specified in a configure log
filter events match command. This is best explained with an example. Suppose an event in the
XYZ component, named XYZ.event5, contains a physical port number, a source MAC address, but no
destination MAC address. If you configure a filter to match a source MAC address and a destination
MAC address, XYZ.event5 will match the filter when the source MAC address matches regardless of the
destination MAC address, since the event contains no destination MAC address. If you specify the
strict-match keyword, then the filter will never match, since XYZ.event5 does not contain the
destination MAC address.
In other words, if the match keyword is specified, an incident will pass a filter so long as all parameter
values in the incident match those in the match criteria, but all parameter types in the match criteria
need not be present in the event definition.
And Keyword. Use the and keyword to specify multiple parameter type/value pairs that must match
those in the incident. For example, to allow only those events with specific source and destination MAC
addresses, use the following command:
configure log filter myFilter add events bridge severity notice match source
mac-address 00:01:30:23:C1:00 and destination mac-address 01:80:C2:00:00:02
Multiple Match Commands. Multiple configure log add events match commands are logically ORed
together. For example, the following commands define a filter that allows layer 2 bridging incidents
with a source MAC address of one of three possible values:
create log filter bridgeFilter
configure log bridgeFilter add events bridge severity notice match source mac-address
00:11:12:13:14:15
configure log bridgeFilter add events bridge severity notice match source mac-address
00:21:22:23:24:25
configure log bridgeFilter add events bridge severity notice match source mac-address
00:31:32:33:34:35
In order to exclude only incidents whose parameter values match the specified criteria, follow this two
step process. First, include the applicable event(s) using either the configure log filter events
command, or using the configure log filter events match command described here, with a
superset of the match criteria. Second, use the exclude keyword in the configure log filter
events match command to exclude incidents with the specified parameter values.
Filter Optimization. As explained in the configure log filter events command, each time a
configure log filter match command is issued, an attempt is made to logically simplify the
configuration. This simplification extends to cases where one set of match criteria is a superset of
another.
More Information. See the command show log on page 360 for more information about severity
levels.
To get a listing of the components present in the system, use the following command:
Example
By default, all log targets are associated with the built-in filter, DefaultFilter. Therefore, the most
straightforward way to send additional messages to a log target is to modify DefaultFilter. In the
following example, the command modifies the built-in filter to allow incidents in the STP component,
and all subcomponents of STP, of severity critical, error, warning, notice and info. For any of these
events containing a physical port number as a match parameter, limit the incidents to only those
occurring on physical ports 3, 4 and 5:
configure log DefaultFilter add events stp severity info match ports 3-5
If desired, issue the unconfigure log DefaultFilter command to restore the DefaultFilter back to its
original configuration.
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Sets the severity level of an existing filter item.
Syntax Description
Default
N/A.
Usage Guidelines
This command modifies the severity level of an existing filter item describing a particular set of events.
Using this command is equivalent to deleting the filter item from the filter and then adding back a filter
item describing the same set of events with a different severity level. The command can only be used to
modify a filter item referring to a set of events with a severity level, as opposed to one that makes use
of only a single severity. It can be used to modify either “exclude” or “include” filter items.
Using the single command eliminates the possibility of missing an event of interest between the
separate delete and add commands.
Note that the severity of a filter item configured to include or exclude incidents based on event
parameter values can also be modified using the configure log filter set severity match
command on page 327.
See the command show log on page 360 for a detailed description of severity levels.
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Sets the severity level of an existing filter item.
Syntax Description
Default
N/A.
Usage Guidelines
This command modifies the severity level of an existing filter item describing a particular set of events
and the parameter values of the desired events. Using this command is equivalent to deleting the filter
item from the filter and then adding back a filter item describing the same set of events with a different
severity level. The command can only be used to modify a filter item referring to a set of events with a
severity level, as opposed to one that makes use of only a single severity. It can be used to modify either
“exclude” or “include” filter items.
For example, to change the severity level of the filter item added with this command:
configure log slbFilter2 add exclude events slb.conn severity notice match
source ipaddress 10.1.2.0/24
configure log slbFilter2 set severity info events events slb.conn match
source ipaddress 10.1.2.0/24
Using this single command is preferred to using a delete command followed by an add command:
configure log slbFilter2 delete exclude events slb.conn severity notice match
source ipaddress 10.1.2.0/24
configure log slbFilter2 add exclude events slb.conn severity info match
Using the single command eliminates the possibility of missing an event of interest between the
separate delete and add commands.
See the command show log on page 360 for a detailed description of severity levels.
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Associates a filter to a target.
Syntax Description
Default
If severity is not specified, the severity level for the target is left unchanged.
Usage Guidelines
This command associates the specified filter and severity with the specified target. A filter limits
messages sent to a target.
Although each target can be configured with its own filter, by default, all targets are associated with the
built-in filter, DefaultFilter. Each target can also be configured with its own severity level. This provides
the ability to associate multiple targets with the same filter, while having a configurable severity level
for each target.
A message is sent to a target if the target has been enabled, the message passes the associated filter, the
message is at least as severe as the configured severity level, and the message output matches the
regular expression specified. By default, the memory buffer and the NVRAM targets are enabled. For
other targets, use the command enable log target on page 355. Table 9 describes the default
characteristics of each type of target.
The built-in filter, DefaultFilter, and a severity level of info are used for each new telnet session. These
values may be overridden on a per-session basis using the configure log target filter command
and specify the target as session. Use the following form of the command for per-session configuration
changes:
configure log target session filter <filter name> {severity <severity> {only}}
Configuration changes to the current session target are in effect only for the duration of the session, and
are not saved in FLASH memory. The session option can also be used on the console display, if the
changes are desired to be temporary. If changes to the console-display are to be permanent (saved to
FLASH memory), use the following form of the command:
configure log target console-display filter <filter name> {severity <severity> {only}}
In other versions of ExtremeWare, so-called static messages with a severity level of warning and
above were stored in NVRAM so they would be available across a reboot. This remains the default
behavior for ExtremeWare releases, but message filtering for the NVRAM target is now configurable.
Example
The following command sends log messages to the previously syslog host at 10.31.8.25, port 8993, and
facility local3, that pass the filter myFilter and are of severity warning and above:
configure log target syslog 10.31.8.25:8993 local3 filter myFilter severity warning
The following command sends log messages to the current session, that pass the filter myFilter and are
of severity warning and above:
configure log target session filter myFilter severity warning
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the formats of the items that comprise a message, on a per-target basis.
Syntax Description
Default
The following defaults apply to console display, memory buffer, NVRAM, and session targets:
• timestamp—hundredths
• date—mm-dd-yyyy
• severity—on
• event-name—condition
• host-name—off
• priority—off
• tag-id—off
• tag-name—off
• sequence-number—off
• process-name—off
• process-id—off
• source-function—off
• source-line—off
• timestamp—seconds
• date—mmm-dd
• severity—on
• event-name—none
• host-name—off
• priority—on
• tag-id—off
• tag-name—on
• sequence-number—off
• process-name—off
• process-id—off
• source-function—off
• source-line—off
Usage Guidelines
This command configures the format of the items that make up log messages. You can choose to include
or exclude items and set the format for those items, but you cannot vary the order in which the items
are assembled.
When applied to the targets console-display or session, the format specified is used for the messages
sent to the console display or telnet session. Configuration changes to the session target, be it either a
telnet or console display target session, are in effect only for the duration of the session, and are not
saved in FLASH.
When this command is applied to the target memory-buffer, the format specified is used in subsequent
show log and upload log commands. The format configured for the internal memory buffer can be
overridden by specifying a format on the show log and upload log commands.
When this command is applied to the target syslog, the format specified is used for the messages sent
to the specified syslog host.
Timestamps. Timestamps refer to the time an event occurred, and can be output in either seconds as
described in RFC 3164 (for example, “13:42:56”), hundredths of a second (for example, “13:42:56.98”), or
suppressed altogether. To display timestamps as hh:mm:ss, use the seconds keyword, to display as
hh:mm:ss.HH, use the hundredths keyword, or to suppress timestamps altogether, use the none
keyword. Timestamps are displayed in hundredths by default.
Date. The date an event occurred can be output are described in RFC 3164. Dates are output in
different formats, depending on the keyword chosen. The following lists the date keyword options, and
how the date “March 26, 2003” would be output:
• Mmm-dd—Mar 26
• mm-dd-yyyy—03/26/2003
• dd-mm-yyyy—26-03-2003
• yyyy-mm-dd—2003-03-26
• dd-Mmm-yyyy—26-Mar-2003
Dates are suppressed altogether by specifying none. Dates are displayed as mm-dd-yyyy by default.
Severity. A four-letter abbreviation of the severity of the event can be output by specifying severity
on or suppressed by specifying severity off. The default setting is severity on. The abbreviations
are: Crit, Erro, Warn, Noti, Info, Summ, Verb, and Data. These correspond to: Critical, Error, Warning,
Notice, Informational, Debug-Summary, Debug-Verbose, and Debug-Data.
Event Names. Event names can be output as the component name only by specifying event-name
component, as component and subcomponent name by specifying event-name subcomponent, as
component and subcomponent name with condition mnemonic by specifying event-name condition,
or suppressed by specifying event-name none. The default setting is event-name condition to specify
the complete name of the events.
Host Name. The configured SNMP name of the switch can be output as HOSTNAME described in
RFC 3164 by specifying host-name on or suppressed by specifying host-name off. The default
setting is host-name off.
Tag ID. The (internal) ExtremeWare task identifiers of the applications detecting the events can be
output as the pid described in RFC 3164 by specifying tag-id on or suppressed by specifying tag-id
off. The default setting is tag-id off.
Tag Name. The component name used by the application when detecting the events can be output as
the TAG described in RFC 3164 by specifying tag-name on or suppressed by specifying tag-name off.
The default setting is tag-name off.
Sequence Number. Sequence numbers refer to the specific ordering of events as they occur, and can
be output as an ASCII decimal integer by specifying sequence-number on or suppressed by specifying
sequence-number off. The default setting is sequence-number off.
Process Name. For providing detailed information to technical support, the (internal) ExtremeWare
task names of the applications detecting the events can be displayed by specifying process-name on or
suppressed by specifying process-name off. The default setting is process-name off.
Process ID. For providing detailed information to technical support, the (internal) ExtremeWare task
identifiers of the applications detecting the events can be displayed by specifying process-id on or
suppressed by specifying process-id off. The default setting is process-id off.
Source Function. For providing detailed information to technical support, the names of the
application source functions detecting the events can be displayed by specifying source-function on
or suppressed by specifying source-function off. The default setting is source-function off.
Source Line. For providing detailed information to technical support, the application source file
names and line numbers detecting the events can be displayed by specifying source-line on or
suppressed by specifying source-line off. The default setting is source-line off.
Example
In the following example, the switch generates the identical event from the component SNTP, using
three different formats.
Using the default format for the session target, an example log message might appear as:
05/29/2003 12:15:25.00 <Warn:SNTP.RslvSrvrFail> The SNTP server parameter value
(TheWrongServer.example.com) can not be resolved.
If you set the current session format using the following command:
configure log target session format date mm-dd-yyy timestamp seconds event-name
component
In order to provide some detailed information to technical support, you set the current session format
using the following command:
configure log target session format date mmm-dd timestamp hundredths event-name
condition source-line on process-name on
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Associates a match expression to a target.
Syntax Description
Default
By default, targets do not have a match expression.
Usage Guidelines
This command configures the specified target with a match expression. The filter associated with the
target is not affected. A message is sent to a target if the target has been enabled, the message passes the
associated filter, the message is at least as severe as the configured severity level, and the message
output matches the regular expression specified.
See the command show log on page 360 for a detailed description of simple regular expressions. By
default, targets do not have a match expression.
Specifying any instead of match-expression effectively removes a match expression that had been
previously configured, causing any message to be sent that has satisfied all of the other requirements.
Example
The following command sends log messages to the current session, that pass the current filter and
severity level, and contain the string user5:
configure log target session match user5
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Sets the severity level of messages sent to the target.
Syntax Description
Default
By default, targets are sent messages of the following severity level and above:
• console display—info
• memory buffer—debug-data
• NVRAM—warning
• session—info
• syslog—debug-data
Usage Guidelines
This command configures the specified target with a severity level. The filter associated with the target
is not affected. A message is sent to a target if the target has been enabled, the message passes the
associated filter, the message is at least as severe as the configured severity level, and the message
output matches the regular expression specified.
See the command show log on page 360 for a detailed description of severity levels.
Example
The following command sends log messages to the current session, that pass the current filter at a
severity level of info or greater, and contain the string user5:
configure log target session severity info
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
configure sys-recovery-level
configure sys-recovery-level [none | [all | critical] [ reboot ]]
Description
Configures a recovery option for instances where an exception occurs in ExtremeWare.
Syntax Description
none Configures the level to no recovery. No action is taken when a task exception
occurs; there is no system shutdown or reboot.
all Configures ExtremeWare to log an error into the syslog and either shutdown
or reboot the system after any task exception occurs.
critical Configures ExtremeWare to log an error into the syslog and either shutdown
or reboot the system after a critical task exception.
reboot Reboots the switch.
Default
None.
Usage Guidelines
This command is used for system troubleshooting. If the system fails before the switch is booted up, the
switch will automatically start the console and allow access to the system to view the logs or debug the
failure. You can also configure the system to respond to software failures automatically. You must
specify one of the following parameters for the system to respond to software failures:
• none—No action is taken when a task exception occurs.
• all—The system will reboot or shut down if any task exception occurs.
• critical—The system will reboot or shutdown if a critical task exception occurs. Critical tasks
include the tBGTask, tNetTask, tEdpTask, and tESRPTask.
You must specify whether the system should shut down or reboot upon a task exception if the recovery
level is all or critical.
Example
The following command configures a switch to reboot after a critical task exception occurs:
configure sys-recovery-level critical reboot
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the remote syslog server host address, and filters messages to be sent to the remote syslog
target.
Syntax Description
host name/ip Specifies the remote syslog server host name or IP address.
udp-port Specifies the UDP port number for the syslog target.
local0 ... local7 Specifies the local syslog facility.
severity Specifies a message severity. Severities include critical, error, warning, notice,
info, debug-summary, debug-verbose, and debug-data.
Default
If a severity level is not specified, all messages are sent to the remote syslog server target. If UDP port is
not specified, 514 is used.
Usage Guidelines
Options for configuring the remote syslog server include:
• host name/ip—The name or IP address of the remote syslog server host.
• udp-port—The UDP port
• facility—The syslog facility level for local use (local0– local7).
• severity—Filters the messages sent to the remote syslog server target to have the selected severity or
higher (more critical). Severities include critical, error, warning, notice, info, debug-summary,
debug-verbose, and debug-data.
The switch log overwrites existing log messages in a wrap-around memory buffer, which may cause
you to lose valuable information once the buffer becomes full. The remote syslog server does not
overwrite log information, and can store messages in non-volatile files (disks, for example).
The enable syslog command must be issued in order for messages to be sent to the remote syslog
server(s). Syslog is disabled by default. A total of four syslog servers can be configured at one time.
When a syslog server is added, it is associated with the filter DefaultFilter. Use the configure log
target filter command to associate a different filter.
The syslog facility level is defined as local0 – local7. The facility level is used to group syslog data.
Example
The following command configures the remote syslog server target with an critical severity:
configure syslog 123.45.67.78 local1 critical
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a remote syslog server address.
Syntax Description
host name/ip Specifies the remote syslog server host name or IP address.
udp-port Specifies the UDP port number for the syslog target.
local0 ... local7 Specifies the local syslog facility.
Default
If a UDP port number is not specified, 514 is used.
Usage Guidelines
This command is used to delete a remote syslog server target.
Example
The following command deletes the remote syslog server with an IP address of 10.0.0.1:
configure syslog delete 10.0.0.1 local1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Create a log filter with the specified name.
Syntax Description
Default
N/A.
Usage Guidelines
This command creates a filter with the name specified. A filter is a customizable list of events to include
or exclude, and optional parameter values. The list of events can be configured by component or
subcomponent with optional severity, or individual condition, each with optional parameter values. See
the commands configure log filter events and configure log filter events match for
details on how to add items to the filter.
The filter can be associated with one or more targets using the configure log target filter
command to control the messages sent to those targets. The system has one built-in filter named
DefaultFilter, which itself may be customized. Therefore, the create log filter command can be used
if a filter other than DefaultFilter is desired. As its name implies, DefaultFilter initially contains the
default level of logging in which every ExtremeWare component and subcomponent has a pre-assigned
severity level.
If another filter needs to be created that will be similar to an existing filter, use the copy option to
populate the new filter with the configuration of the existing filter. If the copy option is not specified,
the new filter will have no events configured and therefore no incidents will pass through it.
The total number of supported filters, including DefaultFilter, is 20.
Example
The following command creates the filter named fdb2, copying its configuration from the filter
DefaultFilter:
create log filter fdb2 copy DefaultFilter
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Delete a log filter with the specified name.
Syntax Description
Default
N/A.
Usage Guidelines
This command deletes the specified filter, or all filters except for the filter DefaultFilter. The specified
filter must not be associated with a target. To remove that association, associate the target with
DefaultFilter instead of the filter to be deleted, using the following command:
configure log target <target> filter DefaultFilter
Example
The following command deletes the filter named fdb2:
delete log filter fdb2
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
disable cli-config-logging
disable cli-config-logging
Description
Disables the logging of CLI configuration commands to the switch Syslog.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
The disable cli-config-logging command discontinues the recording of all switch configuration
changes and their sources that are made using the CLI via Telnet or the local console. After you disable
configuration logging, no further changes are logged to the system log.
To view the status of configuration logging on the switch, use the show management command. The
show management command displays information about the switch including the enable/disable state
for configuration logging.
Example
The following command disables the logging of CLI configuration command to the Syslog:
disable cli-config-logging
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables debug mode. The switch stops logging events of severity debug-summary, debug-verbose, and
debug-data.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command disables debug mode. Debug mode must be enabled prior to logging debug messages,
which can severely degrade performance. For typical network device monitoring, debug mode should
remain disabled, the default setting. Debug mode should only be enabled when advised by technical
support, or when advanced diagnosis is required. The debug mode setting is saved to FLASH.
Example
The following command disables debug mode:
disable log debug-mode
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the sending of messages to the console display.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command was available in other versions of ExtremeWare and has now been replaced. The new
command equivalent to disable log display is the following:
Example
The following command disables the log display:
disable log display
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on all platforms.
Description
Stop sending log messages to the specified target.
Syntax Description
Default
Enabled, for memory buffer and NVRAM; all other targets are disabled by default.
Usage Guidelines
This command stops sending messages to the specified target. By default, the memory buffer and the
NVRAM targets are enabled. Other targets must be enabled before messages are sent to those targets.
Configuration changes to the session target are in effect only for the duration of the console display or
telnet session, and are not saved in FLASH. Changes to the other targets are saved to FLASH.
In other versions of ExtremeWare, a similar command was used to disable displaying the log on the
console. That command:
disable log display
is equivalent to:
disable log target console-display
Example
The following command disables log messages to the current session:
disable log target session
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable rmon
disable rmon
Description
Disables the collection of RMON statistics on the switch.
Syntax Description
This command has no arguments or variables.
Default
By default, RMON is disabled. However, even in the disabled state, the switch responds to RMON
queries and sets for alarms and events.
Usage Guidelines
The switch supports four out of nine groups of Ethernet RMON statistics. In a disabled state, the switch
continues to respond to the following two groups:
• Alarms—The Alarms group provides a versatile, general mechanism for setting threshold and
sampling intervals to generate events on any RMON variable. Both rising and falling thresholds are
supported, and thresholds can be on the absolute value of a variable or its delta value. In addition,
alarm thresholds may be auto calibrated or set manually.
• Events—The Events group creates entries in an event log and/or sends SNMP traps to the
management workstation. An event is triggered by an RMON alarm. The action taken can be
configured to ignore it, to log the event, to send an SNMP trap to the receivers listed in the trap
receiver table, or to both log and send a trap. The RMON traps are defined in RFC 1757 for rising
and falling thresholds.
To view the status of RMON polling on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for
RMON polling.
Example
The following command disables the collection of RMON statistics on the switch:
disable rmon
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable syslog
disable syslog
Description
Disables logging to all remote syslog server targets.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Disables logging to all remote syslog server targets, not to the switch targets. This setting is saved in
FLASH, and will be in effect upon boot up.
Example
The following command disables logging to all remote syslog server targets:
disable syslog
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable cli-config-logging
enable cli-config-logging
Description
Enables the logging of CLI configuration commands to the Syslog for auditing purposes.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
ExtremeWare allows you to record all configuration changes and their sources that are made using the
CLI by way of Telnet or the local console. The changes are logged to the system log. Each log entry
includes the user account name that performed the changes and the source IP address of the client (if
Telnet was used). Configuration logging applies only to commands that result in a configuration
change.
To view the status of configuration logging on the switch, use the show management command. The
show management command displays information about the switch including the enable/disable state
for configuration logging.
Example
The following command enables the logging of CLI configuration commands to the Syslog:
enable cli-config-logging
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables debug mode. The switch allows debug events included in log filters to be logged.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command enables debug mode. Debug mode must be enabled prior to logging debug messages,
which can severely degrade performance. For typical network device monitoring, debug mode should
remain disabled, the default setting. Debug mode should only be enabled when advised by technical
support, or when advanced diagnosis is required. The debug mode setting is saved to FLASH.
Example
The following command enables debug mode:
enable log debug-mode
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables a running real-time display of log messages on the console display.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
If you enable the log display on a terminal connected to the console port, your settings will remain in
effect even after your console session is ended (unless you explicitly disable the log display).
You configure the messages displayed in the log using the configure log display, or configure log
target console-display commands.
This command was available in other versions of ExtremeWare and has now been replaced. The new
command equivalent to enable log display is the following:
To change the log filter association, severity threshold, or match expression for messages sent to the
console display, use the configure log target console-display command
Example
The following command enables a real-time display of log messages:
enable log display
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Start sending log messages to the specified target.
Syntax Description
Default
Enabled, for memory buffer and NVRAM; all other targets are disabled by default.
Usage Guidelines
This command starts sending messages to the specified target. By default, the memory-buffer and the
NVRAM targets are enabled. Other targets must be enabled before messages are sent to those targets.
Configuration changes to the session target are in effect only for the duration of the console display or
telnet session, and are not saved in FLASH. Others are saved in FLASH.
In earlier versions of ExtremeWare, a similar command was used to enable displaying the log on the
console. That command:
enable log display
is equivalent to:
enable log target console-display
Example
The following command enables log messages on the current session:
enable log target session
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
enable rmon
enable rmon
Description
Enables the collection of RMON statistics on the switch.
Syntax Description
This command has no arguments or variables.
Default
By default, RMON is disabled. However, even in the disabled state, the switch responds to RMON
queries and sets for alarms and events. By enabling RMON, the switch begins the processes necessary
for collecting switch statistics.
Usage Guidelines
The switch supports four out of nine groups of Ethernet RMON statistics. In an enabled state, the
switch responds to the following four groups:
• Statistics—The RMON Ethernet Statistics group provides traffic and error statistics showing packets,
bytes, broadcasts, multicasts, and errors on a LAN segment or VLAN.
• History—The History group provides historical views of network performance by taking periodic
samples of the counters supplied by the Statistics group. The group features user-defined sample
intervals and bucket counters for complete customization of trend analysis.
• Alarms—The Alarms group provides a versatile, general mechanism for setting threshold and
sampling intervals to generate events on any RMON variable. Both rising and falling thresholds are
supported, and thresholds can be on the absolute value of a variable or its delta value. In addition,
alarm thresholds may be auto calibrated or set manually.
• Events—The Events group creates entries in an event log and/or sends SNMP traps to the
management workstation. An event is triggered by an RMON alarm. The action taken can be
configured to ignore it, to log the event, to send an SNMP trap to the receivers listed in the trap
receiver table, or to both log and send a trap. The RMON traps are defined in RFC 1757 for rising
and falling thresholds.
NOTE
You can only use the RMON features of the system if you have an RMON management application and
have enabled RMON on the switch.
RMON requires one probe per LAN segment, and standalone RMON probes have traditionally been
expensive. Therefore, Extreme’s approach has been to build an inexpensive RMON probe into the agent
of each system. This allows RMON to be widely deployed around the network without costing more
than traditional network management. The switch accurately maintains RMON statistics at the
maximum line rate of all of its ports.
For example, statistics can be related to individual ports. Also, because a probe must be able to see all
traffic, a stand-alone probe must be attached to a nonsecure port. Implementing RMON in the switch
means that all ports can have security features enabled.
To view the status of RMON polling on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for
RMON polling.
Example
The following command enables the collection of RMON statistics on the switch:
enable rmon
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable syslog
enable syslog
Description
Enables logging to all remote syslog host targets.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
In order to enable remote logging, you must do the following:
• Configure the syslog host to accept and log messages.
• Enable remote logging by using the enable syslog command.
• Configure remote logging by using the configure syslog add command.
When you use the enable syslog command, the exporting process of the syslog begins. This command
also determines the initial state of an added remote syslog target.
Example
The following command enables logging to all remote syslog hosts:
enable syslog
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
show log
show log {messages [memory-buffer | nvram]} {severity <severity> {only}}
{starting [date <date> time <time> | date <date> | time <time>]} {ending
[date <date> time <time> | date <date> | time <time>]} {match
<match-expression>} {format <format>} {chronological}
Description
Displays the current log messages.
Syntax Description
messages Specifies the target location from which to display the log messages.
memory-buffer Show messages stored in volatile memory (default).
nvram Show messages stored in NVRAM.
severity Specifies the minimum severity level to display (if the keyword only is omitted).
only Specifies that only the specified severity level is to be displayed
starting Show messages with timestamps equal to or greater than that specified
date Specifies the date, where date is <month (1-12)> / <day> {/ <year (yyyy)>}.
time Specifies the time, where time is <hour (0-23)> {: <minute (0-59)> {:
<seconds> {. <hundredths>}}}
ending Show messages with timestamps equal to or less than that specified.
match-expression Specifies a regular expression. Only messages that match the regular
expression will be displayed.
format Specifies a format to use to override the format configured for the memory
buffer.
chronological Specifies displaying log messages in ascending chronological order (oldest to
newest).
Default
The following defaults apply:
• messages—memory buffer
• severity—none (displays everything stored in the target)
• starting, ending—if not specified, no timestamp restriction
• match—no restriction
• format—the format configured with the configure log target format command
• chronological—if not specified, show messages in order from newest to oldest
Usage Guidelines
Switch configuration and fault information is filtered and saved to target logs, in a memory buffer, and
in NVRAM. Each entry in the log contains the following information:
• Timestamp—records the month and day of the event, along with the time (hours, minutes, seconds,
and hundredths).
• Severity Level—indicates the urgency of a condition reported in the log. Table 10 describes the
severity levels assigned to events.
• Component, Subcomponent, and Condition Name—describes the subsystem in the software that
generates the event. This provides a good indication of where a fault might lie.
• Message—a description of the event occurrence. If the event was caused by a user, the user name is
also provided.
This command displays the messages stored in either the internal memory buffer or in NVRAM. The
messages shown can be limited by specifying a severity level, a time range, or a match expression.
Messages stored in the target have already been filtered as events occurred, and specifying a severity or
match expression on the show log command can only further limit the messages shown.
If the messages keyword is not present, the messages stored in the memory-buffer target are displayed.
Otherwise, the messages stored in the specified target are displayed.
If the only keyword is present following the severity value, then only the events at that exact severity
are included. Without the only keyword, events at that severity or more urgent are displayed. For
example, severity warning implies critical, error, or warning, whereas severity warning only implies
only warning.
Messages whose timestamps are equal or later than the starting time and are equal or earlier than the
specified ending time will be shown if they also pass the severity requirements and match expression, if
specified.
If the format phrase is specified, this format overrides the format already configured for the specified
log. See the command configure log target format on page 331 for more information on specifying
a format.
If a match phrase is specified, the formatted message must match the simple regular expression
specified by match-expression for it to be shown.
A simple regular expression is a string of single characters including the dot character (.), which are
optionally combined with quantifiers and constraints. A dot matches any single character while other
characters match only themselves (case is significant). Quantifiers include the star character (*) that
matches zero or more occurrences of the immediately preceding character or dot. Constraints include
the caret character (^) that matches at the beginning of a message, and the currency character ($) that
matches at the end of a message. Bracket expressions are not supported. There are a number of sources
available on the Internet and in various language references describing the operation of regular
expressions.
If the chronological keyword is specified, messages are shown from oldest to newest; otherwise,
messages are displayed newest to oldest.
Severity Level. The severity levels are critical, error, warning, notice, and info, plus three
severity levels for extended debugging, debug-summary, debug-verbose, and debug-data. In log
messages, the severity levels are shown by four letter abbreviations. The abbreviated forms are:
• Critical—Crit
• Error—Erro
• Warning—Warn
• Notice—Noti
• Info—Info
• Debug-Summary—Summ
• Debug-Verbose—Verb
• Debug-Data—Data
The three severity levels for extended debugging, debug-summary, debug-verbose, and debug-data,
require that debug mode be enabled (which may cause a performance degradation). See the command
enable log debug-mode on page 353.
Level Description
Critical A serious problem has been detected which is compromising the operation of the
system and that the system can not function as expected unless the situation is
remedied. The switch may need to be reset.
Error A problem has been detected which is interfering with the normal operation of the
system and that the system is not functioning as expected.
Warning An abnormal condition, not interfering with the normal operation of the system, has
been detected which may indicate that the system or the network in general may not
be functioning as expected.
Notice A normal but significant condition has been detected, which signals that the system is
functioning as expected.
Info (Informational) A normal but potentially interesting condition has been detected, which signals that the
system is functioning as expected and simply provides information or confirmation
about the condition.
Debug-Summary A condition has been detected that may interest a developer determining the reason
underlying some system behavior.
Debug-Verbose A condition has been detected that may interest a developer analyzing some system
behavior at a more verbose level than provided by the debug summary information.
Debug-Data A condition has been detected that may interest a developer inspecting the data
underlying some system behavior.
Log entries remain in the NVRAM log after a switch reboot. Issuing a clear log command does not
remove these static entries. To remove log entries from NVRAM, use the following command:
clear log messages nvram
Example
The following command displays messages with a critical severity:
show log critical
The following command displays messages with warning, error, or critical severity:
show log warning
The following command displays messages containing the string “port 2”:
show log match "port 2"
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to include the messages, severity, only, starting,
ending, chronological, match, and format options.
In ExtremeWare 7.3e, the Summit 300-48 replaced the priority keyword with the severity keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Display the name, description and default severity for all components.
Syntax Description
Default
N/A.
Usage Guidelines
This command displays the name, description, and default severity defined for the specified
components and subcomponents.
Example
The following command displays the log components:
show log components
The output produced by the show log components command is similar to the following:
show log components
Severity
Component Title Threshold
------------------- ---------------------------------------------- -------------
Bridge Layer 2 Bridging Error
Learning Layer 2 Bridge Learning Error
EAPS Ethernet Automatic Protection Switching (EAPS) Error
MSMFailover EAPS MSM Failover Error
SharedPort EAPS SharedPort Domain Error
EDP Extreme Discovery Protocol (EDP) Error
ELRP Extreme Loop Recovery Protocol (ELRP) Error
ESRP Extreme Standby Router Protocol (ESRP) Notice
Aware ESRP Aware Processing Notice
Message ESRP PDU Tx/Rx Error
MSMFailover ESRP MSM Failover Error
State ESRP State Transitions Notice
Tracking ESRP Tracking Error
FDB Forwarding Data Base Error
IP IP FDB Error
IPMC IP Multicast FDB Error
Replacement FDB Replacement Error
IGMP Internet Group Management Protocol Error
Snooping IGMP Snooping Error
IP N/A
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the log configuration, including the syslog host IP address, the priority level of messages being
logged locally, and the priority level of messages being sent to the syslog host.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This command displays the log configuration for all targets. The state of the target, enabled or disabled
is displayed. For the enabled targets, the associated filter, severity, match expression, and format is
displayed. The debug mode state of the switch is also displayed.
Example
The following command displays the configuration of all the log targets:
show log configuration
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the log configuration for the specified filter.
Syntax Description
Default
If no options are specified, the command displays the configuration for all filters.
Usage Guidelines
This command displays the configuration for filters.
Example
The following command displays the configuration for the filter, myFilter:
show log configuration filter myFilter
The above output shows two filter items. The first item excludes all events from the STP.OutBPDU
component. The second item includes the remaining events from the STP component. The severity
value is show as “-”, indicating that the component’s default severity threshold controls which
messages are passed.
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the log configuration for the specified target.
Syntax Description
Default
If no options are specified, the command displays the configuration for the current session and console
display.
Usage Guidelines
This command displays the log configuration for the specified target. The associated filter, severity,
match expression, and format is displayed.
Example
The following command displays the log configuration:
show log configuration target
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the incident counters for events.
Syntax Description
Default
If severity is not specified, then events of all severity are displayed. If detail is not specified, then
summary only information is displayed.
Usage Guidelines
This command displays the incident counters for each event specified. Two incident counters are
displayed. One counter displays the number of times an event has occurred, and the other displays the
number of times that notification for the event was made to the system (an incident record was injected
into the system for further processing). Both incident counters reflect totals accumulated since reboot or
since the counters were cleared using the clear log counters or clear counters command,
regardless of whether it was filtered or not.
This command also displays a reference count (the column titled Rf in the output). The reference count
is the number of enabled targets receiving notifications of this event.
See the command show log on page 360 for more information about severity levels.
To get a listing of the event conditions in the system, use the following command:
show log events
To get a listing of the components present in the system, use the following command:
show log components
Example
The following command displays the event counters for event conditions of severity debug-summary or
greater in the component STP.InBPDU:
show log counters stp.inbpdu severity debug-summary
The following command displays the event counters for the event condition PDUDrop in the component
STP.InBPDU:
show log counters "STP.InBPDU.PDUDrop"
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays information about the individual events (conditions) that can be logged.
Syntax Description
Default
If severity is not specified, then events of all severity are displayed. If detail is not specified, then
summary only information is displayed.
Usage Guidelines
This command displays the mnemonic, message format, severity, and parameter types defined for each
condition in the event set specified.
See the command show log on page 360 for more information about severity levels.
When the detail option is specified, the message format is displayed for the event conditions specified.
The message format parameters are replaced by the value of the parameters when the message is
generated.
To get a listing of the components present in the system, use the following command:
Example
The following command displays the event conditions of severity debug-summary or greater in the
component STP.InBPDU:
show log events stp.inbpdu severity debug-summary
The following command displays the details of the event condition PDUTrace in the component
STP.InBPDU:
show log events stp.inbpdu.pdutrace detail
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show memory
show memory {detail}
Description
Displays the current system memory information.
Syntax Description
Default
N/A.
Usage Guidelines
Your Summit switch must have 32MB of DRAM to support the features in ExtremeWare version 4.0 and
above.
Viewing statistics on a regular basis allows you to see how well your network is performing. If you
keep simple daily records, you will see trends emerging and notice problems arising before they cause
major network faults. This way, statistics can help you get the best out of your network.
The show memory command displays the following information in a tabular format:
• System memory information including the total DRAM size of your system.
• Current memory (both free and allocated memory) used by the system and the users.
• Cumulative memory (both free and allocated memory) used by the users.
• Software packet memory statistics including the type of packet, the number of allocated and free
packets, the number of packet failures, and data and other blocks.
• Memory utilization statistics including the total blocks of memory available and the memory being
used on your system. You can review how your memory is being utilized For example you can view
memory utilization for the system, management, ESRP, IP, and other system functions.
This information may be useful for your technical support representative if you experience a problem.
Depending on the software version running on your switch, additional or different memory information
may be displayed.
Example
The following command displays current system memory information:
show memory
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays real-time receive error statistics.
Syntax Description
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more ports numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
If you do not specify a port number or range of ports, receive error statistics are displayed for all ports.
This status information may be useful for your technical support representative if you have a network
problem.
• Receive Frames Lost (RX Lost)—The total number of frames received by the port that were lost
because of buffer overflow in the switch.
Example
The following command displays receive error statistics for ports 1 through 3:
show ports 1-3 rxerrors
===============================================================================
=====Link Status: A-Active R-Ready D-Disabled NP-Not Present LB-Loopback
0->Clear Counters U->page up D->page down ESC->exit
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to add support for management ports.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays real-time port statistics.
Syntax Description
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5, 1:5,
1:6-1:8.
vlan name Specifies a VLAN name.
cable-diagnostics Specifies that cable diagnostics information should be shown for the specified
port(s).
Default
N/A.
Usage Guidelines
If you do not specify a port number or range of ports, statistics are displayed for all ports.
Jumbo frame statistics are displayed for switches that are configured for jumbo frame support.
This status information may be useful for your technical support representative if you have a network
problem.
• Received Broadcast (RX Bcast)—The total number of frames received by the port that are addressed
to a broadcast address.
• Received Multicast (RX Mcast)—The total number of frames received by the port that are addressed
to a multicast address.
Example
The following command displays port statistics for a Summit 300-24:
show ports stats
Port Statistics Sun Sep 12 14:56:09 2004
Port Link Tx Pkt Tx Byte Rx Pkt Rx Byte Rx
Status Count Count Count Count Bcast
================================================================================
1 A 3587087 2077645883 2085802 188073946 79614
2 A 3169114 2510839136 1605196 613374716 40305
3 R 0 0 0 0 0
4 A 3102109 2036444975 1483625 124105390 15517
5 A 3057351 2023953061 1458344 119777971 17790
6 A 2883291 2007803014 2271624 1186338727 12448
7 R 0 0 0 0 0
8 R 0 0 0 0 0
9 R 0 0 0 0 0
10 R 0 0 0 0 0
11 R 0 0 0 0 0
12 R 0 0 0 0 0
13 R 0 0 0 0 0
15 R 0 0 0 0 0
16 R 0 0 0 0 0
17 R 0 0 0 0 0
18 R 0 0 0 0 0
19 R 0 0 0 0 0
20 R 0 0 0 0 0
21 R 0 0 0 0 0
22 R 0 0 0 0 0
23 R 0 0 0 0 0
24 R 0 0 0 0 0
25 A 7546549 2148548762 8041387 2932084477 677836
26 R 0 0 0 0 0
0
================================================================================
======Link Status: A-Active R-Ready D-Disabled NP-Not Present LB-Loopback
0->Clear Counters U->page up D->page down ESC->exit
The following command displays cable diagnostics information for all ports:
show ports stats cable-diagnostics
The output produced by the show ports stats cable-diagnostics command is similar to the
following:
1:4 R 0 0 0 0
1:5 R 10 8 2 0
1:6 A 0 0 0 0
1:7 R 0 0 0 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays real-time transmit error statistics.
Syntax Description
mgmt Specifies the management port. Supported only for switches that provide a
management port, such as the Summit 400.
portlist Specifies one or more ports numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
If you do not specify a port number or range of ports, error statistics are displayed for all ports.
This status information may be useful for your technical support representative if you have a network
problem.
Example
The following command displays transmit error statistics for ports 1 through 3:
The output produced by the show ports txerrors command is similar to the following:
================================================================================
Link Status: A-Active R-Ready D-Disabled NP-Not Present LB-Loopback
0->Clear Counters U->page up D->page down ESC->exit
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show version
show version {detail}
Description
Displays the hardware serial numbers and versions, and software versions currently running on the
switch.
Syntax Description
Default
N/A.
Usage Guidelines
The following is an example of the type of information displayed when you execute the show version
command:
• System Serial Number—A collection of numbers and letters that make up the serial number of the
switch.
• CPU Serial Number—A collection of numbers and letters that make up the serial number of the CPU
running in the switch. A rev number may also be listed.
• Image—The ExtremeWare software version currently running on the switch. If you have two
software images downloaded on the switch, only the currently running ExtremeWare version
information is displayed. The information displayed includes the version number, build number, and
the software build date.
• BootROM—The BootROM version currently running on the switch.
If you use the detail option you might also see the following:
• Platform Name—The name of the system, inserted before the Serial Number in the display.
Example
The following command displays the hardware and software versions currently running on the switch:
show version
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the detail option.
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the log filter to its default values; removes all filter items.
Syntax Description
Default
N/A.
Usage Guidelines
If the filter name specified is DefaultFilter, this command restores the configuration of DefaultFilter back
to its original settings.
If the filter name specified is not DefaultFilter, this command sets the filter to have no events configured
and therefore, no incidents will pass. This is the configuration of a newly created filter that was not
copied from an existing one.
See the delete log filter command for information about deleting a filter.
Example
The following command sets the log filter myFilter to stop passing any events:
unconfigure log filter myFilter
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the log target format to its default values.
Syntax Description
Default
When a target format is unconfigured, it is reset to the default values.
The following defaults apply to console display, memory buffer, NVRAM, and session targets:
• timestamp—hundredths
• date—mm-dd-yyyy
• severity—on
• event-name—condition
• host-name—off
• priority—off
• tag-id—off
• tag-name—off
• sequence-number—off
• process-name—off
• process-id—off
• source-function—off
• source-line—off
• timestamp—seconds
• date—mmm-dd
• severity—on
• event-name—none
• host-name—off
• priority—on
• tag-id—off
• tag-name—on
• sequence-number—off
• process-name—off
• process-id—off
• source-function—off
• source-line—off
Usage Guidelines
Use this command to reset the target format to the default format.
Example
The following command sets the log format for the target session (the current session) to the default:
unconfigure log target session format
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
upload log
upload log <host name/ip> <filename> {messages [memory-buffer | nvram]}
{severity <severity> {only}} {starting [date <date> time <time> | date
<date> | time <time>]} {ending [date <date> time <time> | date <date> |
time <time>]} {match <match-expression>} {format <format>} {chronological}
Description
Uploads the current log messages to a TFTP server.
Syntax Description
Default
The following defaults apply:
• messages—memory buffer
• severity—none (displays everything stored in the target)
• starting, ending—if not specified, no timestamp restriction
• match—no restriction
• format—the format configured with the configure log target format command
• chronological—if not specified, show messages in order from newest to oldest
Usage Guidelines
This command is similar to the show log command, but instead of displaying the log contents on the
command line, this command saves the log to a file on the TFTP server you specify. For more details on
most of the options of this command, see the command show log on page 360, and for the format
option see the command configure log target format on page 331.
Example
The following command uploads messages with a critical severity to the filename switch4critical.log on
TFTP server at 10.31.8.25:
upload log 10.31.8.25 switch4critical.log critical
The following command uploads messages with warning, error, or critical severity to the filename
switch4warn.log on TFTP server at 10.31.8.25:
upload log 10.31.8.25 switch4warn.log warning
The following command uploads messages starting August 1, ending August 31, containing the string
“port 2” in order of oldest to newest to the filename switch4aug03.log on TFTP server at 10.31.8.25:
upload log 10.31.8.25 switch4aug03.log starting date 8/1 ending date 8/31 match "port
2"
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Access policies are a generalized category of features that impact forwarding and route forwarding
decisions. Access policies are used primarily for security and quality of service (QoS) purposes.
IP access lists (also referred to as Access Lists or ACLs) consist of IP access rules and are used to perform
packet filtering and forwarding decisions on incoming traffic. Each packet arriving on an ingress port is
compared to the access list in sequential order and is either forwarded to a specified QoS profile or
dropped. Using access lists has no impact on switch performance.
Access lists are typically applied to traffic that crosses layer 3 router boundaries, but it is possible to use
access lists within a layer 2 VLAN. Extreme products are capable of performing this function with no
additional configuration.
Routing access policies are used to control the advertisement or recognition of routing protocols, such as
RIP, or OSPF. Routing access policies can be used to ‘hide’ entire networks or to trust only specific
sources for routes or ranges of routes. The capabilities of routing access policies are specific to the type
of routing protocol involved, but are sometimes more efficient and easier to implement than access lists.
SSH
Secure Shell 2 (SSH2) is a feature of ExtremeWare that allows you to encrypt session data between a
network administrator using SSH2 client software and the switch, or to send encrypted data from the
switch to an SSH2 client on a remote system. Image and configuration files may also be transferred to
the switch using the Secure Copy Program 2 (SCP2)
User Authentication
Remote Authentication Dial In User Service (RADIUS, RFC 2138) is a mechanism for authenticating and
centrally administrating access to network nodes. The ExtremeWare RADIUS client implementation
allows authentication for Telnet, Vista, or console access to the switch.
Extreme switches are also capable of sending RADIUS accounting information. You can configure
RADIUS accounting servers to be the same as the authentication servers, but this is not required.
Terminal Access Controller Access Control System Plus (TACACS+) is a mechanism for providing
authentication, authorization, and accounting on a centralized server, similar in function to the RADIUS
client. The ExtremeWare version of TACACS+ is used to authenticate prospective users who are
attempting to administer the switch. TACACS+ is used to communicate between the switch and an
authentication database.
NOTE
You cannot use RADIUS and TACACS+ at the same time.
Network Login
Network Login is a feature designed to control the admission of user packets into a network by giving
network access only to users that have been properly authenticated. Network Login is controlled by an
administrator on a per port, per VLAN basis and uses an integration of DHCP, user authentication over
the web interface or 802.1x client software, and, a RADIUS server to provide a user database or specific
configuration details.
Denial of Service
You can configure ExtremeWare to protect your Extreme switches in the event of a denial of service
attack. During a typical denial of service attack, the CPU on the switch gets flooded with packets from
multiple attackers, potentially causing the switch to fail. To protect against this type of attack, you can
configure the software so that when the number of packets received is more than the configured
threshold limit of packets per second, then a specific type of traffic on the port is blocked.
The unified structure simplifies security policies without compromising protection and provides the
following benefits:
• Single user experience — Same authentication procedures for wired and wireless users
• Unified management — Single management platform for wired and wireless networks
• Unified configuration — Consistent CLI for wired and wireless functions
• Single authentication infrastructure — Single set of policies, RADIUS, and certificate servers
Description
Clears and initializes the Network Login sessions on a VLAN port.
Syntax Description
Default
None.
Usage Guidelines
Clear the states of every MAC learned on this VLAN port and put the port back to unauthenticated
state. The port will be moved to its original VLAN if configured in Campus mode.
Example
The following example clears the Network Login state of port 9 in VLAN corp:
clear netlogin state port 9 vlan corp
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Initialize/Reset the Network Login sessions for a specified supplicant.
Syntax Description
Default
N/A.
Usage Guidelines
This command is essentially equivalent to a particular supplicant logging out. The MAC address will be
cleared from the FDB, the port is put back to its original VLAN (for Campus mode), and the port state
is set to unauthenticated, if this was the last authenticated MAC on this port.
Example
The following example resets the Network Login session for the supplicant with the MAC address of
00:e0:18:01:32:1f:
clear netlogin state mac-address 00:e0:18:01:32:1f
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds an entry to the access profile.
Syntax Description
Default
N/A.
Usage Guidelines
You can specify the sequence number for each access profile entry. If you do not specify a sequence
number, entries are sequenced in the order they are added. Each entry is assigned a value of 5 more
than the sequence number of the last entry.
The explicit sequence number and the permit or deny attribute should be specified if the access profile
mode is none.
The subnet mask specified in the access profile command is interpreted as a reverse mask. A reverse
mask indicates the bits that are significant in the IP address. In other words, a reverse mask specifies the
part of the address that must match the IP address to which the profile is applied.
The as-path keyword uses a regular expression string to match against the AS path. Regular expression
notation can include any of the characters listed in Table 16.
Character Definition
N AS number
N1 - N2 Range of AS numbers, where N1 and N2 are AS numbers and N1 < N2
[Nx ... Ny] Group of AS numbers, where Nx and Ny are AS numbers or a range of AS
numbers
[^Nx ... Ny] Any AS numbers other than the ones in the group
. Matches any number
^ Matches the beginning of the AS path
$ Matches the end of the AS path
– Matches the beginning or end, or a space
- Separates the beginning and end of a range of numbers
* Matches 0 or more instances
+ Matches 1 or more instances
? Matches 0 or 1 instance
{ Start of AS SET segment in the AS path
} End of AS SET segment in the AS path
( Start of a confederation segment in the AS path
) End of a confederation segment in the AS path
Example
The following command adds an IP subnet address to access profile nosales, as the next available entry:
configure access-profile nosales add ipaddress 10.1.33.0/24
The following command configures the access profile AS1 to permit AS paths beginning with AS
number 1, followed by any AS number from 2 - 8, and ending with either AS number 11, 13, or 15:
configure access-profile AS1 add 15 permit as-path “^1 2-8 [11 13 15]$”
History
This command was introduced in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support for the AS-path, ipxnet andipxsap.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes an access profile entry using the sequence number.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the entry with sequence number 15 from the access profile AS1:
configure access-profile AS1 delete 15
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the access profile mode to permit or deny access, or to require per-entry access control.
Syntax Description
Default
Permit.
Usage Guidelines
The access list mode determines whether the items in the list are to be permitted access or denied
access.
Example
The following command configures the access profile no_subnet_33 to deny access:
configure access-profile no_subnet_33 mode deny
The following command specifies that the access profile no_subnet_33 uses per-entry access control:
configure access-profile no_subnet_33 mode none
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures to authenticate all management sessions through RADIUS servers.
Syntax Description
Default
Uses RADIUS for authentication for management sessions. If RADIUS is not enabled, TACACS+ servers
are used. If neither RADIUS or TACACS+ servers are configured, local authentication is used.
Usage Guidelines
Use this command to authenticate all the management sessions through RADIUS servers. The RADIUS
server should be configured before using this command. This command fails is the primary and
secondary RADIUS servers are not configured.
The following types of management sessions can be configured:
• Telnet
• SSH
• Console
• HTTP
If you are using RADIUS authentication servers, you should only use RADIUS accounting servers for
accounting management sessions. RADIUS authentication servers should be configured before
configuring RADIUS accounting servers for management sessions.
Example
In the following example, management sessions are configured for RADIUS:
configure auth mgmt-access radius primary 192.168.14.12 secondary 192.168.14.55
In the following example, managements sessions are configured for RADIUS accounting:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures to authenticate all management sessions through TACACS+ servers.
Syntax Description
Default
Uses RADIUS for authentication for management sessions. If RADIUS is not enabled, TACACS+ servers
are used. If neither RADIUS or TACACS+ servers are configured, local authentication is used.
Usage Guidelines
Use this command to authenticate all the management sessions through TACACS+ servers. The
TACACS+ server should be configured before using this command. This command fails is the primary
and secondary TACACS+ servers are not configured.
The following types of management sessions can be configured:
• Telnet
• SSH
• Console
• HTTP
If you are using TACACS+ authentication servers, you should only use TACACS+ accounting servers
for accounting management sessions. TACACS+ authentication servers should be configured before
configuring TACACS+ accounting servers for management sessions.
Example
In the following example, management sessions for both the primary and secondary servers are
configured for TACACS+:
configure auth mgmt-access tacacs primary 192.168.14.12 secondary 192.168.14.55
In the following example, management sessions for both the primary and secondary servers are
configured for TACACS+ accounting:
configure auth mgmt-access tacacs-accounting primary 192.168.14.12 secondary
192.168.14.55
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures to authenticate all netlogin sessions through RADIUS servers.
Syntax Description
Default
Unconfigured. Uses RADIUS for authentication for login sessions. If RADIUS is not enabled, TACACS+
servers are used. If neither RADIUS or TACACS+ servers are configured, local authentication is used.
Usage Guidelines
The RADIUS server must be configured before this command is used. The command will fail if the
given primary and secondary RADIUS servers are not configured.
The following types of netlogin sessions can be configured:
• Dot1x-based netlogin
• Web-based netlogin
If you are using RADIUS authentication servers, you should only use RADIUS accounting servers for
accounting management sessions. RADIUS authentication servers should be configured before
configuring RADIUS accounting servers for management sessions.
Example
In the following example, both primary and secondary RADIUS servers are configured for netlogin:
configure auth netlogin radius primary 192.168.14.12 secondary 192.168.14.55
In this example the primary and secondary RADIUS accounting servers are configured for netlogin:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures to authenticate all netlogin sessions through TACACS+ servers.
Syntax Description
Default
Unconfigured. Uses RADIUS for authentication for login sessions. If RADIUS is not enabled, TACACS+
servers are used. If neither RADIUS or TACACS+ servers are configured, local authentication is used.
Usage Guidelines
The TACACS+ server should be configured before this command. This command returns an error if the
given primary and secondary TACACS+ servers are not configured or if TACACS+ authentication is not
configured for netlogin sessions.
If you are using TACACS+ authentication servers, you should only use TACACS+ accounting servers
for accounting netlogin sessions. TACACS+ authentication servers should be configured before
configuring TACACS+ accounting servers for netlogin sessions.
Example
In the following example, both primary and secondary TACACS+ servers are configured for netlogin:
configure auth netlogin tacacs primary 192.168.14.12 secondary 192.168.14.55
In this example the primary and secondary TACACS+ accounting servers are configured for netlogin:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Sets the maximum allowed limit before invoking denial of service (DoS) protection and discarding
packets.
Syntax Description
portnumber Specifies one or more port numbers. May be in the form 1, 2, 3-5.
pkts Configures the maximum number of packets, or threshold level, where packets
are discarded. Range is 50 to 20000 packets per second. Default is 150.
seconds Configures a duration in seconds. Range is 1 to 20 seconds. Default is 1
second.
Default
All ports are disabled for DoS protection.
Usage Guidelines
Use this command to isolate or block a particular type of broadcast. You can also use it to identify
layer 3 misses to the CPU or when too many IP multicasts are coming on a port.
Examples
The following example configures an alert threshold of 500 packets on port 8 every 3 seconds:
History
This command was first introduced in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures denial of service protection.
Syntax Description
alert-threshold Configures the number of packets per second that the switch needs to receive
on a port for an ACL to be enabled. Range is 150 to 100,000 packets per
second. Default is 4000.
notice-threshold Configures the number of packets per second that the switch needs to receive
on a port for messages to be logged. Range is 150 to 100,000 packets per
second. Default is 4000.
timeout Configures a duration in seconds. Range is 2 to 300 seconds. Default is 15.
messages Configures messaging to be on or off. Default is on.
filter-precedence Configures the access list precedence. Default is 10.
filter-type-allowed Configures the type of access list allowed. Default is destination
destination Specifies that destination ACLs can be created
source Specifies that source ACLs can be created
protocol Specifies that an ACL will be created to block packets from a single protocol,
either TCP, UDP, or other.
Default
The option defaults are:
• alert-threshold—4000
• notice-threshold—4000.
• timeout—15
• messages—on
• filter-precedence—10
• filter-type-allowed—destination
Usage Guidelines
This command configures denial of service protection for Extreme Networks switches. When heavy
traffic reaches the alert threshold, a hardware ACL is created that blocks the traffic for the timeout
number of seconds.
NOTE
If you set the filter-precedence to 0, the ACLs created by DoS protection will be overwritten by the
default VLAN QoS profile.
Example
The following command configures denial of service protection to be invoked when 3000 or more
packets per second are received by a port on the switch. This command configures logging to occur
when the number of packets per second that the switch receives is 2000, the timeout is 15 seconds, and
messages are on:
configure cpu-dos-protect alert-threshold 3000 notice-threshold 2000 timeout 15
messages on filter-precedence 10
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures ports as trusted, so that denial of service protection is not applied to port.
Syntax Description
port number Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
By default, no ports are trusted.
Usage Guidelines
Trusted ports can prevent innocent hosts from being blocked, or ensure that when an innocent host
responds to an attack that the flood of response packets is not mistaken as the attack.
Example
The following command configures a port as trusted, so that denial of service protection is not applied
port 3:
configure cpu-dos-protect trusted-port 3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures ports as trusted, so that denial of service protection is not applied to port.
Syntax Description
Default
By default, no ports are trusted.
Usage Guidelines
Typically, you would use the all parameter when you want to set the denial of service protection to
only a few of the ports on a switch. Use the all parameter, then use the command configure
cpu-dos-protect trusted-ports delete <port number> to set ports that should not be trusted
(that denial of service protection should be applied to).
Example
The following command configures a port as trusted, so that denial of service protection is not applied
to port 3:
configure cpu-dos-protect trusted-port add 3
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the aging time on untrusted ports for enhanced denial of service protection.
Syntax Description
aging Specifies the number of seconds for the aging time per port. The aging value
is the software cache timeout: the duration of time to be considered to reach
the threshold. The valid range is 1-300 seconds. The default value is 30
seconds.
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default aging time is 30 seconds.
Usage Guidelines
Use this command to change the aging time values for selected untrusted ports. To verify configuration,
use the show enhanced-dos-protect ipfdb ports <portlist> command and view data in the
Aging column.
Example
The following command configures the aging time on port 2 to 100 seconds:
configure enhanced-dos-protect ipfdb agingtime 100 ports 2
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the cache size on untrusted ports for enhanced denial of service protection.
Syntax Description
cache-size Specifies the cache size limit in kilobytes. The default value is 256. The
maximum value is 256000.
Default
The default cache size value is 256.
Usage Guidelines
Enhanced DoS Protection maintains the number of IPFDB entries according to the cache-size limit. Use
this command to set the cache size to some value other than the default value of 256K.
Use the following command to reset the cache-size to the 256K default value:
Example
The following command configures the cache size at 512K:
configure enhanced-dos-protect ipfdb cache-size 512
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the learning limit on untrusted ports for enhanced denial of service protection.
Syntax Description
learn-limit Specifies the number of packets allowed on the selected ports within the
learning window before the rate limit is applied; or before the software can
create an IPFDB entry in the hardware. The valid value range is 100-1953125.
The default on Fast Ethernet ports is 100 pkts/learn window. The default on
Gigabyte ports is 100 pkts/learn window.
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default learn-limit on Fast Ethernet ports is 100 pkts/learn window.
The default learn-limit on Gigabyte ports is 100 pkts/learn window.
Usage Guidelines
Use this command to configure a learning limit value to define the number of packets to be counted
before ExtremeWare can create an IPFDB entry in the hardware.
To reset the learning limit for enhanced denial of service protection to default values for selected ports,
use the following command:
Example
The following command configures the learn limit on port 3 at 75 packets within the learning window
before the IPFDB entry is created:
configure enhanced-dos-protect ipfdb learn-limit 75 ports 3
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the learning window on untrusted ports for the enhanced denial of service protection IPFDB
learning qualifier.
Syntax Description
learn-window Specifies the number of seconds for the learning window per port. This value
is the duration of time to be considered to reach the threshold. The valid
range is 5-300 seconds. The default value is 10 seconds.
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default learning window is 10 seconds.
Usage Guidelines
Use this command to change the learning window values for selected untrusted ports. To verify
configuration, use the show enhanced-dos-protect ipfdb ports <portlist> command.
Example
The following command configures the learn window on port 2 at 80 seconds:
configure enhanced-dos-protect ipfdb learn-window 80 ports 2
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures ports as trusted, so that enhanced denial of service protection is not applied to the ports; or
configures ports as untrusted, so that enhanced denial of service protection is applied to the ports.
Syntax Description
trusted Specifies the selected ports as trusted, so that enhanced denial of service is
not applied to the ports.
untrusted Specifies the selected ports as untrusted, so that enhanced denial of service
is applied to the ports.
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 2:*, 2:5, 2:6-2:8.
Default
By default, ports are trusted.
Usage Guidelines
You can configure each port as trusted or untrusted. A trusted port behaves as a normal port. An
untrusted port behaves according to the configuration parameter used in IPFDB thrashing.
Verify the status of each port by using the show enhanced-dos-protect [rate-limit | ipfdb]
ports <portlist> command.
Example
The following command configures a range of ports as trusted, so that enhanced denial of service
protection is not applied to ports 2 through 4:
configure enhanced-dos-protect ports trusted 2-4
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures rate limiting for enhanced denial of service protection.
Syntax Description
threshold Specifies the number of packets allowed on a given port within the learning window
before the rate limit is applied. The valid value range is 100-1953125. The default on
Fast Ethernet ports is 100 pkts/learn window. The default on Gigabyte ports is 100
pkts/learn window.
drop-probability Specifies the percentage of slow-path traffic to be dropped per port. The valid range
is 0-100 percent. The default value is 50 percent.
learn-window Specifies the number of seconds for the learning window per port. This value is the
duration of time to be considered to reach the rate limit threshold. The valid range is
5-300 seconds. The default value is 10 seconds.
protocol [all | icmp] Specifies the protocol packets to which rate limiting is applied. By default, rate limiting
is applied to Internet Control Message Protocol (ICMP) packets.
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a list of
slots and ports. On a stand-alone switch, can be one or more port numbers. May be
in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default threshold on Fast Ethernet ports is 100 pkts/learn window.
The default threshold on Gigabyte ports is 100 pkts/learn window.
The default drop-probability is 50 percent.
The default learn-window value is 10 seconds.
Rate limiting is applied by default to ICMP packets.
Usage Guidelines
Use this command to configure the rate-limit threshold, drop probability, learning window, or packet
protocol. To verify settings, use the show enhanced-dos-protect rate-limit ports <portlist>
command. To remove ports from rate limiting, use the unconfigure enhanced-dos-protect
rate-limit command.
Example
The following command sets the rate limiting threshold on port 3 to 200 packets:
configure enhanced-dos-protect rate-limit threshold 200 ports 3
The following command sets the rate limiting drop probability on port 4 to 60 percent:
configure enhanced-dos-protect rate-limit drop-probability 50 ports 4
The following command sets the rate limiting learn window on ports 2 and 3 to 90 seconds:
configure enhanced-dos-protect rate-limit learn-window 90 ports 2,3
The following command sets the rate limiting protocol to all packet types on ports 1 through 3:
configure enhanced-dos-protect rate-limit protocol all ports 1-3
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the base URL for Network Login.
Syntax Description
Default
The base URL default value is “network-access.net”.
Usage Guidelines
When you login using a web browser, you are redirected to the specified base URL, which is the DNS
name for the switch.
You must configure a DNS name of the type “www.xx…xx.xxx” or “xx…xx.xxx”.
This command applies only to the web-based authentication mode of Network Login.
Example
The following example configures the base URL as access.net:
configure netlogin base-url access.net
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the redirect URL for Network Login.
Syntax Description
Default
The redirect URL default value is “http://www.extremenetworks.com”.
Usage Guidelines
In ISP mode, you can configure netlogin to be redirected to a base page after successful login using this
command. If a RADIUS server is used for authentication, then base page redirection configured on the
RADIUS server takes priority over this configuration.
You must configure a complete URL starting from either http:// or https://
This command applies only to the web-based authentication mode of Network Login.
Example
The following example configures the redirect URL as http://www.extremenetworks.com:
configure netlogin redirect-page http://www.extremenetworks.com
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the primary and secondary RADIUS authentication server.
Syntax Description
Default
Unconfigured.
Usage Guidelines
Use this command to specify RADIUS server information. You can configure up to two primary and
two secondary RADIUS authentication servers.
The RADIUS server defined by this command is used for user name authentication and CLI command
authentication.
Example
The following command configures the primary RADIUS server on host radius1 using the default UDP
port (1645) for use by the RADIUS client on switch 10.10.20.30:
configure radius primary server radius1 client-ip 10.10.20.30
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the authentication string used to communicate with the RADIUS authentication server.
Syntax Description
primary Configures the authentication string for the primary RADIUS server.
secondary Configures the authentication string for the secondary RADIUS server.
Ipaddress The IP address of the server being configured.
Hostname The host name of the server being configured.
encrypted Indicates that the secret should be encrypted.
string The string to be used for authentication.
Default
Unconfigured.
Usage Guidelines
The secret must be the same between the client switch and the RADIUS server.
The RADIUS server must first be configured for use with the switch as a RADIUS client.
If the server address is not specified, it configures shared-secret for all configured primary and
secondary RADIUS authentication servers.
You must configure the RADIUS server first before configuring the shared secret for a specific server.
Example
The following command configures the shared secret as “purplegreen” on the primary RADIUS server:
configure radius primary shared-secret purplegreen
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout interval for RADIUS authentication requests.
Syntax Description
Default
The default is 3 seconds.
Usage Guidelines
This command configures the timeout interval for RADIUS authentication requests. When the timeout
has expired, another authentication attempt is made. After three failed attempts to authenticate, the
alternate server is used. After five failed attempts, local user authentication is used.
Example
This example configures the timeout interval for the primary RADIUS authentication to 10 seconds.
After 30 seconds (three attempts), the alternate RADIUS server will be used. After 50 seconds (five
attempts) local user authentication is used:
configure radius primary timeout 10
This example configures the timeout interval for RADIUS secondary server 192.168.4.4 authentication to
10 seconds. After 30 seconds (three attempts), the alternate RADIUS server will be used. After 50
seconds (five attempts) local user authentication is used:
configure radius secondary server 192.168.4.4 timeout 10
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the primary and secondary RADIUS accounting servers.
Syntax Description
Default
The default UDP port setting is 1646.
Usage Guidelines
Use this command to specify the RADIUS accounting server information for up to two primary and two
secondary RADIUS accounting servers.
Example
The following command configures RADIUS accounting on host radius1 using the default UDP port
(1646) for use by the RADIUS client on switch 10.10.20.30:
configure radius-accounting primary server radius1 client-ip 10.10.20.30
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the authentication string used to communicate with the RADIUS accounting server.
Syntax Description
primary Configures the authentication string for the primary RADIUS accounting
server.
secondary Configures the authentication string for the secondary RADIUS accounting
server.
ipaddress Specifies the IP address of the server being configured.
hostname Specifies the host name of the server being configured.
encrypted Indicates that the secret should be encrypted
string The string to be used for authentication.
Default
Unconfigured.
Usage Guidelines
The secret must be the same between the client switch and the RADIUS accounting server.
If the server address is not specified, shared-secret is configured on all primary and secondary RADIUS
accounting servers.
You must configure the RADIUS accounting server first before configuring the shared secret for a
specific server.
Example
The following command configures the shared secret as “purpleaccount” on the primary RADIUS
accounting server:
configure radius primary shared-secret purpleaccount
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout interval for RADIUS accounting authentication requests.
Syntax Description
primary Configures the timeout for the primary RADIUS accounting server.
secondary Configures the timeout for the secondary RADIUS accounting server.
ipaddress Specifies the IP address of the server being configured.
hostname Specifies the host name of the server being configured.
seconds Specifies the number of seconds to wait before retrying accounting requests.
Range is 3 to 120 seconds
Default
The default is 3 seconds.
Usage Guidelines
This command configures the timeout interval for RADIUS accounting authentication requests. When
the timeout expires, another authentication attempt is made. After three failed attempts to authenticate,
the alternate server is used. After five failed attempts, local user authentication is used.
Example
This example configures the timeout interval for RADIUS accounting authentication to 10 seconds on
the primary server. After 30 seconds (three attempts), the alternate RADIUS server will be used:
configure radius-accounting primary timeout 10
This example configures the timeout interval for RADIUS accounting authentication to 10 seconds for
the secondary server. After 30 seconds (three attempts), the alternate RADIUS server will be used:
configure radius-accounting secondary server 192.168.4.12 timeout 10
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the default data VLAN for wireless users.
Syntax Description
Default
Wireless management default VLAN.
Usage Guidelines
Wireless users are placed in default-user-vlan after authentication. Users who do not have a
VSA-VLAN assignment on the RADIUS server are placed in this VLAN.
Example
The following example sets the security profile, open-auth, to use the VLAN open-vlan:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables dot11 authentication, network authentication, and encryption.
Syntax Description
Default
N/A.
Usage Guidelines
The following table lists the valid combinations of authentication and encryption:
Examples
The following command sets the authentication and encryption:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
When the network-authentication is set to dot1x, WPA, or WPA-PSK, this command configures the
interval when group keys for dot1x and WPA clients are updated.
Syntax Description
Default
10 minutes.
Usage Guidelines
Use this command to change WPA and dot1x key update time values. Change timers only when you do
not want the keys to be updated frequently.
Example
The following example sets the interval for updating keys to 29 minutes:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
When the network-authentication is set to dot1x, WPA, or WPA-PSK, this command configures the
interval when pairwise keys for dot1x and WPA clients are updated.
Syntax Description
Default
15 minutes.
Usage Guidelines
Use this command to change WPA and dot1x key update time values. Change timers only when you do
not want the keys to be updated frequently.
Example
The following example sets the interval for updating keys to 60 minutes:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
When the network-authentication is set to dot1x or WPA, this command configures the interval when
clients are re-authenticated.
Syntax Description
Default
600 seconds.
Usage Guidelines
Use this command to change the re-authenticate interval time values for a security profile. Change
timers only when you do not want the client to be re-authenticated frequently.
Example
The following example sets the re-authentication interval for clients to 2 minutes:
configure security-profile open-profile dot1x-wpa-timers reauth-period 120
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets the name of the wireless network for the 802.11 interface associated with the security profile.
Syntax Description
Default
N/A.
Usage Guidelines
ESS names can be shared across wireless ports and interfaces.
Example
The following example assigns the name shared_ess to the security profile shared-auth:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Establishes whether the service set identifier (SSID) is published in the beacon or not.
Syntax Description
Default
On
Usage Guidelines
The beacon turns on whether the SSID is published in the beacon or not. If you set this command to off,
the client must know the SSID before it can associate. Sniffing on the beacon shows an empty SSID.
Configuration changes take effect immediately and are propagated to all ports sharing the named
profile. If the command fails, none of the changes is propagated to any of the ports.
Examples
The following command configures the security profile secure1 not to publish the SSID in the beacon:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Determines whether the security profile uses the dynamic VLAN (VLAN pushed by the RADIUS server
through a VSA (Vendor Specific Attribute)).
Syntax Description
Default
Y (yes).
Usage Guidelines
If the variable is set to Y (yes), and if the RADIUS server is configured to push back VSA 203 or 209,
then the pushed-back VSAs will override the default-user-vlan setting. (If both VSAs are
configured, then they have to point to the same VLAN.) The user will be placed in the VLAN indicated
by the VSA after authentication.
If the variable is set to N (no), then the user will be placed in the VLAN indicated by
default-user-vlan regardless of any VSAs from the RADIUS server.
Example
The following example sets the security profile, open-profile, to use the dynamic VLAN:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets the default key index for the security profile in case of static WEP encryption.
Syntax Description
Default
Zero (0)
Usage Guidelines
Sets the index of the WEP key. The key at the specified index must be configured before you can set the
default index for WEP auth/encryption.
Configuration changes take effect immediately and are propagated to all ports sharing the named
profile. If the command fails, none of the changes is propagated to any of the ports.
The index value is used when a user sets the WEP key in the following command:
configure security-profile <name> wep key add <index> hex <hexoctets> | plaintext
<string>
Examples
The following example sets the index of the WEP key to 3:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Adds the given WEP key at the specified index.
Syntax Description
Default
Hex
Usage Guidelines
This key is used for WEP encryption. If you use hex mode, then the key should be made up of hex
digits (i.e., if encryption-length is 64 the key should be 10 hex digits (64-24 (ICV) = 40bits = 5 bytes = 10
hex digits). When you specify plaintext mode, the key is simply the ASCII value of the letters in the
specified key (for example, A = 35 and so on...). Plaintext does not mean passphrase.
Configuration changes take effect immediately and are propagated to all ports sharing the named
profile. If the command fails, none of the changes is propagated to any of the ports.
Examples
The following example adds the first WEP key (0) with the hex encryption code 1234567891:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Deletes the specified WEP key.
Syntax Description
Default
Zero (0)
Usage Guidelines
When you delete a WEP key whose index is the default WEP key index, then the default index is
changed automatically to the lowest specified WEP key (or N/A if no WEP keys have been specified).
Configuration changes take effect immediately and are propagated to all ports sharing the named
profile. If the command fails, none of the changes is propagated to any of the ports.
Examples
The following example deletes the first WEP key (0).
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the WPA pre-shared key.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to configure the WPA pre-shared key using a hexadecimal (64 bytes) digit or ASCII
alphanumeric string (8-63 characters in length).
Examples
The following example configures the WPA pre-shared key “abcdefgh” for the security profile sec_prof1
as passphrase:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
configure ssh2
configure ssh2 key {pregenerated}
Description
Generates the Secure Shell 2 (SSH2) host key.
Syntax Description
pregenerated Indicates that the SSH2 authentication key has already been generated. The
user will be prompted to enter the existing key.
Default
The switch generates a key for each SSH2 session.
Usage Guidelines
Secure Shell 2 (SSH2) is a feature of ExtremeWare that allows you to encrypt session data between a
network administrator using SSH2 client software and the switch, or to send encrypted data from the
switch to an SSH2 client on a remote system. Image and configuration files may also be transferred to
the switch using the Secure Copy Program (SCP) or the Secure File Transfer Protocol (SFTP).
Before you can enable SSH2, you must first obtain a security license from Extreme Networks. After you
receive the license, you must enable SSH2 and generate a host key. To enable SSH2, use the enable
ssh2 command. To generate an SSH2 host key, use the configure ssh2 key command.
An authentication key must be generated before the switch can accept incoming SSH2 sessions. This can
be done automatically by the switch, or you can enter a previously generated key.
If you elect to have the key generated, you are prompted to enter a set of random characters to be used
in generating the key. The key generation process takes approximately ten minutes, and cannot be
canceled after it has started. Once the key has been generated, you should save your configuration to
preserve the key.
To use a key that has been previously created, use the pregenerated keyword. You are prompted to
enter the pregenerated key. You can use the show configure command to list the previously generated
key, and then copy and paste it after the prompt from the configure ssh2 key pregenerated
command.
The key generation process generates the SSH2 private host key. The SSH2 public host key is derived
from the private host key, and is automatically transmitted to the SSH2 client at the beginning of an
SSH2 session.
Example
The following command generates an authentication key for the SSH2 session:
configure ssh2 key
Type in a series of random characters, and then press the Enter or Return key. The key generation
process will then proceed.
To configure an SSH2 session using a previously generated key, use the following command:
configure ssh2 key pregenerated
Enter the previously-generated key (you can copy and paste it from the saved configuration file).
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Obtains the pre-generated certificate from the user.
Syntax Description
This command has no parameters or variables.
Default
N/A
Usage Guidelines
This command is also used when downloading/ uploading the configuration. The certificate
information stored in the uploaded configuration file should not be modified, because it is signed using
the issuer’s private key.
The certificate and private key file should be in PEM format and generated using RSA as the
cryptography algorithm.
Example
The following command obtains the pre-generated certificate from the user:
Next, the user will open the certificate and then file, copy, and paste the certificate into the
console/telnet session, followed by a “.” (period) to end the command.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Creates a self-signed certificate and private key that can be saved in NVRAM.
Syntax Description
length Specifies the private key length in bytes. Valid values are between 1024 and
4096.
code Specifies the country code in 2 character format. For a list of supported
country codes, see “configure wireless country-code” on page 1017.
org_name Specifies the organization name.The org_name can be up to 64 characters
long.
name Specifies the common name. The common name can be up to 64 characters
long.
Default
N/A
Usage Guidelines
Creates a self signed certificate and private key that can be saved in NVRAM. The certificate generated
is in X509v3 format. The certificate generated is in PEM format.
Most web browsers check whether the common-name field in the received server certificate is the same
as the URL used to reach the site, otherwise they give a warning.
The size of the certificate generated depends on the RSA Key length (privkeylen) and the length of the
other parameters (country, organization name etc.) supplied by the user. If the RSA key length is 1024,
then the certificate size is ~ 1kb and the private key length is ~1kb. For RSA Key length of 4096, the
certificate length is ~2kb and the private key length is ~3kb.
Examples
The following command creates an SSL certificate in the USA for a website called bigcats:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Obtains the pre-generated private key from the user.
Syntax Description
This command has no parameters or variables.
Default
N/A
Usage Guidelines
This command will also be used when downloading/uploading the configuration. The private key will
be stored in the uploaded configuration file in an encrypted format using a hard coded passphrase.
Hence the private key information in the configuration file should not be modified.
The certificate and private key file should be in PEM format and generated using RSA as the
cryptography algorithm.
Example
The following command obtains the pre-generated private key from the user:
Next, the user will open the certificate and then file, copy, and paste the certificate into the
console/telnet session, followed by a “.” (period) to end the command.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the primary and secondary server information for a TACACS+ authentication server.
Syntax Description
Default
TACACS+ uses TCP port 49.
Usage Guidelines
Configure the server information for a TACACS+ server.
Example
The following command configures server tacacs1 as the primary TACACS+ server for client switch
10.10.20.35:
configure tacacs primary server tacacs1 client-ip 10.10.20.35
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the shared secret string used to communicate with the TACACS+ authentication server.
Syntax Description
primary Configures the authentication string for the primary TACACS+ server.
secondary Configures the authentication string for the secondary TACACS+ server.
ipaddress Specifies the IP address of the TACACS+ server being configured.
hostname Specifies the host name of the TACACS+ server being configured.
encrypted Indicates that the secret should be encrypted.
string Specifies the string to be used for authentication.
Default
Unconfigured.
Usage Guidelines
The secret must be the same between the client switch and the TACACS+ server.
The TACACS+ server must first be configured for use with the switch as a RADIUS client.
If the server address is not specified, shared secret is configured for all primary and secondary
TACACS+ authentication servers.
You must first configure the TACACS+ server information before configuring the shared secret for a
specific server.
Example
The following command configures the shared secret as “purplegreen” on the primary TACACS+
server:
configure tacacs-accounting primary shared-secret purplegreen
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timeout interval for TACAS+ authentication requests.
Syntax Description
Default
The default is 3 seconds.
Usage Guidelines
This command configures the timeout interval for TACACS+ authentication requests. When the timeout
has expired, another authentication attempt to the next alternative server is made.
Example
The following command configures the timeout interval for the secondary TACACS+ authentication to
10 seconds:
configure tacacs secondary timeout 10
The following command configures the timeout interval for TACACS+ authentication to 10 seconds:
configure tacacs primary server 192.168.14.8 timeout 10
History
This command was first available in ExtremeWare 7.2.e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the primary and secondary TACACS+ accounting servers.
Syntax Description
Default
Unconfigured.
Usage Guidelines
Use this command to specify the TACACS+ accounting server information for up to two primary and
two secondary TACACS+ accounting servers.
Example
The following command configures server tacacs1 as the primary TACACS+ accounting server for client
switch 10.10.20.35:
configure tacacs-accounting primary server tacacs1 client-ip 10.10.20.35
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the shared secret string used to communicate with the TACACS+ accounting server.
Syntax Description
primary Configures the authentication string for the primary TACACS+ accounting
server.
secondary Configures the authentication string for the secondary TACACS+ accounting
server.
ipaddress Specifies the IP address of the TACACS+ server being configured.
hostname Specifies the host name of the TACACS+ server being configured. Must be
able to be resolved to an IP address.
encrypted Indicates that the secret should be encrypted.
string The string to be used for authentication.
Default
Unconfigured
Usage Guidelines
The secret must be the same between the client switch and the TACACS+ accounting server.
If the server address is not specified, shared secret is configured for all primary and secondary
TACACS+ accounting servers.
You must first configure the TACACS+ accounting server information before configuring the shared
secret for a specific server.
Example
The following command configures the shared secret as “tacacsaccount” on the primary TACACS+
accounting server:
configure tacacs-accounting primary shared-secret tacacsaccount
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platform.
Description
Configures the timeout interval for TACACS+ accounting authentication requests.
Syntax Description
primary Configures the timeout for the primary TACACS+ accounting server.
secondary Configures the timeout for the secondary TACACS+ accounting server.
ipaddress Specifies the IP address of the TACACS+ server being configured.
hostname Specifies the host name of the TACACS+ server being configured..
seconds Specifies the number of seconds to wait before retrying accounting requests.
Range is 3 to 120 seconds
Default
The default is 3 seconds.
Usage Guidelines
This command configures the timeout interval for TACACS+ accounting authentication requests. When
the timeout has expired, another authentication attempt is made to the alternative server.
Example
The following command configures the timeout interval for TACACS+ accounting authentication to 10
seconds:
configure tacacs-accounting primary server 192.168.12.12 timeout 10
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a set of DHCP addresses for a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
This command configures in the switch a set of DHCP addresses for a particular VLAN. The configured
address range can be for a local subnet (the range falls in one of the local subnets of the switch) or a
remote subnet (the configured IP address does not fall in any of the local subnets of the switch).
To configure address ranges for a remote subnet the optional parameter mask must be provided.
To configure address ranges for a local subnet the parameter mask should not be provided.
You can configure a maximum of 64 local and remote address ranges.
Example
You can allocate IP addresses for a remote subnet (non-local subnet) using the DHCP server. The
following command gives an example of configuring DHCP address ranges for a remote subnet using
the subnet 60.0.0.x/24 in the VLAN named test:
configure vlan test dhcp-address-range 60.0.0.5 - 60.0.0.40 mask 255.255.255.0
NOTE
The mask option is required when configuring the DHCP address range for the remote subnet.
History
This command was first available in ExtremeWare 7.2e.
This command was modified in ExtremeWare 7.3e to allow remote subnets to be configured in
ExtremeWare.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timer value in seconds returned as part of the DHCP response.
Syntax Description
Default
N/A.
Usage Guidelines
The timer value is specified in seconds.
The DHCP server should be used with Network Login and not as a stand-alone DHCP server.
Example
The following command configures the DHCP lease timer value for VLAN corp:
configure vlan corp dhcp-lease-timer <lease-timer>
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the DHCP options returned as part of the DHCP response by a switch configured as a
DHCP server.
Syntax Description
Default
N/A.
Usage Guidelines
Use the dhcp-gateway keyword to configure the DHCP gateway option for a specified DHCP address
range.
Use the dns-server keyword to configure the DNS server option for a specified DHCP address range.
Use the wins-server keyword to configure the WINS server option for a given DHCP address range.
A VLAN can have multiple DHCP address ranges; therefore, the parameter start-addr identifies the
DHCP address range for which this configuration is applicable.
The DHCP address range is identified as the one whose starting IP address is the same as start-addr.
If start-addr is not provided, then the DHCP option will be applied for the primary DHCP address
range.
Example 1
Consider a VLAN named test with a primary subnet 40.0.0.x/24 and a secondary subnet 50.0.0.x/24.
Assume that for the primary subnet a DHCP address range is configured ranging from 40.0.0.5 -
40.0.0.40. Similarly, for the secondary subnet the DHCP address range is configured ranging from
50.0.0.5 - 50.0.0.40.
To configure the DHCP gateway as 40.0.0.90 for the primary subnet, issue the following command:
To configure the DHCP gateway as 50.0.0.90 for the secondary subnet issue the following command:
NOTE
You can configure multiple DHCP address ranges for a VLAN. The start-addr option in the command
(50.0.0.5 in this example) specifies the exact DHCP address range for which the command applies. If
the last option is not specified, the command is applied for the primary subnet.
Example 2
Consider a VLAN named test with a primary subnet 40.0.0.x/24 and a secondary subnet 50.0.0.x/24.
Assume that for the primary subnet a DHCP address range is configured ranging from 40.0.0.5 -
40.0.0.40. Similarly, for the secondary subnet the DHCP address range is configured ranging from
50.0.0.5 - 50.0.0.40.
To configure the DNS server as 40.0.0.90 for the primary subnet, issue the following command:
To configure the DNS Server as 50.0.0.90 for the secondary subnet, issue the following command:
NOTE
You can configure multiple DHCP address ranges for a VLAN. The start-addr option in the command
(50.0.0.5 in this example) specifies the exact DHCP address range for which the command applies. If
the last option is not specified, the command is applied for the primary subnet.
Example 3
Consider a VLAN named test with a primary subnet 40.0.0.x/24 and a secondary subnet 50.0.0.x/24.
Assume that for the primary subnet a DHCP address range is configured ranging from 40.0.0.5 -
40.0.0.40. Similarly, for the secondary subnet the DHCP address range is configured ranging from
50.0.0.5 - 50.0.0.40.
To configure the WINS Server as 40.0.0.90 for the primary subnet, issue the following command:
To configure the WINS Server as 50.0.0.90 for the secondary subnet, issue the following command:
NOTE
You can configure multiple DHCP address ranges for a VLAN. The start-addr option in the command
(50.0.0.5 in this example) specifies the exact DHCP address range for which the command applies. If
the last option is not specified, the command is applied for the primary subnet.
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.3e to allow remote or secondary subnets to be
configured for DHCP options in ExtremeWare (through the addition of the parameter start-addr).
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timer value returned as part of the DHCP response for clients attached to
Network Login-enabled ports.
Syntax Description
vlan name Specifies the VLAN to which this timer value applies.
seconds Specifies the timer value, in seconds.
Default
10 seconds.
Usage Guidelines
The timer value is specified in seconds.
This command applies only to the web-based authentication mode of Network Login.
Example
The following command sets the timer value to 15 seconds for VLAN corp:
configure vlan corp netlogin-lease-timer 15
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
create access-list
create access-list <name> access-mask <access-mask name> {dest-mac
<dest_mac} {source-mac <src_mac>} {vlan <name>} {ethertype [IP | ARP |
<hex_value>]} {tos <ip_precedence> | code-point <code_point>} {ipprotocol
[tcp | udp | icmp | igmp | <prococol_num>]} {dest-ip <dest_IP>/<mask
length>} {dest-L4port <dest_port>} {source-ip <src_IP>/<mask length>}
{source-L4port <src_port> [permit {qosprofile <qosprofile>} {set code-point
<code_point>} {set dot1p <dot1p_value} | permit-established |
deny]{vlan-pri}{vlan-pri-2bits}
Description
Creates an access list.
Syntax Description
History
This form of the command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
create access-mask
create access-mask <access-mask name> {dest-mac} {source-mac} {vlan} {tos
|code-point} {ethertype} {ipprotocol} {dest-ip/<mask length>}
{source-L4port | {icmp-type} {icmp-code}} {permit-established} {egresport}
{ports} {precedence <number>}{vlan-pri}{vlan-pri-2bits}
Description
Creates an access mask.
Syntax Description
History
This form of the command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
create access-profile
create access-profile <access profile> type [ipaddress | ipx-node | ipx-net
| ipx-sap | as-path]
Description
Creates an access profile.
Syntax Description
Default
N/A.
Usage Guidelines
You must give the access profile a unique name (in the same manner as naming a VLAN, protocol filter,
or Spanning Tree Domain).
After the access profile is created, you must configure the access profile mode. The access profile mode
determines whether the items in the list are to be permitted access or denied access.
Example
The following command creates an access profile named nosales that will contain IP address/mask pairs:
create access-profile nosales type ipaddress
The following command creates an access profile that will contain AS path expressions:
create access-profile AS1 type as-path
History
This command was introduced in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
create rate-limit
create rate-limit <rule_name> access-mask <access-mask name> {dest-mac
<dest_mac>} {source-mac <scr_mac>} {vlan <name>} {ethertype [IP | ARP |
<hex_value>]} {tos <ip_precedence> | code-point <code_point>} {ipprotocol
[tcp | udp | icmp | igmp | <prococol_num>]} {dest-ip <dest_IP>/<mask
length>} {dest-L4port <dest_port>} {source-ip <src_IP>/<mask length>}
{source-L4port <src_port> [permit {qosprofile <qosprofile>} {set code-point
<code_point>} {set dot1p <dot1p_value} limit <rate_in_Mbps> {exceed-action
[drop | set code-point <code_point>]} {vlan-pri}{vlan-pri-2bits}
Description
Creates a rate limit rule.
Syntax Description
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
create security-profile
create security-profile <name> {copy <existing_profile>}
Description
Creates a new security profile.
Syntax Description
Default
N/A
Usage Guidelines
Use this command to create a new profile from scratch or to copy an existing profile using a new name.
Example
The following example creates a new security-profile called wep-secure using an existing profile called
unsecure:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
create trusted-mac-address
create trusted-mac-address mac-address <mac_address> [mask <mask>] vlan
<vlan_name>| all [ports <portlist>] [protocol {DHCP|ARP}]
Description
Configures a trusted media access control (MAC) address with mask for each VLAN or all VLANs for
the ARP or DHCP protocols.
Syntax Description
mac_address Specifies the MAC address for enabling the trusted-MAC feature. Specified in
the form nn:nn:nn:nn:nn:nn.
mask Specifies the MAC address mask value. If a mask is not specified, the default
mask of ff:ff:ff:ff:ff:ff is used.
vlan_name Specifies the name of a VLAN. If the all keyword is specified,.
all Specifies all VLANs are configured for trusted-MAC.
portlist Specifies one or more ports or slots and ports of the VLAN. Can be one or
more port numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
DHCP Specifies to use the DHCP protocol.
ARP Specifies to use the ARP protocol.
Default
N/A
Usage Guidelines
Use this command to configures a trusted MAC address. A mask for the MAC address is optional. If
you do not specify a mask, the default mask of ff:ff:ff:ff:ff:ff is used. This command is equivalent to
configuring an individual MAC address.
ExtremeWare performs an AND operation between the source MAC address of the incoming packet and
its mask. It then compares that result with the result of the AND operation between the configured
address and the mask. If the results are the same, the address is trusted and the packet is forwarded
independent to the port authentication state.
Example
The following example creates a trusted MAC on all ports in the VLAN bldg5 allowing the use of the
DHCP protocol.
History
This command was first available in 7.3e.
Platform Availability
This command is available on the “e” series platforms.
delete access-list
delete access-list <name>
Description
Deletes an access list.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes access list allow102:
delete access-list allow102
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete access-mask
delete access-mask <name>
Description
Deletes the named access-mask.
Syntax Description
Usage Guidelines
None.
Example
The following command disables statistics collection for access list allow102:
delele access-list allow102
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete access-profile
delete access-profile <access profile>
Description
Deletes an access profile.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes an access profile named nosales:
delete access-profile nosales
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete rate-limit
delete rate-limit <name>
Description
Deletes a rate limit rule.
Syntax Description
Usage Guidelines
None.
Example
The following command deletes a rate limit rule named throttle2:
delete access-profile throttle2
History
Platform Availability
This command is available on the “e” series platforms.
delete security-profile
delete security-profile <name>
Description
Deletes the named security profile.
Syntax Description
Default
N/A
Usage Guidelines
Use this command to delete the named security profile. The named profile cannot be attached to any
active ports.
To verify your configuration, use the show security-profile command. The show
security-profile output displays the configured parameters of the security profile.
Example
The following example deletes the RF profile named wep-secure:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Deletes a trusted media access control (MAC) address.
Syntax Description
mac_address Specifies the MAC address of the enabled trusted-MAC. Specified in the form
nn:nn:nn:nn:nn:nn.
mask Specifies a mask for the MAC address. If a mask is not specified, the default
mask of ff:ff:ff:ff:ff:ff is used.
all Specifies all VLANs.
vlan_name Specifies the name of a VLAN.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
DHCP Specifies the DHCP protocol.
ARP Specifies the ARP protocol.
Default
N/A
Usage Guidelines
Use this command to delete a trusted MAC address. If you do not specify a MAC address, all the MAC
addresses in the VLAN are deleted.
Example
The following example deletes a MAC address from a VLAN named corp:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all “e” series switches.
disable arp-learning
disable arp-learning
Description
Disables the ARP-learning feature on the switch.
Syntax Description
This command has no arguments or variables.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
Description
Disables the ARP-learning feature on a port or ports.
Syntax Description
portlist Specifies the ingress port(s) on which this rule is applied.
any specifies that the rule will be applied to all ports.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
Description
Disables the ARP-learning feature on a vlan.
Syntax Description
vlan name Specifies the vlan to which the rule applies.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
Description
Disables the ARP-learning feature on a port in the given vlan.
Syntax Description
vlan name Specifies the vlan to which the rule applies.
portlist Specifies the ports to which the rule applies.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
disable cpu-dos-protect
disable cpu-dos-protect
Description
Disables denial of service protection.
Syntax Description
There are no arguments or variables for this command.
Default
Default is disabled.
Usage Guidelines
None.
Example
The following command disables denial of service protection.
disable cpu-dos-protect
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables DHCP on a specified port in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
The DHCP server should be used with Network Login and not as a stand-alone DHCP server.
Example
The following command disables DHCP for port 9 in VLAN corp:
disable dhcp ports 9 vlan corp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable enhanced-dos-protect
disable enhanced-dos-protect {rate-limit | ipfdb} {ports [<portlist> |
all]}
Description
Disables enhanced denial of service protection globally or for selected ports.
Syntax Description
Default
Default is disabled.
Usage Guidelines
Use the rate-limit keyword in this command to disable the lowering of the percentage of slow path
traffic being sent to the CPU. Verify the disabled status by using the show enhanced-dos-protect
rate-limit command. To globally disable rate limiting, omit the ports keyword and qualifier.
Use the ipfdb keyword in this command to disable the IPFDB learning qualifier. Verify the disabled
status by using the show enhanced-dos-protect ipfdb command. To globally disable the IPFDB
learning qualifier, omit the ports keyword and qualifier.
Example
The following command disables enhanced denial of service protection rate limiting for all ports.
disable enhanced-dos-protect rate-limit ports all
The following command globally disables the enhanced denial of service protection IPFDB learning
qualifier.
disable enhanced-dos-protect ipfdb
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
disable netlogin
disable netlogin [web-based |dot1x]
Description
Disables Network Login modes.
Syntax Description
Default
Both types of authentication are enabled.
Usage Guidelines
Both types, either type, or no type of authentication can be enabled on the same switch. To enable an
authentication mode, use the following command:
enable netlogin [web-based | dot1x]
This command was first introduced as disable netlogin, which disabled the initial version of
Network Login, the web-based mode. The original command was subsequently deprecated when the
802.1x mode of Network Login was introduced in ExtremeWare 7.1.0. The deprecated version of the
command is temporarily supported in configurations. During an upgrade, the deprecated command:
disable netlogin
Example
The following command disables Network Login:
disable netlogin
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables Network Login logout window pop-up.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
This command controls the logout window pop-up on the web-based network client. This command
applies only to the web-based authentication mode of Network Login. When disabled, the logout
window pop-up will no longer appear.
Example
The following command disables Network Login logout-privilege:
disable netlogin logout-privilege
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables Network Login on a specified port in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
Network Login must be disabled on a port before you can delete a VLAN that contains that port.
This command applies to both the web-based and 802.1x mode of Network Login. To control which
authentication mode is used by Network Login, use the following commands:
Example
The following command disables Network Login on port 9 in VLAN corp:
disable netlogin ports 9 vlan corp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables Network Login session refresh.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Network Login sessions can refresh themselves after a configured timeout. After the user has been
logged in successfully, a logout window opens which can be used to close the connection by clicking on
the LogOut link. Any abnormal closing of this window is detected on the switch and the user is logged
out after a time interval as configured for session refresh. The session refresh is enabled and set to five
minutes by default.
This command applies only to the web-based authentication mode of Network Login.
Example
The following command disables Network Login session refresh:
disable netlogin session-refresh
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
disable radius
disable radius
Description
Disables the RADIUS client.
Syntax Description
This command has no arguments or variables.
Default
RADIUS authentication is disabled by default.
Usage Guidelines
None.
Example
The following command disables RADIUS authentication for the switch:
disable radius
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable radius-accounting
disable radius-accounting
Description
Disables RADIUS accounting.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command disables RADIUS accounting for the switch:
disable radius-accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable ssh2
disable ssh2
Description
Disables the SSH2 server for incoming SSH2 sessions to switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
SSH2 session options (access profile and non-default port setting) are not saved when SSH2 is disabled.
To view the status of SSH2 Telnet sessions on the switch, use the show management command. The
show management command displays information about the switch including the enable/disable state
for SSH2 Telnet sessions.
SSH2 client connections can still be initiated from the switch when the SSH2 server is disabled.
Example
The following command disables the SSH2 server:
disable ssh2
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable tacacs
disable tacacs
Description
Disables TACACS+ authentication.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command disables TACACS+ authentication for the switch:
disable tacacs
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable tacacs-accounting
disable tacacs-accounting
Description
Disables TACACS+ accounting.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command disables TACACS+ accounting:
disable tacacs-accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable tacacs-authorization
disable tacacs-authorization
Description
Disables TACACS+ authorization.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This disable CLI command authorization but leaves user authentication enabled.
Example
The following command disables TACACS+ CLI command authorization:
disable tacacs-authorization
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable trusted-mac-address
disable trusted-mac-address {vlan <vlan-name>}
Description
Disables trusted Organizational Unique Identifier (OUI) or MAC addresses for port-specific
configurations.
Syntax Description
vlan name Specifies the VLAN on whose ports trusted-MAC feature should be disabled.
Default
Disabled.
Usage Guidelines
Use this command to disable OUI or MAC addresses for port-specific configurations. Disabling this
feature does not remove the previous port-specific configurations.
Example
The following command disables trusted MAC addresses on the corp VLAN:
disable trusted-mac-address vlan corp
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
disable web
disable web
Description
Disables both HTTP access and secure HTTP access (HTTPS) to the switch.
Syntax Description
This command has no parameters or variables.
Default
Enabled
Usage Guidelines
Use this command to prevent web access..
Example
The following command disables HTTP and HTTPS:
disable web
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables HTTP access to the switch on the default HTTP port (80).
Syntax Description
This command has no parameters or variables.
Default
Enabled
Usage Guidelines
Use this command to disallow users from connecting with HTTP. Disabling HTTP access forces users to
use a secured HTTPS connection if web HTTPS is enabled. Use the following command to enable web
HTTPS:
enable web https
Example
The following command disables HTTP on the default port:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables secure HTTP access (HTTPS) to the switch on the default HTTPS port (443).
Syntax Description
This command has no parameters or variables.
Default
Enabled
Usage Guidelines
Use this command to disable HTTPS before changing the certificate or private key.
Example
The following command disables HTTPS on the default port:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Permits downloading of a certificate key from files stored in a TFTP server.
Syntax Description
Default
N/A
Usage Guidelines
If the operation is successful, any existing certificate will be overwritten. Following successful
download, a check is performed to find out whether the public key in the certificate matches with the
private key stored. If the private and public keys do not match, warning message will be displayed
(“Warning: The Private Key does not match with the Public Key in the certificate.”). This warning will
act as a reminder to the user to download the private key also.
The certificate and private key file should be in PEM format and generated using RSA as the
cryptography algorithm.
Example
The following example downloads a certificate from IP address 166.81.0.14:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Permits downloading of a private key from files in a TFTP server.
Syntax Description
Default
N/A
Usage Guidelines
When this command is executed, if the private key is encrypted, the user is prompted to enter the
passphrase that was used to encrypt the private key when the private key was generated. Only DES
and 3DES encryption mechanisms are supported for private key encryption. If the operation is
successful the existing private key will be overwritten.
After the download is successful, a check is performed to find out whether the private key downloaded
matches with the public key stored in the certificate. If they do not match, a warning message is
displayed (“Warning: The Private Key does not match with the Public Key in the certificate.”). This
warning acts as a reminder to the user to download the corresponding certificate.
The certificate and private key file should be in PEM format and generated using RSA as the
cryptography algorithm.
Example
The following command enables downloading of a private key from a TFTP server:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
enable arp-learning
enable arp-learning
Description
Enables the ARP-learning feature on the switch.
Syntax Description
This command has no arguments or variables.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
Description
Enables the ARP-learning feature on a port or ports.
Syntax Description
portlist Specifies the ingress port(s) on which this rule is applied.
any specifies that the rule will be applied to all ports.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
Description
Enables the ARP-learning feature on a port in the given vlan.
Syntax Description
vlan name Specifies the vlan to which the rule applies.
portlist Specifies the ports to which the rule applies.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
enable cpu-dos-protect
enable cpu-dos-protect
Description
Enables denial of service protection.
Syntax Description
There are no arguments or variables for this command.
Default
Default is disabled.
Usage Guidelines
None.
Example
The following command enables denial of service protection.
enable cpu-dos-protect
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables simulated denial of service protection.
Syntax Description
There are no arguments or variables for this command.
Default
Default is disabled.
Usage Guidelines
When simulated denial of service protection is enabled, no ACLs are created. This mode is useful to
gather information about normal traffic levels on a switch. This will assist in configuring denial of
service protection so that legitimate traffic is not blocked.
Example
The following command enables simulated denial of service protection.
enable cpu-dos-protect simulated
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables DHCP on a specified port in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
The DHCP server should be used with Network Login and not as a stand-alone DHCP server.
Example
The following command enables DHCP for port 9 in VLAN corp:
enable dhcp ports 9 vlan corp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable enhanced-dos-protect
enable enhanced-dos-protect {rate-limit | ipfdb} {ports [<portlist> | all]}
Description
Enables enhanced denial of service protection globally or for selected ports.
Syntax Description
Default
Default is disabled.
Usage Guidelines
Use the rate-limit keyword in this command to lower the percentage of slow path traffic being sent to
the CPU. Verify the enabled/disabled status by using the show enhanced-dos-protect rate-limit
command.
Use the ipfdb keyword in this command to prevent IPFDB thrashing. Verify the enabled/disabled
status by using the show enhanced-dos-protect ipfdb command.
Example
The following command enables enhanced denial of service protection rate limiting for all ports.
enable enhanced-dos-protect rate-limit ports all
The following command globally enables the enhanced denial of service protection IPFDB learning
qualifier.
enable enhanced-dos-protect ipfdb
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
enable netlogin
enable netlogin [web-based | dot1x]
Description
Enables Network Login authentication modes.
Syntax Description
Default
Both types of authentication are enabled.
Usage Guidelines
Both types, either type, or no type of authentication can be enabled on the same switch. To disable an
authentication mode, use the following command:
disable netlogin [web-based | dot1x]
This command was first introduced as enable netlogin, which enabled the initial version of Network
Login, the web-based mode. The original command was subsequently deprecated when the 802.1x
mode of Network Login was introduced in ExtremeWare 7.1.0. The deprecated version of the command
is temporarily supported in configurations. During an upgrade, the deprecated command:
enable netlogin
Example
The following command enables web-based Network Login:
enable netlogin web-based
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables Network Login logout pop-up window.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
This command controls the logout window pop-up on the web-based network client. This command
applies only to the web-based authentication mode of Network Login.
Example
The following command enables Network Login logout-privilege:
enable netlogin logout-privilege
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Enables Network Login on a specified port in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
The VLAN you specify must exist and include the specified ports prior to enabling Network Login.
Only untagged ports are allowed to be configured for Network Login.
For campus mode login with web-based clients, the following conditions must be met:
• A DHCP server must be available, and a DHCP range must be configured for the port or ports in the
VLAN on which you want to enable Network Login.
• The switch must be configured as a RADIUS client, and the RADIUS server must be configured to
enable the Extreme Network Login capability.
For ISP mode login, no special conditions are required. A RADIUS server must be used for
authentication.
Network Login is used on a per port, per VLAN basis.In this case, Network Login can be enabled on
one port for each VLAN.
Example
The following command configures Network Login on port 9 in VLAN corp:
enable netlogin ports 9 vlan corp
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables Network Login session refresh.
Syntax Description
minutes Specifies the session refresh time for Network Login in minutes.
Default
Disabled, with a value of three minutes for session refresh.
Usage Guidelines
Network Login sessions can refresh themselves after a configured timeout. After the user has been
logged in successfully, a logout window opens which can be used to close the connection by clicking on
the LogOut link. Any abnormal closing of this window is detected on the switch and the user is logged
out after a time interval as configured for session refresh. The session refresh is enabled and set to three
minutes by default. The value can range from 1 to 255 minutes. When you configure the Network Login
session refresh for the logout window, ensure that the FDB aging timer is greater than the Network
Login session refresh timer.
This command applies only to the web-based authentication mode of Network Login.
Use this command without the minutes parameter to reset the session refresh value to the default.
Example
The following command enables Network Login session refresh and sets the refresh time to ten
minutes:
enable netlogin session-refresh 10
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable radius
enable radius
Description
Enables the RADIUS client on the switch.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
When enabled, all web and CLI logins are sent to the RADIUS servers for authentication. When used
with a RADIUS server that supports ExtremeWare CLI authorization, each CLI command is sent to the
RADIUS server for authorization before it is executed.
Example
The following command enables RADIUS authentication for the switch:
enable radius
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable radius-accounting
enable radius-accounting
Description
Enables RADIUS accounting.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
The RADIUS client must also be enabled.
Example
The following command enables RADIUS accounting for the switch:
enable radius-accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable ssh2
enable ssh2 {access-profile [<access profile> | none]} {port
<tcp_port_number>}
Description
Enables SSH2 server to accept incoming sessions from SSH2 clients.
Syntax Description
Default
The SSH2 feature is disabled by default.
Usage Guidelines
SSH2 enables the encryption of session data. You must be logged in as an administrator to enable SSH2,
and you must obtain and enter a Security License Key to enable the SSH2 feature. To obtain a Security
License Key, access the Extreme Networks website.
You can specify a list of predefined clients that are allowed SSH2 access to the switch. To do this, you
must create an access profile that contains a list of allowed IP addresses. To create an access profile, use
the create access-profile command. To configure an access profile, use the configure
access-profile add command.
Use the port option to specify a TCP port number other than the default.
To view the status of SSH2 sessions on the switch, use the show management command. The show
management command displays information about the switch including the enable/disable state for
SSH2 sessions.
Example
The following command enables the SSH2 feature, with access allowed based on the access profile
management:
enable ssh2 access-profile management
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable tacacs
enable tacacs
Description
Enables TACACS+ authentication.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
After they have been enabled, all web and CLI logins are sent to one of the two TACACS+ servers for
login name authentication and accounting.
Example
The following command enables TACACS+ user authentication:
enable tacacs
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable tacacs-accounting
enable tacacs-accounting
Description
Enables TACACS+ accounting.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
If accounting is used, the TACACS+ client must also be enabled.
Example
The following command enables TACACS+ accounting for the switch:
enable tacacs-accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable tacacs-authorization
enable tacacs-authorization
Description
Enables CLI command authorization.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
When enabled, each command is transmitted to the remote TACACS+ server for authorization before
the command is executed.
Example
The following command enables TACACS+ command authorization for the switch:
enable tacacs-authorization
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable trusted-mac-address
enable trusted-mac-address {vlan <vlan_name>}
Description
Enables the trusted-MAC feature at either the global level or at a VLAN level.
Syntax Description
vlan_name Specifies the name of a VLAN on which to enable the trusted-MAC feature.
Default
Disabled
Usage Guidelines
Use this command to enable the trusted-MAC feature at either the global level or at a VLAN-specific
level. If you specify the command without the VLAN option, the trusted-MAC feature is enabled for
VLAN-specific configurations. By disabling this feature with the disable trusted-mac-address
command does not remove the previous port-specific information.
enable trusted-mac-address
Example
The following command enables the trusted-MAC feature globally on the corp VLAN:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
enable web
enable web
Description
Enables both HTTP access to the switch and HTTPS on the default ports.
Syntax Description
This command has no parameters or variables.
Default
Enabled
Usage Guidelines
Use this command to enable HTTP and HTTPS access to the switch web pages on the default ports. The
default port for HTTP is port (80) and HTTPS is port (443).
Example
The following command enables HTTP and HTTPS on the default port:
enable web
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables HTTP access to the switch on the default HTTP port (80).
Syntax Description
This command has no parameters or variables.
Default
Enabled
Usage Guidelines
Use this command to enable HTTP access to the switch web pages.
Example
The following command enables HTTP on the default port:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Allows HTTP access on the specified (non-default) port.
Syntax Description
Default
N/A
Usage Guidelines
Use this command to set up an access profile for a particular port number to restrict HTTP usage.
Example
The following example enables HTTP access using the access-profile named open_web on port 120:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables secure HTTP access (HTTPS) to the switch on the default HTTPS port (443).
Syntax Description
This command has no parameters or variables.
Default
Enabled
Usage Guidelines
Use this command to allow users to connect using a more secure HTTPS connection.
Example
The following command enables HTTPS on the default port:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Allows HTTPS access on the specified (non-default) port.
Syntax Description
Default
N/A
Usage Guidelines
Use this command to set up an access profile for a particular port number to restrict HTTPS usage.
Example
The following example enables HTTPS access using the access-profile named secure_web on port 120:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
scp2
scp2 {cipher [3des | blowfish]} {port <portnum>} {debug <debug_level>}
<user>@ [<hostname> | <ipaddress>] :<remote_file> [configuration
{incremental} | image [primary | secondary] | bootrom]
Description
Initiates an SCP2 client session to a remote SCP2 server and copies a file from the remote system to the
switch.
Syntax Description
3des Specifies that the 3des cipher should be used for encryption. This is the
default.
blowfish Specifies that the blowfish cipher should be used for encryption.
portnum Specifies the TCP port number to be used for communicating with the SSH2
client. Default is port 22.
debug_level Specifies a debug level. Default is 0.
user Specifies a login name for the remote host.
host Specifies the name of the remote host.
ipaddress Specifies the IP address of the remote host.
remote file Specifies the name of the remote file to be copied to the switch.
configuration Specifies that the copied file is a switch configuration file. It the incremental
option is not specified, it replaces the current switch configuration.
incremental Specifies that the copied file should be handled like an incremental
configuration download (only the commands in the file are executed).
image Specifies that the copied file is an ExtremeWare image.
primary Specifies that the image should be placed in the primary image area.
secondary Specifies that the image should be placed in the secondary image area.
bootrom Specifies that the copied file is a bootrom image.
Default
N/A.
Usage Guidelines
You must be running a security-enabled version of ExtremeWare 7.2e or later (which is under Export
Control) in order to use the SCP2 command.
SSH2 does not need to be enabled on the switch in order to use this command.
This command logs into the remote host as <user> and accesses the file <remote_file>. You will be
prompted for a password from the remote host, if required.
CAUTION
You can download a configuration to an Extreme Networks switch using SCP. If you do this, you cannot
save this configuration. If you save this configuration and reboot the switch, the configuration will be
corrupted.
Example
The following command copies a configuration file from the file configpart1.save on host system1 to the
switch as an incremental configuration:
scp2 admin@system1:configpart1.save configuration incremental
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
scp2 configuration
scp2 {cipher [3des | blowfish]} {port <portnum>} {debug <debug_level>}
configuration <user>@ [<hostname> | <ipaddress>]:<remote_file>
Description
Copies the configuration file from the switch to a remote system using SCP2.
Syntax Description
3des Specifies that the 3des cipher should be used for encryption. This is the
default.
blowfish Specifies that the blowfish cipher should be used for encryption.
portnum Specifies the TCP port number to be used for communicating with the SSH2
client. Default is port 22.
debug_level Specifies a debug level. Default is 0.
user Specifies a login name for the remote host.
host Specifies the name of the remote host.
ipaddress Specifies the IP address of the remote host.
remote file Specifies the name of the file to be created on the remote host.
Default
N/A.
Usage Guidelines
You must be running a security-enabled version of ExtremeWare 7.2e or later (which is under Export
Control) in order to use the SCP2 command.
SSH2 does not need to be enabled on the switch in order to use this command. (SSH2 is enabled by
default if you are running a security-enabled version of ExtremeWare).
This command logs into the remote host as <user> and creates the file <remote_file>.
Example
The following command copies the switch configuration and saves it as file config1.save on host system1:
scp2 configuration admin@system1:config1.save
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show access-list
show access-list {<name> | port <portlist>}
Description
Displays access list information and real-time statistics.
Syntax Description
Default
Shows information for all access lists.
Usage Guidelines
To verify access list settings, you can view the access list configuration and see real-time statistics on
which access list entries are being accessed when processing traffic.
Example
The following command shows information on all current the access lists:
show access-list
Egress Port:
Ingress Ports: 2 3 4 5
In Profile: permit QOS=QP5
#show access-list port 2
Access-list "a1"
Access-mask: "f1"
MAC:
IP/mask:L4port: dest-ip=11.11.11.0/24:---- source-ip=none/--:----
Layer 2:
Layer 3/4:
Egress Port:
Ingress Ports: 2 3 4 5
In Profile: permit QOS=QP5
The following command shows real-time access list statistics for ingress ports 5-7:
show access-list port 5-7
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show access-mask
show access-mask {<name>}
Description
Displays information about a specific access mask or all access masks.
Syntax Description
Default
N/A
Usage Guidelines
None.
Example
The following example creates an access mask called MyIpMask. The show access-mask command
generates output similar to the following:
* Summit400-48t:38 # create access-mask MyIpMask
* Summit400-48t:39 # show MyIpMask
Access-mask with name "MyIpMask" created by user
MAC:
IP/mask:L4port:
Layer 2:
Layer 3/4:
Ports:
Precedence:
ACL/Rate-limit:
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show access-profile
show access-profile {<access profile>}
Description
Displays access-profile related information for the switch.
Syntax Description
Default
Shows all access profile information for the switch.
Usage Guidelines
None.
Example
The following command displays access-profile related information for access profile nosales:
show access-profile nosales
History
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the ARP-learning feature on a port in the given vlan.
Syntax Description
vlan name Specifies the vlan to which the rule applies.
Default
By default, arp-learning is enabled.
Usage Guidelines
None.
Example
N/A.
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on all platforms.
Description
Displays the ARP-learning configuration for a port in the given vlan.
Syntax Description
vlan name Specifies the vlan to which the rule applies.
portlist Specifies the ports to which the rule applies.
Default
By default, arp-learning is enabled.
Usage Guidelines
The first column of the show output displays the configuration of the VLAN and port. The second
column of the output display the ARP learning configuration on that port.
Example
The following example displays the arp-learning configuration on vlan1:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
show auth
show auth
Description
Displays the current authentication and accounting servers configured for management and netlogin
sessions.
Syntax Description
There are no arguments or variables for this command.
Default
N/A
Usage Guidelines
The output from this command displays the information about the type of authentication and
accounting used by the primary and secondary servers that are configured for that particular type of
session.
Example
The following example displays the authentication information:
show auth
Default configuration :
Using Radius servers for Authentication/Accounting
Primary Authentication Server : 172.16.1.2
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on all platforms.
show cpu-dos-protect
show cpu-dos-protect [ports <portnumber>]
Description
Displays the status of denial of service protection for a particular port or for the entire switch.
Syntax Description
portnumber Specifies one or more port numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
The output of this command only has valid values when the CPU DoS protection is enabled.
Example
The following command displays the status of denial of service protection on port 1.
show cpu-dos-protect
Port L3Miss L3Err Bcast IpUnkMcast Learn Curr Int Cfg Thr Cfg Int Pass
______________________________________________________________________
1 150 150 150 150 150 1 150 1 3
The output of this show command displays the following information, which can help you analyze the
type of activity coming across the port to the CPU:
• IP multicast unknown
These are IPMC packets that do not have corresponding IPMC FDB entries.
• Learning packets
These are packets that do not have a corresponding FDB entries.
• Current interval
The current time interval, less than or equal to the configured interval.
• Configured alert threshold
The maximum number of packets that can be sent to the CPU. This variable is equal to the configured
interval parameter in seconds for each traffic category.
• Configured interval
• Free pass indicator (Zero in this field indicates a free pass for three intervals after the port comes
up.)
• Trusted port status
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show enhanced-dos-protect
show enhanced-dos-protect [rate-limit | ipfdb] ports [<portlist> | all]
Description
Displays the status of the enhanced denial of service protection feature.
Syntax Description
Default
N/A.
Usage Guidelines
The output from this command displays status of the following enhanced denial of service protection
conditions:
• Enabled/Disabled
• Max. entries
• Current entries
• List of trusted/untrusted ports
• Rate limiting configuration
• Packet filtering statistics
Example
The following command shows global enhanced denial of service protection rate limit information:
show enhanced-dos-protect rate-limit
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
show netlogin
show netlogin {port <portlist> vlan <vlan name>}
Description
Shows status information for Network Login.
Syntax Description
portlist Specifies one or more port numbers. May be in the form 1, 2, 3-5, 1:5,
1:6-1:8.
vlan name Specifies the name of a VLAN.
Default
N/A.
Usage Guidelines
The information reported by this command is the following:
• Whether Network Login is enabled or disabled.
• The base-URL.
• The default redirect page.
• The logout privileges setting.
• The netlogin session-refresh setting and time.
• The MAC and IP address of supplicants
• The type of authentication, 802.1x or HTTP (web-based).
Example
The following command shows the summary Network Login information:
show netlogin
------------------------------------------------
Web-based Mode Global Configuration
------------------------------------------------
Base-URL : "network-access.net"
Default-Redirect-Page : "http://www.extremenetworks.com"
Logout-privilege : YES
Netlogin Session-Refresh : DISABLED ; 3 minutes
------------------------------------------------
------------------------------------------------
802.1x Mode Global Configuration
------------------------------------------------
Quiet Period : 60 secs
The following command shows the detailed Network Login information for the port 13 in the VLAN
Default:
show netlogin ports 13 "Default"
History
This command was modified to show the authentication type in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show radius
show radius {<ipaddress> | <hostname>}
Description
Displays the current RADIUS client configuration and statistics.
Syntax Description
ipaddress Specifies to display RADIUS server information from the server with this IP
address.
hostname Specifies to display RADIUS server information from this host.
Default
N/A.
Usage Guidelines
The output from this command displays:
• The status of the RADIUS authentication and accounting (enabled or disabled)
• The statistics for the configured primary and secondary servers
If you specify the ipaddress option, configuration and statistics for that server is displayed.
Example
The following command displays the current RADIUS client configuration and statistics:
show radius
Radius: enabled
Radius Accounting: enabled
Radius Server Connect Timeout sec: 3
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show radius-accounting
show radius-accounting {[<ipaddress> | <hostname>]}
Description
Displays the RADIUS accounting client configuration and statistics.
Syntax Description
ipaddress Specifies to display RADIUS server information from the server with this IP
address.
hostname Specifies to display RADIUS server information from this host.
Default
N/A.
Usage Guidelines
The output from this command displays:
• The status of the RADIUS accounting (enabled or disabled)
• The statistics for the configured primary and secondary servers
If you specify the ipaddress option, configuration and statistics for that server is displayed.
Example
The following command displays RADIUS accounting client configuration and statistics:
show radius-accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show rate-limit
show rate-limit {<name> | ports <portlist>}
Description
Displays information for a specific rate limit rule or for all rate limit rules.
Syntax Description
Default
N/A.
Usage Guidelines
If you do not specify a rate limit name, information for all the rate limit rules are displayed.
Example
The following example displays all rate limit information configured for the switch:
#show rate-limit
Rate-limit Access-mask Vlan QoS Limit Port Flags
r1 f1 10 5 DI-IP-P-EC
r2 f3 3 3 IP-P-ED
Flags: DM=Dest MAC, SM=Source MAC, ET=Ether Type,
T=TOS, C=Code Point, I=IP Protocol
DI=Dest IP, SI=Src IP, D4=Dest L4 Port, S4=Src L4 Port
MT=ICMP Type, MC=ICMP Code, EP=Egress Port
P=Permit, Q=Qosprofile, SC=Set Code-Point, SD=Set Dot.1p
ED=Exceed Drop, EC=Exceed Set Code-Point
#show rate-limit r1
Rate-Limit with name "r1" created by user
Access-mask: "f1"
MAC:
IP/mask:L4port: dest-ip=13.13.13.0/24:---- source-ip=none/--:----
Layer 2:
Layer 3/4:
Egress Port:
Ingress Ports: 5
In Profile: permit
Rate Limit: 10 Mbps
Out Profile: set code-point=0x2c
The following example shows information for the rate limit configured on port 5:
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show security-profile
show security-profile {<name>}
Description
Displays the configured parameters of the security profile
Syntax Description
Usage Guidelines
Use this command to show security profiles currently configured on the platform and all values
associated with each security profile. If no security profile name is entered, configuration parameters for
all security profiles will be displayed.
Examples
The following command displays the configuration for the all profiles:
show security-profile
Interfaces: 1
1:2:1,
Platform Availability
This command is available on Summit 300 seriesonly.
show ssl
show ssl {detail}
Description
Displays the Secure Sockets Layer (SSL) configuration.
Syntax Description
Usage Guidelines
Displays the following information:
• HTTPS port configured. This is the port on which the clients will connect.
• Result of a check to see whether the private key matches with the public key stored in the certificate.
• Length of RSA key (number of bits used to generate the private key)
The optional keyword detail, provides the same output as the show ssl command, plus the complete
certificate. Private key (in PEM format) will be displayed for users with administration privileges.
Examples
The following command displays the SSL configuration:
show ssl
The following command displays the SSL configuration with the complete certificate.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
show tacacs
show tacacs {[<ipaddress> | <hostname>]}
Description
Displays the current TACACS+ configuration and statistics.
Syntax Description
ipaddress Specifies to display TACACS+ server information from the server with this IP
address.
hostname Specifies to display TACACS+ server information from this host.
Default
N/A.
Usage Guidelines
The output from this command displays:
• The status of the TACACS+ authentication and accounting servers
• The statistics for the configured primary and secondary servers
If you specify the ipaddress option, configuration and statistics for that server is displayed.
Example
The following command displays TACACS+ client configuration and statistics:
show tacacs
TACACS+: enabled
TACACS+ Authorization: enabled
TACACS+ Accounting: enabled
TACACS+ Server Connect Timeout sec: 3
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show tacacs-accounting
show tacacs-accounting {[<ipaddress> | <hostname>]}
Description
Displays the current TACACS+ accounting client configuration and statistics.
Syntax Description
ipaddress Specifies to display TACACS+ accounting information from the server with this
IP address.
hostname Specifies to display TACACS+ accounting information from this host.
Default
N/A.
Usage Guidelines
The output from this command displays:
• The status of the TACACS+ accounting servers
• The statistics for the configured primary and secondary servers
If you specify the ipaddress option, configuration and statistics for that server is displayed.
Example
The following command displays TACACS+ accounting client configuration and statistics:
show tacacs-accounting
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
show trusted-mac-address
show trusted-mac-address [vlan <vlan_name>] [port <portlist>]
Description
Displays the status of the enabled and disabled keywords before displaying all of the configured
trusted-MAC addresses.
Syntax Description
vlan_name Specifies the name of the VLAN.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
N/A.
Usage Guidelines
Use this command to display the status of the enabled and disabled keywords before displaying all of
the configured trusted-MAC addresses.
Example
The following command displays trusted-MAC address information for the corp VLAN:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Displays information about dynamic MAC addresses on a VLAN.
Syntax Description
vlan_name Specifies the name of the VLAN.
Default
N/A.
Usage Guidelines
None.
Example
The following example shows the security settings for a VLAN named vsa-dksp.
* S24-FZ:6 # show vlan vsa-dksp security
Port Limit State Appeared Learnt Blackholed Locked
1 Unlimited Unlocked 7 7 0 0
2 Unlimited Unlocked 4 4 0 0
3 Unlimited Unlocked 0 0 0 0
4 Unlimited Unlocked 2 2 0 0
5 Unlimited Unlocked 0 0 0 0
6 Unlimited Unlocked 4 4 0 0
25 Unlimited Unlocked 13 13 0 0
26 Unlimited Unlocked 0 0 0 0
* S24-FZ:7 #
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
ssh2
ssh2 {cipher [3des | blowfish]} {port <portnum>} {compression [on | off]}
{user <username>} {debug <debug_level>} {<username>@} [<host> |
<ipaddress>] {<remote command>}
Description
Initiates an SSH2 client session to a remote SSH2 server.
Syntax Description
3des Specifies that the 3des cipher should be used for encryption. This is the
default.
blowfish Specifies that the blowfish cipher should be used for encryption.
portnum Specifies the TCP port number to be used for communicating with the SSH2
client. Default is port 22.
compression on specifies that data is to be compressed.
off specifies that compression is not to be used. Default is off.
username Specifies a login name for the remote host, as an alternate to the user@host
parameter.
debug_level Specifies a debug level. Default is 0
username Specifies a login name for the remote host. May be omitted if it is the same as
the username on the switch.
host Specifies the name of the remote host
ipaddress Specifies the IP address of the remote host
remote command Specifies a command to be passed to the remote system for execution.
Remote commands are not supported on switches. This option is only valid if
the remote system is a system, such as a UNIX workstation, that can accept
remote commands.
Default
N/A.
Usage Guidelines
You must be running a security-enabled version of ExtremeWare 7.2e or later (which is under Export
Control) in order to use the SSH2 client command.
SSH2 does not need to be enabled on the switch in order to use this command.
Typically this command is used to establish a secure session to a remote switch. You will be prompted
for your password. Once you have logged in successfully, all ExtremeWare commands you enter will be
executed on the remote switch. When you terminate the remote session, commands will then resume
being executed on the original switch.
The remote command option cannot be used with Extreme Networks switches. If you include a remote
command, you will receive an error message.
Example
The following command establishes an SSH2 session on switch engineering1:
ssh2 admin@engineering1
The following command establishes an SSH2 session with the switch Summit 400 over TCP port 2050
with compression enabled:
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the remote authentication for management sessions.
Syntax Description
This command has no arguments or variables.
Default
Unconfigured
Usage Guidelines
None.
Example
unconfigure auth mgmt-access
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the remote authentication for netlogin sessions.
Syntax Description
This command has no arguments or variables.
Default
Unconfigured.
Usage Guidelines
None.
Example
unconfigure auth netlogin
History
This command was first available in ExtremeWare 7.3.
Platform Availability
This command is available on the “e” series platforms.
unconfigure cpu-dos-protect
unconfigure cpu-dos-protect
Description
Resets denial of service protection configuration to default parameter values.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This command will not change whether denial of service protection is enabled or disabled. To enable or
disable denial of service protection, use the following commands:
enable cpu-dos-protect
disable cpu-dos-protect
The default values for the denial of service protection parameters are as follows:
Example
The following command resets the denial of service protection configuration to the default values:
unconfigure cpu-dos-protect
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Resets aging time configuration for enhanced denial of service protection to default values for the
selected ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default aging time is 30 seconds.
Usage Guidelines
Use this command to reset aging time to default values for selected untrusted ports. To verify
configuration, use the show enhanced-dos-protect ipfdb ports <portlist> command and view
data in the Aging column.
Example
The following command resets the aging time on port 2 to the default value, 30 seconds:
unconfigure enhanced-dos-protect ipfdb agingtime ports 2
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the cache size for enhanced denial of service protection to default parameter values.
Syntax Description
This command has no arguments or variables.
Default
The default cache size value is 256 (in kilobytes).
Usage Guidelines
Enhanced DoS Protection maintains the number of IPFDB entries according to the cache-size limit. Use
this command to reset the cache size to the default of 256K.
Use the following command to set the cache-size to something other than the 256K default value:
Example
The following command resets the cache size to the 256K default value:
unconfigure enhanced-dos-protect ipfdb cache-size
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the learning limit for enhanced denial of service protection to default parameter values for the
selected ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default learn-limit on Fast Ethernet ports is 100 pkts/learn window.
The default learn-limit on Gigabyte ports is 100 pkts/learn window.
Usage Guidelines
Use this command to reset to default the learning limit value that defines the number of packets to be
counted before ExtremeWare can create an IPFDB entry in the hardware.
To configure the learning limit on untrusted ports for enhanced denial of service protection, use the
following command:
Usage Guidelines
Use this command to reset the learning limit value to the default number of packets being counted
before the software can create an entry in hardware.
Example
The following command resets the learn limit on Fast Ethernet port 3 to 100 packets within the learning
window before an IPFDB entry can be created:
unconfigure enhanced-dos-protect ipfdb learn-limit ports 3
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the learning window on untrusted ports for the enhanced denial of service protection IPFDB
learning qualifier to default values for the selected ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default learning window is 10 seconds.
Usage Guidelines
Use this command to reset the IPFDB learning window values for selected untrusted ports to the
default value of 10 seconds. To verify configuration, use the show enhanced-dos-protect ipfdb
ports <portlist> command.
Example
The following command resets the learning window on port 2 to the default value, 10 seconds:
unconfigure enhanced-dos-protect ipfdb learn-window ports 2
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the enhanced denial of service protection to the default trusted value for selected ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a
list of slots and ports. On a stand-alone switch, can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
By default, ports are trusted.
Usage Guidelines
Use this command to reset the enhanced denial of service protection to the default value for selected
ports. The default value is trusted.
You can configure each port as trusted or untrusted by using the configure enhanced-dos-protect
ports command. A trusted port behaves as a normal port. An untrusted port behaves according to the
configuration parameter used in IPFDB thrashing.
Verify the status of each port by using the show enhanced-dos-protect ports <portlist>
command.
Example
The following command resets a range of ports to trusted, so that enhanced denial of service protection
is not applied to ports 2 through 4:
unconfigure enhanced-dos-protect ports 2-4
History
This command was first available in ExtremeWare 7.3s
Platform Availability
This command is available on the “e” series platforms.
Description
Removes ports from rate limiting or resets the rate limiting configuration for enhanced denial of service
protection to default parameter values for the selected ports.
Syntax Description
threshold Resets to the default value the number of packets allowed on a given port within the
learning window before the rate limit is applied. The default on Fast Ethernet ports is
100 pkts/learn window. The default on Gigabyte ports is 100 pkts/learn window.
drop-probability Resets to the default value the percentage of slow-path traffic to be dropped per port.
The default value is 50 percent.
learn-window Resets to the default value the number of seconds for the learning window per port.
This value is the duration of time to be considered to reach the rate limit threshold.
The default value is 10 seconds.
protocol [all | icmp] Resets to the default value the protocol packets to which rate limiting is applied. By
default, rate limiting is applied to Internet Control Message Protocol (ICMP) packets.
portlist Specifies one or more ports or slots and ports. On a modular switch, can be a list of
slots and ports. On a stand-alone switch, can be one or more port numbers. May be
in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default threshold on Fast Ethernet ports is 100 pkts/learn window.
The default threshold on Gigabyte ports is 100 pkts/learn window.
The default drop-probability is 50 percent.
The default learn-window value is 10 seconds.
Rate limiting is applied by default to ICMP packets.
Usage Guidelines
Use this command to remove ports from rate limiting, or reset the rate-limit threshold, drop probability,
learning window, or packet protocol. To verify settings, use the show enhanced-dos-protect
rate-limit command.
Example
The following command resets the rate limiting threshold on Fast Ethernet port 3 to the default value,
100 packets:
unconfigure enhanced-dos-protect rate-limit threshold ports 3
The following command resets the rate limiting drop probability on port 4 to the default value, 50
percent:
unconfigure enhanced-dos-protect rate-limit drop-probability ports 4
The following command resets the rate limiting learn window on ports 2 and 3 to the default value, 10
seconds:
unconfigure enhanced-dos-protect rate-limit learn-window ports 2,3
The following command resets the rate limiting protocol to the default value, ICMP packet types, on
ports 1 through 3:
unconfigure enhanced-dos-protect rate-limit protocol ports 1-3
The following command removes ports 1 through 4 from rate limiting:
unconfigure enhanced-dos-protect rate-limit ports 1-4
History
This command was first available in ExtremeWare 7.3s
Platform Availability
This command is available on the “e” series platforms.
unconfigure radius
unconfigure radius {[primary | secondary] {server <ipaddress> |
<hostname>}}
Description
Unconfigures the RADIUS client configuration.
Syntax Description
Default
Unconfigures both the primary and secondary authentication servers.
Usage Guidelines
None.
Example
The following command unconfigures the secondary RADIUS server for the client:
unconfigure radius server secondary
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure radius-accounting
unconfigure radius-accounting {[primary | secondary] {server <ipaddress> |
<hostname>}}
Description
Unconfigures the RADIUS accounting client configuration.
Syntax Description
Default
Unconfigures both the primary and secondary RADIUS accounting servers.
Usage Guidelines
None.
Example
The following command unconfigures the secondary RADIUS accounting server for the client:
unconfigure radius-accounting server secondary
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure tacacs
unconfigure tacacs {[primary | secondary] {server [<ipaddress> |
<hostname>}}
Description
Unconfigures the TACACS+ client configuration.
Syntax Description
Default
Unconfigures both the primary and secondary TACACS+ servers.
Usage Guidelines
None.
Example
The following command unconfigures all TACACS+ servers for the client:
unconfigure tacacs
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure tacacs-accounting
unconfigure tacacs-accounting {[primary | secondary] server {<ipaddress> |
<hostname>}}
Description
Unconfigures the TACACS+ accounting client configuration.
Syntax Description
Default
Unconfigures both the primary and secondary TACACS+ accounting servers.
Usage Guidelines
None.
Example
The following command unconfigures all TACACS+ accounting servers for the client:
unconfigure tacacs-accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Clears the specified DHCP address range in the a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to unconfigure, or clear, the specified DHCP address in a VLAN.
A VLAN can have multiple DHCP address ranges; therefore, the start-addr parameter identifies the
DHCP address range for which the clearing needs to be done.
The DHCP address range is identified as the one whose starting IP address is the same as start-addr.
If start-addr is not provided, then the primary DHCP address range will be unconfigured.
Examples
Consider a VLAN named test with a primary subnet 40.0.0.x/24 and a secondary subnet 50.0.0.x/24.
Assume that for the primary subnet a DHCP address range is configured ranging from 40.0.0.5 -
40.0.0.40. Similarly, for the secondary subnet the DHCP address range is configured ranging from
50.0.0.5 - 50.0.0.40.
To unconfigure the DHCP Address range of the primary subnet, issue the following command:
To unconfigure the DHCP Address range with the start-addr as 50.0.0.5, issue the following command
NOTE
You can configure multiple DHCP address ranges for a VLAN. The start-addr option in the command
(50.0.0.5 in this example) specifies the exact DHCP address range for which the command applies. If
the last option is not specified, the command is applied for the primary subnet.
History
This command has been modified so that clearing of the secondary or remote address ranges is possible
(through the addition of the parameter start-addr). This enhanced command was made available in
ExtremeWare 7.3.0.
Platform Availability
This command is available on the “e” series platforms.
Description
Clears the DHCP options for the specified address range in a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to unconfigure, or clear, the DHCP options for the specified address range in a
VLAN.
A VLAN can have multiple DHCP address ranges; therefore, the start-addr parameter identifies the
DHCP address range that requires clearing of DHCP options.
The DHCP address range is identified as the range whose starting IP address is the same as
start-addr. If start-addr is not provided, then the DHCP options for the primary address range will
be cleared.
To configure DHCP options for the specified address range in a VLAN, use the following command:
Examples
Consider a VLAN named test with a primary subnet 40.0.0.x/24 and a secondary subnet 50.0.0.x/24.
Assume that for the primary subnet a DHCP address range is configured ranging from 40.0.0.5 -
40.0.0.40.
Similarly, for the secondary subnet the DHCP address range is configured ranging from 50.0.0.5 -
50.0.0.40. Assume that for the DHCP Address range 40.0.0.5 - 40.0.0.40 the DHCP gateway is configured
as 40.0.0.90. Similarly, assume that for the DHCP address range 50.0.0.5 - 50.0.0.40 the DHCP gateway
is configured as 50.0.0.90.
To unconfigure the DHCP options for the primary subnet, issue the following command:
To unconfigure the DHCP options for the DHCP address range starting from 50.0.0.5, issue the
following command:
NOTE
You can configure multiple DHCP address ranges for a VLAN. The start-addr option in the command
(50.0.0.5 in this example) specifies the exact DHCP address range for which the command applies. If
the last option is not specified, the command is applied for the primary subnet.
History
This command has been modified so that clearing the DHCP options for secondary or remote subnets is
possible (through the addition of the parameter start-addr). This enhanced command was made
available in ExtremeWare 7.3.0.
Platform Availability
This command is available on the “e” series platforms.
The switch software image contains the executable code that runs on the switch. An image comes
preinstalled from the factory. The image can be upgraded by downloading a new version from a Trivial
File Transfer Protocol (TFTP) server on the network.
A switch can store up to two images; a primary and a secondary image. You can download a new
image into either one of these, and you can select which image will load on the next switch reboot.
The configuration is the customized set of parameters that you have selected to run on the switch. As
you make configuration changes, the new settings are stored in run-time memory. To retain the settings,
and have them load when you reboot the switch, you must save the configuration to nonvolatile
storage.
A switch can store two different configurations: a primary and a secondary configuration. You can select
to which configuration you want the changes saved, and which configuration will be used on the next
switch reboot.
The BootROM initializes certain important switch variables during the switch boot process. In specific
situations, the BootROM can be upgraded by download from a TFTP server on the network.
Description
Configures the TFTP server(s) used by a scheduled incremental configuration download.
Syntax Description
primary Specifies that the following parameters refer to the primary TFTP server.
secondary Specifies that the following parameters refer to the secondary TFTP server.
ip address Specifies the IP address of the TFTP server from which the configuration
should be obtained.
hostname Specifies the hostname of the TFTP server from which the configuration
should be obtained.
filename Specifies the filename on the server that contains the configuration to be
downloaded.
Default
N/A.
Usage Guidelines
This command must be executed before scheduled configuration downloads can be performed.
Example
The following command specifies that scheduled incremental downloads into the primary configuration
space be done from the server named tftphost, from the ASCII file primeconfig.txt (residing in directory
\configs\archive on the server).
configure download server primary tftphost \configs\archive\prime_config.txt
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
download bootrom
download bootrom [<ip address> | <hostname>] <filename>
Description
Downloads a BootROM image from a TFTP server after the switch has booted. The downloaded image
replaces the BootROM in the onboard FLASH memory.
Syntax Description
Default
N/A.
Usage Guidelines
Upgrade the BootROM only when asked to do so by an Extreme Networks technical representative.
If this command does not complete successfully it could prevent the switch from booting. In the event
the switch does not boot properly, some boot option functions can be accessed through a special
BootROM menu (see Upgrading and Accessing BootROM).
Example
The following command downloads a bootROM image from the tftp server tftphost from the file
bootimages (residing in directory \images on the server):
download bootrom tftphost \images\bootimage
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
download configuration
download configuration [<ip address> | <hostname>] <filename> {incremental}
Description
Downloads a previously saved ASCII configuration file from a specific TFTP server host.
Syntax Description
ip address Specifies the IP address of the TFTP server from which the configuration
should be obtained.
hostname Specifies the hostname of the TFTP server from which the configuration
should be obtained.
filename Specifies the path and filename of a saved ASCII configuration.
incremental Specifies an incremental configuration download (v 6.0 or later).
Default
N/A.
Usage Guidelines
Unless you specify the incremental keyword, this command does a complete download, resetting the
current switch configuration and replacing it with the new downloaded configuration. You will be
prompted to reboot the switch after the download is complete. If you do not reboot when prompted, the
switch views the configuration file as corrupted and the next time you reboot the switch prompts you to
reset to the factory defaults.
Use the incremental keyword to specify an incremental or partial configuration download. In this case,
the commands specified in the incremental download file are executed, but configuration settings not
specified in the file are left intact. No reboot is required.
The new configuration information is stored in switch runtime memory, and is not retained if the switch
has a power failure. After the switch has rebooted, you should save the configuration to the primary or
secondary configuration area to retain it through a power cycle. You can include a save command at the
end of the configuration file to have the save done at the end of the download.
The file on the server is assumed to be located relative to the TFTP server base directory. You can
specify a path as part of the file name.
Example
The following command clears the current switch configuration, and downloads a new full
configuration from the tftp server tftphost. It uses the configuration from the file stdconfigs.txt residing in
the subdirectory configs\archive of the TFTP server base directory on the server:
download configuration tftphost configs\archive\stdconfig.txt
The following command downloads a partial configuration from the tftp server tftphost from the file
modifyconfig.txt (residing in the subdirectory configs\archive on the server):
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Cancels a scheduled incremental configuration download.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This command cancels the scheduled download command completely, not just the next scheduled daily
download. The download configuration every <hour> command must be issued again to
resume automatic downloads.
Example
The following command cancels a previously scheduled download:
download configuration cancel
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Automatically does an incremental configuration download every day at the specified time, or
immediately after switch bootup, based on the parameters specified in the configure download
server command.
Syntax Description
Default
N/A.
Usage Guidelines
You must run the configure download server command prior to using this command, to specify:
• The TFTP server and the configuration file from which the downloaded configuration will be
obtained.
• Whether this TFTP server is the primary server or the secondary (backup) TFTP server.
Example
The following commands set up a scheduled incremental download of the file config_info.txt, to be done
from the TFTP server named tftphost into the primary configuration area, every day at 10:00 pm:
configure download server primary tftphost config_info.txt
download configuration every 22:00
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
download image
download image [<hostname> | <ipaddress>] <filename> {primary | secondary}
Description
Downloads a new version of the ExtremeWare software image.
Syntax Description
hostname Specifies the hostname of the TFTP server from which the image should be
obtained.
ipaddress Specifies the IP address of TFTP server from which the image should be
obtained.
filename Specifies the filename of the new image.
primary Specifies that the new image should be stored as the primary image.
secondary Specifies that the new image should be stored as the secondary image.
Default
Stores the downloaded image in the current location (the location used for the last reboot).
Usage Guidelines
Prior to downloading an image, you must place the new image in a file on a TFTP server on your
network. Unless you include a path with the filename, this command assumes that the file resides in the
same directory as the TFTP server itself.
The switch can store up to two images: a primary image and a secondary image. When you download a
new image, you must select into which image space (primary or secondary) you want the new image to
be placed. If no parameters are defined, the software image is saved to the selected image, that is, the
next boot-up image.
Example
The following command downloads the switch software image from the TFTP server named tftphost,
from the file named s4119b2.xtr, to the secondary image store:
download image tftphost s4119b2.xtr secondary
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
save configuration
save configuration {primary | secondary}
Description
Saves the current configuration from the switch’s runtime memory to non-volatile memory.
Syntax Description
Default
Saves the current configuration to the location used on the last reboot.
Usage Guidelines
The configuration takes effect on the next reboot.
Example
The following command save the current switch configuration in the secondary configuration area:
save configuration secondary
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show configuration
show configuration [detail]
Description
Displays the currently active configuration to the terminal.
Syntax Description
Usage Guidelines
If the output scrolls off the top of the screen, you can use the enable clipaging command to pause the
display when the output fills the screen. The default for clipaging is enabled.
Example
This command shows the current configuration active in the switch:
show configuration detail
History
This command was available in ExtremeWare 7.1e.
The command was modified in ExtremeWare 7.2e to support the detail keyword.
Platform Availability
This command is available on the “e” series platforms.
unconfigure switch
unconfigure switch {all}
Description
Returns the switch configuration to its factory default settings.
Syntax Description
all Specifies that the entire current configuration should be erased, and the switch
rebooted.
Default
Resets configuration to factory defaults without reboot.
Usage Guidelines
Use unconfigure switch to reset the configuration to factory defaults, but without erasing the
configuration and rebooting. This preserves users account information, date and time settings, and so
on.
Include the parameter all to clear the entire current configuration, including all switch parameters, and
reboot using the last used image and configuration.
Example
The following command erases the entire current configuration, resets to factory defaults, and reboots
the switch using the last specified saved image and saved configuration:
unconfigure switch all
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
upload configuration
upload configuration [<ip address> | <hostname>] <filename> {every <time>}
Description
Uploads the current configuration to a TFTP server on your network.
Syntax Description
Default
Uploads the current configuration immediately.
Usage Guidelines
The filename can be up to 255 characters long, and cannot include any spaces, commas, quotation
marks, or special characters. Unless you include a path with the filename, this command places the file
in the same directory as the TFTP server itself.
The uploaded ASCII file retains the command-line interface (CLI) format. This allows you to do the
following:
• Modify the configuration using a text editor, and later download a copy of the file to the same
switch, or to one or more different switches.
• Send a copy of the configuration file to Extreme Networks Technical Support for problem-solving
purposes.
If every <time> is specified, the switch automatically saves the configuration to the server once per
day, at the specified time. Because the filename is not changed, the configured file stored in the TFTP
server is overwritten every day. The keyword every is required if a time is specified.
To cancel automatic upload, use the cancel option. If no options are specified, the current configuration
is uploaded immediately.
Example
The following command uploads the current configuration to the file configbackup.txt on the TFTP server
named tftphost, every night at 10:15 p.m.:
upload configuration tftphost configbackup.txt every 22:15
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Cancels a previously scheduled configuration upload.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This command cancels the scheduled upload command completely, not just the next scheduled daily
upload. You must re-issue the upload configuration every <hour> command to resume
automatic uploads.
Example
The following command cancels the current automatic upload schedule:
upload configuration cancel
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
use configuration
use configuration [primary | secondary]
Description
Configures the switch to use a previously saved configuration on the next reboot.
Syntax Description
Default
N/A.
Usage Guidelines
The keyword “configuration” can be abbreviated to “config.”
Example
The following command specifies that the next reboot should use the primary saved configuration:
use configuration primary
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
use image
use image [primary | secondary]
Description
Configures the switch to use a saved image on the next reboot.
Syntax Description
Default
Primary.
Usage Guidelines
None.
Example
The following command configures the switch to use the primary image on the next reboot:
use image primary
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
If you encounter problems when using your switch, ExtremeWare provides troubleshooting commands.
Use these commands only under the guidance of Extreme Networks technical personnel.
You can contact Extreme Networks technical support at (800) 998-2408 or (408) 579-2826.
The Event Management System (EMS), introduced in ExtremeWare 7.1.0, provides enhanced features to
filter and capture information generated on a switch. The various systems in ExtremeWare are being
converted to EMS components. As a system is converted, the corresponding debug trace command is no
longer available. Details of using EMS are discussed in the ExtremeWare User Guide, in the chapter,
“Status Monitoring and Statistics”, and the commands used for EMS are detailed in this document in
Chapter 8,“Commands for Status Monitoring and Statistics”.
Until all the systems in ExtremeWare are converted, you may need to use a mix of EMS and debug trace
commands under the guidance of Extreme Networks technical personnel.
Included in this chapter, as well as in Chapter 8, are the EMS commands to enable and disable debug
mode for EMS components.
If CPU utilization is high, use the debug trace commands sparingly, as they require the CPU. Disable
any external syslog before you configure a debug trace, because the debug trace utility can send large
amounts of information to the syslog, and if your syslog is external, that information travels over your
network. Alternatively, you can configure a filter to select only the most necessary information.
Configure a debug trace at lower levels first, and look for obvious problems. Higher levels typically
record so much information that they record enough information within a few seconds.
clear debug-trace
clear debug-trace
Description
Resets the debug-trace levels to the factory settings of level 0.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command resets the debug-trace levels to level 0:
clear debug-trace
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command provides system-level debug tracing for the accounting subsystem.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for accounting to 3:
configure debug-trace accounting 3
History
This command was first available in an ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for BOOTP relay errors to 3:
configure debug-trace bootprelay 3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command is not currently supported.
Syntax Description
Default
The default level is 0.
Usage Guidelines
This command is not currently supported.
Example
This command is not currently supported.
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Level 0 disables the debug-trace for link detection, and level 1 enables
debug-trace for link detection.
Example
The following command enables debug-trace for link detection:
configure debug-trace debug-link 1
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for flow redirect errors to 2:
configure debug-trace flow-redirect 2
<DBUG:SYST> Adding new flow for next hop ip 30.0.0.5 group fffe
<DBUG:SYST> Balancing group fffe
<DBUG:SYST> Adding new flow for next hop ip 30.0.0.5 group fffd
<DBUG:SYST> Balancing group fffd
<DBUG:SYST> Adding new flow for next hop ip 30.0.0.5 group fffb
<DBUG:SYST> Balancing group fffb
<DBUG:SYST> Looking for entries to balance in redirect 0
<DBUG:SYST> Entry Up: Adding new flow for next hop ip 30.0.0.5 group fffa
<DBUG:SYST> redirectServerListAdd 0 4
<DBUG:SYST> redirectServerListAdd 0 3
<DBUG:SYST> redirectServerListAdd 0 2
<DBUG:SYST> redirectServerListAdd 0 1
<DB UG:SYST> redirectServerListAdd 0 0
<INFO:SYST> msm-a-console admin: enable http1
<DBUG:SYST> redirectServerListDelEntry: Checking server entry 0x866c2efc 1 4
<DBUG:SYST> redirectServerListDelEntry 0x8 66c2f5c 0 4
<DBUG:SYST> redirectServerListDelEntry: Checking server entry 0x866c198c 2 4
<DBUG:SYST> redirectServerListDelEntry 0x866c19ec 0 4
<DBUG:SYST> redirectServerListDelEntry: Checking server entry 0x866c201c 3 4
<DBUG:SYST> redirectServerListDelEntry 0x866c207c 0 4
<DBUG:SYST> redirectServerListDelEntry: Freeing server entry 0x866c3efc 0 4
<DBUG:SYST> redirectServerListDelEntry 0x866c3f8c 0 4
<DBUG:SYST> Grps0 = 0 0 0 0 0 0 0 0
<DBUG:SYST> rLBS inst=0 inUse=1 SA=24.3.89.144 sMask=fffffff 8 dPort=50
<DBUG:SYST> Entry Down: Deleting sub flow for next hop ip 30.0.0.9 group fffe
<DBUG:SYST> Entry Down: Deleting sub flow for next hop ip 30.0.0.9 group fffd
<DBUG:SYST> Entry Down: Deleting sub flow for next hop ip 30.0.0.9 group fffb
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on all platforms.
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for IP ARP errors to 3:
configure debug-trace iparp 3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for RIP message errors to 3:
configure debug-trace rip-message 3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command is not currently supported.
Syntax Description
Default
The default level is 0.
Usage Guidelines
This command is not currently supported.
Example
This command is not currently supported.
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command records debug information to the syslog.
Syntax Description
Default
The default level is 0.
Usage Guidelines
The debug level range is 0 to 5. Higher levels record more verbose messages. Higher levels also record
the messages recorded at lower levels.
Example
The following command sets the reporting level for RIP triggered update errors to 3:
configure debug-trace rip-triggered-update 3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command is not currently supported.
Syntax Description
Default
The default level is 0.
Usage Guidelines
This command is not currently supported.
Example
This command is not currently supported.
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
This command records wireless information to the syslog.
Syntax Description
Default
N/A
Usage Guidelines
None.
Example
In the following example, port 1:8 is configured to record SNMP information:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
configure reboot-loop-protection
configure reboot-loop-protection threshold <time-interval> <count>
Description
Configures reboot loop protection.
Syntax Description
time-interval The length of time during which the switch can reboot the specified count before
entering minimal mode. The range is 0 - 255 minutes.
count The number of reboots within the specified time-interval. The range is 1 - 7.
Default
If you enter a time-interval but not a count, the default count is 3.
Usage Guidelines
Specifying a time interval of 0 disables reboot loop protection. Specifying any other value enables it. To
view the current settings, use the show switch or show configuration commands.
If you reboot the switch manually or use the run msm-failover or run diagnostics commands, the
time interval and count are both reset to 0.
Example
The following command configures the time interval to 5 minutes and the count to 4:
configure reboot-loop-protection threshold 5 4
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables debug mode. The switch stops generating debug events.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command disables debug mode. Debug mode must be enabled prior to configuring advanced
debugging capabilities. These include allowing debug messages, which can severely degrade
performance. For typical network device monitoring, debug mode should remain disabled, the default
setting. Debug mode should only be enabled when advised by technical support, or when advanced
diagnosis is required. The debug mode setting is saved to FLASH.
Example
The following command disables debug mode:
disable log debug-mode
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables debug mode. The switch generates debug events.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This command enables debug mode. Debug mode must be enabled prior to configuring advanced
debugging capabilities. These include allowing debug messages, which can severely degrade
performance. For typical network device monitoring, debug mode should remain disabled, the default
setting. Debug mode should only be enabled when advised by technical support, or when advanced
diagnosis is required. The debug mode setting is saved to FLASH.
Example
The following command enables debug mode:
enable log debug-mode
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
nslookup
nslookup <hostname>
Description
Displays the IP address of the requested host.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command looks up the IP address of a computer with the name of bigserver.xyz_inc.com:
nslookup bigserver.xyz_inc.com
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
ping
ping {udp} {continuous} {start-size <size number> {-<end_size}}
[<ip_address> | <hostname>] {from <src_ipaddress> | with record-route |
from <src_ipaddress> with record-route}
Description
Enables you to send User Datagram Protocol (UDP) or Internet Control Message Protocol (ICMP) echo
messages or to a remote IP device.
Syntax Description
udp Specifies that the ping request should use UDP instead of ICMP.
continuous Specifies that UDP or ICMP echo messages to be sent continuously. This
option can be interrupted by pressing any key.
size-number Specifies the size, in bytes, of the packet to be sent, or the starting size if
incremental packets are to be sent.
end_size Specifies the maximum size, in bytes, of the packet to be sent in the UDP or
ICMP request. When both the start_size and end_size are specified, ICMP
requests are transmitted using 1 byte increments, per packet.
ipaddress Specifies the IP address of the host.
hostname Specifies the name of the host.
src_ipaddress Uses the specified source address in the ICMP packet. If not specified, the
address of the transmitting interface is used.
record-route Decodes the list of recorded routes and displays them when the ICMP echo
reply is received.
Default
N/A.
Usage Guidelines
The ping command is used to test for connectivity to a specific host.
The ping command is available for both the user and administrator privilege level.
If a ping request fails, the switch continues to send ping messages until interrupted. Press any key to
interrupt a ping request.
Example
The following command enables continuous ICMP echo messages to be sent to a remote host:
ping continuous 123.45.67.8
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
run diagnostics
run diagnostics [extended | normal]
Description
Runs normal or extended diagnostics on the switch.
Syntax Description
extended Runs an extended diagnostic routine. Takes the switch fabric and ports offline,
and performs extensive ASIC, ASIC-memory, packet memory, and packet
loopback tests.
normal Runs a normal diagnostic routine. Takes the switch fabric and ports offline,
and performs a simple ASIC and packet loopback test on all the ports.
Default
N/A.
Usage Guidelines
NOTE
Run diagnostics when the switch can be brought off-line. The tests conducted are extensive and affect
traffic that must be processed by the system CPU.
The normal diagnostics are short series of tests that do not test all the internal ASIC functions. On a
management module, the extended diagnostic routine tests all components including the internal ASIC
functions. The management module is taken off-line while the diagnostic test is performed. It is reset
and operational once the test is completed.
To view results of normal or extended diagnostics tests, use the following commands:
show diagnostics
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Runs diagnostics on Ethernet cables.
Syntax Description
Default
N/A
Usage Guidelines
This command tests each of the four Unshielded Twisted-Pair (UTP). When the test completes, the
command prompts you to enter the show port portlist cable diagnostics command to see the results
of the test.
Examples
The following example tests the Ethernet cable inserted into port 1. The four copper pairs do not all
have the same length, which might indicate a kink in the cable, or a open connection:
The following example shows none of the twisted pairs terminate successfully at port 1, which could
indicate that the cable is not inserted into the port:
History
This command was introduced in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show debug-trace
show debug-trace [accounting | bootprelay | debug-link| | eaps-system | |
iparp | iproute | netlogin | npcard | npdiag | pppauth | ppphexdump
|radius | rip-message | rip-route-change | rip-triggered-update |snmp-trace
| stp-in-pdu | stp-out-pdu | stp-system |vrrp | vrrp-hello] vlan <vlan
name>
Description
Displays the configured debug-trace levels.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to display the debug trace level configured for a particular system, and VLAN. Some
of the debug trace systems commands can be applied to a particular VLAN, some apply to the switch as
a whole, so the vlan option is not available with all systems.
Example
The following command displays the debug trace levels configured:
show debug-trace
OSPF SPF 3
Flowstats 3
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show diagnostics
show diagnostics
Description
Displays the status from the last diagnostic test run on the switch.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to display the last diagnostic test run on the switch. The switch diagnostics are
displayed in a tabular format with the day, month, date, year, and time of the diagnostic test at the top
of the table.
Field Definitions
System Platform Specifies system type.
System Part No. Specifies system part number, revision level, and serial number.
Main Board No. Specifies main board part number, revision level, and serial number.
MAC Address Specifies system MAC address.
CPU System Indicates diagnostic results.
Registers Test Indicates diagnostic results.
Memory Test Indicates diagnostic results.
System Test Indicates diagnostic results.
Depending on the software version running on your switch, additional or different diagnostics
information might be displayed.
Example
------------------------------------------------------------------------
CPU System | Passed
------------------------------------------------------------------------
Registers Test | Passed
------------------------------------------------------------------------
Memory Test | Passed
------------------------------------------------------------------------
System Test | Passed
------------------------------------------------------------------------
History
This command was available in ExtremeWare 4.1.19, and in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the results of the last run cable diagnostics ports command.
Default
N/A
Syntax Description
Usage Guidelines
The results of the command display in tabular format:
Pair—Each Ethernet cable is comprised of four copper pairs of Unshielded Twisted-Pair (UTP). To have
a successful link, two of the four cables must have a status of Terminated and even lengths. The pairs are
labeled A through D. The output shows the test results of each pair.
Length—The length of the cable. All pairs should have the same length. An uneven length can indicate
a kink in the cable, or a broken connection.
Status—The result of the test. The status of Terminated indicates a successful completion. The status of
Open or Short indicates a failure in the cable.
Examples
The following example tests the Ethernet cable inserted into port 1:
The following example shows none of the twisted pairs terminate successfully at port 1:
History
This command was introduced in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show tech-support
show tech-support
Description
Displays the output of various show commands to assist in monitoring and troubleshooting the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
The show tech-support command displays the output for the following show commands:
• show version
• show switch
• show configuration
• show diag
• show fdb
• show iparp
• show ipfdb
• show ipstats
• show iproute
• show ipmc cache detail
• show ipmc fdb
• show igmp snooping detail
• show memory detail
• show log
It also displays the output from internal debug commands. This command disables the CLI paging
feature.
This information can be useful for your technical support representative if you experience a problem.
Depending on the software version running on your switch, additional or different show command
output is displayed.
Example
The following command displays the show command output on the switch:
show tech-support
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
top
top
Description
Displays real-time CPU utilization information by process.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Use this command to show the percentage of CPU processing devoted to each task, sampled every 30
seconds. In a healthy ExtremeWare system, only the BGTask takes up significant CPU processing power.
Investigate tasks showing consistent or periodic high CPU utilization.
You can change the display by typing a character while the display is active. These single character
commands are as follows:
Task Description
httpd The HTTP daemon task manages the HTTP web management interface on the
system.
Logpoll In an active dual CPU system, the master CPU will initiate the log polling task
(Logpoll) to periodically poll the secondary or slave CPU(s). This process clears the
individual syslogs and consolidates them onto the master CPU switch log.
mportTask The management port task.
pifstate The port interface state task (pifstate) processes port link state changes. It is
watchdog timer poll driven as opposed to interrupt driven by hardware events.
tAsyncSave The tAsyncSave tasks the NVRAM asynchronous save/write processing task. This
process manages the save or writes to the NVRAM.
tBgQosMon The background Quality of Service monitor task (tBgQosMon) is a background
version of the QoS monitoring task that monitors transmit count and kill count of
ports and cycles as long as the monitor is enabled.
tBGTask The background task (tBGTask) is the core task switching process. It receives
packets from the hardware ASICs and switches them to the appropriate functional
task to process that packet type or group. The tBGTask typically runs with a high
CPU utilization (90% or greater). It is constantly checking for packets to be sent up
by the hardware ASICs. It only releases control of the CPU if packets are sent to the
switch or if timer functions signal another task to become active.
tCardTask The I/O card event task (tCardTask) manages the event signaling hardware and
state machine for the I/O cards in a chassis-based system.
tChecksumPoll The checksum polling task (tChecksumPoll) periodically polls the boards for fabric
checksum errors.
tConsole The console task.
tdiagTask The diagnostic task (tdiagTask) executes the diagnostic routines for the particular
hardware platform.
tEapsTask The Ethernet automatic protection switching task implements and processes EAPS
on the switch.
tEdpTask The Extreme Discovery Protocol task (tEdpTask) implements and processes the EDP
neighbor discovery process.
tEsrpTask The Extreme Standby Router Protocol (tEsrpTask) implements and processes ESRP
on the switch.
tExcTask If the operating system recognizes an exception condition, it will invoke the exception
handling task (tExcTask).
tFastTimer The fast timer task (tFastTimer) is used to maintain a queue of timer events
triggering periodic or single event functions. These events have a small delay in time
between re-occurrences. The tFastTimer has a higher priority than the slow timer
task (tSlowTimer). Therefore, tFastTimer events are processed prior to iSlowTimer
events occurring at the same time.
tfdbAgeTask The forwarding database aging task (tfdbAgeTask) performs the aging of MAC FDB
entries in the hardware and software tables.
tIquery The iQuery support task for 3DNS (tIquery) processes iQuery requests.
TIRDP The ICMP router discovery protocol task (tIRDP) implements and processes IRDP on
the switch.
tISRtask The interrupt service routine task (tISRtask) manages the interrupt driven port link
state changes.
Task Description
tLinkEvent The link event task (tLinkEvent) is the interrupt driven link event processing task. It
handles hardware interrupts for link events.
tMACPoll The media access controller poll task (tMACPoll) polls the various MAC PHY chips
on the switch to pull up MAC layer control messages for the CPU to process.
tmt32LinkPoll F32F module link poll task.
tmuTelnetd The telnet daemon task.
tNetTask The network stack task (tNetTask) handles all the software-based processing of
packets including:
• Packets that cannot be handled by the switch's ASIC because the forwarding
tables do not have entries built in.
• Packets destined to the CPU for one of the router interfaces.
• Packets that must be examined or snooped by the CPUPackets detected for
copying to the CPU.
tospfMsgTask The OSPF message processing task (tospfMsgTask) implements and manages the
processing of OSPF messages.
tospfSpfTask The OSPF shortest path forward task (tospfSpfTask) executes the SPF algorithm run
processing for OSPF.
tospfTimer The OSPF timer task (tospfTimer) manages the internal timer trigger functions and
delays for OSPF.
tPCSPoll The tPCSPoll task services the Gigabit Ethernet PCS poll messages.
tPhyPoll The PHY layer poll task (tPhyPoll) polls the Road Runner PHY layer every 2
seconds to verify the proper operation.
tPortUtilization The port utilization data collection task (tPortUtilization) is a 30 second task that pulls
physical port data statistics from the hardware and updates the software database
tables.
tRip The Routing Information Protocol task (tRip) implements and processes RIP on the
switch.
tRipTimer The RIP timer task (tRipTimer) manages the internal timer trigger functions and
delays for RIP.
TRmonTask The remote monitoring task
tRRPoll The Road Runner poll task (tRRPoll) pulls the MAC and PHY layer statistics from the
store in the software based tables.
tRxMsgTask The receive message task (tRxMsgTask) is located on the secondary system.
ExtremeWare 6.2 commences use of the secondary CPU in BlackDiamond switches.
This is the secondary slave CPU inter-CPU receive task.
tShell The core operating system internal shell process (tShell) is spawned whenever the
internal shell is accessed.
tSlbFailover The server load balancing failover task.
tSlowTimer The slow timer task (tSlowTimer) maintains a queue of timer events triggering
periodic or single event functions. Typically these events have a large period gap in
terms of time between recurrences.
tsmartTrap Extreme smart trap task.
tSnmpd The SNMP daemon task manages all SNMP processing on the system.
tSntpc The simple network time protocol client task (tSntpc) implements the SNTP client
function and processing.
tsshshell The secure shell (SSH) task.
tStatsPoll The port interface statistics poll task (tStatsPoll) polls the port interfaces for statistic
counters.
Task Description
tstpTask The Spanning Tree protocol task (tstpTask) implements the STP algorithm and
processing.
tSwFault The software fault handler task (tSwFault) will perform a stack dump for any task that
has crashed.
tsyslogTask The system log task (tsyslogTask) receives messages/text from other tasks and
asynchronously logs these to the switch NVRAM log area.
tTimeout The Timeout task (tTimeout) is used to manage and execute various functions on
timeouts.
tTRRecv The trace route receiver task (tTrRecv) is spawned dynamically when the trace route
utility is used.
tvrrpTask The virtual router redundancy protocol task (tvrrpTask) implements and processes
VRRP on the switch.
Investigate tasks that, for no apparent reason, show CPU utilization consistently above 25% (except for
the BGTask). Configure the appropriate debug-trace command and look for messages indicating a
problem. Common problems are source or destination addresses.
Example
The following command displays the show command output on the switch:
top
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
This chapter describes commands for configuring and monitoring Ethernet Automatic Protection
Switching (EAPS).
To use EAPS, you must enable EDP on the switch and the EAPS ring ports.
The EAPS protocol provides fast protection switching to layer 2 switches interconnected in an Ethernet
ring topology, such as a metropolitan area network (MAN) or large campuses. EAPS protection
switching is similar to what can be achieved with the Spanning Tree Protocol (STP), but offers the
advantage of converging in less than a second when a link in the ring breaks.
To take advantage of the Spatial Reuse technology and broaden the use of the ring’s bandwidth, EAPS
supports multiple EAPS domains running on the ring at the same time.
EAPS operates by declaring an EAPS domain on a single ring. Any VLAN that warrants fault protection
is configured on all ring ports in the ring, and is then assigned to an EAPS domain. On that ring
domain, one switch, or node, is designated the master node, while all other nodes are designated as
transit nodes.
One port of the master node is designated the master node’s primary port (P) to the ring; another port is
designated as the master node’s secondary port (S) to the ring. In normal operation, the master node
blocks the secondary port for all non-control traffic belonging to this EAPS domain. If the master node
detects a break in the ring, it unblocks its secondary port and allows data traffic to be transmitted and
received through it.
EAPS fault detection on a ring is based on a single control VLAN per EAPS domain. This EAPS domain
provides protection to one or more data-carrying VLANs called protected VLANs. The control VLAN is
used only to send and receive EAPS messages; the protected VLANs carry the actual data traffic. As
long as the ring is complete, the EAPS master node blocks the protected VLANs from accessing its
secondary port.
When the master node detects a failure, it declares a “failed” state and opens its logically blocked
secondary port on all the protected VLANs. The master node also flushes its forwarding database (FDB)
and sends a message on the control VLAN to all of its associated transit nodes to flush their forwarding
databases.
Description
Adds the specified control VLAN to the specified EAPS domain.
Syntax Description
Default
N/A.
Usage Guidelines
You must configure one control VLAN for each EAPS domain. The control VLAN is used only to send
and receive EAPS messages.
The VLAN that will act as the control VLAN must be configured as follows:
• The VLAN must NOT be assigned an IP address, to avoid loops in the network.
• Only ring ports may be added as members of the control VLAN.
• The ring ports of the control VLAN must be tagged. This ensures that EAPS control VLAN traffic is
serviced before any other traffic and that control VLAN messages reach their intended destinations.
• The control VLAN must be assigned a QoS profile of QP8 with the QoS profile priority setting
HighHi.
Example
The following command adds the control VLAN “keys” to the EAPS domain “eaps_1.”
configure eaps eaps_1 add control vlan keys
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds the specified protected VLAN to the specified EAPS domain.
Syntax Description
Default
N/A.
Usage Guidelines
You must configure one or more protected VLANs for each EAPS domain. The protected VLANs are the
data-carrying VLANs.
When you configure the VLAN that will act as a protected VLAN, the ring ports of the protected VLAN
must be tagged (except in the case of the default VLAN). As long as the ring is complete, the master
node blocks the protected VLANs on its secondary port.
Example
The following command adds the protected VLAN “orchid” to the EAPS domain “eaps_1”:
configure eaps eaps_1 add protect vlan orchid
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes the specified control VLAN from the specified EAPS domain.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the control VLAN “keys” from the EAPS domain “eaps_1”:
configure eaps eaps_1 delete control vlan keys
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes the specified protected VLAN from the specified EAPS domain.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the protected VLAN “orchid” from the EAPS domain “eaps_1”:
configure eaps eaps_1 delete protect vlan orchid
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the value of the failtimer the master node uses for EAPS health-check packets.
Syntax Description
Default
The default is three seconds.
Usage Guidelines
Use the failtime keyword and its associated seconds parameter to specify the amount of time the
master node waits before the failtimer expires. The seconds parameter must be set greater than the
configured value for hellotime. The default value is three seconds.
Increasing the failtime value provides more protection by waiting longer to receive a health-check
packet when the network is congested.
NOTE
In previous versions of ExtremeWare, the secondary port on the Master node would open when the
failtimer expired. In ExtremeWare 7.1 the default behavior has been modified to not open the secondary
port. You can configure the action taken when the failtimer expires by using the configure eaps
failtime expiry-action command.
Example
The following command configures the failtimer value for the EAPS domain “eaps_1” to 15 seconds:
configure eaps eaps_1 failtime 15
History
This command was first available in ExtremeWare 7.2.e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the action taken when the failtimer expires.
Syntax Description
Default
Default is send-alert.
Usage Guidelines
In earlier releases of ExtremeWare, when the failtimer of a master node expired, the default action was
to open the secondary port. If the master node loses three Hello-PDUs in a row, the failtimer will expire,
but there might not necessarily be a break in the ring. Opening the secondary port in this situation
would create a loop.
The configure eaps failtime expiry-action command allows you to configure the action taken
when the failtimer expires.
By default the action is to send an alert if the failtimer expires. Instead of going into a “Failed” state, the
master node remains in a “Complete” or “Init” state, maintains the secondary port blocking, and writes
a critical error message to syslog warning the user that there is a fault in the ring. An SNMP trap is also
sent.
To use the failtimer expiry action of earlier releases, use the open-secondary-port parameter.
NOTE
You must explicitly configure the failtimer expiry action to open-secondary-port if the EAPS ring
includes a section composed of non-EAPS devices.
NOTE
If you have a previous release of ExtremeWare and are upgrading to ExtremeWare 7.3e the failtimer
expiry action will default to send-alert.
Example
The following command configures the failtimer expiry-action for EAPS domain “eaps_1”:
configure eaps eaps_1 failtime expiry-action open-secondary-port
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the value of the hello timer the master node used for the EAPS health-check packet.
Syntax Description
Default
Default is 1 second.
Usage Guidelines
Use the hellotime keyword and its associated seconds parameter to specify the amount of time the
master node waits between transmissions of health-check packets on the control VLAN. Increasing the
hellotime value keeps the processor from sending and processing too many health-check packets.
Increasing the hellotime value should not affect the network convergence time, because transit nodes
are already sending “link down” notifications.
This command applies only to the master node. If you configure the polling timers for a transit node,
they will be ignored. If you later reconfigure that transit node as the master node, the polling timer
values will be used as the current values.
Example
The following command configures the hellotime value for the EAPS domain “eaps_1” to 2 seconds:
configure eaps eaps_1 hellotime 2
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the switch as either the EAPS master node or as an EAPS transit node for the specified
domain.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command identifies this switch as the master node for the domain named eaps_1:
configure eaps eaps_1 mode master
The following command identifies this switch as a transit node for the domain named eaps_1:
configure eaps eaps_1 mode transit
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
This command is available on all platforms.
Description
Renames an existing EAPS domain.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command renames EAPS domain “eaps-1” to “eaps-5”:
configure eaps eaps-1 name eaps-5
History
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a node port as the primary or secondary port for the specified EAPS domain.
Syntax Description
Default
N/A.
Usage Guidelines
Each node on the ring connects through two ring ports. One port must be configured as the primary
port; the other must be configured as the secondary port.
Example
The following command adds port 1 to the EAPS domain “eaps_1” as the primary port:
configure eaps eaps_1 primary port 1
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the link ID of the shared port.
Syntax Description
Default
N/A.
Usage Guidelines
Each common link in the EAPS network must have a unique link ID. The controller and partner shared
ports belonging to the same common link must have matching link IDs. No other instance in the
network should have that link ID.
Example
The following command configures the EAPS shared port 1:1 to have a link ID of 1.
configure eaps shared-port 1:1 link-id 1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the mode of the shared port.
Syntax Description
Default
N/A.
Usage Guidelines
The shared port on one end of the common link must be configured to be the controller. This is the end
responsible for blocking ports when the common link fails thereby preventing the superloop.
The shared port on the other end of the common link must be configured to be the partner. This end
does not participate in any form of blocking. It is responsible for only sending and receiving
health-check messages.
Example
The following command configures the shared port 1:1 to be the controller.
configure eaps shared-port 1:1 mode controller
History
This command was first available in ExtremeWare 7.1.
Platform Availability
This command is available on the “e” series platforms.
create eaps
create eaps <name>
Description
Creates an EAPS domain with the specified name.
Syntax Description
Default
N/A.
Usage Guidelines
Only a single EAPS domain per switch is supported by Summit "e" series switches.
The name parameter is a character string of up to 32 characters that identifies the EAPS domain to be
created. EAPS domain names and VLAN names must be unique: Do not use the same name string to
identify both an EAPS domain and a VLAN.
Example
The following command creates EAPS domain eaps_1 on an “e” series switch:
create eaps eaps-1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Creates an EAPS shared port on the switch.
Syntax Description
Default
N/A.
Usage Guidelines
To configure a common link, you must create a shared port on each switch of the common link.
Example
The following command creates a shared port on the EAPS domain.
create eaps shared-port 2
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
delete eaps
delete eaps <name>
Description
Deletes the EAPS domain with the specified name.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes EAPS domain eaps_1:
delete eaps eaps-1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes an EAPS shared port on a switch.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes shared port 1.
delete eaps shared-port 1
History
Platform Availability
This command is available on the “e” series platforms.
disable eaps
disable eaps {<name>}
Description
Disables the EAPS function for a named domain or for an entire switch.
Syntax Description
Default
Disabled for the entire switch.
Usage Guidelines
None.
Example
The following command disables the EAPS function for entire switch:
disable eaps
The following command disables the EAPS function for the domain “eaps-1”:
disable eaps eaps-1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable eaps
enable eaps {<name>}
Description
Enables the EAPS function for a named domain or for an entire switch.
Syntax Description
Default
Disabled.
Usage Guidelines
EDP must be enabled on the switch and EAPS ring ports.
Example
The following command disables the EAPS function for entire switch:
enable eaps
The following command disables the EAPS function for the domain “eaps-1”:
enable eaps eaps-1
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
show eaps
show eaps {<name>} {detail}
Description
Displays EAPS status information.
Syntax Description
Default
N/A.
Usage Guidelines
If you enter the show eaps command without a keyword, the command displays less than with the
detail keyword.
Use the optional domain name parameter to display status information for a specific EAPS domain.
The output displayed by this command depends on whether the node is a transit node or a master
node. The display for a transit node contains information fields that are not shown for a master node.
Also, some state values are different on a transit node than on a master node.
State: On a transit node, the command displays one of the following states:
• Idle—The EAPS domain has been enabled, but the configuration is not
complete.
• Links-Up—This EAPS domain is running, and both its ports are up and in
the FORWARDING state.
• Links-Down—This EAPS domain is running, but one or both of its ports are
down.
• Preforwarding—This EAPS domain is running, and both of its ports are up,
but one of them is in a temporary BLOCKED state.
On a master node, the command displays one of the following states:
• Idle—The EAPS domain has been enabled, but the configuration is not
complete.
• Init—The EAPS domain has started but has not yet determined the status
of the ring. The secondary port is in a BLOCKED state.
• Complete—The ring is in the COMPLETE state for this EAPS domain.
• Failed—There is a break in the ring for this EAPS domain.
• [Failtimer Expired]—When the failtimer expires and it’s action is set to
send-alert, this flag is set. This flag indicates there is a misconfiguration or
hardware problem in the EAPS ring. The EAPS master node will continue
to remain in COMPLETE or INIT state with it’s secondary port blocking.
[Running: …] • Yes—This EAPS domain is running.
• No—This EAPS domain is not running.
Enabled: Indicates whether EAPS is enabled on this domain.
• Y—EAPS is enabled on this domain.
• N—EAPS is not enabled.
Mode: The configured EAPS mode for this switch: transit (T) or master (M).
Primary/Secondary port: The port numbers assigned as the EAPS primary and secondary ports. On the
master node, the port distinction indicates which port is blocked to avoid a
loop.
Port status: • Unknown—This EAPS domain is not running, so the port status has not yet
been determined.
• Up—The port is up and is forwarding data.
• Down—The port is down.
• Blocked—The port is up, but data is blocked from being forwarded.
Tag status: Tagged status of the control VLAN:
• Tagged—The control VLAN has this port assigned to it, and the port is
tagged in the VLAN.
• Untagged—The control VLAN has this port assigned to it, but the port is
untagged in the control VLAN.
• Undetermined—Either a VLAN has not been added as the control VLAN to
this EAPS domain or this port has not been added to the control VLAN.
Hello Timer interval: The configured value of the timer in seconds, specifying the time that the
master node waits between transmissions of health check packets.
Fail Timer interval: The configured value of the timer in seconds, specifying the time that the
master node waits before the failtimer expires.
Failtimer expiry action: Displays the action taken when the failtimer expires:
• Send-alert—Sends a critical message to the syslog when the failtimer
expires.
• Open-secondary-port—Opens the secondary port when the failtimer
expires.
Displays only for master nodes.
Preforwarding Timer interval:1 The configured value of the timer. This value is set internally by the EAPS
software.
Last update:1 Displayed only for transit nodes; indicates the last time the transit node
received a hello packet from the master node (identified by its MAC address).
EAPS Domain has … Controller Lists the assigned name and ID of the control VLAN.
Vlans:
EAPS Domain has … Protected Lists the assigned names and VLAN IDs of all the protected VLANs
Vlans:2 configured on this EAPS domain.
Number of Protected Vlans: The count of protected VLANs configured on this EAPS domain.
1. These fields apply only to transit nodes; they are not displayed for a master node.
2. This list is displayed when you use the detail keyword in the show eaps command.
Example
The following command displays detailed EAPS information for domain “eaps1”:
show eaps eaps1 detail
The results for domain “eaps1” on a master node are shown as follows:
Name: "eaps1" (instance=0)
State: Complete [Running: Yes]
Enabled: Yes Mode: Master
Primary port: 10 Port status: Up Tag status: Tagged
Secondary port: 20 Port status: Blocked Tag status: Tagged
Hello Timer interval: 1 sec Fail Timer interval: 3 sec
Fail timer expiry action: Send alert
Last update: From Master Id 00:04:96:18:40:92, at Wed Jan 28 15:58:20 2004
EAPS Domain has following Controller Vlan:
Vlan Name VID QosProfile
"cvlan" 0100 QP8
EAPS Domain has following Protected Vlan(s):
Vlan Name VID QosProfile
"pvlan" 0200 QP1
Number of Protected Vlans: 1
* Summit400-48t:67 #
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays shared-port information for one or more EAPS domains.
Syntax Description
Default
N/A.
Usage Guidelines
If you enter the show eaps shared-port command without an argument or keyword, the command
displays a summary of status information for all configured EAPS shared ports. You can use the detail
keyword to display more detailed status information about the segments and VLANs associated with
each shared port.
Example
The following command displays shared-port statistics on “eaps2”, “eaps3”, and “eaps4”: The EAPS
domain is in a “ready” state in this example:
show eaps shared-port
History
This command was first available in ExtremeWare.7.3e
Platform Availability
This command is available on the “e” series platforms.
Description
Displays summary information on one or more EAPS domains.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
Displays EAPS domains and associated info such as Domain Name, Domain State, EAPS Mode,
Enabled State, Control VLAN and VLAN ID and the Number of Protect VLANs in the domain. This is
helpful when viewing the status info for large numbers of EAPS domains quickly.
Example
The following command displays summary EAPS information on a transit node:
show eaps summary
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Unconfigures an EAPS link ID on a shared port on the switch.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command unconfigures the link ID on shared port 1.
unconfigure eaps shared-port 1 link-id
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Unconfigures the EAPS shared port mode.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command unconfigures the shared port mode on port 1.
unconfigure eaps shared-port 1 mode
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Sets the specified port’s internal configuration state to INVALID.
Syntax Description
Default
N/A.
Usage Guidelines
Unconfiguring an EAPS port sets its internal configuration state to INVALID, which causes the port to
appear in the Idle state with a port status of Unknown when you use the show eaps detail command
to display the status information about the port.
Example
The following command unconfigures this node’s EAPS primary ring port on the domain eaps_1:
unconfig eaps eaps_1 primary port
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
ESRP is a feature of ExtremeWare that allows multiple switches to provide redundant layer 3 routing
services to users. In addition to providing layer 3 routing redundancy, ESRP also provides for layer 2
redundancy. These “layered” redundancy features can be used in combination or independently. The
layer 2 redundancy features of ESRP offer fast failure recovery and provide for dual-homed system
design. In some instances, depending on network system design, ESRP can provide better resiliency
than using the Spanning Tree Protocol (STP) or Virtual Router Redundancy Protocol (VRRP).
Extreme switches that are not running ESRP, but are connected on a network that has other Extreme
switches running ESRP are ESRP-aware. This means that when Extreme switches are attached to the
ESRP-enabled switches, the non-ESRP switches reliably perform fail-over and fail-back scenarios in the
prescribed recovery times. No configuration of this feature is necessary.
NOTE
If you disable EDP on the switch, the switch is no longer ESRP-aware.
ESRP is configured on a per-VLAN basis on each switch. A maximum of four switches can participate
in providing redundant layer 3 or layer 2 services to a single VLAN. The switches exchange keep-alive
packets for each VLAN independently. Only one switch can actively provide layer 3 routing and/or
layer 2 switching for each VLAN. The switch performing the forwarding for a particular VLAN is
considered the “master” for that VLAN. Other participating switches for the VLAN are in slave mode.
To have two or more switches participate in ESRP, the following must be true:
• For each VLAN to be made redundant, the switches must have the ability to exchange packets on
the same layer 2 broadcast domain for that VLAN. Multiple paths of exchange can be used.
• For a VLAN to be recognized as participating in ESRP, the assigned IP address or the IPX NETid for
the separate switches must be identical. Other aspects of the VLAN, including its name, are ignored.
• ESRP must be enabled on the desired VLANs for each switch. ESRP cannot be enabled on the VLAN
“default.”
• Extreme Discovery Protocol (EDP) must be enabled on the ports that are members of the ESRP
VLANs. (The default setting is enabled.)
ESRP can also be enabled on super-VLANs. The super-VLAN must be configured with all the ports as
the sub-VLANs.
It is highly recommended that all switches participating in ESRP run the same version of ExtremeWare.
Not all ESRP features are available in all ExtremeWare software releases.
Extreme Loop Recovery Protocol (ELRP) is a feature of ExtremeWare that allows you to prevent, detect,
and recover from layer 2 loops in the network. You can use ELRP with other protocols such as ESRP.
With ELRP, each switch, except for the sender, treats the ELRP PDU as a layer 2 multicast packet. The
sender uses the source and destination MAC addresses to identify the packet it sends and receives.
When the sender receives its original packet back, that triggers loop detection and prevention. Once a
loop is detected, the loop recovery agent is notified of the event and takes the necessary actions to
recover from the loop. ELRP operates only on the sending switch; therefore, ELRP operates
transparently across the network.
NOTE
Because ELRP introduces the pre-master state to ESRP, you must upgrade all ESRP-enabled switches
within an ESRP domain to ExtremeWare 6.2.2b134 (or later) for ESRP to operate correctly. Earlier
ExtremeWare releases do not recognize the pre-master state.
Description
Clears the transmitted and received ELRP packet counters.
Syntax Description
Default
N/A.
Usage Guidelines
If you do not specify the optional vlan name parameter, you clear the system level ELRP counters, the
VLAN counters, and the global counters.
If you specify the optional vlan name parameter, you clear the counters for a specific VLAN.
Example
The following command clears the ELRP system counters:
clear elrp stats
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platform.
Description
Configures the ESRP port mode for ESRP host attach.
Syntax Description
Default
Normal.
Usage Guidelines
This feature is useful in dual-homed server environments in conjunction with high availability server
load-balancing (SLB) configurations.
Ports configured as normal ports do not accept or transmit Layer 2 or Layer 3 traffic when the local
ESRP device is a slave.
Ports configured as host ports allow configured ports that do not represent loops to the network to
continue operation independent of ESRP status. The command sets the port to forward, allowing those
ports directly attached to the slave’s hosts to communicate with other hosts that are connected to the
master. If you use load sharing with the host attach feature, configure all ports in the same load sharing
groups as host attach ports.
don’t-count has the effect of not counting the host ports and normal ports as active ports. This has the
convenience of minimal ESRP state changes due to frequent client activities like reboots and unplugging
laptops. If you use load sharing with the don’t count feature, configure all ports in the same load
sharing group as don’t count ports.
Example
The following command configures ports 1 through 5 as host ports, and prevents them from being
counted as active ports:
configure esrp port-mode host ports 1-5 don’t-count
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Adds a VLAN to an ESRP domain.
Syntax Description
Default
N/A.
Usage Guidelines
ESRP is performed in the domain master VLAN only, and not the other domain members. The domain
master VLAN controls member VLANs whether they are in forward or blocked states.
The domain master does not need to have all the ports as the domain members. Domain master VLANs
can have their own set of ports and the members can have different ports.
Example
The following command adds the domain member-VLAN sub_esrp1 to ESRP-enabled domain
master-VLAN esrp-super:
configure vlan esrp-super add domain-member vlan sub_esrp1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the ports of a VLAN where ELRP packet transmission is requested by ESRP.
Syntax Description
Default
All ports of an ESRP-enabled VLAN have ELRP transmission enabled.
Usage Guidelines
This command allows you to configure the ports in your network that might experience loops, such as
ports that connect to master, slave, or ESRP-aware switches, to receive ELRP packets. You do not need
to send ELRP packets to host ports.
Example
The following command enables ELRP packet transmission for ports 3-5 on VLAN esrp1:
configure vlan esrp1 add elrp-poll ports 3-5
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables port restart for a port.
Syntax Description
Default
N/A.
Usage Guidelines
To disable port restart, you either delete the ports and then add them again with the no-restart
option, or directly add the ports with the no-restart option.
Example
The following command disables port restart for ports 7-9 on VLAN esrp1:
configure vlan esrp1 add ports 7-9 no-restart
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures ESRP to restart ports if there is a state change and the downstream switch is from another
vendor.
Syntax Description
Default
N/A.
Usage Guidelines
If a VLAN becomes a slave, ESRP disconnects member ports that have port restart enabled. The
disconnection of these ports causes downstream devices to remove the ports from their FDB tables.
After 3 seconds the ports re-establish connection with the ESRP-enabled device. This feature allows you
to use ESRP in networks that include equipment from other vendors.
Example
The following command enables port restart for ports 7-9 on VLAN esrp1:
configure vlan esrp1 add ports 7-9 restart
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures backplane diagnostics failure tracking for an ESRP-enabled VLAN.
Syntax Description
Default
No diagnostic tracking.
Usage Guidelines
If a diagnostic failure is detected, the ESRP VLAN priority steps to the failover-priority value specified.
By setting the failover priority to be lower than the normal priority of the VLAN, it will cause the
affected VLAN to go into standby.
The range of the priority value is 0 to 254. Setting the priority to 255 configures the switch to slave
mode, and makes it ineligible to become the master. The switch will remain in slave mode even when
the VLAN fails over from the current master.
To make effective use of this feature, the normal priority of the ESRP-enabled VLANs must be higher
than the failover priority of this command.
Example
The following command enables diagnostic failure tracking, and specifies that the ESRP priority for
VLAN esrp-1 be set to 10 upon a diagnostic failure.
configure vlan esrp-1 add track-diagnostic failover 10
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures an ESRP-enabled VLAN to track environmental failures.
Syntax Description
Default
No environmental tracking.
Usage Guidelines
Environmental tracking tracks fan, power supply, and chassis temperature status.
If a failure is detected, the ESRP VLAN priority steps to the failover-priority value specified. By setting
the failover priority to be lower than the normal priority of the VLAN, it will cause the affected VLAN
to go into standby.
The range of the priority value is 0 to 254. Setting the priority to 255 configures the switch to slave
mode, and to be ineligible to become the master. The switch will remain in slave mode even when the
VLAN fails over from the current master.
To make effective use of this feature, the normal priority of the ESRP-enabled VLANs must be higher
than the failover priority of this command.
Example
The following command enables diagnostic failure tracking, and specifies that the ESRP priority for
VLAN esrp-1 be set to 10 upon a diagnostic failure.
configure vlan esrp-1 add track-environment failover 10
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures an ESRP-enabled VLAN or a VRRP VLAN to track a route entry in the kernel route table.
Syntax Description
Default
No route tracking.
Usage Guidelines
If the specified routes are not reachable, the device automatically relinquishes master status and remains
in slave mode (for ESRP) or backup mode (for VRRP).
This command can be used with both ESRP-enabled VLANs and VRRP VLANs.
Example
The following command enables IP route failure tracking for routes to the specified subnet:
configure vlan esrp-1 add track-iproute 192.168.46.0/24
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures an ESRP-enabled VLAN to track any available OSPF route.
Syntax Description
Default
No OSPF route tracking.
Usage Guidelines
The switch cannot be the ESRP master if none of the specified routes are reachable.
If no OSPF routes are detected, the ESRP VLAN priority steps to the failover-priority value specified. By
setting the failover priority to be lower than the normal priority of the VLAN, it will cause the affected
VLAN to go into standby.
The range of the priority value is 0 to 254. Setting the priority to 255 configures the switch to slave
mode, and to be ineligible to become the master. The switch will remain in slave mode even when the
VLAN fails over from the current master.
To make effective use of this feature, the normal priority of the ESRP-enabled VLANs must be higher
than the failover priority of this command.
Example
The following command enables OSPF route failure tracking, and specifies that the ESRP priority for
VLAN esrp-1 be set to 10 when all OSPF routes become unreachable:
configure vlan esrp-1 add track-ospf failover 10
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures an ESRP-enabled VLAN or VRRP VLAN to track an external gateway using ping.
Syntax Description
Default
No ping tracking. Default miss number for VRRP is 3 consecutive missed ping responses.
Usage Guidelines
If the external gateway is not reachable as indicated by consecutive ping failures, the device
automatically relinquishes master status and remains in slave mode (for ESRP) or backup mode (for
VRRP).
This command can be used with both ESRP-enabled VLANs and VRRP VLANs.
Example
The following command enables ping tracking for the external gateway at 10.207.29.17, pinging every 10
seconds, and considering the gateway to be unreachable if no response is received to 5 consecutive
pings:
configure vlan esrp-1 add track-ping 10.207.29.17 frequency 10 miss 5
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures an ESRP-enabled VLAN to track any available RIP route.
Syntax Description
Default
No RIP route tracking.
Usage Guidelines
If no RIP routes are detected, the ESRP VLAN priority steps to the failover-priority value specified. By
setting the failover priority to be lower than the normal priority of the VLAN, it will cause the affected
VLAN to go into standby.
The range of the priority value is 0 to 254. Setting the priority to 255 configures the switch to slave
mode, and to be ineligible to become the master. The switch will remain in slave mode even when the
VLAN fails over from the current master.
Example
The following command enables RIP route tracking, and specifies that the ESRP priority for VLAN
esrp-1 be set to 10 upon a diagnostic failure:
configure vlan esrp-1 add track-rip failover 10
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures an ESRP-enabled VLAN or a VRRP VLAN to track port connectivity to a specified VLAN.
Syntax Description
Default
Disabled.
Usage Guidelines
If no active ports remain on the specified VLANs, the device automatically relinquishes master status
and remains in slave mode (for ESRP) or backup mode (for VRRP).
This command can be used with both ESRP-enabled VLANs and VRRP VLANs.
Example
The following command enables ESRP-enabled VLAN esrp-1 to track port connectivity to VLAN
engineering:
configure vlan esrp-1 add track-vlan engineering
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Deletes a VLAN from an ESRP domain.
Syntax Description
Default
N/A.
Usage Guidelines
The domain master does not need to have all the ports as the domain members. Domain master VLANs
can have their own set of ports and the members can have different ports.
Example
The following command deletes the domain member-VLAN sub_esrp1 from ESRP-enabled domain
master-VLAN esrp-super:
configure vlan esrp-super delete domain-member vlan sub_esrp1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables ELRP packet transmission on ports of an ESRP-enabled VLAN.
Syntax Description
Default
All ports of an ESRP-enabled VLAN have ELRP transmission enabled.
Usage Guidelines
If you have host ports on an ESRP-enabled VLAN, you do not need to send ELRP packets to those
ports.
If you change your network configuration, and a port no longer connects to a master, slave, or
ESRP-aware switch, you can disable ELRP transmission on that port.
Example
The following command disables ELRP packet transmission for ports 3-5 on VLAN esrp1:
configure vlan esrp1 delete elrp-poll ports 3-5
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables diagnostics failure tracking for an ESRP-enabled VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command disables diagnostic failure tracking for VLAN esrp-1:
configure vlan esrp-1 delete track-diagnostic
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables environmental failure tracking.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command disables environmental failure tracking for VLAN esrp-1:
configure vlan esrp-1 delete track-environment
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables route table entry tracking for an ESRP-enabled VLAN or a VRRP VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
This command can be used with both ESRP-enabled VLANs and VRRP VLANs.
Example
The following command disables tacking of routes to the specified subnet for VLAN esrp-1:
configure vlan esrp-1 delete track-iproute 192.168.46.0/24
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables OSPF route tracking for an ESRP-enabled VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command disables OSPF route tracking for VLAN esrp-1:
configure vlan esrp-1 delete track-ospf
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables the tracking of an external gateway using ping.
Syntax Description
Default
N/A.
Usage Guidelines
This command can be used with both ESRP-enabled VLANs and VRRP VLANs.
Example
The following command disables ping tracking for the external gateway at 10.207.29.17:
configure vlan esrp-1 delete track-ping 10.207.29.17
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables RIP route tracking for an ESRP-enabled VLAN.
Syntax Description
Default
No RIP route tracking.
Usage Guidelines
None.
Example
The following command disables RIP route failure tracking for VLAN esrp-1:
configure vlan esrp-1 delete track-rip
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables the tracking of port connectivity to a specified VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
This command can be used with both ESRP-enabled VLANs and VRRP VLANs.
Example
The following command disables the tracking of port connectivity to VLAN engineering:
configure vlan esrp-1 delete track-vlan engineering
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables the use of ELRP by ESRP in the master state.
Syntax Description
Default
Disabled.
Usage Guidelines
Use this command to disable the use of ELRP by ESRP in the master state. When you disable ELRP, the
ESRP master switch no longer transmits ELRP PDUs to detect network loops.
Example
The following command disables the use of ELRP in the master state on the ESRP-enabled VLAN
elrp1:
configure vlan elrp1 esrp elrp-master poll disable
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Enables the use of ELRP by ESRP in the master state, and configures how often the master checks for
loops in the network.
Syntax Description
Default
• Use of ELRP in the master state—disabled
• Interval—1 second
Usage Guidelines
Use this command to enable the use of ELRP by ESRP in the master state. When an ESRP-enabled
switch is in the master state, and you enable elrp-master-poll, the switch periodically sends ELRP PDUs
at the configured interval level. If a loop is detected in the network, the transmitted PDUs are received
by the switch. The ESRP master switch then transitions to the slave state to break the network loop.
Specify the interval parameter to configure how often successive ELRP PDUs are sent while in the
master state. If you do not specify an interval value, the default value is used.
Example
The following command enables the use of ELRP in the master state on the ESRP-enabled VLAN elrp1:
configure vlan elrp1 esrp elrp-master poll enable
The following command configures the ESRP master to check for loops in the network every 3 seconds:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables the use of ELRP by ESRP in the pre-master state.
Syntax Description
Default
Disabled.
Usage Guidelines
Use this command to disable the use of ELRP by ESRP in the pre-master state. When you disable ELRP
in the pre-master state, the ESRP pre-master switch no longer transmits ELRP PDUs to detect network
loops prior to changing to the master state.
Example
The following command disables the use of ELRP in the pre-master state on the ESRP-enabled VLAN
elrp1:
configure vlan elrp1 esrp elrp-premaster poll disable
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Enables the use of ELRP by ESRP in the pre-master state, and configures how many times the switch
sends ELRP PDUs and how often the switch sends ELRP PDUS in the pre-master state.
Syntax Description
Default
• Use of ELRP in the pre-master state—disabled
• Count—3 times
• Interval—1 second
Usage Guidelines
Use this command to enable the use of ELRP by ESRP in the pre-master state to prevent network loops
from occurring. When an ESRP-enabled switch is in the pre-master state (waiting to become the master),
and you enable elrp-premaster-poll, the switch periodically sends ELRP PDUs at the configure level for
a specified number of times. If there is a loop in the network, the transmitted PDUs are received by the
switch. If this happens, the ESRP pre-master switch does not transition to the master state; rather, the
switch transitions to the slave state.
If you do not specify the optional count or interval parameters, the default values are used.
Example
The following command enables the use of ELRP in the pre-master state on the ESRP-enabled VLAN
elrp1:
configure vlan elrp1 esrp elrp-premaster poll enable
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the election algorithm on the switch.
Syntax Description
Default
ports_track_priority_mac election algorithm.
Usage Guidelines
The election algorithm determines the order of precedence of the election factors used to determine the
ESRP Master. The election factors are:
• Active Ports (ports): the number of active ports (the switch with the highest number takes priority)
• Tracking Information (track): whether the switch is using ESRP tracking. A switch using tracking
has priority.
• ESRP Priority (priority): a user-defined priority number between 0 and 254. A higher number has
higher priority. The default priority setting is 0. A priority setting of 255 makes an ESRP switch
remain in slave mode and is the recommended setting for system maintenance. A switch with a
priority setting of 255 will never become the master.
• MAC address (mac): the switch MAC address. A higher-number address has priority.
The election algorithm must be the same on all switches for a particular VLAN.
If a switch is master, it actively provides layer 3 routing services to other VLANs, and layer 2 switching
between all the ports of that VLAN. Additionally, the switch exchanges ESRP packets with other
switches that are in slave mode.
If a switch is in slave mode, it exchanges ESRP packets with other switches on that same VLAN. When
a switch is in slave mode, it does not perform layer 3 routing or layer 2 switching services for the
VLAN.
Example
The following command configures the election algorithm to use tracking information as the first
criteria for determining the ESRP master switch for VLAN esrp-1:
configure vlan esrp-1 esrp esrp-election track-ports-priority-mac
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the ESRP pre-master timeout value.
Syntax Description
Default
The default timeout is 6 seconds (three times the hello timer).
Usage Guidelines
The premaster-timer range is 0 - 512. If you set the premaster-timer to 0, ESRP uses the default. To
see the premaster-timer settings, use the show esrp vlan command.
CAUTION
Configure the pre-master state timeout only with guidance from Extreme Networks personnel.
Misconfiguration can severely degrade the performance of ESRP and your switch.
Example
The following command configures the pre-master timeout to 10 seconds for the VLAN esrp-1:
configure vlan esrp-1 esrp esrp-premaster-timeout 10
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the group number to be used for the ESRP VLAN.
Syntax Description
Default
The default group number is 0.
Usage Guidelines
Each group runs an instance of ESRP within the same VLAN or broadcast domain. A maximum of four
ESRP groups can be defined within the same networked broadcast domain. In addition a maximum of
four distinct ESRP groups can be supported on a single ESRP switch.You can configure a maximum of
32 ESRP groups in a network.
The most typical application for multiple ESRP groups is when two or more sets of ESRP switches are
providing fast-failover protection within a common subnet for two or more groups of users. An
additional use for ESRP groups is ESRP Host Attach; ESRP VLANs that share ESRP HA ports must be
members of different ESRP groups.
Example
The following command configures VLAN esrp-1 to be a member of ESRP group 2:
configure vlan esrp-1 esrp group 2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Enables selective forwarding on an ESRP-aware VLAN.
Syntax Description
Default
Disabled.
Usage Guidelines
An ESRP-aware switch floods ESRP PDUs to all ports in an ESRP-aware VLAN and the CPU. This
flooding increases the amount of network traffic because all ports receive ESRP PDUs, whether or not
they are connected to switches running the same ESRP group. To reduce the amount of traffic, you can
select the ports that receive ESRP PDUs by configuring selective forwarding on an ESRP-aware VLAN.
By configuring selective forwarding, you create a portlist for the ESRP groups associated with an
ESRP-aware VLAN, and that portlist is used for forwarding ESRP PDUs on the relevant ports only.
The ESRP group number must be the same as the ESRP-aware VLAN number.
If you specify the all or portlist options, the ports must be connected to switches running ESRP, and
the ports must connect to the ESRP master and slave switches.
When an ESRP-aware switch receives an ESRP PDU, the software will lookup the group to which the
PDU belongs and will forward the ESRP PDU to the group's portlist and the CPU.
Example
The following command configures ESRP-aware VLAN purple to receive ESRP PDUs on ports 1, 2, 3,
and 4:
configure vlan purple esrp group 1 add esrp-aware-ports 1-4
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables selective forwarding on an ESRP-aware VLAN.
Syntax Description
Default
Disabled.
Usage Guidelines
An ESRP-aware switch floods ESRP PDUs to all ports in an ESRP-aware VLAN and the CPU. This
flooding increases the amount of network traffic because all ports, regardless if they are connected to
switches running the same ESRP group or not, receive ESRP PDUs. To reduce the amount of traffic, you
can select the ports that receive ESRP PDUs by configuring selective forwarding on an ESRP-aware
VLAN. By configuring selective forwarding, you create a portlist for the ESRP groups associated with
an ESRP-aware VLAN, and that portlist is used for forwarding ESRP PDUs on the relevant ports only.
If all ports are removed from the esrp-aware-ports list, selective forwarding is disabled.
Example
The following command disables selective forwarding for ESRP-aware VLAN purple:
configure vlan purple esrp group 1 delete esrp-aware-ports 1-4
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the ESRP priority.
Syntax Description
Default
Priority = 0.
Usage Guidelines
The ESRP priority is one of the factors used by the ESRP election algorithm in determining which
switch is the Master switch.
The range of the priority value is 0 to 254, with 0 being the lowest priority, 254 being the highest. If the
ESRP priority is the determining criteria for the election algorithm, the highest priority value
determines which switch will act as master for a particular VLAN.
Setting the priority to 255 configures the switch to slave mode, and to be ineligible to become the
master. The switch will remain in slave mode even when the VLAN fails over from the current master.
This feature is typically used to ensure a switch cannot become the ESRP master while it is offline for
servicing.
Example
The following command configures the ESRP priority to the highest priority on VLAN esrp-1:
configure vlan esrp-1 esrp priority 254
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the ESRP timer values.
Syntax Description
Default
The default timervalue is 2 seconds.
Usage Guidelines
The timer specifies the interval, in seconds, for exchanging keep-alive packets between the ESRP
switches for this VLAN. A lower value specifies a more frequent exchange of keep-alive messages,
resulting in the faster detection of a failover condition. The timer setting must be configured identically
for the VLAN across all participating switches. If your configuration contains more than 2,500 ESRP
VLANs and 256,000 FDB entries, we recommend a timer setting greater than 3 seconds.
The neighbor timeout specifies the amount of time that ESRP waits before considering the neighbor
down. The timeout value must be at least 3 times, but not more than 30 times the timervalue. Entering a
value outside of that range generates an error message.
In a large ESRP configuration, the slave ESRP VLAN might inadvertently become the master ESRP
VLAN. This can occur when FDB entries are flushed during a master-slave transition. To avoid this we
recommend the general neighbor timeout guidelines listed in Table 15.
Number of Domains Number of VLANs Number of Active ports Suggested Neighbor Timeout
64 1000 6 or more >8
48 or more 1500 4 or more > 10
48 or more 2000 4 or more > 11
Example
The following command configures the ESRP timer to 3 seconds and the ESRP neighbor timeout to 12
seconds:
configure vlan esrp-1 esrp timer 3 esrp-nbr-timeout 12
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables ESRP on a VLAN.
Syntax Description
Default
Disabled.
Usage Guidelines
None.
Example
The following command disables ESRP on the VLAN accounting:
disable esrp vlan accounting
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Enables ESRP on a VLAN.
Syntax Description
Default
Disabled.
Usage Guidelines
EDP must be enabled on all ports participating in ESRP.
Example
The following command enables ESRP on the VLAN esrp-1:
enable esrp vlan esrp-1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
show elrp
show elrp {<vlan name> | detail}
Description
Displays ELRP information.
Syntax Description
Default
N/A.
Usage Guidelines
If you enter the show elrp command without a keyword, the command displays the:
• Total number of clients registered with ELRP
• ELRP packets transmitted
• ELRP packets received
If you enter the detail keyword, more detailed status information for VLANs in the master and
pre-master states is displayed. If you enter a vlan name, the command displays ELRP information for
that specific VLAN.
The additional table output for the detail keyword or a specific VLAN name includes the following:
Example
The following command displays summary ELRP status information on the switch:
show elrp
The following command displays detailed ELRP status information on the switch:
show elrp detail
The following command displays the ELRP status information for VLAN uj-mas:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
show esrp
show esrp {detail}
Description
Displays ESRP configuration information.
Syntax Description
Default
Shows summary ESRP information.
Usage Guidelines
This command shows information about the state of an ESRP VLAN and its neighbors. This includes
information about tracked devices.
In addition to ESRP information, ELRP status information is also displayed. This includes information
about the master and pre-master states, number of transitions to the pre-master state, and the ports
where ELRP is disabled.
The output varies depending upon the configuration and the state of the switch:
• Standby switch—Information about the impending failover and the timeout is displayed
• none—Information about not participating in hitless failover is displayed
Example
The following command displays summary ESRP status information for the VLANs on the switch:
show esrp
It produces output similar to the following:
VLAN Name VID Virtual IP/IPX State Master MAC Addres NbrPri/Gr/Prt/In/TR/TP/T
uj-mas1 0001 192.169.1.1 Master 00:E0:2B:80:E6:00 1
070/10/004/00/01/00/02
The following command displays detailed ESRP status information for the VLANs on the switch:
show esrp detail
It produces output similar to the following:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
show esrp-aware-ports
show esrp-aware-ports {vlan <vlan name>}
Description
Displays the ESRP-aware VLAN(s), the ESRP group(s), and the ESRP-aware port(s) that receive ESRP
PDUs.
Syntax Description
Default
N/A.
Usage Guidelines
To reduce the amount of traffic, you can select the ports that receive ESRP PDUs by configuring
selective forwarding on ESRP-aware VLANs. By configuring selective forwarding, you create a portlist
of the ESRP groups associated with an ESRP-aware VLAN, and that portlist is used for forwarding
ESRP PDUs on the relevant ports only. Use the show esrp-aware-ports command to view the ESRP
group portlist that forwards ESRP PDUs.
Example
The following command displays selective forwarding statistics:
show esrp-aware-ports
VLAN tt
--------
ESRP Group 0: 1:2 1:1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Displays ESRP-aware information for a specific VLAN.
Syntax Description
Default
Displays summary information for the VLAN.
Usage Guidelines
The display includes the group number, MAC address for the master of the group, and age of the
information.
Example
The following command displays ESRP-aware status information for ESRP-aware VLAN
demo-esrp-aware:
show esrp-aware vlan demo-esrp-aware
Summit48i:24 # sh esrp-aware
VLAN Interface: [demo-esrp-aware1]. DisableLearnTimeout=0 secs, Total-Fdb-Flushes=6
Last EsrpAware Fdb-Flush on Mon Nov 18 05:22:26 2002
Esrp-Group:0 Esrp-Master-Mac=00:01:30:08:36:00, Age=1 secs
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Displays ESRP configuration information for a specific VLAN.
Syntax Description
Default
Displays summary ESRP and ELRP information for the VLAN.
Usage Guidelines
None.
Example
The following command displays ESRP status information for ESRP-enabled VLAN demo-esrp:
show esrp vlan demo-esrp
It produces output similar to the following:
VLAN Interface(Layer 2): demo_esrp
Priority: 0 (Priority In Use: 0)
Active Ports: 2
Internal Ports: 0
Tracked Rt/Ping/LSP: 0
Tracked Ports: 0
Tracked Diag: -
Tracked Env: -
Tracked RIP: -
Tracked OSPF: -
Tracked BGP: -
Tracked LSP: None
ELRP in Premaster(Int, Cnt):Enabled(1, 3)
ELRP in Master(Int): Enabled(1)
Election Algorithm: ports-track-priority-mac
Group: 0
Hello Timer: 2
Esrp Nbr Timeout: 6
Premaster Timeout: 6
State: Enabled(Slave) on Mon Jun 2 10:09:48 2003
State Trans Counters: ToMaster:(1) ToPremaster:(1) ToSlave:(2)
The following command displays the ESRP counters for ESRP-enabled VLAN demo-esrp:
show esrp vlan demo-esrp counters
It produces output similar to the following:
VLAN=demo_esrp Current-time: Mon Jun 2 08:40:15 2003
Rx-Esrp-Pkts=0 Tx-Esrp-Pkts=0
Rx-Aware-Esrp-Pkts=0, Rx-Elrp-Pkts=0
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
The Spanning Tree Protocol (STP) is a bridge-based mechanism for providing fault tolerance on
networks. STP is a part of the 802.1d bridge specification defined by the IEEE Computer Society. To
explain STP in terms used by the 802.1d specification, the switch will be referred to as a bridge.
STP allows you to implement parallel paths for network traffic, and ensure that:
• Redundant paths are disabled when the main paths are operational.
• A redundant path is enabled if the main path fails.
The Rapid Spanning Tree Protocol (RSTP; 802.1w) provides an enhanced spanning tree algorithm that
improves the convergence speed of bridged networks. RSTP takes advantage of point-to-point links in
the network and actively confirms that a port can safely transition to the forwarding state without
relying on any timer configurations. If a network topology change or failure occurs, RSTP rapidly
recovers network connectivity by confirming the change locally before propagating that change to other
devices across the network. For broadcast links, there is no difference in convergence time between STP
and RSTP.
RSTP supersedes legacy STP protocols, supports the existing STP parameters and configurations, and
allows for seamless interoperability with legacy STP.
A port can belong to multiple STPDs. In addition, a VLAN can span multiple STPDs.
The key points to remember when configuring VLANs and STP are:
If you delete a STPD, the VLANs that were members of that STPD are also deleted. You must remove
all VLANs associated with the STP before deleting the STPD.
STPD Modes
An STPD has two modes of operation:
• 802.1d mode
Use this mode for backward compatibility with previous STP versions and for compatibility with
third-party switches using IEEE standard 802.1d. When configured in this mode, all rapid
configuration mechanisms are disabled.
• 802.1w mode
Use this mode for compatibility with Rapid Spanning Tree (RSTP). When configured in this mode,
all rapid configuration mechanisms are enabled. This mode is available for point-to-point links only.
RSTP is enabled or disabled on a per STPD basis only. You do not enable RSTP on a per port basis.
By default, the:
Port Modes
An STP port has three modes of operation:
• 802.1d mode
This mode is used for backward compatibility with previous STP versions and for compatibility with
third-party switches using IEEE standard 802.1d. BPDUs are sent untagged in 1D mode. Because of
this, on any given physical interface there can be only one STPD running in 1D mode.
• Limited Support for Extreme Multiple Instance Spanning Tree Protocol (EMISTP) mode
Normally EMISTP mode is an extension of STP that allows a physical port to belong to multiple
STPDs by assigning the port to multiple VLANs. BPDUs are sent with an 802.1Q tag having an
STPD instance Identifier (StpdID) in the VLANid field.
With this implementation on the “e” series of switches, EMISTP is limited to supporting a single
EMISTP domain per physical port, called Compatibility Mode. Compatibility mode is supported to
allow other switches using the full EMISTP mode to interoperate with the “e” series.
• Limited Support for PVST+ mode
This mode implements PVST+ in compatibility with third-party switches running this version of STP.
The STPDs running in this mode have a one-to-one relationship with VLANs, and send and process
packets in PVST+ format.
These port modes are for STP ports, not for physical ports. When a physical port belongs to multiple
STPDs, it is associated with multiple STP ports It is possible for the physical port to run in different
modes for different domains to which it belongs.
Description
Adds one or more VLANs, or a list of ports within a VLAN, to a specified STPD.
Syntax Description
Default
All ports are emistp mode, except those in STPD s0, whose default setting is dot1d mode.
Usage Guidelines
This command adds a list of ports within a VLAN to a specified STPD. If no ports are specified, the
entire VLAN is added.
Care must be taken to ensure that ports in overlapping domains do not interfere with the orderly
working of each domain’s protocol.
You must create a VLAN to add a VLAN to the STPD. To create a VLAN, use the create vlan <vlan
name> command.
You can create STP domains using the create stpd <name> command.
The keywords dot1d, emistp, and pvst-plus specify STP port modes:
• dot1d—In this mode, BPDUs are sent untagged in 802.1d mode. Because of this, on any given
physical interface there can be only one STPD running in 802.1d mode. This mode supports the
industry standard implementation, and can be used with non-Extreme devices. It can also be used
for backward compatibility with previous STP versions.
• emistp—This mode sends BPDUs with an 802.1Q tag having an STPD instance Identifier (StpdID) in
the VLANid field. This is an Extreme proprietary mode, and cannot be used with non-Extreme
devices. EMISTP is limited to supporting a single EMISTP domain per physical port., called
Compatibility Mode. Compatibility mode is supported to allow other switches using the full PVST+
mode to interoperate with “e” switches.
• pvst-plus—.This mode implements PVST+ in compatibility with third-party switches running this
version of STP. The STPDs running in this mode have a one-to-one relationship with VLANs, and
send and process packets in PVST+ format. Like EMISTP compatibility mode, PVST+ also is also
limited to supporting a single PVST+ domain per physical port. PVST+ compatibilty mode is
supported to allow other switches using the full PVST+ mode to interoperate with “e” switches.
An StpdID is used to identify each STP domain. You assign the StpdID when configuring the domain.
An StpdID must be identical to the VLANid of one of the member VLANs in that STP domain, and that
VLAN cannot belong to another STPD.
These port modes are for STP ports, not for physical ports. If it is in EMISTP or PVST+ compatibility
mode it is limited to a single physical port.
When the switch boots, it automatically creates a VLAN named default with a tag value of 1, and STPD
s0 with an StpdID of zero or none. The switch associates VLAN default to STPD s0. By default, all ports
that belong to this VLAN and STPD are in 802.1d mode.
Example
Create a VLAN named marketing and an STPD named STPD1 as follows:
create vlan marketing
create stpd stpd1
The following command adds the VLAN named marketing to the STPD STPD1:
configure stpd stpd1 add vlan marketing
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support STP port mode configurations. The
default port mode also changed from dot1d to emistp in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a VLAN from and STPD or one or more ports in the specified VLAN from an STPD.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes a VLAN named Marketing from the STPD STPD1:
configure stpd stpd1 delete vlan marketing
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
The default mode was changed from dot1d to emistp in ExtremeWare 7.3e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the time (in seconds) that the ports in this STPD spend in the listening and learning states
when the switch is the Root Bridge.
Syntax Description
Default
15 seconds.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
Example
The following command sets the forward delay from STPD1 to 20 seconds:
configure stpd stpd1 forwarddelay 20
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the time delay (in seconds) between the transmission of Bridge Protocol Data Units (BPDUs)
from this STPD when it is the Root Bridge.
Syntax Description
Default
2 seconds.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
Example
The following command sets the time delay from STPD1 to 10 seconds:
configure stpd stpd1 hellotime 10
History
This command was first available in ExtremeWare 6.2a ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the maximum age of a BPDU in the specified STPD.
Syntax Description
Default
20 seconds.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
Note that the time must be greater than, or equal to 2 * (Hello Time + 1) and less than, or equal to 2 *
(Forward Delay –1).
Example
The following command sets the maximum age of STPD1 to 30 seconds:
configure stpd stpd1 maxage 30
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the operational mode for the specified STP domain.
Syntax Description
Default
Operates in 802.1d mode.
Usage Guidelines
If you configure the STP domain in 802.1d mode, the rapid reconfiguration mechanism is disabled.
If you configure the STP domain in 802.1w mode, the rapid reconfiguration mechanism is enabled.
Example
The following command configures STPD s1 to enable the rapid reconfiguration mechanism and operate
in 802.1w mode:
configure stpd s1 mode dot1w
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the path cost of the port in the specified STPD.
Syntax Description
Default
The switch automatically assigns a default path cost based on the speed of the port, as follows:
• For a 10Mbps port, the default cost is 100.
• For a 100Mbps port, the default cost is 19.
• For a 1000Mbps port, the default cost is 4.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
The range for the cost parameter is 1 through 65,535. The switch automatically assigns a default path
cost based on the speed of the port.
Example
The following command configures a cost of 100 to ports 1 through 5 in STPD s0:
configure stpd s0 ports cost 100 1-5
History
This command was first available in ExtremeWare 6.2a and 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the ports in the specified STPD as auto, edge, broadcast or point-to-point link types.
Syntax Description
Default
All ports are broadcast link types.
Usage Guidelines
The default, broadcast links, supports legacy STP (802.1d) configurations.
If you configure a port to be an edge port, the port immediately enters the forwarding state. Edge ports
remain in the forwarding state unless the port receives a BPDU.
RSTP does not send any BPDUs from an edge port, nor does it generate topology change events when
an edge port changes its state.
RSTP rapidly moves the designated ports of a point-to-point link type into the forwarding state. This
behavior is supported by RSTP only.
An auto link behaves like a point-to-point link if the link is in full duplex mode or if link aggregation is
enabled on the port; otherwise, an auto link behaves like a broadcast link. If a non-STP switch exists
between several switches operating in 802.1w mode with auto links, the non-STP switch may negotiate
full duplex even though the broadcast domain extends over several STP devices. In this situation, an
802.1w port may advance to the “forwarding” state more quickly than desired.
If the switch operates in 802.1d mode, any configured port link type will behave the same as the
broadcast link type.
Example
The following command configures ports 1 through 4 to be point-to-point links in STPD s1:
configure stpd s1 ports link-type point-to-point 1-4
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the STP mode of operation for the specified port list.
Syntax Description
Default
Ports in the default STPD (s0) are dot1d mode. Ports in user-created STPDs are in emistp mode.
Usage Guidelines
None.
Example
The following command configures STPD s1 with dot1d packet formatting for port 1:
configure stpd s1 ports mode dot1d 1
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the port priority of the port in the specified STPD.
Syntax Description
Default
The default setting is 16.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
By changing the priority of the port, you can make it more or less likely to become the root port or a
designated port.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Example
The following command assigns a priority of 1 to ports 1 through 5 in STPD s0:
configure stpd s0 ports priority 1 1-5
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the bridge priority of the STPD.
Syntax Description
Default
32,768.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
By changing the priority of the STPD, you can make it more or less likely to become the root bridge.
The range for the priority parameter is 0 through 65,535. A setting of 0 indicates the highest priority.
Example
The following command sets the bridge priority of STPD1 to 16,384:
configure stpd stpd1 priority 16384
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Assigns an StpdID to an STPD.
Syntax Description
Default
N/A.
Usage Guidelines
You should not configure any STP parameters unless you have considerable knowledge and experience
with STP. The default STP parameters are adequate for most networks.
An StpdID is used to identify each STP domain. You assign the StpdID when configuring the domain.
An StpdID must be identical to the VLANid of one of the member VLANs in that STP domain, and that
VLAN cannot belong to another STPD. Unless all ports are running in 802.1d mode, an STPD must be
configured with an StpdID.
You must create and configure the VLAN, along with the tag, before you can configure the STPD tag. To
create a VLAN, use the create vlan command. To configure the VLAN, use the configure vlan
command.
In addition to the VLAN attributes that you will use in the STPD, you must first create an STPD. To
create an STPD, use the create stpd command.
Example
The following command assigns an StpdID to the purple_st STPD:
configure stpd purple_st tag 200
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a list of ports within a VLAN to a specified STPD.
Syntax Description
Default
All ports are in emistp mode, except those in STPD s0, whose default setting is dot1d mode.
Usage Guidelines
This command performs the same function as the configure stpd add vlan command with the ports
option included.
This command adds a list of ports within a VLAN to a specified STPD, and specifies the mode for those
ports.
• dot1d—In this mode, BPDUs are sent untagged in 802.1d mode. Because of this, on any given
physical interface there can be only one STPD running in 802.1d mode. This mode supports the
industry standard implementation, and can be used with non-Extreme devices. It can also be used
for backward compatibility with previous STP versions.
• emistp—This mode sends BPDUs with an 802.1Q tag having an STPD instance Identifier (StpdID) in
the VLANid field. This is an Extreme proprietary mode, and cannot be used with non-Extreme
devices. EMISTP is limited to supporting a single EMISTP domain per physical port., called
Compatibility Mode. Compatibilty mode is supported to allow other switches using the full PVST+
mode to interoperate with “e” switches.
• pvst-plus—This mode implements PVST+ in compatibility with third-party switches running this
version of STP. The STPDs running in this mode have a one-to-one relationship with VLANs, and
send and process packets in PVST+ format. Like EMISTP compatibility mode, PVST+ also is also
limited to supporting a single PVST+ domain per physical port. PVST+ compatibilty mode is
supported to allow other switches using the full PVST+ mode to interoperate with “e” switches..
These port modes are for STP ports, not for physical ports. When a physical ports belongs to multiple
STPDs, it is associated with multiple STP ports if it is in Dot1d mode. If it is in EMISTP or PVST+
compatiblity mode, it is limited to a single physical port. It is possible for the physical port to run in
different modes for different domains for which it belongs.
Example
The following command adds ports 2 and 3, members of a VLAN named Marketing, to the STPD named
STPD1, and specifies that they be in EMISTP mode:
configure vlan marketing add ports 2-3 stpd stpd1 emistp
History
This command was first available in ExtremeWare 7.2e
Platform Availability
This command is available on the “e” series platforms.
create stpd
create stpd <name>
Description
Creates a user-defined STPD.
Syntax Description
Default
The default device configuration contains a single STPD called s0.
When an STPD is created, the STPD has the following default parameters:
• State—disabled
• StpdID—none
• Assigned VLANs—none
• Bridge priority—32,768
• Max age—20 seconds
• Hello time—2 seconds
• Forward delay—15 seconds
• Operational mode—802.1d
• Rapid Root Failover—disabled state
• Port mode—Ports in the default STPD (s0) are 802.1d mode. Ports in user-created STPDs are in
emistp mode.
Usage Guidelines
Each STPD name must be unique, and cannot duplicate any other named elements on the switch (such
as VLANs, QoS profiles, Access profiles, or route maps). If you are uncertain about the VLAN profile
names on the switch, use the show vlan command to view the VLAN profiles. If you are uncertain
about QoS profile names on the switch, use the show qos <qos profile> command to view the QoS
profiles.
Each STPD has its own Root Bridge and active path. After the STPD is created, one or more VLANs can
be assigned to it.
Example
The following example creates an STPD named purple_st:
create stpd purple_st
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete stpd
delete stpd <spanning tree name>
Description
Removes a user-defined STPD from the switch.
Syntax Description
Default
N/A.
Usage Guidelines
If you remove an STPD, the VLANs that were members of that STPD are also deleted. An STPD should
only be removed if all VLANs have been deleted from it.
Example
The following command deletes an STPD named purple_st:
delete stpd purple_st
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Allows a VLAN to use STP port information.
Syntax Description
Default
Disabled.
Usage Guidelines
The vlan keyword is optional. To configure the switch to ignore the STP protocol and not block traffic
for the VLAN(s), see the following command: enable ignore-stp vlan <vlan name>.
Example
The following command disables the ignore-stp option on the VLAN accounting:
disable ignore-stp accounting
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable stpd
disable stpd {<spanning tree name>}
Description
Disables the STP protocol on a particular STPD or for all STPDs.
Syntax Description
Default
Disabled.
Usage Guidelines
All VLANs belong to an STPD. If you do not want to run STP on a VLAN, you must add the VLAN to
an STPD that is disabled.
The spanning tree name keyword is optional. You do not need to indicate an STPD name if you
disable the STP protocol for all STPDs.
To enable or re-enable the STP protocol on a particular STPD or on all STPDs, use the enable stpd
{<spanning tree name>} command.
Example
The following command disables an STPD named purple_st:
disable stpd purple_st
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables STP on one or more ports for a given STPD.
Syntax Description
Default
N/A.
Usage Guidelines
Disabling STP on one or more ports puts those ports in forwarding state; all Bridge Protocol Data Units
(BPDUs) received on those ports will be disregarded and dropped.
The portlist keyword is optional. You do not need to indicate a list of ports if you want to disable STP
on all ports in the STPD.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
You must create one or more STP domains, configure, and enable an STPD before you can use the
disable stpd ports command.
To enable STP on one or more ports for a given STPD, use the enable stpd <spanning tree name>
{ports <portlist>|vlan <vlan name> command.
Example
The following command disables port 4 on an STPD named Backbone_st:
disable stpd backbone_st ports 4
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables rapid root failover for STP recovery times.
Syntax Description
Default
Disabled.
Usage Guidelines
To view the status of rapid root failover on the switch, use the show stpd command. The show stpd
command displays information about the STPD configuration on the switch including the
enable/disable state for rapid root failover. To enable or re-enable rapid root failover for STP recovery
times, use the enable stpd <spanning tree name> rapid-root-failover command.
Example
The following command disables rapid root fail over on STPD Backbone_st:
disable stpd backbone_st rapid-root-failover
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the switch to ignore the STP protocol and not block traffic for the VLAN(s).
Syntax Description
Default
Disabled.
Usage Guidelines
This command is useful when multiple VLANs share the same physical ports, but only some of the
VLANs require STP protection. To allow a VLAN to use STP port information, use the disable
ignore-stp vlan <vlan name> command.
Example
The following command enables the ignore-stp option on the VLAN accounting:
enable ignore-stp accounting
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable stpd
enable stpd {<spanning tree name>}
Description
Enables the STP protocol for one or all STPDs.
Syntax Description
Default
Disabled.
Usage Guidelines
You must create one or more STP domains and configure an STPD before you can use the enable stpd
command. Use the create stpd <name> command to create an STPD.
The spanning tree name keyword is optional. You do not need to indicate an STPD name if you
enable the STP protocol for all STPDs
To disable the STP protocol on a particular STPD or on all STPDs, use the disable stpd {<spanning
tree name>} command.
The default port mode is emistp, which requires an StpdID. When using 802.1d, configure the mode of
all the ports to dot1d before enabling the domain.
Example
The following command enables an STPD named Backbone_st:
enable stpd backbone_st
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the STP protocol on one or more ports.
Syntax Description
Default
Enabled.
Usage Guidelines
If STPD is enabled for a port, Bridge Protocol Data Units (BPDUs) will be generated on that port if STP
is enabled for the associated STPD.
You must create and configure one or more STP domains before you can use the enable stpd ports
command. Use the create stpd <name> command to create an STP domain. If you have considerable
knowledge and experience with STP, you can configure the STPD using the configure stpd
commands. However, the default STP parameters are adequate for most networks.
To disable STP on one or more ports for a given STPD, use the disable stpd <spanning tree name>
{ports <portlist>|vlan <vlan name>} command.
The <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
Example
The following command enables port 4 on an STPD named Backbone_st:
enable stpd backbone_st ports 4
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables rapid root failover for faster STP recovery times.
Syntax Description
Default
Disabled.
Usage Guidelines
To view the status of rapid root failover on the switch, use the show stpd command. The show stpd
command displays information about the STPD configuration on the switch including the
enable/disable state for rapid root failover. To disable rapid root failover, use the disable stpd
<spanning tree name> rapid-root-failover command.
Example
The following command enables rapid root fail over on STPD Backbone_st:
enable stpd backbone_st rapid-root-failover
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show stpd
show stpd {<domain>}
Description
Displays STPD settings on the switch.
Syntax Description
Default
N/A.
Usage Guidelines
The command displays the following STPD information:
• STPD name
• STPD state
• STPD mode of operation
• Rapid Root Failover
• Tag
• Ports
• Active VLANs
• Bridge Priority
• Bridge ID
• Designated root
• STPD configuration information
You can create, configure, and enable one or more STP domains and use the show stpd command to
display STP configurations. Use the create stpd <name> command to create an STP domain. Use the
enable stpd {<spanning tree name>} command to enable an STPD. If you have considerable
knowledge and experience with STP, you can configure the STPD using the configure stpd
commands. However, the default STP parameters are adequate for most networks.
Example
The following command displays STPD settings on an STPD named Backbone_st:
show stpd backbone_st
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the STP state of a port.
Syntax Description
Default
N/A.
Usage Guidelines
This command displays the following:
• STPD port configuration
• STPD port mode of operation
• STPD path cost
• STPD priority
• STPD state (root bridge, and so on)
• Port role (root bridge, edge port, etc.)
• STPD port state (forwarding, blocking, and so on)
• Configured port link type
• Operational port link type
The, <portlist> can be one or more port numbers. For a detailed explanation of port specification, see
“Switch Numerical Ranges” in Chapter 1.
When an STPD is disabled on a port, the STPD port state is displayed as forwarding.
Example
The following command displays the state of port 4 on an STPD named Backbone_st:
show stpd Backbone_st ports 4
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the STP configuration of the ports assigned to a specific VLAN. It is an alternate syntax to the
show stpd <spanning tree name> ports vlan <vlan name> command.
Syntax Description
Default
N/A.
Usage Guidelines
If you have a VLAN that spans multiple STPDs, use this command to display the STP configuration of
the ports assigned to that specific VLAN.
Example
The following command displays the spanning tree configurations for the vlan Default:
show vlan default stpd
The following command displays the detailed spanning tree configurations for s0:
show stpd s0 ports detail
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure stpd
unconfigure stpd {<spanning tree name>}
Description
Restores default STP values to a particular STPD or all STPDs.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to restore default STP values to a particular STPD. If you want to restore default STP
values on all STPDs, do not specify a spanning tree name.
Example
The following command restores default values to an STPD named Backbone_st:
unconfigure stpd backbone_st
History
This command was first available in ExtremeWare 6.2a and ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
NOTE
Commands for enabling and disabling port restart and enabling and disabling failure tracking for VRRP
are described in Chapter 14, “ESRP Commands”.
Like ESRP, VRRP is a protocol that allows multiple switches to provide redundant routing services to
users. A virtual router is a group of one or more physical devices that acts as the default gateway for
hosts on the network. The virtual router is identified by a virtual router identifier (VRID) and an IP
address. All of the VRRP routers that participate in the virtual router are assigned the same VRID.
Extreme Networks’ VRRP implementation is compliant with RFC 2338, Virtual Router Redundancy
Protocol.
VRRP uses an election algorithm to dynamically assign responsibility for the master router to one of the
VRRP routers on the network. A VRRP router is elected master if one of the following is true:
• The router is the IP address owner (router that has the IP address of the virtual router configured as
its real interface address).
• The router is configured with the highest priority (the range is 1 - 255).
If the master router becomes unavailable, the election process provides dynamic failover and the backup
router that has the highest priority assumes the role of master.
If a tracking option is enabled, and the object being tracked becomes unreachable, the master device will
fail over. These tracking features are documented in the chapter on ESRP.
VRRP also supports port restart. Like the tracking features, the commands to enable and disable this
feature are described in the chapter on ESRP.
Description
Enables VRRP on a particular VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following enables VRRP on VLAN vrrp-1:
configure vrrp add vlan vrrp-1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Disables VRRP on one or all VLANs.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command disables VRRP on VLAN vrrp-1:
configure vrrp delete vlan vrrp-1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures the VRID instance on the VRRP VLAN as master or backup.
Syntax Description
Default
N/A.
Usage Guidelines
The IP address must be the same on all VRRP routers that make up the virtual router for this VLAN. If
the IP address is the same as the actual interface address of the device, this device is the IP address
owner, and is automatically elected as the master router as long as it remains functional.
Example
The following command sets up this device as the master router for VLAN vrrp-1, using IP address
192.168.1.3 as the virtual router IP address:
configure vrrp vlan vrrp-1 add master vrid 1 192.168.1.3
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures VRRP authentication.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command configures authentication for VRRP VLAN vrrp-1 with the password newvrrp:
configure vrrp vlan vrrp-1 authentication simple-password newvrrp
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Deletes one or all VRIDs.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the virtual router identified by VRID 2:
configure vrrp vlan vrrp-1 delete vrid 2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Configures VRRP parameters.
Syntax Description
Default
N/A.
Usage Guidelines
This command may be used to configure a VRRP router priority, advertisement interval, and preempt
mode.
The priority is used to determine which VRRP router takes over when the master fails over. A value of
255 is reserved for the router that is configured with the virtual router IP address. A value of 0 is
reserved for the master router’s use to indicate it is releasing responsibility for the virtual router.
The advertisement interval specifies the interval between advertisements sent by the master router to
inform the backup routers that it is alive. The master down interval is the interval that a backup router
waits after the last received advertisement before it determines that the master router is down.
If you have an extremely busy CPU, a short dual master situation can occur. To avoid this, increase the
advertisement interval.
The preempt mode controls whether a higher priority backup router preempts a lower priority master.
preempt allows preemption. dont_preempt prohibits preemption. The default setting is preempt. The
router that owns the virtual router IP address always preempts, independent of the setting of this
parameter.
Example
The following commands set a priority and advertisement interval for the VRRP router on VLAN
vrrp-1, and sets the preempt mode to disallow preemption:
configure vrrp vlan vrrp-1 vrid 2 priority 200
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
disable vrrp
disable vrrp
Description
Disables VRRP on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
This disables VRRP on the device. All virtual routers defined on this device will also be disabled.
Example
The following command disables VRRP on the device:
disable vrrp
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
enable vrrp
enable vrrp
Description
Enables VRRP on the switch.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
IGMP snooping must be enabled for VRRP to operate correctly. Use the following command to enable
IGMP snooping:
enable igmp snooping
Example
The following command enables VRRP on this device:
enable vrrp
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
show vrrp
show vrrp [vlan <vlan name> | all] {detail}
Description
Displays VRRP configuration information for one or all VLANs.
Syntax Description
Default
N/A.
Usage Guidelines
Use the detail option for a detailed display.
Example
The following command displays summary status information for VRRP:
show vrrp
It produces output similar to the following:
VRRP Router: Enabled
VLAN Name VRID Pri Virtual IP Addr State Master Mac Addres Prt/TR/TPr/W/M/T
demo_vr(En) 0001 100 192.168.1.1 MSTR 00:00:5E:00:01:01 1 0 0 Y Y 1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Description
Displays VRRP statistics for a particular VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays statistics for VLAN vrrp-1:
show vrrp vlan vrrp-1 stats
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on all platforms.
Extreme Networks switches provide full layer 3, IP unicast routing. They exchange routing information
with other routers on the network using either the Routing Information Protocol (RIP) or the Open
Shortest Path First (OSPF) protocol. The switches dynamically build and maintain routing tables and
determine the best path for each of its routes.
Each host that uses the IP unicast routing functionality of the switch must have a unique IP address
assigned. In addition, the default gateway assigned to the host must be the IP address of the router
interface.
The routing software and hardware directs IP traffic between router interfaces. A router interface is
simply a VLAN that has an IP address assigned to it.
As you create VLANs with IP addresses belonging to different IP subnets, you can also choose to route
between the VLANs. The VLAN switching and IP routing functions occur within the switch.
Each IP address and mask assigned to a VLAN must represent a unique IP subnet. You cannot
configure the same IP subnet on different VLANs.
The Extreme Networks switch maintains an IP routing table for network routes and host routes. The
table is populated from the following sources:
• Dynamically, by way of routing protocol packets or by ICMP redirects exchanged with other routers
• Statically, by way of routes entered by the administrator
— Default routes, configured by the administrator
— Locally, by way of interface addresses assigned to the system
— By other static routes, as configured by the administrator
Dynamic routes are typically learned by way of RIP or OSPF. Routers that use RIP or OSPF exchange
information in their routing tables in the form of advertisements. Using dynamic routes, the routing
table contains only networks that are reachable.
Dynamic routes are aged out of the table when an update for the network is not received for a period of
time, as determined by the routing protocol.
Static routes are manually entered into the routing table. Static routes are used to reach networks not
advertised by routers. You can configure up to 64 static unicast routes on the switch.
Static routes can also be used for security reasons, to control which routes you want advertised by the
router. Static routes are never aged out of the routing table.
A static route must be associated with a valid IP subnet. An IP subnet is associated with a single VLAN
by its IP address and subnet mask. If the VLAN is subsequently deleted, the static route entries using
that subnet must be deleted manually.
When there are multiple, conflicting choices of a route to a particular destination, the router picks the
route with the longest matching network mask. If these are still equal, the router picks the route using
the following criteria (in the order specified):
• Directly attached network interfaces
• ICMP redirects
• Static routes
• Directly attached network interfaces that are not active
If you define multiple default routes, the route that has the lowest metric is used. If there are multiple
default routes that have the same lowest metric, the system picks one of the routes.
You can also configure blackhole routes—traffic to these destinations is silently dropped.
Internet Control Message Protocol (ICMP) is used to transmit information needed to control IP traffic. It
is used mainly to provide information about routes to destination addresses. ICMP redirect messages
inform hosts about more accurate routes to other systems, whereas ICMP unreachable messages indicate
problems with a route.
Additionally, ICMP can cause TCP connection to terminate gracefully if the route becomes unavailable.
After IP unicast routing has been configured, you can configure the switch to forward Dynamic Host
Configuration Protocol (DHCP) or BOOTP requests coming from clients on subnets being service by the
switch and going to hosts on different subnets. This feature can be used in various applications,
including DHCP services between Windows NT servers and clients running Windows 95.
UDP-forwarding is a flexible and generalized routing utility for handling the directed forwarding of
broadcast UDP packets. UDP-forwarding allows applications, such as multiple DHCP relay services
from differing sets of VLANs, to be directed to different DHCP servers. The following rules apply to
UDP broadcast packets handled by this feature:
• If the UDP profile includes BOOTP or DHCP, the packet is handled according to guidelines in RFC
1542.
• If the UDP profile includes other types of traffic, these packets have the IP destination address
modified as configured, and changes are made to the IP and UDP checksums and decrements to the
TTL field, as appropriate.
If the UDP-forwarding is used for BOOTP or DHCP forwarding purposes, do not configure or use the
existing bootprelay function. However, if the previous bootprelay functions are adequate, you can
continue to use them.
To configure UPD-forwarding, you must first create a UDP-forward destination profile. The profile
describes the types of UDP packets (by port number) that are used and where they are to be forwarded.
You must give the profile a unique name, in the same manner as a VLAN, protocol filter, or Spanning
Tree Domain (STD).
Next, configure a VLAN to make use of the UDP-forwarding profile. As a result, all incoming traffic
from the VLAN that matches the UDP profile is handled as specified in the UDP-forwarding profile.
A maximum of 10 UDP-forwarding profiles can be defined. Each named profile may contain a
maximum of eight “rules” defining the UDP port, and destination IP address or VLAN. A VLAN can
Proxy Address Resolution Protocol (ARP) was first developed so that ARP-capable devices could
respond to ARP Request packets on behalf of ARP-incapable devices. Proxy ARP can also be used to
achieve router redundancy and simplify IP client configuration. The Extreme Networks switch supports
proxy ARP for this type of network configuration.
Once IP ARP is configured, the system responds to ARP Requests on behalf of the device, as long as the
following conditions are satisfied:
• The valid IP ARP Request is received on a router interface.
• The target IP address matches the IP address configured in the proxy ARP table.
• The proxy ARP table entry indicates that the system should always answer this ARP Request,
regardless of the ingress VLAN (the always parameter must be applied).
After all the proxy ARP conditions have been met, the switch formulates an ARP Response using the
configured MAC address in the packet.
In some networks, it is desirable to configure the IP host with a wider subnet than the actual subnet
mask of the segment. Proxy ARP can be used so that the router answers ARP Requests for devices
outside of the subnet. As a result, the host communicates as if all devices are local. In reality,
communication with devices outside of the subnet are proxied by the router.
clear iparp
clear iparp {<ip address> | vlan <vlan name>}
Description
Removes dynamic entries in the IP ARP table.
Syntax Description
Default
N/A.
Usage Guidelines
Permanent IP ARP entries are not affected.
Example
The following command removes a dynamically created entry from the IPARP table:
clear iparp 10.1.1.5/24
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
clear ipfdb
clear ipfdb {<ip address> <netmask>| vlan <vlan name>}
Description
Removes the dynamic entries in the IP forwarding database.
Syntax Description
Default
N/A.
Usage Guidelines
If no options are specified, all IP FDB entries are removed.
Example
The following command removes dynamically created entries in the IP forwarding database:
clear ipfdb 10.1.2.1/24
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the addresses to which BOOTP requests should be directed.
Syntax Description
Default
N/A.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward Dynamic Host
Configuration Protocol (DHCP) or BOOTP requests coming from clients on subnets being serviced by
the switch and going to hosts on different subnets. To configure the relay function, follow these steps:
1 Configure VLANs and IP unicast routing.
2 Enable the DHCP or BOOTP relay function, using the following command:
enable bootprelay
3 Configure the addresses to which DHCP or BOOTP requests should be directed, using the following
command:
configure bootprelay add <ip address>
Example
The following command configures BOOTP requests to be directed to 123.45.67.8:
configure bootprelay add 123.45.67.8
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms
Description
Removes one or all IP destination addresses for forwarding BOOTP packets.
Syntax Description
Default
N/A.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward Dynamic Host
Configuration Protocol (DHCP) or BOOTP requests coming from clients on subnets being serviced by
the switch and going to hosts on different subnets. To configure the relay function, follow these steps:
1 Configure VLANs and IP unicast routing.
2 Enable the DHCP or BOOTP relay function, using the following command:
enable bootprelay
3 Configure the addresses to which DHCP or BOOTP requests should be directed, using the following
command:
configure bootprelay add <ip address>
Example
The following command removes the destination address:
configure bootprelay delete 123.45.67.8
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the Dynamic Host Configuration Protocol (DHCP) relay agent option (option 82) information
checking in the DHCP reply packet.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward DHCP or BOOTP
requests coming from clients on subnets being serviced by the switch and going to hosts on different
subnets.
To configure the relay function and enable relay agent information checking in the DHCP reply packet,
follow these steps:
To disable the DHCP relay agent information checking in the DHCP reply packet, use the following
command:
Example
The following command configures DHCP relay agent option check:
configure bootprelay dhcp-agent information check
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the Dynamic Host Configuration Protocol (DHCP) relay agent option (option 82).
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward DHCP or BOOTP
requests coming from clients on subnets being serviced by the switch and going to hosts on different
subnets.
To disable the DHCP relay agent option (option 82), use the following command:
Example
The following command configures the DHCP relay agent option:
configure bootprelay dhcp-agent information option
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the Dynamic Host Configuration Protocol (DHCP) relay agent reforwarding policy.
Syntax Description
Default
Replace.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward DHCP or BOOTP
requests coming from clients on subnets being serviced by the switch and going to hosts on different
subnets.
To configure the relay function and the relay agent reforwarding policy, follow these steps:
To disable the DHCP relay agent reforwarding policy, using the following command:
Example
The following command configures the relay agent to drop the packets with existing relay agent
information:
configure bootprelay dhcp-agent information policy drop
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a permanent entry to the ARP table. Specify the IP address and MAC address of the entry.
Syntax Description
Default
N/A.
Usage Guidelines
Add a permanent IP ARP entry to the system. The ip address is used to match the IP interface
address to locate a suitable interface.
Example
The following command adds a permanent IP ARP entry to the switch for IP address 10.1.2.5:
configure iparp add 10.1.2.5 00:11:22:33:44:55
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the switch to respond to ARP Requests on behalf of devices that are incapable of doing so.
Up to 64 proxy ARP entries can be configured.
Syntax Description
Default
N/A.
Usage Guidelines
When mask is not specified, an address with the mask 255.255.255.255 is assumed. When mac_address
is not specified, the MAC address of the switch is used in the ARP Response. When always is specified,
the switch answers ARP Requests without filtering requests that belong to the same subnet of the
receiving router interface.
After IP ARP is configured, the system responds to ARP Requests on behalf of the device as long as the
following conditions are satisfied:
• The valid IP ARP Request is received on a router interface.
• The target IP address matches the IP address configured in the proxy ARP table.
• The proxy ARP table entry indicates that the system should always answer this ARP Request,
regardless of the ingress VLAN (the always parameter must be applied).
After all the proxy ARP conditions have been met, the switch formulates an ARP Response using the
configured MAC address in the packet.
Example
The following command configures the switch to answer ARP Requests for all devices with the address
range of 100.101.45.1 to 100.101.45.255:
configure iparp add proxy 100.101.45.0/24
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes an entry from the ARP table. Specify the IP address of the entry.
Syntax Description
Default
N/A.
Usage Guidelines
Removes any IP ARP entry (dynamic or permanent) from the table. The ip address is used to match
the IP interface address to locate a suitable interface.
Example
The following command deletes an IP address entry from the ARP table:
configure iparp delete 10.1.2.5
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes one or all proxy ARP entries.
Syntax Description
Default
Not Always.
Usage Guidelines
Proxy ARP can be used for two purposes:
1 To support host that cannot process ARP traffic. In this case, the switch answers the ARP Request for
that host.
2 To hide the IP topology from the host. The network administrator can configure a large network on
the host machine (16-bit mask) and a smaller network on each router interface (for example, 22-bit
mask). When the host sends ARP Request for another host on another subnet, the switch answers
the ARP Request and all subsequent traffic will be sent directly to the router.
You can configure up to 64 proxy ARP entries. When the mask is not specified, then software will
assume a host address (that is, a 32-bit mask). When the MAC address is not specified, then the
software uses the switch's MAC address as the proxy host. Always should be specified for type-1 usage,
not always is the default (type-2).
Example
The following command deletes the IP ARP proxy entry 100.101.45.0/24:
configure iparp delete proxy 100.101.45.0/24
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the maximum allowed IP ARP entries.
Syntax Description
Default
4096.
Usage Guidelines
Range: 1 - 20480. The maximum IP ARP entries include dynamic, static, and incomplete IP ARP
entries.
Example
The following command sets the maximum IP ARP entries to 2000 entries:
configure iparp max-entries 2000
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the maximum allowed incomplete IP ARP entries.
Syntax Description
Default
256.
Usage Guidelines
Range: 1 - 20480, but cannot be greater than the configured IP ARP max-entries value.
Example
The following command sets the maximum IP ARP entries to 500 entries:
configure iparp max-pending-entries 500
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the IP ARP timeout period.
Syntax Description
Default
20 minutes.
Usage Guidelines
A setting of 0 disables ARP aging.
Example
The following command sets the IP ARP timeout period to 10 minutes:
configure iparp timeout 10
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
configure ip-down-vlan-action
configure ip-down-vlan-action [consume | drop | forward]
Description
Configures the forwarding functionality destined to nonworking IP interfaces.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command configures the forwarding functionality destined to nonworking IP interfaces:
configure ip-down-vlan-action forward
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies which routes are deleted and reinstalled with a new gateway.
Syntax Description
clear-all Clears all IPFDB entries associated with a route if a more specific route
is installed.
clear-subnet Clears only the IPFDB entries associated with the new route’s subnet.
Default
The default is clear-all.
Usage Guidelines
To see the current setting, use the show ipconfig command.
Example
The following command clears only the IPFDB entries associated with the new route’s subnet:
configure ipfdb route-add clear-subnet
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a static address to the routing table.
Syntax Description
Default
N/A.
Usage Guidelines
Use a value of 255.255.255.255 for mask to indicate a host entry.
Example
The following command adds a static address to the routing table:
configure iproute add 10.1.1.1/24 123.45.67.1 5
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a blackhole address to the routing table. All traffic destined for a configured blackhole IP address
is silently dropped, and no Internet Control Message Protocol (ICMP) message is generated.
Syntax Description
Default
N/A.
Usage Guidelines
A blackhole entry configures packets with a specified MAC destination address to be discarded.
Blackhole entries are useful as a security measure or in special circumstances where a specific
destination address must be discarded. Blackhole entries are treated like permanent entries in the event
of a switch reset or power off/on cycle. Blackhole entries are never aged out of the forwarding database
(FDB).
Example
The following command adds a blackhole address to the routing table for packets with a destination
address of 100.101.145.4:
configure iproute add blackhole 100.101.145.4
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a default blackhole route to the routing table. All traffic destined for an unknown IP destination is
silently dropped, and no Internet Control Message Protocol (ICMP) message is generated.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
While a default route is for forwarding traffic destined to an unknown IP destination, and a blackhole
route is for discarding traffic destined to a specified IP destination, a default blackhole route is for
discarding traffic to the unknown IP destination.
Using this command, all traffic with an unknown destination is discarded. If there is another static
default route existing in the routing table, the blackhole default route takes higher route priority.
The default blackhole route is treated like a permanent entry in the event of a switch reset or power
off/on cycle. The default blackhole route’s origin is “b” or “blackhole” and the gateway IP address for
this route is 0.0.0.0.
Example
The following command adds a blackhole default route into the routing table:
configure iproute add blackhole default
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a default gateway to the routing table.
Syntax Description
Default
If no metric is specified, the default metric of 1 is used.
Usage Guidelines
Default routes are used when the router has no other dynamic or static route to the requested
destination. A default gateway must be located on a configured IP interface. Use the unicast-only or
multicast-only options to specify a particular traffic type. If not specified, both unicast and multicast
traffic uses the default route.
Example
The following command configures a default route for the switch:
configure iproute add default 123.45.67.1
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a static address from the routing table.
Syntax Description
Default
N/A.
Usage Guidelines
Use a value of 255.255.255.255 for mask to indicate a host entry.
Example
The following command deletes an address from the gateway:
configure iproute delete 10.101.0.250/24 10.101.0.1
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a blackhole address from the routing table.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes a blackhole address from the routing table:
configure iproute delete blackhole 100.101.145.4
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a default blackhole route from the routing table.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes a blackhole default route from the routing table:
configure iproute delete blackhole default
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a default gateway from the routing table.
Syntax Description
Default
N/A.
Usage Guidelines
Default routes are used when the router has no other dynamic or static route to the requested
destination. A default gateway must be located on a configured IP interface.
Example
The following command deletes a default gateway:
configure iproute delete default 123.45.67.1
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Changes the priority for all routes from a particular route origin.
Syntax Description
Default
Table 16 lists the relative priorities assigned to routes depending upon the learned source of the route.
Usage Guidelines
Although these priorities can be changed, do not attempt any manipulation unless you are expertly
familiar with the possible consequences.
Example
The following command sets IP route priority for static routing to 1200:
configure iproute priority static 1200
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
configure irdp
configure irdp [multicast | broadcast]
Description
Configures the destination address of the router advertisement messages.
Syntax Description
Default
Multicast (224.0.0.1).
Usage Guidelines
None.
Example
The following command sets the address of the router advertiser messages to multicast:
configure irdp multicast
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
configure irdp
configure irdp <mininterval> <maxinterval> <lifetime> <preference>
Description
Configures the router advertisement message timers, using seconds.
Syntax Description
Default
N/A.
Usage Guidelines
All arguments need to be specified. All time intervals are in seconds.
An ICMP Router Discover Protocol (IRDP) client always uses the router with the highest preference
level. Change the preference setting to encourage or discourage the use of this router. The default
setting is 0.
Example
The following command configures the router advertisement message timers:
configure irdp 30 40 300 1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a UDP-forwarding profile.
Syntax Description
Default
N/A.
Usage Guidelines
A maximum of 10 UDP-forwarding profiles can be defined. Each named profile may contain a
maximum of eight “rules” defining the UDP port, and destination IP address or VLAN. A VLAN can
make use of a single UDP-forwarding profile. UDP packets directed toward a VLAN use an all-ones
broadcast on that VLAN.
Example
The following command adds port 34 to UDP profile port_34_to_server:
configure udp-profile port_34_to_server add 34 ip address 10.1.1.1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a forwarding entry from the specified UDP-profile.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes port 34 from UDP profile port_34_to_server:
configure udp-profile port_34_to_server delete 34 ip address 10.1.1.1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Assigns a UDP-forwarding profile to the source VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
After the UDP profile has been associated with the VLAN, the switch picks up any broadcast UDP
packets that match the user-configured UDP port number, and forwards those packets to the
user-defined destination. If the UDP port is the DHCP/BOOTP port number, appropriate
BOOTP/DHCP proxy functions are invoked.
Example
The following command assigns a UDP profile to VLAN accounting:
configure vlan accounting udp-profile port_34_to_server
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
create udp-profile
create udp-profile <profile_name>
Description
Creates a UDP-forwarding destination profile that describes the types of UDP packets (by port number)
that are used, and where they are to be forwarded.
Syntax Description
Default
N/A.
Usage Guidelines
You must give the profile a unique name, in the same manner as a VLAN, protocol filter, or Spanning
Tree Domain (STD). A maximum of 10 UDP-forwarding profiles can be defined.
Example
The following command creates a UPD profile named backbone:
create udp-profile backbone
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
delete udp-profile
delete udp-profile <profile_name>
Description
Deletes a UDP-forwarding profile.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes a UPD profile named backbone:
delete udp-profile backbone
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation and processing of BOOTP packets on a VLAN to obtain an IP address for the
VLAN from a BOOTP server.
Syntax Description
Default
Enabled for all VLANs.
Usage Guidelines
None.
Example
The following command disables the generation and processing of BOOTP packets on a VLAN named
accounting:
disable bootp vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable bootprelay
disable bootprelay
Description
Disables the BOOTP relay function.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward Dynamic Host
Configuration Protocol (DHCP) or BOOTP requests coming from clients on subnets being serviced by
the switch and going to hosts on different subnets. This feature can be used in various applications,
including DHCP services between Windows NT servers and clients running Windows 95. To configure
the relay function, follow these steps:
1 Configure VLANs and IP unicast routing.
2 Enable the DHCP or BOOTP relay function, using the following command:
enable bootprelay
3 Configure the addresses to which DHCP or BOOTP requests should be directed, using the following
command:
configure bootprelay add <ip address>
Example
The following command disables the forwarding of BOOTP requests:
disable bootprelay
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of an ICMP address-mask reply on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Disables the generation of an ICMP address-mask reply (type 18, code 0) when an ICMP address mask
request is received. The default setting is enabled. If a VLAN is not specified, the command applies to
all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command disables the generation of an ICMP address-mask reply on VLAN accounting:
disable icmp address-mask vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of an ICMP parameter-problem message on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Disables the generation of an ICMP parameter-problem message (type 12) when the switch cannot
properly process the IP header or IP option information. If a VLAN is not specified, the command
applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command disables the generation of an ICMP parameter-problem message on VLAN
accounting:
disable icmp parameter-problem vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of ICMP port unreachable messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Disables the generation of ICMP port unreachable messages (type 3, code 3) when a TPC or UDP
request is made to the switch, and no application is waiting for the request, or access policy denies the
request. If a VLAN is not specified, the command applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command disables ICMP port unreachable messages on VLAN accounting:
disable icmp port-unreachables vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables generation of ICMP redirect messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
This option only applies to the switch when the switch is not in routing mode.
Example
The following command disables ICMP redirects from VLAN accounting:
disable icmp redirects vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of ICMP time exceeded messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Disables the generation of an ICMP time exceeded message (type 11) when the TTL field expires during
forwarding. IP multicast packets do not trigger ICMP time exceeded messages. If a VLAN is not
specified, the command applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command disables the generation of ICMP time exceeded messages on VLAN accounting:
disable icmp time-exceeded vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of an ICMP timestamp response on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Disables the generation of an ICMP timestamp response (type 14, code 0) when an ICMP timestamp
request is received. If a VLAN is not specified, the command applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command disables the generation of an ICMP timestamp response on VLAN accounting:
disable icmp timestamp vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of ICMP unreachable messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables the generation of ICMP unreachable messages on all VLANs:
disable icmp unreachables
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the modification of route table information when an ICMP redirect message is received.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This option only applies to the switch when the switch is not in routing mode.
Example
The following command disables the changing of routing table information:
disable icmp useredirects
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disable checking if the ARP Request source IP address is within the range of the local interface or
VLAN domain.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables IP ARP checking:
disable iparp checking
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables IP ARP to refresh its IP ARP entries before timing out.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
IP ARP refresh can only be disabled if IP forwarding is disabled. The purpose of disabling ARP refresh
is to reduce ARP traffic in a high node count layer 2 switching only environment.
Example
The following command disables IP ARP refresh:
disable iparp refresh
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
disable ipforwarding
disable ipforwarding {[broadcast |ignore-broadcast]} {vlan <vlan name>}
Description
Disables routing (or routing of broadcasts) for one or all VLANs. If no argument is provided, disables
routing for all VLANs.
Syntax Description
Default
Disabled.
Usage Guidelines
Disabling IP forwarding also disables broadcast forwarding. Broadcast forwarding can be disabled
without disabling IP forwarding.When new IP interfaces are added, IP forwarding and IP broadcast
forwarding) is disabled by default.
Other IP related configuration is not affected.
Example
The following command disables forwarding of IP broadcast traffic for a VLAN named accounting:
disable ipforwarding broadcastvlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the loose source route IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables the loose source route IP option:
disable ip-option loose-source-route
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the record route IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables the record route IP option:
disable ip-option record-route
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the record timestamp IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables the record timestamp IP option:
disable ip-option record-timestamp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the strict source route IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables the strict source route IP option:
disable ip-option strict-source-route
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the generation of the router alert IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command disables generation of the router alert IP option:
disable ip-option use-router-alert
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables load sharing if multiple routes to the same destination are available. When multiple routes to
the same destination are available, load sharing can be enabled to distribute the traffic to multiple
destination gateways. Only paths with the same lowest cost is will be shared.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
IP route sharing allows multiple equal-cost routes to be used concurrently. IP route sharing can be used
with static routes or with OSPF routes. In OSPF, this capability is referred to as equal cost multipath
(ECMP) routing.
Configure static routes and/or OSPF as you would normally. ExtremeWare supports unlimited route
sharing across static routes and up to 12 ECMP routes for OSPF.
Route sharing is useful only in instances where you are constrained for bandwidth. This is typically not
the case using Extreme switches. Using route sharing makes router troubleshooting more difficult
because of the complexity in predicting the path over which the traffic will travel.
Example
The following command disables load sharing for multiple routes:
disable iproute sharing
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable irdp
disable irdp {vlan <vlan name>}
Description
Disables the generation of ICMP router advertisement messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
If no optional argument is specified, all the IP interfaces are affected.
Example
The following command disables IRDP on VLAN accounting:
disable irdp vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disallows a VLAN to be placed in the UP state without an external active port. This allows (disallows)
the VLANs routing interface to become active.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to specify a stable interface as a source interface for routing protocols. This decreases
the possibility of route flapping, which can disrupt connectivity.
Example
The following command disallows the VLAN accounting to be placed in the UP state without an
external active port:
disable loopback-mode vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable udp-echo-server
disable udp-echo-server
Description
Disables UDP echo server support.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
UDP Echo packets are used to measure the transit time for data between the transmitting and receiving
end.
Example
The following command disables UDP echo server support:
disable udp-echo-server
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation and processing of BOOTP packets on a VLAN to obtain an IP address for the
VLAN from a BOOTP server.
Syntax Description
Default
Enabled for all VLANs.
Usage Guidelines
None.
Example
The following command enables the generation and processing of BOOTP packets on a VLAN named
accounting:
enable bootp vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable bootprelay
enable bootprelay
Description
Enables the BOOTP relay function.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
After IP unicast routing has been configured, you can configure the switch to forward Dynamic Host
Configuration Protocol (DHCP) or BOOTP requests coming from clients on subnets being serviced by
the switch and going to hosts on different subnets. This feature can be used in various applications,
including DHCP services between Windows NT servers and clients running Windows 95. To configure
the relay function, follow these steps:
1 Configure VLANs and IP unicast routing.
2 Enable the DHCP or BOOTP relay function, using the following command:
enable bootprelay
3 Configure the addresses to which DHCP or BOOTP requests should be directed, using the following
command:
configure bootprelay add <ip address>
Example
The following command enables the forwarding of BOOTP requests:
enable bootprelay
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of an ICMP address-mask reply on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Enables the generation of an ICMP address-mask reply (type 18, code 0) when an ICMP address mask
request is received.The default setting is enabled. If a VLAN is not specified, the command applies to all
IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command enables the generation of an ICMP address-mask reply on VLAN accounting:
enable icmp address-mask vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of an ICMP parameter-problem message on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Enables the generation of an ICMP parameter-problem message (type 12) when the switch cannot
properly process the IP header or IP option information. If a VLAN is not specified, the command
applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command enables the generation of an ICMP parameter-problem message on VLAN
accounting:
enable icmp parameter-problem vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of ICMP port unreachable messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Enables the generation of ICMP port unreachable messages (type 3, code 3) when a TPC or UDP request
is made to the switch, and no application is waiting for the request, or access policy denies the request.
If a VLAN is not specified, the command applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command enables ICMP port unreachable messages on VLAN accounting:
enable icmp port-unreachables vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables generation of ICMP redirect messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
This option only applies to the switch when the switch is not in routing mode.
Example
The following command enables the generation of ICMP redirect messages on all VLANs:
enable icmp redirects
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of ICMP time exceeded messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Enables the generation of an ICMP time exceeded message (type 11) when the TTL field expires during
forwarding. IP multicast packets do not trigger ICMP time exceeded messages. If a VLAN is not
specified, the command applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command enables the generation of ICMP time exceeded messages on VLAN accounting:
enable icmp time-exceeded vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of an ICMP timestamp response on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
Enables the generation of an ICMP timestamp response (type 14, code 0) when an ICMP timestamp
request is received. If a VLAN is not specified, the command applies to all IP interfaces.
This command only affects the generation of certain ICMP packets. Filtering of ICMP packets usually
forwarded by the switch is controlled by the access-list commands.
Example
The following command enables the generation of an ICMP timestamp response on VLAN accounting:
enable icmp timestamp vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of ICMP unreachable messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables the generation of ICMP unreachable messages on all VLANs:
enable icmp unreachables
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the modification of route table information when an ICMP redirect message is received.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
This option only applies to the switch when the switch is not in routing mode.
Example
The following command enables the modification of route table information:
enable icmp useredirects
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables checking if the ARP Request source IP address is within the range of the local interface or
VLAN domain.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables IP ARP checking:
enable iparp checking
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables IP ARP to refresh its IP ARP entries before timing out.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
IP ARP refresh can only be disabled if IP forwarding is disabled. The purpose of disabling ARP refresh
is to reduce ARP traffic in a high node count layer 2 switching only environment.
Example
The following command enables IP ARP refresh:
enable iparp refresh
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
enable ipforwarding
enable ipforwarding {[broadcast | ignore-broadcast]}{vlan <vlan name>}
Description
Enables IP routing or IP broadcast forwarding for one or all VLANs. If no argument is provided,
enables IP routing for all VLANs that have been configured with an IP address.
Syntax Description
Default
Disabled.
Usage Guidelines
IP forwarding must first be enabled before IP broadcast forwarding can be enabled. When new IP
interfaces are added, IP forwarding (and IP broadcast forwarding) is disabled by default.
Example
The following command enables forwarding of IP traffic for all VLANs with IP addresses:
enable ipforwarding
The following command enables forwarding of IP broadcast traffic for a VLAN named accounting:
enable ipforwarding broadcast vlan accounting
History
This command was available in ExtremeWare 7.1e.
This command was modified in an ExtremeWare 7.2e to support the ignore-broadcast keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the loose source route IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables the loose source route IP option:
enable ip-option loose-source-route
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the record route IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables the record route IP option:
enable ip-option record-route
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the record timestamp IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables the record timestamp IP option:
enable ip-option record-timestamp
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the strict source route IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables the strict source route IP option:
enable ip-option strict-source-route
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the generation of the router alert IP option.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
None.
Example
The following command enables generation of the router alert IP option:
enable ip-option use-router-alert
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables load sharing if multiple routes to the same destination are available. When multiple routes to
the same destination are available, load sharing can be enabled to distribute the traffic to multiple
destination gateways. Only paths with the same lowest cost is will be shared.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
IP route sharing allows multiple equal-cost routes to be used concurrently. IP route sharing can be used
with static routes or with OSPF routes. In OSPF, this capability is referred to as equal cost multipath
(ECMP) routing.
Configure static routes and/or OSPF as you would normally. ExtremeWare supports unlimited route
sharing across static routes and up to 12 ECMP routes for OSPF.
Route sharing is useful only in instances where you are constrained for bandwidth. This is typically not
the case using Extreme switches. Using route sharing makes router troubleshooting more difficult
because of the complexity in predicting the path over which the traffic will travel.
Example
The following command enables load sharing for multiple routes:
enable iproute sharing
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable irdp
enable irdp {vlan <vlan name>}
Description
Enables the generation of ICMP router advertisement messages on one or all VLANs.
Syntax Description
Default
Enabled.
Usage Guidelines
If no optional argument is specified, all the IP interfaces are affected.
Example
The following command enables IRDP on VLAN accounting:
enable irdp vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Allows a VLAN to be placed in the UP state without an external active port. This allows (disallows) the
VLANs routing interface to become active.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to specify a stable interface as a source interface for routing protocols. This decreases
the possibility of route flapping, which can disrupt connectivity.
Example
The following command allows the VLAN accounting to be placed in the UP state without an external
active port:
enable loopback-mode vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable udp-echo-server
enable udp-echo-server
Description
Enables UDP echo server support.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
UDP Echo packets are used to measure the transit time for data between the transmitting and receiving
end.
Example
The following command enables UDP echo server support:
enable udp-echo-server
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
rtlookup
rtlookup [<ip address> | <hostname>]
Description
Performs a look-up in the route table to determine the best route to reach an IP address or host.
Syntax Description
Default
N/A.
Usage Guidelines
The output of the rtlookup command has been enhanced to include information about MPLS LSPs
associated with the routes. The flags field displayed by this command has been enhanced to indicate the
presence of MPLS next hops. An uppercase L indicates the presence of a direct LSP next hop for the
route. A lowercase l indicates the presence of an indirect LSP next hope for the route.
An optional mpls keyword has been added to the rtlookup command. When the mpls keyword is
specified, the information displayed is modified; some of the information normally displayed is
omitted, and the LSP endpoint and outgoing MPLS label are displayed instead. The LSP endpoint is the
IP address/prefix of the FEC associated with the LSP. The LSP endpoint matches the destination for
direct LSPs and is a 32-bit prefix address of a proxy router for indirect LSPs.
Example
The following command performs a look up in the route table to determine the best way to reach the
specified hostname:
rtlookup berkeley.edu
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show iparp
show iparp {<ip address> | <mac_address> | vlan <vlan name> | permanent}
Description
Displays the IP Address Resolution Protocol (ARP) table. You can filter the display by IP address, MAC
address, VLAN, or permanent entries.
Syntax Description
Default
Show all entries.
Usage Guidelines
Displays the IP ARP table, including:
• IP address
• MAC address
• Aging timer value
• VLAN name, VLAN ID and port number
• Flags
Example
The following command displays the IP ARP table:
show iparp 10.1.1.5/24
History
This command was available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2.e to provide the MAC address option.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the proxy ARP table.
Syntax Description
Default
N/A.
Usage Guidelines
If no argument is specified, then all proxy ARP entries are displayed.
Example
The following command displays the proxy ARP table:
show iparp proxy 10.1.1.5/24
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show ipconfig
show ipconfig {vlan <vlan name>} {detail}
Description
Displays configuration information for one or more VLANs.
Syntax Description
Default
N/A.
Usage Guidelines
If no VLAN information is specified, then global IP configuration is displayed. Otherwise, specific
VLAN(s) information will be displayed. Global IP configuration information includes:
• IP address/netmask/etc.
• IP forwarding information / IP multicast forwarding information
• BOOTP configuration
• VLAN name and VLANID
• ICMP configuration (global)
• IGMP configuration (global)
• IRDP configuration (global)
Example
The following command displays configuration information on a VLAN named accounting:
show ipconfig vlan accounting
History
This command was available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the detail keyword.
Platform Availability
This command is available on the “e” series platforms.
show ipfdb
show ipfdb {<ip address> <netmask> | vlan <vlan name>}
Description
Displays the contents of the IP forwarding database (FDB) table. Used for technical support purposes. If
no option is specified, all IP FDB entries are displayed.
Syntax Description
Default
Default is to show all IP FDB entries.
Usage Guidelines
Displays IP FDB table content including:
Example
The following command displays the contents of the IP FDB table on a VLAN named accounting:
show ipfdb vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show iproute
show iproute {priority | vlan <vlan name> | permanent | <ip address>
<netmask> | origin [direct | static | blackhole | rip | bootp | icmp |
ospf-intra | ospf-inter | ospf-as-external | ospf-extern1 | ospf-extern2]}
{sorted}
Description
Displays the contents of the IP routing table or the route origin priority.
Syntax Description
Default
N/A.
Usage Guidelines
Route maps for IP routing can be configured based on the route origin. When routes are added to the IP
routing table from various sources, the route map configured for the origin of the route is applied to the
route. After matching on specified characteristics, the characteristics for the route can be modified using
the route maps. The characteristics that can be matched and modified are dependent on the origin of the
route. Route maps for IP routing can be dynamically changed. In the case of direct and static route
origins, the changes are reflected immediately. In the case of routes that are sourced from other origin,
the changes are reflected within 30 seconds.
The output of the show iproute command has been enhanced to include information about MPLS
LSPs associated with the routes. The flags field displayed by this command has been enhanced to
indicate the presence of MPLS next hops. An uppercase L indicates the presence of a direct LSP next
hop for the route. A lowercase l indicates the presence of an indirect LSP next hope for the route.
An optional mpls keyword has been added to the show iproute command. When the mpls keyword is
specified, the information displayed is modified; some of the information normally displayed is
omitted, and the LSP endpoint and outgoing MPLS label are displayed instead. The LSP endpoint is the
IP address/prefix of the FEC associated with the LSP. The LSP endpoint matches the destination for
direct LSPs and is a 32-bit prefix address of a proxy router for indirect LSPs.
If a route is active and in use, it is preceded in the display by an “*”. If there are multiple routes to the
same destination network, the “*” will indicate which route is the most preferable route.
The Use and M-Use fields indicate the number of times the route table entry is being used for packet
forwarding decisions. The Use field indicates a count for unicast routing while the M-Use field indicates
a count for multicast routing. If the use count is going up unexpectedly, the software is making route
decisions and should be investigated further.
Example
The following command displays detailed information about all IP routing:
show iproute detail
Destination: 10.10.121.111/30
Gateway: 10.10.121.201 VLAN : helium Origin : *d
Metric : 1 Flags : U------u- Time : 13:15:26:49
Use : 14409 M-Use : 0 Acct-1 : 0
Destination: 10.11.166.112/29
Gateway: 10.17.0.1 VLAN : helium Origin : *be
Metric : 2 Flags : UG-----um Time : 01:11:23:49
Use : 0 M-Use : 0 Acct-1 : 0
Destination: 10.13.105.112/29
Gateway: 10.11.110.123 VLAN : helium Origin : *be
Metric : 2 Flags : UG-----um Time : 00:29:09:23
Use : 0 M-Use : 0 Acct-1 :
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show ipstats
show ipstats {vlan <vlan name>}
Description
Displays IP statistics for the CPU for the switch or for a particular VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
This command only shows statistics of the CPU-handled packets. Not all packets are handled by the
CPU.
The fields displayed in the show ipstats command are defined in Table 17 though Table 21.
Field Definition
InReceives Total number of incoming IP packets processed by the CPU.
InUnicast Total number of unicast IP packets processed by the CPU.
InBcast Total number of broadcast IP packets processed by the CPU.
InMcast Total number of multicast IP packets processed by the CPU.
InHdrEr Total number of packets with an IP Header Error forwarded to the CPU.
Bad vers Total number of packets with a version other than IP v4 in the IP version field.
Bad chksum Total number of packets with a bad IP checksum forwarded to the CPU.
Short pkt IP packets that are too short.
Short hdr IP packets with a header that is too short.
Bad hdrlen IP packets with a header length that is less than the length specified.
Bad length IP packets with a length less than that of the header.
InDelivers IP packets passed to upper layer protocols.
Bad Proto IP packets with unknown (not standard) upper layer protocol.
OutRequest IP packets sent from upper layers to the IP stack.
OutDiscard IP packets that are discarded due to lack of buffer space or the router
interface being down, or broadcast packets with broadcast forwarding
disabled.
OutNoRoute IP packets with no route to the destination.
Forwards ForwardOK and Fwd Err aggregate count.
ForwardOK Total number of IP packets forwarded correctly.
Fwd Err Total number of IP packets that cannot be forwarded.
Field Definition
NoFwding Aggregate number of IP packets not forwarded due to errors.
Redirects IP packets forwarded on the same network.
No route Not used.
Bad TTL IP packets with a bad time-to-live.
Bad MC TTL IP packets with a bad multicast time-to-live.
Bad IPdest IP packets with an address that does not comply with the IP v4 standard.
Blackhole IP packets with a destination that is a blackhole entry.
Output err Not used. This is the same as Fwd Err.
MartianSrc IP packets with an invalid source address.
Field Definition
OutResp Echo replies sent from the CPU.
OutError Redirect from broadcast or multicast source addresses.
InBadcode Incoming ICMP packets with an invalid CODE value.
InTooshort Incoming ICMP packets that are too short.
Bad chksum Incoming ICMP packets with checksum errors.
In Badlen Incoming ICMP packets with length errors.
echo reply (In/Out): ICMP “echo reply” packets that are received and transmitted.
destination unreachable (In/Out): ICMP packets with destination unreachable that are received and transmitted.
port unreachable (In/Out): ICMP packets with port unreachable that are received and transmitted.
echo (In/Out): ICMP echo packets that are received and transmitted.
Field Definition
Out Query Number of IGMP query messages sent by the router.
Out Report Number of reports sent on an active multicast route interface for reserved
multicast addresses and for regular IGMP reports forwarded by the query
router.
Out Leave Number of IGMP out leave messages forwarded for IP multicast router
interfaces.
In Query Number of IGMP query messages received.
In Report Number of IGMP report messages received (mostly from hosts).
In Leave Number of IGMP leave messages received (mostly from hosts).
In Error Number of IGMP packets with bad header fields or checksum failures.
Field Definition
Received to server Number of DHCP packets forwarded to server.
Received to client Number of DHCP packets received by clients.
Requests relayed Number of DHCP request packets relayed.
Responses relayed Number of DHCP response packets relayed.
DHCP Discover Number of DHCP Discover messages.
DHCP Offer Number of DHCP Offer messages.
DHCP Request Number of DHCP Request messages.
DHCP Decline Number of DHCP Decline responses.
DHCP Ack Number of DHCP Ack responses.
DHCP NAck Number of DHCP NAck responses.
DHCP Release Number of DHCP Release instances.
DHCP Inform Not used.
Field Definition
Packets IN/OUT Total number of IP packets received or transmitted on a VLAN router
interface.
Octets IN/OUT Total number of octets received or transmitted on a VLAN router interface.
Mcast packets IN/OUT Total number of multicast packets received or transmitted on a VLAN router
interface.
Bcast packets IN/OUT Total number of broadcast packets received or transmitted on a VLAN router
interface.
Errors IN/OUT Total number of IP packets with errors received or transmitted on a VLAN
router interface.
Discards IN/OUT Total number of IP packets that cannot travel up to the CPU due to lack of
buffer space.
Unknown Protocols IN/OUT Total number of IP packets with unknown upper layer protocols received by
the router interface.
Example
The following command displays IP statistics for the VLAN accounting:
show ipstats vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show udp-profile
show udp-profile {<profile_name>}
Description
Displays the UDP profile information.
Syntax Description
Default
N/A.
Usage Guidelines
Displays the following information:
• Profile names
• Input rules of UDP port, destination IP address, or VLAN
• Source VLANs to which the profile is applied.
Example
The following command displays the UDP profile information for the UPD profile named backbone:
show udp-profile backbone
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the Dynamic Host Configuration Protocol (DHCP) relay agent information checking in the
DHCP reply packet.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
The following command configures DHCP relay agent option check:
configure bootprelay dhcp-agent information check
To disable the DHCP relay agent information check in the DHCP reply packet, use the following
command:
Example
The following command disables DHCP relay agent information checking in the DHCP reply packet:
unconfigure bootprelay dhcp-agent information check
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the Dynamic Host Configuration Protocol (DHCP) relay agent option (option 82).
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
The following command configures the DHCP relay agent option:
configure bootprelay dhcp-agent information option
To disable the DHCP relay agent option (option 82), use the following command:
Example
The following command disables the DHCP relay agent option (option 82):
unconfigure bootprelay dhcp-agent information option
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the Dynamic Host Configuration Protocol (DHCP) relay agent reforwarding policy.
Syntax Description
This command has no arguments or variables.
Default
Replace. (Replaces the existing the relay agent information with its own information.)
Usage Guidelines
The following command configures the DHCP relay agent reforwarding policy:
configure bootprelay dhcp-agent information policy <policy>
To disable the DHCP relay agent reforwarding policy, use the following command:
Example
The following command disables the DHCP relay agent reforwarding policy:
unconfigure bootprelay dhcp-agent information policy
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure icmp
unconfigure icmp
Description
Resets all ICMP settings to the default values.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command resets all ICMP settings to the default values.
unconfigure icmp
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure iparp
unconfigure iparp
Description
Resets IP ARP timeout, IP ARP max-entries, and IP ARP max-pending-entries to their default values.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command resets all IP ARP related settings to the default values:
unconfigure iparp
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure irdp
unconfigure irdp
Description
Resets all router advertisement settings to the default values.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command resets all router advertisement settings to the default values.
unconfigure irdp
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure udp-profile
unconfigure udp-profile vlan [<vlan name> | all]
Description
Removes the UDP-forwarding profile configuration for one or all VLANs.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command removes the UDP profile configuration from the VLAN accounting:
unconfigure udp-profile vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
This chapter documents commands used for the following interior gateway protocols:
• OSPF
• RIP
OSPF is a link-state protocol that distributes routing information between routers belonging to a single
IP domain, also known as an autonomous system (AS). In a link-state routing protocol, each router
maintains a database describing the topology of the autonomous system. Each participating router has
an identical database maintained from the perspective of that router.
From the link-state database (LSDB), each router constructs a tree of shortest paths, using itself as the
root. The shortest path tree provides the route to each destination in the autonomous system. When
several equal-cost routes to a destination exist, traffic can distributed among them. The cost of a route is
described by a single metric.
OSPF allows parts of a networks to be grouped together into areas. The topology within an area is
hidden from the rest of the autonomous system. Hiding this information enables a significant reduction
in LSA traffic, and reduces the computations needed to maintain the LSDB. Routing within the area is
determined only by the topology of the area.
Each switch that is configured to run OSPF must have a unique router ID. It is recommended that you
manually set the router ID of the switches participating in OSPF, instead of having the switch
automatically choose its router ID based on the highest interface IP address. Not performing this
configuration in larger, dynamic environments could result in an older LSDB remaining in use.
NOTE
Do not set the router ID to 0.0.0.0.
Routing Information Protocol (RIP) is an Interior Gateway Protocol (IGP) first used in computer routing
in the Advanced Research Projects Agency Network (ARPAnet) as early as 1969. It is primarily intended
for use in homogeneous networks of moderate size.
To determine the best path to a distant network, a router using RIP always selects the path that has the
least number of hops. Each router that data must traverse is considered to be one hop.
The routing table in a router using RIP contains an entry for every known destination network. Each
routing table entry contains the following information:
• IP address of the destination network
• Metric (hop count) to the destination network
• IP address of the next router
• Timer that tracks the amount of time since the entry was last updated
The router exchanges an update message with each neighbor every 30 seconds (default value), or if
there is a change to the overall routed topology (also called triggered updates). If a router does not receive
an update message from its neighbor within the route timeout period (180 seconds by default), the
router assumes the connection between it and its neighbor is no longer available.
A new version of RIP, called RIP version 2 (RIPv2), expands the functionality of RIP version 1 to
include:
• Variable-Length Subnet Masks (VLSMs)
• Next-hop addresses
• Support for next-hop addresses allows for optimization of routes in certain environments
• Multicasting
If you are using RIP with supernetting/Classless Inter-Domain Routing (CIDR), you must use RIPv2
only, and RIP route aggregation must be turned off.
Description
Configures a global inter-area filter policy.
Syntax Description
Default
N/A.
Usage Guidelines
For switches configured to support multiple OSPF areas (an ABR function), an access profile can be
applied to an OSPF area that filters a set of OSPF inter-area routes from being sourced from any other
areas.
Example
The following command configures an inter-area filter policy from the access profile nosales:
configure ospf area 0.0.0.6 interarea-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Description
Configures an external filter policy.
Syntax Description
Default
N/A.
Usage Guidelines
For switches configured to support multiple OSPF areas (an ABR function), an access profile can be
applied to an OSPF area that filters a set of OSPF external routes from being advertised into that area.
NOTE
If any of the external routes specified in the filter have already been advertised, those routes will remain
until the associated LSAs in that area time-out.
Example
The following command configures an external filter policy from the access profile nosales:
configure ospf area 1.2.3.4 external-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Description
Configures the cost metric of one or all interface(s).
Syntax Description
Default
The default cost is automatic.
Usage Guidelines
None.
Example
The following command configures the cost metric of the VLAN accounting:
configure ospf vlan accounting cost 10
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the priority used in the designated router-election algorithm for one or all OSPF interface(s)
for all the interfaces within the area.
Syntax Description
Default
The default setting is 1.
Usage Guidelines
The range is 0 through 255, and the default setting is 1. Setting the value to 0 ensures that the router is
never selected as the designated router or backup designated router.
Example
The following command sets the switch to not be selected as the designated router:
configure ospf area 1.2.3.4 priority 0
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the authentication password (up to eight characters) or Message Digest 5 (MD5) key for one or
all interfaces in an area.
Syntax Description
Default
N/A.
Usage Guidelines
The md5_key is a numeric value with the range 0 to 65,536 or alphanumeric. When the OSPF area is
specified, authentication information is applied to all OSPF interfaces within the area.
Example
The following command configures MD5 authentication on the VLAN subnet_26:
configure ospf vlan subnet_26 authentication md5 32 test
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the timers for one interface or all interfaces in the same OSPF area.
Syntax Description
Default
• retransmit interval—Default: 5
• transit delay—Default: 1
• hello interval—Default: 10
• dead interval—Default: 40
• wait timer interval—Default: dead interval
Usage Guidelines
Configuring OSPF timers and authentication on a per-area basis is a shorthand for applying the timers
and authentication to each VLAN in the area at the time of configuration. If you add more VLANs to
the area, you must configure the timers and authentication for the new VLANs explicitly.
Example
The following command sets the timers on the virtual link in area 0.0.0.2:
configure ospf virtual-link 6.6.6.6 0.0.0.2 timer 10 1 20 200
History
This command was available in ExtremeWare 7.1e.
The syntax was modified in ExtremeWare 7.2e to support the wait timer interval.
Platform Availability
This command is available on the “e” series platforms.
Description
Adds a virtual link connected to another ABR.
Syntax Description
Default
N/A.
Usage Guidelines
A virtual link provides a logical path between the ABR of the disconnected area and the ABR of the
normal area that connects to the backbone. A virtual link must be established between two ABRs that
have a common area, with one ABR connected to the backbone. Specify the following:
• routerid—Far-end router identifier number.
• area identifier—Transit area used for connecting the two end-points. The transit area cannot have the
IP address 0.0.0.0. the transit area cannot be a stub area or an NSSA.
Example
The following command configures a virtual link between the two interfaces:
configure ospf add virtual-link 10.1.2.1 10.1.0.0
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Associates a VLAN (router interface) with an OSPF area. By default, all router interfaces are associated
with area 0.0.0.0. The Summit 400 allows up to two non-passive interfaces.
Syntax Description
Default
Area 0.0.0.0
Usage Guidelines
Any OSPF network that contains more than one area is required to have an area configured as area 0,
also called the backbone. All areas in an autonomous system must be connected to the backbone. When
designing networks, you should start with area 0, and then expand into other areas.
The backbone allows summary information to be exchanged between ABRs. Every ABR hears the area
summaries from all other ABRs. The ABR then forms a picture of the distance to all networks outside of
its area by examining the collected advertisements, and adding in the backbone distance to each
advertising router.
When a VLAN is configured to run OSPF, by default you must assign it to an area.
If a user attempts to configure more than two non-passive interfaces, the Summit 400 displays the
following warning message:
Example
The following command associates the VLAN accounting with an OSPF area:
configure ospf vlan accounting area 0.0.0.6
History
This command was available in ExtremeWare 2.0.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables OSPF on one or all VLANs (router interfaces).
Syntax Description
Default
Disabled.
Usage Guidelines
None.
Using OSPF and MPLS. The following detailed information pertains to using OSPF in conjunction
with MPLS. When the peer LSR is also an Extreme switch, the following options are available for
ensuring that an OSPF route is advertised for the tunnel endpoint IP address:
• A route is advertised when OSPF is enabled on the VLAN to which the IP address is assigned (using
the configure ospf add vlan command on the peer switch).
• A route is advertised when the peer switch is configured to distribute direct routes into the OSPF
domain (via the enable ospf export direct command). The export option should be used when
the tunnel LSP needs to cross OSPF area boundaries or when the Extreme Standby Routing Protocol
(ESRP) is enabled on the VLAN to which the IP address is assigned.
In either case, LDP must be configured to advertise label mappings for direct routing interfaces.
In some configurations, you may want to enable loopback mode on the VLAN to which the tunnel
endpoint IP address is assigned. One situation where loopback mode may be useful is when multiple
physical interfaces, associated with different VLANs, are connected to the MPLS backbone. In this case,
use of loopback-mode can provide redundancy by enabling TLS traffic to continue even when the
physical interfaces associated with the tunnel endpoint IP address VLAN fail.
Example
The following command enables OSPF on a VLAN named accounting:
configure ospf add vlan accounting area 0.0.0.1
History
This command was available in ExtremeWare 7.1e.
This command was modified in an ExtremeWare 7.2e to support the all keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the OSPF link type.
Syntax Description
Default
Auto.
Usage Guidelines
The passive parameter indicates that the router only synchronizes and listens, and does not originate or
send any new information on the interface.
Example
The following command configures the OSPF link type as automatic on a VLAN named accounting:
configure ospf add vlan accounting area 0.0.0.1 link-type auto
History
This command was first available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the all keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an external filter policy.
Syntax Description
Default
N/A.
Usage Guidelines
For switches configured to support multiple OSPF areas (an ABR function), an access profile can be
applied to an OSPF area that filters a set of OSPF external routes from being advertised into that area.
NOTE
If any of the external routes specified in the filter have already been advertised, those routes will remain
until the associated LSAs in that area time-out.
Example
The following command configures an external filter policy from the access profile nosales:
configure ospf area 1.2.3.4 external-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a global inter-area filter policy.
Syntax Description
Default
N/A.
Usage Guidelines
For switches configured to support multiple OSPF areas (an ABR function), an access profile can be
applied to an OSPF area that filters a set of OSPF inter-area routes from being sourced from any other
areas.
Example
The following command configures an inter-area filter policy from the access profile nosales:
configure ospf area 0.0.0.6 interarea-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a range of IP addresses in an OSPF area to be aggregated.
Syntax Description
Default
N/A.
Usage Guidelines
If advertised, the aggregated IP range is exported as a single LSA by the ABR.
Example
The following command is used to summarize a certain range of IP addresses within an area and export
them out as a single address:
configure ospf area 1.2.3.4 add range 10.1.2.0/24 advertise type-3
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes a range of aggregated IP addresses in an OSPF area.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes an aggregated IP address range:
configure ospf area 1.2.3.4 delete range 10.1.2.0/24
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an OSFP area as a normal area.
Syntax Description
Default
Normal.
Usage Guidelines
A normal area is an area that is not any of the following:
• Stub area
• NSSA
Virtual links can be configured through normal areas. External routes can be distributed into normal
areas.
Example
The following command configures an OSPF area as a normal area:
configure ospf area 10.1.0.0 normal
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an OSPF area as an NSSA.
Syntax Description
Default
N/A.
Usage Guidelines
NSSAs are similar to the existing OSPF stub area configuration option, but have the following two
additional capabilities:
• External routes originating from an ASBR connected to the NSSA can be advertised within the
NSSA.
• External routes originating from the NSSA can be propagated to other areas, including the backbone
area, if translated to type 5 LSAs.
When configuring an OSPF area as an NSSA, the translate option should only be used on NSSA border
routers, where translation is to be enforced. If translate is not used on any NSSA border router in a
NSSA, one of the ABRs for that NSSA is elected to perform translation (as indicated in the NSSA
specification). The option should not be used on NSSA internal routers. Doing so inhibits correct
operation of the election algorithm.
Example
The following command configures an OSPF area as an NSSA:
configure ospf area 10.1.1.0 nssa summary stub-default-cost 10 translate
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an OSPF area as a stub area.
Syntax Description
Default
N/A.
Usage Guidelines
A stub area is connected to only one other area. The area that connects to a stub area can be the
backbone area. External route information is not distributed into stub areas. Stub areas are used to
reduce memory and computation requirements on OSPF routers.
Example
The following command configures an OSPF area as a stub area:
configure ospf area 0.0.0.6 stub nosummary stub-default-cost 10
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a route filter for all OSPF exported routes.
Syntax Description
Default
N/A.
Usage Guidelines
For switches configured to support RIP, and static route re-distribution into OSPF, an access profile can
be used to limit the routes that are advertised into OSPF for the switch as a whole.
Example
The following command configures a route filter for all routes OSPF exports from RIP or other sources:
configure ospf asbr-filter subnet25-filter
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the AS-external LSA limit and overflow duration associated with OSPF database overflow
handling.
Syntax Description
number Specifies the number of external routes that can be held on a link-state
database.
seconds Specifies a duration for which the system has to remain in the overflow state.
Default
The default for timeout is 0, which indicates that once the router goes into overflow state, it stays there
until OSPF is disabled and then re-enabled.
Usage Guidelines
None.
Example
The following command configures the AS-external LSA limit and overflow duration:
configure ospf ase-limit 50000 timeout 1800
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Aggregates AS-external routes in a specified address range.
Syntax Description
Default
N/A.
Usage Guidelines
This command is only valid on an ASBR.
Example
The following command summarizes AS-external routes:
configure ospf ase-summary add 175.1.0.0/16 cost 10
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes an aggregated OSPF external route.
Syntax Description
Default
N/A.
Usage Guidelines
This command is only valid on an ASBR.
Example
The following command deletes the aggregated AS-external route:
configure ospf ase-summary delete 175.1.0.0/16
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes a virtual link.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes a virtual link:
configure ospf delete virtual-link 10.1.2.1 10.1.0.0
History
This command was available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Disables OSPF on one or all VLANs (router interfaces).
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command disables OSPF on VLAN accounting:
configure ospf delete vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a route filter for direct routes.
Syntax Description
Default
N/A.
Usage Guidelines
If none is specified, all direct routes are exported if ospf export direct is enabled.
In other versions of ExtremeWare, direct routes corresponding to the interfaces on which RIP was
enabled were exported into OSPF as part of RIP routes, using the command enable ospf export rip.
Using ExtremeWare 6.0 and above, you must configure ExtremeWare to export these direct routes to
OSPF. You can use an access profile to filter unnecessary direct routes.
For switches configured to support direct route re-distribution into OSPF, an access profile can be used
to limit the routes that are advertised into OSPF for the switch as a whole.
Example
The following command configures a route filter for direct routes based on the access profile nosales:
configure ospf direct-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the OSPF LSA batching interval.
Syntax Description
Default
The default setting is 30 seconds.
Usage Guidelines
The range is between 0 (disabled) and 600 seconds, using multiples of 5 seconds. The LSAs added to the
LSDB during the interval are batched together for refresh or timeout.
Example
The following command configures the OSPF LSA batch interval to a value of 100 seconds:
configure ospf lsa-batch-interval 100
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the automatic interface costs for 10 Mbps, 100 Mbps, 1 Gbps, and 10 Gbps interfaces.
Syntax Description
Default
• 10 Mbps—The default cost is 10.
• 100 Mbps—The default cost is 5.
• 1 Gbps—The default cost is 4.
• 10 Gbps—The default cost is 2.
Usage Guidelines
None.
Example
The following command configures the automatic interface costs for 10 Mbps,
100 Mbps, and 1 Gbps interfaces:
configure ospf metric-table 10m 20 100m 10 1g 2
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the OSPF router ID. If automatic is specified, the switch uses the highest IP interface address
as the OSPF router ID.
Syntax Description
Default
Automatic.
Usage Guidelines
Each switch that is configured to run OSPF must have a unique router ID. It is recommended that you
manually set the router ID of the switches participating in OSPF, instead of having the switch
automatically choose its router ID based on the highest interface IP address. Not performing this
configuration in larger, dynamic environments could result in an older link-state database remaining in
use.
NOTE
Do not set the router ID to 0.0.0.0.
The implementation of the configure ospf routerid command has been augmented to support automatic
advertisement of a label mapping for the OSPF router ID. A label is advertised for the OSPF router ID
regardless of whether OSPF distributes a route for the router ID IP address in its router LSA.
To support the use of indirect LSPs, Extreme LSRs automatically advertise a label mapping for a /32
LSP to its OSPF router ID (configured using the configure ospf routerid command).
Example
The following command sets the router ID:
configure ospf routerid 10.1.6.1
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the minimum number of seconds between Shortest Path First (SPF) recalculations.
Syntax Description
Default
3 seconds.
Usage Guidelines
None.
Example
The following command configures the minimum number of seconds between Shortest Path First (SPF)
recalculations:
configure ospf spf-hold-time 6
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the IP address of a point-to-point neighbor.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command configures the IP address of a point-to-point neighbor:
configure ospf vlan accounting neighbor add 10.0.0.1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes the IP address of a point-to-point neighbor.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command deletes the IP address of a point-to-point neighbor:
configure ospf vlan accounting neighbor delete 10.0.0.1
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the OSPF timer interval.
Syntax Description
Default
• retransmit interval—5 seconds.
Usage Guidelines
Specify the following:
• retransmit interval—If you set an interval that is too short, unnecessary retransmissions will result.
Example
The following command configures the OSPF retransmit interval on the VLAN accounting:
configure ospf vlan accounting timer 10
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures RIP on an IP interface.
Syntax Description
Default
All. If no VLAN is specified, then all is assumed.
Usage Guidelines
When an IP interface is created, RIP configuration is disabled on the interface by default. When the RIP
interface is disabled, the parameters are not reset to default automatically.
Example
The following command configures RIP on the VLAN finance:
configure rip add finance
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables RIP on an IP interface.
Syntax Description
Default
All. If no VLAN is specified, then all is assumed.
Usage Guidelines
When an IP interface is created, RIP configuration is disabled on the interface by default. When the RIP
interface is disabled, the parameters are not reset to default automatically.
Example
The following command deletes RIP on a VLAN named finance:
configure rip delete finance
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the RIP garbage time.
Syntax Description
Default
120 seconds.
Usage Guidelines
None.
Example
The following command configures the RIP garbage time to have a 60-second delay:
configure rip garbagetime 60
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the route timeout period.
Syntax Description
Default
180 seconds.
Usage Guidelines
If a router does not receive an update message from its neighbor within the route timeout period (180
seconds by default), the router assumes the connection between it and its neighbor is no longer
available.
Example
The following example sets the route timeout period to 120 seconds:
configure rip routetimeout 120
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Changes the RIP receive mode for one or more VLANs.
Syntax Description
Default
Any.
Usage Guidelines
If no VLAN is specified, the setting is applied to all VLANs.
Example
The following command configures the receive mode for the VLAN finance to accept only RIP version 1
format packets:
configure rip rxmode v1only finance
History
This command was available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the all keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Changes the RIP transmission mode for one or more VLANs.
Syntax Description
Default
v2only.
Usage Guidelines
If no VLAN is specified, the setting is applied to all VLANs.
Example
The following command configures the transmit mode for the VLAN finance to transmit version 2
format packets to the broadcast address:
configure rip txmode v1comp finance
History
This command was available in ExtremeWare 7.1e.
This command was modified in ExtremeWare 7.2e to support the all keyword.
Platform Availability
This command is available on the “e” series platforms.
Description
Specifies the time interval in seconds within which RIP sends update packets.
Syntax Description
Default
30 seconds.
Usage Guidelines
The router exchanges an update message with each neighbor every 30 seconds (default value), or if
there is a change to the overall routed topology (also called triggered updates). The timer granularity is 10
seconds.
Example
The following command sets the update timer to 60 seconds:
configure rip updatetime 60
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the cost (metric) of the interface.
Syntax Description
Default
The default setting is 1.
Usage Guidelines
None.
Example
The following command configures the cost for the VLAN finance to a metric of 3:
configure rip vlan finance cost 3
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures RIP to suppress certain routes when performing route advertisements.
Syntax Description
Default
N/A.
Usage Guidelines
Use an access profile to determine trusted RIP router neighbors for the VLAN on the switch running
RIP.
Using the none mode, the access profile can contain a combination of permit and deny entries. Each
entry must have a permit or deny attribute. The operation is compared with each entry in the list. When
a match is found, the operation is either permitted or denied, depending on the configuration of the
matched entry. If no match is found, the operation is implicitly denied.
Example
The following command uses the access profile nosales to determine which RIP routes are advertised
into the VLAN backbone:
configure rip vlan backbone export-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures RIP to ignore certain routes received from its neighbor.
Syntax Description
Default
N/A.
Usage Guidelines
Configures an import filter policy, which uses an access profile to determine which RIP routes are
accepted as valid routes. This policy can be combined with the trusted neighbor policy to accept
selected routes only from a set of trusted neighbors.
Using the none mode, the access profile can contain a combination of permit and deny entries. Each
entry must have a permit or deny attribute. The operation is compared with each entry in the list. When
a match is found, the operation is either permitted or denied, depending on the configuration of the
matched entry. If no match is found, the operation is implicitly denied.
Example
The following command configures the VLAN backbone to accept selected routes from the access profile
nosales:
configure rip vlan backbone import-filter nosales
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a trusted neighbor policy, which uses an access profile to determine trusted RIP router
neighbors for the VLAN on the switch running RIP.
Syntax Description
Default
N/A.
Usage Guidelines
Using the none mode, the access profile can contain a combination of permit and deny entries. Each
entry must have a permit or deny attribute. The operation is compared with each entry in the list. When
a match is found, the operation is either permitted or denied, depending on the configuration of the
matched entry. If no match is found, the operation is implicitly denied.
Example
The following command configures RIP to use the access profile nointernet to determine from which RIP
neighbor to receive (or reject) the routes to the VLAN backbone:
configure rip vlan backbone trusted-gateway nointernet
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Creates an OSPF area.
Syntax Description
Default
Area 0.0.0.0
Usage Guidelines
Area 0.0.0.0 does not need to be created. It exists by default.
Example
The following command creates an OSPF area:
create ospf area 1.2.3.4
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Deletes an OSPF area.
Syntax Description
Default
N/A.
Usage Guidelines
An OSPF area cannot be deleted if it has an associated interface.
Example
The following command deletes an OSPF area:
delete ospf area 1.2.3.4
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable ospf
disable ospf
Description
Disables the OSPF process for the router.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command disables the OSPF process for the router:
disable ospf
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables opaque LSAs across the entire system.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Opaque LSAs are a generic OSPF mechanism used to carry auxiliary information in the OSPF database.
Opaque LSAs are most commonly used to support OSPF traffic engineering.
Normally, support for opaque LSAs is auto-negotiated between OSPF neighbors. In the event that you
experience interoperability problems, you can disable opaque LSAs.
If your network uses opaque LSAs, all routers on your OSPF network should support opaque LSAs.
Routers that do not support opaque LSAs do not store or flood them. At minimum a
well-interconnected subsection of your OSPF network needs to support opaque LSAs to maintain
reliability of their transmission.
On an OSPF broadcast network, the designated router (DR) must support opaque LSAs or none of the
other routers on that broadcast network will reliably receive them. You can use the OSPF priority
feature to give preference to an opaque-capable router, so that it becomes the elected DR.
For transmission to continue reliably across the network, the backup designated router (BDR) must also
support opaque LSAs.
Example
The following command disables opaque LSAs across the entire system:
disable ospf capability opaque-lsa
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables redistribution of routes to OSPF.
Syntax Description
Default
The default setting is disabled.
Usage Guidelines
Use this command to stop OSPF from exporting routes derived from other protocols.
Example
The following command disables OSPF to export RIP-related routes to other OSPF routers:
disable ospf export rip
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable rip
disable rip
Description
Disables RIP for the whole router.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
RIP has a number of limitations that can cause problems in large networks, including:
• A limit of 15 hops between the source and destination networks
• A large amount of bandwidth taken up by periodic broadcasts of the entire routing table
• Slow convergence
• Routing decisions based on hop count; no concept of link costs or delay
• Flat networks; no concept of areas or boundaries
Example
The following command disables RIP for the whole router:
disable rip
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the RIP aggregation of subnet information on a RIP version 2 (RIPv2) interface.
Syntax Description
This command has no arguments or variables.
Default
RIP aggregation is disabled by default.
Usage Guidelines
The disable RIP aggregation command disables the RIP aggregation of subnet information on a switch
configured to send RIPv2-compatible traffic. The switch summarizes subnet routes to the nearest class
network route. The following rules apply when using RIP aggregation:
• Within a class boundary, no routes are aggregated.
• If aggregation is disabled, subnet routes are never aggregated, even when crossing a class boundary.
Example
The following command disables RIP aggregation on the interface:
disable rip aggregation
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables RIP from redistributing routes from other routing protocols.
Syntax Description
direct Specifies interface routes (only interfaces that have IP forwarding enabled are
exported).
ospf Specifies all OSPF routes.
ospf-extern1 Specifies OSPF external route type 1.
ospf-extern2 Specifies OSPF external route type 2.
ospf-inter Specifies OSPF-inter area routes.
ospf-intra Specifies OSPF-intra area routes.
static Specifies static routes.
Default
Disabled.
Usage Guidelines
This command disables the exporting of static, direct, and OSPF-learned routes into the RIP domain.
Example
The following command disables RIP from redistributing any routes learned from OSPF:
disable rip export ospf
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the redistribution of static routes.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Static routes are manually entered into the routing table. Static routes are used to reach networks not
advertised by routers. You can configure 64 static unicast routes. Static routes can also be used for
security reasons, to control which routes you want advertised by the router. You can decide if you want
all static routes to be advertised. Static routes are never aged out of the routing table.
A static route must be associated with a valid IP subnet. An IP subnet is associated with a single VLAN
by its IP address and subnet mask. If the VLAN is subsequently deleted, the static route entries using
that subnet must be deleted manually.
Example
The following command disables the redistribution of static routes:
disable rip exportstatic
History
This command was removed in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the advertisement of a default route.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following command unconfigures a default route to be advertised by RIP if no other default route
is advertised:
disable rip originate-default cost 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables poison reverse algorithm for RIP.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Like split horizon, poison reverse is a scheme for eliminating the possibility of loops in the routed
topology. In this case, a router advertises a route over the same interface that supplied the route, but the
route uses a hop count of 16, defining it as unreachable.
Example
The following command disables the split horizon with poison reverse algorithm for RIP:
disable rip poisonreverse
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the split horizon algorithm for RIP.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Split horizon is a scheme for avoiding problems caused by including routes in updates sent to the
router from which the route was learned. Split horizon omits routes learned from a neighbor in updates
sent to that neighbor.
Example
The following command disables the split horizon algorithm for RIP:
disable rip splithorizon
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the trigger update mechanism. Triggered updates are a mechanism for immediately notifying a
router’s neighbors when the router adds or deletes routes or changes their metric.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Triggered updates occur whenever a router changes the metric for a route and it is required to send an
update message immediately, even if it is not yet time for a regular update message to be sent. This will
generally result in faster convergence, but may also result in more RIP-related traffic.
Example
The following command disables the trigger update mechanism:
disable rip triggerupdate
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable ospf
enable ospf
Description
Enables the OSPF process for the router.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command enables the OSPF process for the router:
enable ospf
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables opaque LSAs across the entire system.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Opaque LSAs are a generic OSPF mechanism used to carry auxiliary information in the OSPF database.
Opaque LSAs are most commonly used to support OSPF traffic engineering.
Normally, support for opaque LSAs is auto-negotiated between OSPF neighbors. In the event that you
experience interoperability problems, you can disable opaque LSAs.
If your network uses opaque LSAs, all routers on your OSPF network should support opaque LSAs.
Routers that do not support opaque LSAs do not store or flood them. At minimum a
well-interconnected subsection of your OSPF network needs to support opaque LSAs to maintain
reliability of their transmission.
On an OSPF broadcast network, the designated router (DR) must support opaque LSAs or none of the
other routers on that broadcast network will reliably receive them. You can use the OSPF priority
feature to give preference to an opaque-capable router, so that it becomes the elected DR.
For transmission to continue reliably across the network, the backup designated router (BDR) must also
support opaque LSAs.
Example
The following command enables opaque LSAs across the entire system:
enable ospf capability opaque-lsa
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables redistribution of routes to OSPF.
Syntax Description
Default
The default tag number is 0. The default setting is disabled.
Usage Guidelines
After it is enabled, the OSPF router is considered to be an ASBR. Interface routes that correspond to the
interface that has OSPF enabled are ignored.
Exporting routes from OSPF to RIP, and from RIP to OSPF, are discrete configuration functions. To run
OSPF and RIP simultaneously, you must first configure both protocols and then verify the independent
operation of each. Then you can configure the routes to export from OSPF to RIP and the routes to
export from RIP to OSPF.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into OSPF. If the cost
metric is set to 0, the cost is inserted from the route. The tag value is used only by special routing
applications. Use 0 if you do not have specific requirements for using a tag. The tag value in this
instance has no relationship with 802.1Q VLAN tagging.
The same cost, type, and tag values can be inserted for all the export routes, or route maps can be used
for selective insertion. When a route map is associated with the export command, the route map is
applied on every exported route. The exported routes can also be filtered using route maps.
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the redistribution of local interface (direct) routes into the OSPF domain. This will not export
the loopback address of 127.0.0.1.
Syntax Description
Default
The default tag number is 0. The default setting is disabled.
Usage Guidelines
After it is enabled, the OSPF router is considered to be an ASBR. Interface routes that correspond to the
interface that has OSPF enabled are ignored.
Exporting routes from OSPF to RIP, and from RIP to OSPF, are discreet configuration functions. To run
OSPF and RIP simultaneously, you must first configure both protocols and then verify the independent
operation of each. Then you can configure the routes to export from OSPF to RIP and the routes to
export from RIP to OSPF.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into OSPF. If the cost
metric is set to 0, the cost is inserted from the route. The tag value is used only by special routing
applications. Use 0 if you do not have specific requirements for using a tag. The tag value in this
instance has no relationship with 802.1Q VLAN tagging.
The same cost, type, and tag values can be inserted for all the export routes, or route maps can be used
for selective insertion. When a route map is associated with the export command, the route map is
applied on every exported route. The exported routes can also be filtered using route maps.
Example
The following command enables the distribution of local interface (direct) routes into the OSPF domain:
enable ospf export direct cost 1 ase-type-1 tag 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the redistribution of RIP to OSPF.
Syntax Description
Default
The default tag number is 0. The default setting is disabled.
Usage Guidelines
After it is enabled, the OSPF router is considered to be an ASBR.
This command enables the exporting of RIP by way of LSA to other OSPF routers as AS-external type 1
or type 2 routes.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into OSPF. The tag value
is used only by special routing applications. Use 0 if you do not have specific requirements for using a
tag. The tag value in this instance has no relationship with 802.1Q VLAN tagging.
When re-distributing RIP routes, you should turn off RIP aggregation unless you are expertly familiar
with the possible consequences and impact. By default, new configurations of RIP disable RIP
aggregation. In previous ExtremeWare versions, RIP aggregation is enabled by default. Verify the
configuration using the command show rip.
Example
The following command enables the exporting of RIP to OSPF:
enable ospf export rip cost 1 ase-type-1 tag 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the redistribution of static routes to OSPF.
Syntax Description
Default
The default tag number is 0. The default setting is disabled.
Usage Guidelines
After it is enabled, the OSPF router is considered to be an ASBR.
This command enables the redistribution of static routes by way of LSA to other OSPF routers as
AS-external type 1 or type 2 routes.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into OSPF. The tag value
is used only by special routing applications. Use 0 if you do not have specific requirements for using a
tag. The tag value in this instance has no relationship with 802.1Q VLAN tagging.
Example
The following command enables the exporting of static routes to OSPF:
enable ospf export static cost 0 ase-type-1 tag 0
History
This command was first available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Enables a default external LSA to be generated by OSPF, if no other default route is originated by OSPF
by way of RIP and static route re-distribution.
Syntax Description
Default
N/A.
Usage Guidelines
If always is specified, OSPF always advertises the default route. If always is not specified, OSPF adds
the default LSA if a reachable default route is in the route table.
Example
The following command generates a default external type-1 LSA:
enable ospf originate-default cost 1 ase-type-1 tag 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable rip
enable rip
Description
Enables RIP for the whole router.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
RIP has a number of limitations that can cause problems in large networks, including:
• A limit of 15 hops between the source and destination networks
• A large amount of bandwidth taken up by periodic broadcasts of the entire routing table
• Slow convergence
• Routing decisions based on hop count; no concept of link costs or delay
• Flat networks; no concept of areas or boundaries
Example
The following command enables RIP for the whole router:
enable rip
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the RIP aggregation of subnet information on a RIP version 2 (RIPv2) interface.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
The enable (disable) rip aggregation command enables (disables) the RIP aggregation of subnet
information on an interface configured to send RIPv1 or RIPv2-compatible traffic. The switch
summarizes subnet routes to the nearest class network route. The following rules apply when using RIP
aggregation:
• Subnet routes are aggregated to the nearest class network route when crossing a class boundary.
• Within a class boundary, no routes are aggregated.
• If aggregation is enabled, the behavior is the same as in RIPv1.
• If aggregation is disabled, subnet routes are never aggregated, even when crossing a class boundary.
Example
The following command enables RIP aggregation on the interface:
enable rip aggregation
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables RIP to redistribute routes from other routing functions.
Syntax Description
direct Specifies interface routes (only interfaces that have IP forwarding enabled are
exported).
ospf Specifies all OSPF routes.
ospf-extern1 Specifies OSPF external route type 1.
ospf-extern2 Specifies OSPF external route type 2.
ospf-inter Specifies OSPF-inter area routes.
ospf-intra Specifies OSPF-intra area routes.
static Specifies static routes.
cost <number>t Specifies the cost metric, from 0-15. If set to 0, RIP uses the route metric
obtained from the route origin.
tag <number> Specifies a tag number.
Default
Disabled.
Usage Guidelines
This command enables the exporting of static, direct and OSPF-learned routes into the RIP domain. You
can choose which types of OSPF routes are injected, or you can simply choose ospf, which injects all
learned OSPF routes regardless of type.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into OSPF. If the cost
metric is set to 0, the cost is inserted from the route. The tag value is used only by special routing
applications. Use 0 if you do not have specific requirements for using a tag.
Example
The following command enables RIP to redistribute routes from all OSPF routes:
enable rip export ospf cost 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the redistribution of static routes.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
Static routes are manually entered into the routing table. Static routes are used to reach networks not
advertised by routers. You can configure 64 static unicast routes. Static routes can also be used for
security reasons, to control which routes you want advertised by the router. You can decide if you want
all static routes to be advertised. Static routes are never aged out of the routing table.
A static route must be associated with a valid IP subnet. An IP subnet is associated with a single VLAN
by its IP address and subnet mask. If the VLAN is subsequently deleted, the static route entries using
that subnet must be deleted manually.
Example
The following command enables the redistribution of static routes:
enable rip exportstatic
History
This command was removed in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a default route to be advertised by RIP if no other default route is advertised.
Syntax Description
Default
Disabled.
Usage Guidelines
If always is specified, RIP always advertises the default route to its neighbors. If always is not specified,
RIP adds a default route if a reachable default route is not in the route table.
The cost metric is inserted for all RIP-learned, static, and direct routes injected into OSPF. If the cost
metric is set to 0, the cost is inserted from the route. The tag value is used only by special routing
applications. Use 0 if you do not have specific requirements for using a tag.
Example
The following command configures a default route to be advertised by RIP if no other default route is
advertised:
enable rip originate-default cost 0
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables poison reverse algorithm for RIP.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Like split horizon, poison reverse is a scheme for eliminating the possibility of loops in the routed
topology. In this case, a router advertises a route over the same interface that supplied the route, but the
route uses a hop count of 16, defining it as unreachable.
Example
The following command enables the split horizon with poison reverse algorithm for RIP:
enable rip poisonreverse
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the split horizon algorithm for RIP.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Split horizon is a scheme for avoiding problems caused by including routes in updates sent to the
router from which the route was learned. Split horizon omits routes learned from a neighbor in updates
sent to that neighbor.
Example
The following command enables the split horizon algorithm for RIP:
enable rip splithorizon
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the trigger update mechanism. Triggered updates are a mechanism for immediately notifying a
router’s neighbors when the router adds or deletes routes or changes their metric.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
Triggered updates occur whenever a router changes the metric for a route and it is required to send an
update message immediately, even if it is not yet time for a regular update message to be sent. This will
generally result in faster convergence, but may also result in more RIP-related traffic.
Example
The following command enables the trigger update mechanism:
enable rip triggerupdate
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show ospf
show ospf
Description
Displays global OSPF information.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays global OSPF information:
show ospf
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays information about a particular OSPF area.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays information about OSPF area 1.2.3.4:
show ospf area 1.2.3.4
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays information about all OSPF areas.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays information about all OSPF areas:
show ospf area detail
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the OSPF external route aggregation configuration.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command displays the OSPF external route aggregation configuration:
show ospf ase-summary
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays detailed information about all OSPF interfaces.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays information about all OSPF interfaces:
show ospf interfaces detail
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays information about one or all OSPF interfaces.
Syntax Description
Default
If no argument is specified, all OSPF interfaces are displayed.
Usage Guidelines
None.
Example
The following command displays information about one or all OSPF interfaces on the VLAN accounting:
show ospf interfaces vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays a table of the current LSDB.
Syntax Description
Default
Display in summary format.
Usage Guidelines
ExtremeWare provides several filtering criteria for the show ospf lsdb command. You can specify
multiple search criteria and only results matching all of the criteria are displayed. This allows you to
control the displayed entries in large routing tables.
A common use of this command is to omit all optional parameters, resulting in the following shortened
form:
show ospf lsdb
The shortened form displays all areas and all types in a summary format.
You can filter the display using either the area ID, the remote router ID, or the link-state ID. The default
setting is all with no detail. If detail is specified, each entry includes complete LSA information.
Example
The following command displays all areas and all types in a summary format:
show ospf lsdb
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays virtual link information about a particular router or all routers.
Syntax Description
Default
N/A.
Usage Guidelines
area identifier—Transit area used for connecting the two end-points. The transit area cannot have the IP
address 0.0.0.0.
Example
The following command displays virtual link information about a particular router:
show ospf virtual-link routerid 1.2.3.4 10.1.6.1
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
show rip
show rip {detail}
Description
Displays RIP specific configuration and statistics for all VLANs.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays RIP specific configuration and statistics for all VLANs:
show rip
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays RIP-specific statistics for all VLANs.
Syntax Description
Default
All.
Usage Guidelines
Statistics include the following per interface:
• Packets transmitted
• Packets received
• Bad packets received
• Bad routes received
• Number of RIP peers
• Peer information
Example
The following command displays RIP-specific statistics for all VLANs:
show rip stat
History
This command was available in ExtremeWare 7.1e
Platform Availability
This command is available on the “e” series platforms.
Description
Displays RIP specific statistics for a VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays RIP specific statistics for the VLAN accounting:
show rip stat accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays RIP configuration and statistics for a VLAN.
Syntax Description
Default
All.
Usage Guidelines
None.
Example
The following command displays RIP configuration and statistics for the VLAN accounting:
show rip vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure ospf
unconfigure ospf {vlan <vlan name> | area <area identifier>}
Description
Resets one or all OSPF interfaces to the default settings.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command resets the OSPF interface to the default settings on the VLAN accounting:
unconfigure ospf accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure rip
unconfigure rip {vlan <vlan name>}
Description
Resets all RIP parameters to the default VLAN.
Syntax Description
Default
All.
Usage Guidelines
Does not change the enable/disable state of the RIP settings.
Example
The following command deletes RIP configuration from the VLAN finance:
unconfigure rip finance
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
IP multicast routing is a function that allows a single IP host to send a packet to a group of IP hosts.
This group of hosts can include devices that reside on the local network, within a private network, or
outside of the local network.
NOTE
You must configure IP unicast routing before you configure IP multicast routing.
IGMP is a protocol used by an IP host to register its IP multicast group membership with a router.
Periodically, the router queries the multicast group to see if the group is still in use. If the group is still
active, a single IP host responds to the query, and group registration is maintained.
IGMP is enabled by default on the switch. However, the switch can be configured to disable the
generation of period IGMP query packets. IGMP query should be enabled when the switch is
configured to perform IP unicast or IP multicast routing.
Protocol Independent Multicast (PIM) is a multicast routing protocol with no inherent route exchange
mechanism. The switch supports sparse mode operation.
Protocol independent Multicast-Sparse Mode (PIM-SM) routes multicast packets to multicast groups.
The sparse mode protocol is designed for installations where the multicast groups are scattered over a
large area such as a wide area network (WAN). PIM-SM is a router-to-router protocol, so all routers and
switches must upgrade to the same PIM-SM version. Summit 400 switches use PIM-SM version 2 to
forward IP packets that are destined to the IP addresses in the Class D Range to multiple networks
using the Multicast Routing information setup.
PIM-SM is an explicit join and prune protocol that is a mixture of the shared tree and shortest path tree
(SPT) models. The routers must explicitly join the group(s) in which they are interested in becoming a
member, which is beneficial for large networks that have group members who are sparsely distributed.
PIM-SM is not dependant on a specific unicast routing protocol.
Using PIM-SM, the router sends a join message for groups learned from IGMP to the rendezvous point
(RP). The RP is a central multicast router that is responsible for receiving and distributing multicast
packets. By default, the RP is selected dynamically (but not automatically). You can also define a static
RP in your network, using the following command:
configure pim crp static <rp address> [none | <access profile>] {<priority [0-254]>}
When a router has a multicast packet to distribute, it encapsulates the packet in a unicast message and
sends it to the RP. The RP decapsulates the multicast packet and distributes it among all member
routers.
When a last-hop receiving-router determines that the multicast rate from of a particular group has
exceeded a configured threshold, that router can send an explicit join to the originating router. When
this occurs, the receiving router gets the multicast directly from the sending router, and bypasses the RP.
Description
Removes one or all IGMP groups.
Syntax Description
Default
N/A.
Usage Guidelines
This command can be used by network operations to manually remove IGMP group entries instantly.
Example
The following command clears IGMP groups from VLAN accounting:
clear igmp group accounting
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes one or all IGMP snooping entries.
Syntax Description
Default
N/A.
Usage Guidelines
This command can be used by network operations to manually remove IGMP snooping entries
instantly. However, removing an IGMP snooping entry can disrupt the normal forwarding of multicast
traffic.
The static IGMP snooping entry will not be removed. The dynamic IGMP snooping entry will be
removed, then re-created upon the next general query.
Example
The following command clears IGMP snooping from VLAN accounting:
clear igmp snooping accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the IP multicast cache table.
Syntax Description
Default
If no options are specified, all IP multicast cache entries are flushed.
Usage Guidelines
This command can be used by network operators to manually remove IPMC hardware forwarding
cache entries instantly. If the source is available, caches will be re-created, otherwise caches are removed
permanently. This command can disrupt the normal forwarding of multicast traffic.
Example
The following command resets the IP multicast table for group 224.1.2.3:
clear ipmc cache 224.1.2.3
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Resets the IP multicast forwarding hardware entry.
Syntax Description
Default
N/A.
Usage Guidelines
If no options are specified, all IP multicast forwarding database entries are cleared. This command has
an effect similar to the command clear ipmc cache, except that the targets are the forwarding
database entries.
Example
The following command resets the IP multicast forwarding database entry:
clear ipmc fdb group 224.1.2.3 sender 10.0.0.0/24
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
configure igmp
configure igmp <query interval> <query response interval> <last member
query interval>
Description
Configures the Internet Group Management Protocol (IGMP) timers.
Syntax Description
query interval Specifies the interval (in seconds) between general queries.
query response interval Specifies the maximum query response time (in seconds).
last member query interval Specifies the maximum group-specific query response time (in seconds).
Default
• query interval—125 seconds
• query response interval—10 seconds
• last member query interval—1 second
Usage Guidelines
Timers are based on RFC2236. Specify the following:
• query interval—The amount of time, in seconds, the system waits between sending out general
queries. The range is 1 to 429,496,729 seconds.
• query response interval—The maximum response time inserted into the periodic general queries.
The range is 1 to 25 seconds.
• last member query interval—The maximum response time inserted into a group-specific query sent
in response to a leave group message. The range is 1 to 25 seconds.
Example
The following command configures the IGMP timers:
configure igmp 100 5 1
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures VLAN ports to receive the traffic from a multicast group, even if no IGMP joins have been
received on the port.
Syntax Description
Default
None.
Usage Guidelines
Use this command to forward a particular multicast group to VLAN ports. In effect, this command
emulates a host on the port that has joined the multicast group. As long as the port is configured with
the static entry, multicast traffic for that multicast group will be forwarded to that port.
The switch sends proxy IGMP messages in place of those generated by a real host. The proxy messages
use the VLAN IP address for source address of the messages. If the VLAN has no IP address assigned,
the proxy IGMP message will use 0.0.0.0 as the source IP address.
The multicast group should be in the class-D multicast address space, but should not be in the multicast
control packets range (224.0.0.x/24).
If the ports also have an IGMP filter configured, the filter entries take precedence. IGMP filters are
configured using the command:
configure igmp snooping vlan <vlan name> ports <portlist> filter <access
profile>
Example
The following command configures a static IGMP entry so the multicast group 224.34.15.37 will be
forwarded to VLAN marketing on ports 2-4:
configure igmp snooping marketing ports 2-4 add static group 224.34.15.37
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes the port configuration that causes multicast group traffic to be forwarded, even if no IGMP
leaves have been received on the port.
Syntax Description
Default
None.
Usage Guidelines
Use this command to remove an entry created by the following command:
configure igmp snooping vlan <vlan name> ports <portlist> add static
group <group address>
Example
The following command removes a static IGMP entry that forwards the multicast group 224.34.15.37 to
the VLAN marketing on ports 2-4:
configure igmp marketing ports 2-4 delete static group 224.34.15.37
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures VLAN ports to forward the traffic from all multicast groups, even if no IGMP joins have
been received on the port.
Syntax Description
Default
None.
Usage Guidelines
Use this command to forward all multicast groups to the specified VLAN ports. In effect, this command
emulates a multicast router attached to those ports. As long as the ports are configured with the static
entry, all available multicast traffic will be forwarded to those ports.
Example
The following command configures a static IGMP entry so all multicast groups will be forwarded to
VLAN marketing on ports 1-4:
configure igmp snooping marketing ports 1-4 add static router
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Removes the configuration that causes VLAN ports to forward the traffic from all multicast groups,
even if no IGMP joins have been received on the port.
Syntax Description
Default
None.
Usage Guidelines
Use this command to remove the static IGMP entry created with the following command:
configure igmp snooping vlan <vlan name> ports <portlist> add static router
Example
The following command removes the static IGMP entry that caused all multicast groups to be
forwarded to VLAN marketing on ports 1-4:
configure igmp snooping marketing ports 1-4 delete static router
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an IGMP snooping access profile filter on VLAN ports.
Syntax Description
Default
None.
Usage Guidelines
Use this command to filter multicast groups to the specified VLAN ports.
The access profile specified in this command must only include IP address type entries, and the IP
addresses included in the entries must be in the class-D multicast address space, but should not be in
the multicast control packets range (224.0.0.x/24).
To remove IGMP snooping filtering from a port, use the none keyword version of the command.
Example
The following command configures the access profile ap_multicast to filter multicast packets forwarded
to VLAN marketing on ports 1-4:
configure igmp snooping marketing ports 1-4 filter ap_multicast
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures certain multicast addresses to be slow path flooded within the VLAN.
Syntax Description
access profile Specifies an access profile with a list of multicast addresses to be handled.
The access profile must be type IP address.
none Specifies no access profile is to be used.
Default
None.
Usage Guidelines
With this command, a user can configure certain multicast addresses to be slow path flooded within the
VLAN, which otherwise will be fast path forwarded according to IGMP and/or layer 3 multicast
protocol.
The specified access profile <access profile> should contain a list of addresses which will determine
if certain multicast streams are to be treated specially. Typically, if the switch receives a stream with
destination address which is in the <access profile> in 'permit' mode, that stream will be software
flooded and no hardware entry would be installed.
When adding an IP address into the access-profile, a 32-bit host address is recommended.
This feature is meant to solve the multicast connectivity problem for unknown destination addresses
within system reserved ranges. Specifically this feature was introduced to solve the problem of
recognizing certain stream as control packets.
NOTE
The switch will not validate any IP address in the access profile used in this command. Therefore,
slow-path flooding should be used only for streams which are very infrequent, such as control packets.
It should not be used for multicast data packets. This option overrides any default mechanism of
hardware forwarding (with respect to IGMP) so it should be used with caution.
You can use the show ipconfig command to see the configuration of slow path flooding. It will be
listed in the IGMP snooping section of the display.
Example
Given access profile access1 created as follows:
create access-profile access1 type ipaddress
configure access-profile access1 add ipaddress 224.1.0.1/32
The following command configures the multicast data stream specified in access1 for slow path flooding:
configure igmp snooping flood-list access1
The following command specifies that no access profile is to be used, this effectively disabling slow path
flooding:
configure igmp snooping flood-list none
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the IGMP snooping leave timeout.
Syntax Description
Default
1000 ms.
Usage Guidelines
The range is 0 - 10000 ms (10 seconds). For timeout values of one second or less, you must set the
leave-timeout to a multiple of 100 ms. For values of more than one second, you must set the
leave-timeout to a multiple of 1000 ms (one second).
The specified time is the maximum leave timeout value. The switch could leave sooner if an IGMP
leave message is received before the timeout occurs.
Example
The following command configures the IGMP snooping leave timeout:
configure igmp snooping leave-timeout 10000
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the IGMP snooping timers.
Syntax Description
Default
The router timeout default setting is 260 seconds. The host timeout setting is 260 seconds.
Usage Guidelines
Timers should be set to approximately 2.5 times the router query interval in use on the network. Specify
the following:
• router timeout—The interval, in seconds, between the last time the router was discovered and the
current time. The range is 10 to 2,147,483,647 seconds (68 years). The default setting is 260 seconds.
• host timeout—The interval, in seconds, between the last IGMP group report message from the host
and the current time. The range is 10 to 2,147,483,647 seconds (68 years). The default setting is 260
seconds.
IGMP snooping is a layer 2 function of the switch. It does not require multicast routing to be enabled.
The feature reduces the flooding of IP multicast traffic. IGMP snooping optimizes the usage of network
bandwidth and prevents multicast traffic from being flooded to parts of the network that do not need it.
The switch does not reduce any IP multicast traffic in the local multicast domain (224.0.0.x).
IGMP snooping is enabled by default on the switch. If you are using multicast routing, IGMP snooping
can be enabled or disabled. If IGMP snooping is disabled, all IGMP and IP multicast traffic floods
within a given VLAN. IGMP snooping expects at least one device on every VLAN to periodically
generate IGMP query messages. Without an IGMP querier, the switch eventually stops forwarding IP
multicast packets to any port, because the IGMP snooping entries will time out, based on the value
specified in host timeout. An optional optimization for IGMP snooping is the strict recognition of
routers only if the remote devices are running a multicast protocol.
Example
The following command configures the IGMP snooping timers:
configure igmp snooping timer 600 600
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables PIM on an IP interface.
Syntax Description
Default
N/A
Usage Guidelines
When an IP interface is created, per-interface PIM configuration is disabled by default.
The switch supports edge mode operation. You can configure sparse mode on a per-interface basis. If
you specify passive, the interface does not act as a peer with another PIM router or switch. Typically all
non-passive interfaces align with USPF non-passive interfaces. A maximum of 2 non-passive PIM
interfaces is allowed on the “e” series.
Example
The following command enables PIM-SM multicast routing on VLAN accounting:
configure pim add vlan accounting
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a rendezvous point and its associated groups statically, for PIM sparse mode operation.
Syntax Description
Default
The default setting for priority is 0, which indicates highest priority. (A priority setting of 254 indicates
the lowest priority.)
Usage Guidelines
Using PIM-SM, the router sends a join message to the rendezvous point (RP). The RP is a central
multicast router that is responsible for receiving and distributing multicast packets. If you use a static
RP, all switches in your network must be configured with the same RP address for the same group
(range).
The RP address cannot be any locally configured IP interface on the series “e” switch. The series “e”
switches are not eligible to be RPs.
The access profile contains a list of multicast group accesses served by this RP.
Example
The following command statically configures an RP and its associated groups defined in access profile
rp-list:
configure pim crp static 10.0.3.1 rp-list
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables PIM on an interface.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command disables PIM-SM on VLAN accounting:
configure pim delete vlan accounting
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the initial PIM-SM periodic register rate.
Syntax Description
Default
Default is 0.
Usage Guidelines
Configuring a non-zero interval time can reduce the CPU load on the first hop in case register stop
messages are not received normally.
If a non-zero value is configured, the first hop switch would send register messages only at time second
intervals. The default value is zero, which sends continuos register messages. This command takes effect
only until the register stop message is not received, in other words, when the register suppression timer
is not running.
Example
The following command configures the initial PIM register rate limit interval:
configure pim register-rate-limit-interval 2
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures an interval for periodically sending null-registers.
Syntax Description
register-suppress-interval <time> Specifies an interval time in seconds. Range is 30 - 200 seconds. Default is
60.
register-probe-interval <time> Specifies an interval time in seconds. Default is 5.
Default
The following defaults apply:
• register-suppress-interval—60
• register-probe-interval—5
Usage Guidelines
The register-probe-interval time should be set less than the register-suppress-interval time. By default, a
null register is sent every 55 seconds (register-suppress-interval - register-probe-interval).
A response to the null register is expected within register probe interval. By specifying a larger interval,
a CPU peak load can be avoided because the null-registers are generated less frequently. The register
probe time should be less than half of the register suppress time, for best results.
Example
The following command configures the register suppress interval and register probe time:
configure pim register-suppress-interval 90 register-probe time 10
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the checksum computation to either include data (for compatibility with Cisco Systems
products) or to exclude data (for RFC-compliant operation), in the register message.
Syntax Description
Default
Include data
Usage Guidelines
None.
Example
The following command configures the checksum mode to include data for compatibility with Cisco
Systems products:
configure pim register-checksum-to include-data
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the threshold, in kbps, for switching to SPT. On leaf routers, this setting is based on data
packets. On the RP, this setting is based on register packets.
Syntax Description
Default
The default setting is 0.
Usage Guidelines
For the best performance leveraged by hardware forwarding, use default value “0,0”, or small values
below 16. Since the RP learns the source address from the register message, the RP threshold has no
effect.
Example
The following command sets the threshold for switching to SPT:
configure pim spt-threshold 4 16
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures the global PIM timers.
Syntax Description
hello interval Specifies the amount of time before a hello message is sent out by the PIM
router. The range is 1 to 65,519 seconds.
join prune interval Specifies the join/prune interval. The range is 1 to 65,519 seconds.
vlan name Specifies a VLAN name.
Default
• hello interval—30 seconds.
• join prune interval—60 seconds.
Usage Guidelines
None.
Example
The following command configures the global PIM timers on the VLAN accounting:
configure pim timer 150 300 vlan accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Configures a trusted neighbor policy.
Syntax Description
Default
No access profile, so all gateways are trusted.
Usage Guidelines
When the PIM protocol is used for routing IP multicast traffic, the switch can be configured to use an
access profile to determine trusted PIM router neighbors for the VLAN on the switch running PIM.
You can use this feature to select or exclude routers as peers. PIM control packets from non-trusted
sources are not processed.
Example
The following command configures a trusted neighbor policy on the VLAN backbone:
configure pim vlan backbone trusted-gateway
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable igmp
disable igmp {vlan <vlan name>}
Description
Disables IGMP on a router interface. If no VLAN is specified, IGMP is disabled on all router interfaces.
Syntax Description
Default
Enabled.
Usage Guidelines
IGMP is a protocol used by an IP host to register its IP multicast group membership with a router.
Periodically, the router queries the multicast group to see if the group is still in use. If the group is still
active, hosts respond to the query, and group registration is maintained.
IGMP is enabled by default on the switch. However, the switch can be configured to disable the
generation and processing of IGMP packets. IGMP should be enabled when the switch is configured to
perform IP unicast or IP multicast routing.
Example
The following command disables IGMP on VLAN accounting:
disable igmp vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables IGMP snooping.
Syntax Description
forward-mcrouter-only Specifies that the switch forwards all multicast traffic to the multicast router
only.
vlan name Specifies a VLAN.
Default
Enabled.
Usage Guidelines
If a VLAN is specified, IGMP snooping is disabled only on that VLAN, otherwise IGMP snooping is
disabled on all VLANs.
If the switch is in the forward-mcrouter-only mode, then the command disable igmp snooping
forward-mcrouter-only changes the mode so that all multicast traffic is forwarded to any IP router. If
not in the forward-mcrouter-mode, the command disable igmp snooping forward-mcrouter-only
has no effect.
To change the snooping mode you must disable IP multicast forwarding. Use the command:
disable ipmcforwarding
Example
The following command disables IGMP snooping on the VLAN accounting:
disable igmp snooping accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Disables the IGMP snooping proxy. The default setting is enabled.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
This command can be used for troubleshooting purpose. It should be enabled for normal network
operation.
Enabling the proxy allows the switch to suppress the duplicate join requests on a group to forward to
the connected layer 3 switch. The proxy also suppresses unnecessary IGMP leave messages so that they
are forwarded only when the last member leaves the group.
Example
The following command disables the IGMP snooping proxy:
disable igmp snooping with-proxy
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
disable ipmcforwarding
disable ipmcforwarding {vlan <vlan name>}
Description
Disables IP multicast forwarding on an IP interface.
Syntax Description
Default
Disabled.
Usage Guidelines
If no options are specified, all configured IP interfaces are affected. When new IP interfaces are added,
IP multicast forwarding is disabled by default.
IP forwarding must be enabled before enabling IP multicast forwarding, and IP multicast forwarding
must be disabled before disabling IP forwarding.
Disabling IP multicast forwarding disables any layer 3 forwarding for the streams coming to the
interface.
Example
The following command disables IP multicast forwarding on the VLAN accounting:
disable ipmcforwarding vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
disable pim
disable pim
Description
Disables PIM on the system.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following command disables PIM on the system:
disable pim
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable igmp
enable igmp {vlan <vlan name>}
Description
Enables IGMP on a router interface. If no VLAN is specified, IGMP is enabled on all router interfaces.
Syntax Description
Default
Enabled.
Usage Guidelines
IGMP is a protocol used by an IP host to register its IP multicast group membership with a router.
Periodically, the router queries the multicast group to see if the group is still in use. If the group is still
active, IP hosts respond to the query, and group registration is maintained.
IGMP is enabled by default on the switch. However, the switch can be configured to disable the
generation and processing of IGMP packets. IGMP should be enabled when the switch is configured to
perform IP unicast or IP multicast routing.
Example
The following command enables IGMP on the VLAN accounting:
enable igmp vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables IGMP snooping on the switch.
Syntax Description
forward-mcrouter-only Specifies that the switch forwards all multicast traffic to the multicast router
only.
vlan name Specifies a VLAN.
Default
Enabled.
Usage Guidelines
If a VLAN is specified, IGMP snooping is enabled only on that VLAN, otherwise IGMP snooping is
enabled on all VLANs.
• The forward-mcrouter-only mode forwards all multicast traffic to the multicast router (that is, the
router running PIM.
• When not in the forward-mcrouter-only mode, the switch forwards all multicast traffic to any IP
router (multicast or not).
To change the snooping mode you must disable IP multicast forwarding. To disable IP multicast
forwarding, use the command:
disable ipmcforwarding
To change the IGMP snooping mode from the forward-mcrouter-only mode to the
non-forward-mcrouter-only mode, use the command:
disable igmp snooping forward-mcrouter-only
The snooping mode is not changed from the non-forward-mcrouter-only mode to the
forward-mcrouter-only mode solely by enabling that mode. You must disable IGMP snooping, then
enable IGMP snooping for multicast only. Disable IP multicast forwarding, then use the following
commands:
Example
The following command enables IGMP snooping on the switch:
enable igmp snooping
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Enables the IGMP snooping proxy. The default setting is enabled.
Syntax Description
This command has no arguments or variables.
Default
Enabled.
Usage Guidelines
This command should be enabled for normal network operation. The command does not alter the
snooping setting. IP multicast forwarding should be disabled globally for this command.
Enabling the proxy allows the switch to suppress the duplicate join requests on a group to forward to
the connected layer 3 switch. The proxy also suppresses unnecessary IGMP leave messages so that they
are forwarded only when the last member leaves the group.
Example
The following command enables the IGMP snooping proxy:
enable igmp snooping with-proxy
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable ipmcforwarding
enable ipmcforwarding {vlan <vlan name>}
Description
Enables IP multicast forwarding on an IP interface.
Syntax Description
Default
Disabled.
Usage Guidelines
If no options are specified, all configured IP interfaces are affected. When new IP interfaces are added,
IPMC forwarding is disabled by default.
IP forwarding must be enabled before enabling IPMC forwarding, and IPMC forwarding must be
disabled before disabling IP forwarding.
Example
The following command enables IPMC forwarding on the VLAN accounting:
enable ipmcforwarding vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
enable pim
enable pim
Description
Enables PIM on the system.
Syntax Description
This command has no arguments or variables.
Default
Disabled.
Usage Guidelines
None.
Example
The following command enables PIM on the system:
enable pim
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
mrinfo
mrinfo <ip address> {from <ip address>} {timeout <seconds>}
Description
Initiates a request to get multicast information from a router.
Syntax Description
<ip address> Specifies an IP address. The first <ip address> parameter specifies the
unicast IP address of the router to query.
from Specifies the unicast address of an interface in the system to use as the
source address in the request.
timeout Specifies the time to wait before indicating a failure.
Defaults
• from—outgoing interface
• timeout—three seconds
Usage Guidelines
This command queries a multicast router for information useful for tracing and troubleshooting. The
command returns the following information:
• code version
• system multicast information
• interface information
— interface IP address
— interface multicast capabilities
— metric configured on the interface
— threshold configured on the interface
— count and IP address of the neighbors discovered on the interface
Example
The following command queries the router at 10.10.34.14:
mrinfo 10.10.34.14
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
mtrace
mtrace source <ip address> {destination <ip address>} {group <ip address>}
{from <ip address>} {gateway <ip address >} {timeout <seconds>}
{maximum-hops <number>}
Description
Initiates a request to trace the path of multicast traffic from the source to the destination of a multicast
group.
Syntax Description
Defaults
• destination—current system
• group—0.0.0.0
• from—outgoing interface to reach the source or destination
• gateway—destination 224.0.0.2
• timeout—three seconds
• maximum-hops—255
Usage Guidelines
This command relies on a feature of multicast routers that is accessed using the IGMP protocol. Since
multicast uses reverse path forwarding, a multicast trace is run from the destination to the source. A
query packet is sent to the last-hop multicast router. This router builds a trace response packet, fills in a
report for its hop, and forwards the packet to the next upstream router. As the request is forwarded,
each router in turn adds its own report to the trace response. When the request reaches the first-hop
router, the filled in request is sent back to the system requesting the trace. The request will also be
returned if the maximum hop limit is reached.
If a router does not support the mtrace functionality, it will silently drop the request packet and no
information will be returned. For this situation, you would send the trace with a small number of
maximum hops allowed, increasing the number of hops as the stream is traced.
The group IP address must be in the class-D multicast address space, but should not be in the multicast
control subnet range (224.0.0.x/24).
ExtremeWare based systems do not maintain packet forwarded statistics for each source/group
combination (S,G) and cannot return that information.
Example
The following command traces the multicast group 221.160.14.23 originating at 10.10.32.14 that is
coming through the gateway at 172.16.255.1:
mtrace source 10.10.34.14 group 227.160.14.23 gateway 172.16.255.1
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Lists the IGMP group membership for the specified VLAN.
Syntax Description
Default
N/A.
Usage Guidelines
If no VLAN is specified all VLANs are displayed. You can also filter the display by group address and
by multicast stream sender address.
Example
The following command lists the IGMP group membership for the VLAN accounting:
show igmp group 10.0.0.1 sender 10.0.0.2 accounting
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays IGMP snooping registration information and a summary of all IGMP timers and states.
Syntax Description
Default
N/A.
Usage Guidelines
The two types of IGMP snooping entry are sender entry and subscribed entry.
Example
The following command displays IGMP snooping registration information on the VLAN accounting:
show igmp snooping vlan accounting
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays IGMP snooping filters.
Syntax Description
Default
None.
Usage Guidelines
Use this command to display IGMP snooping filters configured on the specified VLAN. When no
VLAN is specified, all the filters will be displayed.
Example
To display the IGMP snooping filter configured on VLAN vlan101, use the following command:
show igmp snooping vlan101 filter
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays static IGMP snooping entries.
Syntax Description
Default
None.
Usage Guidelines
Use this command to display IGMP snooping filters configured on the specified VLAN. When no
VLAN is specified, all the filters will be displayed.
Example
To display the IGMP snooping static groups configured on VLAN vlan101, use the following command:
show igmp snooping vlan101 static group
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the IP multicast forwarding cache.
Syntax Description
Default
N/A.
Usage Guidelines
Displays the following information:
• IP group address
• IP source address / source mask
• Upstream neighbor (RPF neighbor)
• Interface (VLAN-port) to upstream neighbor
• Cache expiry time
• Routing protocol
When the detail option is specified, the switch displays the egress VLAN list and the pruned VLAN list.
Example
The following command displays the IP multicast table for group 224.1.2.3:
show ipmc cache 224.1.2.3
History
This command was available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
Description
Displays the IP multicast forwarding database in hardware.
Syntax Description
Default
N/A.
Usage Guidelines
If the group address is specified, only the IP multicast FDB entries corresponding to the group address
are displayed.
Example
The following command displays the IP multicast forwarding database:
show ipmc fdb
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show l2stats
show l2stats {vlan <vlan name>}
Description
Displays the counters for the number of packets bridged, switched, and snooped.
Syntax Description
Default
N/A.
Usage Guidelines
None.
Example
The following command displays the counters for the number of packets bridged, switched, and
snooped for the VLAN accounting:
show l2stats accounting
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
show pim
show pim {detail | rp-set {<IP multicast group>}| vlan <vlan name>}
Description
Displays the PIM configuration and statistics.
Syntax Description
Default
If no VLAN is specified, the configuration is displayed for all PIM interfaces.
If no multicast group is specified for the rp-set option (Rendezvous Point set), all groups are
displayed.
Usage Guidelines
The detail version of this command displays the global statistics for PIM register and register-stop
packets.
Example
The following command displays the PIM configuration and statistics for the VLAN accounting:
show pim accounting
History
This command was first available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure igmp
unconfigure igmp
Description
Resets all IGMP settings to their default values and clears the IGMP group table.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
None.
Example
The following command resets all IGMP settings to their default values and clears the IGMP group
table:
unconfigure igmp
History
This command was available in ExtremeWare 7.1e.
Platform Availability
This command is available on the “e” series platforms.
unconfigure pim
unconfigure pim {vlan <vlan name>}
Description
Resets all PIM settings on one or all VLANs to their default values.
Syntax Description
Default
If no VLAN is specified, the configuration is reset for all PIM interfaces.
Usage Guidelines
None.
Example
The following command resets all PIM settings on the VLAN accounting:
unconfigure pim vlan accounting
History
This command was first available in ExtremeWare 7.2e.
Platform Availability
This command is available on the “e” series platforms.
The Summit 300 series of switches and the Altitude 300 wireless port extend network service to wireless
802.11a/b/g clients within a fully integrated network infrastructure. Ports on the Summit 300 handle all
of the management functions typically associated with an access point. The Altitude 300 wireless port
serves as the radio transmitter and receiver, inheriting configuration information as soon as it is
attached to the switch and as changes are made to the wireless profiles after the system is deployed.
Wireless Devices
You configure ports on the Summit 300 with the “personality” of the device to be connected. Each port
contains separately configurable interfaces for each of its two radios (A and G).
Physical security for the wireless networks ceases to be a problem at the wireless access location
because the Altitude 300 wireless port does not store any security settings. Information is not stored in
the Altitude 300 wireless port, but loaded as needed from the switch. Even if the Altitude 300 wireless
port is physically moved, it can only be reconnected to another Summit 300 model.
You can set network policies at layers 2 and 3 to cover both the wired and wireless networks. In this
way you can block access to individuals suspected of intrusion across the entire network infrastructure.
In addition to traditional wired devices, the switch supports the Altitude 300 wireless port, third party
access points, and devices that rely on Power over Ethernet (PoE).
Description
Clears the counters on one or more wireless ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all ports.
Default
N/A
Usage Guidelines
Use this command to clear the counters for all wireless ports or for a port list.
Example
The following example clears all the counters for wireless ports:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
This command clears the scan results table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Use this command to clear the access point (AP) scan results on any interface: 1 or 2.
Examples
The following command clears the AP scan result table for port 1:18 on interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Clears the counters for a specific MAC address or for all clients.
Syntax Description
mac-address Specifies the MAC address of the client network interface card.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
N/A
Usage Guidelines
Although this command clear the counters, client entries are not removed from the client information
database.
Example
The following example clears the client-history counters on all ports and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Clears the statistics associated with a particular client or with all clients.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
hexoctet Specifies to use the hexadecimal value to identify a particular entry in the
client scan information table.
all Specifies all entries in the client scan information table.
Default
N/A.
Usage Guidelines
Use this command to clear client scan counters on any interface: 1 or 2.
Examples
The following example clears ports 15 and interface 1 of all client-scan statistics:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Clears the contents of the client scan information table or for a specific client MAC address.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
hexoctet Specifies to use the hexadecimal value to identify a particular entry in the
client scan information table.
all Specifies all entries in the client scan information table.
Default
N/A.
Usage Guidelines
Use this command to clear the client scan results on any interface: 1 or 2.
Examples
The following example clears ports 15 and interface 1 of all client-scan results:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Clears the log on one or more wireless ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all ports.
Default
N/A
Usage Guidelines
Use this command to clear the log for all wireless ports or for a port list.
Example
The following example clears the counters for wireless port 1:1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Enables debug tracing for Inter-Access Point Protocol (IAPP) on a per interface basis to troubleshoot
IAPP scenarios.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
debug-level Specifies a debug level in the following range (0-5). The default is 0 (off).
Default
Disabled.
Usage Guidelines
IAPP uses layer 2 updates to allow connected layer 2 devices to update forwarding tables with the
address of the client. The access point (AP) sends the updates on behalf of the clients by inserting the
MAC address of the mobile station in the source address. The switch looks up the UDP request packet
on the local subnet that contains the AP’s MAC address which contains the needed IP address. All APs
on the subnet receive this message. The AP with the matching MAC address sends a unicast response
packet with its IP address.
Example
The following example enables debug tracing for IAPP on port 1:15 with a debug level of 2:
configure debug-trace wireless ports 1:15 iapp 2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Specifies the frequency interval of the beacon in milliseconds.
Syntax Description
Default
40 ms
Usage Guidelines
A beacon is a packet broadcasted by the wireless port to synchronize the wireless network. The
beacon-interval is the time in milliseconds between beacons.
Examples
The following command sets the beacon interval to 100 ms:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Specifies the interval of the delivery traffic indication message (DTIM) in number of beacons.
Syntax Description
Default
2
Usage Guidelines
A DTIM field is a countdown field informing clients of the next listening window to broadcast and
multicast messages. When the wireless port has buffered broadcast or multicast messages, it sends the
next DTIM with a DTIM interval value. Its clients hear the beacons and awaken to receive the broadcast
and multicast messages.
Clients achieve greater power savings with larger DTM intervals. However, a larger DTM interval will
increase the delay before multicast frames are delivered to all stations.
Examples
The following command sets the DTIM interval to every 5 beacons:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Specifies the fragment size in bytes.
Syntax Description
Default
2345 bytes
Usage Guidelines
This value should remain at its default setting of 2345. It specifies the maximum size for a packet before
data is fragmented into multiple packets. If you experience a high packet error rate, you may slightly
increase the fragmentation threshold. Setting the fragmentation threshold too low may result in poor
network performance. Only minor modifications of this value are recommended.
Examples
The following command sets the fragment size to the default setting:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Specifies the number of transmission attempts of a frame larger than the request-to-send (RTS)
threshold.
Syntax Description
Default
7
Usage Guidelines
Use this command to set the number of transmission attempts for frames larger than the RTS threshold
setting in the same RF profile. The long-retry value specifies the number of attempts before a frame
will be discarded when a station attempts to retransmit a frame. Long retry applies to frames longer
than the RTS threshold and it is set to 7 by default. A frame requiring RTS/CTS clearing is
retransmitted seven times before being discarded.
To specify a the number of transmission attempts of a frame smaller than the RTS threshold, use the
following command:
configure rf-profile <name> rts-threshold <value>.
Examples
The following command sets the transmission attempts to 10:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Specifies the size of the packet preamble.
Syntax Description
Default
Short
Usage Guidelines
Use this command to configure the RF profile for 802.11b using the long packet preamble. Configure
the RF profile for 802.11a and 802.11g using the short packet preamble.
Examples
The following command sets the preamble to long:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Specifies the request to send (RTS) threshold in bytes.
Syntax Description
Default
2330 bytes
Usage Guidelines
Should you encounter inconsistent data flow, only minor modifications are recommended. If a network
packet is smaller than the preset RTS threshold size, the RTS and clear-to-send (CTS) mechanism is not
enabled. The wireless port sends RTS frames to a particular receiving station and negotiates the sending
of a data frame. After receiving an RTS, the wireless station responds with a CTS frame to acknowledge
the right to begin transmission.
Examples
The following command sets the RTS threshold to the default setting:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Specifies the number of transmission attempts of frames smaller than the request-to-send (RTS)
threshold.
Syntax Description
Default
4
Usage Guidelines
Use this command to set the number of transmission attempts for frames smaller than the RTS
threshold setting in the same RF profile. The short-retry value specifies the number of attempts
before a frame will be discarded when a station attempts to retransmit a frame. Short retry applies to
frames shorter than the RTS threshold and it is set to 4 by default. A frame requiring RTS/CTS clearing
is retransmitted four times before being discarded.
To specify a the number of transmission attempts of a frame larger than the RTS threshold, use the
following command:
configure rf-profile <name> long-retry <value>.
Examples
The following command sets the transmission attempts to 3:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the country identifier for the switch.
Syntax Description
Default
Extreme_default
Usage Guidelines
When the Summit 300 is set to factory defaults, you must configure the correct country code using the
country code properties listed in the following table. The country code feature allows you to configure
the approved 802.11a or 802.11b/g “channels” applicable to each of the supported countries.
Extreme Networks ships the Summit 300 to be programmed with Extreme Network's special
extreme_default country code, which brings up only the B/G radio in channel 6, and turns off the A
radio. When an Altitude 300 wireless port is connected and the Summit 300 is unable to determine the
country for which the Altitude is programmed, then the extreme_default country code is used. You
must program the country code on the Summit 300 to enable the remaining channels for the desired
country.
The Altitude 300 wireless port is shipped with a pre-programmed code for the following countries:
If you do not program the country code in the Summit 300, then the switch inherits the country code of
the first Altitude 300 wireless port that connects to it, if the Altitude is not programmed for the
'European Union and the Rest of World.
If there is a mismatch between the country codes between the Altitude 300 wireless port and the code
programmed on the Summit 300, the Altitude 300 wireless port is not allowed to come up.
Example
The following example configures the switch level property for Spain:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the default gateway IP address.
Syntax Description
ip_address Indicates the IP address of the default gateway. By default, this is the same IP
address as the management VLAN.
Default
0.0.0.0.
Usage Guidelines
The wireless default gateway IP address is usually set to the wireless management VLAN address. This
address is used by all wireless client traffic whose destination is upstream switches.
Example
The following example configures the switch level property for the default gateway:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Identifies the VLAN on which the Altitude 300 wireless port communicates with the Summit 300
switch.
Syntax Description
vlan name The name of the VLAN with which the Altitude 300 wireless port
communicates with the Summit 300 switch.
Default
Default VLAN
Usage Guidelines
Identifying the VLAN on which the Altitude 300 wireless port communicates with the switch is
required before wireless features can work. This VLAN can be the default VLAN and it can either have
a public or private IP address. This VLAN is an untagged VLAN on which all the Altitude 300 devices
are connected.
Example
The following example configures the switch level property for the default gateway:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets the Altitude 300-2d detachable antenna for indoor or outdoor use.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
indoor Specifies that the antenna is for indoor use.
outdoor Specifies that the antenna is for outdoor use.
Default
Indoor
Usage Guidelines
The detachable Altitude 300-2d antenna is compatible with the Summit 300 switches. Use this command
to configure the antenna type as indoor or outdoor and to comply with regulatory requirements.
Example
The following example configures all ports on the Altitude 300 for indoor use.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets the client current state age time-out value.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
seconds Specifies the amount of time in seconds when the client current state table
times out. Valid values are between 60 to 3600.
Default
600 seconds
Usage Guidelines
Client aging allows you to configure an aging timer for wireless stations. When a specified period of
time elapses with no data traffic from the client to the Altitude 300, the client is de-authenticated and
removed from all client station tables for that interface. After a client is aged out, it can reassociate and
re-authenticate to the Altitude 300. Age-out information can be collected from such events as client
station failures, station idle-timeouts, or a client abruptly leaving the wireless network without notifying
the associated Altitude 300. The timeout value is configured for each port and affects both interfaces 1
and 2.
Example
The following command configures ports 13-24 to time-out the client current state table at 120 seconds.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the client force-disassociation capability.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all-clients Specifies all clients associated with the port list.
every Specifies a repeating disassociation.
time Specifies a single disassociation at a specific time and date. If you do not
specify the every or time parameters, the user immediately disassociates.
cancel-scheduler Specifies to disable forced disassociation.
mac-address Specifies the MAC address of the client network interface card.
Default
No schedule.
Usage Guidelines
Force disassociation permits client user disassociation based on a recurring schedule, a date and time, or
a particular MAC address. You can also disassociate a user immediately. You can specify access based
on a preferred time periods, such as during off-hours, weekends, and holidays. You can also set up a
user policy on a RADIUS server to allow user authentication based on time of day.
Example
The following command configures ports 1:18 to force disassociate all clients every day at noon:.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Configures whether the health check reset function is on or off for the specified port or ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5,
all Specifies all ports.
on Indicates that the health check reset function is on. The port should be reset if
the health check timer expires.
off Indicates that the health check reset function is off. The port is not reset if the
health check timer expires.
Default
On
Usage Guidelines
This command determines whether the port is reset if the health check timer expires.
Example
The following command configures port 1:18 on the Summit 300-48 to use the health check facility:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to have the access point (AP) scan to send an SNMP trap when new stations are
added to the results table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Specifies that the AP scan should send an SNMP trap when new stations are
added to the results table.
off Specifies that the AP scan should not send an SNMP trap when new stations
are added to the results table.
Default
Off.
Usage Guidelines
Use this command when an SNMP-based remote management application is used to monitor the
network.
Example
The following command configures port 18 on the Summit 300-24 to have the AP scan to send an
SNMP trap when new stations are added to the results table:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Adds or removes specific channels for the off-channel access point (AP) scan.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
add Specifies to add the specific channel.
del Specifies to delete the specific channel.
current-channel Specifies to perform the scan on the current channel only.
channel-number Specifies to perform the scan on the channel indicated.
all-channels Specifies to perform the scan on all channels in a given country code.
every-channel Specifies to perform the scan on all channels regardless of the country code.
No beacons are sent on out-of-country-code channels.
Default
All channels.
Usage Guidelines
Use this command when the AP scan must be started on a particular interface.
Example
The following command causes scans on the current channel for wireless port 1:5 using interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Turns continuous off-channel scan on or off.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Specifies to turn the continuous off-channel scan on.
off Specifies to turn the continuous off-channel scan off.
Default
Scan on.
Usage Guidelines
Use this command to toggle continuous off-channel on a particular interface either on or off.
Example
The following command turns off the off-channel scan for wireless port 1:5 using interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to set the maximum time an off-channel scan waits at a particular channel.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
num Specifies the wait time in milliseconds. Valid entries are between 10 and
10000 milliseconds.
Default
600 ms.
Usage Guidelines
Use this command to specify the time that the access point (AP) should wait on a particular channel.
Example
The following command sets the wait time at 5 milliseconds:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Use this command to set the minimum time an off-channel scan waits at a particular channel.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5,
all Specifies all ports.
interface Specifies an interface: 1 or 2.
num Specifies the minimum wait time in milliseconds. Valid entries are between 10
and 10000 milliseconds.
Default
60 ms.
Usage Guidelines
Use this command to specify the minimum time that the access point (AP) should scan a particular
channel.
Example
The following command sets the wait time at 5 milliseconds:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to configure the interval between probe request packets for active off-channel
scanning.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
msec Specifies the time between probe request packets in milliseconds. Valid
entries are between 50 and 3600000 milliseconds.
Default
100 ms.
Usage Guidelines
Use this command to send probe requests at particular intervals on a selected channel during an access
point (AP) scan.
Example
The following example configures the interval between probe request packets to be 10 ms for port 1:9
on interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to have the access point (AP) scan to send an SNMP trap when new stations are
removed from the results table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Specifies that the AP scan should send an SNMP trap when new stations are
removed from the results table.
off Specifies that the AP scan should not send an SNMP trap when new stations
are removed from the results table.
Default
Off.
Usage Guidelines
Use this command to see a trap when stations are removed from the results table.
Example
The following command configures port 18 on the Summit 300-24 to have the AP scan to send an
SNMP trap when new stations are removed from the results table:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Sets the number of elements that the wireless interface stores.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
num Specifies the number of elements that the wireless interface stores. Valid
numbers are between 1 and 128.
Default
128.
Usage Guidelines
Use this command to specify the size of the results table.
Example
The following command configures port 1:7 and interface 1 to store 100 elements:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
This command sets the timeout threshold that sets when entries are aged out from the table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
time Specifies the time in seconds before an entry is aged out of the results table.
Valid numbers are between 0 and n (any number).
Default
300 seconds.
Usage Guidelines
Use this command to specify the age-out time for the clients in the results table.
Example
The following command configures port 1:7 and interface 1 to have a timeout threshold of 5 seconds:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to enable the sending of probes for active scanning.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Specifies to send probes (active scanning).
off Specifies not to send probes (passive scanning).
Default
Off.
Usage Guidelines
Use this command to enable the sending of probes. Setting send-probe to on specifies active scanning.
Setting send-probe to off specifies passive scanning.
Example
The following example enables the port range 1:15-1:24 using interface 1 to enable probes.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to configure the access point (AP) scan to send an SNMP trap when information
about an AP has changed.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Specifies to send an SNMP trap when an AP has changed.
off Specifies not to send an SNMP trap when an AP has changed.
Default
Off.
Usage Guidelines
None.
Example
The following example enables the port 20 on a Summit 300-24 using interface 1 to send an SNMP trap
when an AP has changed.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Configures a channel for the specified interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
interface Specifies an interface: 1 or 2.
0 Specifies that channels will be automatically selected. Enter ‘0’ (zero) to
specify auto selection.
channel Specifies a particular channel. (See Table 22 for valid values.)
Default
Auto for both interfaces
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and interface
2 supports 802.11b/g radio signals. The configure wireless port interface channel command
allows you to configure one of the two individual interfaces (1|2) on a port or ports. You can move an
interface from one profile to another without having to shut it down.
Valid channel values are shown in Table 22.
Example
The following command configures a channel for interface 2 on port 5 on a Summit 300-24:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Use this command to configure the client history size.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
integer Specifies the size of the client-history table in terms of the number of entries.
Valid values are between 1 and 128 entries.
Default
128.
Usage Guidelines
Use this command to specify the maximum number of entries that the client-history table can store.
Example
The following example sets the client-history table for ports 1:1-1:20 and interface 2 to 100 entries:
configure wireless ports 1:1-1:30 interface 2 client-history size 100
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Use this command to configure the client history timeout interval.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
number Specifies the timeout interval of the client-history table in seconds. Valid
numbers are between 0 and n (any number).
Default
600 seconds.
Usage Guidelines
Use this command to specify the timeout interval for the clients in the client history table.
Example
The following example sets the timeout interval for the client-history table for ports 1:1-1:20 and
interface 2 to 100 seconds.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Enables or disables traps from the client-scan feature when a new client is detected.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Enables traps when a new client is detected.
off Disables traps when a new client is detected.
Default
Off.
Usage Guidelines
Enabling traps can saturate management stations if an area is heavily populated.
Example
The following command enables traps for port 1:5 and interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Enables or disables traps from the client-scan feature when a new client has aged-out of the table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
on Enables traps when a client has aged out of the table.
off Disables traps when a client has aged out of the table.
Default
Off.
Usage Guidelines
Enabling traps can saturate management stations if an area is heavily populated.
Example
The following command disables traps for port 1:9 and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Configures the maximum number of entries in the client scan information table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
value Specifies the maximum number of entries in the client scan information table.
The default value is 128. (Range is unlimited.)
Default
128.
Usage Guidelines
Use this command to specify the maximum number of entries that the client-history table can store.
Example
The following command configures the maximum number of entries in the client scan table as 1000 for
port 1:5 and interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Configures the timeout period for entries in the client scan information table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
interface Specifies an interface: 1 or 2.
number Specifies the timeout in seconds for the client scan information table. Valid
numbers are between 0 and n (any number).
Default
600 seconds.
Usage Guidelines
Use this command to specify the age-out time for the clients in the client-scan results table.
Example
The following command sets the timeout period to 150 seconds for entries in the client scan information
table:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Sets the maximum number of clients that can connect simultaneously to a wireless interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
value Specifies the maximum number of clients that are allowed to connect
simultaneously. Valid values are from 0 to 128. The default value is 100.
Default
100.
Usage Guidelines
Use this command to limit the number of clients that can connect on any interface: 1 or 2.
Example
The following example sets the maximum client level to 72 for port 15 and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the power-level for the specified interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
interface Specifies an interface: 1 or 2.
level Specifies the power level for the interface. Valid values are:
• Full
• Half
• Quarter
• One-eighth
• Min (minimum)
Default
Full
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and interface
2 supports 802.11b/g radio signals. The configure wireless port interface power-level
command allows you to configure one of the two individual interfaces (1|2) on a port or ports. If there
is radio interference from other devices, then you can adjust the power level to an appropriate level
below full power.
Example
The following command configures the power level to half-power for interface 1 on ports 5 to 16 on a
Summit 300-24:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Attaches a port or ports and interface to an RF profile.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
name Specifies the name of the profile.
Default
A for interface 1.
B_G for interface 2.
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and interface
2 supports 802.11b/g radio signals. The configure wireless port interface command allows you
to configure one of the two individual interfaces (1|2) on a port or ports.
All ports in the port list must have the same wireless port version.
Example
The following command attaches the RF profile radio1 to interface 1 on port 1:7 on a Summit 300-48:
configure wireless port 1:7 interface 1 security-profile radio1
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Attaches a port or ports and interface to a security profile.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
name Specifies the name of the profile.
Default
Unsecure.
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and interface
2 supports 802.11b/g radio signals. The configure wireless port interface command allows you
to configure one of the two individual interfaces (1|2) on a port or ports..
All ports in the port list must have the same wireless port version.
Example
The following command attaches the security profile secure-wep to interface 1 on port 1:7 on a Summit
300-48:
configure wireless port 1:7 interface 1 security-profile secure-wep
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures a transmission rate for the specified port.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
interface Specifies an interface: 1 or 2.
rate Specifies the transmission rate for the port. Entering auto specifies automatic
transmission rate selection. Valid values are shown in Table 23.
Default
54 Mbps
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and interface
2 supports 802.11b/g radio signals. The configure wireless port interface transmit-level
command allows you to configure the transmission rate for one of the two individual interfaces (1|2) on
a port or ports.
Valid transmission rate values are shown in Table 23.
Example
The following command configures the port 14 on a Summit 300-24 to transmit at 54 Mbps for both
interface 1 and 2 (A and G):
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables or disables the interface as a bridge for wireless clients.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
on Specifies that the indicated interface is enabled. When enabled, wireless
clients on the same interface are able to communicate.
off Specifies that the indicated interface is disabled. When disabled, wireless
clients on the same interface cannot communicate.
Default
On (enabled)
Usage Guidelines
Wireless bridging on an Summit 300 switches allow wireless users within the same VLAN to
communicate with other wireless users on the same switch using layer 2 bridging. Wireless bridging can
be enabled or disabled for each interface of the wireless port, and the setting is locally significant on
each Altitude 300 wireless port. This setting does not prevent bridging between wired and wireless
MAC addresses in the same VLAN or between remote wireless stations associated with a remote
Altitude 300 wireless port.
Example
The following command disables bridging interface 2 on port 1:15 on a Summit 300-48:
configure wireless port 1:15 interface 2 wireless-bridging off
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the source IP address for the specified port or ports.
Syntax Description
portlist Specifies the port for which the IP address is being set
address Indicates the source IP address. The IP address must be an IP address on
the management VLAN.
Default
The default address is 0.0.0.0.
Usage Guidelines
The source IP address can be public or private IP addresses in class A through class C.
Example
The following command configures the default IP address for port 1:18 on the Summit 300-48:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the physical location of the access point (AP) for the specified port or ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
location name Identifies the location to be configured.
Default
Unknown Location
Usage Guidelines
Use this command to indicate the physical location of the access point (AP) for the specified port or
ports. For example, you could designate a physical location as follows: bldg 1, pole 14, cube 7.
Funk Radius can use this attribute for authentication.
Example
The following command configures the location, cube_a7, on port 18 on the Summit 300-24:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Creates a new RF profile by copying an existing RF profile and assigning a new name.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to create a new profile identified by the string name. The copy argument specifies
the name of an existing profile from which to obtain the initial values.
Example
The following command creates a new RF profile called rfprof_alpha from an existing profile called
wireless_prof:
The following command can be used to validate that you created the new RF profile as entered:
or
show rf-profile
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Creates a new RF profile by defining the interface mode,.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to create a new profile without copying from an existing profile.
Example
The following command creates a new RF profile called rfprof_alpha using interface mode G:
The following command can be used to validate that you created the new RF profile as entered:
or
show rf-profile
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
delete rf-profile
delete rf-profile <name>
Description
Deletes the named RF profile.
Syntax Description
Default
N/A
Usage Guidelines
Use this command to delete the named RF profile. The named profile cannot be attached to any active
ports before deletion.
Example
The following example deletes the RF profile named rfprof_alpha:
The following command can be used to validate that you deleted the RF profile as entered:
or
show rf-profile
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Administratively disables a wireless port for use.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
Default
N/A
Usage Guidelines
Use this command to disable one or more wireless ports.
Example
The following command disables port 1:17:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Cancels previously scheduled enable or disable scheduling commands for the port.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
Default
N/A
Usage Guidelines
Use this command with the force disassociation scheduler to cancel a force disassociation schedule.
Example
The following command cancels all scheduled enable or disable commands:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables the specified port or ports every day at the specified hour.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
hour Specifies the hour in military format (0-23).
Default
N/A.
Usage Guidelines
Use this command to configure the disabling of wireless ports according to a daily schedule. The
selected port or ports will be disabled each day on the specified hour.
Example
The following command disables port 1:17 every day at 7 a.m.:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables the specified port interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
Default
N/A
Usage Guidelines
Use this command to disable one of the interfaces. If both interfaces are disabled, it’s the same as using
the command: disable wireless ports x:x.
Example
The following command disables port 1:35 and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Stops an on-channel wireless port scan for the indicated port or ports and interface for the Altitude 300.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
When the scan feature is disabled, entries slowly age out of the scan results table until it is empty. If the
scan is restarted, the table values from the previous scan will be kept.
Example
The following command disables interface 2 on ports 1:18 to 1:28 on a Summit 300-48:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Stops the access point (AP) scan on the indicated interface at the specified time.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
at Specifies a once-only start time for a scan.
every Specifies to start the scan every day at the specified time.
time Specifies the hour in the format (0-23)
Default
N/A
Usage Guidelines
Use this command to stop the off-channel AP scan.
Example
The following command disables port 23 using interface 1 on the Summit 300-24:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables logging of client historical information.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
Default
Disable.
Usage Guidelines
Use this command to disable logging of client-history information on the specified wireless interface.
Example
The following example sets port 1:23 and interface 1 to disable logging of historical information:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables the client scan feature on the specified wireless interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
Default
N/A
Usage Guidelines
Use this command to disable the client scan feature on the specified wireless interface. Disabling the
feature can improve performance if the network is heavily populated and beginning to show
degradation.
Example
The following command disables port 1:31 and interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables Inter-Access Point Protocol (IAPP) on a per interface basis.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
Enabled.
Usage Guidelines
Use this command to disable IAPP for the selected ports and interface. IAPP uses layer 2 updates to
allow connected layer 2 devices to update forwarding tables with the address of the client. The access
point (AP) sends the updates on behalf of the clients by inserting the MAC address of the mobile station
in the source address. The switch looks up the UDP request packet on the local subnet that contains the
AP’s MAC address which contains the needed IP address. All APs on the subnet receive this message.
The AP with the matching MAC address sends a unicast response packet with its IP address.
Example
The following example disables port 1:15 and interface 1 for IAPP:
disable wireless ports 1:15 interface 1 iapp
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables the QoS protocol, SpectraLink Voice Protocol (SVP), for VoIP on the specified port and
interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
Disabled
Usage Guidelines
Use this command to disable the QoS protocol for VoIP. By enabling QoS for VoIP, you give voice traffic
a higher priority than data traffic. VoIP traffic has less tolerance for error recovery than data. Although
voice traffic can tolerate some degree of error recovery, it can be noticeable to users. This command
allows you to enable QoS for VoIP on the port and interface level.
Example
The following example, disables SVP on port 17 and interface 1:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables the specified ports at the given date and hour.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
date Specifies the date in the format (m/d/yyyy).
hour Specifies the hour in the format (0-23)
Default
N/A
Usage Guidelines
Use this command to disable one or more wireless ports at a specified time.
Example
The following command disables port 1:18 on June 29, 2005 at 3 p.m.:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Administratively enables a wireless port for use.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-.
Default
N/A
Usage Guidelines
Use this command to enable wireless ports.
Example
The following command enables port 1:17:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
This command cancels the scheduler on all ports or on a particular port.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
Default
N/A
Usage Guidelines
Use this command to cancel the scheduler.
Example
The following command cancels all scheduled enable or disable commands:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables the specified port or ports every day at the specified hour.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
hour Specifies the hour in military format (0-23).
Default
N/A
Usage Guidelines
Use this command to automatically enable wireless ports according to a daily schedule. The selected
port or ports will be enabled each day on the specified hour.
Example
The following command enables port 1:17 every day at 7 a.m.:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables the specified port interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Use this command for per interface enabling.
Example
The following command enables port 1:35 and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Starts a wireless port on-channel scan for the indicated port or ports and interface for the Altitude 300.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
Default
N/A.
Usage Guidelines
Use this command to start the wireless port on-channel scan on the indicated port and interface for the
Altitude 300. The Altitude 300 continues to carry user traffic during scans operating on the current
channel (“on-channel” scans).
Example
The following command enables interface 2 on ports 1:18 to 1:28 on a Summit 300-48:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Starts the access point (AP) scan on the indicated interface at the specified time.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
interface Specifies an interface: 1 or 2.
at Specifies a once-only start time for a scan.
every Specifies to start the scan every day at the specified time.
time Specifies the hour in the format (0-23)
Default
N/A.
Usage Guidelines
Use this command to schedule the off-channel AP scan. During an “off-channel” scan, the Altitude 300
is not available for user traffic.
Example
The following command enables port 23 using interface 1 on the Summit 300-24:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets the Altitude 300 to log client historical information.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
Disable.
Usage Guidelines
Use this command to get the detail status about each associated client.
Example
The following example sets port 1:23 and interface 1 to keep historical information:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables the client scan feature on the specified wireless interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Use this command to enable the client scan feature on the specified wireless interface.
Example
The following command enables port 1:31 and interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables Inter-Access Point Protocol (IAPP) on a per interface basis.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
Enabled.
Usage Guidelines
Use this command to enable IAPP for the selected ports and interface. IAPP uses layer 2 updates to
allow connected layer 2 devices to update forwarding tables with the address of the client. The access
point (AP) sends the updates on behalf of the clients by inserting the MAC address of the mobile station
in the source address. The switch looks up the UDP request packet on the local subnet that contains the
AP’s MAC address which contains the needed IP address. All APs on the subnet receive this message.
The AP with the matching MAC address sends a unicast response packet with its IP address.
Example
The following example enables port 1:15 and interface 1 for IAPP:
enable wireless ports 1:15 interface 1 iapp
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables the QoS protocol, SpectraLink Voice Protocol (SVP), for VoIP on the specified port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all ports.
interface Specifies an interface: 1 or 2.
Default
Disabled.
Usage Guidelines
Use this command to implement the QoS protocol for VoIP. By enabling QoS for VoIP, you give voice
traffic a higher priority than data traffic. VoIP traffic has less tolerance for error recovery than data.
Although voice traffic can tolerate some degree of error recovery, it can be noticeable to users. This
command allows you to enable QoS for VoIP on the port and interface level.
Example
The following example, turns on SVP on port 17 and interface 1:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables the specified ports at the given date and hour.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
date Specifies the date in the format (m/d/yyyy).
hour Specifies the hour in the format (0-23)
Default
N/A
Usage Guidelines
Use this command to enable selected wireless ports at a particular time.
Example
The following command enables port 1:18 on June 29, 2005 at 3 p.m.:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Resets the wireless ports to their default values
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-51:*, 1:5, 1:6-1:8.
Default
N/A
Usage Guidelines
Use this command to return a port the default values. Default values are:
• Health check—on
• IP address—192.168.0.100 + port number (1-24 for the Summit 300-24 and 1-48 for the Summit
300-48)
• Location—Unknown Location
Example
The following example resets all the wireless ports to the default values:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Forces the wireless port interface to reset.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Use this command to return a port interface the default values. Default values are:
• Channel—auto
• Power level—full
• Transmit rate—54 Mbps
Example
The following example resets all of interface 1 ports to the default values:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
show rf-profile
show rf-profile {<profile_name>}
Description
Displays configuration attributes for a particular RF profile or all RF profiles.
Syntax Description
profile_name Specifies the name of the RF profile whose configuration is to be displayed. If
you do not enter an RF profile name, configuration attributes will be displayed
for all RF profiles.
Default
All.
Usage Guidelines
Use this command to display configuration attributes for a particular RF profile or all RF profiles. If you
do not enter an RF profile name, configuration attributes will be displayed for all RF profiles.
Example
The following command displays configuration information about the RF profile named rfprof_alpha:
show rf-profile rfprof_alpha
Short Retry: 4
Long Retry: 7
Interfaces: 64
1:1:1, 1:2:1, 1:3:1, 1:4:1, 1:5:1,
1:6:1, 1:7:1, 1:8:1, 1:9:1, 1:10:1,
1:11:1, 1:12:1, 1:13:1, 1:14:1, 1:15:1,
1:16:1, 1:17:1, 1:18:1, 1:19:1, 1:20:1,
1:21:1, 1:22:1, 1:23:1, 1:24:1, 1:25:1,
1:26:1, 1:27:1, 1:28:1, 1:29:1, 1:30:1,
1:31:1, 1:32:1, 2:1:1, 2:2:1, 2:3:1,
2:4:1, 2:5:1, 2:6:1, 2:7:1, 2:8:1,
2:9:1, 2:10:1, 2:11:1, 2:12:1, 2:13:1,
2:14:1, 2:15:1, 2:16:1, 2:17:1, 2:18:1,
2:19:1, 2:20:1, 2:21:1, 2:22:1, 2:23:1,
2:24:1, 2:25:1, 2:26:1, 2:27:1, 2:28:1,
2:29:1, 2:30:1, 2:31:1, 2:32:1
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays a switch-wide, correlated view of the results of the access point (AP) scan.
Syntax Description
detail This optional keyword, provides more in-depth information.
Default
N/A
Usage Guidelines
Use this command to see the results of an AP scan. Use the optional keyword, detail, to see all of the
fields in Table 24.
Example
The following command displays information about the AP scan.
AP Mac Address Intf ESS Name AvgRSS Type Chan WEP WPA Last
AP Mac Address Intf ESS Name AvgRSS Type Chan WEP WPA Last
===================================================================================
00:04:96:05:80:B0 5:2 Extreme_g 2 bss 12 Y Y 01:36:17
00:04:96:05:80:F0 5:2 fz-dot1x-128 0 bss 1 Y Y 01:36:15
00:04:96:05:81:50 5:2 Extreme_g 8 bss 2 Y 01:36:18
00:04:96:05:82:00 5:2 DEFAULT_ESS 0 bss 11 N 01:36:18
00:04:96:05:82:80 5:2 Extreme_g 0 bss 1 Y Y 01:36:15
00:04:96:0C:00:00 5:2 wpadyn-g-tkip-ess 0 bss 11 Y Y 01:36:18
00:04:96:0C:04:30 5:2 fz-shared-wep-64 0 bss 7 Y 01:36:11
00:04:96:0C:05:50 5:2 Extreme_gax 0 bss 1 Y Y 01:36:18
00:04:96:0C:1E:F0 5:2 DEFAULT_ESS 3 bss 3 N 01:36:18
00:04:96:0C:23:60 5:2 DEFAULT_ESS 3 bss 11 N 01:36:18
00:04:96:0C:23:B0 5:2 TFZ 0 bss 7 Y 01:36:18
00:04:96:0C:30:A0 5:2 DEFAULT_ESS 0 bss 4 N 01:36:18
00:04:96:0C:31:30 5:2 DEFAULT_ESS 0 bss 10 N 01:36:16
00:04:96:0C:36:30 5:2 DEFAULT_ESS 1 bss 10 N 01:35:58
00:04:96:0C:3C:70 5:2 fz-open-wep-64 4 bss 7 Y 01:36:18
00:04:96:0C:5F:F0 5:2 DEFAULT_ESS 2 bss 11 N 01:36:18
00:04:96:0C:CA:C0 5:2 Extreme_gx 5 bss 11 Y Y 01:36:18
00:04:96:0C:D8:40 5:2 fz-wpa-dyn-aes 3 bss 11 Y Y 01:36:18
00:04:96:0C:DB:A0 5:2 Atheros 3 bss 12 Y Y 01:36:17
00:04:96:0D:9C:70 5:2 DEFAULT_ESS 0 bss 14 N 01:35:50
===================================================================================
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
Description
Displays information about the access point (AP) MAC-address that is entered.
Syntax Description
mac-address Specifies the MAC address of the client network interface card.
Default
N/A
Usage Guidelines
Use this command to review details about the specified AP..
Example
The following command displays information about the AP 00:04:96:0C:23:70:
AP Mac Address Intf ESS Name AvgRSS Type Chan WEP WPA Last
================================================================================
00:04:96:0C:23:70 1:23:2 DEFAULT_ESS 27 bss 6 N02:18:51
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays information about client scan results.
Syntax Description
detail This optional keyword, provides more in-depth information.
Default
N/A
Usage Guidelines
Use this command to get information about client scan results. Use the detail option to get further
details of the client scan.
Examples
The following example displays information about the wireless configuration:
Source : 00:04:23:90:03:91
Source : 00:05:4E:48:45:F8
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays information about a client by MAC address from the client scan results table.
Syntax Description
mac-address Specifies the MAC address of the client network interface card.
detail This optional keyword, provides more in-depth information.
Default
N/A
Usage Guidelines
Use this command to get information about a client from the client scan results table by using the MAC
address. Use the detail option to get further details.
Examples
The following example displays information about a client from the client scan results table:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the country, management VLAN, and gateway.
Syntax Description
This command has no arguments or variables.
Default
N/A
Usage Guidelines
Use this command to check the basic wireless configuration on a switch.
Examples
The following example displays information about the wireless configuration:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
This command shows a summary or detailed report of all wireless ports.
Syntax Description
all Specifies all active ports.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 1:5, 1:6-1:8.
detail This optional keyword, provides more in-depth information.
Default
N/A
Usage Guidelines
Use this command to show a summary of all ports or for a particular port.
Examples
The following example displays summary information about the wireless ports:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays a summary of the wireless configuration.
Syntax Description
all Specifies all active ports.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
N/A
Usage Guidelines
Use this command to review the configuration of one or more wireless ports.
Example
The following example displays a summary report of all the configured wireless ports:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays whether debug-trace is enabled on one or more ports.
Syntax Description
all Specifies all active ports.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
N/A
Usage Guidelines
Use this command to review the debug-trace status on a port.
Example
The following example displays a summary report of the status of debug-trace on all wireless ports:
--------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------
1(i) show wireless ports [all | <portlist>] interface [1 | 2] ap-scan results <mac
address> --This command is used to get information about a AP whose mac address is
selected from the AP scan result table.
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current configuration of the scan feature for the selected ports and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A.
Usage Guidelines
Use this command to see the current configuration of the AP scan feature for the specified wireless port
and interface. Use the optional keyword, detail, to see the detailed or expanded configuration.
Examples
The following example displays the configuration of port 1:5 and interface 1:
Intf En Add Rem Update Probe ProbeInt OCS Cont. Size Timeout Channels
-------------------------------------------------------------------------------
1:5:1 N off off off off 100 N N 128 300
The following example shows the extra details shown when the keyword detail is added to the
command:
Interface : 1:5:1
Enabled : N
Send Added Trap : off
Send Removed Trap : off
Send Updated Trap : off
Probe Interval : 100 (msec)
Send Probe : N
Result Table Size : 128
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays information about the results of an access point (AP) scan from the port perspective.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail (Optional) Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Use this command to see the results of an AP scan. Use the optional keyword, detail, to see all of the
fields in Table 24.
Example
The following example shows summary AP scan results for port 1:2 and interlace 1:
show wireless ports 1:2 interface 1 ap-scan results
Intf AP Mac Address ESS Name AvgRSS Type Chan WEP WPA Last
=================================================================================
1:2:1 00:04:96:05:80:B0 Extreme_a 18 bss 36 Y Y 19:05:33
1:2:1 00:04:96:0C:CA:C0 Extreme_a 7 bss 40 Y Y 19:05:33
1:2:1 00:04:96:05:82:80 Extreme_a 5 bss 40 Y Y 19:05:33
1:2:1 00:04:96:05:80:F0 fz-dot1x-128 30 bss 56 Y Y 19:05:34
1:2:1 00:04:96:05:81:50 Extreme_a 9 bss 64 Y Y 19:05:34
1:2:1 00:04:96:0C:00:00 wpadyn-a-aes-e 6 bss 48 Y Y 19:05:34
1:2:1 00:04:96:0C:23:60 DEFAULT_ESS 10 bss 52 N 19:05:34
1:2:1 00:04:96:0C:04:30 fz-open-wep-64 27 bss 64 Y 19:05:34
1:2:1 00:04:96:0C:02:40 fz-dot1x-128 25 bss 157 Y Y 19:05:34
1:2:1 00:04:96:0C:23:B0 fz-web-unsecure 24 bss 64 N 19:05:34
1:2:1 00:04:96:0C:3C:70 fz-web-unsecure 2 bss 64 N 19:05:34
1:2:1 00:04:96:0C:5F:F0 md-5 9 bss 161 Y Y 19:05:34
1:2:1 00:D0:4D:96:D0:CD Atheros 12 bss 48 Y Y 19:05:33
1:2:1 00:04:96:0C:D8:40 fz-wpa-dyn-tkip 54 bss 52 Y Y 19:05:34
1:2:1 00:04:96:0D:B4:20 QADS300-2410 bss 149 N 1
1:2:1 00:04:96:0D:9E:C0 wpapsk 13 bss 161 Y Y 19:05:34
1:2:1 00:04:96:0D:77:90 Extreme_a 3 bss 161 Y Y 19:05:34
1:2:1 00:30:F1:92:44:39 fz-wpa-psk-tkip 39 bss 153 Y Y 19:05:34
=================================================================================
The following example shows detail AP scan results for port 2:2 and interlace 1:
show wireless ports 2:2 interface 1 ap-scan results detail
Intf : 2:2:1
AP Mac Address : 00:04:96:05:80:B0
ESS Name : Extreme_a
Network Type : bss
Channel : 36
First Seen : 21:23:04
Last Change : 21:23:04
Rate Set : 6,9*,12,18*,24,36*,48*,54*
Ext. Rate Set :
Number of Beacons : 2
Number of Probes : 0
RSS: Min : 35
Max : 37
Avg : 23
WPA Information
Version : 1
Unicast Ciphers : TKIP
Multicast Ciphers : WEP104
WPA Auth Suite : DOT1X
Capability Information
N - G Short Slot
N - Channel Agility
N - PBCC
N - CF Poll REQ
N - CF Pollable
Y - WEP Required
bss - Network Type
L - Preamble
Intf : 2:2:1
AP Mac Address : 00:04:96:0C:CA:C0
ESS Name : Extreme_a
Network Type : bss
Channel : 40
First Seen : 21:23:04
Last Change : 21:23:04
Rate Set : 6,9*,12,18*,24,36*,48*,54*
Ext. Rate Set :
Number of Beacons : 1
Number of Probes : 0
RSS: Min : 14
Max : 14
Avg : 7
WPA Information
Version : 1
Unicast Ciphers : TKIP
Multicast Ciphers : WEP104
WPA Auth Suite : DOT1X
Capability Information
Y - G Short Slot
N - Channel Agility
N - PBCC
N - CF Poll REQ
N - CF Pollable
Y - WEP Required
bss - Network Type
L - Preamble
..
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays information about an access point (AP) whose MAC address is selected from the AP scan
results table.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
mac-address Specifies the MAC address selected from the AP scan results table.
Default
N/A
Usage Guidelines
Use this command to get information about an AP using its MAC address.
Example
The following example display information about an AP by MAC address:
AP Mac Address Intf ESS Name AvgRSS Type Chan WEP WPA Last
================================================================================
00:04:96:05:80:B0 1:8:2 Extreme_g 8 bss 11 Y 23:53:34
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the status of the AP scan for the port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Use this command to check the AP scan status on a particular port and interface.
Examples
The following command shows the status of the AP scan for the port and interface:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays information about a client whose MAC address is selected from the client list.
Syntax Description
Default
N/A
Usage Guidelines
Use this command to review MAC statistic information for a client by MAC address.
Example
The following example displays MAC statistic information for port 1:8 on interface 1:
show wireless ports 1:8 interface 1 client 00:0D:54:98:AC:35 mac-statistics
Intf : 1:8:1
AP Mac Address : 00:0D:54:98:AC:35
RSS: Min : 0
Max : 0
Avg : 0
Total PROBE REQ : 0
Total AUTH REQ : 1
Total ASSOC REQ : 2
Total REASSOC REQ : 0
Total DEASSOC REQ : 0
Total DEAUTH REQ : 0
Total PS POLL : 0
Total Data Frames : 0
NAV Value : 0
--------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current configuration of the client history and diagnostic features.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Use this command to see the current configuration of the client-history feature for the specified wireless
port and interface.
Example
The following example displays the client history and diagnostic features on port 1:25 and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays counters and errors the information collected on a per-client basis.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
mac_address Specifies the MAC address of the wireless client.
Default
N/A
Usage Guidelines
Use this command to display diagnostic counters and error information contained in the
extremeWirelessClientDiagTable.
Example
The following example displays client-history diagnostics information for port 1:25 and interface 1
based on the MAC address of the client:
Interface : 1:25:1
AP Mac Address : 00:0D:54:98:AC:35
State Watermark : FORWARDING
Events In Detected
Enters : 1
Errors : 0
AUTH REQ : 0
Other : 1
MGMT Action : 0
Time Outs : 0
Events In Authenticated
Enters : 1
Errors : 0
ASSOC REQ : 1
Other : 1
MGMT Action : 0
Time Outs : 0
Events In Associated
Enters : 1
Errors : 0
MGMT Action : 0
Time Outs : 0
Events In Forwarding
Enters : 1
MGMT Action : 0
Time Outs : 1
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays 802.11 MAC layer information collected on a per-client basis.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
mac_address Specifies the MAC address of the wireless client.
Default
N/A
Usage Guidelines
Use this command to display information on the operation of the 802.11 MAC layer.
Example
The following example displays client-history information for port 1:25 and interface 1 based on the
MAC address of the client:
Intf : 1:25:1
AP Mac address : 00:0D:54:98:AC:35
Authentication Information
Authenticated : Y
Total AUTH REQ : 1
Total AUTH RESP : 1
Total AUTH OK : 1
Total AUTH Failed : 0
Total AUTH (open) : 0
Total AUTH (shared) : 1
Last AUTH REQ : 19:40:06
Last Auth Type : OPEN
Authentication Error Information
Last Error Time : 00:00:00
Last Error Type : NONE
Errors by Type
Sequence Number : 0
Challenge Text (key) : 0
Type Mismatch (open|shared) : 0
Key Index : 0
Other : 0
Association Information
Associated : Y
Total ASSOC REQ : 2
Total REASSOC REQ : 0
Total ASSOC RESP : 1
Total ASSOC OK : 1
Total ASSOC Fail : 0
Association Error Information
Last Error Time : 00:00:00
Last Error Type : NONE
Errors by Type
Rate Mismatch : 0
Capability : 0
Counter Measure : 0
Cipher Suite : 0
Max Associations : 0
RSN Required : 0
RSN Mismatch : 0
Other : 0
Rate Set : 6*,9*,12*,18*,24*,36*,48*,54*
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current status of the historical client information.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
This command displays information about the client diagnostic and history database. The output has
the following fields:
Field Description
Enable This value indicates if historical information is being collected on this interface or
not.
TableSize This is the number of entries allowed in each of the historical client tables.
Timeout This is the time, in seconds, that entries will persist in the historical client tables
after the referenced client is removed from the SIB.
CurrentSize The current number of entries in the historical client database
Watermark The maximum number of entries which have ever been in the historical client
database.
Overflows Number of entries which have been overwritten in order to make room for a new
entry.
AgeOuts Number of entries which have been aged out of the table
Example
The following example displays the client diagnostic information for port 1 and interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current configuration of the client scan feature.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
Displays the current configuration of the client scan feature, including:
Interface 1 or 2
Max Size: Parameter specified for the number of entries for the table
Examples
The following example displays the current configuration of the client scan feature on port 1:5 and
interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current contents of the probe information table.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
The output of this command displays the probe information table, which has the following fields:
Variable Description
Intf Wireless port and interface on which this client is seen
MAC address of the source MAC address of the source
Probe REQs Number of PROBE REQ packets seen from this source
Last RSS RSSI of last received PROBE REQ packet
Channel Channel on which last PROBE REQ was received
Last Seen Time last PROBE REQ was seen from this source
Client Client is associated to the Altitude 300 (Y | N)
Example
The following example displays the probe information table for port 1:25 and interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the details about the specified client MAC address.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Use this command to check details about the clients in the client scan table.
Example
The following example shows the details of client MAC address 00:03:7F:BE:FE:9D.
show wireless port 5 interface 1 client-scan results 00:03:7F:BE:FE:9D
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the overall operation of the client scan results.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A
Usage Guidelines
The output of this command displays the performance results for the following variables on a per
wireless interface basis:
Variable Description
CurrentTableSize The current size of the table (in entries)
TableWatermark The maximum size the table has been since the last reset of the
historical statistics
TotalOverflows The number of times an entry has been overwritten because the
table is full
TotalTimeouts The number of times an entry has been aged out from the table
LastElement The last time an element was added to the table
TotalProbes The total number of probes received on this interface
Examples
The following example displays the performance results for port 5 on interface 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current wireless client state of a selected port or ports and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
mac-address Specifies to use the MAC address to select the client from the client list.
detail (Optional) Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Client current state information is available for all clients that have sent an authentication message to
the Altitude 300. Information in this table is timed out if no packets are received from the client by the
configurable period of time set by the administrator.
The following fields of the client state table are displayed with this command:
Fields Description
Client MAC MAC address of the client adapter
Current State DETECTED, AUTHED, ASSOC, or FORWARD. Indicates which part
of the state machine the client is currently in.
Last state change The system time when the client last changed states
Encryption Type Type of MAC-level encryption the client is using. This is negotiated
during the association state machine, so is only valid if client state is
FORWARDING.
Authentication Type Last type of authentication the client tried. In the case of a client in
FORWARDING, indicates the type of authentication that granted
access to the network.
ESSID Extended service set identifier of the network
Wireless Port Wireless switch port serving the client
Client VLAN VLAN assigned to this client by a radius VSA or other mechanism.
This is only valid for clients in FORWARDING.
Client Priority Quality of service (QoS) level for the client
Tx Frames Number of frames transferred to the client
Rx Frames Number of frames returned by the client
Fields Description
Tx Bytes Number of bytes transferred to the client
Rx Bytes Number of bytes returned by the client
RSS Received signal strength
Example
The following command displays information about client MAC address 00:09:5B:A1:1F:8F on port 1:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays information about wireless configuration for the selected ports and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Use this command to show in table or list format the configuration and state of the interface of the
selected port or ports.
Examples
The following example displays information about the wireless port configuration for ports 1:26-1:30
and interface 1:
Port Intf State RF Prof. Sec. Prof. TxRate Power Chan. Max Cl. Bridging
-------------------------------------------------------------------------------
1:26 1 EN rf_26 Unsecure 54 FULL 0 100 EN
1:27 1 EN rf_27 Unsecure 54 FULL 0 100 EN
1:28 1 EN rf_28 Unsecure 54 FULL 0 100 EN
1:29 1 EN DEFAULT_A Unsecure 54 FULL 0 100 EN
1:30 1 EN DEFAULT_A Unsecure 54 FULL 0 100 EN
The following example shows the extra details shown when the keyword detail is added to the
command:
Summit300-48:21 #
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays Port Authentication Entity (PAE) diagnostics for the selected port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A.
Usage Guidelines
Use this command to display the PAE diagnostics of the clients associated with the access point (AP).
Examples
The following example lists the output of the PAE diagnostics for ports 1:11 on interface 2:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays Port Authentication Entity (PAE) statistics for the selected port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 1:*, 1:5, 1:6-1:8.
detail Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Use this command to display the PAE statistics of the clients associated with the access point (AP).
Examples
The following example lists the output of the PAE statistics for ports 1:11 on interface 2:
PAE Statistics
CLIENT MAC Port Intf STATE TX RX ERRORS CLIENT ID
================================================================================
00:0D:54:98:AC:35 1:25 1 AUTHED 16 17 0 sqalab\labu
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays data rates for the selected port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and interface
2 supports 802.11b/g radio signals. The show wireless port interface rf-status command
allows you to display information about one of the two individual interfaces (1|2) on a port or ports.
Examples
The following example displays rf-status of all active ports of the switch:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays Wired Equivalent Privacy (WEP) protocol, authentication, dot1x, and ESS name information
for the selected port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5, 2:*, 2:5, 2:6-2:8.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
detail Specifies to display the information in detailed format.
Default
N/A
Usage Guidelines
Each wireless port on the Summit 300 contains two interfaces. Interface 1 supports 802.11a, and
interface 2 supports 802.11b/g radio signals. The show wireless port interface security-status
command allows you to display security status information about one of the two individual interfaces
(1|2) on a port or ports.
Examples
The following example displays the security setting of all active wireless ports of the switch:
The following example shows the detailed security setting of all active wireless ports of the switch:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays 802.11 interface statistics for the selected port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A.
Usage Guidelines
Use this command to search for errors on a per interface basis.
Examples
The following example displays 802.11 interface statistics for ports 1:5-1:34 and interface 1:
================================================================================
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the current state of the selected port and interface.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
all Specifies all active ports.
interface Specifies an interface: 1 or 2.
Default
N/A.
Usage Guidelines
Use this command to examine RF profiles on a per wireless port basis. This command allows you to
view the log of a specific port or ports, filtering out the switch log.
Examples
The following example displays the status for wireless ports 3 on interface 1:
Intf St. Tx Rate Power Ch ESS Max Cl. Last State Change
-------------------------------------------------------------------------------
3:1 EN 54 FULL 52 fz-wpa-psk-aes 100 Mon Jul 26 17:15:11 2004
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays the event log of the selected port or ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 1:2, 3-5.
summary Specifies to display a summary of the log information.
Default
N/A
Usage Guidelines
Use this command to display the Altitude 300 local log for debugging errors.
Examples
The following command displays log information for all ports on the device:
History
This command was first available in ExtremeWare 6.2a and added to the “e” series in 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Power over Ethernet (PoE) is an effective method of supplying 48 VDC power to certain types of
powered devices (PDs) through Category 5 or Category 3 twisted pair Ethernet cables. PDs include the
Altitude 300 wireless port, IP telephones, laptop computers, web cameras, and other devices. With PoE,
a single Ethernet cable supplies power and the data connection, reducing costs associated with separate
power cabling and supply. PoE for ExtremeWare includes a method of detection to assure that power is
delivered only to devices that meet the IEEE 802.3af specification for PoE.
In addition, the Summit 300-24 also supports legacy devices that are not 802.3AF compliant.
For more conceptual information about configuring and managing PoE, see the ExtremeWare Software
User Guide.
Description
Clears the port connection history for the specified slot.
Syntax Description
slot_number Specifies the slot for which the port connection history is cleared.
Default
N/A.
Usage Guidelines
None.
Example
The following command clears the port connection history for slot 2:
clear inline-power connection-history slot 2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Clears the fault condition on the specified ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5.
Default
N/A.
Usage Guidelines
None.
Example
The following command clears the fault condition for port 3:
clear inline-power fault ports 3
History
This command was first available in ExtremeWare7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Clears the inline statistics for the selected port to zero.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
N/A.
Usage Guidelines
Use this command to clear all the information displayed by the show inline-power stats ports
<portlist> command.
Example
The following command clears the inline statistics for ports 1-8:
clear inline-power stats 1-8
The following command displays cleared inline power configuration information for ports 1-8:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Configures the amount of power available for inline-power on the slot.
Syntax Description
Default
15.4 W.
Usage Guidelines
Before issuing this command, disable the slot using the disable inline-power slot <slot_id>
command. The device is allowed to draw about 10% more power than the configured amount before
power is shut off to the device.
Example
The following example configures slot 1 at 10 watts.
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the Summit 300 only.
Description
Sets the power detection mechanism on the specified ports.
Syntax Description
auto Forces automatic power discovery operations and supplies power to detected
power devices (PDs) for the specified ports.
discovery-test-only Forces power discovery operations and does not supply power to detected
PDs for the specified ports.
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
Auto.
Usage Guidelines
This command controls the power detection mechanism on the specified ports. Test mode forces power
discovery operations; however, power is not supplied to detected PDs.
Example
The following command forces automatic power discovery operations and specifies that power is
supplied to detected PDs for ports 1:4 –1: 6:
configure inline-power detection auto ports 1:4-1:6
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the Summit 300-48 only.
Description
Controls the disconnect function of power management.
Syntax Description
lowest-priority Specifies that the port with the lowest priority is to be shut down when the
next port connects.
deny-port Specifies that the next port is denied power, regardless of priority.
Default
Deny-port
Usage Guidelines
The PoE controller disconnects one of the ports to prevent an overload on the power supply. The
disconnect function occurs when the power drain exceeds the available power budget because of a rise
in power consumption after power is allocated to the ports.
Example
The following example configures the disconnect precedence to disconnect the lowest priority port
when the next port attempts to connect:
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the Summit 300-48 only.
Description
Lets you create your own label for a specified power port.
Syntax Description
Default
No label.
Usage Guidelines
Use the show inline-power configuration port <portlist> command, as shown in the following
example, to display inline power configuration information, including the display string (if any) for
each port. The display string is shown under the “Label” column:
show inline-power configuration port 1:1-1:7
Port Config Detect Rsvd Pwr Oper Lmt Viol Prec Label
1:1 enabled auto 0.0 15.4 max-class-operator
1:2 enabled auto 10.0 15.4 advertised-limit test_port2
1:3 enabled auto 0.0 15.4 max-class-operator
1:4 enabled auto 0.0 15.4 max-class-operator
1:5 enabled auto 0.0 15.4 max-class-operator
1:6 enabled auto 0.0 15.4 max-class-operator test_port6
1:7 enabled auto 0.0 15.4 max-class-operator
Example
The following command assigns the name “alpha-test_1” to port 1 on slot 1:
configure inline-power label alpha-test_1 ports 1:1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets the maximum power available for powered devices (PDs) on a per port basis.
Syntax Description
Default
15400 mW.
Usage Guidelines
The Summit 300-24 has an operator limit range of 300 to 15400 milliwatts. The Summit 300-48 has an
operator limit range of 300 to 20000 milliwatts.
The standard 802.3af protocol permits a PD to be classified into one of 5 classes, each of which
determines the maximal power draw to the power sourcing equipment (PSE). Extreme PSEs, in the
default configuration, use the classification-to-power draw in performing power management and
budgeting.
Classification is optional, and many PD devices do not support it. Therefore, under normal conditions,
the Extreme PSE budgets for the maximum permitted power (15.4 watts), even though the maximum
device draw may be less. This may cause fewer devices to be powered, since the power budget is
prematurely exhausted. There is a wide variation in power consumption levels between 802.3af classes
(~8 watts). In such cases, the power level limit (operator-limit) can be set on a per port basis. If this is
done, the operator limit, rather than the discovered class limit will be used for power budgeting. It is
also necessary for the violation-precedence to be set to operator-limit.
Regardless of how the port power limit is derived (through automatic classification or operator limit),
the port power limit is used to determine whether the overall system limit has been exceeded. On the
Summit 300-48, after the overall system limit is reached, additional PoE ports are powered based on the
system violation-precedence setting and port power priority. The Summit 300-24 has sufficient power to
support 15.4 watts on all 24 ports.
The power port limit is also used during system operation to limit the power supplied to each PoE port.
If a powered device attempts to draw more power than has been budgeted, the chassis will remove
power from that port to prevent system overload or device damage.
Example
The following command sets the limit on ports 1:3 – 1:6 to 10000 mW on a Summit 300-48:
configure inline-power operator-limit 10000 ports 1:3-1:6
History
Platform Availability
This command is available on Summit 300 series only.
Description
This command selects the power supply operating mode.
Syntax Description
Default
Redundant mode
Usage Guidelines
The PoE subsystem on the Summit 300-48 supports dual power supplies for either redundant or
load-sharing modes. Redundant mode is the default and provides hitless PoE should one of the two
power supplies fail, be removed, or powered off. Load-sharing mode allows both power supplies to
provide power to the PoE system, providing greater PoE power capacity. For load-sharing operation,
the amount of power provided to the PoE system is the sum of the power supplied by the power
supplies. With load-sharing, all PoE devices may experience a power hit if a power supply fails.
Example
The following command configures a Summit 300-48 for redundant power supply mode:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Configures the port priority.
Syntax Description
low Specifies that the port is to have low priority, which is the default value. Ports
with this priority level are given power only after all critical and high priority ports
have power.
high Specifies that the port is to have high priority. Ports with this priority level are
given power only after all critical ports have power.
critical Specifies that the port is to have critical priority. Ports with this priority receive
power first.
portlist Specifies one or more slots and ports. May be in the form 1:1, 1:2, 1:3-1:5.
Default
Low priority
Usage Guidelines
Power is allocated to ports by their designated priority. Power allocation is first provided to the higher
priority ports.
Example
The following example sets port 5 as a critical power port:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Sets the reserved power on the specified ports to either the default value or the specified watts.
Syntax Description
milliwatts An integer specifying milliwatts at zero (0) or in the range of 3000 – 20000 mW.
portlist Specifies one or more slots and ports. May be in the form 1:1, 1:2, 1:3-1:5.
Default
0 mW.
Usage Guidelines
This command sets the reserved power on the specified ports to either the default value or the specified
watts. The reserved power range is 0 or 3000-20000 mW. The default reserved power range value is 0
mW. Total power reserved may be up to but not greater than the total power for the card. If all of the
power available to the card is reserved, then the common power pool is empty.
Example
The following command sets the reserved power for ports 4 to 15000 mW:
configure inline-power reserved budget 15000 ports 4
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 model only.
Description
Sets the type of powered device (PD) connected to the specified ports.
Syntax Description
Default
Other
Usage Guidelines
This command sets the type of PD connected to the specified ports. This is a management-controlled
entity because there is no support for dynamically determining the PD device type.
Use the detail port argument in the show inline-power info [detail] port <portlist] command to
display the inline-power type for a selected port.
Example
The following command specifies the type of PD connected to port 3 as a wireless device on a
Summit 300-48 switch:
configure inline-power type wireless ports 1:3
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 switches only.
Description
Sets the inline power usage alarm threshold.
Syntax Description
Default
Summit 300-24: 90
Summit 300-48: 70
Usage Guidelines
This command sets the threshold for initiation of an alarm if the measured power exceeds the threshold.
On the Summit 300-48, the alarm threshold is shared between the system-level utilization and the
allocated power budget per slot. If either measurement exceeds the threshold level, an alarm is initiated.
On the Summit 300-24, the usage threshold is not shared with the system usage, it is power used by the
PDs only.
Example
The following command sets the inline power usage alarm threshold at 75%:
config inline-power usage-threshold 75
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Sets a user-defined limit on a port or ports..
Syntax Description
Default
max-class-operator
Usage Guidelines
This command sets a user-defined limit for the specified ports. Power is removed or denied to PDs
connected to the selected ports if the PD consumes more power than the entered limit. The default
value is max-class-operator, which removes or denies power if the PD consumes power beyond the
greater value of the detected class limit or the configured operator limit, whichever is greater. The
operator limit is configured with the following command:
Example
The following command sets the violation precedence for port 3 to the configured operator limit:
configure inline-power violation-precedence operator-limit ports 3
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 switches.
disable inline-power
disable inline-power
Description
Shuts down power to all ports.
Syntax Description
This command has no arguments or variables.
Default
Enable.
Usage Guidelines
You can control whether inline power is provided to the system by using the disable inline-power
command and the enable inline-power command. Using the disable inline-power command
shuts down power currently provided on all ports on all slots. By default, inline power provided to the
system is enabled.
Example
The following command shuts down power currently provided on all ports on all slots:
disable inline-power
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Disables legacy (802.3af compliant) devices from being detected by the PoE subsystem.
Syntax Description
This command has no arguments or variables.
Default
disabled
Usage Guidelines
The Summit 300-24 is capable of powering devices that are compliant to the IEEE 802.3af Power over
Ethernet standard. The enable inline-power legacy command allows PoE devices build before the
standard was approved to be powered.
If all the devices connected to the switch are 802.3af standards compliant, it is advised to keep the
default setting of disabled for legacy device support.
You can determine whether a device connected to the switch is standards compliant or not by using the
show inline-power info [detail] port <portlist] command. The detailed status line shows if
the device is 802.3af standards compliant.
Sample output from the show inline-power info detail ports command follows:
PORT - 5
Example
The following command disables 802.3af compliant devices:
disable inline-power legacy
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-24 only.
Description
Disables power provided by all system ports or specified ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
Enable.
Usage Guidelines
You can control whether inline power is provided by all system ports or specified ports by using the
disable inline-power ports <portlist>] command and the enable inline-power ports
<portlist>] command. Using the disable inline-power ports <portlist>] command shuts
down power currently provided by all system ports or specified ports. The system defaults to enabling
power on all 10/100 ports.
Disabling a port providing power to a powered device (PD) immediately removes power to the PD.
Example
The following command shuts down power currently provided by port 2:
disable inline-power 2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series models only.
Description
Disables power provided to the specified slot.
Syntax Description
Default
Enable.
Usage Guidelines
You can control whether inline power is provided to a specific slot by using the disable inline-power
slot <slot_id> command and the enable inline-power slot <slot_id> command. Using the
disable inline-power slot <slot_id> command shuts down power currently provided to the
selected slot. The system defaults to enabling power on all slots.
Disabling a slot providing power to a powered device (PD) through one of its powered ports
immediately removes power to the PD.
Example
The following command shuts down power currently provided by slot 1:1.
disable inline-power slots 1:1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
enable inline-power
enable inline-power
Description
Enables inline power to all ports, except for the ports that are explicitly disabled by the
disable inline-power ports command.
Syntax Description
This command has no arguments or variables.
Default
Enable.
Usage Guidelines
You can control whether inline power is provided to the system by using the disable inline-power
command and the enable inline-power command. Using the enable inline-power command
makes power available on all ports on all slots. Using the disable inline-power command shuts
down power currently provided on all ports on all slots. By default, inline power provided to the
system is enabled. To shutdown power to a specific port, use the disable inline-power ports
command.
Example
The following command enables power currently provided on all ports:
enable inline-power
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Enables legacy (802.3af compliant) devices from being detected by the PoE subsystem.
Syntax Description
This command has no arguments or variables.
Default
disabled
Usage Guidelines
The Summit 300-24 is capable of powering devices that are compliant to the IEEE 802.3af Power over
Ethernet standard. The enable inline-power legacy command allows PoE devices build before the
standard was approved to be powered.
If all the devices connected to the switch are 802.3af standards compliant, it is advised to keep the
default setting of disabled for legacy device support.
You can determine whether a device connected to the switch is standards compliant or not by using the
show inline-power info [detail] port <portlist] command. The detailed status line shows if
the device is 802.3af standards compliant.
Sample output from the show inline-power info detail ports command follows:
PORT - 5
Example
The following command disables 802.3af compliant devices:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-24 only.
Description
Enables power provided by all system ports or specified ports.
Syntax Description
portlist Specifies one or more slots and ports. May be in the form 1, 2, 3-5, 1:1, 2,
1:3-1:5.
Default
Enable.
Usage Guidelines
You can control whether inline power is provided by all system ports or specified ports by using the
disable inline-power ports <portlist>] command and the enable inline-power ports
<portlist>] command. Using the enable inline-power ports <portlist>] command makes
power available to all system ports or specified ports. Using the disable inline-power ports
<portlist>] command shuts down power currently provided by all system ports or specified ports.
The system defaults to enabling power on all 10/100 ports.
Disabling a port providing power to a powered device (PD) immediately removes power to the PD.
Example
The following command enables power currently provided by port 2:
enable inline-power ports 2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the Summit 300 switches.
Description
Enables power provided to the specified slot.
Syntax Description
Default
Enable.
Usage Guidelines
You can control whether inline power is provided to a specific slot by using the disable inline-power
slot <slot_id> command and the enable inline-power slot <slot_id> command. Using the
enable inline-power slot <slot_id> command makes power available to the selected slot. Using
the disable inline-power slot <slot_id> command shuts down power currently provided to the
selected slot. The system defaults to enabling power on all slots.
Disabling a slot providing power to a powered device (PD) through one of its powered ports
immediately removes power to the PD.
Example
The following command makes power available to slot 1:
enable inline-power slots 1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Power cycles the specified ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
N/A.
Usage Guidelines
This command power cycles the specified ports. Ports are immediately de-powered and re-powered,
maintaining current power allocations.
Example
The following command resets power for port 4:
reset inline-power ports 4
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 seriesonly.
Description
Resets the specified slot.
Syntax Description
Default
N/A.
Usage Guidelines
This command resets the specified slots. Slots are immediately de-powered and re-powered,
maintaining current power allocations.
Example
The following command resets power for slot 1:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
show inline-power
show inline-power
Description
Displays inline power status information for the system.
Syntax Description
This command has no arguments or variables.
Default
N/A.
Usage Guidelines
The output indicates the following inline power status information for the system:
The output indicates the following inline power status information for each slot:
• Main PSU Status—The operational status of the main power supply unit. The status conditions are:
— ON: Power is being provided to the PoE controller.
— OFF: Power is not being provided to the PoE controller.
— FAULT: An error has occurred.
• Backup PSU Status—The condition of the backup power device, indicated by the following
information:
— State: Present, Not Present, Fault
— Status: ACTIVATED, DEACTIVATED
Valid State, Status combinations are:
• Present, ACTIVATED
• Present, DEACTIVATED
• Not Present
• Fault
• Firmware Status—The condition of the firmware, indicated by one the following states:
— Initializing—Firmware is still coming up.
— Operational—Firmware is up and running.
— Download failure—Firmware failed to download properly.
— Needs calibrating—Firmware downloaded properly or is up and running, but values stored in
EEPROM are invalid. The unit should be returned to Extreme Networks Service for recalibration.
Example
The following command displays inline power status for the system:
show inline-power
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Displays inline power configuration information for the specified ports.
Syntax Description
Default
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
N/A.
Usage Guidelines
The output displays the following inline power configuration information for the specified ports:
Example
The following command displays inline power configuration information for ports 1-7 in slot 1:
Port Config Detect Rsvd Pwr Oper Lmt Viol Prec Label
1:1 enabled auto 0.0 15.4 max-class-operator
1:2 enabled auto 10.0 15.4 advertised-limit test_port2
1:3 enabled auto 0.0 15.4 max-class-operator
1:4 enabled auto 0.0 15.4 max-class-operator
1:5 enabled auto 0.0 15.4 max-class-operator
1:6 enabled auto 0.0 15.4 max-class-operator test_port6
1:7 enabled auto 0.0 15.4 max-class-operator
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the Summit 300 switches.
Description
Displays inline power configuration information for the specified slots.
Syntax Description
Default
N/A.
Usage Guidelines
The output displays the following inline power configuration information for the specified slots:
Example
The following command displays inline power configuration information for slot 1:
show inline-power configuration slot 1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the Summit 300-48 only.
Description
Displays inline power information for the specified ports.
Syntax Description
Default
N/A.
Usage Guidelines
You can use this command to generate a summary report or a detailed report.
Summary output displays the following inline power information for the specified ports:
• Volts—Displays the measured voltage. A value from 0 – 2V is valid for ports that are in a searching
or discovered state.
• Curr—Displays the measure current in milli Amps (mA).
• Res—Displays the measured resistance in kilo Ohms (Kohms). A value greater than 100 Kohms
indicates an empty port.
• Power—Displays the measured power in watts.
• Fault—Displays the fault value:
— 0: No fault
— 1: Over voltage
— 2: Over voltage spike
— 3: Peak over current
— 4: Overload
— 8: Discovery resistance failed
— 9: Class violation
— 10: Disconnect
— 11: Discovery resistance, A2D fail
— 12: Classify, A2D fail
— 13: Sample A2D fail
— 14: Device fault, A2D fail
The detail command lists all inline power information for the selected ports. Detail output displays the
following information:
• Fault Status
Example
The following command displays summary inline power information for port 1:
show inline info port 1:1
Common Power
Configured Allocated Measured usage
376000mW 0 mW 0 mW
INLINE-POWER STATISTICS
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 switches.
Description
Displays inline power information for the specified slots.
Syntax Description
Default
N/A.
Usage Guidelines
The output displays the following inline power information for the specified slots:
• Common Power:
— Configured: Displays in watts the configured amount of common power available. This amount is
equal to the total amount of configured power minus the amount of configured reserved power.
— Allocated: Displays in watts the amount of common power allocated.
• Reserved Power:
— Configured: Displays in watts the amount of power configured as reserved.
— Allocated: Displays in watts the amount of reserved power utilized.
• Measured Usage—Displays measured power in watts.
Example
The following command displays inline power information for slot 1:
show inline-power slot 1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Displays inline power statistics for the specified ports.
Syntax Description
portlist Specifies one or more ports. May be in the form 1:1,1: 1:2, 1:3-1:5.
Default
N/A.
Usage Guidelines
The output displays the following inline power statistics for the specified ports:
Example
The following command displays inline power configuration information for ports 1-8 in slot 1:
show inline-power stats ports 1:1-1:8
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the Summit 300-48 only.
Description
Displays inline power statistics for the specified slots.
Syntax Description
Default
N/A.
Usage Guidelines
Use this command to produce a report that shows how many ports are faulted, powered, and waiting
for power for the selected slots.
Example
The following command displays inline power statistics information for slot 1:
show inline-power stats slot 1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 series only.
Description
Resets the power detection scheme to the default for the specified ports.
Syntax Description
portlist Specifies one or more slots and ports. May be in the form 1:*, 1:5, 1:6-1:8.
Default
N/A.
Usage Guidelines
This command resets the power detection scheme configured with the following command:
Example
The following command resets the power detection scheme to its default for port 1 on slot 1:
unconfigure inline-power detection ports 1:1
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Returns the disconnect-precedence to the default value.
Syntax Description
This command has no arguments or variables.
Default
Deny-port
Usage Guidelines
The PoE controller disconnects one of the ports to prevent an overload on the power supply. The
disconnect function occurs when the power drain exceeds the available power budget because of a rise
in power consumption after power is allocated to the ports.
Example
The following example configures the disconnect precedence to disconnect the next port regardless of
priority:
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the Summit 300-48 only.
Description
Resets the operator limit back to the default for the specified ports.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default operator limit is 15400 mW.
Usage Guidelines
This command resets the operator limit configured with the following command:
The Summit 300-24 has an operator limit range of 300 to 15400 milliwatts. The Summit 300-48 has an
operator limit range of 300 to 20000 milliwatts.
Example
The following command resets the operator limit to its default for port 2 on slot 1:
unconfigure inline-power operator-limit ports 1:2
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on the Summit 300 switches.
Description
Sets the power supply mode to the default setting of redundant mode.
Syntax Description
This command has no arguments or variables.
Usage Guidelines
The Summit 300-48 PoE subsystem supports dual power supplies for either redundant or load-sharing
modes. Redundant mode is the default and provides hitless PoE should one of the two power supplies
fail, be removed, or powered off. Load-sharing mode allows both power supplies to provide power to
the PoE system, providing greater PoE power capacity. For load-sharing operation, the amount of power
provided to the PoE system is the sum of the power supplied by the power supplies.
Example
The following command returns a Summit 300-48 to redundant power supply mode:
History
This command was first available in ExtremeWare 7.3e
Platform Availability
This command is available on the Summit 300-48 only.
Description
Resets one or more ports to the default value of low priority.
Syntax Description
portlist Specifies one or more slots and ports. May be in the form 1:1,!:2, !:3-!:5.
Default
Low priority
Usage Guidelines
Power is allocated to ports by their designated priority. Power allocation is first provided to the higher
priority ports.
Example
The following example resets port 1:5 to low priority:
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300-48 only.
Description
Resets the reserved budget back to the default value.
Syntax Description
portlist Specifies one or more ports or slots and ports. Can be one or more port
numbers. May be in the form 1, 2, 3-5, 1:*, 1:5, 1:6-1:8.
Default
The default reserved budget value is 0 mW.
Usage Guidelines
This command resets to default the reserved power budget configured with the following command:
Example
The following command resets the reserved power budget to its default for port 3 on slot 1:
unconfigure inline-power reserved-budget ports 1:3
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Resets the inline power usage threshold to the default value.
Syntax Description
This command has no arguments or variables.
Default
The default value for the inline power usage threshold is 70 percent.
Usage Guidelines
This command resets to default the inline power usage threshold configured with the following
command:
Example
The following command resets the inline power usage threshold to its default value:
unconfigure inline-power usage-threshold
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
Description
Resets violation precedence to the default value for the specified ports.
Syntax Description
portlist Specifies one or more slots and ports. May be in the form 2:*, 2:5, 2:6-2:8.
Default
The default violation precedence value is max-class-operator.
Usage Guidelines
This command resets the violation precedence configured with the following command:
Example
The following command resets the violation precedence to its default value for port 3 on slot 1:
unconfigure inline-power violation-precedence ports 1:3
History
This command was first available in ExtremeWare 7.3e.
Platform Availability
This command is available on Summit 300 series only.
C configure banner 45
clear counters 316 configure banner netlogin 46
clear debug-trace 590 configure bootprelay add 762
clear elrp stats 659 configure bootprelay delete 763
clear fdb 274 configure bootprelay dhcp-agent information option
clear igmp group 951 766
clear igmp snooping 952 configure cpu-dos-protect 407, 408
clear inline-power connection-history slot 1137 configure cpu-dos-protect trusted-ports 410, 411
clear inline-power fault ports 1138 configure debug-trace accounting 591
clear inline-power stats 1139 configure debug-trace bootprelay 592
clear iparp 760 configure debug-trace card-state-change 593
clear ipfdb 761 configure debug-trace debug-link 594
clear ipmc cache 953 configure debug-trace flow-redirect 595
clear ipmc fdb 954 configure debug-trace iparp 597
clear log 317 configure debug-trace rip-message 599
clear log counters 318 configure debug-trace rip-route-change 600
clear log diag-status 317 configure debug-trace rip-triggered-update 601
clear log error-led 317 configure debug-trace udp-forwarding 602
clear log messages 317 configure debug-trace wireless 603
clear log static 317 configure debug-trace wireless ports iapp 1009
clear nat 298 configure dns-client add 47
clear netlogin state 394 configure dns-client add domain-suffix 48
clear netlogin state mac-address 395 configure dns-client add name-server 49
clear session 42 configure dns-client default-domain 50
clear wireless ports counters 1003 configure dns-client delete 51
clear wireless ports interface ap-scan results 1004 configure dns-client delete domain-suffix 52
clear wireless ports interface client-history counters configure dns-client delete name-server 53
1005 configure download server 574
clear wireless ports interface client-scan counters 1006 configure eaps add control vlan 628
clear wireless ports interface client-scan results 1007 configure eaps add protect vlan 629
clear wireless ports log 1008 configure eaps delete control vlan 630
configure access-profile add 396 configure eaps delete protect vlan 631
configure access-profile delete 398 configure eaps failtime 632
configure access-profile mode 399 configure eaps failtime expiry-action 633
configure account 43 configure eaps hellotime 635
configure auth mgmt-access radius 400 configure eaps mode 636
configure auth mgmt-access tacacs 402 configure eaps name 637
configure auth netlogin radius 404 configure eaps port 638
configure auth netlogin tacacs 406 configure eaps shared-port domain 639
configure eaps shared-port mode 640 configure log filter events 320
configure enhanced-dos-protect ipfdb agingtime 412 configure log filter events match 323
configure enhanced-dos-protect ipfdb cache-size 413 configure log filter events strict-match 323
configure enhanced-dos-protect ipfdb learn-window configure log filter set severity 326
415 configure log filter set severity match 327
configure enhanced-dos-protect learn-limit 414 configure log target filter 329
configure enhanced-dos-protect learn-window 417 configure log target format 331
configure enhanced-dos-protect ports 416 configure log target match 335
configure esrp port-mode ports 660 configure log target severity 337
configure fdb agingtime 275 configure mac-vlan add mac-address 252
configure idletimeouts 54 configure mac-vlan delete 254
configure igmp 955 configure mirroring add 191
configure igmp snooping add static group 956 configure mirroring delete 193
configure igmp snooping add static router 959 configure nat add vlan map 299
configure igmp snooping delete static group 958 configure nat delete 302
configure igmp snooping delete static router 960 configure nat finrst-timeout 304
configure igmp snooping filter 961 configure nat icmp-timeout 305
configure igmp snooping flood-list 962 configure nat syn-timeout 306
configure igmp snooping leave-timeout 964 configure nat tcp-timeout 307
configure igmp snooping timer 965 configure nat timeout 308
configure inline-power detection 1141, 1177 configure nat udp-timeout 309
configure inline-power label 1143 configure nat vlan 310
configure inline-power operator-limit 1144, 1151, 1179 configure netlogin base-url 419
configure inline-power power-supply 1146 configure netlogin redirect-page 420
configure inline-power priority 1147 configure ospf add virtual-link 868
configure inline-power reserved budget 1148, 1182 configure ospf add vlan area 870
configure inline-power type 1149 configure ospf add vlan area link-type 872
configure inline-power usage-threshold 1150, 1183 configure ospf area add range 875
configure inline-power violation-precedence 1151, configure ospf area delete range 876
1184 configure ospf area external-filter 862, 873
configure iparp add 769 configure ospf area interarea-filter 861, 874
configure iparp add proxy 770 configure ospf area normal 877
configure iparp delete 772 configure ospf area nssa stub-default-cost 878
configure iparp delete proxy 773 configure ospf area stub stub-default-cost 879
configure iparp max-entries 774 configure ospf asbr-filter 880
configure iparp max-pending-entries 775 configure ospf ase-limint 881
configure iparp timeout 776 configure ospf ase-summary add cost 882
configure ip-down-vlan-action 777 configure ospf ase-summary delete 883
configure ipfdb route-add 778 configure ospf authentication 865
configure ip-mtu vlan 187 configure ospf cost 863
configure iproute add 779 configure ospf delete virtual-link 884
configure iproute add blackhole 780 configure ospf delete vlan 885
configure iproute add blackhole default 781 configure ospf direct-filter 886
configure iproute add default 782 configure ospf lsa-batching-timer 887
configure iproute delete 783 configure ospf metric-table 888
configure iproute delete blackhole 784 configure ospf priority 864
configure iproute delete blackhole default 785 configure ospf routerid 889
configure iproute delete default 786 configure ospf spf-hold-time 890
configure iproute priority 787 configure ospf timer 866
configure irdp 789 configure ospf vlan area 869
configure irpd 790 configure ospf vlan neighbor add 891
configure irpp 789 configure ospf vlan neighbor delete 892
configure jumbo-frame size 189 configure pim add vlan 967
configure log display 319 configure pim crp static 968
configure stpd maxage 713 configure vlan esrp group delete esrp-aware-ports 691
configure stpd mode 714 configure vlan esrp priority 692
configure stpd port link-type 716 configure vlan esrp timer 693
configure stpd ports cost 715 configure vlan ipaddress 259
configure stpd ports mode 718 configure vlan name 260
configure stpd ports priority 719 configure vlan netlogin-lease-timer 457
configure stpd priority 720 configure vlan priority 289
configure stpd tag 721 configure vlan tag 261
configure syslog add 340 configure vlan udp-profile 793
configure syslog delete 342 configure vrrp add vlan 745
configure sys-recovery-level 339 configure vrrp delete 746
configure tacacs server 446 configure vrrp vlan add 747
configure tacacs shared-secret 447 configure vrrp vlan authentication 748
configure tacacs timeout 448 configure vrrp vlan delete vrid 749
configure tacacs-accounting server 449 configure vrrp vlan vrid 750
configure tacacs-accounting shared-secret 450 configure web login-timeout 132
configure tacacs-accounting timeout 451 configure wireless country-code 1017
configure time 55 configure wireless default-gateway 1019
configure timezone 56 configure wireless management-vlan 1020
configure udp-profile add 791 configure wireless port interface ap-scan added-trap
configure udp-profile delete 792 1025
configure vlan add domain-member vlan 662 configure wireless ports client-scan removed-trap 1041
configure vlan add elrp-poll ports 663, 674 configure wireless ports detected-station-timeout 1022
configure vlan add ports 257 configure wireless ports force-disassociation 1023
configure vlan add ports no-restart 664 configure wireless ports health-check 1024
configure vlan add ports restart 665 configure wireless ports interface ap-scan off-channel
configure vlan add ports stpd 722 1026
configure vlan add track-diagnostic 666 configure wireless ports interface ap-scan off-channel
configure vlan add track-environment 667 continuous 1027
configure vlan add track-iproute 668 configure wireless ports interface ap-scan off-channel
configure vlan add track-ospf 669 max-wait 1028
configure vlan add track-ping 670 configure wireless ports interface ap-scan off-channel
configure vlan add track-rip 671 min-wait 1029
configure vlan add track-vlan 672 configure wireless ports interface ap-scan probe-inter-
configure vlan delete domain-member vlan 673 val 1030
configure vlan delete port 258 configure wireless ports interface ap-scan re-
configure vlan delete track-diagnostic 675 moved-trap 1031
configure vlan delete track-environment 676 configure wireless ports interface ap-scan results size
configure vlan delete track-iproute 677 1032
configure vlan delete track-ospf 678 configure wireless ports interface ap-scan results time-
configure vlan delete track-ping 679 out 1033
configure vlan delete track-rip 680 configure wireless ports interface ap-scan send-probe
configure vlan delete track-vlan 681 1034
configure vlan dhcp-address-range 452 configure wireless ports interface ap-scan updated-trap
configure vlan dhcp-lease-timer 453 1035
configure vlan dhcp-options 454 configure wireless ports interface channel 1036
configure vlan esrp elrp-master-poll disable 682 configure wireless ports interface client-history size
configure vlan esrp elrp-master-poll enable 683 1038
configure vlan esrp elrp-premaster-poll disable 684 configure wireless ports interface client-history timeout
configure vlan esrp elrp-premaster-poll enable 685 1038, 1039
configure vlan esrp esrp-election 686 configure wireless ports interface client-scan add-
configure vlan esrp esrp-premaster-timeout 688 ed-trap 1040
configure vlan esrp group 689 configure wireless ports interface client-scan results
configure vlan esrp group add esrp-aware-ports 690 timeout 1043
enable netlogin ports vlan 505 enable wireless ports interface client-history 1072
enable netlogin session-refresh 506 enable wireless ports interface client-scan 1073
enable ospf 918 enable wireless ports interface iapp 1074
enable ospf capability opaque-lsa 919 enable wireless ports interface svp 1075
enable ospf export 920 enable wireless ports time 1076
enable ospf export direct 921 exit 157
enable ospf export rip 923
enable ospf export static 924 H
enable ospf originate-default 925 history 69
enable pim 986
enable ports 222 L
enable radius 507 logout 158
enable radius-accounting 508
enable rip 926 M
enable rip aggregation 927 mrinfo 987
enable rip export cost 928 mtrace 988
enable rip exportstatic 929
enable rip originate-default cost 930 N
enable rip poisonreverse 931 nslookup 607
enable rip splithorizon 932
enable rip triggerupdate 933
P
enable rmon 357
ping 608
enable sharing grouping 223
enable smartredundancy 225
enable snmp access 146
Q
quit 159
enable snmp dot1dtpfdbtable 148
enable snmp traps 149
enable snmp traps port-up-down 150 R
enable sntp-client 152 reate access-profile 461
enable ssh2 509 reboot 70
enable stpd 732 reset inline-power ports 1162, 1163
enable stpd ports 733 reset wireless ports 1077
enable stpd rapid-root-failover 734 reset wireless ports interface 1078
enable syslog 359 restart ports 226
enable system-watchdog 153 rtlookup 840
enable tacacs 510 run diagnostics 610
enable tacacs accounting. 511 run diagnostics cable ports 611
enable tacacs-authorization 512
enable telnet 154 S
enable trusted-mac-address 513 save configuration 581
enable udp-echo-server 839 scp2 519
enable vrrp 753 scp2 configuration 521
enable web 156, 514 show access-list 522
enable web http 515 show access-mask 524
enable web http access-profile 516 show access-profile 525
enable web https 492, 517 show arp-learning vlan 526
enable web https access-profile 518 show arp-learning vlan port 527
enable wireless ports 1066 show banner 71
enable wireless ports cancel-scheduler 1067 show configuration 200, 582
enable wireless ports every 1068 show cpu-dos-protect 529
enable wireless ports interface 1069 show debug-trace 613
enable wireless ports interface ap-scan 1070 show dns-client 72
enable wireless ports interface ap-scan off-channel show eaps 647
1071 show eaps shared-port 651
T
telnet 183
top 621
traceroute 76
U
unconfigure cpu-dos-protect 554, 555, 556
unconfigure diffserv examination ports 296
unconfigure eaps port 656
unconfigure eaps shared-port 654
unconfigure eaps shared-port mode 655
unconfigure enhanced-dos-protect ipfdb agingtime
557