Community Strings (for SNMP version 1 and 2c clients) 2-6
Trap Receivers 2-7
Configuring Access for SNMP Version 3 Clients 2-8
Saving Configuration Settings 2-8
Managing System Files 2-9
Chapter 3: Configuring the Switch 3-1
Using the Web Interface 3-1
Navigating the Web Browser Interface 3-2
Home Page 3-2
Configuration Options 3-3
Panel Display 3-3
Main Menu 3-4
Basic Configuration 3-10
Displaying System Information 3-10
Displaying Switch Hardware/Software Versions 3-11
Displaying Bridge Extension Capabilities 3-13
Setting the Switch’s IP Address 3-14
Manual Configuration 3-15
Using DHCP/BOOTP 3-16
DHCP Relay and Option 82 Information 3-17
Managing Firmware 3-19
Downloading System Software from a Server 3-20
i
Contents
Saving or Restoring Configuration Settings 3-22
Downloading Configuration Settings from a Server 3-23
Console Port Settings 3-24
Telnet Settings 3-26
Configuring Event Logging 3-28
System Log Configuration 3-28
Remote Log Configuration 3-30
Displaying Log Messages 3-31
Sending Simple Mail Transfer Protocol Alerts 3-32
Resetting the System 3-34
Setting the System Clock 3-35
Configuring SNTP 3-35
Configuring NTP 3-36
Setting the Time Zone 3-38
Simple Network Management Protocol 3-38
Enabling the SNMP Agent 3-40
Setting Community Access Strings 3-40
Specifying Trap Managers and Trap Types 3-41
Configuring SNMPv3 Management Access 3-43
Setting a Local Engine ID 3-44
Specifying a Remote Engine ID 3-44
Configuring SNMPv3 Users 3-45
Configuring Remote SNMPv3 Users 3-47
Configuring SNMPv3 Groups 3-49
Setting SNMPv3 Views 3-53
Replacing the Default Secure-site Certificate 3-60
Configuring the Secure Shell 3-61
Generating the Host Key Pair 3-63
Configuring the SSH Server 3-65
Configuring Port Security 3-66
Configuring 802.1X Port Authentication 3-68
Displaying 802.1X Global Settings 3-69
Configuring 802.1X Global Settings 3-70
Configuring Port Settings for 802.1X 3-70
Displaying 802.1X Statistics 3-73
MAC Address Authentication 3-74
Configuring the MAC Authentication Reauthentication Time 3-75
Configuring MAC Authentication for Ports 3-76
Displaying Secure MAC Address Information 3-77
Configuring MAC Address Filters 3-79
Filtering Addresses for Management Access 3-80
ii
Contents
Access Control Lists 3-82
Configuring Access Control Lists 3-82
Setting the ACL Name and Type 3-83
Configuring a Standard IP ACL 3-84
Configuring an Extended IP ACL 3-85
Configuring a MAC ACL 3-87
Binding a Port to an Access Control List 3-88
Port Configuration 3-89
Displaying Connection Status 3-89
Configuring Interface Connections 3-91
Creating Trunk Groups 3-93
Statically Configuring a Trunk 3-94
Enabling LACP on Selected Ports 3-95
Configuring LACP Parameters 3-97
Displaying LACP Port Counters 3-99
Displaying LACP Settings and Status for the Local Side 3-101
Displaying LACP Settings and Status for the Remote Side 3-103
Setting Broadcast Storm Thresholds 3-105
Configuring Port Mirroring 3-106
Configuring Rate Limits 3-107
Rate Limit Granularity 3-107
Rate Limit Configuration 3-108
Showing Port Statistics 3-109
Address Table Settings 3-114
Setting Static Addresses 3-114
Displaying the Address Table 3-115
Changing the Aging Time 3-117
Spanning Tree Algorithm Configuration 3-117
Displaying Global Settings 3-119
Configuring Global Settings 3-123
Displaying Interface Settings 3-127
Configuring Interface Settings 3-130
Configuring Multiple Spanning Trees 3-132
Displaying Interface Settings for MSTP 3-136
Configuring Interface Settings for MSTP 3-137
VLAN Configuration 3-139
IEEE 802.1Q VLANs 3-139
Enabling or Disabling GVRP (Global Setting) 3-142
Displaying Basic VLAN Information 3-142
Displaying Current VLANs 3-143
Creating VLANs 3-145
Adding Static Members to VLANs (VLAN Index) 3-147
Adding Static Members to VLANs (Port Index) 3-148
Configuring VLAN Behavior for Interfaces 3-150
Private VLANs 3-152
Setting the Default Priority for Interfaces 3-158
Mapping CoS Values to Egress Queues 3-160
Selecting the Queue Mode 3-162
Setting the Service Weight for Traffic Classes 3-163
Layer 3/4 Priority Settings 3-164
Mapping Layer 3/4 Priorities to CoS Values 3-164
Selecting IP Precedence/DSCP Priority 3-164
Mapping IP Precedence 3-165
Mapping DSCP Priority 3-166
Mapping IP Port Priority 3-168
Mapping CoS Values to ACLs 3-169
Multicast Filtering 3-170
Layer 2 IGMP (Snooping and Query) 3-171
Configuring IGMP Snooping and Query Parameters 3-171
Enabling IGMP Immediate Leave 3-173
Displaying Interfaces Attached to a Multicast Router 3-174
Specifying Static Interfaces for a Multicast Router 3-175
Displaying Port Members of Multicast Services 3-176
Assigning Ports to Multicast Services 3-177
IGMP Filtering and Throttling 3-178
Enabling IGMP Filtering and Throttling 3-178
Configuring IGMP Filter Profiles 3-179
Configuring IGMP Filtering and Throttling for Interfaces 3-181
Multicast VLAN Registration 3-183
Configuring Global MVR Settings 3-184
Displaying MVR Interface Status 3-185
Displaying Port Members of Multicast Groups 3-186
Configuring MVR Interface Status 3-187
Assigning Static Multicast Groups to Interfaces 3-188
Configuring Domain Name Service 3-189
Configuring General DNS Service Parameters 3-189
Configuring Static DNS Host to Address Entries 3-192
Displaying the DNS Cache 3-193
Switch Clustering 3-194
Cluster Configuration 3-194
Cluster Member Configuration 3-195
Cluster Member Information 3-196
Cluster Candidate Information 3-197
iv
Contents
Chapter 4: Command Line Interface 4-1
Using the Command Line Interface 4-1
Accessing the CLI 4-1
Console Connection 4-1
Telnet Connection 4-1
Entering Commands 4-3
Keywords and Arguments 4-3
Minimum Abbreviation 4-3
Command Completion 4-3
Getting Help on Commands 4-3
Showing Commands 4-4
Partial Keyword Lookup 4-5
Negating the Effect of Commands 4-5
Using Command History 4-5
Understanding Command Modes 4-5
Exec Commands 4-6
Configuration Commands 4-7
Command Line Processing 4-8
Command Groups 4-9
Line Commands 4-11
line 4-11
login 4-12
password 4-13
timeout login response 4-14
exec-timeout 4-14
password-thresh 4-15
silent-time 4-16
databits 4-16
parity 4-17
speed 4-18
stopbits 4-18
disconnect 4-19
show line 4-19
General Commands 4-20
enable 4-20
disable 4-21
configure 4-22
show history 4-22
reload 4-23
end 4-23
exit 4-24
quit 4-24
System Management Commands 4-25
Device Designation Commands 4-25
v
Contents
prompt 4-25
hostname 4-26
User Access Commands 4-26
username 4-27
enable password 4-28
IP Filter Commands 4-29
management 4-29
show management 4-30
Web Server Commands 4-31
ip http port 4-31
ip http server 4-31
ip http secure-server 4-32
ip http secure-port 4-33
Telnet Server Commands 4-34
ip telnet port 4-34
ip telnet server 4-34
Secure Shell Commands 4-35
ip ssh server 4-37
ip ssh timeout 4-38
ip ssh authentication-retries 4-38
ip ssh server-key size 4-39
delete public-key 4-39
ip ssh crypto host-key generate 4-40
ip ssh crypto zeroize 4-40
ip ssh save host-key 4-41
show ip ssh 4-41
show ssh 4-42
show public-key 4-43
Event Logging Commands 4-44
logging on 4-44
logging history 4-45
logging host 4-46
logging facility 4-46
logging trap 4-47
clear logging 4-47
show logging 4-48
show log 4-49
access-list ip 4-103
permit, deny (Standard ACL) 4-104
permit, deny (Extended ACL) 4-105
show ip access-list 4-107
ip access-group 4-107
show ip access-group 4-108
map access-list ip 4-108
show map access-list ip 4-109
MAC ACLs 4-110
access-list mac 4-110
permit, deny (MAC ACL) 4-111
show mac access-list 4-112
mac access-group 4-112
show mac access-group 4-113
map access-list mac 4-113
show map access-list mac 4-114
ACL Information 4-115
show access-list 4-115
show access-group 4-115
SNMP Commands 4-116
viii
Contents
snmp-server 4-117
show snmp 4-117
snmp-server community 4-118
snmp-server contact 4-119
snmp-server location 4-119
snmp-server host 4-120
snmp-server enable traps 4-122
snmp-server engine-id 4-123
show snmp engine-id 4-124
snmp-server view 4-125
show snmp view 4-126
snmp-server group 4-126
show snmp group 4-127
snmp-server user 4-128
show snmp user 4-130
Interface Commands 4-131
interface 4-131
description 4-132
speed-duplex 4-132
negotiation 4-133
capabilities 4-134
flowcontrol 4-135
shutdown 4-136
switchport broadcast packet-rate 4-137
clear counters 4-137
show interfaces status 4-138
show interfaces counters 4-139
show interfaces switchport 4-140
Mirror Port Commands 4-142
port monitor 4-142
show port monitor 4-143
Rate Limit Commands 4-144
rate-limit 4-144
rate-limit granularity 4-145
show rate-limit 4-145
bridge-ext gvrp 4-194
show bridge-ext 4-195
switchport gvrp 4-195
show gvrp configuration 4-196
garp timer 4-196
show garp timer 4-197
Priority Commands 4-198
Priority Commands (Layer 2) 4-198
queue mode 4-199
switchport priority default 4-199
queue bandwidth 4-200
queue cos-map 4-201
show queue mode 4-202
show queue bandwidth 4-202
show queue cos-map 4-203
Priority Commands (Layer 3 and 4) 4-204
map ip port (Global Configuration) 4-204
map ip port (Interface Configuration) 4-205
map ip precedence (Global Configuration) 4-205
map ip precedence (Interface Configuration) 4-206
map ip dscp (Global Configuration) 4-207
map ip dscp (Interface Configuration) 4-207
show map ip port 4-208
show map ip precedence 4-209
show map ip dscp 4-210
Multicast Filtering Commands 4-211
IGMP Snooping Commands 4-212
ip igmp snooping 4-212
ip igmp snooping vlan static 4-212
ip igmp snooping version 4-213
ip igmp snooping immediate-leave 4-213
show ip igmp snooping 4-214
show mac-address-table multicast 4-215
IGMP Query Commands (Layer 2) 4-216
ip igmp snooping querier 4-216
ip igmp snooping query-count 4-216
ip igmp snooping query-interval 4-217
xi
Contents
ip igmp snooping query-max-response-time 4-218
ip igmp snooping router-port-expire-time 4-218
Static Multicast Routing Commands 4-219
ip igmp snooping vlan mrouter 4-219
show ip igmp snooping mrouter 4-220
IGMP Filtering and Throttling Commands 4-221
ip igmp filter (Global Configuration) 4-221
ip igmp profile 4-222
permit, deny 4-223
range 4-223
ip igmp filter (Interface Configuration) 4-224
ip igmp max-groups 4-224
ip igmp max-groups action 4-225
show ip igmp filter 4-226
show ip igmp profile 4-226
show ip igmp throttle interface 4-227
ip host 4-233
clear host 4-234
ip domain-name 4-234
ip domain-list 4-235
ip name-server 4-236
ip domain-lookup 4-237
show hosts 4-238
show dns 4-239
show dns cache 4-239
clear dns cache 4-240
DHCP Commands 4-241
ip dhcp relay information option 4-241
ip dhcp relay information policy 4-242
ip dhcp relay server 4-242
show ip dhcp-relay 4-243
IP Interface Commands 4-244
ip address 4-244
ip default-gateway 4-245
ip dhcp restart 4-246
show ip interface 4-246
show ip redirects 4-247
ping 4-247
Switch Cluster Commands 4-249
cluster 4-249
xii
Contents
cluster commander 4-250
cluster ip-pool 4-250
cluster member 4-251
rcommand 4-252
show cluster 4-252
show cluster members 4-253
show cluster candidates 4-253
Appendix A: Software Specifications A-1
Software Features A-1
Management Features A-2
Standards A-2
Management Information Bases A-3
Appendix B: Troubleshooting B-1
Problems Accessing the Management Interface B-1
Using System Logs B-2
Figure 3-1Home Page 3-2
Figure 3-2Panel Display 3-3
Figure 3-3System Information 3-10
Figure 3-4Displaying Switch Information 3-12
Figure 3-5Bridge Extension Configuration 3-13
Figure 3-6Manual IP Configuration 3-15
Figure 3-7IP Configuration using DHCP 3-16
Figure 3-8DHCP Relay Option 82 Configuration 3-18
Figure 3-9Operation Code Image File Transfer 3-20
Figure 3-10 Select Start-Up Operation File 3-20
Figure 3-11 Deleting Files 3-21
Figure 3-12 Copy Configuration Settings 3-23
Figure 3-13 Setting the Startup Configuration Settings 3-23
Figure 3-14 Console Port Settings 3-25
Figure 3-15 Enabling Telnet 3-27
Figure 3-16 System Logs 3-29
Figure 3-17 Remote Logs 3-30
Figure 3-18 Displaying Logs 3-31
Figure 3-19 Enabling and Configuring SMTP Alerts 3-33
Figure 3-20 Resetting the System 3-34
Figure 3-21 SNTP Configuration 3-35
Figure 3-22 NTP Client Configuration 3-37
Figure 3-23 Setting the System Clock 3-38
Figure 3-24 Enabling the SNMP Agent 3-40
Figure 3-25 Configuring SNMP Community Strings 3-41
Figure 3-26 Configuring SNMP Trap Managers 3-43
Figure 3-27 Setting the SNMPv3 Engine ID 3-44
Figure 3-28 Setting an Engine ID 3-45
Figure 3-29 Configuring SNMPv3 Users 3-46
Figure 3-30 Configuring Remote SNMPv3 Users 3-48
Figure 3-31 Configuring SNMPv3 Groups 3-52
Figure 3-32 Configuring SNMPv3 Views 3-53
Figure 3-33 Access Levels 3-55
Figure 3-34 Authentication Settings 3-58
Figure 3-35 HTTPS Settings 3-60
Figure 3-36 SSH Host-Key Settings 3-64
Figure 3-37 SSH Server Settings 3-65
Figure 3-38 Configuring Port Security 3-67
Figure 3-39 802.1X Global Information 3-69
Figure 3-40 802.1X Configuration 3-70
Figure 3-41 802.1X Port Configuration 3-71
Figure 3-42 Displaying 802.1X Port Statistics 3-74
xix
Figures
Figure 3-43 Network Access Configuration 3-76
Figure 3-44 Network Access Port Configuration 3-77
Figure 3-45 Network Access MAC Address Information 3-78
Figure 3-46 Network Access MAC Filter Configuration 3-79
Figure 3-47Creating a Web IP Filter List 3-81
Figure 3-48 Selecting ACL Type 3-83
Figure 3-49 ACL Configuration - Standard IP 3-84
Figure 3-50 ACL Configuration - Extended IP 3-86
Figure 3-51 ACL Configuration - MAC 3-87
Figure 3-52 Binding a Port to an ACL 3-88
Figure 3-53 Displaying Port/Trunk Information 3-90
Figure 3-54 Port/Trunk Configuration 3-92
Figure 3-55 Configuring Port Trunks 3-94
Figure 3-56 LACP Configuration 3-96
Figure 3-57 LACP - Aggregation Port 3-98
Figure 3-58 LACP - Port Counters Information 3-100
Figure 3-59LACP - Port Internal Information 3-102
Figure 3-60 LACP - Port Neighbors Information 3-103
Figure 3-61 Port Broadcast Control 3-105
Figure 3-62 Mirror Port Configuration 3-107
Figure 3-63Rate Limit Granularity Configuration 3-108
Figure 3-64 Output Rate Limit Port Configuration 3-109
Figure 3-65Port Statistics 3-113
Figure 3-66Static Addresses 3-115
Figure 3-67 Dynamic Addresses 3-116
Figure 3-68 Address Aging 3-117
Figure 3-69 STA Information 3-121
Figure 3-70 STA Global Configuration 3-126
Figure 3-71 STA Port Information 3-129
Figure 3-72 STA Port Configuration 3-132
Figure 3-73 MSTP VLAN Configuration 3-134
Figure 3-74 MSTP Port Information 3-136
Figure 3-75 MSTP Port Configuration 3-138
Figure 3-76 GLobally Enabling GVRP 3-142
Figure 3-77 VLAN Basic Information 3-142
Figure 3-78 VLAN Current Table 3-144
Figure 3-79 VLAN Static List - Creating VLANs 3-146
Figure 3-80 VLAN Static Table - Adding Static Members 3-148
Figure 3-81 VLAN Static Membership by Port 3-149
Figure 3-82 VLAN Port Configuration 3-151
Figure 3-83 Private VLAN Information 3-153
Figure 3-84 Private VLAN Configuration 3-154
Figure 3-85 Private VLAN Association 3-155
Figure 3-86 Private VLAN Port Information 3-156
Figure 3-87 Private VLAN Port Configuration 3-157
xx
Figures
Figure 3-88 Port Priority Configuration 3-159
Figure 3-89 Traffic Classes 3-161
Figure 3-90 Queue Mode 3-162
Figure 3-91 Configuring Queue Scheduling 3-163
Figure 3-92 IP Precedence/DSCP Priority Status 3-164
Figure 3-93 Mapping IP Precedence Priority Values 3-165
Figure 3-94 Mapping IP DSCP Priority Values 3-167
Figure 3-95 IP Port Priority Status 3-168
Figure 3-96 IP Port Priority 3-168
Figure 3-97 ACL CoS Priority 3-170
Figure 3-98 IGMP Configuration 3-172
Figure 3-99 IGMP Immediate Leave 3-173
Figure 3-100 Displaying Multicast Router Port Information 3-174
Figure 3-101 Static Multicast Router Port Configuration 3-175
Figure 3-102 IP Multicast Registration Table 3-176
Figure 3-103 IGMP Member Port Table 3-177
Figure 3-104 Enabling IGMP Filtering and Throttling 3-179
Figure 3-105 IGMP Profile Configuration 3-180
Figure 3-106 IGMP Filter and Throttling Port Configuration 3-182
Figure 3-107 MVR Global Configuration 3-184
Figure 3-108 MVR Port Information 3-185
Figure 3-109 MVR Group IP Information 3-186
Figure 3-110 MVR Port Configuration 3-188
Figure 3-111 MVR Group Member Configuration 3-189
Figure 3-112 DNS General Configuration 3-191
Figure 3-113 DNS Static Host Table 3-192
Figure 3-114 DNS Cache 3-193
Figure 3-115 Cluster Configuration 3-195
Figure 3-116 Cluster Member Configuration 3-196
Figure 3-117 Cluster Member Information 3-196
Figure 3-118 Cluster Candidate Information 3-197
xxi
Figures
xxii
Chapter 1: Introduction
This switch provides a broad range of features for Layer 2 switching. It includes a
management agent that allows you to configure the features listed in this manual.
The default configuration can be used for most of the features provided by this
switch. However, there are many options that you should configure to maximize the
switch’s performance for your particular network environment.
Key Features
Table 1-1 Key Features
FeatureDescription
Configuration Backup
and Restore
AuthenticationConsole, Telnet, web – User name / password, RADIUS, TACACS+
Access Control ListsSupports up to 88 IP or MAC ACLs
DHCP ClientSupported
Port ConfigurationSpeed, duplex mode and flow control
Rate LimitingInput and output rate limiting per port
Port MirroringOne port mirrored to a single analysis port
Port TrunkingSupports up to 4 trunks using either static or dynamic trunking (LACP)
Broadcast Storm
Control
Static AddressUp to 8K MAC addresses in the forwarding table
IEEE 802.1D BridgeSupports dynamic data switching and addresses learning
Store-and-Forward
Switching
Spanning Tree Protocol Supports standard STP and Rapid Spanning Tree Protocol (RSTP)
Virtual LANsUp to 255 using IEEE 802.1Q, port-based, or private VLANs
Traffic PrioritizationDefault port priority, traffic class map, queue scheduling, IP Precedence or
Multicast FilteringSupports IGMP snooping and query
Backup to TFTP server
Web – HTTPS; Telnet – SSH
SNMP – Community strings
Port – IEEE 802.1X, MAC address filtering
Supported
Supported to ensure wire-speed switching while eliminating bad frames
Differentiated Services Code Point (DSCP), and TCP/UDP Port
1-1
Introduction
1
Description of Software Features
The switch provides a wide range of advanced performance enhancing features.
Flow control eliminates the loss of packets due to bottlenecks caused by port
saturation. Broadcast storm suppression prevents broadcast traffic storms from
engulfing the network. Port-based and protocol-based VLANs, plus support for
automatic GVRP VLAN registration provide traffic security and efficient use of
network bandwidth. CoS priority queueing ensures the minimum delay for moving
real-time multimedia data across the network. While multicast filtering provides
support for real-time network applications. Some of the management features are
briefly described below.
Configuration Backup and Restore – You can save the current configuration
settings to a file on a TFTP server, and later download this file to restore the switch
configuration settings.
Authentication – This switch authenticates management access via the console
port, Telnet or web browser. User names and passwords can be configured locally or
can be verified via a remote authentication server (i.e., RADIUS or TACACS+).
Port-based authentication is also supported via the IEEE 802.1X protocol. This
protocol uses the Extensible Authentication Protocol over LANs (EAPOL) to request
user credentials from the 802.1X client, and then verifies the client’s right to access
the network via an authentication server.
Other authentication options include HTTPS for secure management access via the
web, SSH for secure management access over a Telnet-equivalent connection, IP
address filtering for SNMP/web/Telnet management access, and MAC address
filtering for port access.
Access Control Lists – ACLs provide packet filtering for IP frames (based on
address, protocol, TCP/UDP port number or TCP control code) or any frames
(based on MAC address or Ethernet type). ACLs can be used to improve
performance by blocking unnecessary network traffic or to implement security
controls by restricting access to specific network resources or protocols.
Port Configuration – You can manually configure the speed, duplex mode, and
flow control used on specific ports, or use auto-negotiation to detect the connection
settings used by the attached device. Use the full-duplex mode on ports whenever
possible to double the throughput of switch connections. Flow control should also be
enabled to control network traffic during periods of congestion and prevent the loss
of packets when port buffer thresholds are exceeded. The switch supports flow
control based on the IEEE 802.3x standard.
Rate Limiting – This feature controls the maximum rate for traffic transmitted or
received on an interface. Rate limiting is configured on interfaces at the edge of a
network to limit traffic into or out of the network. Traffic that falls within the rate limit is
transmitted, while packets that exceed the acceptable amount of traffic are dropped.
1-2
Description of Software Features
Port Mirroring – The switch can unobtrusively mirror traffic from any port to a
monitor port. You can then attach a protocol analyzer or RMON probe to this port to
perform traffic analysis and verify connection integrity.
Port Trunking – Ports can be combined into an aggregate connection. Trunks can
be manually set up or dynamically configured using IEEE 802.3ad Link Aggregation
Control Protocol (LACP). The additional ports dramatically increase the throughput
across any connection, and provide redundancy by taking over the load if a port in
the trunk should fail. The switch supports up to four trunks.
Broadcast Storm Control – Broadcast suppression prevents broadcast traffic from
overwhelming the network. When enabled on a port, the level of broadcast traffic
passing through the port is restricted. If broadcast traffic rises above a pre-defined
threshold, it will be throttled until the level falls back beneath the threshold.
Static Addresses – A static address can be assigned to a specific interface on this
switch. Static addresses are bound to the assigned interface and will not be moved.
When a static address is seen on another interface, the address will be ignored and
will not be written to the address table. Static addresses can be used to provide
network security by restricting access for a known host to a specific port.
IEEE 802.1D Bridge – The switch supports IEEE 802.1D transparent bridging. The
address table facilitates data switching by learning addresses, and then filtering or
forwarding traffic based on this information. The address table supports up to 8K
addresses.
Store-and-Forward Switching – The switch copies each frame into its memory
before forwarding them to another port. This ensures that all frames are a standard
Ethernet size and have been verified for accuracy with the cyclic redundancy check
(CRC). This prevents bad frames from entering the network and wasting bandwidth.
To avoid dropping frames on congested ports, the switch provides 8 MB for frame
buffering. This buffer can queue packets awaiting transmission on congested
networks.
Spanning Tree Algorithm – The switch supports these spanning tree protocols:
Spanning Tree Protocol (STP, IEEE 802.1D) – This protocol provides loop detection
and recovery by allowing two or more redundant connections to be created between
a pair of LAN segments. When there are multiple physical paths between segments,
this protocol will choose a single path and disable all others to ensure that only one
route exists between any two stations on the network. This prevents the creation of
network loops. However, if the chosen path should fail for any reason, an alternate
path will be activated to maintain the connection.
Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) – This protocol reduces the
convergence time for network topology changes to 3 to 5 seconds, compared to 30
seconds or more for the older IEEE 802.1D STP standard. It is intended as a
complete replacement for STP, but can still interoperate with switches running the
older standard by automatically reconfiguring ports to STP-compliant mode if they
detect STP protocol messages from attached devices.
1
1-3
Introduction
1
Virtual LANs – The switch supports up to 255 VLANs. A Virtual LAN is a collection
of network nodes that share the same collision domain regardless of their physical
location or connection point in the network. The switch supports tagged VLANs
based on the IEEE 802.1Q standard. Members of VLAN groups can be dynamically
learned via GVRP, or ports can be manually assigned to a specific set of VLANs.
This allows the switch to restrict traffic to the VLAN groups to which a user has been
assigned. By segmenting your network into VLANs, you can:
• Eliminate broadcast storms which severely degrade performance in a flat network.
• Simplify network management for node changes/moves by remotely configuring
VLAN membership for any port, rather than having to manually change the network
connection.
• Provide data security by restricting all traffic to the originating VLAN.
• Use private VLANs to restrict traffic to pass only between data ports and the uplink
ports, thereby isolating adjacent ports within the same VLAN, and allowing you to
limit the total number of VLANs that need to be configured.
Traffic Prioritization – This switch prioritizes each packet based on the required
level of service, using four priority queues with strict or Weighted Round Robin
Queuing. It uses IEEE 802.1p and 802.1Q tags to prioritize incoming traffic based on
input from the end-station application. These functions can
independent priorities for delay-sensitive data and best-effort data.
This switch also supports several common methods of prioritizing layer 3/4 traffic to
meet application requirements. Traffic can be prioritized based on the priority bits in
the IP frame’s Type of Service (ToS) octet or the number of the TCP/UDP port.
When these services are enabled, the priorities are mapped to a Class of Service
value by the switch, and the traffic then sent to the corresponding output queue.
Multicast Filtering – Specific multicast traffic can be assigned to its own VLAN to
ensure that it does not interfere with normal network traffic and to guarantee
real-time delivery by setting the required priority level for the designated VLAN. The
switch uses IGMP Snooping and Query to manage multicast group registration.
be used to provide
1-4
System Defaults
1
System Defaults
The switch’s system defaults are provided in the configuration file
“Factory_Default_Config.cfg.” To reset the switch defaults, this file should be set as
the startup configuration file (page 3-24).
The following table lists some of the basic system defaults.
SMTP Email AlertsEvent HandlerEnabled (but no server defined)
SNTP Clock SynchronizationDisabled
(Continued)
1-7
1
Introduction
1-8
Chapter 2: Initial Configuration
Connecting to the Switch
Configuration Options
The switch includes a built-in network management agent. The agent offers a variety
of management options, including SNMP, RMON and a Web-based interface. A PC
may also be connected directly to the switch for configuration and monitoring via a
command line interface (CLI).
Note: The IP address for this switch is obtained via DHCP by default. To change this
address, see “Setting an IP Address” on page 2-4.
The switch’s HTTP Web agent allows you to configure switch parameters, monitor
port connections, and display statistics using a standard Web browser such as
Netscape Navigator version 6.2 and higher or Microsoft IE version 5.0 and higher.
The switch’s Web management interface can be accessed from any computer
attached to the network.
The CLI program can be accessed by a direct connection to the RS-232 serial
console port on the switch, or remotely by a Telnet connection over the network.
The switch’s management agent also supports SNMP (Simple Network
Management Protocol). This SNMP agent permits the switch to be managed from
any system in the network using network management software such as
HP OpenView.
The switch’s Web interface, CLI configuration program, and SNMP agent allow you
to perform the following management functions:
• Set user names and passwords for up to 16 users
• Set an IP interface for a management VLAN
• Configure SNMP parameters
• Enable/disable any port
• Set the speed/duplex mode for any port
• Configure the bandwidth of any port by limiting input or output rates
• Control port access through IEEE 802.1X security or static address filtering
• Filter packets using Access Control Lists (ACLs)
• Configure up to 255 IEEE 802.1Q VLANs
• Enable GVRP automatic VLAN registration
• Configure IGMP multicast filtering
• Upload and download system firmware via TFTP
• Upload and download switch configuration files via TFTP
• Configure Spanning Tree parameters
• Configure Class of Service (CoS) priority queuing
2-1
Initial Configuration
2
• Configure up to 4 static or LACP trunks
• Enable port mirroring
• Set broadcast storm control on any port
• Display system information and statistics
Required Connections
The switch provides an RS-232 serial port that enables a connection to a PC or
terminal for monitoring and configuring the switch. A null-modem console cable is
provided with the switch.
Attach a VT100-compatible terminal, or a PC running a terminal emulation program
to the switch. You can use the console cable provided with this package, or use a
null-modem cable that complies with the wiring assignments shown in the
Installation Guide.
To connect a terminal to the console port, complete the following steps:
1.Connect the console cable to the serial port on a terminal, or a PC running
terminal emulation software, and tighten the captive retaining screws on the
DB-9 connector.
2.Connect the other end of the cable to the RS-232 serial port on the switch.
3.Make sure the terminal emulation software is set as follows:
• Select the appropriate serial port (COM port 1 or COM port 2).
• Set the baud rate to 9600 bps.
• Set the data format to 8 data bits, 1 stop bit, and no parity.
• Set flow control to none.
• Set the emulation mode to VT100.
• When using HyperTerminal, select Terminal keys, not Windows keys.
Notes: 1. When using HyperTerminal with Microsoft® Windows® 2000, make sure that
For a description of how to use the CLI, see “Using the Command Line Interface” on
page 4-1. For a list of all the CLI commands and detailed information on using the
CLI, refer to “Command Groups” on page 4-9.
you have Windows 2000 Service Pack 2 or later installed. Windows 2000
Service Pack 2 fixes the problem of arrow keys not functioning in
HyperTerminal’s VT100 emulation. See www.microsoft.com for information
on Windows 2000 service packs.
2. Refer to “Line Commands” on page 4-11 for a complete description of
console configuration options.
3. Once you have set up the terminal correctly, the console login screen will be
displayed.
2-2
Basic Configuration
2
Remote Connections
Prior to accessing the switch’s onboard agent via a network connection, you must
first configure it with a valid IP address, subnet mask, and default gateway using a
console connection, DHCP or BOOTP protocol.
The IP address for this switch is obtained via DHCP by default. To manually
configure this address or enable dynamic address assignment via DHCP or BOOTP,
see “Setting an IP Address” on page 2-4.
Note: This switch supports four concurrent Telnet/SSH sessions.
After configuring the switch’s IP parameters, you can access the onboard
configuration program from anywhere within the attached network. The onboard
configuration program can be accessed using Telnet from any computer attached to
the network. The switch can also be managed by any computer using a web
browser (Internet Explorer 5.0 or above, or Netscape Navigator 6.2 or above), or
from a network computer using SNMP network management software.
Note: The onboard program only provides access to basic configuration functions. To
access the full range of SNMP management functions, you must use
SNMP-based network management software.
Basic Configuration
Console Connection
The CLI program provides two different command levels — normal access level
(Normal Exec) and privileged access level (Privileged Exec). The commands
available at the Normal Exec level are a limited subset of those available at the
Privileged Exec level and allow you to only display information and use basic
utilities. To fully configure the switch parameters, you must access the CLI at the
Privileged Exec level.
Access to both CLI levels are controlled by user names and passwords. The switch
has a default user name and password for each level. To log into the CLI at the
Privileged Exec level using the default user name and password, perform these
steps:
1.To initiate your console connection, press <Enter>. The “User Access
Verification” procedure starts.
2.At the Username prompt, enter “admin.”
3.At the Password prompt, also enter “admin.” (The password characters are not
displayed on the console screen.)
4.The session is opened and the CLI displays the “Console#” prompt indicating
you have access at the Privileged Exec level.
2-3
Initial Configuration
2
Setting Passwords
Note: If this is your first time to log into the CLI program, you should define new
passwords for both default user names using the “username” command, record
them and put them in a safe place.
Passwords can consist of up to 8 alphanumeric characters and are case sensitive.
To prevent unauthorized access to the switch, set the passwords as follows:
1.Open the console interface with the default user name and password “admin” to
access the Privileged Exec level.
2.Type “configure” and press <Enter>.
3.Type “username guest password 0 password,” for the Normal Exec level, where
password is your new password. Press <Enter>.
4.Type “username admin password 0 password,” for the Privileged Exec level,
where password is your new password. Press <Enter>.
Note: ‘0’ specifies the password in plain text, ‘7’ specifies the password in encrypted
form.
Username: admin
Password:
CLI session with the Standalone Intelligent Switch is opened.
To end the CLI session, enter [Exit].
You must establish IP address information for the switch to obtain management
access through the network. This can be done in either of the following ways:
Manual — You have to input the information, including IP address and subnet mask.
If your management station is not in the same IP subnet as the switch, you will also
need to specify the default gateway router.
Dynamic — The switch sends IP configuration requests to BOOTP or DHCP
address allocation servers on the network.
Manual Configuration
You can manually assign an IP address to the switch. You may also need to specify
a default gateway that resides between this device and management stations that
exist on another network segment. Valid IP addresses consist of four decimal
numbers, 0 to 255, separated by periods. Anything outside this format will not be
accepted by the CLI program.
Note: The IP address for this switch is obtained via DHCP by default.
2-4
Basic Configuration
Before you can assign an IP address to the switch, you must obtain the following
information from your network administrator:
• IP address for the switch
• Default gateway for the network
• Network mask for this network
To assign an IP address to the switch, complete the following steps:
1.From the Privileged Exec level global configuration mode prompt, type
“interface vlan 1” to access the interface-configuration mode. Press <Enter>.
2.Type “ip address ip-address netmask,” where “ip-address” is the switch IP
address and “netmask” is the network mask for the network. Press <Enter>.
3.Type “exit” to return to the global configuration mode prompt. Press <Enter>.
4.To set the IP address of the default gateway for the network to which the switch
belongs, type “ip default-gateway gateway,” where “gateway” is the IP address
of the default gateway. Press <Enter>.
If you select the “bootp” or “dhcp” option, IP will be enabled but will not function until
a BOOTP or DHCP reply has been received. You therefore need to use the “ip dhcp
restart” command to start broadcasting service requests. Requests will be sent
periodically in an effort to obtain IP configuration information. (BOOTP and DHCP
values can include the IP address, subnet mask, and default gateway.)
If the “bootp” or “dhcp” option is saved to the startup-config file (step 6), then the
switch will start broadcasting service requests as soon as it is powered on.
To automatically configure the switch by communicating with BOOTP or DHCP
address allocation servers on the network, complete the following steps:
1.From the Global Configuration mode prompt, type “interface vlan 1” to access
the interface-configuration mode. Press <Enter>.
2.At the interface-configuration mode prompt, use one of the following commands:
• To obtain IP settings via DHCP, type “ip address dhcp” and press <Enter>.
• To obtain IP settings via BOOTP, type “ip address bootp” and press <Enter>.
3.Type “end” to return to the Privileged Exec mode. Press <Enter>.
4.Type “ip dhcp restart” to begin broadcasting service requests. Press <Enter>.
2-5
Initial Configuration
2
5.Wait a few minutes, and then check the IP configuration settings by typing the
“show ip interface” command. Press <Enter>.
6.Then save your configuration changes by typing “copy running-config
startup-config.” Enter the startup file name and press <Enter>.
Console(config)#interface vlan 1
Console(config-if)#ip address dhcp
Console(config-if)#end
Console#ip dhcp restart
Console#show ip interface
IP address and netmask: 192.168.1.54 255.255.255.0 on VLAN 1,
and address mode: User specified.
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Enabling SNMP Management Access
The switch can be configured to accept management commands from Simple
Network Management Protocol (SNMP) applications such as HP OpenView. You
can configure the switch to (1) respond to SNMP requests or (2) generate SNMP
traps.
When SNMP management stations send requests to the switch (either to return
information or to set a parameter), the switch provides the requested data or sets the
specified parameter. The switch can also be configured to send information to
SNMP managers (without being requested by the managers) through trap
messages, which inform the manager that certain events have occurred.
The switch includes an SNMP agent that supports SNMP version 1, 2c, and 3
clients. To provide management access for version 1 or 2c clients, you must specify
a community string. The switch provides a default MIB View (i.e., an SNMPv3
construct) for the default “public” community string that provides read access to the
entire MIB tree, and a default view for the “private” community string that provides
read/write access to the entire MIB tree. However, you may assign new views to
version 1 or 2c community strings that suit your specific security requirements (see
“Setting SNMPv3 Views” on page 3-53).
Community Strings (for SNMP version 1 and 2c clients)
Community strings are used to control management access to SNMP version 1 and
2c stations, as well as to authorize SNMP stations to receive trap messages from
the switch. You therefore need to assign community strings to specified users, and
set the access level.
2-6
Basic Configuration
2
The default strings are:
• public - with read-only access. Authorized management stations are only able to
retrieve MIB objects.
• private - with read-write access. Authorized management stations are able to both
retrieve and modify MIB objects.
To prevent unauthorized access to the switch from SNMP version 1 or 2c clients, it is
recommended that you change the default community strings.
To configure a community string, complete the following steps:
1.From the Privileged Exec level global configuration mode prompt, type
“snmp-server community string mode,” where “string” is the community access
string and “mode” is rw (read/write) or ro (read only). Press <Enter>. (Note that
the default mode is read only.)
2.To remove an existing string, simply type “no snmp-server community string,”
where “string” is the community access string to remove. Press <Enter>.
Console(config)#snmp-server community admin rw4-118
Console(config)#snmp-server community private
Console(config)#
Note: If you do not intend to support access to SNMP version 1 and 2c clients, we
recommend that you delete both of the default community strings. If there are no
community strings, then SNMP management access from SNMP v1 and v2c
clients is disabled.
Trap Receivers
You can also specify SNMP stations that are to receive traps from the switch. To
configure a trap receiver, use the “snmp-server host” command. From the Privileged
Exec level global configuration mode prompt, type:
“snmp-server host host-address community-string
[version {1 | 2c | 3 {auth | noauth | priv}}]”
where “host-address” is the IP address for the trap receiver, “community-string”
specifies access rights for a version 1/2c host, or is the user name of a version 3
host, “version” indicates the SNMP client version, and “auth | noauth | priv” means
that authentication, no authentication, or authentication and privacy is used for v3
clients. Then press <Enter>. For a more detailed description of these parameters,
see “snmp-server host” on page 4-120. The following example creates a trap host
for each type of SNMP client.
Console(config)#snmp-server host 10.1.19.23 batman4-120
Console(config)#snmp-server host 10.1.19.98 robin version 2c
Console(config)#snmp-server host 10.1.19.34 barbie version 3 auth
Console(config)#
2-7
Initial Configuration
2
Configuring Access for SNMP Version 3 Clients
To configure management access for SNMPv3 clients, you need to first create a
view that defines the portions of MIB that the client can read or write, assign the view
to a group, and then assign the user to a group. The following example creates one
view called “mib-2” that includes the entire MIB-2 tree branch, and then another view
that includes the IEEE 802.1d bridge MIB. It assigns these respective read and read/
write views to a group call “r&d” and specifies group authentication via MD5 or SHA.
In the last step, it assigns a v3 user to this group, indicating that MD5 will be used for
authentication, provides the password “greenpeace” for authentication, and the
password “einstien” for encryption.
Console(config)#snmp-server view mib-2 1.3.6.1.2.1 included4-125
Console(config)#snmp-server view 802.1d 1.3.6.1.2.1.17 included
Console(config)#snmp-server group r&d v3 auth mib-2 802.1d4-126
Console(config)#snmp-server user steve group r&d v3 auth md5
greenpeace priv des56 einstien4-128
Console(config)#
For a more detailed explanation on how to configure the switch for access from
SNMP v3 clients, refer to “Simple Network Management Protocol” on page 3-38, or
refer to the specific CLI commands for SNMP starting on page 4-116.
Saving Configuration Settings
Configuration commands only modify the running configuration file and are not
saved when the switch is rebooted. To save all your configuration changes in
nonvolatile storage, you must copy the running configuration file to the start-up
configuration file using the “copy” command.
To save the current configuration settings, enter the following command:
1.From the Privileged Exec mode prompt, type “copy running-config
startup-config” and press <Enter>.
2.Enter the name of the start-up file. Press <Enter>.
Console#copy running-config startup-config
Startup configuration file name []: startup
\Write to FLASH Programming.
\Write to FLASH finish.
Success.
Console#
2-8
Managing System Files
2
Managing System Files
The switch’s flash memory supports three types of system files that can be managed
by the CLI program, Web interface, or SNMP. The switch’s file system allows files to
be uploaded and downloaded, copied, deleted, and set as a start-up file.
The three types of files are:
• Configuration — This file stores system configuration information and is created
when configuration settings are saved. Saved configuration files can be selected
as a system start-up file or can be uploaded via TFTP to a server for backup. A file
named “Factory_Default_Config.cfg” contains all the system default settings and
cannot be deleted from the system. See “Saving or Restoring Configuration
Settings” on page 3-22 for more information.
• Operation Code — System software that is executed after boot-up, also known as
run-time code. This code runs the switch operations and provides the CLI and Web
management interfaces. See “Managing Firmware” on page 3-19 for more
information.
• Diagnostic Code — Software that is run during system boot-up, also known as
POST (Power On Self-Test).
Due to the size limit of the flash memory, the switch supports only two operation
code files. However, you can have as many diagnostic code files and configuration
files as available flash memory space allows.
In the system flash memory, one file of each type must be set as the start-up file.
During a system boot, the diagnostic and operation code files set as the start-up file
are run, and then the start-up configuration file is loaded.
Note that configuration files should be downloaded using a file name that reflects the
contents or usage of the file settings. If you download directly to the running-config,
the system will reboot, and the settings will have to be copied from the
running-config to a permanent file.
2-9
Initial Configuration
2
2-10
Chapter 3: Configuring the Switch
Using the Web Interface
This switch provides an embedded HTTP Web agent. Using a Web browser you can
configure the switch and view statistics to monitor network activity. The Web agent
can be accessed by any computer on the network using a standard Web browser
(Internet Explorer 5.0 or above, or Netscape Navigator 6.2 or above).
Note:
You can also use the Command Line Interface (CLI) to manage the switch over a
serial connection to the console port or via Telnet.For more information on using
the CLI, refer to Chapter 4: “Command Line Interface.”
Prior to accessing the switch from a Web browser, be sure you have first performed
the following tasks:
1.Configure the switch with a valid IP address, subnet mask, and default gateway
using an out-of-band serial connection, BOOTP or DHCP protocol. (See
“Setting an IP Address” on page 2-4.)
2.Set user names and passwords using an out-of-band serial connection. Access
to the Web agent is controlled by the same user names and passwords as the
onboard configuration program. (See “Setting Passwords” on page 2-4.)
3.After you enter a user name and password, you will have access to the system
configuration program.
Notes: 1.
You are allowed three attempts to enter the correct password; on the third
failed attempt the current connection is terminated.
2. If you log into the Web interface as guest (Normal Exec level), you can view
the configuration settings or change the guest password. If you log in as
“admin” (Privileged Exec level), you can change the settings on any page.
3. If the path between your management station and this switch does not pass
through any device that uses the Spanning Tree Algorithm, then you can set
the switch port attached to your management station to fast forwarding (i.e.,
enable Admin Edge Port) to improve the switch’s response time to
management commands issued through the web interface. See “Configuring
Interface Settings” on page 3-130.
3-1
Configuring the Switch
3
Navigating the Web Browser Interface
To access the web-browser interface you must first enter a user name and
password. The administrator has Read/Write access to all configuration parameters
and statistics. The default user name and password for the administrator is “admin.”
Home Page
When your web browser connects with the switch’s web agent, the home page is
displayed as shown below. The home page displays the Main Menu on the left side
of the screen and System Information on the right side. The Main Menu links are
used to navigate to other menus, and display configuration parameters and
statistics.
Figure 3-1 Home Page
Note: Most of the examples in this chapter are based on the ES3526XA. Other than the
number of fixed ports, there are no major differences between the ES3526XA and
ES3552XA.
3-2
Panel Display
3
Configuration Options
Configurable parameters have a dialog box or a drop-down list. Once a configuration
change has been made on a page, be sure to click on the Apply button to confirm
the new setting. The following table summarizes the web page configuration
buttons.
Table 3-1 Configuration Options
ButtonAction.
RevertCancels specified values and restores current values prior to pressing Apply.
ApplySets specified values to the system.
HelpLinks directly to webhelp.
Notes: 1.
To ensure proper screen refresh, be sure that Internet Explorer 5.x is
configured as follows: Under the menu “Tools / Internet Options / General /
Temporary Internet Files / Settings,” the setting for item “Check for newer
versions of stored pages” should be “Every visit to the page.”
2. When using Internet Explorer 5.0, you may have to manually refresh the
screen after making configuration changes by pressing the browser’s refresh
button.
Panel Display
The web agent displays an image of the switch’s ports. The Mode can be set to
display different information for the ports, including Active (i.e., up or down), Duplex
(i.e., half or full duplex, or Flow Control (i.e., with or without flow control). Clicking on
the image of a port opens the Port Configuration page as described on page 3-91.
Figure 3-2 Panel Display
3-3
Configuring the Switch
3
Main Menu
Using the onboard web agent, you can define system parameters, manage and
control the switch, and all its ports, or monitor network conditions. The following
table briefly describes the selections available from this program.
Table 3-2 Main Menu
MenuDescriptionPage
System3-10
System InformationProvides basic system description, including contact information3-10
Switch InformationShows the number of ports, hardware/firmware version
Bridge ExtensionShows the bridge extension parameters3-13
IP ConfigurationSets the IP address for management access3-14
File3-19
CopyAllows the transfer and copying files3-19
DeleteAllows deletion of files from the flash memory3-20
Set StartupSets the startup file3-20
Line3-24
ConsoleSets console port connection parameters3-24
TelnetSets Telnet connection parameters.3-26
Log3-28
LogsStores and displays error messages3-28
System LogsSends error messages to a logging process3-28
Remote LogsConfigures the logging of messages to a remote logging process3-30
SMTP LogsSends an SMTP client message to a participating server3-32
ResetRestarts the switch3-34
SNTP3-35
Configuration Configures SNTP client settings, including broadcast mode or a
Clock Time Zone Sets the local time zone for the system clock3-38
SNMP3-38
Configuration Configures community strings and related trap functions3-40
Security3-54
User AccountsAssigns a new password for the current user3-54
Authentication SettingsConfigures authentication sequence, RADIUS and TACACS3-56
You can easily identify the system by displaying the device name, location and
contact information.
Field Attributes
• System Name – Name assigned to the switch system.
• Object ID – MIB II object ID for switch’s network management subsystem.
• Location – Specifies the system location.
• Contact – Administrator responsible for the system.
• System Up Time – Length of time the management agent has been up.
These additional parameters are displayed for the CLI.
• MAC Address – The physical layer address for this switch.
• Web server – Shows if management access via HTTP is enabled.
• Web server port – Shows the TCP port number used by the web interface.
• Web secure server – Shows if management access via HTTPS is enabled.
• Web secure server port – Shows the TCP port used by the HTTPS interface.
• Telnet server – Shows if management access via Telnet is enabled.
• Telnet port – Shows the TCP port used by the Telnet interface.
• Jumbo Frame – Shows if jumbo frames are enabled.
• POST result – Shows results of the power-on self-test.
Web – Click System, System Information. Specify the system name, location, and
contact information for the system administrator, then click Apply. (This page also
includes a Telnet button that allows access to the Command Line Interface via Telnet.)
Figure 3-3 System Information
3-10
Basic Configuration
CLI – Specify the hostname, location and contact information.
System description: Layer2+ Fast Ethernet Standalone Switch ES3526XA
System OID string: 1.3.6.1.4.1.259.6.10.74
System information
System Up time: 0 days, 2 hours, 4 minutes, and 7.13 seconds
System Name: R&D 5
System Location: WC 9
System Contact Ted
MAC address 00-30-F1-12-34-56
Web server: enabled
Web server port: 80
Web secure server: enabled
Web secure server port: 443
Telnet server: enabled
Telnet port: 23
Jumbo Frame: Disabled
POST result
DUMMY Test 1.................PASS
UART LOOP BACK Test..........PASS
DRAM Test....................PASS
Timer Test...................PASS
RTC Initialization...........PASS
Switch Int Loopback test.....PASS
Done All Pass.
Console#
3
Displaying Switch Hardware/Software Versions
Use the Switch Information page to display hardware/firmware version numbers for
the main board and management software, as well as the power status of the system.
Field Attributes
Main Board
• Serial Number – The serial number of the switch.
• Number of Ports – Number of built-in ports.
• Hardware Version – Hardware version of the main board.
• Internal Power Status – Displays the status of the internal power supply.
Management Software
• Loader Version – Version number of loader code.
• Boot-ROM Version – Version of Power-On Self-Test (POST) and boot code.
• Operation Code Version – Version number of runtime code.
• Role – Shows that this switch is operating as Master or Slave.
These additional parameters are displayed for the CLI.
• Unit - This is unit 1.
• Redundant Power Status – Displays the status of the redundant power supply.
Web – Click System, Switch Information.
Figure 3-4 Displaying Switch Information
CLI – Use the following command to display version information.
Console#show version4-68
Unit 1
Serial number: S542021059
Service tag:
Hardware version: R01A
Module A type: 1000BaseT
Module B type: 1000BaseT
Number of ports: 26
Main power status: up
Redundant power status :not present
Agent (master)
Unit ID: 1
Loader version: 2.2.1.4
Boot ROM version: 2.3.0.0
Operation code version: 2.3.1.16
Console#
3-12
Basic Configuration
3
Displaying Bridge Extension Capabilities
The Bridge MIB includes extensions for managed devices that support Multicast
Filtering, Traffic Classes, and Virtual LANs. You can access these extensions to
display default settings for the key variables.
Field Attributes
• Extended Multicast Filtering Services – This switch does not support the filtering
of individual multicast addresses based on GMRP (GARP Multicast Registration
Protocol).
• Traffic Classes – This switch provides mapping of user priorities to multiple traffic
classes. (Refer to “Class of Service Configuration” on page 3-158.)
• Static Entry Individual Port – This switch allows static filtering for unicast and
multicast addresses. (Refer to “Setting Static Addresses” on page 3-114.)
• VLAN Learning – This switch uses Independent VLAN Learning (IVL), where each
port maintains its own filtering database.
• Configurable PVID Tagging – This switch allows you to override the default Port
VLAN ID (PVID used in frame tags) and egress status (VLAN-Tagged or
Untagged) on each port. (Refer to “VLAN Configuration” on page 3-139.)
• Local VLAN Capable – This switch does not support multiple local bridges outside
of the scope of 802.1Q defined VLANs.
• GMRP – GARP Multicast Registration Protocol (GMRP) allows network devices to
register endstations with multicast groups. This switch does not support GMRP; it
uses the Internet Group Management Protocol (IGMP) to provide automatic
multicast filtering.
Web – Click System, Bridge Extension Configuration.
Figure 3-5 Bridge Extension Configuration
3-13
Configuring the Switch
3
CLI – Enter the following command.
Console#show bridge-ext4-195
Max support VLAN numbers: 255
Max support VLAN ID: 4094
Extended multicast filtering services: No
Static entry individual port: Yes
VLAN learning: IVL
Configurable PVID tagging: Yes
Local VLAN capable: No
Traffic classes: Enabled
Global GVRP status: Disabled
GMRP: Disabled
Console#
Setting the Switch’s IP Address
This section describes how to configure an IP interface for management access
over the network. The IP address for this switch is obtained via DHCP by default. To
manually configure an address, you need to change the switch’s default settings
(IP address 0.0.0.0 and netmask 255.0.0.0) to values that are compatible with your
network. You may also need to a establish a default gateway between the switch
and management stations that exist on another network segment.
You can manually configure a specific IP address, or direct the device to obtain an
address from a BOOTP or DHCP server. Valid IP addresses consist of four decimal
numbers, 0 to 255, separated by periods. Anything outside this format will not be
accepted by the CLI program.
Command Attributes
• Management VLAN – ID of the configured VLAN (1-4094, no leading zeroes). By
default, all ports on the switch are members of VLAN 1. However, the management
station can be attached to a port belonging to any VLAN, as long as that VLAN has
been assigned an IP address.
• IP Address Mode – Specifies whether IP functionality is enabled via manual
configuration (Static), Dynamic Host Configuration Protocol (DHCP), or Boot
Protocol (BOOTP). If DHCP/BOOTP is enabled, IP will not function until a reply has
been received from the server. Requests will be broadcast periodically by the
switch for an IP address. (DHCP/BOOTP values can include the IP address,
subnet mask, and default gateway.)
• IP Address – Address of the VLAN interface that is allowed management access.
Valid IP addresses consist of four numbers, 0 to 255, separated by periods.
(Default: 0.0.0.0)
• Subnet Mask – This mask identifies the host address bits used for routing to
specific subnets. (Default: 255.0.0.0)
• Gateway IP address – IP address of the gateway router between this device and
management stations that exist on other network segments. (Default: 0.0.0.0)
• MAC Address – The physical layer address for this switch.
• Restart DHCP – Requests a new IP address from the DHCP server.
3-14
Basic Configuration
Manual Configuration
Web – Click System, IP Configuration. Select the VLAN through which the
management station is attached, set the IP Address Mode to “Static,” enter the IP
address, subnet mask and gateway, then click Apply.
Figure 3-6 Manual IP Configuration
CLI – Specify the management interface, IP address and default gateway.
If your network provides DHCP/BOOTP services, you can configure the switch to be
dynamically configured by these services.
Web – Click System, IP Configuration. Specify the VLAN to which the management
station is attached, set the IP Address Mode to DHCP or BOOTP. Click Apply to
save your changes. Then click Restart DHCP to immediately request a new
address. Note that the switch will also broadcast a request for IP configuration
settings on each power reset.
Figure 3-7 IP Configuration using DHCP
Note: If you lose your management connection, use a console connection and enter
“show ip interface” to determine the new switch address.
CLI – Specify the management interface, and set the IP address mode to DHCP or
BOOTP, and then enter the “ip dhcp restart” command.
Console#config
Console(config)#interface vlan 14-131
Console(config-if)#ip address dhcp4-244
Console(config-if)#end
Console#ip dhcp restart4-246
Console#show ip interface4-246
IP address and netmask: 192.168.1.54 255.255.255.0 on VLAN 1,
and address mode: dhcp
Console#
Renewing DCHP – DHCP may lease addresses to clients indefinitely or for a
specific period of time. If the address expires or the switch is moved to another
network segment, you will lose management access to the switch. In this case, you
can reboot the switch or submit a client request to restart DHCP service via the CLI.
3-16
Basic Configuration
Web – If the address assigned by DHCP is no longer functioning, you will not be
able to renew the IP settings via the web interface. You can only restart DHCP
service via the web interface if the current address is still available.
CLI – Enter the following command to restart DHCP service.
Console#ip dhcp restart4-246
Console#
3
DHCP Relay and Option 82 Information
The switch supports DHCP relay service for attached host devices. If a subnet does
not include a DHCP server, you can relay DHCP client requests to a DHCP server
on another subnet.
When DHCP relay is enabled and the switch sees a DHCP request broadcast, it
inserts its own IP address into the request (so that the DHCP server knows the
subnet of the client), then forwards the packet to the DHCP server. When the server
receives the DHCP request, it allocates a free IP address for the DHCP client from
its defined scope for the DHCP client’s subnet, and sends a DHCP response back to
the switch. The switch then broadcasts the DHCP response to the client.
DHCP also provides a mechanism for sending information about the switch and its
DHCP clients to the DHCP server. Known as DHCP Option 82, it allows compatible
DHCP servers to use the information when assigning IP addresses, or to set other
services or policies for clients.
Using DHCP Relay Option 82, clients can be identified by the VLAN and switch port
to which they are connected rather than just their MAC address. DHCP client-server
exchange messages are then forwarded directly between the server and client
without having to flood them to the entire VLAN.
In some cases, the switch may receive DHCP packets from a client that already
includes DHCP Option 82 information. The switch can be configured to set the
action policy for these packets. Either the switch can discard the Option 82
information, keep the existing information, or replace it with the switch’s relay
information.
Command Usage
You must specify the IP address of at least one DHCP server. Otherwise, the
switch’s DHCP relay agent will not operate and all DHCP request and reply packets
will be flooded to the entire VLAN.
Command Attributes
• DHCP Relay Option 82 – Enables the DHCP relay agant with Option 82 support.
• DHCP Relay Option 82 Policy – Sets the DHCP relay policy for DHCP client
packets that include Option 82 information. (Default: Drop)
• Replace – Overwrites the DHCP client packet information with the switch’s relay
information.
• Keep – Retains the client’s DHCP information.
3-17
Configuring the Switch
3
• Drop – Discards the Option 82 information in a packet and then floods it to the
entire VLAN.
• DHCP Relay Server – IP addresses of DHCP servers to be used by the switch’s
DHCP relay agent in order of preference. Up to five servers can be specified.
Web – Click System, IP Configuration. Enable the DHCP Relay Option 82 function,
set the Option 82 policy, and specify at least one DHCP server IP address. Click
Apply.
Figure 3-8 DHCP Relay Option 82 Configuration
CLI – This example enables DHCP relay with Option 82, and sets the policy as
replace.
Console(config)#ip dhcp relay server 192.168.1.9 192.168.1.54
Console(config)#ip dhcp relay information option 4-241
Console(config)#ip dhcp relay information policy replace 4-242
Console(config)#exit
Console#show ip dhcp-relay
Status of DHCP relay option82:
Insertion of option82 is Enabled.
DHCP option policy :replace.
DHCP relay-server address 192.168.1.9 192.168.1.54 0.0.0.0 0.0.0.0
0.0.0.0
Console#
3-18
Basic Configuration
3
Managing Firmware
You can upload/download firmware to or from a TFTP server. By saving runtime
code to a file on a TFTP server, that file can later be downloaded to the switch to
restore operation. You can also set the switch to use new firmware without
overwriting the previous version. You must specify the method of file transfer, along
with the file type and file names as required.
Command Attributes
• File Transfer Method – The firmware copy operation includes these options:
- file to file – Copies a file within the switch directory, assigning it a new name.
- file to tftp – Copies a file from the switch to a TFTP server.
- tftp to file – Copies a file from a TFTP server to the switch.
- file to unit
- unit to file
• TFTP Server IP Address – The IP address of a TFTP server.
• File Type – Specify opcode (operational code) to copy firmware.
• File Name –
the file name should not be a period (.), and the maximum length for file names on
the TFTP server is 127 characters or 31 characters for files on the switch.
(Valid characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
Note:
1
– Copies a file from this switch to another unit in the stack.
1
– Copies a file from another unit in the stack to this switch.
The file name should not contain slashes (\ or /),
Up to two copies of the system software (i.e., the runtime firmware) can be stored
in the file directory on the switch. The currently designated startup version of this
file cannot be deleted.
the leading letter of
1. These operations are not supported for this switch.
3-19
Configuring the Switch
3
Downloading System Software from a Server
When downloading runtime code, you can specify the destination file name to
replace the current image, or first download the file using a different name from the
current runtime code file, and then set the new file as the startup file.
Web –Click System, File Management, Copy Operation. Select “tftp to file” as the file
transfer method, enter the IP address of the TFTP server, set the file type to
“opcode,” enter the file name of the software to download, select a file on the switch
to overwrite or specify a new file name, then click Apply. If you replaced the current
firmware used for startup and want to start using the new operation code, reboot the
system via the System/Reset menu.
Figure 3-9 Operation Code Image File Transfer
If you download to a new destination file, go to the System/File/Set Start-Up menu,
mark the operation code file used at startup, and click Apply. To start the new
firmware, reboot the system via the System/Reset menu.
Figure 3-10 Select Start-Up Operation File
3-20
Basic Configuration
3
To delete a file select System, File, Delete. Select the file name from the given list by
checking the tick box and click Apply. Note that t
startup code cannot be deleted.
Figure 3-11 Deleting Files
he file currently designated as the
CLI – To download new firmware form a TFTP server, enter the IP address of the
TFTP server, select “opcode” as the file type, then enter the source and destination
file names. When the file has finished downloading, set the new file to start up the
system, and then restart the switch.
To start the new firmware, enter the “reload” command or reboot the system.
Console#copy tftp file4-70
TFTP server ip address: 192.168.1.23
Choose file type:
-Write to FLASH finish.
Success.
Console#config
Console(config)#boot system opcode:ES3552XA_Opcpde_V2262.bix4-75
Console(config)#exit
Console#reload4-23
3-21
Configuring the Switch
3
Saving or Restoring Configuration Settings
You can upload/download configuration settings to/from a TFTP server. The
configuration files can be later downloaded to restore the switch’s settings.
Command Attributes
• File Transfer Method – The configuration copy operation includes these options:
- file to file – Copies a file within the switch directory, assigning it a new name.
- file to running-config – Copies a file in the switch to the running configuration.
- file to startup-config – Copies a file in the switch to the startup configuration.
- file to tftp – Copies a file from the switch to a TFTP server.
- running-config to file – Copies the running configuration to a file.
- running-config to startup-config – Copies the running config to the startup config.
- running-config to tftp – Copies the running configuration to a TFTP server.
- startup-config to file – Copies the startup configuration to a file on the switch.
- startup-config to running-config – Copies the startup config to the running config.
- startup-config to tftp – Copies the startup configuration to a TFTP server.
- tftp to file – Copies a file from a TFTP server to the switch.
- tftp to running-config – Copies a file from a TFTP server to the running config.
- tftp to startup-config – Copies a file from a TFTP server to the startup config.
- file to unit
- unit to file
• TFTP Server IP Address – The IP address of a TFTP server.
• File Type – Specify config (configuration) to copy configuration settings.
•
File Name
the file name should not be a period (.), and the maximum length for file names on
the TFTP server is 127 characters or 31 characters for files on the switch. (Valid
characters: A-Z, a-z, 0-9, “.”, “-”, “_”)
Note:
2
– Copies a file from this switch to another unit in the stack.
2
– Copies a file from another unit in the stack to this switch.
— The file name should not contain slashes (\ or /),
The maximum number of user-defined configuration files is limited only by
available flash memory space.
the leading letter of
2. These operations are not supported for this switch.
3-22
Basic Configuration
3
Downloading Configuration Settings from a Server
You can download the configuration file under a new file name and then set it as the
startup file, or you can specify the current startup configuration file as the destination
file to directly replace it. Note that the file “Factory_Default_Config.cfg” can be
copied to the TFTP server, but cannot be used as the destination on the switch.
Web – Click System, File, Copy. Select “tftp to startup-config” or “tftp to file” and
enter the IP address of the TFTP server. Specify the name of the file to download
and select a file on the switch to overwrite or specify a new file name, then click
Apply.
Figure 3-12 Copy Configuration Settings
If you download to a new file name using “tftp to startup-config” or “tftp to file,” the file
is automatically set as the start-up configuration file. To use the new settings, reboot
the system via the System/Reset menu.
Note that you can also select any configuration file as the start-up configuration by
using the System/File/Set Start-Up page.
Figure 3-13 Setting the Startup Configuration Settings
3-23
Configuring the Switch
3
CLI – Enter the IP address of the TFTP server, specify the source file on the server,
set the startup file name on the switch, and then restart the switch.
Console#copy tftp startup-config4-70
TFTP server ip address: 192.168.1.19
Source configuration file name: config-1
Startup configuration file name [] : startup
\Write to FLASH Programming.
-Write to FLASH finish.
Success.
Console#reload
To select another configuration file as the start-up configuration, use the boot
system command and then restart the switch.
Console#config
Console(config)#boot system config: startup-new4-75
Console(config)#exit
Console#reload4-23
Console Port Settings
You can access the onboard configuration program by attaching a VT100
compatible device to the switch’s serial console port. Management access through
the console port is controlled by various parameters, including a password, timeouts,
and basic communication settings. These parameters can be configured via the
Web or CLI interface.
Command Attributes
• Login Timeout – Sets the interval that the system waits for a user to log into the
CLI. If a login attempt is not detected within the timeout interval, the connection is
terminated for the session. (Range: 0-300 seconds; Default: 0)
• Exec Timeout – Sets the interval that the system waits until user input is detected.
If user input is not detected within the timeout interval, the current session is
terminated. (Range: 0-65535 seconds; Default: 0 seconds)
• Password Threshold – Sets the password intrusion threshold, which limits the
number of failed logon attempts. When the logon attempt threshold is reached, the
system interface becomes silent for a specified amount of time (set by the Silent
Time parameter) before allowing the next logon attempt.
(Range: 0-120; Default: 3 attempts)
• Silent Time – Sets the amount of time the management console is inaccessible
after the number of unsuccessful logon attempts has been exceeded.
(Range: 0-65535; Default: 0)
• Data Bits – Sets the number of data bits per character that are interpreted and
generated by the console port. If parity is being generated, specify 7 data bits per
character. If no parity is required, specify 8 data bits per character. (Default: 8 bits)
• Parity – Defines the generation of a parity bit. Communication protocols provided
by some terminals can require a specific parity bit setting. Specify Even, Odd, or
None. (Default: None)
3-24
Basic Configuration
• Speed – Sets the terminal line’s baud rate for transmit (to terminal) and receive
(from terminal). Set the speed to match the baud rate of the device connected to
the serial port. (Range: 9600, 19200, 38400, 57600, or 115200 baud, Auto;
Default: 9600 bps)
• Stop Bits – Sets the number of the stop bits transmitted per byte.
(Range: 1-2; Default: 1 stop bit)
• Password
started on a line with password protection, the system prompts for the password.
If you enter the correct password, the system shows a prompt.
(Default: No password)
• Login
single global password as configured for the Password parameter, or by
passwords set up for specific user-name accounts. (Default: Local)
Web – Click System, Line, Console. Specify the console port connection parameters
as required, then click Apply.
3
– Specifies a password for the line connection. When a connection is
3
– Enables password checking at login. You can select authentication by a
3
3. CLI only.
Figure 3-14 Console Port Settings
3-25
Configuring the Switch
3
CLI – Enter Line Configuration mode for the console, then specify the connection
parameters as required. To display the current console port settings, use the show line command from the Normal Exec level.
You can access the onboard configuration program over the network using Telnet
(i.e., a virtual terminal). Management access via Telnet can be enabled/disabled and
other various parameters set, including the TCP port number, timeouts, and a
password. These parameters can be configured via the Web or CLI interface.
Command Attributes
• Telnet Status – Enables or disables Telnet access to the switch.
(Default: Enabled)
• Telnet Port Number – Sets the TCP port number for Telnet on the switch.
(Default: 23)
• Login Timeout – Sets the interval that the system waits for a user to log into the
CLI. If a login attempt is not detected within the timeout interval, the connection is
terminated for the session. (Range: 0-300 seconds; Default: 300 seconds)
• Exec Timeout – Sets the interval that the system waits until user input is detected.
If user input is not detected within the timeout interval, the current session is
terminated. (Range: 0-65535 seconds; Default: 600 seconds)
3-26
Basic Configuration
• Password Threshold – Sets the password intrusion threshold, which limits the
number of failed logon attempts. When the logon attempt threshold is reached, the
system interface becomes silent for a specified amount of time (set by the Silent
Time parameter) before allowing the next logon attempt.
(Range: 0-120; Default: 3 attempts)
4
• Password
started on a line with password protection, the system prompts for the password.
If you enter the correct password, the system shows a prompt. (Default: No
password)
• Login
single global password as configured for the Password parameter, or by
passwords set up for specific user-name accounts. (Default: Local)
Web – Click System, Line, Telnet. Specify the connection parameters for Telnet
access, then click Apply.
– Specifies a password for the line connection. When a connection is
4
– Enables password checking at login. You can select authentication by a
3
4. CLI only.
Figure 3-15 Enabling Telnet
3-27
Configuring the Switch
3
CLI – Enter Line Configuration mode for a virtual terminal, then specify the
connection parameters as required. To display the current virtual terminal settings,
use the show line command from the Normal Exec level.
The switch allows you to control the logging of error messages, including the type of
events that are recorded in switch memory, logging to a remote System Log (syslog)
server, and displays a list of recent event messages.
System Log Configuration
The system allows you to enable or disable event logging, and specify which levels
are logged to RAM or flash memory.
Severe error messages that are logged to flash memory are permanently stored in
the switch to assist in troubleshooting network problems. Up to 4096 log entries can
be stored in the flash memory, with the oldest entries being overwritten first when the
available log memory (256 kilobytes) has been exceeded.
The System Logs page allows you to configure and limit system messages that are
logged to flash or RAM memory. The default is for event levels 0 to 3 to be logged to
flash and levels 0 to 6 to be logged to RAM.
Command Attributes
• System Log Status – Enables/disables the logging of debug or error messages to
the logging process. (Default: Enabled)
• Flash Level – Limits log messages saved to the switch’s permanent flash memory
for all levels up to the specified level. For example, if level 3 is specified, all
messages from level 0 to level 3 will be logged to flash. (Range: 0-7, Default: 3)
3-28
Basic Configuration
Table 3-3 Logging Levels
LevelSeverity NameDescription
7DebugDebugging messages
6InformationalInformational messages only
5NoticeNormal but significant condition, such as cold start
2CriticalCritical conditions (e.g., memory allocation, or free memory
error - resource exhausted)
1AlertImmediate action needed
0EmergencySystem unusable
* There are only Level 2, 5 and 6 error messages for the current firmware release.
3
• RAM Level – Limits log messages saved to the switch’s temporary RAM memory
for all levels up to the specified level. For example, if level 7 is specified, all
messages from level 0 to level 7 will be logged to RAM. (Range: 0-7, Default: 6)
The Flash Level must be equal to or less than the RAM Level.
Note:
Web – Click System, Log, System Logs. Specify System Log Status, then
change
the level of messages to be logged to RAM and flash memory, then click Apply.
Figure 3-16 System Logs
CLI – Enable system logging and then specify the level of messages to be logged to
RAM and flash memory. Use the show logging command to display the current
settings.
Console(config)#logging on4-44
Console(config)#logging history ram 04-45
Console(config)#end
Console#show logging flash4-48
Syslog logging: Enabled
History logging in FLASH: level emergencies
Console#
3-29
Configuring the Switch
3
Remote Log Configuration
The Remote Logs page allows you to configure the logging of messages that are
sent to syslog servers or other management stations. You can also limit the error
messages sent to only those messages below a specified level.
Command Attributes
• Remote Log Status – Enables/disables the logging of debug or error messages
to the remote logging process. (Default: Enabled)
• Logging Facility – Sets the facility type for remote logging of syslog messages.
There are eight facility types specified by values of 16 to 23. The facility type is
used by the syslog server to dispatch log messages to an appropriate service.
The attribute specifies the facility type tag sent in syslog messages. (See RFC
3164.) This type has no effect on the kind of messages reported by the switch.
However, it may be used by the syslog server to process messages, such as
sorting or storing messages in the corresponding database. (Range: 16-23,
Default: 23)
• Logging Trap – Limits log messages that are sent to the remote syslog server for
all levels up to the specified level. For example, if level 3 is specified, all messages
from level 0 to level 3 will be sent to the remote server. (Range: 0-7, Default: 6)
• Host IP List – Displays the list of remote server IP addresses that receive the
syslog messages. The maximum number of host IP addresses allowed is five.
• Host IP Address – Specifies a new server IP address to add to the Host IP List.
Web – Click System, Log, Remote Logs. To add an IP address to the Host IP List,
type the new IP address in the Host IP Address box, and then click Add. To delete
an IP address, click the entry in the Host IP List, and then click Remove.
3-30
Figure 3-17 Remote Logs
Basic Configuration
3
CLI – Enter the syslog server host IP address, choose the facility type and set the
logging trap.
Console(config)#logging host 192.168.1.154-46
Console(config)#logging facility 234-46
Console(config)#logging trap 44-47
Console(config)#end
Console#show logging trap4-47
Syslog logging: Enabled
REMOTELOG status: Enabled
REMOTELOG facility type: local use 7
REMOTELOG level type: Warning conditions
REMOTELOG server ip address: 192.168.1.15
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
REMOTELOG server ip address: 0.0.0.0
Console#
Displaying Log Messages
The Logs page allows you to scroll through the logged system and event messages.
The switch can store up to 2048 log entries in temporary random access memory
(RAM; i.e., memory flushed on power reset) and up to 4096 entries in permanent
flash memory.
Web – Click System, Log, Logs.
Figure 3-18 Displaying Logs
CLI – This example shows the event message stored in RAM.
To alert system administrators of problems, the switch can use SMTP (Simple Mail
Transfer Protocol) to send email messages when triggered by logging events of a
specified level. The messages are sent to specified SMTP servers on the network
and can be retrieved using POP or IMAP clients.
Command Attributes
• Admin Status – Enables/disables the SMTP function. (Default: Enabled)
• Email Source Address – Sets the email address used for the “From” field in alert
messages. You may use a symbolic email address that identifies the switch, or the
address of an administrator responsible for the switch.
• Severity – Sets the syslog severity threshold level (see table on page 3-29) used
to trigger alert messages. All events at this level or higher will be sent to the
configured email recipients. For example, using Level 7 will report all events from
level 7 to level 0. (Default: Level 7)
• SMTP Server List – Specifies a list of up to three recipient SMTP servers. The
switch attempts to connect to the other listed servers if the first fails. Use the New
SMTP Server text field and the Add/Remove buttons to configure the list.
• Email Destination Address List – Specifies the email recipients of alert
messages. You can specify up to five recipients. Use the New Email Destination
Address text field and the Add/Remove buttons to configure the list.
3-32
Basic Configuration
Web – Click System, Log, SMTP. Enable SMTP, specify a source email address,
and select the minimum severity level. To add an IP address to the SMTP Server
List, type the new IP address in the SMTP Server field and click Add. To delete an IP
address, click the entry in the SMTP Server List and click Remove. Specify up to five
email addresses to receive the alert messages, and click Apply.
3
Figure 3-19 Enabling and Configuring SMTP Alerts
3-33
Configuring the Switch
3
CLI – Enter the IP address of at least one SMTP server, set the syslog severity level
to trigger an email message, and specify the switch (source) and up to five recipient
(destination) email addresses. Enable SMTP with the logging sendmail command
to complete the configuration. Use the show logging sendmail command to display
the current SMTP configuration.
Web – Click System, Reset to reboot the switch. When prompted, confirm that you
want reset the switch.
Figure 3-20 Resetting the System
CLI – Use the reload command to restart the switch. When prompted, confirm that
you want to reset the switch.
Console#reload4-23
System will be restarted, continue <y/n>? y
Note:
When restarting the system, it will always run the Power-On Self-Test.
3-34
Basic Configuration
3
Setting the System Clock
Simple Network Time Protocol (SNTP) allows the switch to set its internal clock
based on periodic updates from a Network Time Protocol (NTP) server. Maintaining
an accurate time on the switch enables the system log to record meaningful dates
and times for event entries. You can also manually set the clock using the CLI. (See
“calendar set” on page 4-62.) If the clock is not set, the switch will only record the
time from the factory default set at the last bootup.
When the SNTP client is enabled, the switch periodically sends a request for a time
update to a configured time server. You can configure up to three time server IP
addresses. The switch will attempt to poll each server in the configured sequence.
For more robust, secure time updates from trusted servers, the NTP client can be
enabled instead of the SNTP client. Using the NTP client provides more reliable time
updates, since the updates are collected from many NTP servers, then filtered and
selected using an algorithm that determines the most accurate time. The NTP client
also uses authentication and encryption to ensure that updates are received from
authorized servers only.
The SNTP and NTP client cannot be enabled at the same time.
Note:
Configuring SNTP
You can configure the switch to send time synchronization requests to time servers.
Command Attributes
• SNTP Client – Configures the switch to operate as an SNTP client. This requires
at least one time server to be specified in the SNTP Server field. (Default: Disabled)
• SNTP Poll Interval – Sets the interval between sending requests for a time update
from a time server. (Range: 16-16384 seconds; Default: 16 seconds)
• SNTP Server – Sets the IP address for up to three time servers. The switch
attempts to update the time from the first server, if this fails it attempts an update
from the next server in the sequence.
Web – Select NTP/SNTP, Configuration. Modify any of the required parameters, and
click Apply.
Figure 3-21 SNTP Configuration
3-35
Configuring the Switch
3
CLI – This example configures the switch to operate as an SNTP unicast client and
then displays the current time and settings.
Console(config)#sntp server 10.1.0.19 137.82.140.80 128.250.36.24-55
Console(config)#sntp poll 604-56
Console(config)#sntp client4-54
Console(config)#exit
Console#show sntp
Current time: Jan 6 14:56:05 2004
Poll interval: 60
Current mode: unicast
SNTP status : Enabled
SNTP server 10.1.0.19 137.82.140.80 128.250.36.2
Current server: 128.250.36.2
Console#
Configuring NTP
The NTP client allows you to configure up to 50 NTP servers to poll for time updates.
You can also enable authentication to ensure that reliable updates are received from
only authorized NTP servers. The authentication keys and their associated key
number must be centrally managed and manually distributed to NTP servers and
clients. The key numbers and key values must match on both the server and client.
Command Attributes
• NTP Client – Configures the switch to operate as an NTP client. This requires at
least one time server to be specified in the NTP Server list. (Default: Disabled)
• NTP Polling Interval – Sets the interval between sending requests for a time
update from NTP servers. (Range: 16-16384 seconds; Default: 16 seconds)
• NTP Authenticate – Enables authentication for time requests and updates
between the switch and NTP servers. (Default: Disabled)
• NTP Server – Sets the IP address for an NTP server to be polled. The switch
requests an update from all configured servers, then determines the most accurate
time update from the responses received.
• Version – Specifies the NTP version supported by the server. (Range: 1-3;
Default: 3)
• Authenticate Key – Specifies the number of the key in the NTP Authentication Key
List to use for authentication with the configured server. The authentication key
must match the key configured on the NTP server.
• Key Number – A number that specifies a key value in the NTP Authentication Key
List. Up to 255 keys can be configured in the NTP Authentication Key List. Note
that key numbers and values must match on both the server and client. (Range:
1-65535)
• Key Context – Specifies an MD5 authentication key string. The key string can be
up to 32 case-sensitive printable ASCII characters (no spaces).
Web – Select NTP/SNTP, Configuration. Modify any of the required parameters, and
click Apply.
3-36
Basic Configuration
Figure 3-22 NTP Client Configuration
CLI – This example configures the switch to operate as an NTP client and then
displays the current settings.
Console(config)#ntp authentication-key 19 md5 thisiskey194-59
Console(config)#ntp authentication-key 30 md5 ntpkey30
Console(config)#ntp server 192.168.3.204-57
Console(config)#ntp server 192.168.3.21
Console(config)#ntp server 192.168.4.22 version 2
Console(config)#ntp server 192.168.5.23 version 3 key 19
Console(config)#ntp poll 604-58
Console(config)#ntp client4-57
Console(config)#ntp authenticate4-59
Console(config)#exit
Console#show ntp4-60
Current time: Jan 1 02:58:58 2001
Poll interval: 60
Current mode: unicast
NTP status : Enabled NTP Authenticate status : Enabled
Last Update NTP Server: 0.0.0.0 Port: 0
Last Update time: Dec 31 00:00:00 2000 UTC
NTP Server 192.168.3.20 version 3
NTP Server 192.168.3.21 version 3
NTP Server 192.168.4.22 version 2
NTP Server 192.168.5.23 version 3 key 19
NTP Authentication-Key 19 md5 Q33O16Q6338241J022S29Q731K7 7
NTP Authentication-Key 30 md5 D2V8777I51K1132K3552L26R6141O4 7
Console#
3
3-37
Configuring the Switch
3
Setting the Time Zone
SNTP uses Coordinated Universal Time (or UTC, formerly Greenwich Mean Time,
or GMT) based on the time at the Earth’s prime meridian, zero degrees longitude. To
display a time corresponding to your local time, you must indicate the number of
hours and minutes your time zone is east (before) or west (after) of UTC.
Command Attributes
• Current Time – Displays the current time.
• Name – Assigns a name to the time zone. (Range: 1-29 characters)
• Hours (0-12) – The number of hours before/after UTC.
• Minutes (0-59) – The number of minutes before/after UTC.
• Direction – Configures the time zone to be before (east) or after (west) UTC.
Web – Select SNTP, Clock Time Zone. Set the offset for your time zone relative to
the UTC, and click Apply.
Figure 3-23 Setting the System Clock
CLI - This example shows how to set the time zone for the system clock.
SNMP is a communication protocol designed specifically for managing devices on a
network. Equipment commonly managed with SNMP includes switches, routers and
host computers. SNMP is typically used to configure these devices for proper
operation in a network environment, as well as to monitor them to evaluate
performance or detect potential problems.
Managed devices supporting SNMP contain software, which runs locally on the
device and is referred to as an agent. A defined set of variables, known as managed
objects, is maintained by the SNMP agent and used to manage the device. These
objects are defined in a Management Information Base (MIB) that provides a
standard presentation of the information controlled by the agent. SNMP defines both
3-38
Simple Network Management Protocol
3
the format of the MIB specifications and the protocol used to access this information
over the network.
The switch includes an onboard agent that supports SNMP versions 1, 2c, and 3.
This agent continuously monitors the status of the switch hardware, as well as the
traffic passing through its ports. A network management station can access this
information using software such as HP OpenView. Access to the onboard agent
from clients using SNMP v1 and v2c is controlled by community strings. To
communicate with the switch, the management station must first submit a valid
community string for authentication.
Access to the switch using from clients using SNMPv3 provides additional security
features that cover message integrity, authentication, and encryption; as well as
controlling user access to specific areas of the MIB tree.
The SNMPv3 security structure consists of security models, with each model having
it’s own security levels. There are three security models defined, SNMPv1,
SNMPv2c, and SNMPv3. Users are assigned to “groups” that are defined by a
security model and specified security levels. Each group also has a defined security
access to set of MIB objects for reading and writing, which are known as “views.”
The switch has a default view (all MIB objects) and default groups defined for
security models v1 and v2c. The following table shows the security models and
levels available and the system default settings.
Table 3-4 SNMPv3 Security Models and Levels
Model LevelGroupRead View Write View Notify View Security
v1noAuthNoPriv public
(read only)
v1noAuthNoPriv private
(read/write)
v1noAuthNoPriv user defined user defined user defined user defined Community string only
v2cnoAuthNoPriv public
(read only)
v2cnoAuthNoPriv private
(read/write)
v2cnoAuthNoPriv user defined user defined user defined user defined Community string only
v3noAuthNoPriv user defined user defined user defined user defined A user name match only
v3AuthNoPrivuser defined user defined user defined user defined Provides user
v3AuthPrivuser defined user defined user defined user defined Provides user
defaultview nonenoneCommunity string only
defaultview defaultview noneCommunity string only
defaultview nonenoneCommunity string only
defaultview defaultview noneCommunity string only
authentication via MD5 or
SHA algorithms
authentication via MD5 or
SHA algorithms and data
privacy using DES 56-bit
encryption
Note:
The predefined default groups and view can be deleted from the system. You can
then define customized groups and views for the SNMP clients that require access.
3-39
Configuring the Switch
3
Enabling the SNMP Agent
Enables SNMPv3 service for all management clients (i.e., versions 1, 2c, 3).
Command Attributes
SNMP Agent Status – Enables SNMP on the switch.
Web – Click SNMP, Agent Status. Enable the SNMP Agent by marking the Enabled
checkbox, and click Apply.
Figure 3-24 Enabling the SNMP Agent
CLI – The following example enables SNMP on the switch.
Console(config)#snmp-server4-117
Console(config)#
Setting Community Access Strings
You may configure up to five community strings authorized for management access
by clients using SNMP v1 and v2c. All community strings used for IP Trap Managers
should be listed in this table. For security reasons, you should consider removing the
default strings.
Command Attributes
• SNMP Community Capability – The switch supports up to five community strings.
• Current – Displays a list of the community strings currently configured.
• Community String – A community string that acts like a password and permits
access to the SNMP protocol.
• Access Mode – Specifies the access rights for the community string:
- Read-Only – Authorized management stations are only able to retrieve MIB
objects.
- Read/Write – Authorized management stations are able to both retrieve and
modify MIB objects.
3-40
Specifying Trap Managers and Trap Types
Web – Click SNMP, Configuration. Add new community strings as required, select
the access rights from the Access Mode drop-down list, then click Add.
Figure 3-25 Configuring SNMP Community Strings
CLI – The following example adds the string “spiderman” with read/write access.
Console(config)#snmp-server community spiderman rw4-118
Console(config)#
3
Specifying Trap Managers and Trap Types
Traps indicating status changes are issued by the switch to specified trap managers.
You must specify trap managers so that key events are reported by this switch to
your management station (using network management platforms such as HP
OpenView). You can specify up to five management stations that will receive
authentication failure messages and other trap messages from the switch.
Command Usage
• If you specify an SNMP Version 3 host, then the “Trap Manager Community String”
is interpreted as an SNMP user name. If you use V3 authentication or encryption
options (authNoPriv or authPriv), the user name must first be defined in the
SNMPv3 Users page (page 3-45). Otherwise, the authentication password and/or
privacy password will not exist, and the switch will not authorize SNMP access for
the host. However, if you specify a V3 host with the no authentication (noAuth)
option, an SNMP user account will be automatically generated, and the switch will
authorize SNMP access for the host.
• Notifications are issued by the switch as trap messages by default. The recipient
of a trap message does not send a response to the switch. Traps are therefore not
as reliable as inform messages, which include a request for acknowledgement of
receipt. Informs can be used to ensure that critical information is received by the
host. However, note that informs consume more system resources because they
must be kept in memory until a response is received. Informs also add to network
traffic. You should consider these effects when deciding whether to issue
notifications as traps or informs.
3-41
Configuring the Switch
3
To send an inform to a SNMPv2c host, complete these steps:
1.Enable the SNMP agent (page 3-54).
2.Enable trap informs as described in the following pages.
3.Create a view with the required notification messages (page 3-53).
4.Create a group that includes the required notify view (page 3-49).
To send an inform to a SNMPv3 host, complete these steps:
1.Enable the SNMP agent (page 3-54).
2.Enable trap informs as described in the following pages.
3.Create a view with the required notification messages (page 3-53).
4.Create a group that includes the required notify view (page 3-49).
5.Specify a remote engine ID where the user resides (page 3-44).
6.Then configure a remote user (page 3-47).
Command Attributes
• Trap Manager Capability – This switch supports up to five trap managers.
• Current – Displays a list of the trap managers currently configured.
• Trap Manager IP Address – IP address of a new management station to receive
notification messages.
• Trap Manager Community String – Specifies a valid community string for the
new trap manager entry. Though you can set this string in the Trap Managers table,
we recommend that you define this string in the SNMP Configuration page (for
Version 1 or 2c clients), or define a corresponding “User Name” in the SNMPv3
Users page (for Version 3 clients). (Range: 1-32 characters, case sensitive)
• Trap UDP Port – Specifies the UDP port number used by the trap manager.
• Trap Version – Indicates if the user is running SNMP v1, v2c, or v3. (Default: v1)
• Trap Security Level – When trap version 3 is selected, you must specify one of
the following security levels. (Default: noAuthNoPriv)
- noAuthNoPriv – There is no authentication or encryption used in SNMP
communications.
- AuthNoPriv – SNMP communications use authentication, but the data is not
encrypted (only available for the SNMPv3 security model).
- AuthPriv – SNMP communications use both authentication and encryption (only
available for the SNMPv3 security model).
• Trap Inform – Notifications are sent as inform messages. Note that this option is
only available for version 2c and 3 hosts. (Default: traps are used)
- Timeout – The number of seconds to wait for an acknowledgment before
resending an inform message. (Range: 0-2147483647 centiseconds;
Default: 1500 centiseconds)
- Retry times – The maximum number of times to resend an inform message if
the recipient does not acknowledge receipt. (Range: 0-255; Default: 3)
3-42
Configuring SNMPv3 Management Access
• Enable Authentication Traps5 – Issues a notification message to specified IP
trap managers whenever authentication of an SNMP request fails.
(Default: Enabled)
• Enable Link-up and Link-down Traps – Issues a notification message whenever
a port link is established or broken. (Default: Enabled)
Web – Click SNMP, Configuration. Enter the IP address and community string for
each management station that will receive trap messages, specify the UDP port,
SNMP trap version, trap security level (for v3 clients), trap inform settings (for v2c/v3
clients), and then click Add. Select the trap types required using the check boxes for
Authentication and Link-up/down traps, and then click Apply.
3
Figure 3-26 Configuring SNMP Trap Managers
CLI – This example adds a trap manager and enables authentication traps.
Console(config)#snmp-server host 10.1.19.23 private version 2c
To configure SNMPv3 management access to the switch, follow these steps:
1. If you want to change the default engine ID, do so before configuring other
SNMP parameters.
2. Specify read and write access views for the switch MIB tree.
3. Configure SNMP user groups with the required security model (i.e., SNMP v1,
5. These are legacy notifications and therefore when used for SNMP Version 3 hosts, they must
be enabled in conjunction with the corresponding entries in the Notification View (page 3-49).
3-43
Configuring the Switch
3
v2c or v3) and security level (i.e., authentication and privacy).
4. Assign SNMP users to groups, along with their specific authentication and
privacy passwords.
Setting a Local Engine ID
An SNMPv3 engine is an independent SNMP agent that resides on the switch. This
engine protects against message replay, delay, and redirection. The engine ID is
also used in combination with user passwords to generate the security keys for
authenticating and encrypting SNMPv3 packets.
A local engine ID is automatically generated that is unique to the switch. This is
referred to as the default engine ID. If the local engineID is deleted or changed, all
SNMP users will be cleared. You will need to reconfigure all existing users.
A new engine ID can be specified by entering 1 to 26 hexadecimal characters. If less
than 26 characters are specified, trailing zeroes are added to the value. For
example, the value “1234” is equivalent to “1234” followed by 22 zeroes.
Web – Click SNMP, SNMPv3, Engine ID. Enter an ID of up to 26 hexadecimal
characters and then click Save.
Figure 3-27 Setting the SNMPv3 Engine ID
CLI – This example sets an SNMPv3 engine ID.
Console(config)#snmp-server engine-id local 12345abcdef4-123
Console(config)#exit
Console#show snmp engine-id4-124
Local SNMP engineID: 8000002a8000000000e8666672
Local SNMP engineBoots: 1
Console#
Specifying a Remote Engine ID
To send inform messages to an SNMPv3 user on a remote device, you must first
specify the engine identifier for the SNMP agent on the remote device where the
user resides. The remote engine ID is used to compute the security digest for
authenticating and encrypting packets sent to a user on the remote host.
SNMP passwords are localized using the engine ID of the authoritative agent. For
informs, the authoritative SNMP agent is the remote agent. You therefore need to
3-44
Configuring SNMPv3 Management Access
configure the remote agent’s SNMP engine ID before you can send proxy requests
or informs to it. (See “Specifying Trap Managers and Trap Types” on page 3-41 and
“Configuring Remote SNMPv3 Users” on page 3-47.)
The engine ID can be specified by entering 1 to 26 hexadecimal characters. If less
than 26 characters are specified, trailing zeroes are added to the value. For
example, the value “1234” is equivalent to “1234” followed by 22 zeroes.
Web – Click SNMP, SNMPv3, Remote Engine ID. Enter an ID of up to 26
hexadecimal characters and then click Save.
Figure 3-28 Setting an Engine ID
CLI – This example specifies a remote SNMPv3 engine ID.
Console(config)#snmp-server engineID remote 54321 192.168.1.194-123
Console(config)#exit
Console#show snmp engine-id4-124
Local SNMP engineID: 8000002a8000000000e8666672
Local SNMP engineBoots: 1
Remote SNMP engineID IP address
80000000030004e2b316c54321 192.168.1.19
Console#
3
Configuring SNMPv3 Users
Each SNMPv3 user is defined by a unique name. Users must be configured with a
specific security level and assigned to a group. The SNMPv3 group restricts users to
a specific read, write, or notify view.
Command Attributes
• User Name – The name of user connecting to the SNMP agent. (Range: 1-32
characters)
• Group Name – The name of the SNMP group to which the user is assigned.
(Range: 1-32 characters)
• Security Model – The user security model; SNMP v1, v2c or v3.
• Security Level – The security level used for the user:
- noAuthNoPriv – There is no authentication or encryption used in SNMP
communications. (This is the default for SNMPv3.)
- AuthNoPriv – SNMP communications use authentication, but the data is not
encrypted (only available for the SNMPv3 security model).
- AuthPriv – SNMP communications use both authentication and encryption (only
3-45
Configuring the Switch
3
available for the SNMPv3 security model).
• AuthenticationProtocol – The method used for user authentication. (Options:
MD5, SHA; Default: MD5)
• AuthenticationPassword – A minimum of eight plain text characters is required.
• PrivacyProtocol – The encryption algorithm use for data privacy; only 56-bit DES
is currently available.
• PrivacyPassword – A minimum of eight plain text characters is required.
• Actions – Enables the user to be assigned to another SNMPv3 group.
Web – Click SNMP, SNMPv3, Users. Click New to configure a user name. In the
New User page, define a name and assign it to a group, then click Add to save the
configuration and return to the User Name list. To delete a user, check the box next
to the user name, then click Delete. To change the assigned group of a user, click
Change Group in the Actions column of the users table and select the new group.
3-46
Figure 3-29 Configuring SNMPv3 Users
Configuring SNMPv3 Management Access
3
CLI – Use the snmp-server user command to configure a new user name and
assign it to a group.
Console(config)#snmp-server user chris group r&d v3 auth md5
greenpeace priv des56 einstien4-128
Console(config)#exit
Console#show snmp user4-130
EngineId: 80000034030001f488f5200000
User Name: chris
Authentication Protocol: md5
Privacy Protocol: des56
Storage Type: nonvolatile
Row Status: active
Console#
Configuring Remote SNMPv3 Users
Each SNMPv3 user is defined by a unique name. Users must be configured with a
specific security level and assigned to a group. The SNMPv3 group restricts users to
a specific read and a write view.
To send inform messages to an SNMPv3 user on a remote device, you must first
specify the engine identifier for the SNMP agent on the remote device where the
user resides. The remote engine ID is used to compute the security digest for
authenticating and encrypting packets sent to a user on the remote host. (See
“Specifying Trap Managers and Trap Types” on page 3-41 and “Specifying a
Remote Engine ID” on page 3-44.)
Command Attributes
• User Name – The name of user connecting to the SNMP agent. (Range: 1-32
characters)
• Group Name – The name of the SNMP group to which the user is assigned.
(Range: 1-32 characters)
• Engine ID – The engine identifier for the SNMP agent on the remote device where
the remote user resides. Note that the remote engine identifier must be specified
before you configure a remote user. (See “Specifying a Remote Engine ID” on
page 3-44.)
• Remote IP – The Internet address of the remote device where the user resides.
• Security Model – The user security model; SNMP v1, v2c or v3. (Default: v1)
• Security Level – The security level used for the user:
- noAuthNoPriv – There is no authentication or encryption used in SNMP
communications. (This is the default for SNMPv3.)
- AuthNoPriv – SNMP communications use authentication, but the data is not
encrypted (only available for the SNMPv3 security model).
- AuthPriv – SNMP communications use both authentication and encryption (only
available for the SNMPv3 security model).
• AuthenticationProtocol – The method used for user authentication. (Options:
MD5, SHA; Default: MD5)
• AuthenticationPassword – A minimum of eight plain text characters is required.
3-47
Configuring the Switch
3
• PrivacyProtocol – The encryption algorithm use for data privacy; only 56-bit DES
is currently available.
• PrivacyPassword – A minimum of eight plain text characters is required.
Web – Click SNMP, SNMPv3, Remote Users. Click New to configure a user name.
In the New User page, define a name and assign it to a group, then click Add to save
the configuration and return to the User Name list. To delete a user, check the box
next to the user name, then click Delete.
3-48
Figure 3-30 Configuring Remote SNMPv3 Users
Configuring SNMPv3 Management Access
3
CLI – Use the snmp-server user command to configure a new user name and
assign it to a group.
Console(config)#snmp-server user mark group r&d remote 192.168.1.19 v3
auth md5 greenpeace priv des56 einstien4-128
Console(config)#exit
Console#show snmp user4-130
No user exist.
SNMP remote user
EngineId: 80000000030004e2b316c54321
User Name: mark
Authentication Protocol: none
Privacy Protocol: none
Storage Type: nonvolatile
Row Status: active
Console#
Configuring SNMPv3 Groups
An SNMPv3 group sets the access policy for its assigned users, restricting them to
specific read, write, and notify views. You can use the pre-defined default groups or
create new groups to map a set of SNMP users to SNMP views.
Command Attributes
• Group Name – The name of the SNMP group. (Range: 1-32 characters)
• Model – The group security model; SNMP v1, v2c or v3.
• Level – The security level used for the group:
- noAuthNoPriv – There is no authentication or encryption used in SNMP
communications.
- AuthNoPriv – SNMP communications use authentication, but the data is not
encrypted (only available for the SNMPv3 security model).
- AuthPriv – SNMP communications use both authentication and encryption (only
available for the SNMPv3 security model).
• Read View – The configured view for read access. (Range: 1-64 characters)
• Write View – The configured view for write access. (Range: 1-64 characters)
• Notify View – The configured view for notifications. (Range: 1-64 characters)
3-49
Configuring the Switch
3
Table 3-5 Supported Notification Messages
Object LabelObject IDDescription
RFC 1493 Traps
newRoot1.3.6.1.2.1.17.0.1The newRoot trap indicates that the sending
topologyChange1.3.6.1.2.1.17.0.2A topologyChange trap is sent by a bridge when
SNMPv2 Traps
coldStart1.3.6.1.6.3.1.1.5.1A coldStart trap signifies that the S NMPv2 entity,
warmStart1.3.6.1.6.3.1.1.5.2A warmStart trap signifies that the SNMPv2
a
linkDown
a
linkUp
authenticationFailure
RMON Events (V2)
risingAlarm1.3.6.1.2.1.16.0.1The SNMP trap that is generated when an alarm
fallingAlarm1.3.6.1.2.1.16.0.2The SNMP trap that is generated when an alarm
1.3.6.1.6.3.1.1.5.3A linkDown trap signifies that the SNMP entity,
1.3.6.1.6.3.1.1.5.4A linkUp trap signifies that the SNMP entity,
a
1.3.6.1.6.3.1.1.5.5An authenticationFailure trap signifies that the
agent has become the new root of the Spanning
Tree; the trap is sent by a bridge soon after its
election as the new root, e.g., upon expiration of
the Topology Change Timer immediately
subsequent to its election.
any of its configured ports transitions from the
Learning state to the Forwarding state, or from
the Forwarding state to the Disca rding state. The
trap is not sent if a newRoot trap is sent for the
same transition.
acting in an agent role, is reinitializing itself and
that its configuration may have been altered.
entity, acting in an agent role, is reinitializing
itself such that its configuration is unaltered.
acting in an agent role, has detected that the
ifOperStatus object for one of its communication
links is about to enter the down state from some
other state (but not from the notPresent state).
This other state is indicated by the included
value of ifOperStatus.
acting in an agent role, has detected that the
ifOperStatus object for one of its communication
links left the down state and transitioned into
some other state (but not into the notPresent
state). This other state is indicated by the
included value of ifOperStatus.
SNMPv2 entity, acting in an agent role, has
received a protocol message that is not properly
authenticated. While all implementations of the
SNMPv2 must be capable of generating this
trap, the snmpEnableAuthenTraps object
indicates whether this trap will be generated.
entry crosses its rising threshold and generates
an event that is configured for sending SNMP
traps.
entry crosses its falling threshold and generates
an event that is configured for sending SNMP
traps.
swFanFailureTrap1.3.6.1.4.1.259.6.10.95.2.1.0.17 This trap is sent when the fan fails.
swFanRecoverTrap1.3.6.1.4.1.259.6.10.95.2.1.0.18 This trap is sent when the fan failure has
swPortSecurityTrap1.3.6.1.4.1.259.6.10.95.2.1.0.36 This trap is sent when a port is intruded.
swIpFilterRejectTrap1.3.6.1.4.1.259.6.10.95.2.1.0.40 This trap is sent when an incorrect IP address is
swSmtpConnFailure
Trap
swMainBoardVer
MismatchNotificaiton
swModuleVer
MismatchNotificaiton
swThermalRising
Notification
swThermalFalling
Notification
swModuleInsertion
Notificaiton
swModuleRemoval
Notificaiton
a. These are legacy notifications and therefore must be enabled in conjunction with the corresponding traps on the
SNMP Configuration menu (page 3-43).
1.3.6.1.4.1.259.6.10.95.2.1.0.1 This trap is sent when the power state changes.
recovered.
rejected by the IP Filter.
1.3.6.1.4.1.259.6.10.95.2.1.0.41 This trap is triggered if the SMTP system cannot
1.3.6.1.4.1.259.6.10.95.2.1.0.56 This trap is sent when the slave board version is
1.3.6.1.4.1.259.6.10.95.2.1.0.57 This trap is sent when the slide-in module
1.3.6.1.4.1.259.6.10.95.2.1.0.58 This trap is sent when the temperature exceeds
1.3.6.1.4.1.259.6.1 0.95.2.1.0.59 This trap is sent whe n the temperature falls below
1.3.6.1.4.1.259.6.10.95.2.1.0.60 This trap is sent when a module is inserted.
1.3.6.1.4.1.259.6.10.95.2.1.0.61 This trap is sent when a module is removed.
open a connection to the mail server
successfully.
mismatched with the master board version. This
trap binds two objects, the first object indicates
the master version, whereas the second
represents the slave version.
version is mismatched with the main board
version.
the switchThermalActionRisingThreshold.
the switchThermalActionFallingThreshold.
3-51
Configuring the Switch
3
Web – Click SNMP, SNMPv3, Groups. Click New to configure a new group. In the
New Group page, define a name, assign a security model and level, and then select
read, write, and notify views. Click Add to save the new group and return to the
Groups list. To delete a group, check the box next to the group name, then click
Delete.
Figure 3-31 Configuring SNMPv3 Groups
CLI – Use the snmp-server group command to configure a new group, specifying
the security model and level, and restricting MIB access to defined read and write
views.
Console(config)#snmp-server group secure-users v3 priv read defaultview
SNMPv3 views are used to restrict user access to specified portions of the MIB tree.
The predefined view “defaultview” includes access to the entire MIB tree.
Command Attributes
• View Name – The name of the SNMP view. (Range: 1-64 characters)
• View OID Subtrees – Shows the currently configured object identifiers of branches
within the MIB tree that define the SNMP view.
• Edit OID Subtrees – Allows you to configure the object identifiers of branches
within the MIB tree. Wild cards can be used to mask a specific portion of the OID
string.
• Type – Indicates if the object identifier of a branch within the MIB tree is included
or excluded from the SNMP view.
Web – Click SNMP, SNMPv3, Views. Click New to configure a new view. In the New
View page, define a name and specify OID subtrees in the switch MIB to be included
or excluded in the view. Click Back to save the new view and return to the SNMPv3
Views list. For a specific view, click on View OID Subtrees to display the current
configuration, or click on Edit OID Subtrees to make changes to the view settings. To
delete a view, check the box next to the view name, then click Delete.
Figure 3-32 Configuring SNMPv3 Views
3-53
Configuring the Switch
3
CLI – Use the snmp-server view command to configure a new view. This example
view includes the MIB-2 interfaces table, and the wildcard mask selects all index
entries.
included4-125
Console(config)#exit
Console#show snmp view4-126
View Name: ifEntry.a
Subtree OID: 1.3.6.1.2.1.2.2.1.1.*
View Type: included
Storage Type: nonvolatile
Row Status: active
View Name: readaccess
Subtree OID: 1.3.6.1.2
View Type: included
Storage Type: nonvolatile
Row Status: active
View Name: defaultview
Subtree OID: 1
View Type: included
Storage Type: nonvolatile
Row Status: active
Console#
User Authentication
You can restrict management access to this switch using the following options:
• User Accounts – Manually configure access rights on the switch for specified users.
• Authentication Settings – Use remote authentication to configure access rights.
• HTTPS Settings – Provide a secure web connection.
• SSH Settings – Provide a secure shell (for secure Telnet access).
• Port Security – Configure secure addresses for individual ports.
• 802.1X – Use IEEE 802.1X port authentication to control access to specific ports.
• IP Filter – Filters management access to the web, SNMP or Telnet interface.
Configuring User Accounts
The guest only has read access for most configuration parameters. However, the
administrator has write access for all parameters governing the onboard agent. You
should therefore assign a new administrator password as soon as possible, and
store it in a safe place.
The default guest name is “guest” with the password “guest.” The default
administrator name is “admin” with the password “admin.”
Command Attributes
• Account List – Displays the current list of user accounts and associated access
levels. (Defaults: admin, and guest)
3-54
User Authentication
• New Account – Displays configuration settings for a new account.
- User Name – The name of the user.
(Maximum length: 8 characters)
- Access Level – Specifies the user level.
(Options: Normal and Privileged)
- Password – Specifies the user password.
(Range: 0-8 characters plain text, case sensitive)
• Change Password – Sets a new password for the specified user name.
• Add/Remove – Adds or removes an account from the list.
Web – Click Security, User Accounts. To configure a new user account, specify a
user name, select the user’s access level, then enter a password and confirm it.
Click Add to save the new user account and add it to the Account List. To change the
password for a specific user, enter the user name and new password, confirm the
password by entering it again, then click Apply.
3
Figure 3-33 Access Levels
CLI – Assign a user name to access-level 15 (i.e., administrator), then specify the
password.
Console(config)#username bob access-level 154-27
Console(config)#username bob password 0 smith
Console(config)#
3-55
Configuring the Switch
3
Configuring Local/Remote Logon Authentication
Use the Authentication Settings menu to restrict management access based on
specified user names and passwords. You can manually configure access rights on
the switch, or you can use a remote access authentication server based on RADIUS
or TACACS+ protocols.
Remote Authentication Dial-in
User Service (RADIUS) and
Terminal Access Controller
Access Control System Plus
(TACACS+) are logon
Web
Telnet
authentication protocols that
use software running on a
central server to control
access to RADIUS-aware or
TACACS-aware devices on the
network. An authentication
RADIUS/
TACACS+
server
1. Client attempts management access.
2. Switch contacts authentication server.
3. Authentication server challenges client.
4. Client responds with proper password or key.
5. Authentication server approves access.
6. Switch grants management access.
server contains a database of
multiple user name/password pairs with associated privilege levels for each user
that requires management access to the switch.
RADIUS uses UDP while TACACS+ uses TCP. UDP only offers best effort delivery,
while TCP offers a connection-oriented transport. Also, note that RADIUS encrypts
only the password in the access-request packet from the client to the server, while
TACACS+ encrypts the entire body of the packet.
Command Usage
• By default, management access is always checked against the authentication
database stored on the local switch. If a remote authentication server is used, you
must specify the authentication sequence and the corresponding parameters for
the remote authentication protocol. Local and remote logon authentication control
management access via the console port, web browser, or Telnet.
• RADIUS and TACACS+ logon authentication assign a specific privilege level for
each user name/password pair. The user name, password, and privilege level
must be configured on the authentication server.
• You can specify up to three authentication methods for any user to indicate the
authentication sequence. For example, if you select (1) RADIUS, (2) TACACS and
(3) Local, the user name and password on the RADIUS server is verified first. If the
RADIUS server is not available, then authentication is attempted using the
TACACS+ server, and finally the local user name and password is checked.
console
3-56
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.