ECS4620 Series
28/52-Port Layer 3
Stackable GE Switch
Software Release v1.2.2.26
CLI Reference Guide
www.edge-core.com
Page 2
CLI Reference Guide
ECS4620-28T Stackable GE Switch
Layer 3 Stackable Gigabit Ethernet Switch
with 24 10/100/1000BASE-T (RJ-45) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-28P Stackable GE PoE Switch
Layer 3 Stackable Gigabit Ethernet PoE Switch
with 24 10/100/1000BASE-T (RJ-45) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-28F Stackable GE Fiber Switch
Layer 3 Stackable Gigabit Ethernet Fiber Switch
with 22 SFP Ports,
2 10/100/1000BASE-T (RJ-45/SFP) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-28T-DC Stackable GE Switch
Layer 3 Stackable Gigabit Ethernet Switch
with 24 10/100/1000BASE-T (RJ-45) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-52T Stackable GE Switch
Layer 3 Stackable Gigabit Ethernet Switch
with 48 10/100/1000BASE-T (RJ-45) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-52P Stackable GE PoE Switch
Layer 3 Stackable Gigabit Ethernet PoE Switch
with 48 10/100/1000BASE-T (RJ-45) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-52P-2AC Stackable GE PoE Switch
Layer 3 Stackable Gigabit Ethernet PoE Switch
with 48 10/100/1000BASE-T (RJ-45) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
(Dual AC/DC power inputs)
ECS4620-28F-DC Stackable GE Fiber Switch
Layer 3 Stackable Gigabit Ethernet Fiber Switch
with 22 SFP Ports,
2 10/100/1000BASE-T (RJ-45/SFP) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
ECS4620-28F-2AC Stackable GE Fiber Switch
Layer 3 Stackable Gigabit Ethernet Fiber Switch
with 22 SFP Ports,
2 10/100/1000BASE-T (RJ-45/SFP) Ports,
2 10-Gigabit SFP+ Ports,
and Optional Module with 2 10-Gigabit SFP+ Ports
(Dual AC/DC power inputs)
E022019-CS-R06
Page 3
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 or information about the web browser
management interface refer to the Web Management Guide.
The guide includes these sections:
◆Section I “Getting Started” — Includes information on initial configuration.
◆Section II “Command Line Interface” — Includes all management options
available through the CLI.
◆Section III “Ap pe ndi ces” — 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
For information on how to install the switch, see the following guide:
Installation Guide
For all safety information and regulatory statements, see the following documents:
Quick Start Guide
Safety and Regulatory Information
– 3 –
Page 4
How to Use This Guide
Conventions The following conventions are used throughout this guide to show 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.
Documentation
Notice
This documentation is provided for general information purposes only. If any
product feature details in this documentation conflict with the product datasheet,
refer to the datasheet for the latest information.
Revision History This section summarizes the changes in each revision of this guide.
February 2019 Revision
This is the sixth version of this guide. This guide is valid for software release
v1.2.2.26. It contains the following changes:
◆Added documentation notice.
November 2016 Revision
This is the fifth version of this guide. This guide is valid for software release
v1.2.2.26. It contains the following changes:
◆Added information for ECS4620-52T-2AC and ECS4620-52P-2AC.
◆Added "show process cpu guard" on page 130.
◆Added SFTP option to "copy" on page 142.
◆Updated syntax for "snmp-server user" on page 215.
◆Added "show authorization" on page 267.
◆Added "telnet (client)" on page 274.
◆Updated Command Usage for "dot1x default" on page 285.
◆Updated syntax for "ip dhcp snooping information option circuit-id" on
page 347.
◆Updated syntax for "clear ip dhcp snooping binding" on page 349.
◆Updated Command Usage for "ip source-guard max-binding" on page 365.
– 4 –
Page 5
How to Use This Guide
◆Added Command Usage for "show interfaces brief" on page 433.
◆Updated syntax for "show port monitor" on page 475.
◆Updated Command Usage for "spanning-tree bpdu-filter" on page 536.
◆Updated Command Usage for "spanning-tree bpdu-guard" on page 537.
◆Added Command Usage to "spanning-tree spanning-disabled" on page 547.
◆Updated syntax for "switchport allowed vlan" on page 595.
◆Added "switchport dot1q-tunnel priority map" on page 604.
◆Updated syntax for "show l2protocol-tunnel" on page 613.
◆Updated syntax for "show protocol-vlan protocol-group" on page 618.
◆Updated syntax for "class-map" on page 646.
◆Updated syntax for "show policy-map interface" on page 663.
◆Added "ipv6 mld snooping proxy-reporting" on page 703.
◆Added "ipv6 mld snooping unsolicited-report-interval" on page 708.
◆Updated syntax for "ipv6 mld snooping vlan immediate-leave" on page 709.
◆Updated syntax for "show ipv6 mld snooping" on page 712.
◆Updated syntax for "show ipv6 mld snooping group source-list" on page 713.
◆Added "show ipv6 mld snooping statistics" on page 715.
◆Updated Command Usage for "ipv6 nd reachable-time" on page 949.
◆Updated syntax for "vrrp authentication" on page 966, "vrrp ip" on page 966,
"vrrp preempt" on page 967, "vrrp priority" on page 968, and "vrrp timers
advertise" on page 969.
◆Updated syntax for "ipv6 route" on page 981.
◆Updated syntax for "show ipv6 route" on page 983.
◆Updated syntax for "redistribute" on page 1011.
◆Updated syntax for "redistribute" on page 1053.
– 5 –
Page 6
How to Use This Guide
December 2014 Revision
This is the fourth version of this guide. This guide is valid for software release
v1.2.2.0. It contains the following changes:
◆Added information for ECS4620-28F-DC.
July 2014 Revision
This is the third version of this guide. This guide is valid for software release v1.2.2.0.
It contains the following changes:
◆Added information for ECS4620-28T-DC.
◆Updated usage information for the command "mac-learning" on page 312.
◆Updated syntax and usage information for the command "ip source-guard
binding" on page 362.
◆Updated usage information for the command "ip source-guard mode" on
page 366.
◆Added the command "loopback-detection action" on page 502.
April 2014 Revision
This is the second version of this guide. This guide is valid for software release
v1.2.1.3. It contains the following changes:
◆Added information for ECS4620-28F, ECS4620-28T, and ECS4620-28P.
◆Extended configurable VLAN range from 1-4093 to 1-4094.
◆Added "Stack Operations" on page 69.
◆ Added the command "show process cpu task" on page 130.
◆Added "Stacking" on page 198.
◆Updated syntax for "snmp-server enable traps" on page 208.
◆Added the commands "snmp-server enable port-traps mac-notification" on
page 212 and "show snmp-server enable port-traps" on page 212.
◆Updated command usage section for the command "pppoe
intermediate-agent port-format-type" on page 305.
◆Added the command "pppoe intermediate-agent port-format-type remote-id-
delimiter" on page 306.
◆Added the command "mac-learning" on page 312.
– 6 –
Page 7
How to Use This Guide
◆Updated command usage section for the command "port security" on
page 313.
◆Added the command "port security mac-address-as-permanent" on page 315.
◆Added the commands "ip dhcp snooping information option encode no-
subtype" on page 342, "ip dhcp snooping information option remote-id" on
page 343, and "ip dhcp snooping information option tr101 board-id" on
page 344.
◆Added the commands "ipv6 dhcp snooping option remote-id" on page 355,
and "ipv6 dhcp snooping option remote-id policy" on page 356.
◆Updated syntax for the command "ip source-guard binding" on page 362 and
"ip source-guard max-binding" on page 365, and "show ip source-guard
binding" on page 368.
◆Added the commands "ip source-guard mode" on page 366 and "clear ip
source-guard binding blocked" on page 367.
◆Updated syntax for the command "media-type" on page 429.
◆Updated range for the commands "transceiver-threshold current" on page 442,
"transceiver-threshold rx-power" on page 443, "transceiver-threshold
temperature" on page 444, "transceiver-threshold tx-power" on page 445, and
"transceiver-threshold voltage" on page 446.
◆Added the command "show interfaces transceiver-threshold" on page 448.
◆Updated command usage section for the command "power inline maximum
allocation" on page 468.
◆Updated syntax for the command "auto-traffic-control control-release" on
page 495.
◆Added the command "loopback-detection action" on page 502.
◆Removed the command “loopback-detection mode.”
◆Added the command "loopback detection trap" on page 504.
◆Added the commands "udld detection-interval" on page 507, "udld recovery"
on page 509, and "udld recovery-interval" on page 509.
◆Updated range for the command "mac-address-table aging-time" on page 515.
◆Added the commands "spanning-tree tc-prop" on page 531, "spanning-tree
tc-prop-stop" on page 547, and "show spanning-tree tc-prop" on page 552.
◆Updated syntax for the command "mac-vlan" on page 622.
– 7 –
Page 8
How to Use This Guide
◆Updated syntax for the commands "show qos map cos-dscp" on page 641,
"show qos map dscp-mutation" on page 641, and "show qos map phb-queue"
on page 642.
◆Added the commands "clear ip igmp snooping groups dynamic" on page 683,
and "clear ip igmp snooping statistics" on page 683.
◆Updated command usage section for the command "ip igmp authentication"
on page 693.
◆Added the commands "clear ipv6 mld snooping groups dynamic" on page 711
and "clear ipv6 mld snooping statistics" on page 712.
◆Updated range for the command "mvr priority" on page 730.
◆Added the commands "clear mrv groups dynamic" on page 739 and "clear mrv
statistics" on page 739.
◆Updated syntax for the command "show mvr members" on page 743 and
"show mvr statistics" on page 745.
◆Added the command "mvr6 priority" on page 751.
◆Added the command "clear efm oam event-log" on page 866.
◆Updated syntax for the commands "ip route" on page 976 and "show ip route"
on page 978.
◆Added BGP to the parameter list for the RIP command "redistribute" on
page 991.
◆Added BGP to the parameter list for the OSPFv2 command "redistribute" on
page 1011.
◆Added the command "area authentication" on page 1014.
◆Added the command "neighbor password" on page 1126.
December 2013 Revision
This is the first version of this guide. This guide is valid for software release v1.1.1.1.
– 8 –
Page 9
Contents
How to Use This Guide 3
Contents 9
Figures 53
Tables 55
Section IGetting Started 63
1 Initial Switch Configuration 65
Connecting to the Switch 65
Configuration Options 65
Connecting to the Console Port 66
Logging Onto the Command Line Interface 67
Setting Passwords 67
Remote Connections 68
Stack Operations 69
Selecting the Stack Master 69
Selecting the Backup Unit 70
Recovering from Stack Failure or Topology Change 70
Renumbering the Stack 71
Ensuring Consistent Code is Used Across the Stack 71
Configuring the Switch for Remote Management 72
Using the Network Interface 72
Setting an IP Address 72
Enabling SNMP Management Access 78
Managing System Files 80
Upgrading the Operation Code 81
Saving or Restoring Configuration Settings 81
Automatic Installation of Operation Code and Configuration Settings 83
– 9 –
Page 10
Contents
Downloading Operation Code from a File Server 83
Specifying a DHCP Client Identifier 86
Downloading a Configuration File and Other Parameters from a DHCP Server 87
Table 32: show ip mroute - display description 1177
Table 33: show ip mroute - display description 1180
Table 34: Static Multicast Routing Commands 1181
Table 35: IPv4 and IPv6 PIM Commands 1183
Table 36: PIM-DM and PIM-SM Multicast Routing Commands 1183
Table 37: show ip pim neighbor - display description 1192
Table 38: show ip pim bsr-router - display description 1204
Table 39: show ip pim rp mapping - display description 1205
Table 40: show ip pim rp-hash - display description 1206
Table 41: PIM-DM and PIM-SM Multicast Routing Commands 1206
Table 42: show ipv6 pim neighbor - display description 1215
Table 43: show ip pim bsr-router - display description 1227
Table 44: show ip pim rp mapping - display description 1228
Table 45: show ip pim rp-hash - display description 1229
– 61 –
Page 62
Tabl es
Table 46: Troubleshooting Chart 1233
– 62 –
Page 63
Section I
Getting Started
This section describes how to configure the switch for management access through
the web interface or SNMP.
This section includes these chapters:
◆"Initial Switch Configuration" on page 65
– 63 –
Page 64
Section I
| Getting Started
– 64 –
Page 65
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 72.
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 11, Mozilla Firefox 49, or Google Chrome 54 or more recent
versions. 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
◆Control port access through IEEE 802.1X security or static address filtering
– 65 –
Page 66
Chapter 1
Connecting to the Switch
| Initial Switch Configuration
◆Filter packets using Access Control Lists (ACLs)
◆Configure up to 4094 IEEE 802.1Q VLANs
◆Enable GVRP automatic VLAN registration
◆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 16)
◆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
◆Configure any stack unit through the same IP address
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.
Note:
When configuring a stack, connect to the console port on the Master unit.
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.
– 66 –
Page 67
Chapter 1
■
Set flow control to none.
■
Set the emulation mode to VT100.
■
When using HyperTerminal, select Terminal keys, not Windows keys.
| Initial Switch Configuration
Connecting to the Switch
4. Power on the switch.
After the system completes the boot cycle, the logon screen appears.
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.
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>.
– 67 –
Page 68
Chapter 1
Connecting to the Switch
| Initial Switch Configuration
4. Type “username admin password 0 password,” for the Privileged Exec level,
where password is your new password. Press <Enter>.
Username: admin
Password:
CLI session with the ECS4620-28T* is opened.
To end the CLI session, enter [Exit].
* This manual covers all switches in the ECS4620 series. Other than the difference
in port types, and support for PoE (ECS4620-28P/52P/52P-2AC), there are no
significant differences. Therefore nearly all of the screen display examples are
based on the ECS4620-28T.
Remote Connections Prior to accessing the switch’s onboard agent via a network connection, you must
first configure it with a valid IPv4 or IPv6 address, subnet mask, and default gateway
using a console connection, BOOTP or DHCP protocol. To configure this device as
the default gateway, use the ip default-gateway command.
An IPv4 address for the switch 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 72.
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 6, Mozilla Firefox 4, or Google Chrome 29, or more
recent versions), or from a network computer using SNMP network management
software.
Note:
This switch supports eight Telnet sessions or SSH sessions.
Note:
Any VLAN group can be assigned an IP interface address (page 72) for
managing the switch. Also, note that the Master unit does not have to include an
active port member in the VLAN interface used for management access.
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.
– 68 –
Page 69
Stack Operations
Chapter 1
| Initial Switch Configuration
Stack Operations
Up to eight switches can be stacked together as described in the Installation Guide.
One unit in the stack acts as the Master for configuration tasks and firmware
upgrade. All of the other units function in Slave mode, but can automatically take
over management of the stack if the Master unit fails.
To configure any unit in the stack, first verify the unit number from the front panel
indicator on the switch, and then select the appropriate unit number from the web
or console management interface.
Selecting the
Stack Master
Note the following points about unit numbering:
◆When the stack is initially powered on, the Master unit is selected based on the
following rules:
■
If the stack master button has been enabled with the switch master button
command on only one unit in the stack, that unit will serve as the stack
Master.
■
If the stack master button has been enabled on more than one unit, the
system will select the unit with the lowest MAC address as the stack Master
from those with the stack master button enabled.
■
If the stack master button is not enabled on any unit, the system will select
the unit with the lowest MAC address as the stack Master.
◆When the stack is initially powered on, the Master unit is designated as unit 1
for a ring topology. For a line topology, the stack is simply numbered from top
to bottom, with the first unit in the stack designated at unit 1. This unit
identification number appears on the Stack Unit ID LED on the front panel of
the switch. Any unit in the stack can be selected on the front panel graphic of
the web interface (from the Unit scroll-down list), or from the CLI (as specified
by the “unit” parameter for applicable commands).
◆If the Master unit fails and another unit takes over control of the stack, the unit
numbering will not change.
◆If a unit in the stack fails or is removed from the stack, the unit numbers will not
change. This means that when you replace a unit in the stack, the original
configuration for the failed unit will be restored to the replacement unit.
◆If a unit is removed from the stack and later reattached to the stack, it will retain
the original unit number obtained during stacking.
◆If a unit is removed from the stack, and powered up as a stand-alone unit, it will
also retain the original unit number obtained during stacking.
– 69 –
Page 70
Chapter 1
Stack Operations
| Initial Switch Configuration
Selecting the
Backup Unit
Recovering from
Stack Failure or
Topology Change
Once the Master unit finishes booting up, it continues to synchronize configuration
information to all of the Slave units in the stack. If the Master unit fails or is powered
off, a new master unit will be selected based on the election rules described in the
preceding section. The backup unit elected to serve as the new stack Master will
take control of the stack without any loss of configuration settings. To ensure a
logical fail over to the next unit down in the stack, place the Slave unit with the
lowest MAC address directly beneath the Master unit in the stack.
When a link or unit in the stack fails, a trap message is sent and a failure event is
logged. The stack will be rebooted after any system failure or topology change. It
takes two to three minutes to for the stack to reboot. If the Master unit fails, the
backup unit will take over operations as the new Master unit, reboot the stack, and
then select another backup unit after the stack finishes rebooting. Also note that
powering down a unit or inserting a new unit in the stack will cause the stack to
reboot. If a unit is removed from the stack (due to a power down or failure) or a new
unit added to the stack, the original unit IDs are not affected after rebooting, and a
new unit is assigned the lowest available unit ID.
Broken Link for Line and Wrap-around Topologies
All units in the stack must be connected via stacking cable. You can connect the
units in a simple cascade configuration from the top to the bottom unit. Using this
kind of line topology, if any link or unit in the stack fails, the stack will be broken in
two.
When the stack fails, a Master unit is selected from the two stack segments, either
the unit with the Master button enabled, or the unit with the lowest MAC address if
the Master button is not enabled on any unit. The stack reboots and resumes
operations. However, note that the IP address will be the same for any common
VLANs (with active port connections) that appear in both of the new stack
segments. To resolve the conflicting IP addresses, you should manually replace the
failed link or unit as soon as possible. If you are using a wrap-around stack topology,
a single point of failure in the stack will not cause the stack to fail. It would take two
or more points of failure to break the stack apart.
Note:
If a stack breaks apart, the IP address will be the same for any common
VLANs (with active port connections) that appear in both stack segments.
Resilient IP Interface for Management Access
The stack functions as one integral system for management and configuration
purposes. You can therefore manage the stack through any IP interface configured
on the stack. The Master unit does not even have to include an active port member
in the VLAN interface used for management access. However, if the unit to which
you normally connect for management access fails, and there are no active port
members on the other units within this VLAN interface, then this IP address will no
longer be available. To retain a constant IP address for management access across
– 70 –
Page 71
Chapter 1
| Initial Switch Configuration
Stack Operations
failover events, you should include port members on several units within the
primary VLAN used for stack management.
Resilient Configuration
If a unit in the stack fails, the unit numbers will not change. This means that when
you replace a unit in the stack, the original configuration for the failed unit will be
restored to the replacement unit. This applies to both the Master and Slave units.
Renumbering
the Stack
Ensuring Consistent
Code is Used Across
the Stack
The startup configuration file maps configuration settings to each switch in the
stack based on the unit identification number. If the units are no longer numbered
sequentially after several topology changes or failures, you can reset the unit
numbers using the System > Stacking (Renumber) menu in the web interface or the
switch all renumber command in the CLI. Just remember to save the new
configuration settings to a startup configuration file prior to powering off the stack
Master.
Consistent Runtime Code in Each Switch – The main board runtime firmware
version for each unit in the stack must be the same as the Master unit’s runtime
firmware. After Auto-ID assignment is completed, the Master unit checks the image
versions for consistency. If the firmware versions (i.e., runtime code) configured for
bootup on any slave units are not the same as those on the Master unit, the stack
will operate in Special Stacking Mode in which all backup units are disabled as
described below:
◆The master unit starts normal operation mode in standalone mode.
◆The master unit can see all units in the stack and maintain stack topology.
◆None of the other units can function (all ports will be disabled).
◆All user-initiated commands to configure the non-functioning units are
dropped. The master unit, however, will be able to communicate the following
information to the non-functioning units:
■
Image downloads
■
Stack topology information
■
System configuration information already stored on the master.
In Special Stacking mode, the master unit displays warning messages whenever
you log into the system through the CLI that inform you that an image download is
required.
You can use the CLI, web or SNMP to download the runtime image from an FTP or
TFTP server to the master unit. The master unit stores the image as its “Next boot
– 71 –
Page 72
Chapter 1
Configuring the Switch for Remote Management
| Initial Switch Configuration
image” and downloads the image to those backup units that are running a different
image version.
Configuring the Switch for Remote Management
Using the Network
Interface
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-28/52).
Setting an IP Address You must establish IP address information for a stand-alone switch or a stack 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. To configure this
device as the default gateway, use the ip default-gateway command.
◆Dynamic — The switch can send IPv4 configuration requests to BOOTP or
DHCP address allocation servers on the network, or 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 77.
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 73.
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 VLAN 1 is obtained via DHCP by default.
– 72 –
Page 73
Chapter 1
Configuring the Switch for Remote Management
| Initial Switch Configuration
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>.
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 922.
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.
– 73 –
Page 74
Chapter 1
| Initial Switch Configuration
Configuring the Switch for Remote Management
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::1:ff11:6700
ff02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
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.
– 74 –
Page 75
Chapter 1
| Initial Switch Configuration
Configuring the Switch for Remote Management
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(config)#interface vlan 1
Console(config-if)#ipv6 address 2001:DB8:2222:7272::/64
Console(config-if)#exit
Console(config)#ipv6 default-gateway 2001:DB8:2222:7272::254
Console(config)end
Console#show ipv6 interface
VLAN 1 is up
IPv6 is enabled.
Link-local address:
fe80::200:e8ff:fe94:4000%1/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:ff94:4000
ff02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
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#show ipv6 route
Codes: C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
* - candidate default
S* ::/0 [1/0] via 2001:db8:2222:7272::254, VLAN1
C 2001:db8:2222:7272::/64, VLAN1
C fe80::/64, VLAN1
Console#
– 75 –
Page 76
Chapter 1
Configuring the Switch for Remote Management
| Initial Switch Configuration
Dynamic Configuration
Obtaining an IPv4 Address
If you select the “bootp” or “dhcp” option, the system will immediately start
broadcasting service requests. IP will be enabled but will not function until a
BOOTP or DHCP reply has been received. Requests are broadcast every few minutes
using exponential backoff until IP configuration information is obtained from a
BOOTP or DHCP server. BOOTP and DHCP values can include the IP address, subnet
mask, and default gateway. If the DHCP/BOOTP 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 BOOTP or 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 “bootp” or “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 BOOTP or 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 one of the following
commands:
■
To obtain IP settings via DHCP, type “ip address dhcp” and press <Enter>.
■
To obtain IP settings via BOOTP, type “ip address bootp” and press <Enter>.
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>.
– 76 –
Page 77
Chapter 1
| Initial Switch Configuration
Configuring the Switch for Remote Management
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
DHCP Client Vendor Class ID (text): ECS4620-28T
DHCP Inform is disabled
DHCP relay server: 0.0.0.0
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::7272:cfff:fe83:3466%1/64
Global unicast address(es):
(None)
Joined group address(es):
ff02::1:ff94:4000
ff02::1:ff00:0
ff02::1
IPv6 link MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3.
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#
– 77 –
Page 78
Chapter 1
Enabling SNMP Management Access
| Initial Switch Configuration
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.
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.
To configure a community string, complete the following steps:
1. From the Privileged Exec level global configuration mode prompt, type “snmp-
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.)
2. To remove an existing string, simply type “no snmp-server community string,”
where “string” is the community access string to remove. Press <Enter>.
– 78 –
Page 79
Chapter 1
Console(config)#snmp-server community admin rw
Console(config)#snmp-server community private
Console(config)#
Note:
If you do not intend to support access to SNMP version 1 and 2c clients, we
| Initial Switch Configuration
Enabling SNMP Management Access
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.
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
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 read mib-2 write 802.1d
Console(config)#snmp-server user steve group r&d v3 auth md5 greenpeace priv
des56 einstien
Console(config)#
– 79 –
Page 80
Chapter 1
Managing System Files
| Initial Switch Configuration
For a more detailed explanation on how to configure the switch for access from
SNMP v3 clients, refer to “SNMP Commands” on page 203 or to the 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
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 81 for more information.
◆Operation Code — System software that is executed after boot-up, also
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.
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 128 Mbytes 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 running-
– 80 –
Page 81
Chapter 1
| Initial Switch Configuration
Managing System Files
config, 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:
m360.bix OpCode Y 2013-02-25 15:41:04 25812529
m355.bix OpCode N 2012-12-04 13:23:59 25783857
Factory_Default_Config.cfg Config N 2012-12-04 13:18:37 455
startup1.cfg Config Y 2013-03-21 05:39:15 3463
---------------------------------------------------------------------------- Free space for compressed user config files:1593241600
Console#
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
– 81 –
Page 82
Chapter 1
| Initial Switch Configuration
Managing System Files
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>.
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#
– 82 –
Page 83
Chapter 1
Automatic Installation of Operation Code and Configuration Settings
| Initial Switch Configuration
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 ECS4620-28T.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 ECS4620-28T.BIX from
the server even though ECS4620-28T.bix was requested). However, keep in mind
that the file systems of many operating systems such as Unix and most Unixlike systems (FreeBSD, NetBSD, OpenBSD, and most Linux distributions, etc.) are
case-sensitive, meaning that two files in the same directory, ecs4620-28t.bix and
ECS4620-28T.BIX are considered to be unique files. Thus, if the upgrade file is
stored as ECS4620-28T.BIX (or even Ecs4620-28t.bix) on a case-sensitive server,
then the switch (requesting ECS4620-28T.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 case-sensitive Unix-like operating
systems is Mac OS X, which by default is case-insensitive. Please check the
documentation for your server’s operating system if you are unsure of its file
system’s behavior.
– 83 –
Page 84
Chapter 1
Automatic Installation of Operation Code and Configuration Settings
| Initial Switch Configuration
◆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.
If no user name nor password is required for the connection, then the “@”
character cannot be used in the path name.
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 ECS4620-28T.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 : ECS4620-28T.bix
Console#
– 85 –
Page 86
Chapter 1
| Initial Switch Configuration
Automatic Installation of Operation Code and Configuration Settings
The following shows an example of the upgrade process.
Console#dir
File Name Type Startup Modify Time Size(bytes)
-------------------------- -------------- ------- ------------------- ------ Unit 1:
ECS4620-28T_V1.2.2.26.bix OpCode Y 2000-12-31 00:19:13 18601012
Factory_Default_Config.cfg Config N 1999-12-31 00:00:34 455
startup1.cfg Config Y 2001-01-01 00:03:16 2055
--------------------------------------------------------------------------- Free space for compressed user config files: 46497792
Total space: 128 MB
...
Press ENTER to start session
Automatic Upgrade is looking for a new image
New image detected: current version V1.2.2.26; new version V1.2.2.27
Image upgrade in progress
Downloading new image
Flash programming started
Flash programming completed
Success
The switch will now restart
...
Press ENTER to start session
Automatic Upgrade is looking for a new image
No new image detected
User Access Verification
Specifying a DHCP
Client Identifier
Username: admin
Password:
CLI session with the ECS4100-26TX is opened.
To end the CLI session, enter [Exit].
Console#dir
File Name Type Startup Modify Time Size(bytes)
-------------------------- -------------- ------- ------------------- ------ Unit 1:
File Name Type Startup Modify Time Size(bytes)
-------------------------- -------------- ------- ------------------- ------ Unit 1:
ECS4620-28T_V1.2.2.27.bix OpCode Y 2000-12-31 00:19:13 18601012
Factory_Default_Config.cfg Config N 1999-12-31 00:00:34 455
startup1.cfg Config Y 2001-01-01 00:03:16 2055
--------------------------------------------------------------------------- Free space for compressed user config files: 46497792
Total space: 128 MB
Console#
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.
– 86 –
Page 87
Chapter 1
Downloading a Configuration File and Other Parameters from a DHCP Server
| Initial Switch Configuration
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.
Downloading a Configuration File and Other Parameters from a DHCP Server
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, as well as other parameters. 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.
◆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.
– 87 –
Page 88
Chapter 1
| Initial Switch Configuration
Downloading a Configuration File and Other Parameters from a DHCP Server
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 1: 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
Statement
◆By default, DHCP option 66/67 parameters are not carried in a DHCP server
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 2: 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 = "ecs4620-28t.cfg";
option tftp-server-name "192.168.255.101";
option bootfile-name "test";
}
Note:
Setting the System Clock
Chapter 1
| Initial Switch Configuration
Setting the System Clock
Use “ecs4620-28t.cfg” for the vendor-class-identifier in the dhcpd.conf file.
Setting the Time
Manually
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),
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.
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)#
– 89 –
Page 90
Chapter 1
| Initial Switch Configuration
Setting the System Clock
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#
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 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#
– 91 –
Page 92
Chapter 1
Setting the System Clock
| Initial Switch Configuration
– 92 –
Page 93
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 95
◆“General Commands” on page 109
◆“System Management Commands” on page 117
◆“SNMP Commands” on page 203
◆“Remote Monitoring Commands” on page 229
◆“Flow Sampling Commands” on page 237
◆“Authentication Commands” on page 243
◆“General Security Measures” on page 311
◆“Access Control Lists” on page 395
◆“Interface Commands” on page 423
◆“Link Aggregation Commands” on page 453
◆“Power over Ethernet Commands” on page 467
◆“Port Mirroring Commands” on page 473
◆“Congestion Control Commands” on page 483
◆“Loopback Detection Commands” on page 501
◆“UniDirectional Link Detection Commands” on page 507
– 93 –
Page 94
Section II
| Command Line Interface
◆“Address Table Commands” on page 515
◆“Spanning Tree Commands” on page 523
◆“ERPS Commands” on page 553
◆“VLAN Commands” on page 585
◆“Class of Service Commands” on page 631
◆“Quality of Service Commands” on page 645
◆“Multicast Filtering Commands” on page 665
◆“LLDP Commands” on page 793
◆“CFM Commands” on page 819
◆“OAM Commands” on page 861
◆“Domain Name Service Commands” on page 873
◆“DHCP Commands” on page 883
◆“IP Interface Commands” on page 907
◆“VRRP Commands” on page 965
◆“IP Routing Commands” on page 975
◆“Multicast Routing Commands” on page 1175
– 94 –
Page 95
2Using the Command Line
Interface
This chapter describes how to use the Command Line Interface (CLI).
Note: You can only access the console interface through the Master unit in the
stack.
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 ECS4620-28T is opened.
To end the CLI session, enter [Exit].
Console#
– 95 –
Page 96
Chapter 2
Accessing the CLI
| Using the Command Line Interface
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
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 or host
name 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 ECS4620-28T is opened.
To end the CLI session, enter [Exit].
Vty-0#
– 96 –
Page 97
Entering Commands
Chapter 2
Note:
You can open up to eight sessions to the device via Telnet or SSH.
| 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
conficonfiguration, enter the following commands. The default password
“super” is used to change from Normal Exec to Privileged Exec mode:
◆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.”
– 97 –
Page 98
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 system ?” displays a list of
possible show commands:
Console#show ?
access-group Access groups
access-list Access lists
accounting Uses the specified accounting list
arp Information of ARP cache
authorization Enables EXEC accounting
auto-traffic-control Auto traffic control information
banner Banner info
bridge-ext Bridge extension information
cable-diagnostics Shows the information of cable diagnostics
calendar Date and time information
class-map Displays class maps
cluster Display cluster
collision-mac-address-table Show collision mac address
debug State of each debugging option
discard Discard packet
dns DNS information
dos-protection Shows the system dos-protection summary
information
dot1q-tunnel dot1q-tunnel
dot1x 802.1X content
efm Ethernet First Mile feature
erps Displays ERPS configuration
ethernet Shows Metro Ethernet information
garp GARP properties
gvrp GVRP interface information
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
line TTY line information
lldp LLDP
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
mac-vlan MAC-based VLAN information
management Shows management information
memory Memory utilization
mvr multicast vlan registration
mvr6 IPv6 Multicast VLAN registration
network-access Shows the entries of the secure port.
nlm Show notification log
ntp Network Time Protocol configuration
policy-map Displays policy maps
– 98 –
Page 99
Chapter 2
| Using the Command Line Interface
Entering Commands
port Port characteristics
port-channel Port channel information
power Shows power
power-save Shows the power saving information
pppoe Displays PPPoE configuration
privilege Shows current privilege level
process Device process
protocol-vlan Protocol-VLAN information
public-key Public key information
qos Quality of Service
queue Priority queue information
radius-server RADIUS server information
reload Shows the reload settings
rmon Remote monitoring information
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
subnet-vlan IP subnet-based VLAN information
switch stacking switch
system System information
tacacs-server TACACS server information
tech-support Technical information
time-range Time range
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
vlan-translation VLAN translation information
voice Shows the voice VLAN information
vrrp Shows VRRP
watchdog Displays watchdog status
web-auth Shows web authentication configuration
Console#show
The command “show interfaces ?” will display the following information:
Console#show interfaces ?
brief Shows brief interface description
counters 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
– 99 –
Page 100
Chapter 2
Entering Commands
| Using the Command Line Interface
display the rest of the information without stopping. You can press any other key to
terminate the display.
Partial Keyword
Lookup
Negating the Effect of
Commands
Using Command
History
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 subnet-vlan switch system
Console#show s
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.
Understanding
Command Modes
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:
– 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.