ADMINISTRATION
GUIDE
Cisco 500 Series Stackable Managed Switch
Administration Guide Release 1.3.5
Contents
Table of Contents
Chapter 1: Getting Started 1
Starting the Web-based Configuration Utility 1
Quick Start Device Configuration 5
Interface Naming Conventions 6
Differences Between Sx500, SG500X, ESW2-550X and the SG500XG Devices<Sx500> 7
Window Navigation 8
Chapter 2: Status and Statistics 12
System Summary <print only> 12
Viewing Ethernet Interfaces 13
Viewing Etherlike Statistics 14
<Sx300-500>Viewing GVRP Statistics 15
Viewing 802.1X EAP Statistics 16
<Sx300-500>Viewing TCAM Utilization[ 17
Health<print only> 19
Managing RMON 19
View Log<print only> 27
Chapter 3: Administration: System Log 28
Setting System Log Settings 29
Setting Remote Logging Settings 31
Viewing Memory Logs 32
Chapter 4: Administration: File Management 34
System Files 34
Cisco 500 Series Stackable Managed Switch Administration Guide 1
Contents
Upgrade/Backup Firmware/Language 37
Active Image <Sx300-500> 41
Download/Backup Configuration/Log 42
Configuration Files Properties 48
Copy/Save Configuration 49
Auto Configuration via DHCP 50
Chapter 5: Administration: Stack Management 58
Overview 59
Types of Units in Stack 60
Stack Topology 62
Unit ID Assignment 63
Master Selection Process 65
Stack Changes 66
Unit Failure in Stack 68
Software Auto Synchronization in Stack 70
Stack Unit Mode 70
Stack Ports 74
Default Configuration 80
Interactions With Other Features 80
System Modes 81
Chapter 6: Administration 98
Device Models 99
System Settings 104
Console Settings (Autobaud Rate Support) 110
Management Interface<print only> 111
System Mode and Stack Management<Sx500 - print only> 111
User Accounts<print only> 111
Defining Idle Session Timeout 112
Cisco 500 Series Stackable Managed Switch Administration Guide 2
Contents
Time Settings<print only> 112
System Log<print only> 112
File Management<print only> 113
Rebooting the Device 113
Routing Resources<Sx300-500> 115
Health 119
Diagnostics<print only> 121
Discovery - Bonjour<print only> 121
UDLD<print only> 121
Discovery - LLDP<print only> 121
Discovery - CDP<print only> 121
Ping 121
<Sx300-500>Traceroute 123
Chapter 7: Administration: Time Settings 126
System Time Options 127
SNTP Modes 128
Configuring System Time 129
Chapter 8: Administration: Diagnostics 140
Testing Copper Ports 140
Displaying Optical Module Status 143
Configuring Port and VLAN Mirroring 144
Viewing CPU Utilization and Secure Core Technology 146
Chapter 9: Administration: Discovery 148
Bonjour 148
LLDP and CDP 151
Configuring LLDP 152
Configuring CDP 172
Cisco 500 Series Stackable Managed Switch Administration Guide 3
Contents
Chapter 10: Administration: Unidirectional Link Detection 183
UDLD Overview 183
UDLD Operation 184
Usage Guidelines 187
Dependencies On Other Features 187
Default Settings and Configuration 188
Before You Start 188
Common UDLD Tasks 188
Configuring UDLD 189
Chapter 11: Port Management 194
Configuring Ports 195
Setting Port Configuration 195
Link Aggregation 200
PoE<print only> 208
Configuring Green Ethernet 208
Chapter 12: Smartport 216
Overview 217
What is a Smartport 218
Smartport Types 218
Smartport Macros 221
Macro Failure and the Reset Operation 222
How the Smartport Feature Works 223
Auto Smartport 224
Error Handling 228
Default Configuration 228
Relationships with Other Features and Backwards Compatibility 228
Common Smartport Tasks 229
Configuring Smartport Using The Web-based Interface 231
Cisco 500 Series Stackable Managed Switch Administration Guide 4
Contents
Built-in Smartport Macros 236
Chapter 13: Port Management: PoE 248
PoE on the Device 248
Configuring PoE Properties 251
Configuring PoE Settings 253
Chapter 14: VLAN Management 256
VLANs 257
Configuring Default VLAN Settings 260
Creating VLANs 261
Configuring VLAN Interface Settings 262
Defining VLAN Membership 264
GVRP Settings<Sx300-500 > 267
VLAN Groups<Sx300-500> 268
Voice VLAN 272
Access Port Multicast TV VLAN<Sx300-500> 286
Customer Port Multicast TV VLAN<Sx300-500> 289
Chapter 15: Spanning Tree 292
STP Flavors 292
Configuring STP Status and Global Settings 293
Defining Spanning Tree Interface Settings 295
Configuring Rapid Spanning Tree Settings 298
Multiple Spanning Tree 300
Defining MSTP Properties 301
Mapping VLANs to a MSTP Instance 302
Defining MSTP Instance Settings 303
Defining MSTP Interface Settings 304
Cisco 500 Series Stackable Managed Switch Administration Guide 5
Contents
Chapter 16: Managing MAC Address Tables 308
Configuring Static MAC Addresses 309
Managing Dynamic MAC Addresses 310
Defining Reserved MAC Addresses 311
Chapter 17: Multicast 312
Multicast Forwarding 312
Defining Multicast Properties 316
Adding MAC Group Address 317
Adding IP Multicast Group Addresses 319
Configuring IGMP Snooping 321
MLD Snooping 324
Querying IGMP/MLD IP Multicast Group 326
Defining Multicast Router Ports 327
Defining Forward All Multicast 328
Defining Unregistered Multicast Settings 329
Chapter 18: IP Configuration 332
Overview 333
IPv4 Management and Interfaces 338
DHCP Server<Sx300-500> 358
IPv6 Management and Interfaces 373
Domain Name 396
Chapter 19: IP Configuration: RIPv2 402
Overview 402
How RIP Operates on the Device 403
Configuring RIP 408
Chapter 20: IP Configuration: VRRP 416
Cisco 500 Series Stackable Managed Switch Administration Guide 6
Contents
Overview 416
Configurable Elements of VRRP 420
Configuring VRRP 423
Chapter 21: Security 428
Defining Users 430
Configuring TACACS+<Sx300-500> 433
Configuring RADIUS 438
Key Management<Sx500> 442
Management Access Method 445
Management Access Authentication 451
Secure Sensitive Data Management<print only> 452
SSL Server 452
SSH Server<Sx300-500 print only> 454
SSH Client<print only> 454
Configuring TCP/UDP Services 455
Defining Storm Control 456
Configuring Port Security 457
802.1X<print only> 460
Denial of Service Prevention 460
DHCP Snooping<Sx300-500 print only) 471
IP Source Guard<Sx300-500> 471
ARP Inspection 474
First Hop Security<300-500 print only> 480
Chapter 22: Security: 802.1X Authentication 482
Overview of 802.1X 482
Authenticator Overview 484
Common Tasks 497
802.1X Configuration Through the GUI 499
Cisco 500 Series Stackable Managed Switch Administration Guide 7
Contents
<Sx300-500>Defining Time Ranges 510
<Sx300-500>Authentication Method and Port Mode Support 511
Chapter 23: Security: First Hop Security 515
First Hop Security Overview 516
Router Advertisement Guard 520
Neighbor Discovery Inspection 520
DHCPv6 Guard 521
Neighbor Binding Integrity 522
Attack Protection 525
Policies, Global Parameters and System Defaults 527
Common Tasks 528
Default Settings and Configuration 530
Before You Start 530
Configuring First Hop Security through Web GUI 531
Chapter 24: Security: SSH Client 544
Secure Copy (SCP) and SSH 544
Protection Methods 545
SSH Server Authentication 547
SSH Client Authentication 548
Before You Begin 549
Common Tasks 549
SSH Client Configuration Through the GUI 551
Chapter 25: Security: SSH Server 556
Overview 556
Common Tasks 557
SSH Server Configuration Pages 558
Cisco 500 Series Stackable Managed Switch Administration Guide 8
Contents
Chapter 26: Security: Secure Sensitive Data Management 562
Introduction 562
SSD Rules 563
SSD Properties 569
Configuration Files 571
SSD Management Channels 576
Menu CLI and Password Recovery 577
Configuring SSD 577
Chapter 27: Access Control 582
Access Control Lists 582
Defining MAC-based ACLs 585
IPv4-based ACLs 587
IPv6-Based ACLs 591
Defining ACL Binding 595
Chapter 28: Quality of Service 598
QoS Features and Components 599
Configuring QoS - General 602
QoS Basic Mode 615
QoS Advanced Mode 617
Managing QoS Statistics 628
Chapter 29: SNMP 634
SNMP Versions and Workflow 635
Model OIDs 637
SNMP Engine ID 640
Configuring SNMP Views 642
Creating SNMP Groups 643
Managing SNMP Users 645
Cisco 500 Series Stackable Managed Switch Administration Guide 9
Contents
Defining SNMP Communities 647
Defining Trap Settings 649
Notification Recipients 650
SNMP Notification Filters 654
Cisco 500 Series Stackable Managed Switch Administration Guide 10
Getting Started
This section provides an introduction to the web-based configuration utility, and
covers the following topics:
• Starting the Web-based Configuration Utility
• Quick Start Device Configuration
• Interface Naming Conventions
1
• Differences Between 500 Devices<500>
• Window Navigation
Starting the Web-based Configuration Utility
This section describes how to navigate the web-based switch configuration utility.
If you are using a pop-up blocker, make sure it is disabled.
Browser Restrictions
If you are using IPv6 interfaces on your management station, use the IPv6 global
address and not the IPv6 link local address to access the device from your
browser.
Launching the Configuration Utility
To open the web-based configuration utility:
STEP 1 Open a Web browser.
STEP 2 Enter the IP address of the device you are configuring in the address bar on the
browser, and then press Enter.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 1
1
Getting Started
Starting the Web-based Configuration Utility
NOTE When the device is using the factory default IP address of 192.168.1.254, its power
LED flashes continuously. When the device is using a DHCP assigned IP address or
an administrator-configured static IP address, the power LED is on solid.
Logging In
The default username is cisco and the default password is cisco. The first time
that you log in with the default username and password, you are required to enter
a new password.
NOTE If you have not previously selected a language for the GUI, the language of the Login
page is determined by the language(s) requested by your browser and the
languages configured on your device. If your browser requests Chinese, for
example, and Chinese has been loaded into your device, the Login page is
automatically displayed in Chinese. If Chinese has not been loaded into your
device, the Login page appears in English.
The languages loaded into the device have a language and country code (en-US,
en-GB and so on). For the Login page to be automatically displayed in a particular
language, based on the browser request, both the language and country code of
the browser request must match those of the language loaded on the device. If the
browser request contains only the language code without a country code (for
example: fr). The first embedded language with a matching language code is
taken (without matching the country code, for example: fr_CA).
To log in to the device configuration utility:
STEP 1 Enter the username/password. The password can contain up to 64 ASCII
characters. Password-complexity rules are described in the Setting Password
Complexity Rules section of the Configuring Security chapter.
STEP 2 If you are not using English, select the desired language from the Language drop-
down menu. To add a new language to the device or update a current one, refer to
the Upgrade/Backup Firmware/Language section.
STEP 3 If this is the first time that you logged on with the default user ID (cisco) and the
default password (cisco) or your password has expired, the Change Password
Page appears. See Password Expiration for additional information.
STEP 4 Choose whether to select Disable Password Complexity Enforcement or not.
For more information on password complexity, see the Setting Password
Complexity Rules section.
STEP 5 Enter the new password and click Apply.
2 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Getting Started
!
Starting the Web-based Configuration Utility
When the login attempt is successful, the Getting Started page appears.
If you entered an incorrect username or password, an error message appears and
the Login page remains displayed on the window. If you are having problems
logging in, please see the Launching the Configuration Utility section in the
Administration Guide for additional information.
Select Don't show this page on startup to prevent the Getting Started page from
being displayed each time that you log on to the system. If you select this option,
the System Summary page is opened instead of the Getting Started page.
HTTP/HTTPS
You can either open an HTTP session (not secured) by clicking Log In, or you can
open an HTTPS (secured) session, by clicking Secure Browsing (HTTPS). You are
asked to approve the logon with a default RSA key, and an HTTPS session is
opened.
1
NOTE There is no need to input the username/password prior to clicking the Secure
Browsing (HTTPS) button.
For information on how to configure HTTPS, see SSL Server.
Password Expiration
The New Password page appears:
• The first time you access the device with the default username cisco and
password cisco. This page forces you to replace the factory default
password.
• When the password expires, this page forces you to select a new
password.
Logging Out
By default, the application logs out after ten minutes of inactivity. You can change
this default value as described in the Defining Idle Session Timeout section.
CAUTION Unless the Running Configuration is copied to the Startup Configuration, rebooting
the device will remove all changes made since the last time the file was saved.
Save the Running Configuration to the Startup Configuration before logging off to
preserve any changes you made during this session.
A flashing red X icon to the left of the Save application link indicates that Running
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 3
1
Getting Started
Starting the Web-based Configuration Utility
Configuration changes have not yet been saved to the Startup Configuration file.
The flashing can be disabled by clicking on the Disable Save Icon Blinking button
on the Copy/Save Configuration page
When the device auto-discovers a device, such as an IP phone (see What is a
Smartport), and it configures the port appropriately for the device. These
configuration commands are written to the Running Configuration file. This causes
the Save icon to begin blinking when the you log on even though you did not make
any configuration changes.
When you click Save, the Copy/Save Configuration page appears. Save the
Running Configuration file by copying it to the Startup Configuration file. After this
save, the red X icon and the Save application link are no longer displayed.
To l o g o u t , c li ck Logout in the top right corner of any page. The system logs out of
the device.
When a timeout occurs or you intentionally log out of the system, a message
appears and the Login page appears, with a message indicating the logged-out
state. After you log in, the application returns to the initial page.
The initial page displayed depends on the “Do not show this page on startup”
option in the Getting Started page. If you did not select this option, the initial page
is the Getting Started page. If you did select this option, the initial page is the
System Summary page.
4 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Getting Started
Quick Start Device Configuration
Quick Start Device Configuration
To simplify device configuration through quick navigation, the Getting Started
page provides links to the most commonly used pages.
Category Link Name (on the Page) Linked Page
1
Initial Setup Change System Mode and
Stack Management
Change Management
Applications and Services
Change Device IP Address IPv4 Interface page
Create VLAN Create VLAN page
Configure Port Settings Port Setting page
Device Status System Summary System Summary page
Port Statistics Interface page
RMON Statistics Statistics page
View Log RAM Memory page
Quick Access Change Device Password User Accounts page
Upgrade Device Software Upgrade/Backup Firmware/
Backup Device Configuration Download/Backup
System Mode and Stack
Management page
TCP/UDP Services page
Language page
Configuration/Log page
Create MAC Based ACL MAC Based ACL page
Create IP Based ACL IPv4 Based ACL page
Configure QoS QoS Properties page
Configure Port Mirroring Port and VLAN Mirroring page
There are two hot links on the Getting Started page that take you to Cisco web
pages for more information. Clicking on the Support link takes you to the device
product support page, and clicking on the Forums link takes you to the Small
Business Support Community page.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 5
1
Interface Naming Conventions
Within the GUI, interfaces are denoted by concatenating the following elements:
• Type of interface: The following types of interfaces are found on the various
types of devices:
- Fast Ethernet (10/100 bits)—These are displayed as FE.
- Gigabit Ethernet ports (10/100/1000 bits)—These are displayed as
GE.
- Ten Gigabit Ethernet ports (10000 bits)—These are displayed as XG.
- LAG (Port Channel)—These are displayed as LAG.
- VLAN—These are displayed as VLAN.
Getting Started
Interface Naming Conventions
- Tunnel —These are displayed as Tunnel.
• Unit Number—Number of the unit in the stack. In standalone mode this is
always 1.
• Slot Number—The slot number is either 1 or 2.
• Interface Number: Port, LAG, tunnel or VLAN ID
Differences Between 500 Devices
This guide is relevant for both Sx500, SG500X,SG500XG and ESW2-550X
devices. Notes are provided when a feature is relevant for one but not all of these
devices.
The following summarizes the differences between these devices:
• The RIP and VRRP features are only supported on SG500X, SG500XG,
ESW2-550X devices, running in standalone mode and in (and in advanced
hybrid stack of SG500X and Sx500 devices - see Administration: Stack
Management for more details).
• TCAM size, see <300-500>Viewing TCAM Utilization
• Stack ports are different on these devices. See Stack Ports.
• Port speed availability per cable types are different on these devices. See
Cables Types.
6 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Getting Started
Differences Between 500 Devices
• Enabling IPv4 routing is done differently in the devices, as follows:
1
- SG500XSG500XG/ESW2-550X—IPv4 routing must be enabled in the
IPv4 Interface page.
- Sx500—When the device is switched from Layer 2 to Layer 3 system
mode, IPv4 routing is automatically enabled.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 7
1
Window Navigation
This section describes the features of the web-based switch configuration utility.
Application Header
The Application Header appears on every page. It provides the following
application links:
Getting Started
Window Navigation
Application Link
Name
Username Displays the name of the user logged on to the device. The
Description
A flashing red X icon displayed to the left of the Save
application link indicates that Running Configuration
changes have been made that have not yet been saved to
the Startup Configuration file. The flashing of the red X can
be disabled on the Copy/Save Configuration page.
Click Save to display the Copy/Save Configuration page.
Save the Running Configuration file by copying it to the
Startup Configuration file type on the device. After this
save, the red X icon and the Save application link are no
longer displayed. When the device is rebooted, it copies
the Startup Configuration file type to the Running
Configuration and sets the device parameters according
to the data in the Running Configuration.
default username is cisco. (The default password is cisco).
8 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Getting Started
Window Navigation
1
Application Link
Name
Language Menu This menu provides the following options:
Description
• Select a language: Select one of the languages that
appear in the menu. This language will be the webbased configuration utility language.
• Download Language: Add a new language to the
device.
• Delete Language: Deletes the second language on
the device. The first language (English) cannot be
deleted.
• Debug: Used for translation purposes. If you select
this option, all web-based configuration utility labels
disappear and in their place are the IDs of the
strings that correspond to the IDs in the language
file.
NOTE To upgrade a language file, use the Upgrade/
Backup Firmware/Language page.
Logout Click to log out of the web-based switch configuration
utility.
About Click to display the device name and device version
number.
Help Click to display the online help.
The SYSLOG Alert Status icon appears when a SYSLOG
message, above the critical severity level, is logged. Click
the icon to open the RAM Memory page. After you access
this page, the SYSLOG Alert Status icon is no longer
displayed. To display the page when there is not an active
SYSLOG message, Click Status and Statistics > View
Log > RAM Memory.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 9
1
Getting Started
Window Navigation
Management Buttons
The following table describes the commonly-used buttons that appear on various
pages in the system.
Button Name Description
Use the pull-down menu to configure the number of
entries per page.
Indicates a mandatory field.
Add Click to display the related Add page and add an entry to a
table. Enter the information and click Apply to save it to the
Running Configuration. Click Close to return to the main
page. Click Save to display the Copy/Save Configuration
page and save the Running Configuration to the Startup
Configuration file type on the device.
Apply Click to apply changes to the Running Configuration on the
device. If the device is rebooted, the Running
Configuration is lost, unless it is saved to the Startup
Configuration file type or another file type. Click Save to
display the Copy/Save Configuration page and save the
Running Configuration to the Startup Configuration file
type on the device.
Cancel Click to reset changes made on the page.
Clear All
Interfaces
Counters
Clear Interface
Counters
Clear Logs Clears log files.
Clear Table Clears table entries.
Close Returns to main page. If any changes were not applied to
Click to clear the statistic counters for all interfaces.
Click to clear the statistic counters for the selected
interface.
the Running Configuration, a message appears.
10 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Getting Started
Window Navigation
1
Button Name Description
Copy Settings A table typically contains one or more entries containing
configuration settings. Instead of modifying each entry
individually, it is possible to modify one entry and then
copy the selected entry to multiple entries, as described
below:
1. Select the entry to be copied. Click Copy Settings to
display the popup.
2. Enter the destination entry numbers in the to field.
3. Click Apply to save the changes and click Close to
return to the main page.
Delete After selecting an entry in the table, click Delete to
remove.
Details Click to display the details associated with the entry
selected.
Edit Select the entry and click Edit. The Edit page appears,
and the entry can be modified.
1. C li ck Apply to save the changes to the Running
Configuration.
2. Click Close to return to the main page.
Go Enter the query filtering criteria and click Go. The results
are displayed on the page.
Refresh Clich Refresh to refresh the counter values.
Te st Click Te s t to perform the related tests.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 11
1
Getting Started
Window Navigation
12 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
This section describes how to view device statistics.
It covers the following topics:
• System Summary
• Viewing Ethernet Interfaces
• Viewing Etherlike Statistics
2
• Viewing GVRP Statistics
• Viewing 802.1X EAP Statistics
• Viewing TCAM Utilization
• Health
• Managing RMON
• View Log
System Summary
See System Settings.
Viewing Ethernet Interfaces
The Interface page displays traffic statistics per port. The refresh rate of the
information can be selected.
This page is useful for analyzing the amount of traffic that is both sent and
received and its dispersion (Unicast, Multicast, and Broadcast).
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 13
2
Status and Statistics
Viewing Ethernet Inter faces
To display Ethernet statistics and/or set the refresh rate:
STEP 1 Click Status and Statistics > Interface.
STEP 2 Enter the parameters.
• Interface—Select the type of interface and specific interface for which
Ethernet statistics are to be displayed.
• Refresh Rate—Select the time period that passes before the interface
Ethernet statistics are refreshed. The available options are:
- No Refresh—Statistics are not refreshed.
- 15 Sec—Statistics are refreshed every 15 seconds.
- 30 Sec—Statistics are refreshed every 30 seconds.
- 60 Sec—Statistics are refreshed every 60 seconds.
The Receive Statistics area displays information about incoming packets.
• Tot al B y te s (O ct ets )—Octets received, including bad packets and FCS
octets, but excluding framing bits.
• Unicast Packets—Good Unicast packets received.
• Multicast Packets—Good Multicast packets received.
• Broadcast Packets—Good Broadcast packets received.
• Packets with Errors—Packets with errors received.
The Transmit Statistics area displays information about outgoing packets.
• Tot al B y te s (O ct ets )—Octets transmitted, including bad packets and FCS
octets, but excluding framing bits.
• Unicast Packets—Good Unicast packets transmitted.
• Multicast Packets—Good Multicast packets transmitted.
• Broadcast Packets—Good Broadcast packets transmitted.
To clear or view statistics counters:
• Click Clear Interface Counters to clear counters for the interface displayed.
• Click View All Interfaces Statistics to see all ports on a single page.
14 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
Viewing Etherlike Statistics
Viewing Etherlike Statistics
The Etherlike page displays statistics per port according to the Etherlike MIB
standard definition. The refresh rate of the information can be selected. This page
provides more detailed information regarding errors in the physical layer (Layer 1),
which might disrupt traffic.
To view Etherlike Statistics and/or set the refresh rate:
STEP 1 Click Status and Statistics > Etherlike.
STEP 2 Enter the parameters.
• Interface—Select the type of interface and specific interface for which
Ethernet statistics are to be displayed.
2
• Refresh Rate—Select the amount of time that passes before the Etherlike
statistics are refreshed.
The fields are displayed for the selected interface.
• Frame Check Sequence (FCS) Errors—Received frames that failed the
CRC (cyclic redundancy checks).
• Single Collision Frames—Frames that were involved in a single collision,
but were successfully transmitted.
• Late Collisions—Collisions that have been detected after the first 512 bits
of data.
• Excessive Collisions—Number of transmissions rejected due to excessive
collisions.
• Oversize Packets—Packets greater than 2000 octets received.
• Internal MAC Receive Errors—Frames rejected because of receiver errors.
• Pause Frames Received—Received flow control pause frames.
• Pause Frames Transmitted—Flow control pause frames transmitted from
the selected interface.
To clear statistics counters:
• Click Clear Interface Counters to clear the selected interfaces counters.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 15
2
• Click View All Interfaces Statistics to see all ports on a single page.
Viewing GVRP Statistics
The GVRP page displays information regarding GARP VLAN Registration Protocol
(GVRP) frames that were sent or received from a port. GVRP is a standards-based
Layer 2 network protocol, for automatic configuration of VLAN information on
switches. It was defined in the 802.1ak amendment to 802.1Q-2005.
GVRP statistics for a port are only displayed if GVRP is enabled globally and on
the port. See the GVRP page.
To view GVRP statistics and/or set the refresh rate:
Status and Statistics
Viewing GVRP Statistics
STEP 1 Click Status and Statistics > GVRP.
STEP 2 Enter the parameters.
• Interface—Select the specific interface for which GVRP statistics are to be
displayed.
• Refresh Rate—Select the time period that passes before the GVRP
statistics page is refreshed.
The Attribute Counter block displays the counters for various types of packets per
interface.
• Join Empty—Number of GVRP Join Empty packets received/transmitted.
• Empty—Number of GVRP empty packets received/transmitted.
• Leave Empty—Number of GVRP Leave Empty packets received/
transmitted.
• Join In—Number of GVRP Join In packets received/transmitted.
• Leave In—Number of GVRP Leave In packets received/transmitted.
• Leave All—Number of GVRP Leave All packets received/transmitted.
The GVRP Error Statistics section displays the GVRP error counters.
• Invalid Protocol ID—Invalid protocol ID errors.
• Invalid Attribute Type—Invalid attribute ID errors.
16 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
Viewing 802.1X EAP Statistics
• Invalid Attribute Value—Invalid attribute value errors.
• Invalid Attribute Length—Invalid attribute length errors.
• Invalid Event—Invalid events.
To clear statistics counters:
• Click Clear Interface Counters to clear the selected counters.
• Click View All Interfaces Statistics to see all ports on a single page.
Viewing 802.1X EAP Statistics
2
The 802.1x EAP page displays detailed information regarding the EAP (Extensible
Authentication Protocol) frames that were sent or received. To configure the
802.1X feature, see the 802.1X Properties page.
To view the EAP Statistics and/or set the refresh rate:
STEP 1 Click Status and Statistics > 802.1x EAP.
STEP 2 Select the Interface that is polled for statistics.
STEP 3 Select the time period (Refresh Rate) that passes before the EAP statistics are
refreshed.
The values are displayed for the selected interface.
• EAPOL Frames Received—Valid EAPOL frames received on the port.
• EAPOL Frames Transmitted—Valid EAPOL frames transmitted by the port.
• EAPOL Start Frames Received—EAPOL Start frames received on the port.
• EAPOL Logoff Frames Received—EAPOL Logoff frames received on the
port.
• EAP Response/ID Frames Received—EAP Resp/ID frames received on the
port.
• EAP Response Frames Received—EAP Response frames received by the
port (other than Resp/ID frames).
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 17
2
Status and Statistics
Viewing TCAM Utilization
• EAP Request/ID Frames Transmitted—EAP Req/ID frames transmitted by
the port.
• EAP Request Frames Transmitted—EAP Request frames transmitted by
the port.
• Invalid EAPOL Frames Received—Unrecognized EAPOL frames received
on this port.
• EAP Length Error Frames Received—EAPOL frames with an invalid Packet
Body Length received on this port.
• Last EAPOL Frame Version—Protocol version number attached to the most
recently received EAPOL frame.
• Last EAPOL Frame Source—Source MAC address attached to the most
recently received EAPOL frame.
To clear statistics counters:
• Click Clear Interface Counters to clear the selected interfaces counters.
• Click Clear All Interface Counters to clear the counters of all interfaces.
Viewing TCAM Utilization
The device architecture uses a Ternary Content Addressable Memory (TCAM) to
support packet actions in wire speed.
TCAM TCAM holds the rules produced by applications, such as ACLs (Access
Control Lists), Quality of Service (QoS), IP Routing and user-created rules.
Some applications allocate rules upon their initiation. Additionally, processes that
initialize during system boot use some of their rules during the startup process.
To view TCAM utilization, click Status and Statistics > TCAM Utilization.
The following fields are displayed for SG500X/SG500XG devices and for Sx500
devices in Layer 3 system mode and when the device is part of a stack (per unit):
• Unit No—Unit in stack for which TCAM utilization appears. This is not
displayed when the device is in standalone mode.
• Maximum TCAM Entries for IPv4 and IPv6 Routing—Maximum TCAM
entries available.
18 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
Health
2
• IPv4 Routing
- In Use—Number of TCAM entries used for IPv4 routing.
- Maximum—Number of available TCAM entries that can be used for IPv4
routing.
• IPv6 Routing—Number of TCAM entries used for IPv6 routing.
- In Use—Number of TCAM entries used for IPv6 routing.
- Maximum—Number of available TCAM entries that can be used for IPv6
routing.
• Maximum TCAM Entries for Non-IP Rules—Maximum TCAM Entries
available for non-IP rules.
• Non-IP Rules
To view how the allocation among various processes can be changed (for the 500
series), see the Router Resources section.
Health
See Health.
Managing RMON
RMON (Remote Networking Monitoring) is an SNMP specification that enables an
SNMP agent in the device to proactively monitor traffic statistics over a given
period and send traps to an SNMP manager. The local SNMP agent compares
actual, real-time counters against predefined thresholds and generates alarms,
without the need for polling by a central SNMP management platform. This is an
effective mechanism for proactive management, provided that you have the
correct thresholds set relative to your network’s base line.
- In Use—Number of TCAM entries used for non-IP rules.
- Maximum—Number of available TCAM entries that can be used for non-
IP rules.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 19
2
Status and Statistics
Managing RMON
RMON decreases the traffic between the manager and the device because the
SNMP manager does not have to poll the device frequently for information, and
enables the manager to get timely status reports, because the device reports
events as they occur.
With this feature, you can perform the following actions:
• View the current statistics (since the counter values were cleared). You can
also collect the values of these counters over a period of time, and then
view the table of collected data, where each collected set is a single line of
the History tab.
• Define interesting changes in counter values, such as “reached a certain
number of late collisions” (defines the alarm), and then specify what action
to perform when this event occurs (log, trap, or log and trap).
Viewing RMON Statistics
The Statistics page displays detailed information regarding packet sizes and
information regarding physical layer errors. The information displayed is according
to the RMON standard. An oversized packet is defined as an Ethernet frame with
the following criteria:
• Packet length is greater than MRU byte size.
• Collision event has not been detected.
• Late collision event has not been detected.
• Received (Rx) error event has not been detected.
• Packet has a valid CRC.
To view RMON statistics and/or set the refresh rate:
STEP 1 Click Status and Statistics > RMON > Statistics.
STEP 2 Select the Interface for which Ethernet statistics are to be displayed.
STEP 3 Select the Refresh Rate, the time period that passes before the interface
statistics are refreshed.
The statistics are displayed for the selected interface.
• Bytes Received—Number of octets received, including bad packets and
FCS octets, but excluding framing bits.
• Drop Events—Number of packets dropped.
20 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
Managing RMON
2
• Packets Received—Number of good packets received, including Multicast
and Broadcast packets.
• Broadcast Packets Received—Number of good Broadcast packets
received. This number does not include Multicast packets.
• Multicast Packets Received—Number of good Multicast packets received.
• CRC & Align Errors—Number of CRC and Align errors that have occurred.
• Undersize Packets—Number of undersized packets (less than 64 octets)
received.
• Oversize Packets—Number of oversized packets (over 2000 octets)
received.
• Fragments—Number of fragments (packets with less than 64 octets,
excluding framing bits, but including FCS octets) received.
• Jabbers—Total number received packets that were longer than 1632
octets. This number excludes frame bits, but includes FCS octets that had
either a bad FCS (Frame Check Sequence) with an integral number of octets
(FCS Error) or a bad FCS with a non-integral octet (Alignment Error) number.
A Jabber packet is defined as an Ethernet frame that satisfies the following
criteria:
- Packet data length is greater than MRU.
- Packet has an invalid CRC.
- Received (Rx) Error Event has not been detected.
• Collisions—Number of collisions received. If Jumbo Frames are enabled,
the threshold of Jabber Frames is raised to the maximum size of Jumbo
Frames.
• Frames of 64 Bytes—Number of frames, containing 64 bytes that were
received.
• Frames of 65 to 127 Bytes—Number of frames, containing 65-127 bytes
that were received.
• Frames of 128 to 255 Bytes—Number of frames, containing 128-255 bytes
that were received.
• Frames of 256 to 511 Bytes—Number of frames, containing 256-511 bytes
that were received.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 21
2
Status and Statistics
Managing RMON
• Frames of 512 to 1023 Bytes—Number of frames, containing 512-1023
bytes that were received.
• Frames of 1024 Bytes or More—Number of frames, containing 1024-2000
bytes, and Jumbo Frames, that were received.
To clear statistics counters:
• Click Clear Interface Counters to clear the selected interfaces counters.
• Click View All Interfaces Statistics to see all ports on a single page.
Configuring RMON History
The RMON feature enables monitoring statistics per interface.
The History Control Table page
samples to store and the port from where to gather the data.
defines the sampling frequency, amount of
After the data is sampled and stored, it appears in the History Table page that can
be viewed by clicking History Table.
To enter RMON control information:
STEP 1 Click Status and Statistics > RMON > History. The fields displayed on this page
are defined in the Add RMON History page, below. The only field is that is on this
page and not defined in the Add page is:
• Current Number of Samples—RMON is allowed by standard to not grant all
requested samples, but rather to limit the number of samples per request.
Therefore, this field represents the sample number actually granted to the
request that is equal or less than the requested value.
STEP 2 Click Add.
STEP 3 Enter the parameters.
• New History Entry—Displays the number of the new History table entry.
• Source Interface—Select the type of interface from which the history
samples are to be taken.
• Max No. of Samples to Keep—Enter the number of samples to store.
• Sampling Interval—Enter the time in seconds that samples are collected
from the ports. The field range is 1-3600.
22 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
Managing RMON
2
• Owner—Enter the RMON station or user that requested the RMON
information.
STEP 4 Click Apply. The entry is added to the History Control Table page
Configuration file is updated.
STEP 5 Click History Table to view the actual statistics.
,
and the Running
Viewing the RMON History Table
The History Table page displays interface-specific statistical network samplings.
The samples were configured in the History Control table described above.
To view RMON history statistics:
STEP 1 Click Status and Statistics > RMON > History.
STEP 2 Click History Table.
STEP 3 From the History Entry No. list, select the entry number of the sample to display.
The fields are displayed for the selected sample.
• Owner—History table entry owner.
• Sample No.—Statistics were taken from this sample.
• Drop Events—Dropped packets due to lack of network resources during the
sampling interval. This may not represent the exact number of dropped
packets, but rather the number of times dropped packets were detected.
• Bytes Received—Octets received including bad packets and FCS octets,
but excluding framing bits.
• Packets Received—Packets received, including bad packets, Multicast,
and Broadcast packets.
• Broadcast Packets—Good Broadcast packets excluding Multicast packets.
• Multicast Packets—Good Multicast packets received.
• CRC Align Errors—CRC and Align errors that have occurred.
• Undersize Packets—Undersized packets (less than 64 octets) received.
• Oversize Packets—Oversized packets (over 2000 octets) received.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 23
2
Status and Statistics
Managing RMON
• Fragments—Fragments (packets with less than 64 octets) received,
excluding framing bits, but including FCS octets.
• Jabbers—Total number of received packets that were longer than 2000
octets. This number excludes frame bits, but includes FCS octets that had
either a bad FCS (Frame Check Sequence) with an integral number of octets
(FCS Error) or a bad FCS with a non-integral octet (Alignment Error) number.
• Collisions—Collisions received.
• Utilization—Percentage of current interface traffic compared to maximum
traffic that the interface can handle.
Defining RMON Events Control
You can control the occurrences that trigger an alarm and the type of notification
that occurs. This is performed as follows:
• Events Page—Configures what happens when an alarm is triggered. This
can be any combination of logs and traps.
• Alarms Page—Configures the occurrences that trigger an alarm.
To define RMON events:
STEP 1 Click Status and Statistics > RMON > Events.
This page displays previously defined events.
STEP 2 Click Add.
STEP 3 Enter the parameters.
• Event Entry—Displays the event entry index number for the new entry.
• Community—Enter the SNMP community string to be included when traps
are sent (optional). Note that the community must be defined using the
Defining SNMPv1,2 Notification Recipients or Defining SNMPv3
Notification Recipients pages for the trap to reach the Network
Management Station.
• Description—Enter a name for the event. This name is used in the Add
RMON Alarm page to attach an alarm to an event.
• Notification Type—Select the type of action that results from this event.
Values are:
24 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
Managing RMON
STEP 4 Click Apply. The RMON event is saved to the Running Configuration file.
STEP 5 Click Event Log Table to display the log of alarms that have occurred and that have
2
- None—No action occurs when the alarm goes off.
- Log (Event Log Table)—Add a log entry to the Event Log table when the
alarm is triggered.
- Trap (SNMP Manager and SYSLOG Server)—Send a trap to the remote
log server when the alarm goes off.
- Log and Trap—Add a log entry to the Event Log table and send a trap to
the remote log server when the alarm goes off.
• Time—Displays the time of the event. (This is a read-only table in the parent
window and cannot be defined).
• Owner—Enter the device or user that defined the event.
been logged (see description below).
Viewing the RMON Events Logs
The Event Log Table page displays the log of events (actions) that occurred. Two
types of events can be logged: Log or Log and Trap. The action in the event is
performed when the event is bound to an alarm (see the Alarms page) and the
conditions of the alarm have occurred.
STEP 1 Click Status and Statistics > RMON > Events.
STEP 2 Click Event Log Table.
This page displays the following fields:
• Event Entry No.—Event’s log entry number.
• Log No.—Log number (within the event).
• Log Time—Time that the log entry was entered.
• Description—Description of event that triggered the alarm.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 25
2
Status and Statistics
Managing RMON
Defining RMON Alarms
RMON alarms provide a mechanism for setting thresholds and sampling intervals
to generate exception events on any counter or any other SNMP object counter
maintained by the agent. Both the rising and falling thresholds must be configured
in the alarm. After a rising threshold is crossed, no rising events are generated until
the companion falling threshold is crossed. After a falling alarm is issued, the next
alarm is issued when a rising threshold is crossed.
One or more alarms are bound to an event, which indicates the action to be taken
when the alarm occurs.
The Alarms page provides the ability to configure alarms and to bind them with
events. Alarm counters can be monitored by either absolute values or changes
(delta) in the counter values.
To enter RMON alarms:
STEP 1 Click Status and Statistics > RMON > Alarms. All previously-defined alarms are
displayed. The fields are described in the Add RMON Alarm page below. In
addition to those fields, the following field appears:
• Counter Value—Displays the value of the statistic during the last sampling
period.
STEP 2 Click Add.
STEP 3 Enter the parameters.
• Alarm Entry—Displays the alarm entry number.
• Interface—Select the type of interface for which RMON statistics are
displayed.
• Counter Name—Select the MIB variable that indicates the type of
occurrence measured.
• Sample Type—Select the sampling method to generate an alarm. The
options are:
- Absolute—If the threshold is crossed, an alarm is generated.
- Delta—Subtracts the last sampled value from the current value. The
difference in the values is compared to the threshold. If the threshold was
crossed, an alarm is generated.
• Rising Threshold—Enter the value that triggers the rising threshold alarm.
26 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Status and Statistics
View Log
2
• Rising Event—Select an event to be performed when a rising event is
triggered. Events are created in the Events page.
• Falling Threshold—Enter the value that triggers the falling threshold alarm.
• Falling Event—Select an event to be performed when a falling event is
triggered.
• Startup Alarm—Select the first event from which to start generation of
alarms. Rising is defined by crossing the threshold from a low-value
threshold to a higher-value threshold.
- Rising Alarm—A rising value triggers the rising threshold alarm.
- Falling Alarm—A falling value triggers the falling threshold alarm.
- Rising and Falling—Both rising and falling values trigger the alarm.
• Interval—Enter the alarm interval time in seconds.
View Log
• Owner—Enter the name of the user or network management system that
receives the alarm.
STEP 4 Click Apply. The RMON alarm is saved to the Running Configuration file.
See Viewing Memory Logs.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 27
2
Status and Statistics
View Log
28 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: System Log
This section describes the System Log feature, which enables the device to
generate multiple independent logs. Each log is a set of messages describing
system events.
The device generates the following local logs:
• Log sent to the console interface.
3
• Log written into a cyclical list of logged events in the RAM and erased when
the device reboots.
• Log written to a cyclical log-file saved to the Flash memory and persists
across reboots.
In addition, you can send messages to remote SYSLOG servers in the form of
SNMP traps and SYSLOG messages.
This section covers the following sections:
• Setting System Log Settings
• Setting Remote Logging Settings
• Viewing Memory Logs
Setting System Log Settings
You can enable or disable logging on the Log Settings page, and select whether to
aggregate log messages.
You can select the events by severity level. Each log message has a severity level
marked with the first letter of the severity level concatenated with a dash (-) on
each side (except for Emergency that is indicated by the letter F). For example, the
log message "%INIT-I-InitCompleted: … " has a severity level of I, meaning
Informational.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 29
3
Administration: System Log
Setting System Log Settings
The event severity levels are listed from the highest severity to the lowest severity,
as follows:
• Emergency—System is not usable.
• Alert—Action is needed.
• Critical—System is in a critical condition.
• Error—System is in error condition.
• Warning—System warning has occurred.
• Notice—System is functioning properly, but a system notice has occurred.
• Informational—Device information.
• Debug—Detailed information about an event.
You can select different severity levels for RAM and Flash logs. These logs are
displayed in the RAM Memory page and Flash Memory page, respectively.
Selecting a severity level to be stored in a log causes all of the higher severity
events to be automatically stored in the log. Lower severity events are not stored
in the log.
For example, if Warning is selected, all severity levels that are Warning and higher
are stored in the log (Emergency, Alert, Critical, Error, and Warning). No events with
severity level below Warning are stored (Notice, Informational, and Debug).
To set global log parameters:
STEP 1 Click Administration > System Log > Log Settings.
STEP 2 Enter the parameters.
• Logging—Select to enable message logging.
• Syslog Aggregator—Select to enable the aggregation of SYSLOG
messages and traps. If enabled, identical and contiguous SYSLOG
messages and traps are aggregated over the specified Max Aggregation
Time and sent in a single message. The aggregated messages are sent in
the order of their arrival. Each message states the number of times it was
aggregated.
• Max Aggregation Time—Enter the interval of time that SYSLOG messages
are aggregated.
30 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: System Log
Setting Remote Logging Settings
3
• Originator Identifier—Enables adding an origin identifier to SYSLOG
messages. The options are:
- None—Do not include the origin identifier in SYSLOG messages.
- Hostname—Include the system hostname in SYSLOG messages.
- IPv4 Address—Include the IPv4 address of the sending interface in
SYSLOG messages.
- IPv6 Address—Include the IPv6 address of the sending interface in
SYSLOG messages.
- User Defined—Enter a description to be included in SYSLOG messages.
• RAM Memory Logging—Select the severity levels of the messages to be
logged to the RAM.
• Flash Memory Logging—Select the severity levels of the messages to be
logged to the Flash memory.
STEP 3 Click Apply. The Running Configuration file is updated.
Setting Remote Logging Settings
The Remote Log Servers page enables defining remote SYSLOG servers where
log messages are sent (using the SYSLOG protocol). For each server, you can
configure the severity of the messages that it receives.
To d e f i n e S YS LO G s er v e r s :
STEP 1 Click Administration > System Log > Remote Log Servers.
STEP 2 Enter the following fields:
• IPv4 Source Interface—Select the source interface whose IPv4 address will
be used as the source IPv4 address of SYSLOG messages sent to SYSLOG
servers.
• IPv6 Source Interface—Select the source interface whose IPv6 address will
be used as the source IPv6 address of SYSLOG messages sent to SYSLOG
servers.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 31
3
Administration: System Log
Setting Remote Logging Settings
NOTE If the Auto option is selected, the system takes the source IP address
from the IP address defined on the outgoing interface.
STEP 3 Click Add.
STEP 4 Enter the parameters.
• Server Definition—Select whether to identify the remote log server by IP
address or name.
• IP Version—Select the supported IP format.
• IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The
options are:
- Link Local—The IPv6 address uniquely identifies hosts on a single
network link. A link local address has a prefix of FE80, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
- Global—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
• Link Local Interface—Select the link local interface (if IPv6 Address Type
Link Local is selected) from the list.
• Log Server IP Address/Name—Enter the IP address or domain name of the
log server.
• UDP Port—Enter the UDP port to which the log messages are sent.
• Facility—Select a facility value from which system logs are sent to the
remote server. Only one facility value can be assigned to a server. If a second
facility code is assigned, the first facility value is overridden.
• Description—Enter a server description.
• Minimum Severity—Select the minimum level of system log messages to
be sent to the server.
STEP 5 Click Apply. The Add Remote Log Server page
added, and the Running Configuration file is updated.
closes, the SYSLOG server is
32 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: System Log
Viewing Memory Logs
Viewing Memory Logs
The device can write to the following logs:
• Log in RAM (cleared during reboot).
• Log in Flash memory (cleared only upon user command).
You can configure the messages that are written to each log by severity, and a
message can go to more than one log, including logs that reside on external
SYSLOG servers.
RAM Memory
The RAM Memory page displays all messages that were saved in the RAM
(cache) in chronological order. Entries are stored in the RAM log according to the
configuration in the Log Settings page.
3
To view log entries, click Status and Statistics > View Log > RAM Memory.
The top of the page has a button that allows you to Disable Alert Icon Blinking.
Click to toggle between disable and enable.
This page contains the following fields:
• Log Index—Log entry number.
• Log Time—Time when message was generated.
• Severity—Event severity.
• Description—Message text describing the event.
To clear the log messages, click Clear Logs. The messages are cleared.
Flash Memory
The Flash Memory page displays the messages that were stored in the Flash
memory, in chronological order. The minimum severity for logging is configured in
the Log Settings page. Flash logs remain when the device is rebooted. You can
clear the logs manually.
To view the Flash logs, click Status and Statistics > View Log > Flash Memory.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 33
3
Administration: System Log
Viewing Memory Logs
This page contains the following fields:
• Log Index—Log entry number.
• Log Time—Time when message was generated.
• Severity—Event severity.
• Description—Message text describing the event.
To clear the messages, click Clear Logs. The messages are cleared.
34 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
This section describes how system files are managed.
The following topics are covered:
• System Files
• Upgrade/Backup Firmware/Language
• Active Image
4
System Files
• Download/Backup Configuration/Log
• Configuration Files Properties
• Copy/Save Configuration
• Auto Configuration via DHCP
System files are files that contain configuration information, firmware images or
boot code.
Various actions can be performed with these files, such as: selecting the firmware
file from which the device boots, copying various types of configuration files
internally on the device, or copying files to or from an external device, such as an
external server.
The possible methods of file transfer are:
• Internal copy.
• HTTP/HTTPS that uses the facilities that the browser provides.
• TFTF/SCP client, requiring a TFTP/SCP server.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 35
4
Administration: File Management
System Files
Configuration files on the device are defined by their type, and contain the
settings and parameter values for the device.
When a configuration is referenced on the device, it is referenced by its
configuration file type (such as Startup Configuration or Running Configuration),
as opposed to a file name that can be modified by the user.
Content can be copied from one configuration file type to another, but the names
of the file types cannot be changed by the user.
Other files on the device include firmware, boot code, and log files, and are
referred to as operational files.
The configuration files are text files and can be edited in a text editor, such as
Notepad after they are copied to an external device, such as a PC.
Files and File Types
The following types of configuration and operational files are found on the device:
• Running Configuration—Contains the parameters currently being used by
the device to operate. This is the only file type that is modified when you
change parameter values on the device.
If the device is rebooted, the Running Configuration is lost. The Startup
Configuration, stored in Flash, overwrites the Running Configuration, stored
in RAM.
To preserve any changes you made to the device, you must save the
Running Configuration to the Startup Configuration, or another file type.
• Startup Configuration—The parameter values that were saved by copying
another configuration (usually the Running Configuration) to the Startup
Configuration.
The Startup Configuration is retained in Flash and is preserved when the
device is rebooted. At this time, the Startup Configuration is copied to RAM
and identified as the Running Configuration.
• Mirror Configuration—A copy of the Startup Configuration, created by the
device when the following conditions exist:
- The device has been operating continuously for 24 hours.
- No configuration changes have been made to the Running Configuration
in the previous 24 hours.
- The Startup Configuration is identical to the Running Configuration.
36 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
System Files
Only the system can copy the Startup Configuration to the Mirror
Configuration. However, you can copy from the Mirror Configuration to other
file types or to another device.
The option of automatically copying the Running Configuration to the mirror
configuration can be disabled in the Configuration Files Properties page.
• Backup Configuration—A manual copy of a configuration file used for
protection against system shutdown or for the maintenance of a specific
operating state. You can copy the Mirror Configuration, Startup
Configuration, or Running Configuration to a Backup Configuration file. The
Backup Configuration exists in Flash and is preserved if the device is
rebooted.
• Firmware—The program that controls the operations and functionality of
the device. More commonly referred to as the image.
4
• Boot Code—Controls the basic system startup and launches the firmware
image.
• Language File—The dictionary that enables the web-based configuration
utility windows to be displayed in the selected language.
• Flash Log—SYSLOG messages stored in Flash memory.
File Actions
The following actions can be performed to manage firmware and configuration
files:
• Upgrade the firmware or boot code, or replace a second language, as
described in Upgrade/Backup Firmware/Language section.
• View the firmware image currently in use or select the image to be used in
the next reboot as described in the Active Image section.
• Save configuration files on the device to a location on another device as
described in the Download/Backup Configuration/Log section.
• Clear the Startup Configuration or Backup Configuration file types as
described in the Configuration Files Properties section.
• Copy one configuration file type to another configuration file type as
described in the Copy/Save Configuration section.
• Enable automatically uploading a configuration file from a DHCP server to
the device, as described in the Auto Configuration via DHCP section.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 37
4
This section covers the following topics:
• Upgrade/Backup Firmware/Language
• Active Image
• Download/Backup Configuration/Log
• Configuration Files Properties
• Copy/Save Configuration
• Auto Configuration via DHCP
Upgrade/Backup Firmware/Language
Administration: File Management
Upgrade/Backup Firmware/Language
The Upgrade/Backup Firmware/Language process can be used to:
• Upgrade or backup the firmware image.
• Upgrade or backup the boot code.
• Import or upgrade a second language file.
The following methods for transferring files are supported:
• HTTP/HTTPS that uses the facilities provided by the browser
• TFTP that requires a TFTP server
• Secure Copy Protocol (SCP) that requires an SCP server
If a new language file was loaded onto the device, the new language can be
selected from the drop-down menu. (It is not necessary to reboot the device). This
language file is automatically copied to all devices in the stack.
All software images on the stack must be identical to ensure the proper operation
of the stack. If a device is added to a stack and its software image is not identical
to the master's software image, the master automatically loads the correct image
to the new device.
There are two different ways to update images across the stack:
• Image can be updated prior to connecting a unit to the stack. This is the
recommended method.
• Upgrade device or stack. If the stack is updated, the slave units are
automatically updated. This is done as follows:
38 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Upgrade/Backup Firmware/Language
- Copy image from TFTP/SCP server to master, using the Upgrade/
- Change the active image, using the Active Image page.
- Reboot, using the Reboot page.
There are two firmware images stored on the device. One of the images is
identified as the active image and other image is identified as the inactive image.
When you upgrade the firmware, the new image always replaces the image
identified as the inactive image.
Even after uploading new firmware on the device, the device continues to boot by
using the active image (the old version) until you change the status of the new
image to be the active image by using the procedure in the Active Image section.
Then boot the device.
4
Backup Firmware/Language page.
NOTE If the device is running in stacking mode, the new firmware is pushed to all of the
stack units. If there is a new device joining the stack with a different firmware
version, the master unit syncs the firmware version automatically with this newly
joined unit. This occurs transparently, without any manual intervention.
Upgrade/Backing Firmware or Language File
To upgrade or backup a software image or language file:
STEP 1 Click Administration > File Management > Upgrade/Backup Firmware/
Language.
STEP 2 Click the Transfer Method. Proceed as follows:
• If you selected TFTP, go to STEP 3.
• If you selected via HTTP/HTTPS, go to STEP 4.
• If you selected via SCP, go to STEP 5.
STEP 3 If you selected via TFTP, enter the parameters as described in this step.
Otherwise, skip to STEP 4.
Select one of the following Save Actions:
• Upgrade—Specifies that the file type on the device is to be replaced with a
new version of that file type located on a TFTP server.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 39
4
Administration: File Management
Upgrade/Backup Firmware/Language
• Backup—Specifies that a copy of the file type is to be saved to a file on
another device.
Enter the following fields:
• File Type—Select the destination file type. Only valid file types are shown.
(The file types are described in the Files and File Types section).
• TFTP Server Definition—Select whether to specify the TFTP server by IP
address or domain name.
• IP Version—Select whether an IPv4 or an IPv6 address is used.
• IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The
options are:
- Link Local—The IPv6 address uniquely identifies hosts on a single
network link. A link local address has a prefix of FE80, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
- Global—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
• Link Local Interface—Select the link local interface (if IPv6 is used) from the
list.
• TFTP Server IP Address/Name—Enter the IP address or the domain name
of the TFTP server.
• (For Upgrade) Source File Name—Enter the name of the source file.
• (For Backup) Destination File Name—Enter the name of the backup file.
STEP 4 If you selected via HTTP/HTTPS, you can only Upgrade. Enter the parameters as
described in this step.
• File Type—Select one of the following file types:
- Firmware Image—Select this to upgrade the firmware image.
- Language—Select this to upgrade the language file.
• File Name—Click Browse to select a file or enter the path and source file
name to be used in the transfer.
STEP 5 If you selected via SCP (Over SSH), see SSH Client Authentication for
instructions. Then, enter the following fields: (only unique fields are described, for
non-unique fields, see the descriptions above)
40 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Upgrade/Backup Firmware/Language
• Remote SSH Server Authentication—To enable SSH server authentication
(which is disabled by default), click Edit. This takes you to the SSH Server
Authentication page to configure the SSH server, and return to this page.
Use the SSH Server Authentication page to select an SSH user
authentication method (password or public/private key), set a username and
password on the device (if the password method is selected), and generate
an RSA or DSA key if required.
SSH Client Authentication—Client authentication can be done in one of the
following ways:
• Use SSH Client System Credentials—Sets permanent SSH user
credentials. Click System Credentials to go to the SSH User Authentication
page where the user/password can be set once for all future use.
• Use SSH Client One-Time Credentials—Enter the following:
4
- Username—Enter a username for this copy action.
- Password—Enter a password for this copy.
NOTE The username and password for one-time credential will not saved in
configuration file.
Select one of the following Save Actions:
• Upgrade—Specifies that the file type on the device is to be replaced with a
new version of that file type located on a TFTP server.
• Backup—Specifies that a copy of the file type is to be saved to a file on
another device.
Enter the following fields:
• File Type—Select the destination file type. Only valid file types are shown.
(The file types are described in the Files and File Types section).
• SCP Server Definition—Select whether to specify the SCP server by IP
address or by domain name.
• IP Version—Select whether an IPv4 or an IPv6 address is used.
• IPv6 Address Type—Select the IPv6 address type (if used). The options
are:
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 41
4
Administration: File Management
Active Image
- Link Local—The IPv6 address uniquely identifies hosts on a single
network link. A link local address has a prefix of FE80, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
- Global—The IPv6 address is a global Unicast IPv6 type that is visible and
reachable from other networks.
• Link-Local Interface—Select the link local interface from the list.
• SCP Server IP Address/Name—Enter the IP address or domain name of
the SCP server.
• (For Upgrade) Source File Name—Enter the name of the source file.
• (For Backup) Destination File Name—Enter the name of the backup file.
STEP 6 Click Apply. If the files, passwords and server addresses are correct, one of the
Active Image
following may happen:
• If SSH server authentication is enabled (in the SSH Server Authentication
page), and the SCP server is trusted, the operation succeeds. If the SCP
server is not trusted, the operation fails and an error is displayed.
• If SSH server authentication is not enabled, the operation succeeds for any
SCP server.
There are two firmware images stored on the device. One of the images is
identified as the active image and other image is identified as the inactive image.
The device boots from the image you set as the active image. You can change the
image identified as the inactive image to the active image. (You can reboot the
device by using the process described in the Management Interface section).
To select the active image:
STEP 1 Click Administration > File Management > Active Image.
The page displays the following:
• Active Image—Displays the image file that is currently active on the device.
42 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Download/Backup Configuration/Log
• Active Image Version Number—Displays the firmware version of the active
image.
• Active Image After Reboot—Displays the image that is active after reboot.
• Active Image Version Number After Reboot—Displays the firmware
version of the active image as it be after reboot.
STEP 2 Select the image from the Active Image After Reboot menu to identify the
firmware image that is used as the active image after the device is rebooted. The
Active Image Version Number After Reboot displays the firmware version of the
active image that is used after the device is rebooted.
STEP 3 Click Apply. The active image selection is updated.
4
Download/Backup Configuration/Log
The Download/Backup Configuration/Log page enables:
• Backing up configuration files or logs from the device to an external device.
• Restoring configuration files from an external device to the device.
NOTE If the device is working in stacking mode, the configuration files are taken from the
master unit.
When restoring a configuration file to the Running Configuration, the imported file
adds any configuration commands that did not exist in the old file and overwrites
any parameter values in the existing configuration commands.
When restoring a configuration file to the Startup Configuration or a backup
configuration file, the new file replaces the previous file.
When restoring to Startup Configuration, the device must be rebooted for the
restored Startup Configuration to be used as the Running Configuration. You can
reboot the device by using the process described in the Management Interface
section.
Configuration File Backwards Compatibility
When restoring configuration files from an external device to the device, the
following compatibility issues might arise:
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 43
4
Administration: File Management
Download/Backup Configuration/Log
• Change Queues Mode from 4 to 8—Queue-related configurations must be
examined and adjusted to meet QoS objectives with the new Queues
mode. See the CLI Reference Guide for a listing of these QoS commands.
• Change Queues Mode from 8 to 4—Queue-related configuration
commands that conflict with the new Queues mode are rejected, meaning
that the download of the configuration file fails. Use the System Mode and
Stack Management page to change the Queues mode.
• Change the System Mode—If the System mode is contained in a
configuration file that is downloaded to the device, and the file's System
mode matches the current System mode, this information is ignored.
Otherwise, if the System mode is changed, the following cases are
possible:
- If the configuration file is downloaded onto the device (using the
Download/Backup Configuration/Log page), the operation is aborted,
and a message is displayed indicating that the System mode must be
changed in the System Mode and Stack Management page.
- If the configuration file is downloaded during an automatic configuration
process, the Startup Configuration file is deleted and the device reboots
automatically in the new System mode. The device is configured with an
empty configuration file. See Auto Configuration via DHCP.
• See Configuration After Reboot for a description of what happens when
the stacking modes are changed.
Downloading or Backing-up a Configuration or Log File
To backup or restore the system configuration file:
STEP 1 Click Administration > File Management > Download/Backup Configuration/
Log.
STEP 2 Select the Transfer Method.
STEP 3 If you selected via TFTP, enter the parameters. Otherwise, skip to STEP 4.
44 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Download/Backup Configuration/Log
Select either Download or Backup as the Save Action.
Download Save Action—Specifies that the file on another device replaces a file
type on the device. Enter the following fields:
a. Server Definition—Select whether to specify the TFTP server by IP address
or by domain name.
b. IP Version—Select whether an IPv4 or an IPv6 address is used.
NOTE If the server is selected by name in the Server Definition, there is no
need to select the IP Version related options.
c. IPv6 Address Type—Select the IPv6 address type (if used). The options are:
- Link Local—The IPv6 address uniquely identifies hosts on a single
4
network link. A link local address has a prefix of FE80, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
- Global—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
d. Link-Local Interface—Select the link local interface from the list.
e. TFTP Server—Enter the IP address of the TFTP server.
f. Source File Name—Enter the source file name. File names cannot contain
slashes (\ or /), cannot start with a period (.), and must include between 1 and
160 characters. (Valid characters: A-Z, a-z, 0-9, “.”, “-”, “_”).
g. Destination File Type—Enter the destination configuration file type. Only valid
file types are displayed. (The file types are described in the Files and File
Types section).
Backup Save Action—Specifies that a file type is to be copied to a file on another
device. Enter the following fields:
a. Server Definition—Select whether to specify the TFTP server by IP address
or by domain name.
b. IP Version—Select whether an IPv4 or an IPv6 address is used.
c. IPv6 Address Type—Select the IPv6 address type (if used). The options are:
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 45
4
Administration: File Management
Download/Backup Configuration/Log
• Link Local—The IPv6 address uniquely identifies hosts on a single network
link. A link local address has a prefix of FE80, is not routable, and can be used
for communication only on the local network. Only one link local address is
supported. If a link local address exists on the interface, this entry replaces
the address in the configuration.
• Global—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
d. Link-Local Interface—Select the link local interface from the list.
e. TFTP Server IP Address/Name—Enter the IP address or domain name of the
TFTP server.
f. Source File Type—Enter the source configuration file type. Only valid file
types are displayed. (The file types are described in the Files and File Types
section).
g. Sensitive Data—Select how sensitive data should be included in the backup
file. The following options are available:
- Exclude—Do not include sensitive data in the backup.
- Encrypted—Include sensitive data in the backup in its encrypted form.
- Plaintext—Include sensitive data in the backup in its plaintext form.
NOTE The available sensitive data options are determined by the current
user SSD rules. For details, refer to Secure Sensitive Data Management >
SSD Rules page.
h. Destination File Name—Enter the destination file name. File names cannot
contain slashes (\ or /), the leading letter of the file name must not be a period
(.), and the file name must be between 1 and 160 characters. (Valid characters:
A-Z, a-z, 0-9, “.”, “-”, “_”).
i. Click Apply. The file is upgraded or backed up.
46 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Download/Backup Configuration/Log
STEP 4 If you selected via HTTP/HTTPS, enter the parameters as described in this step.
Select the Save Action.
If Save Action is Download (replacing the file on the device with a new version
from another device), do the following. Otherwise, go to the next procedure in this
step.
a. Source File Name—Click Browse to select a file or enter the path and source
file name to be used in the transfer.
b. Destination File Type—Select the configuration file type. Only valid file types
are displayed. (The file types are described in the Files and File Types
section).
c. Click Apply. The file is transferred from the other device to the device.
If Save Action is Backup (copying a file to another device), do the following:
4
a. Source File Type—Select the configuration file type. Only valid file types are
displayed. (The file types are described in the Files and File Types section).
b. Sensitive Data—Select how sensitive data should be included in the backup
file. The following options are available:
- Exclude—Do not include sensitive data in the backup.
- Encrypted—Include sensitive data in the backup in its encrypted form.
- Plaintext—Include sensitive data in the backup in its plaintext form.
NOTE The available sensitive data options are determined by the current
user SSD rules. For details, refer to Secure Sensitive Data Management >
SSD Rules page.
c. Click Apply. The file is upgraded or backed up.
STEP 5 If you selected via SCP (Over SSH), see SSH Client Configuration Through the
GUI for instructions. Then enter the following fields:
• Remote SSH Server Authentication—To enable SSH server authentication
(it is disabled by default), click Edit, which takes you to the SSH Server
Authentication page to configure this, and return to this page. Use the SSH
Server Authentication page to select an SSH user authentication method
(password or public/private key), set a username and password on the
device, if the password method is selected, and generate an RSA or DSA
key if required.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 47
4
Administration: File Management
Download/Backup Configuration/Log
SSH Client Authentication—Client authentication can be done in one of the
following ways:
• Use SSH Client—Sets permanent SSH user credentials. Click System
Credentials to go to the SSH User Authentication page where the user/
password can be set once for all future use.
• Use SSH Client One-Time Credentials—Enter the following:
- Username—Enter a username for this copy action.
- Password—Enter a password for this copy.
• SCP Server Definition—Select whether to specify the TFTP server by IP
address or by domain name.
• IP Version—Select whether an IPv4 or an IPv6 address is used.
• IPv6 Address Type—Select the IPv6 address type (if used). The options
are:
- Link Local—The IPv6 address uniquely identifies hosts on a single
network link. A link local address has a prefix of FE80, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
- Global—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
• Link-Local Interface—Select the link local interface from the list.
• SCP Server IP Address/Name—Enter the IP address or domain name of
the TFTP server.
If Save Action is Download (replacing the file on the device with a new version
from another device), enter the following fields.
• Source File Name—Enter the name of the source file.
• Destination File Type—Select the configuration file type. Only valid file
types are displayed. (The file types are described in the Files and File
Types section).
48 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Configuration Files Properties
If Save Action is Backup (copying a file to another device), enter the following
fields (in addition to those fields listed above):
• Source File Type—Select the configuration file type. Only valid file types
are displayed. (The file types are described in the Files and File Types
section).
• Sensitive Data—Select how sensitive data should be included in the
backup file. The following options are available:
- Exclude—Do not include sensitive data in the backup.
- Encrypted—Include sensitive data in the backup in its encrypted form.
- Plaintext—Include sensitive data in the backup in its plaintext form.
NOTE The available sensitive data options are determined by the current
user SSD rules. For details, refer to Secure Sensitive Data Management >
SSD Rules page.
4
• Destination File Name—Name of file being copied to.
STEP 6 Click Apply. The file is upgraded or backed up.
Configuration Files Properties
The Configuration Files Properties page allows you to see when various system
configuration files were created. It also enables deleting the Startup Configuration
and Backup Configuration files. You cannot delete the other configuration file
types.
NOTE If the device is working in stack mode, the configuration files are taken from the
master unit.
To set whether mirror configuration files will be created, clear configuration files
and see when configuration files were created:
STEP 1 Click Administration > File Management > Configuration Files Properties.
This page displays the following fields:
• Configuration File Name—Type of system file.
• Creation Time—Date and time that file was modified.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 49
4
STEP 2 If required, disable Auto Mirror Configuration. This disables the automatic
creation of mirror configuration files. When disabling this feature, the mirror
configuration file, if it exists, is deleted. See System Files for a description of
mirror files and why you might not want to automatically create mirror
configuration files.
STEP 3 If required, select either the Startup Configuration, Backup Configuration or both
and click Clear Files to delete these files.
Copy/Save Configuration
When you click Apply on any window, changes that you made to the device
configuration settings are stored only in the Running Configuration. To preserve
the parameters in the Running Configuration, the Running Configuration must be
copied to another configuration type or saved on another device.
Administration: File Management
Copy/Save Configuration
!
CAUTION Unless the Running Configuration is copied to the Startup Configuration or another
configuration file, all changes made since the last time the file was copied are lost
when the device is rebooted.
The following combinations of copying internal file types are allowed:
• From the Running Configuration to the Startup Configuration or Backup
Configuration.
• From the Startup Configuration to the Running Configuration, Startup
Configuration or Backup Configuration.
• From the Backup Configuration to the Running Configuration, Startup
Configuration or Backup Configuration.
• From the Mirror Configuration to the Running Configuration, Startup
Configuration or Backup Configuration.
To copy one type of configuration file to another type of configuration file:
STEP 1 Click Administration > File Management > Copy/Save Configuration.
STEP 2 Select the Source File Name to be copied. Only valid file types are displayed
(described in the Files and File Types section).
STEP 3 Select the Destination File Name to be overwritten by the source file.
50 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Auto Configuration via DHCP
• If you are backing up a configuration file, select one of the following formats
for the backup file.
- Exclude—Sensitive data is not included in the backup file.
- Encrypted—Sensitive data is included in the backup file in encrypted
- Plaintext—Sensitive data is included in the backup file in plain text.
NOTE The available sensitive data options are determined by the current
user SSD rules. For details, refer to Secure Sensitive Data Management >
SSD Rules page.
STEP 4 The Save Icon Blinking field indicates whether an icon blinks when there is
unsaved data. To disable/enable this feature, click Disable/Enable Save Icon
Blinking.
4
form.
STEP 5 Click Apply. The file is copied.
Auto Configuration via DHCP
DHCP auto configuration enables passing configuration information to hosts on a
TCP/IP network. Based on this protocol, the Auto Configuration feature enables a
device to download configuration files from a TFTP/SCP server.
To use this feature, the device must be configured as a DHCPv4 client in which
case auto configuration from a DHCPv4 server is supported and/or a DHCPv6
client in which case auto configuration from a DHCPv6 server is supported.
By default, the device is enabled as a DHCP client when the Auto Configuration via
DHCP feature is enabled.
The Auto Configuration process also supports downloading a configuration file
that includes sensitive information, such as RADIUS server keys and SSH/SSL
keys, by using the Secured Copy Protocol (SCP) and the Secure Sensitive Data
(SSD) feature (See Security: Secure Sensitive Data Management).
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 51
4
Administration: File Management
Auto Configuration via DHCP
Auto Configuration via DHCPv4 is triggered in the following cases:
• After reboot when an IP address is allocated or renewed dynamically (using
DHCPv4).
• Upon an explicit DHCPv4 renewal request and if the device and the server
are configured to do so.
• Upon automatic renewal of the DHCPv4 lease.
Auto Configuration via DHCPv6 is triggered when the following conditions are
fulfilled:
• When a DHCPv6 server sends information to the device. This occurs in the
following cases:
- When an interface, which is IPv6 enabled, is defined as a DHCPv6
stateless configuration client.
- When DHCPv6 messages are received from the server (for example,
when you press the Restart button on IPv6 Interfaces page,
- When DHCPv6 information is refreshed by the device.
- After rebooting the device when stateless DHCPv6 client is enabled.
• When the DHCPv6 server packets contain the configuration filename
option.
DHCP Server Options
DHCP messages might contain the configuration server name/address and the
configuration file name/path (these are optional options). These options are found
in the Offer message coming from the DHCPv4 servers and in the Information
Reply messages coming from DHCPv6 servers.
Backup information (configuration server name/address and configuration file
name/path) can be configured in the Auto Configuration page. This information is
used when the DHCPv4 message does not contain this information (but it is not
used by DHCPv6).
52 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Auto Configuration via DHCP
Auto Configuration Download Protocol (TFTP or SCP)
The Auto Configuration download protocol can be configured, as follows:
• Auto By File Extension—(Default) If this option is selected, a user-defined
file extension indicates that files with this extension are downloaded using
SCP (over SSH), while files with other extensions are downloaded using
TFTP. For example, if the file extension specified is.xyz, files with the .xyz
extension are downloaded using SCP, and files with the other extensions
are downloaded using TFTP.
• TFTP Only—The download is done through TFTP regardless of the file
extension of the configuration file name.
• SCP Only—The download is done through SCP (over SSH) regardless of
the file extension of the configuration file name.
4
SSH Client Authentication Parameters
By default, remote SSH server authentication is disabled, so that the device
accepts any remote SSH server out of the box. You can enable remote SSH server
authentication to only allow connections from servers found in the trusted server
list.
SSH Client Authentication parameters are required to access the SSH server by
the client (which is the device). The default SSH Client authentication parameters
are:
• SSH Authentication method: by username/password
• SSH username: anonymous
• SSH password: anonymous
NOTE The SSH Client authentication parameters can also be used when downloading a
file for manual download (a download that is not performed through the DHCP Auto
Configuration feature).
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 53
4
Administration: File Management
Auto Configuration via DHCP
Auto Configuration Process
When the Auto Configuration process is triggered, the following sequence of
events occurs:
• The DHCP server is accessed to acquire the TFTP/SCP server name/
address and configuration file name/path (DHCPv4 options: 66,150, and 67,
DHCPv6 options: 59 and 60).
• If a server and configuration file options were not supplied by the DHCP
server, then:
- For DHCPv4: The user-defined, backup configuration file name is used.
- For DHCPv6: The process is halted.
• If the DHCP server did not send these options and the backup TFTP/SCP
server address parameter is empty then:
- For DHCPv4:
SCP—The Auto Configuration process is halted.
TFTP—The device sends TFTP Request messages to a limited
Broadcast address (for IPv4) or ALL NODES address (for IPv6) on its IP
interfaces and continues the process of Auto Configuration with the first
answering TFTP server.
- For DHCPv6: The Auto Configuration process is halted.
• If the configuration filename was supplied by the DHCP server (DHCPv4:
option 67, DHCPv6: option 60), then the copy protocol (SCP/TFTP) is
selected as described in Auto Configuration Download Protocol (TFTP or
SCP).
• When downloading using SCP, the device accepts any specified SCP/SSH
server (without authentication) if either of the following is true:
- The SSH server authentication process is disabled. Note that by default
the SSH server authentication is disabled in order to allow downloading
configuration file for devices with factory default configuration (for
example out-of-box devices).
- The SSH Server is configured in the SSH Trusted Servers list.
If the SSH server authentication process is enabled, and the SSH server is
not found in the SSH Trusted Servers list, the Auto Configuration process is
halted.
54 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration: File Management
Auto Configuration via DHCP
• If the information is available, the TFTP/SCP server is accessed to download
the file from it.
The download process is done only if the new configuration filename is
different from the current configuration filename (even if the current
configuration file is empty).
• A SYSLOG message is generated acknowledging that the Auto
Configuration process is completed.
Configuring DHCP Auto Configuration
Workflow
To configure DHCP Auto Configuration.
1. Configure the DHCPv4 and/or DHCPv6 servers to send the required options.
this process is not described in this guide.
4
2. Configure Auto Configuration parameters.
3. Def ine the device as a DHCP v4 client i n the Defining an IPv4 Interface in Layer
2 System Mode or Defining IPv4 Interface in Layer 3 System Mode pages,
and/or define the device as a DHCPv6 client in the IPv6 Interface page.
Web Configuration
The DHCP Auto Configuration page is used to perform the following actions when
the information is not provided in a DHCP message:
• Enable the DHCP auto configuration feature.
• Specify the download protocol.
• Configure the device to receive configuration information from a specific file
on a specific server.
Note the following regarding the DHCP auto configuration process:
• A configuration file that is placed on the TFTP/SCP server must match the
form and format requirements of the supported configuration file. The form
and format of the file are checked, but the validity of the configuration
parameters is not checked prior to loading it to the Startup Configuration.
• In IPv4, to ensure that the device configuration functions as intended, due to
allocation of different IP addresses with each DHCP renew cycle, it is
recommended that IP addresses be bound to MAC addresses in the DHCP
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 55
4
Administration: File Management
Auto Configuration via DHCP
server table. This ensures that each device has its own reserved IP address
and other relevant information.
To configure auto configuration:
STEP 1 Click Administration > File Management > DHCP Auto Configuration.
STEP 2 Enter the values.
• Auto Configuration Via DHCP—Select this field to enable DHCP Auto
Configuration. This feature is enabled by default, but can be disabled here.
• Download Protocol—Select one of the following options:
Auto By File Extension
-
the TFTP or SCP protocol depending on the extension of the
configuration file. If this option is selected, the extension of the
configuration file does not necessarily have to be given. If it is not given,
the default extension is used (as indicated below).
-
File Extension for SCP
indicate a file extension here. Any file with this extension is downloaded
using SCP. If no extension is entered, the default file extension.scp is
used.
-
TFTP Only
for auto configuration.
SCP Only
-
auto configuration.
• SSH Settings for SCP—When using SCP for downloading the configuration
files, select one of the following options:
Remote SSH Server Authentication
-
navigate to the SSH Server Authentication page. There you can enable
authentication of the SSH server to be used for the download and enter
the trusted SSH server if required.
—Select to indicate that only the TFTP protocol is to be used
—Select to indicate that only the SCP protocol is to be used for
—Select to indicate that auto configuration uses
—If Auto By File Extension is selected, you can
—Click on the Enable/Disable link to
-
SSH Client Authentication
user credentials in the SSH User Authentication page.
STEP 3 Enter the following optional information to be used if no configuration file name
was received from the DHCP server.
• Backup Server Definition—Select By IP address or By name to configure
the server.
56 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
—Click on the System Credentials link to enter
Administration: File Management
Auto Configuration via DHCP
• IP Version—Select whether an IPv4 or an IPv6 address is used.
• IPv6 Address Type—Select the IPv6 address type (if IPv6 is used). The
options are:
- Link Local—The IPv6 address uniquely identifies hosts on a single
- Global—The IPv6 address is a global Unicast IPV6 type that is visible and
• Link Local Interface—Select the link local interface (if IPv6 is used) from the
list.
• Backup Server IP Address/Name—Enter the IP address or the name of the
server to be used if no server IP address was specified in the DHCP
message.
4
network link. A link local address has a prefix of FE80, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
reachable from other networks.
• Backup Configuration File Name—Enter the path and file name of the file to
be used if no configuration file name was specified in the DHCP message.
STEP 4 Click Apply. The parameters are copied to the Running Configuration file.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 57
Administration: Stack Management
This section describes how stacks are managed. It covers the following topics:
• Overview
• Types of Units in Stack
• Stack Topology
• Unit ID Assignment
• Master Selection Process
• Stack Changes
• Unit Failure in Stack
5
Overview
• Software Auto Synchronization in Stack
• Stack Unit Mode
• Stack Ports
• Default Configuration
• Interactions With Other Features
• System Modes
Devices can either function on their own (Standalone mode), or they can be
connected into a stack of up to eight devices in various stacking modes (see
Stack Unit Mode).
The devices (units) in a stack are connected through stack ports. These devices
are then collectively managed as a single logical device.
The stack is based on a single master/backup and multiple slaves model.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 58
Administration: Stack Management
Overview
An example of eight devices connected into a stack is shown in the following:
Stack Architecture (Chain Topology)
5
A stack provides the following benefits:
• Network capacity can be expanded or contracted dynamically. By adding a
unit, the administrator can dynamically increase the number of ports in the
stack while maintaining a single, logically-managed device. Similarly, units
can be removed to decrease network capacity.
• The stacked system supports redundancy in the following ways:
- The backup unit becomes the master of the stack if the original master
fails.
- The stack system supports two types of topologies: chain (see “Stack
Architecture (Chain Topology)”and ring (see “Stack in Ring
To po lo g y” ). In ring topology, if one of the stack ports fails, the stack
continues to function in chain topology (see Stack Topology).
- A process known as Fast Stack Link Failover is supported on the ports in
a ring stack to reduce the duration of data packet loss when one of the
stack ports link fails. Until the stack recovers to the new chain topology,
the stack port that is currently down, loops back the packets that were
supposed to be sent through it, so that the packets arrive at their
destination using the remaining stacking links. During Fast Stack Link
failover, the master/backup units remain active and functioning.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 59
Administration: Stack Management
Types of Units in Stack
Types of Units in Stack
A stack consists of a maximum of eight units. A unit in a stack is one of the
following types:
• Master—The master unit’s ID must be either 1 or 2. The stack is managed
through the master unit that manages itself, the backup unit and the slave
units.
• Backup—If the master unit fails, the backup unit assumes the master role
(switchover). The backup unit’s ID must be either 1 or 2.
• Slave—These units are managed by the master unit.
In order for a group of units to function as a stack, there must be a master-enabled
unit. When the master-enabled unit fails, the stack continues to function as long as
there is a backup unit (the active unit that assumes the master role).
5
If the backup unit fails, in addition to the master, and the only functioning units are
the slave units, these also stop functioning after one minute. This means for
example, that if after 1 minute, you plug in a cable to one of the slave units that was
running without a master, the link will not come up.
Backward Compatibility of Number of Units in Stack
Previous versions of the device supported a maximum of four units as opposed to
the current version that supports eight units. Upgrading from earlier software
releases can be done without changing the configuration files.
When a firmware version, which does not support the hybrid stack modes is
loaded to the stack and the stack is rebooted, the stack reverts to Native Stack
mode. When a device in Hybrid stack mode is loaded with a firmware version that
does not support Hybrid stack mode, its system mode will revert to the default
system mode (SG500X/EWS2-550X: L3 and L2, Sx500: L2).
If a stack whose unit IDs are manually-configured, those units whose ID is greater
than 4 are switched to auto numbering.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 60
Administration: Stack Management
Types of Units in Stack
Unit LEDs
The device has 4 LEDs marked as 1, 2, 3, 4, which are used to display the unit ID of
each unit (e.g. on Unit ID 1, LED 1 is ON and the other LEDs are OFF). To support unit
IDs greater than 4, the LED display is changed in accordance to the below
definition:
• Units 1-4: LEDs 1-4 are lit, respectively.
• Unit 5: LED 1 and 4 are lit.
• Unit 6: LED 2 and 4 are lit.
• Unit 7: LED 3 and 4 are lit.
• Unit 8: LED 1, 3, and 4 are lit.
5
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 61
Administration: Stack Management
Stack Topology
Stack Topology
Types of Stack Topology
The units in a stack can be connected in one of the following types of topologies:
Chain Topology—One stack port (either left or right) of the first unit is connected to
the stack port in the second unit. All units in the stack are connected to the stack
port in the next unit except for the first and last unit. “Stack Architecture (Chain
To po lo g y) ” shows a chain topology.
Ring Topology—All the units in the stack are connected in a chain. The last unit is
connected to the first unit. The following shows a ring topology of an eight-unit
stack:
5
Stack in Ring Topology
A ring topology is more reliable than a chain topology. The failure of one link in a
ring does not affect the function of the stack, whereas the failure of one link in a
chain connection might cause the stack to be split.
Topology Discovery
A stack is established by a process called topology discovery. This process is
triggered by a change in the up/down status of a stack port.
The following are examples of events that trigger this process:
• Changing the stack topology from a ring to a chain
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 62
Administration: Stack Management
Unit ID Assignment
• Merging two stacks into a single stack
• Splitting the stack
• Inserting other slave units to the stack, for instance because the units were
previously disconnected from the stack due to a failure. This can happen in
a chain topology if a unit in the middle of the stack fails.
During topology discovery, each unit in a stack exchanges packets, which contain
topology information.
After the topology discovery process is completed, each unit contains the stack
mapping information of all units in the stack.
Unit ID Assignment
5
After topology discovery is completed, each unit in a stack is assigned a unique
unit ID.
The unit ID is set in the System Mode and Stack Management page in one of the
following ways:
• Automatically (Auto)—The Unit ID is assigned by the topology discovery
process. This is the default setting.
• Manually—The unit ID is manually set to an integer from 1-8. In addition,
manual numbering includes the following options:
- 1 - Force Master—Forces unit 1 to be the master.
- 2 - Force Master—Forces unit 2 to be the master.
Duplicate Unit IDs
If you assign the same unit ID to two separate units, only one of them can join the
stack with that unit ID.
If auto numbering has been selected, the duplicate unit is assigned a new unit
number. If auto numbering was not selected, the duplicate unit is shut down.
The following examples show where unit ID duplication might occur.
The following shows a case where two units were manually assigned the same
unit ID. Unit 1 does not join the stack and is shut down. It did not win the master
selection process between the master-enabled units (1 or 2).
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 63
Administration: Stack Management
Unit ID Assignment
Duplicate Unit Shut Down
The following shows a case where one of the duplicate units (auto-numbered) is
renumbered.
5
Duplicate Unit Renumbered
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 64
Administration: Stack Management
Master Selection Process
The following shows a case where one of the duplicate units is renumbered. The
one with the lower MAC retains its unit ID (see Master Selection Process for a
description of this process).
Duplication Between Two Units With Auto Number Unit ID
5
NOTE If a new stack has more than the maximum number of units (8), all extra units are shut
down.
Master Selection Process
The master unit is selected from the master-enabled units (1 or 2). The factors in
selecting the master unit are taken into account in the following priority:
• Force Master—If Force Master is activated on a unit, it is selected.
• System Up Time—The master-enabled units exchange up-time, which is
measured in segments of 10 minutes. The unit with the higher number of
segments is selected. If both units have the same number of time segments,
and the unit ID of one of the units was set manually while the other unit’s unit
ID was set automatically, the unit with the manually-defined unit ID is
selected; otherwise the unit with the lowest unit ID is selected. If both units
IDs are the same, the unit with the lowest MAC address is chosen. Note:
The up time of the backup unit is retained when it is selected as master in
the switch failover process.
• Unit ID—f both units have the same number of time segments, the unit with
the lowest unit ID is selected.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 65
Administration: Stack Management
Stack Changes
• MAC Address—If both units IDs are the same, the unit with the lowest MAC
address is chosen.
NOTE For a stack to operate, it must have a master unit. A master unit is defined as the
active unit that assumes the master role. The stack must contain a unit 1 and/or unit
2 after the master selection process. Otherwise, the stack and all its units are
partially shut down, not as a complete power-off, but with traffic-passing
capabilities halted.
Stack Changes
This section describes various events that can cause a change to the stack. A
stack topology changes when one of the following occurs:
• One or more units are connecting and/or disconnecting to and from the
stack.
5
• Any of its stack ports has a link up or down.
• The stack changes between ring and chain formation.
When units are added or removed to and from a stack, it triggers topology
changes, master election process, and/or unit ID assignment.
Connecting a New Unit
When a unit is inserted into the stack, a stack topology change is triggered. The
unit ID is assigned (in case of auto numbering), and the unit is configured by the
master.
One of the following cases can occur when connecting a new unit to an existing
stack:
• No duplicate unit IDs exist.
- Units with user-defined IDs retain their unit ID.
- Units with automatically-assigned IDs retain their unit ID.
- Factory default units receive unit IDs automatically, beginning from the
lowest available ID.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 66
Administration: Stack Management
Stack Changes
• One or more duplicate unit IDs exist. Auto numbering resolves conflicts and
assigns unit IDs. In case of manual numbering, only one unit retains its unit ID
and the other(s) are shutdown.
• The number of units in the stack exceeds the maximum number of units
allowed. The new units that joined the stack are shut down, and a SYSLOG
message is generated and appears on the master unit.
The following shows an example of auto numbering when a master-enabled unit
joins the stack. There are two units with unit ID = 1. The master selection process
selects the best unit to be the master unit. The best unit is the unit with the higher
uptime in segments of 10 minutes. The other unit is made the backup.
Auto-numbered Master-enabled Unit
5
The following shows an example of auto numbering when a new unit joins the
stack. The existing units retain their ID. The new unit receives the lowest available
ID.
Auto Number Unit
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 67
Administration: Stack Management
Unit Failure in Stack
The following shows what happens when a user-assigned, master-enabled unit
with Unit ID 1 joins a stack that already has a master unit with user-assigned unit ID
1. The newer Unit 1 does not join the stack and is shutdown.
User-assigned Master-enabled Unit
5
Unit Failure in Stack
Failure of Master Unit
If the Master fails, the backup unit takes over the master role and continues to
operate the stack normally.
In order for the backup to be able to take the place of the master, both units
maintain a warm standby at all times. In warm standby, the master and its backup
units are synchronized with the static configuration (contained in both the Startup
and Running configuration files). Backup configuration files are not synchronized.
The backup configuration file remains on the previous master.
Dynamic process-state information, such as the STP state table, dynamicallylearned MAC addresses, dynamically-learned Smartport types, MAC Multicast
tables, LACP, and GVRP are not synchronized.
When a master is being configured, it synchronizes the backup immediately.
Synchronization is performed as soon as a command is executed. This is
transparent.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 68
Administration: Stack Management
Unit Failure in Stack
If a unit is inserted into a running stack, and is selected as a backup unit, the master
synchronizes it so that it has an up-to date configuration, and then generates a
SYNC COMPLETE SYSLOG message. This is a unique SYSLOG message that
appears only when backup is converging with the master unit, and looks like this:
%DSYNCH-I-SYNCH_SUCCEEDED: Synchronization with unit 2 is finished
successfully.
Master/Backup Switchover
When a master fails or when you configure a force master on the backup unit, a
switchover occurs.
The backup unit becomes the master, and all of its processes and protocol stacks
are initialized to take responsibility for the entire stack. As a result, there is
temporarily no traffic forwarding in this unit, but slave units remain active.
NOTE When STP is used and the ports are in link up, the STP port’s state is temporarily
Blocking, and it cannot forward traffic or learn MAC addresses. This is to prevent
spanning tree loops between active units.
5
Slave Unit Handling
While the backup becomes the master, the active slave units remain active and
continue to forward packets based on the configuration from the original master.
This minimizes data traffic interruption in units.
After the backup unit has completed the transition to the master state, it initializes
the slave units one at a time by performing the following operations:
• Clear and reset the configuration of the slave unit to default (to prevent an
incorrect configuration from the new master unit). As a result, there is no
traffic forwarding on the slave unit.
• Apply related user configurations to the slave unit.
• Exchange dynamic information such as port STP state, dynamic MAC
addresses, and link up/down status between the master and the slave unit.
Packet forwarding on the slave unit resumes after the state of its ports are
set to forwarding by the master according to STP.
NOTE Packet flooding to unknown unicast MAC addresses occurs until the
MAC addresses are learned or relearned.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 69
Administration: Stack Management
Software Auto Synchronization in Stack
Reconnecting the Original Master Unit After Failover
After failover, if the original master is connected again, the master selection
process is performed. If the original master (unit 1) is reselected to be the master,
the current master (unit 2, which was the original backup unit) is rebooted and
becomes the backup once again.
NOTE During master/backup failover, the up time of the backup unit is retained.
Software Auto Synchronization in Stack
All the units in the stack must run the same software version (firmware and
bootcode). Each unit in a stack automatically downloads firmware and bootcode
from the master unit if the firmware and/or boot code that the unit and the master
are running is different. The unit automatically reboots itself to run the new version.
5
Stack Unit Mode
The stack unit mode of a device indicates whether it can be part of a stack or
whether it is operating on its own.
Devices can operate in one of the following stack unit modes:
• Standalone—A device in Standalone stack unit mode is not connected to
any other device and does not have a stack port.
• Native Stacking—A device in Native Stacking mode can be connected to
other devices of the same type through its stack ports to form a stack. All
units in a native stack must be of the same type (either all Sx500s, all
SG500Xs/ESW2-550Xs or all SG500XGs).
• Basic Hybrid—A device in Basic Hybrid mode can be connected to
Sx500and SG500X/ESW2-550X devices to form a stack. The only limitation
(and the reason that this mode is called Basic Hybrid as opposed to
Advanced Hybrid) is that there is no support for VRRP or RIP. In this mode,
the GUI displays the pages of Sx500, even if the stack master is a SG500X/
ESW2-550X, since the feature set is that of the Sx500.
In this mode, any type of device can take the master/backup roles. Only the
5G stacking ports can be used as stack ports.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 70
Administration: Stack Management
Stack Unit Mode
• Advanced Hybrid—A device in Advanced Hybrid mode can be connected
to Sx500 and SG500X/ESW2-550X devices to form a stack. In this mode,
VRRP and/or RIP are supported, but auto numbering of units is not
supported, because only the SG500Xor ESW2-550X devices can function
as master/backup.
Sx500 devices can only be slaves, therefore up to 6 Sx500 units can be
stacked together with two SG500X/ESW2-550Xs devices.
• Advanced Hybrid XG—A device in Advanced Hybrid XG mode can be
connected to SG500X/ESW2-550X and SG500XG devices to form a stack.
All units can be master or slave units.
Stack Configuration Options
5
The following describes some typical stack configurations:
Possible Stack Configuration Possible RIP/
VRRP
Support
Stack consists of all SG500Xs in
Native Stacking mode.
Stack consists of all ESW2-550Xs
in Native Stacking mode.
Stack consists of all Sx500s in
Native Stacking mode.
Stack consists of mixed device
types in Basic Hybrid mode.
• Master: Either SG500X,
ESW2-550X or Sx500s
• Backup: Either type of
device
• Slaves: Either type of device
Enabled/
Disabled
Enabled/
Disabled
Not
supported.
Not
supported.
Stack Ports Speed
1G/10G or 1G/5G
1G/10G or 1G/5G
1G/5G (default) or 1G
Copper/SFP (Combo)
1G/5G
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 71
Administration: Stack Management
Stack Unit Mode
5
Possible Stack Configuration Possible RIP/
VRRP
Support
Stack consists of mixed device
types in Advanced Hybrid mode.
• Master: SG500X
• Backup: SG500X
• Slaves: Either type of device
Stack consists of mixed device
types in Advanced Hybrid XG
mode.
• Master: SG500X/ESW2-
550X or SG500XG
• Backup: SG500X/ESW2-
550X or SG500XG
• Slaves: Either type of device
Enabled/
Disabled
Enabled/
Disabled
Stack Ports Speed
1G/5G
1 G or 10G
Consistency of Stack Unit Modes in the Stack
All units in the stack must have the same stack unit mode.
When the stack is initialized, it runs a topology discovery algorithm that collects
information on the units of the stack.
After a unit is selected to become the master, it can reject its neighbor’s request to
join the stack if it has an inconsistent stack unit mode. When a unit is rejected
because of its stack unit mode, it is logically shutdown (the ports cannot send/
receive traffic) and all its LEDs (system, FAN, unit IDs, network ports and stack
ports LEDs) are turned on. The information regarding the stack unit mode is
displayed as a SYSLOG error in the master unit.
Note that the only way for the unit to recover from this mode is by unplugging its
electricity and plugging it back in.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 72
Administration: Stack Management
Stack Unit Mode
Changing the Stack Unit Mode
Change the stack unit mode of a device to remove it from a stack (by changing its
stack unit mode to Standalone), or when configuring it to become part of a stack
(by changing its stack unit mode to Native Stacking, Basic Hybrid Stacking or
Advanced Hybrid Stacking).
The following sections describe the system mode and configuration of the
devices after reboot when the stack unit mode is changed.
System Mode (500 Devices) After Reboot
When the stack mode of a device is changed, the system mode of the device may
be changed after reboot:
• Sx500 devices—The system mode (Layer 2 or Layer 3) of the backup and
slave Sx500 units is taken from the master-enabled unit. If the system mode
is not specifically set before reboot, it is Layer 2 after reboot (this is the
default). If you want the device to be in Layer 3 mode after reboot, this must
be specifically set before reboot.
5
• SG500X/ESW2-550X devices—When the device is in Standalone or
Native Stacking mode, its system mode is always Layer 2 and 3. When the
device is in Basic or Advanced Hybrid mode, it behaves as described
above for Sx500 devices. When the device is in Advanced Hybrid XG mode,
its system mode is always Layer 2 and 3.
• SG500XG devices—Always Layer 2 and Layer 3.
Configuration After Reboot
When you change the stack mode of a device and reboot the device, the Startup
Configuration file is usually removed because it may contain configuration
information that is not applicable to the new mode.
It is retained after bootup in the following cases:
• SG500X/ESW2-550X devices:
- Standalone to Native Stacking—Retained only when the unit is forced
to become the master with unit ID = 1
- Basic Hybrid to Advanced Hybrid—Retained only when the unit is
forced to become the master with unit ID = 1
- Basic Hybrid to Advanced Hybrid XG—Retained only when the unit is
forced to become the master with unit ID = 1
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 73
Administration: Stack Management
Stack Ports
• SG500XG:
- Standalone to Native Stacking—Retained only when the unit is forced
to become the master unit with unit ID = 1
- Native to Advanced Hybrid XG—Retained only when the unit is forced
to become the master unit with unit ID = 1
• Sx500 devices:
- Standalone to Native Stacking—Retained only when the unit is forced
to become the master unit with unit ID = 1
- Standalone to Basic Hybrid—Retained only when the unit is forced to
become the master with unit ID = 1
- Native Stacking to Basic Hybrid—Retained only when the unit is
forced to become the master with unit ID = 1
5
Stack Ports
Ports in a stack must be reserved to be one of the following port types:
• Network Ports—Also known as uplink ports. These are ports that are
connected to the network.
• Stack Ports—Ports that connect two units in a stack. Stack ports are used
to transfer data and protocol packets among the units.
You must indicate to the system (reserve) which ports you plan to use as stack
ports (in the System Mode and Stack Management page). All ports that are not
reserved to be stack ports, are considered to be network ports.
Default Stack and Network Ports
The following are the default stack and network ports:
• Sx500 Devices—When an Sx500 device operates in Native Stacking
mode, S1-S2-1G operate as regular network ports, and S3-S4-5G operate
as stack ports by default.
• SG500X/ESW2-550X Devices—S1-S2-10G are stack ports by default.
You can manually reconfigure S1-S2-10G and S1-S2-5G as network ports or
stack ports.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 74
Administration: Stack Management
Stack Ports
• SG500XG Devices—Any ports can be stack or network. By default the
device is standalone.
When you convert a device from one of the Stacking modes to Standalone mode,
all its stack ports automatically become regular network ports.
5
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 75
Administration: Stack Management
Stack Ports
Pairs of Ports
The following table describes the pairs of ports that are available on the device in
the various stack unit modes:
5
Device Type/
Pair of Ports
Sx500
S3-S4 5G Stack
Sx500
Combo slot 1G
Fiber/Copper
S1-S2 1G Stack
SG500X/ESW2550X
S1-S2 5G Stack
S1-S2 10G Stack
SG500XG
XG1- XG16 ports.
These are 10G
slots.
Stacking Standalone
• Native Stacking mode: Available
as both network and stack ports
• Hybrid Modes: Available as stack
ports
• Native Stacking mode: Available
as both network and stack ports
• Hybrid Modes: Available as
network ports
• Native Stacking mode: 5G slot or
10G slot available.
• Hybrid Modes: Only 5G slot
available.
• Native Stacking mode: 1G or 10G
ports available.
• Hybrid Modes: 1G or 10G ports
available.
Ava il ab le as
network
port
Ava il ab le as
network
port
Only
available as
10G slot
Ava il ab le as
network
ports
Port Speeds
The speed of stack ports can be set manually or set to auto selection. The
following describes the available types of stack ports and their speeds on the
various types of devices:
Device Type Port Pair Possible Speeds in
Stack
Sx500 S1-S2 1G No
Sx500 S3-S4 5G/1G Yes
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 76
Auto Speed
Selection
Available
Administration: Stack Management
Stack Ports
5
Device Type Port Pair Possible Speeds in
Stack
SG500X/
ESW2-550X
SG500X/
ESW2-550X
SG500XG Any pair of ports
S1-S 2-XG 10 G/1G Yes
S1-S 2- 5G 5G /1 G Yes
1G or 10G Yes
from XG1 - XG16
Auto Speed
Selection
Available
Auto Selection of Port Speed
You can set the stacking cable type to be discovered automatically when the
cable is connected to the port (auto-discovery is the default setting). The system
automatically identifies the stack cable type and selects the highest speed
supported by the cable and the port.
A SYSLOG message (informational level) requesting that the user configures the
port speed manually is displayed when the cable type is not recognized.
Connecting Units
Two units can only be connected in a stack if the ports on both ends of the link are
of the same speed. This is done by configuring the stack ports speed to:
• Auto Speed mode
• Same speed on each side of the connection
Cables Types
Each type of stack port can be used with specific cable types.
When the stack mode is set to Native Stacking, you can use either a fiber or
copper cable as a stacking cable. If both cables (Fiber and Copper) are
connected, fiber is the preferred media. Dual connection can be used for
redundancy. When a media change occurs, for example you disconnect the fiber
stacking cable and the copper stacking cable becomes active, the system initiates
a topology change event.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 77
Administration: Stack Management
Stack Ports
The following describes the possible combinations of cables types and ports.
Stack Ports Network Ports
Connector Type S1-S2-5G
for
SG500X/
ESW2550X and
S3-S4 for
Sx500
S1, S2 in
Sx500
S1,S2 - XG
in SG500X/
ESW2550X
S1,S2 - 5G
for
SG500X
and S3, S4
for Sx500
S1,S2 in
Sx500
5
S1,S2 - XG
in SG500X
Cisco SFPH10G B-CU1M –
Passive Copper
Cable
Cisco SFPH10G B-CU 3M –
Passive Copper
Cable
Cisco SFPH10G B-CU 5M –
Passive Copper
Cable
Cisco SFP-10G-SRNot
Cisco SFP-10GLRM
Cisco SFP-10G-LRNot
1G SFP Module
MGBSX1
5G 1G 10G1G1G10G
5G 1G 10G1G1G10G
5G 1G 10G1G1G10G
supported
Not
supported
supported
1G 1G 1G 1G 1G 1G
Not
supported
Not
supported
Not
supported
10G Not
supported
10G Not
supported
10G Not
supported
Not
supported
Not
supported
Not
supported
10G
10G
10G
1G SFP Module
MGBT1
1G SFP Module
MGBLX1
1G SFP Module
MGBBX1
100Mbs SFP
Module MFELX1
100Mbs SFP
Module MFEFX1
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 78
1G 1G 1G 1G 1G 1G
1G 1G 1G 1G 1G 1G
1G 1G 1G 1G 1G 1G
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
100Mbs Not
supported
100Mbs Not
supported
Administration: Stack Management
Stack Ports
Stack Ports Network Ports
Connector Type S1-S2-5G
for
SG500X/
ESW2550X and
S3-S4 for
Sx500
100Mbs SFP
Module MFEBX1
Other SFPs 1G According
Not
supported
S1, S2 in
Sx500
Not
supported
to:
S1,S2 - XG
in SG500X/
ESW2550X
Not
supported
According
to:
S1,S2 - 5G
for
SG500X
and S3, S4
for Sx500
Not
supported
1G According
S1,S2 in
Sx500
100Mbs Not
to:
5
S1,S2 - XG
in SG500X
supported
According
to:
Forced user
speed
EEPROM
speed
1G speed
Stack Ports or Network Ports
Connector Type All ports
Cisco SFP-H10GB-CU1M – Passive Copper Cable 1G - 10G
Cisco SFP-H10GB-CU3M – Passive Copper Cable 1G - 10G
Cisco SFP-H10GB-CU5M – Passive Copper Cable 1G - 10G
Cisco SFP-10G-SR Not supported
Cisco SFP-10G-LRM Not supported
Cisco SFP-10G-LR Not supported
1G SFP Module MGBSX1 1G
1G SFP Module MGBT1 1G
1G SFP Module MGBLX1 1G
1G SFP Module MGBBX1 1G
Forced user
speed
EEPROM
speed
1G speed
Forced
user speed
EEPROM
speed
1G speed
Forced
user speed
EEPROM
speed
10G speed
100Mbs SFP Module MFELX1 Not supported
100Mbs SFP Module MFEFX1 Not supported
100Mbs SFP Module MFEBX1 Not supported
Other SFPs 1G
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 79
Administration: Stack Management
Default Configuration
Default Configuration
The following are the device defaults in the various stacking modes:
5
Device
Type
Sx500 Native Stack S3-S4 5G Stack Layer 2
SG500X/
ESW2550X
SG500XG Native Stack User can choose
Stack Mode Default Stack
Ports
Basic Hybrid S3-S4 5G Stack Layer 2
Advanced Hybrid S3-S4 5G Stack Layer 2
Native Stack S1-S 2 1 0G Sta ck Layer 2+Layer 3
Basic Hybrid S1-S2 5 G S ta ck Layer 2
Advanced Hybrid S1-S2 5 G Stack Layer 2
Advanced Hybrid XG S1-S2 5G St ack Layer 2
any pair
Advanced Hybrid XG User can choose
any pair
Default System
Mode
Layer 2+Layer 3
Layer 2+Layer 3
Interactions With Other Features
RIP and VRRP are not supported in Basic Hybrid stack mode.
System Modes
Use the System Mode and Stack Management page to perform the following:
• Change the stack mode of a device to Standalone.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 80
Administration: Stack Management
System Modes
• Change the stack mode of a device to one of the stacking modes, change
the unit ID, stack ports, and the speed of the stack ports of all the devices in
a stack.
• Change the system mode (Layer 2/3) of a standalone device or of the stack.
• Change the queues mode from 4 to 8 supported queues or vice versa.
Information about these modes is stored in the configuration file, as follows:
• Configuration File Header—Contains the system mode and the queues
mode (even if these are the default values).
• Configuration File Body—Contains configuration commands.
System Mode Backwards Compatibility
5
The following modes have been expanded in the current software version of the
device. Care must be taken when using these features in previous software
versions:
• Queues Mode—This mode can be changed from 4 QoS queues to 8 QoS
queues. There is no issue when upgrading from previous software versions
that did not support 8 queues, since the 4-queue mode is the default
queues mode in the current software version. However, when changing the
queues mode to 8 queues, the configuration must be examined and
adjusted to meet the desired QoS objectives with the new queues mode.
Changing the queues mode takes effect after rebooting the system. Queuerelated configuration that conflicts with the new queues mode is rejected.
• Stacking Mode—The Stacking mode has been expanded to include hybrid
stacking modes. There is no problem in upgrading from previous software
versions, since the device will boot with the existing stacking mode (Native
Stacking mode). If you want to downgrade software from a device that was
configured in a hybrid stacking mode to a software version that does not
support hybrid stacking, configure the device to Native Stacking mode first.
System Mode and Stack Management
To configure the stack:
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 81
Administration: Stack Management
System Modes
STEP 1 Click Administration > System Mode and Stack Management.
The operational status of a standalone device or a stack is displayed in the
Operational Status block:
• Stack Unit Mode—Displays one of the following values for the device:
- Standalone—Device is not part of a stack.
- Native Stacking—Device is part of a stack in which all of the units are of
the same types.
- Basic Hybrid Stacking—Device is part of a stack that can consist of both
SG500X and Sx500 devices with the Sx500 feature set.
- Advanced Hybrid Stacking—Device is part of a stack that can consist of
both SG500X and Sx500 devices with the SG500X feature set.
5
- Advanced Hybrid Stacking XG—Device is part of a stack that can
consist of both SG500X/ESW2-550X and SG500XG devices with the
SG500X feature set.
• Stack Topology—Displays whether the topology of the stack is chain or
ring.
• System Mode—Displays whether the stack/standalone devices are
operating in Layer 2, Layer 3 or Layer 2 and Layer 3 system mode.
• Stack Master—Displays the unit ID of the master unit of the stack.
• Master Election Status—Displays how the stack master unit was selected.
See Master Selection Process.
STEP 2 To configure the system mode after reboot, select either Layer 2 or Layer 3 mode.
STEP 3 To configure the queues mode after reboot, select whether to configure 4 or 8
QoS queues on the device. See Configuring QoS Queues.
STEP 4 Configure the units in a stack in the Stack Administrative Settings Table. These
changes become effective after reboot.
NOTE If the device is an Sx500 and if the stack unit mode is changed from Native Stacking
to Standalone, the device will be in Layer 2 system mode after reboot, unless you
change the System Mode field to Layer 3 at this time.
The following operational status of every unit in a stack is displayed in the table.
• Stack Unit Number—Displays the unit ID of a known and active unit.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 82
Administration: Stack Management
System Modes
• Model Name—Model name of a known and active unit.
• Stack Connection 1—Information for the first stack connection:
- Port—The type of the stack port that is connected.
- Speed—The speed of the stack port that is connected.
- Neighbor—Unit ID of the connected stack unit.
5
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 83
Administration
This section describes how to view system information and configure various
options on the device.
It covers the following topics:
• Device Models
• System Settings
5
• Console Settings (Autobaud Rate Support)
• Management Interface
• System Mode and Stack Management<500 - print only>
• User Accounts
• Defining Idle Session Timeout
• Time Settings
• System Log
• File Management
• Routing Resources
• Health
• Diagnostics
• Discovery - Bonjour
• Discovery - LLDP
• Discovery - CDP
• Ping
• Traceroute
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 57
5
Device Models
NOTE Each model can be set to Layer 3 system mode by using the System Mode and
NOTE The following port conventions are used:
Administration
Device Models
All models can be fully managed through the web-based switch configuration
utility.
Stack Management page.
When the device operates in Layer 3 system mode, the VLAN Rate Limit, and QoS
policers are not operational. Other QoS Advanced mode features are operational.
Only the SG500X/SG500XG/ESW2-550X models support Virtual Router
Redundancy Protocol (VRRP), and Routing Information Protocol (RIP).
• GE is used for Gigabit Ethernet (10/100/1000) ports.
• FE is used for Fast Ethernet (10/100) ports.
• XG is used for 10 Gigabit Ethernet ports.
The following table describes the various models, the number and type of ports
on them and their PoE information.
Model Name Product ID (PID) Description of Ports on Device Power
Dedicated
to PoE
SF500-24 SF500-24-K9 24-Port 10/100 Stackable
Managed Switch
SF500-24P SF500-24P-K9 24-Port 10/100 PoE Stackable
Managed Switch
SF500-48 SF500-48-K9 48-Port 10/100 Stackable
Managed Switch
SF500-48P SF500-48P-K9 48-Port 10/100 PoE Stackable
Managed Switch
N/A N/A
180W 24
N/A N/A
375W 48
No. of
Ports that
Support
PoE
SG500-28 SG5000-28-K9 28-Port Gigabit Stackable
Managed Switch
SG500-28MPP SG500-28MPP-K9 28-Port Gigabit PoE Managed
Switch
58 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
N/A N/A
740W 24
Administration
Device Models
5
Model Name Product ID (PID) Description of Ports on Device Power
Dedicated
to PoE
SG500-28P SG500-28P-K9 28-Port Gigabit PoE Stackable
Managed Switch
SG500-52 SG500-52-K9 52-Port Gigabit Stackable
Managed Switch
SG500-52MP SG500-52MP-K9 52-Port Gigabit Max-PoE Managed
Switch
SG500-52P SG500-52P-K9 52-Port Gigabit PoE Stackable
Managed Switch
SG500X-24 SG500X-24-K9 24-Port Gigabit with 4-Port 10-
Gigabit Stackable Managed Switch
SG500X-24P SG500X-24P-K9 24-Port Gigabit with 4-Port 10-
Gigabit PoE Stackable Managed
Switch
SG500X-48 SG500X-48-K9 48-Port Gigabit with 4-Port 10-
Gigabit Stackable Managed Switch
180W 24
N/A N/A
740W 48
375W 48
N/A N/A
375W 24
N/A N/A
No. of
Ports that
Support
PoE
SG500X-48P SG500X-48P-K9 48-Port Gigabit with 4-Port 10-
Gigabit PoE Stackable Managed
Switch
ESW2-550X-48 ESW2-550X-48-
K9
ESW2-550X48DC
SG500XG-8F8T SG500XG-8F8T-
ESW2-550X48DC-K9
K9
48-Port Gigabit with 4-Port 10Gigabit Stackable Managed Switch
48-Port Gigabit with 4-Port 10Gigabit Stackable Managed Switch
16-Port 10-Gigabit Stackable
Managed Switch
375W 48
N/A N/A
N/A N/A
N/A N/A
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 59
5
System Settings
The System Summary page provides a graphic view of the device, and displays
device status, hardware information, firmware version information, general PoE
status, and other items.
Displaying the System Summary
To view system information, click Status and Statistics > System Summary.
The System Summary page contains system and hardware information.
System Information:
Administration
System Settings
• Base MAC Address—Device MAC address. If the system is in stack mode,
the base MAC address of the master unit is displayed.
NOTE If the system is in Native Stacking mode, the Firmware Version
number shown is based on the version of the master.
• Firmware Version (Non-active Image)—Firmware version number of the
non-active image. If the system is in Native Stacking mode, the version of
the master unit is displayed.
• System Stack Mode—Displays whether the device is part of a stack
(Native Stacking or Standalone). The following options are available:
• System Operational Mode—Specifies whether the system is operating in
Layer 2 or Layer 3 system mode for 500 devices. .
• System Description—A description of the system.
• System Location—Physical location of the device. Click Edit to go the
System Settings page to enter this value.
• System Contact—Name of a contact person. Click Edit to go the System
Settings page to enter this value.
• Host Name—Name of the device. Click Edit to go the System Settings
page to enter this value. By default, the device hostname is composed of
the word switch concatenated with the three least significant bytes of the
device MAC address (the six furthest right hexadecimal digits).
• System Object ID—Unique vendor identification of the network
management subsystem contained in the entity (used in SNMP).
60 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Administration
System Settings
5
• System Uptime—Time that has elapsed since the last reboot.
• Current Time—Current system time.
• Base MAC Address—Device MAC address. If the system is in stack mode,
the base MAC address of the master unit is displayed.
• Jumbo Frames—Jumbo frame support status. This support can be
enabled or disabled by using the Port Settings page of the Port
Management menu.
NOTE Jumbo frames support takes effect only after it is enabled, and after
the device is rebooted.
Software Information:
• Firmware Version (Active Image)—Firmware version number of the active
image.
NOTE If the system is in stack mode (Native Stacking mode), the Firmware
Version number shown is based on the version of the master. See the Stack
Unit Mode section for more information about stack modes.
• Firmware MD5 Checksum (Active Image)—MD5 checksum of the active
image.
• Firmware Version (Non-active Image)—Firmware version number of the
non-active image. If the system is in stack mode, the version of the master
unit is displayed.
• Firmware MD5 Checksum (Non-active Image)—MD5 checksum of the
non-active image.
• Boot Version—Boot version number.
• Boot MD5 Checksum—MD5 checksum of the boot version.
• Locale—Locale of the first language. (This is always English.)
• Language Version—Language package version of the first or English
language.
• Language MD5 Checksum—MD5 checksum of the language file.
TCP/UDP Services Status:
• HTTP Service—Displays whether HTTP is enabled/disabled.
• HTTPS Service—Displays whether HTTPS is enabled/disabled.
Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version) 61
5
Administration
System Settings
• SNMP Service—Displays whether SNMP is enabled/disabled.
• Tel net Se rv ic e—Displays whether Telnet is enabled/disabled.
• SSH Service—Displays whether SSH is enabled/disabled.
PoE Power Information on Master Unit:
• Maximum Available PoE Power (W)—Maximum available power that can
be delivered by the PoE.
• Total PoE Power Consumption (W)—Tota l PoE power delivere d to
connected PoE devices.
• PoE Power Mode—Port Limit or Class Limit.
There is a
selected, takes you directly to the Port Management > PoE > Properties page. This
page shows the PoE power information on a per-unit basis.
The units in the stack are displayed graphically, along with the following
information for each unit:
• Unit ID of Master Unit
• Model Description—Device model description.
• Serial Number—Serial number.
• PID VID—Part number and version ID.
Detail
link next to PoE Power Information on Master Unit that, when
System Settings
To enter system settings:
STEP 1 Click Administration > System Settings.
STEP 2 View or modify the system settings.
• System Description—Displays a description of the device.
• System Location—Enter the location where the device is physically
located.
• System Contact—Enter the name of a contact person.
• Host Name—Select the host name of this device. This is used in the prompt
of CLI commands:
62 Cisco Small Business 200, 300 and 500 Series Managed Switch Administration Guide (Internal Version)
Loading...