54-Port 10G Ethernet Switch with
48 10GBASE SFP+ Ports,
6 40GBASE QSFP Ports,
2 Power Supply Units,
and 4 Fan Trays (4 Fans – F2B and B2F Airflow)
AS6700-32X
32-Port 40G Data Center Switch
with 20 40G QSFP+ Ports,
2 40G Expansion Slots,
2 Power Supply Units,
and 5 Fan Trays (5 Fans – F2B or B2F Airflow)
E032016/ST-R02
149100000198A
How to Use This Guide
This guide includes detailed information on the switch software, including how to
operate and use the management functions of the switch. To deploy this switch
effectively and ensure trouble-free operation, you should first read the relevant
sections in this guide so that you are familiar with all of its software features.
Who Should Read This
Guide?
How This Guide is
Organized
Related
Documentation
This guide is for network administrators who are responsible for operating and
maintaining network equipment. The guide assumes a basic working knowledge of
LANs (Local Area Networks), the Internet Protocol (IP), and Simple Network
Management Protocol (SNMP).
This guide describes the switch’s command line interface (CLI). For more detailed
information on the switch’s key features refer to the Administrator’s Guide.
The guide includes these sections:
◆Section I “Getting Started” — Includes information on connecting to the switch
and basic configuration procedures.
◆Section II “Command Line Interface” — Includes all management options
available through the CLI.
◆Section III “App en di ce s” — Includes information on troubleshooting switch
management access.
This guide focuses on switch software configuration through the CLI.
For information on how to manage the switch through the Web management
interface, see the following guide:
Web Management Guide
Note:
For a general description of switch features, refer to “Introduction” in the
Web Management Guide.
For information on how to install the switch, see the following guide:
Installation Guide
– 3 –
How to Use This Guide
Conventions The following conventions are used throughout this guide to show information:
For all safety information and regulatory statements, see the following documents:
Quick Start Guide
Safety and Regulatory Information
Note:
Emphasizes important information or calls your attention to related features
or instructions.
Caution:
Alerts you to a potential hazard that could cause loss of data, or damage
the system or equipment.
Warning:
Alerts you to a potential hazard that could cause personal injury.
Revision History This section summarizes the changes in each revision of this guide.
March 2016 Revision
This is the second version of this guide. This guide is valid for software release
v1.1.166.154. It contains the following changes:
Table 1: Revision History
Description of Changes
Added:
Updated:
Deleted:
October 2015 Revision
This is the first version of this guide. This guide is valid for software release
v1.1.0.152.
– 4 –
Contents
How to Use This Guide 3
Contents 5
Figures 43
Tables 45
Section IGetting Started 53
1 Initial Switch Configuration 55
Connecting to the Switch 55
Configuration Options 55
Connecting to the Console Port 56
Selecting Legacy or Hybrid Operation Mode 57
Logging Onto the Command Line Interface 57
Setting Passwords 58
Remote Connections (Network Interface or Craft Port) 58
Obtaining and Installing a License for the Network Ports 59
Configuring the Switch for Remote Management 61
Using the Service Port or Network Interface 61
Setting an IP Address 62
Enabling SNMP Management Access 67
Managing System Files 69
Upgrading the Operation Code 70
Saving or Restoring Configuration Settings 71
Configuring Automatic Installation of Operation Code and Configuration Settings
72
Downloading Operation Code from a File Server 72
Specifying a DHCP Client Identifier 75
Downloading a Configuration File Referenced by a DHCP Server 75
Table 194: General Multicast Routing Commands 1013
Table 195: show ip mroute - display description 1015
Table 196: show ip mroute - display description 1018
Table 197: Static Multicast Routing Commands 1019
Table 198: Static Multicast Routing Commands 1020
Table 199: IPv4 and IPv6 PIM Commands 1022
Table 200: PIM-DM and PIM-SM Multicast Routing Commands 1022
Table 201: show ip pim neighbor - display description 1031
Table 202: show ip pim bsr-router - display description 1045
Table 203: show ip pim rp mapping - display description 1046
Table 204: show ip pim rp-hash - display description 1047
– 50 –
Tabl es
Table 205: PIM-DM and PIM-SM Multicast Routing Commands 1047
Table 206: show ipv6 pim neighbor - display description 1056
Table 207: show ip pim bsr-router - display description 1068
Table 208: show ip pim rp mapping - display description 1069
Table 209: show ip pim rp-hash - display description 1070
Table 210: Legacy and Hybrid Operating Mode Feature Set Differences 1073
Table 211: Troubleshooting Chart 1077
– 51 –
Tabl es
– 52 –
Section I
Getting Started
This section provides an overview of the switch, and introduces some basic
concepts about network switches. It also describes the basic settings required to
access the management interface.
This section includes these chapters:
◆"Initial Switch Configuration" on page 55
– 53 –
Section I
| Getting Started
– 54 –
1Initial Switch Configuration
This chapter includes information on connecting to the switch and basic
configuration procedures.
Connecting to the Switch
The switch includes a built-in network management agent. The agent offers a
variety of management options, including SNMP, RMON and a web-based interface.
A PC may also be connected directly to the switch for configuration and monitoring
via a command line interface (CLI).
Note:
An IPv4 address for this switch is obtained via DHCP by default. To change
this address, see “Setting an IP Address” on page 62.
Configuration Options The switch’s HTTP web agent allows you to configure switch parameters, monitor
port connections, and display statistics using a standard web browser such as
Internet Explorer 8 or above, Mozilla Firefox 32 or above, and Google Chrome 39 or
above. The switch’s web management interface can be accessed from any
computer attached to the network.
The CLI program can be accessed by a direct connection to the RS-232 serial
console port on the switch, or remotely by a Telnet connection over the network.
The switch’s management agent also supports SNMP (Simple Network
Management Protocol). This SNMP agent permits the switch to be managed from
any system in the network using network management software.
The switch’s web interface, console interface, and SNMP agent allow you to
perform the following management functions:
◆Set user names and passwords
◆Set an IP interface for any VLAN
◆Configure SNMP parameters
◆Enable/disable any port
◆Set the speed/duplex mode for any port
◆Configure the bandwidth of any port by limiting input or output rates
– 55 –
Chapter 1
Connecting to the Switch
| Initial Switch Configuration
◆Control port access through IEEE 802.1X security or static address filtering
◆Filter packets using Access Control Lists (ACLs)
◆Configure up to 4094 IEEE 802.1Q VLANs
◆Configure IP routing for unicast or multicast traffic
◆Configure router redundancy
◆Configure IGMP multicast filtering
◆Upload and download system firmware or configuration files via HTTP (using
the web interface) or FTP/TFTP (using the command line or web interface)
◆Configure Spanning Tree parameters
◆Configure Class of Service (CoS) priority queuing
◆Configure static or LACP trunks (up to 8)
◆Enable port mirroring
◆Set storm control on any port for excessive broadcast, multicast, or unknown
unicast traffic
Connecting to the
Console Port
◆Display system information and statistics
The switch provides an RS-232 serial port that enables a connection to a PC or
terminal for monitoring and configuring the switch. A null-modem console cable is
provided with the switch.
Attach a VT100-compatible terminal, or a PC running a terminal emulation program
to the switch. You can use the console cable provided with this package, or use a
null-modem cable that complies with the wiring assignments shown in the
Installation Guide.
To connect a terminal to the console port, complete the following steps:
1. Connect the console cable to the serial port on a terminal, or a PC running
terminal emulation software, and tighten the captive retaining screws on the
DB-9 connector.
2. Connect the other end of the cable to the RS-45 serial port on the switch.
3. Make sure the terminal emulation software is set as follows:
■
Select the appropriate serial port (COM port 1 or COM port 2).
■
Set the baud rate to 115200 bps.
■
Set the data format to 8 data bits, 1 stop bit, and no parity.
■
Set flow control to none.
■
Set the emulation mode to VT100.
■
When using HyperTerminal, select Terminal keys, not Windows keys.
– 56 –
Chapter 1
| Initial Switch Configuration
Connecting to the Switch
4. Power on the switch.
After the system completes the boot cycle, the logon screen appears.
Selecting Legacy or
Hybrid Operation
Mode
The switch supports two operating modes:
◆Legacy Mode – Basic feature set, accessible via CLI, web interface, or SNMP.
tables, switch configuration from OpenFlow controller, and partial legacy
feature set. This operating mode is only accessible via the CLI and SNMP.
Note:
For a list of differences in the features provided by Legacy Mode and Hybrid
Mode, see “Legacy and Hybrid Operating Mode Feature Set Differences” on
page 1073.
To select the operating mode, select one of the following options during bootup:
Select operation mode. If no selection is made within 5 seconds,
the mode, Legacy (example), you used last time will start automatically.....
1 - Legacy mode
2 - Hybrid mode
Select (1, 2): Operation Mode : Legacy......
Logging Onto the
Command Line
Interface
The CLI program provides two different command levels — normal access level
(Normal Exec) and privileged access level (Privileged Exec). The commands
available at the Normal Exec level are a limited subset of those available at the
Privileged Exec level and allow you to only display information and use basic
utilities. To fully configure the switch parameters, you must access the CLI at the
Privileged Exec level.
Access to both CLI levels are controlled by user names and passwords. The switch
has a default user name and password for each level. To log into the CLI at the
Privileged Exec level using the default user name and password, perform these
steps:
1. To initiate your console connection, press <Enter>. The “User Access
Verification” procedure starts.
2. At the User Name prompt, enter “admin.”
3. At the Password prompt, also enter “admin.” (The password characters are not
displayed on the console screen.)
4. The session is opened and the CLI displays the “Console#” prompt indicating
you have access at the Privileged Exec level.
– 57 –
Chapter 1
Connecting to the Switch
| Initial Switch Configuration
Setting Passwords If this is your first time to log into the CLI program, you should define new
passwords for both default user names using the “username” command, record
them and put them in a safe place.
Passwords can consist of up to 32 alphanumeric characters and are case sensitive.
To prevent unauthorized access to the switch, set the passwords as follows:
1. Open the console interface with the default user name and password “admin”
to access the Privileged Exec level.
2. Type “configure” and press <Enter>.
3. Type “username guest password 0 password,” for the Normal Exec level, where
password is your new password. Press <Enter>.
4. Type “username admin password 0 password,” for the Privileged Exec level,
where password is your new password. Press <Enter>.
Remote Connections
(Network Interface
or Craft Port)
Username: admin
Password:
CLI session with the AOS5700-54X* is opened.
To end the CLI session, enter [Exit].
* This manual covers the AS5700-54X 10G and AS6700-32X 40G Layer 3 Ethernet
switches. AS5700-54X and AS6700-32X are the bare metal switch names
without any operating system installed. AOS5700-54X and AOS6700-32X are the
same switches with the AOS operating system as described in this manual.
Other than the difference in port types, there are no significant differences.
Therefore most of the screen display examples are based on the AOS5700-54X.
Prior to accessing the switch’s onboard agent via a network connection, you must
first configure the switch’s network interface or craft port with a valid IPv4 or IPv6
address.
The default network interface is VLAN 1 which includes ports 1-32/54. However,
note that the switch also includes a Craft port on the front panel which provides a
secure management channel that is isolated from all other ports on the switch. This
interface is not configured with an IP address by default, but may be manually
configured with an IPv4 address. The Craft port is specified with the name “craft” in
the commands used to configure its IP address.
When configuring the network interface, the IP address, subnet mask, and default
gateway may all be set using a console connection, or DHCP protocol as described
in the following sections.
– 58 –
Chapter 1
| Initial Switch Configuration
Connecting to the Switch
An IPv4 address for the primary network interface is obtained via DHCP by default.
To manually configure this address or enable dynamic address assignment via
DHCP, see “Setting an IP Address” on page 62.
After configuring the switch’s IP parameters, you can access the onboard
configuration program from anywhere within the attached network. The onboard
configuration program can be accessed using Telnet or SSH from any computer
attached to the network. The switch can also be managed by any computer using a
web browser (Internet Explorer 8 or above, Mozilla Firefox 32 or above, and Google
Chrome 39 or above).
Note:
This switch supports eight Telnet sessions or SSH sessions.
The onboard program only provides access to basic configuration functions. To
access the full range of SNMP management functions, you must use SNMP-based
network management software.
Obtaining and
Installing a License
for the Network Ports
The operational ports (that is network ports but not the craft port) are disabled by
default. These ports will only function when a port usage license is obtained from
your distributor and installed on the switch.
To verify whether or not a port usage license is installed on the switch, enter the
following command from the craft port. If the Link Down Reason displays “Invalid
or Trial License, then you need to obtain and install a license for the network ports.
Note that a trial licence limits the number of usable ports, whereas a valid license
provides full access to all ports.
Note:
A trial license provides access to ports 1-12 and 49-52 for one month.
Console#show interfaces status ethernet 1/1
Information of Eth 1/1
Basic Information:
Member port of trunk 1 was created by user.
Port Type : 10GBASE SFP+
MAC Address : 70-72-CF-EA-1B-72
Configuration:
Port Admin : Up
Speed-duplex : 10G full
Capabilities : 10Gfull
Broadcast Storm : Enabled
Broadcast Storm Limit : 500 packets/second
Multicast Storm : Disabled
Multicast Storm Limit : 500 packets/second
Unknown Unicast Storm : Disabled
Unknown Unicast Storm Limit : 500 packets/second
Flow Control : Disabled
LACP : Disabled
MAC Learning : Enabled
Link-up-down Trap : Enabled
Media Type : None
MTU : 1518
– 59 –
Chapter 1
| Initial Switch Configuration
Connecting to the Switch
Current Status:
Link Status : Down
Link Down Reason : Invalid License or Trial License
Operation Speed-duplex : 10G full
Flow Control Type : None
Max Frame Size : 1522 bytes (1522 bytes for tagged frames)
MAC Learning Status : Enabled
To order a licence, you must provide the following information to your distributor:
◆Switch model number (AOS5700-54X or AOS6700-32X)
◆System MAC address. Enter the “show system” command from the craft port to
display this information.
Console#show system
System Description : AOS5700-54X
System OID String : 1.3.6.1.4.1.259.12.1.2.101
System Information
System Up Time : 0 days, 1 hours, 22 minutes, and 57.7 seconds
System Name :
System Location :
System Contact :
MAC Address (Unit 1) : 70-72-CF-EA-1B-71
Web Server : Enabled
Web Server Port : 80
Web Secure Server : Enabled
Web Secure Server Port : 443
Telnet Server : Enabled
Telnet Server Port : 23
Jumbo Frame : Disabled
...
To install a license, first verify that the craft port is configured with a valid IP address
using the “show interface” command. If no information is displayed for the craft
interface, use the ”ip address” command to configure the IP address for the craft
port as shown in the following example:
Download the corresponding license file as shown in the following example. Note
that the license file is named according to the device MAC address. The network
ports will be automatically activated within two minutes after successful
installation.
Console#copy tftp file
TFTP server IP address: 192.168.0.102
Choose file type:
The service port is a dedicated for out-of-band management. In general, the service
port should be used to manage the switch for security reasons. Traffic on this port is
segregated from normal network traffic on other switch ports and cannot be
switched or routed to the operational network. Additionally, if the operational
network is experiencing problems, the service port still allows you to access the
switch’s management interface and troubleshoot network problems. Configuration
options on the service port are limited, which makes it difficult to accidentally cut
off management access to the switch.
Alternatively, the switch can be managed through the operational network, known
as in-band management. Because in-band management traffic is mixed in with
operational network traffic, it is subject to all of the filtering rules usually applied to
a standard network ports such as ACLs and VLAN tagging. In-band network
management can be accessed via a connection to any network port (1-32/54).
– 61 –
Chapter 1
Configuring the Switch for Remote Management
| Initial Switch Configuration
Setting an IP Address You must establish IP address information for the switch to obtain management
access through the network. This can be done in either of the following ways:
◆Manual — You have to input the information, including IP address and subnet
mask. If your management station is not in the same IP subnet as the switch,
you will also need to specify the default gateway router.
◆Dynamic — The switch can send IPv4 configuration requests to DHCP address
allocation servers on the network, or can automatically generate a unique IPv6
host address based on the local subnet address prefix received in router
advertisement messages. An IPv6 link local address for use in a local network
can also be dynamically generated as described in “Obtaining an IPv6 Address”
on page 66.
This switch is designed as a router, and therefore does not support DHCP for
IPv6, so an IPv6 global unicast address for use in a network containing more
than one subnet can only be manually configured as described in “Assigning an
IPv6 Address” on page 63.
Manual Configuration
You can manually assign an IP address to the switch. You may also need to specify a
default gateway that resides between this device and management stations that
exist on another network segment. Valid IPv4 addresses consist of four decimal
numbers, 0 to 255, separated by periods. Anything outside this format will not be
accepted by the CLI program.
Note:
The IPv4 address for the network interface on this switch is obtained via
DHCP by default.
Assigning an IPv4 Address
Before you can assign an IP address to the switch, you must obtain the following
information from your network administrator:
◆IP address for the switch
◆Network mask for this network
◆Default gateway for the network
To assign an IPv4 address to the switch, complete the following steps
1. From the Global Configuration mode prompt, type “interface vlan 1” to access
the interface-configuration mode. Press <Enter>.
2. Type “ip address ip-address netmask,” where “ip-address” is the switch IP
address and “netmask” is the network mask for the network. Press <Enter>.
3. Type “exit” to return to the global configuration mode prompt. Press <Enter>.
– 62 –
Chapter 1
| Initial Switch Configuration
Configuring the Switch for Remote Management
4. To set the IP address of the default gateway for the network to which the switch
belongs, type “ip default-gateway gateway,” where “gateway” is the IP address
of the default gateway. Press <Enter>.
This section describes how to configure a “link local” address for connectivity
within the local subnet only, and also how to configure a “global unicast” address,
including a network prefix for use on a multi-segment network and the host
portion of the address.
An IPv6 prefix or address must be formatted according to RFC 2373 “IPv6
Addressing Architecture,” using 8 colon-separated 16-bit hexadecimal values. One
double colon may be used to indicate the appropriate number of zeros required to
fill the undefined fields. For detailed information on the other ways to assign IPv6
addresses, see “IPv6 Interface” on page 754.
Link Local Address — All link-local addresses must be configured with a prefix in
the range of FE80~FEBF. Remember that this address type makes the switch
accessible over IPv6 for all devices attached to the same local subnet only. Also, if
the switch detects that the address you configured conflicts with that in use by
another device on the subnet, it will stop using the address in question, and
automatically generate a link local address that does not conflict with any other
devices on the local subnet.
To configure an IPv6 link local address for the switch, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access
the interface-configuration mode. Press <Enter>.
2. Type “ipv6 address” followed by up to 8 colon-separated 16-bit hexadecimal
values for the ipv6-address similar to that shown in the example, followed by
the “link-local” command parameter. Then press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ipv6 address FE80::260:3EFF:FE11:6700 link-local
Console(config-if)#ipv6 enable
Console(config-if)#end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
fe80::260:3eff:fe11:6700%1/64
Global unicast address(es):
(None)
Joined group address(es):
ff02::2
ff02::1:ff00:0
– 63 –
Chapter 1
| Initial Switch Configuration
Configuring the Switch for Remote Management
ff02::1:ff11:6700
ff02::1:2
ff02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 1.
ND retransmit interval is 1000 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised router lifetime is 1800 seconds
Console#
Address for Multi-segment Network — Before you can assign an IPv6 address to the
switch that will be used to connect to a multi-segment network, you must obtain
the following information from your network administrator:
◆Prefix for this network
◆IP address for the switch
◆Default gateway for the network
For networks that encompass several different subnets, you must define the full
address, including a network prefix and the host address for the switch. You can
specify either the full IPv6 address, or the IPv6 address and prefix length. The prefix
length for an IPv6 network is the number of bits (from the left) of the prefix that
form the network address, and is expressed as a decimal number. For example, all
IPv6 addresses that start with the first byte of 73 (hexadecimal) could be expressed
as 73:0:0:0:0:0:0:0/8 or 73::/8.
To generate an IPv6 global unicast address for the switch, complete the following
steps:
1. From the global configuration mode prompt, type “interface vlan 1” to access
the interface-configuration mode. Press <Enter>.
2. From the interface prompt, type “ipv6 address ipv6-address” or “ipv6 address
ipv6-address/prefix-length,” where “prefix-length” indicates the address bits
used to form the network portion of the address. (The network address starts
from the left of the prefix and should encompass some of the ipv6-address
bits.) The remaining bits are assigned to the host interface. Press <Enter>.
3. Type “exit” to return to the global configuration mode prompt. Press <Enter>.
4. To set the IP address of the IPv6 default gateway for the network to which the
switch belongs, type “ipv6 default-gateway gateway,” where “gateway” is the
IPv6 address of the default gateway. Press <Enter>.
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
fe80::260:3eff:fe11:6700%1/64
Global unicast address(es):
2001:db8:2222:7272::/64, subnet is 2001:db8:2222:7272::/64
Joined group address(es):
ff02::2
ff02::1:ff00:0
ff02::1:ff11:6700
ff02::1:2
ff02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 1.
ND retransmit interval is 1000 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised router lifetime is 1800 seconds
If you select the “dhcp” option, the system will immediately start broadcasting
service requests. IP will be enabled but will not function until a DHCP reply has
been received. Requests are broadcast every few minutes using exponential
backoff until IP configuration information is obtained from a DHCP server. DHCP
values can include the IP address, subnet mask, and default gateway. If the DHCP
server is slow to respond, you may need to use the “ip dhcp restart client”
command to re-start broadcasting service requests.
Note that the “ip dhcp restart client” command can also be used to start
broadcasting service requests for all VLANs configured to obtain address
assignments through DHCP. It may be necessary to use this command when DHCP
is configured on a VLAN, and the member ports which were previously shut down
are now enabled.
If the “dhcp” option is saved to the startup-config file (step 6), then the switch will
start broadcasting service requests as soon as it is powered on.
To automatically configure the switch by communicating with DHCP address
allocation servers on the network, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access
the interface-configuration mode. Press <Enter>.
2. At the interface-configuration mode prompt, use the following command:
■
To obtain IP settings via DHCP, type “ip address dhcp” and press <Enter>.
– 65 –
Chapter 1
| Initial Switch Configuration
Configuring the Switch for Remote Management
3. Type “end” to return to the Privileged Exec mode. Press <Enter>.
4. Wait a few minutes, and then check the IP configuration settings by typing the
“show ip interface” command. Press <Enter>.
5. Then save your configuration changes by typing “copy running-config startup-
config.” Enter the startup file name and press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ip address dhcp
Console(config-if)#end
Console#show ip interface
VLAN 1 is Administrative Up - Link Up
Address is 00-E0-0C-00-00-FB
Index: 1001, MTU: 1500
Address Mode is DHCP
IP Address: 192.168.0.2 Mask: 255.255.255.0
Proxy ARP is disabled
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Obtaining an IPv6 Address
Link Local Address — There are several ways to configure IPv6 addresses. The
simplest method is to automatically generate a “link local” address (identified by an
address prefix in the range of FE80~FEBF). This address type makes the switch
accessible over IPv6 for all devices attached to the same local subnet.
To generate an IPv6 link local address for the switch, complete the following steps:
1. From the Global Configuration mode prompt, type “interface vlan 1” to access
the interface-configuration mode. Press <Enter>.
2. Type “ipv6 enable” and press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ipv6 enable
Console(config-if)#end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled
Link-local address:
FE80::260:3EFF:FE11:6700/64
Global unicast address(es):
2001:DB8:2222:7272::/64, subnet is 2001:DB8:2222:7272::/64
Joined group address(es):
FF02::1:FF00:0
FF02::1:FF11:6700
FF02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 1.
ND retransmit interval is 1000 milliseconds
– 66 –
ND advertised retransmit interval is 0 milliseconds
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised router lifetime is 1800 seconds
Console#
Enabling SNMP Management Access
The switch can be configured to accept management commands from Simple
Network Management Protocol (SNMP) applications such as Edge -Core ECView Pro.
You can configure the switch to respond to SNMP requests or generate SNMP traps.
When SNMP management stations send requests to the switch (either to return
information or to set a parameter), the switch provides the requested data or sets
the specified parameter. The switch can also be configured to send information to
SNMP managers (without being requested by the managers) through trap
messages, which inform the manager that certain events have occurred.
Chapter 1
| Initial Switch Configuration
Enabling SNMP Management Access
The switch includes an SNMP agent that supports SNMP version 1, 2c, and 3 clients.
To provide management access for version 1 or 2c clients, you must specify a
community string. The switch provides a default MIB View (i.e., an SNMPv3
construct) for the default “public” community string that provides read access to
the entire MIB tree, and a default view for the “private” community string that
provides read/write access to the entire MIB tree. However, you may assign new
views to version 1 or 2c community strings that suit your specific security
requirements (see snmp-server view command).
Community Strings (for SNMP version 1 and 2c clients)
Community strings are used to control management access to SNMP version 1 and
2c stations, as well as to authorize SNMP stations to receive trap messages from the
switch. You therefore need to assign community strings to specified users, and set
the access level.
The default strings are:
◆public - with read-only access. Authorized management stations are only able
to retrieve MIB objects.
◆private - with read/write access. Authorized management stations are able to
both retrieve and modify MIB objects.
To prevent unauthorized access to the switch from SNMP version 1 or 2c clients, it is
recommended that you change the default community strings.
– 67 –
Chapter 1
Enabling SNMP Management Access
| Initial Switch Configuration
To configure a community string, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt, type “snmp-
2. To remove an existing string, simply type “no snmp-server community string,”
Console(config)#snmp-server community admin rw
Console(config)#snmp-server community private
Console(config)#
Note:
recommend that you delete both of the default community strings. If there are no
community strings, then SNMP management access from SNMP v1 and v2c clients
is disabled.
server community string mode,” where “string” is the community access string
and “mode” is rw (read/write) or ro (read only). Press <Enter>. (Note that the
default mode is read only.)
where “string” is the community access string to remove. Press <Enter>.
If you do not intend to support access to SNMP version 1 and 2c clients, we
Trap Receivers
You can also specify SNMP stations that are to receive traps from the switch. To
configure a trap receiver, use the “snmp-server host” command. From the
Privileged Exec level global configuration mode prompt, type:
where “host-address” is the IP address for the trap receiver, “community-string”
specifies access rights for a version 1/2c host, or is the user name of a version 3 host,
“version” indicates the SNMP client version, and “auth | noauth | priv” means that
authentication, no authentication, or authentication and privacy is used for v3
clients. Then press <Enter>. For a more detailed description of these parameters,
see the snmp-server host command. The following example creates a trap host for
each type of SNMP client.
Console(config)#snmp-server host 10.1.19.23 batman
Console(config)#snmp-server host 10.1.19.98 robin version 2c
Console(config)#snmp-server host 10.1.19.34 barbie version 3 auth
Console(config)#
Configuring Access for SNMP Version 3 Clients
To configure management access for SNMPv3 clients, you need to first create a
view that defines the portions of MIB that the client can read or write, assign the
view to a group, and then assign the user to a group. The following example creates
one view called “mib-2” that includes the entire MIB-2 tree branch, and then
– 68 –
Chapter 1
| Initial Switch Configuration
Managing System Files
another view that includes the IEEE 802.1d bridge MIB. It assigns these respective
read and read/write views to a group call “r&d” and specifies group authentication
via MD5 or SHA. In the last step, it assigns a v3 user to this group, indicating that
MD5 will be used for authentication, provides the password “greenpeace” for
authentication, and the password “einstien” for encryption.
Console(config)#snmp-server view mib-2 1.3.6.1.2.1 included
Console(config)#snmp-server view 802.1d 1.3.6.1.2.1.17 included
Console(config)#snmp-server group r&d v3 auth mib-2 802.1d
Console(config)#snmp-server user steve r&d v3 auth md5 greenpeace priv des56
einstien
Console(config)#
For a more detailed explanation on how to configure the switch for access from
SNMP v3 clients, refer to the CLI Reference Guide or Web Management Guide.
Managing System Files
The switch’s flash memory supports three types of system files that can be
managed by the CLI program, the web interface, or SNMP. The switch’s file system
allows files to be uploaded and downloaded, copied, deleted, and set as a start-up
file. The types of files are:
◆Configuration — This file type stores system configuration information and is
◆Operation Code — System software that is executed after boot-up, also
created when configuration settings are saved. Saved configuration files can be
selected as a system start-up file or can be uploaded via FTP/TFTP to a server
for backup. The file named “Factory_Default_Config.cfg” contains all the system
default settings and cannot be deleted from the system. If the system is booted
with the factory default settings, the switch will also create a file named
“startup1.cfg” that contains system settings for switch initialization, including
information about the unit identifier, and MAC address for the switch. The
configuration settings from the factory defaults configuration file are copied to
this file, which is then used to boot the switch. See “Saving or Restoring
Configuration Settings” on page 71 for more information.
known as run-time code. This code runs the switch operations and provides the
CLI and web management interfaces.
◆Diagnostic Code — Software that is run during system boot-up, also known as
POST (Power On Self-Test).
Note:
The Boot ROM and Loader cannot be uploaded or downloaded from the
FTP/TFTP server. You must follow the instructions in the release notes for new
firmware, or contact your distributor for help.
– 69 –
Chapter 1
| Initial Switch Configuration
Managing System Files
Due to the size limit of the flash memory, the switch supports only two operation
code files. However, you can have as many diagnostic code files and configuration
files as available flash memory space allows. The switch has a total of 2 GB of flash
memory for system files.
In the system flash memory, one file of each type must be set as the start-up file.
During a system boot, the diagnostic and operation code files set as the start-up file
are run, and then the start-up configuration file is loaded.
Note that configuration files should be downloaded using a file name that reflects
the contents or usage of the file settings. If you download directly to the runningconfig, the system will reboot, and the settings will have to be copied from the
running-config to a permanent file.
Upgrading the
Operation Code
The following example shows how to download new firmware to the switch and
activate it. The TFTP server could be any standards-compliant server running on
Windows or Linux. When downloading from an FTP server, the logon interface will
prompt for a user name and password configured on the remote server. Note that
“anonymous” is set as the default user name.
File names on the switch are case-sensitive. The destination file name should not
contain slashes (\ or /), and the maximum length for file names is 32 characters for
files on the switch or 128 characters for files on the server. (Valid characters: A-Z,
a-z, 0-9, “.”, “-”)
Console#copy tftp file
TFTP server ip address: 10.1.0.19
Choose file type:
-Write to FLASH finish.
Success.
Console#config
Console(config)#boot system opcode: m360.bix
Console(config)#exit
Console#dir
File Name Type Startup Modify Time Size(bytes)
-------------------------- -------------- ------- ------------------- --------- Unit 1:
runtime.bix OpCode Y 1972-05-18 21:50:04 32842013
Factory_Default_Config.cfg Config N 2014-12-30 02:34:32 455
startup1.cfg Config Y 2014-12-30 02:34:38 2917
---------------------------------------------------------------------------- Free space for compressed user config files:1593241600
Console#
– 70 –
Chapter 1
| Initial Switch Configuration
Managing System Files
Saving or Restoring
Configuration
Settings
Configuration commands only modify the running configuration file and are not
saved when the switch is rebooted. To save all your configuration changes in
nonvolatile storage, you must copy the running configuration file to the start-up
configuration file using the “copy” command.
New startup configuration files must have a name specified. File names on the
switch are case-sensitive, can be from 1 to 31 characters, must not contain slashes
(\ or /), and the leading letter of the file name must not be a period (.). (Valid
characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
There can be more than one user-defined configuration file saved in the switch’s
flash memory, but only one is designated as the “startup” file that is loaded when
the switch boots. The copy running-config startup-config command always sets
the new file as the startup file. To select a previously saved configuration file, use
the boot system config:<filename> command.
The maximum number of saved configuration files depends on available flash
memory. The amount of available flash memory can be checked by using the dir
command.
To save the current configuration settings, enter the following command:
1. From the Privileged Exec mode prompt, type “copy running-config startup-
config” and press <Enter>.
2. Enter the name of the start-up file. Press <Enter>.
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Console#
To restore configuration settings from a backup server, enter the following
command:
1. From the Privileged Exec mode prompt, type “copy tftp startup-config” and
press <Enter>.
2. Enter the address of the TFTP server. Press <Enter>.
3. Enter the name of the startup file stored on the server. Press <Enter>.
4. Enter the name for the startup file on the switch. Press <Enter>.
– 71 –
Chapter 1
Configuring Automatic Installation of Operation Code and Configuration Settings
| Initial Switch Configuration
Console#copy tftp startup-config
TFTP server IP address: 192.168.0.4
Source configuration file name: startup-rd.cfg
Startup configuration file name [startup1.cfg]:
Success.
Console#
Configuring Automatic Installation of Operation Code and Configuration Settings
Downloading
Operation Code from
a File Server
Automatic Operation Code Upgrade can automatically download an operation
code file when a file newer than the currently installed one is discovered on the file
server. After the file is transferred from the server and successfully written to the file
system, it is automatically set as the startup file, and the switch is rebooted.
Usage Guidelines
◆If this feature is enabled, the switch searches the defined URL once during the
bootup sequence.
◆FTP (port 21) and TFTP (port 69) are both supported. Note that the TCP/UDP
port bindings cannot be modified to support servers listening on non-standard
ports.
◆The host portion of the upgrade file location URL must be a valid IPv4 IP
address. DNS host names are not recognized. Valid IP addresses consist of four
numbers, 0 to 255, separated by periods.
◆The path to the directory must also be defined. If the file is stored in the root
directory for the FTP/TFTP service, then use the “/” to indicate this (e.g., ftp://
192.168.0.1/).
◆The file name must not be included in the upgrade file location URL. The file
name of the code stored on the remote server must be ecs5610-52s.bix (using
lower case letters as indicated).
◆The FTP connection is made with PASV mode enabled. PASV mode is needed to
traverse some fire walls, even if FTP traffic is not blocked. PASV mode cannot be
disabled.
◆The switch-based search function is case-insensitive in that it will accept a file
name in upper or lower case (i.e., the switch will accept AOS5700-54X.BIX from
the server even though AOS5700-54X.bix was requested). However, keep in
mind that the file systems of many operating systems such as Unix and most
Unix-like systems (FreeBSD, NetBSD, OpenBSD, and most Linux distributions,
etc.) are case-sensitive, meaning that two files in the same directory,
aos5700-52x.bix. and AOS5700-54X.BIX are considered to be unique files. Thus, if
– 72 –
Chapter 1
Configuring Automatic Installation of Operation Code and Configuration Settings
| Initial Switch Configuration
the upgrade file is stored as AOS5700-54X.BIX (or even Aos5700-54x.bix) on a
case-sensitive server, then the switch (requesting AOS5700-54X.bix) will not be
upgraded because the server does not recognize the requested file name and
the stored file name as being equal. A notable exception in the list of casesensitive Unix-like operating systems is Mac OS X, which by default is caseinsensitive. Please check the documentation for your server’s operating system
if you are unsure of its file system’s behavior.
◆Note that the switch itself does not distinguish between upper and lower-case
file names, and only checks to see if the file stored on the server is more recent
than the current runtime image.
◆If two operation code image files are already stored on the switch’s file system,
then the non-startup image is deleted before the upgrade image is transferred.
◆The automatic upgrade process will take place in the background without
impeding normal operations (data switching, etc.) of the switch.
◆During the automatic search and transfer process, the administrator cannot
transfer or update another operation code image, configuration file, public key,
or HTTPS certificate (i.e., no other concurrent file management operations are
possible).
◆The upgrade operation code image is set as the startup image after it has been
successfully written to the file system.
◆The switch will send an SNMP trap and make a log entry upon all upgrade
successes and failures.
◆The switch will immediately restart after the upgrade file is successfully written
to the file system and set as the startup image.
To enable automatic upgrade, enter the following commands:
1. Specify the TFTP or FTP server to check for new operation code.
■
When specifying a TFTP server, the following syntax must be used, where
filedir indicates the path to the directory containing the new image:
tftp://192.168.0.1[/filedir]/
■
When specifying an FTP server, the following syntax must be used, where
filedir indicates the path to the directory containing the new image:
If the user name is omitted, “anonymous” will be used for the connection. If
the password is omitted a null string (“”) will be used for the connection.
– 73 –
Chapter 1
| Initial Switch Configuration
Configuring Automatic Installation of Operation Code and Configuration Settings
This shows how to specify a TFTP server where new code is stored.
3. Set the switch to automatically upgrade the current operational code when a
new version is detected on the server. When the switch starts up and automatic
image upgrade is enabled by this command, the switch will follow these steps
when it boots up:
a. It will search for a new version of the image at the location specified by
upgrade opcode path command. The name for the new image stored on
the TFTP server must be aos5700-54x.bix. If the switch detects a code
version newer than the one currently in use, it will download the new
image. If two code images are already stored in the switch, the image not
set to start up the system will be overwritten by the new version.
b. After the image has been downloaded, the switch will send a trap message
to log whether or not the upgrade operation was successful.
c. It sets the new version as the startup image.
d. It then restarts the system to start using the new image.
Console(config)#upgrade opcode auto
Console(config)#
4. Display the automatic upgrade settings.
Console#show upgrade
Auto Image Upgrade Global Settings:
Status : Enabled
Reload Status : Enabled
Path :
File Name : aos5700-54x.bix
Console#
– 74 –
Chapter 1
Configuring Automatic Installation of Operation Code and Configuration Settings
| Initial Switch Configuration
Specifying a DHCP
Client Identifier
DHCP servers index their database of address bindings using the client’s Media
Access Control (MAC) Address or a unique client identifier. The client identifier is
used to identify the vendor class and configuration of the switch to the DHCP
server, which then uses this information to decide on how to service the client or
the type of information to return.
DHCP client Identifier (Option 60) is used by DHCP clients to specify their unique
identifier. The client identifier is optional and can be specified while configuring
DHCP on the primary network interface. DHCP Option 60 is disabled by default.
The general framework for this DHCP option is set out in RFC 2132 (Option 60). This
information is used to convey configuration settings or other identification
information about a client, but the specific string to use should be supplied by your
service provider or network administrator. Options 60 (vendor-class-identifier), 66
(tftp-server-name) and 67 (bootfile-name) statements can be added to the server
daemon’s configuration file as described in the following section.
If the DHCP server has an index entry for a switch requesting service, it should reply
with the TFTP server name and boot file name. Note that the vendor class identifier
can be formatted in either text or hexadecimal, but the format used by both the
client and server must be the same.
Information passed on to the switch from a DHCP server may also include a
configuration file to be downloaded and the TFTP servers where that file can be
accessed. If the Factory Default Configuration file is used to provision the switch at
startup, in addition to requesting IP configuration settings from the DHCP server, it
will also ask for the name of a bootup configuration file and TFTP servers where
that file is stored.
If the switch receives information that allows it to download the remote bootup file,
it will save this file to a local buffer, and then restart the provision process.
Note the following DHCP client behavior:
◆The bootup configuration file received from a TFTP server is stored on the
switch with the original file name. If this file name already exists in the switch,
the file is overwritten.
◆If the name of the bootup configuration file is the same as the Factory Default
Configuration file, the download procedure will be terminated, and the switch
will not send any further DHCP client requests.
– 75 –
Chapter 1
Configuring Automatic Installation of Operation Code and Configuration Settings
| Initial Switch Configuration
◆If the switch fails to download the bootup configuration file based on
information passed by the DHCP server, it will not send any further DHCP client
requests.
◆If the switch does not receive a DHCP response prior to completing the bootup
process, it will continue to send a DHCP client request once a minute. These
requests will only be terminated if the switch’s address is manually configured,
but will resume if the address mode is set back to DHCP.
To successfully transmit a bootup configuration file to the switch, the DHCP
daemon (using a Linux based system for this example) must be configured with the
following information:
◆Options 60, 66 and 67 statements can be added to the daemon’s configuration
file.
Table 2: Options 60, 66 and 67 Statements
Option
KeywordParameter
60vendor-class-identifiera string indicating the vendor class identifier
66tftp-server-namea string indicating the tftp server name
67bootfile-namea string indicating the bootfile name
◆By default, DHCP option 66/67 parameters are not carried in a DHCP server
Statement
reply. To ask for a DHCP reply with option 66/67 information, the DHCP client
request sent by this switch includes a “parameter request list” asking for this
information. Besides these items, the client request also includes a “vendor
class identifier” that allows the DHCP server to identify the device, and select
the appropriate configuration file for download. This information is included in
Option 55 and 124.
Table 3: Options 55 and 124 Statements
Option
KeywordParameter
55dhcp-parameter-request-lista list of parameters, separated by a comma ', '
124vendor-class-identifiera string indicating the vendor class identifier
Statement
The following configuration example is provided for a Linux-based DHCP daemon
(dhcpd.conf file). In the “Vendor class” section, the server will always send Option
66 and 67 to tell the switch to download the “test” configuration file from server
class "Option66,67_1" {#DHCP Option 60 Vendor class
two
match if option vendor-class-identifier = "aos5700-54x.cfg";
option tftp-server-name "192.168.255.101";
option bootfile-name "test";
}
| Initial Switch Configuration
Setting the System Clock
Note:
Setting the System Clock
Simple Network Time Protocol (SNTP) or Network Time Protocol (NTP) can be used
to set the switch’s internal clock based on periodic updates from a time server.
Maintaining an accurate time on the switch enables the system log to record
meaningful dates and times for event entries. You can also manually set the clock. If
the clock is not set manually or via SNTP or NTP, the switch will only record the time
from the factory default set at the last bootup.
When the SNTP client is enabled, the switch periodically sends a request for a time
update to a configured time server. You can configure up to three time server IP
addresses. The switch will attempt to poll each server in the configured sequence.
The switch also supports the following time settings:
◆Time Zone – You can specify the offset from Coordinated Universal Time (UTC),
Use “aos5700-54x.cfg” for the vendor-class-identifier in the dhcpd.conf file.
also known as Greenwich Mean Time (GMT).
◆Summer Time/Daylight Saving Time (DST) – In some regions, the time shifts by
one hour in the fall and spring. The switch supports manual entry for one-time
or recurring clock shifts.
– 77 –
Chapter 1
| Initial Switch Configuration
Setting the System Clock
Setting the Time
Manually
To manually set the clock to 14:11:36, April 1st, 2013, enter this command.
Console#calendar set 14 11 36 1 April 2013
Console#
To set the time zone, enter a command similar to the following.
Console(config)#clock timezone Japan hours 8 after-UTC
Console(config)#
To set the time shift for summer time, enter a command similar to the following.
Console(config)#clock summer-time SUMMER date 2 april 2013 0 0 30 june 2013 0
0
Console(config)#
To display the clock configuration settings, enter the following command.
Console#show calendar
Current Time : Apr 2 15:56:12 2013
Time Zone : UTC, 08:00
Summer Time : SUMMER, offset 60 minutes
Apr 2 2013 00:00 to Jun 30 2013 00:00
Summer Time in Effect : Yes
Console#
Configuring SNTP Setting the clock based on an SNTP server can provide more accurate clock
synchronization across network switches than manually-configured time. To
configure SNTP, set the switch as an SNTP client, and then set the polling interval,
and specify a time server as shown in the following example.
Console(config)#sntp client
Console(config)#sntp poll 60
Console(config)#sntp server 10.1.0.19
Console(config)#exit
Console#show sntp
Current Time : Apr 2 16:06:07 2013
Poll Interval : 60 seconds
Current Mode : Unicast
SNTP Status : Enabled
SNTP Server : 10.1.0.19
Current Server : 10.1.0.19
Console#
– 78 –
Chapter 1
| Initial Switch Configuration
Setting the System Clock
Configuring NTP Requesting the time from a an NTP server is the most secure method. You can
enable NTP authentication to ensure that reliable updates are received from only
authorized NTP servers. The authentication keys and their associated key number
must be centrally managed and manually distributed to NTP servers and clients.
The key numbers and key values must match on both the server and client.
When more than one time server is configured, the client will poll all of the time
servers, and compare the responses to determine the most reliable and accurate
time update for the switch.
To configure NTP time synchronization, enter commands similar to the following.
Console(config)#ntp client
Console(config)#ntp authentication-key 45 md5 thisiskey45
Console(config)#ntp authenticate
Console(config)#ntp server 192.168.3.20
Console(config)#ntp server 192.168.3.21
Console(config)#ntp server 192.168.5.23 key 19
Console(config)#exit
Console#show ntp
Current Time : Apr 29 13:57:32 2011
Polling : 1024 seconds
Current Mode : unicast
NTP Status : Enabled
NTP Authenticate Status : Enabled
Last Update NTP Server : 192.168.0.88 Port: 123
Last Update Time : Mar 12 02:41:01 2013 UTC
NTP Server 192.168.0.88 version 3
NTP Server 192.168.3.21 version 3
NTP Server 192.168.4.22 version 3 key 19
NTP Authentication Key 19 md5 42V68751663T6K11P2J307210R885
Current Time : Apr 2 16:28:34 2013
Polling : 1024 seconds
Current Mode : unicast
NTP Status : Enabled
NTP Authenticate Status : Enabled
Last Update NTP Server : 192.168.5.23 Port: 0
Last Update Time : Apr 2 16:00:00 2013 UTC
NTP Server 192.168.3.20 version 3
NTP Server 192.168.3.21 version 3
NTP Server 192.168.5.23 version 3 key 19
NTP Authentication Key 45 md5 2662T75S5658RU5424180034777
Console#
– 79 –
Chapter 1
Setting the System Clock
| Initial Switch Configuration
– 80 –
Section II
Command Line Interface
This section provides a detailed description of the Command Line Interface, along
with examples for all of the commands.
This section includes these chapters:
◆“Using the Command Line Interface” on page 83
◆“General Commands” on page 95
◆“System Management Commands” on page 103
◆“SNMP Commands” on page 181
◆“Remote Monitoring Commands” on page 203
◆“Authentication Commands” on page 211
◆“General Security Measures” on page 255
◆“Access Control Lists” on page 335
◆“Interface Commands” on page 359
◆“Link Aggregation Commands” on page 389
◆“Port Mirroring Commands” on page 409
◆“Congestion Control Commands” on page 419
◆“Loopback Detection Commands” on page 423
◆“UniDirectional Link Detection Commands” on page 429
◆“Address Table Commands” on page 437
◆“Spanning Tree Commands” on page 443
◆“VLAN Commands” on page 467
– 81 –
Section II
| Command Line Interface
◆“Class of Service Commands” on page 507
◆“Quality of Service Commands” on page 527
◆“Multicast Filtering Commands” on page 581
◆“LLDP Commands” on page 653
◆“CFM Commands” on page 681
◆“DHCP Commands” on page 733
◆“IP Interface Commands” on page 741
◆“VRRP Commands” on page 791
◆“IP Routing Commands” on page 801
◆“Multicast Routing Commands” on page 1013
– 82 –
2Using the Command Line
Interface
This chapter describes how to use the Command Line Interface (CLI).
Accessing the CLI
When accessing the management interface for the switch over a direct connection
to the server’s console port, or via a Telnet or Secure Shell connection (SSH), the
switch can be managed by entering command keywords and parameters at the
prompt. Using the switch's command-line interface (CLI) is very similar to entering
commands on a UNIX system.
Console Connection To access the switch through the console port, perform these steps:
1. At the console prompt, enter the user name and password. (The default user
names are “admin” and “guest” with corresponding passwords of “admin” and
“guest.”) When the administrator user name and password is entered, the CLI
displays the “Console#” prompt and enters privileged access mode
(i.e., Privileged Exec). But when the guest user name and password is entered,
the CLI displays the “Console>” prompt and enters normal access mode
(i.e., Normal Exec).
2. Enter the necessary commands to complete your desired tasks.
3. When finished, exit the session with the “quit” or “exit” command.
After connecting to the system through the console port, the login screen displays:
User Access Verification
Username: admin
Password:
CLI session with the AOS5700-54X is opened.
To end the CLI session, enter [Exit].
Console#
Telnet Connection Telnet operates over the IP transport protocol. In this environment, your
management station and any network device you want to manage over the
network must have a valid IP address. Valid IP addresses consist of four numbers, 0
to 255, separated by periods. Each address consists of a network portion and host
– 83 –
Chapter 2
Accessing the CLI
| Using the Command Line Interface
portion. For example, the IP address assigned to this switch, 10.1.0.1, consists of a
network portion (10.1.0) and a host portion (1).
Note:
The IP address for this switch is obtained via DHCP by default.
To access the switch through a Telnet session, you must first set the IP address for
the Master unit, and set the default gateway if you are managing the switch from a
different IP subnet. For example,
If your corporate network is connected to another network outside your office or to
the Internet, you need to apply for a registered IP address. However, if you are
attached to an isolated network, then you can use any IP address that matches the
network segment to which you are attached.
After you configure the switch with an IP address, you can open a Telnet session by
performing these steps:
1. From the remote host, enter the Telnet command and the IP address of the
device you want to access.
2. At the prompt, enter the user name and system password. The CLI will display
the “Vty-n#” prompt for the administrator to show that you are using privileged
access mode (i.e., Privileged Exec), or “Vty-n>” for the guest to show that you
are using normal access mode (i.e., Normal Exec), where n indicates the number
of the current Telnet session.
3. Enter the necessary commands to complete your desired tasks.
4. When finished, exit the session with the “quit” or “exit” command.
After entering the Telnet command, the login screen displays:
Username: admin
Password:
CLI session with the AOS5700-54X is opened.
To end the CLI session, enter [Exit].
Vty-0#
Note:
You can open up to eight sessions to the device via Telnet or SSH.
– 84 –
Entering Commands
Chapter 2
| Using the Command Line Interface
This section describes how to enter CLI commands.
Entering Commands
Keywords and
Arguments
A CLI command is a series of keywords and arguments. Keywords identify a
command, and arguments specify configuration parameters. For example, in the
command “show interfaces status ethernet 1/5,” show interfaces and status are
keywords, ethernet is an argument that specifies the interface type, and 1/5
specifies the unit/port.
You can enter commands as follows:
◆To enter a simple command, enter the command keyword.
◆To enter multiple commands, enter each command in the required order. For
example, to enable Privileged Exec command mode, and display the startup
configuration, enter:
Console>enable
Console#show startup-config
◆To enter commands that require parameters, enter the required parameters
after the command keyword. For example, to set a password for the
administrator, enter:
Console(config)#username admin password 0 smith
Minimum
Abbreviation
Command
Completion
The CLI will accept a minimum number of characters that uniquely identify a
command. For example, the command “configure” can be entered as con. If an
entry is ambiguous, the system will prompt for further input.
If you terminate input with a Tab key, the CLI will print the remaining characters of a
partial keyword up to the point of ambiguity. In the “logging history” example,
typing log followed by a tab will result in printing the command up to “logging.”
– 85 –
Chapter 2
| Using the Command Line Interface
Entering Commands
Getting Help on
Commands
You can display a brief description of the help system by entering the help
command. You can also display command syntax by using the “?” character to list
keywords or parameters.
Showing Commands
If you enter a “?” at the command prompt, the system will display the first level of
keywords or command groups. You can also display a list of valid keywords for a
specific command. For example, the command “show ?” displays a list of possible
show commands:
Console#show ?
access-group Access groups
access-list Access lists
arp Information of ARP cache
banner Banner info
bridge-ext Bridge extension information
calendar Date and time information
class-map Displays class maps
cn Displays congestion notification information
dcbx DCBX
debug State of each debugging option
dns DNS information
dot1q-tunnel 802.1Q tunnel
dot1x 802.1X content
ecmp ECMP information
ethernet Shows Metro Ethernet information
ets 802.1Qaz configuration
hardware Hardware ralated functions
hash-selection Hash selection lists
history Shows history information
hosts Host information
interfaces Shows interface information
ip IP information
ipv6 IPv6 information
l2protocol-tunnel Layer 2 protocol tunneling configuration
lacp LACP statistics
license show license
line TTY line information
lldp LLDP
location-led Location LED operation
log Log records
logging Logging setting
loop Shows the information of loopback
loopback-detection Shows loopback detection information
mac MAC access list
mac-address-table Configuration of the address table
management Shows management information
memory Memory utilization
mlag Displays MLAG information
network-access Shows the entries of the secure port
nlm Show notification log
ntp Network Time Protocol configuration
pfc Displays Priority-based Flow Control Information
policy-map Displays policy maps
port Port characteristics
port-channel Port channel information
process Device process
public-key Public key information
qos Quality of Service
queue Priority queue information
– 86 –
Chapter 2
| Using the Command Line Interface
Entering Commands
radius-server RADIUS server information
reload Shows the reload settings
rmon Remote Monitoring Protocol
route-map Shows route-map
rspan Display status of the current RSPAN configuration
running-config Information on the running configuration
sflow Shows the sflow information
snmp Simple Network Management Protocol configuration and
statistics
snmp-server Displays SNMP server configuration
sntp Simple Network Time Protocol configuration
spanning-tree Spanning-tree configuration
ssh Secure shell server connections
startup-config Startup system configuration
system System information
tacacs-server TACACS server information
tech-support Technical information
traffic-segmentation Traffic segmentation information
udld Displays UDLD information
upgrade Shows upgrade information
users Information about users logged in
version System hardware and software versions
vlan Shows virtual LAN settings
vrrp Shows VRRP
vxlan Shows VXLAN information
watchdog Displays watchdog status
web-auth Shows web authentication configuration
Console#show
Partial Keyword
Lookup
The command “show interfaces ?” will display the following information:
Console#show interfaces ?
brief Brief interface description
counters Interface counters information
history Historical sample of interface counters information
protocol-vlan Protocol-VLAN information
status Shows interface status
switchport Shows interface switchport information
transceiver Interface of transceiver information
transceiver-threshold Interface of transceiver-threshold information
Console#
Show commands which display more than one page of information (e.g., show
running-config) pause and require you to press the [Space] bar to continue
displaying one more page, the [Enter] key to display one more line, or the [a] key to
display the rest of the information without stopping. You can press any other key to
terminate the display.
If you terminate a partial keyword with a question mark, alternatives that match the
initial letters are provided. (Remember not to leave a space between the command
and question mark.) For example “s?” shows all the keywords starting with “s.”
Console#show s?
sflow snmp snmp-server sntp spanning-tree
ssh startup-config system
Console#show s
– 87 –
Chapter 2
Entering Commands
| Using the Command Line Interface
Negating the Effect of
Commands
Using Command
History
Understanding
Command Modes
For many configuration commands you can enter the prefix keyword “no” to cancel
the effect of a command or reset the configuration to the default value. For
example, the logging command will log system messages to a host server. To
disable logging, specify the no logging command. This guide describes the
negation effect for all applicable commands.
The CLI maintains a history of commands that have been entered. You can scroll
back through the history of commands by pressing the up arrow key. Any
command displayed in the history list can be executed again, or first modified and
then executed.
Using the show history command displays a longer list of recently executed
commands.
The command set is divided into Exec and Configuration classes. Exec commands
generally display information on system status or clear statistical counters.
Configuration commands, on the other hand, modify interface parameters or
enable certain switching functions. These classes are further divided into different
modes. Available commands depend on the selected mode. You can always enter a
question mark “?” at the prompt to display a list of the commands available for the
current mode. The command classes and associated modes are displayed in the
following table:
Table 4: General Command Modes
ClassMode
ExecNormal
Privileged
Configuration
* You must be in Privileged Exec mode to access the Global configuration mode.
You must be in Global Configuration mode to access any of the other configuration modes.
Global
*
Access Control List
CFM
Class Map
DHCP
IGMP Profile
Interface
Line
Multiple Spanning Tree
Policy Map
Route Map
Router
Time Range
VLAN Database
Exec Commands When you open a new console session on the switch with the user name and
password “guest,” the system enters the Normal Exec command mode (or guest
mode), displaying the “Console>” command prompt. Only a limited number of the
– 88 –
Chapter 2
| Using the Command Line Interface
Entering Commands
commands are available in this mode. You can access all commands only from the
Privileged Exec command mode (or administrator mode). To access Privilege Exec
mode, open a new console session with the user name and password “admin.” The
system will now display the “Console#” command prompt. You can also enter
Privileged Exec mode from within Normal Exec mode, by entering the enable
command, followed by the privileged level password “super.”
To enter Privileged Exec mode, enter the following user names and passwords:
Username: admin
Password: [admin login password]
CLI session with the AOS5700-54X is opened.
To end the CLI session, enter [Exit].
Console#
Username: guest
Password: [guest login password]
Configuration
Commands
CLI session with the AOS5700-54X is opened.
To end the CLI session, enter [Exit].
Configuration commands are privileged level commands used to modify switch
settings. These commands modify the running configuration only and are not
saved when the switch is rebooted. To store the running configuration in nonvolatile storage, use the copy running-config startup-config command.
The configuration commands are organized into different modes:
◆Global Configuration - These commands modify the system level configuration,
and include commands such as hostname and snmp-server community.
◆Access Control List Configuration - These commands are used for packet
filtering.
◆CFM Configuration - Configures connectivity monitoring using continuity
check messages, fault verification through loopback messages, and fault
isolation by examining end-to-end connections between Provider Edge
devices or between Customer Edge devices.
◆Class Map Configuration - Creates a DiffServ class map for a specified traffic
type.
◆DHCP Configuration - These commands are used to configure the DHCP server.
– 89 –
Chapter 2
| Using the Command Line Interface
Entering Commands
◆IGMP Profile - Sets a profile group and enters IGMP filter profile configuration
mode.
◆Interface Configuration - These commands modify the port configuration such
as speed-duplex and negotiation.
◆Line Configuration - These commands modify the console port and Telnet
configuration, and include command such as parity and databits.
◆Multiple Spanning Tree Configuration - These commands configure settings for
the selected multiple spanning tree instance.
◆Policy Map Configuration - Creates a DiffServ policy map for multiple interfaces.
◆Route Map Configuration - These commands specify the action (next hop or
silently drop) to take when a match is found.
◆Router Configuration - These commands configure global settings for unicast
and multicast routing protocols.
◆Time Range - Sets a time range for use by other functions, such as Access
Control Lists.
◆VLAN Configuration - Includes the command to create VLAN groups.
To enter the Global Configuration mode, enter the command configure in
Privileged Exec mode. The system prompt will change to “Console(config)#” which
gives you access privilege to all Global Configuration commands.
Console#configure
Console(config)#
To enter the other modes, at the configuration prompt type one of the following
commands. Use the exit or end command to return to the Privileged Exec mode.
Table 5: Configuration Command Modes
ModeCommandPromptPage
Access
Control List
access-list ip standard
access-list ip extended
access-list ipv6 standard
access-list ipv6 extended
access-list mac
For example, you can use the following commands to enter interface configuration
mode, and then return to Privileged Exec mode
Console(config)#interface ethernet 1/5
.
.
.
Console(config-if)#exit
Console(config)#
Command Line
Processing
Commands are not case sensitive. You can abbreviate commands and parameters
as long as they contain enough letters to differentiate them from any other
currently available commands or parameters. You can use the Tab key to complete
partial commands, or enter a partial command followed by the “?” character to
display a list of possible matches. You can also use the following editing keystrokes
for command-line processing:
Table 6: Keystroke Commands
KeystrokeFu nction
Ctrl-AShifts cursor to start of command line.
Ctrl-BShifts cursor to the left one character.
Ctrl-CTerminates the current task and displays the command prompt.
Ctrl-EShifts cursor to end of command line.
Ctrl-FShifts cursor to the right one character.
Ctrl-KDeletes all characters from the cursor to the end of the line.
Ctrl-LRepeats current command line on a new line.
Ctrl-NEnters the next command line in the history buffer.
Ctrl-PEnters the last command.
Ctrl-RRepeats current command line on a new line.
Ctrl-U Deletes from the cursor to the beginning of the line.
Ctrl-W Deletes the last word typed.
Esc-BMoves the cursor back one word.
Esc-DDeletes from the cursor to the end of the word.
Esc-FMoves the cursor forward one word.
Delete key or
backspace key
Erases a mistake when entering a command.
– 92 –
CLI Command Groups
Chapter 2
| Using the Command Line Interface
CLI Command Groups
The system commands can be broken down into the functional groups shown
.
below
Table 7: Command Group Index
Command GroupDescriptionPage
General Basic commands for entering privileged access mode,
System Management Display and setting of system information, basic modes of
Simple Network
Management Protocol
Remote MonitoringSupports statistics, history, alarm and event groups203
User Authentication Configures user names and passwords, logon access using
General Security Measures Segregates traffic for clients attached to common data ports;
Access Control ListProvides filtering for IPv4 frames (based on address, protocol,
Interface Configures the connection parameters for all Ethernet ports,
restarting the system, or quitting the CLI
operation, maximum frame size, file management, console
port and telnet settings, system logs, SMTP alerts, and the
system clock,
Activates authentication failure traps; configures community
access strings, and trap receivers
local or remote authentication, management access through
the web server, Telnet server and Secure Shell; as well as port
security, IEEE 802.1X port access control, and restricted access
based on specified IP addresses,
and prevents unauthorized access by configuring valid static
or dynamic addresses, web authentication, MAC address
authentication, filtering DHCP requests and replies, and
discarding invalid ARP responses
TCP/UDP port number or TCP control code), IPv6 frames
(based on address, or non-IP frames (based on MAC address or
Ethernet type)
aggregated links, and VLANs
95
103
181
211
255
335
359
Link AggregationStatically groups multiple ports into a single logical trunk;
Mirror Port Mirrors data to another port for analysis without affecting the
Congestion ControlSets the input/output rate limits, traffic storm thresholds, and
UniDirectional Link
Detection
Address Table Configures the address table for filtering specified addresses,
Spanning Tree Configures Spanning Tree settings for the switch 443
VLANsConfigures VLAN settings, and defines port membership for
Class of Service Sets port priority for untagged frames, selects strict priority or
configures Link Aggregation Control Protocol for port trunks
data passing through or the performance of the monitored
port
thresholds for broadcast and multicast storms which can be
used to trigger configured rate limits or to shut down a port.
Detect and disables unidirectional links429
displays current entries, clears the table, or sets the aging time
VLAN groups
weighted round robin, relative weight for each priority queue,
also sets priority for TCP/UDP traffic types, IP precedence, and
DSCP
389
409
419
437
467
507
– 93 –
Chapter 2
| Using the Command Line Interface
CLI Command Groups
Table 7: Command Group Index (Continued)
Command GroupDescriptionPage
Quality of ServiceConfigures Differentiated Services 527
Multicast FilteringConfigures IGMP multicast filtering, query, profile, and proxy
Link Layer Discovery
Protocol
Domain Name ServiceConfigures DNS services.723
Dynamic Host
Configuration Protocol
Router RedundancyConfigures router redundancy to create primary and backup
IP InterfaceConfigures IP address for the switch interfaces; also
IP RoutingConfigures static unicast routing, policy-based unicast
Multicast RoutingConfigures static multicast routing for IPv4 1013
Data CenterConfigures Database Center Bridging Exchange (DCBX),
DebugDisplays debugging information for all key function
parameters; specifies ports attached to a multicast router
Configures LLDP settings to enable information discovery
about neighbor devices
Configures DHCP client, relay and server functions733
routers
configures ARP parameters
routing for BGP, and dynamic unicast routing
Congestion Notification (CN), Enhanced Transmission
Selection (ETS), Priority-Based Flow Control (PFC), and
OpenFlow
These commands are not described in this manual
Please refer to the prompt messages included in the CLI interface.
581
653
791
741
801
545
The access mode shown in the following tables is indicated by these abbreviations:
ACL (Access Control List Configuration)
CFM (Connectivity Fault Management Configuration)
CM (Class Map Configuration)
DC (DHCP Server Configuration)
GC (Global Configuration)
IC (Interface Configuration)
IPC (IGMP Profile Configuration)
LC (Line Configuration)
MST (Multiple Spanning Tree)
NE (Normal Exec)
PE (Privileged Exec)
PM (Policy Map Configuration)
RC (Router Configuration)
RM (Route Map Configuration)
VC (VLAN Database Configuration)
– 94 –
3General Commands
The general commands are used to control the command access mode,
configuration mode, and other basic functions.
Table 8: General Comm ands
CommandFunctionMode
promptCustomizes the CLI promptGC
reloadRestarts the system at a specified time, after a specified delay, or at a
periodic interval
enable Activates privileged modeNE
quitExits a CLI session NE, PE
show historyShows the command history buffer NE, PE
configureActivates global configuration mode PE
disableReturns to normal mode from privileged mode PE
reloadRestarts the system immediatelyPE
show reloadDisplays the current reload settings, and the time at which next
scheduled reload will take place
endReturns to Privileged Exec mode any config.
exitReturns to the previous configuration mode, or exits the CLI any mode
help Shows how to use help any mode
? Shows options for command completion (context sensitive)any mode
GC
PE
mode
prompt This command customizes the CLI prompt. Use the no form to restore the default
prompt.
Syntax
prompt string
no prompt
string - Any alphanumeric string to use for the CLI prompt.
(Maximum length: 255 characters)
Default Setting
Console
– 95 –
Chapter 3
| General Commands
Command Mode
Global Configuration
Example
Console(config)#prompt RD2
RD2(config)#
reload
(Global Configuration)
This command restarts the system at a specified time, after a specified delay, or at a
periodic interval. You can reboot the system immediately, or you can configure the
switch to reset after a specified amount of time. Use the cancel option to remove a
configured setting.
Syntax
reload {at hour minute [{month day | day month} [year]] |
The ! command repeats commands from the Execution command history buffer
when you are in Normal Exec or Privileged Exec Mode, and commands from the
Configuration command history buffer when you are in any of the configuration
modes. In this example, the !2 command repeats the second command in the
Execution history buffer (config).
Console#!2
Console#config
Console(config)#
configure This command activates Global Configuration mode. You must enter this mode to
modify any settings on the switch. You must also enter Global Configuration mode
prior to enabling some of the other configuration modes, such as Interface
Configuration, Line Configuration, and VLAN Database Configuration. See
“Understanding Command Modes” on page 88.
Default Setting
None
Command Mode
Privileged Exec
Example
Console#configure
Console(config)#
Related Commands
end (101)
– 99 –
Chapter 3
| General Commands
disable This command returns to Normal Exec mode from privileged mode. In normal
access mode, you can only display basic information on the switch's configuration
or Ethernet statistics. To gain access to all commands, you must use the privileged
mode. See “Understanding Command Modes” on page 88.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
The “>” character is appended to the end of the prompt to indicate that the system
is in normal access mode.
Example
Console#disable
Console>
Related Commands
enable (97)
reload (Privileged Exec) This command restarts the system.
Note:
When the system is restarted, it will always run the Power-On Self-Test. It will
also retain all configuration information stored in non-volatile memory by the copy
running-config startup-config command.
Default Setting
None
Command Mode
Privileged Exec
Command Usage
This command resets the entire system.
Example
This example shows how to reset the switch:
Console#reload
System will be restarted, continue <y/n>? y
– 100 –
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.