Smc 8728L2 Management Guide

Download

TigerSwitch 1000

L2 Gigabit Standalone Switch

◆ 24 auto-MDI/MDI-X 10/100/1000BASE-T ports

◆ 4 SFP transceiver slots

◆ 2 XFP media expansion module slots

◆ Non-blocking switching architecture

◆ Support for a redundant power unit

◆ Spanning Tree Protocol, Rapid STP, and MSTP

◆ Up to 6 LACP or static trunks

◆ CoS support for eight-level priority

◆ Full support for VLANs with GVRP

◆ IGMP multicast filtering and snooping

◆ Support for jumbo frames up to 9 KB

◆ Manageable via console, Telnet, Web, and SNMP/RMON

Management Guide

SMC8728L2

TigerSwitch 1000 Management Guide

From SMC’s Tiger line of feature-rich workgroup LAN solutions

38 Tesla Irvine, CA 92618 Phone: (949) 679-8000

October 2006

Pub. # 149100028400A

Information furnished by SMC Networks, Inc. (SMC) is believed to be accurate and reliable. However, no responsibility is assumed by SMC for its use, nor for any infringements of patents or other rights of third parties which may result from its use. No license is granted by implication or otherwise under any patent or patent rights of SMC. SMC reserves the right to change specifications at any time without notice.

SMC Networks, Inc.

38 Tesla

Irvine, CA 92618

Trademarks:

SMC is a registered trademark; and EZ Switch, TigerStack and TigerSwitch are trademarks of SMC Networks, Inc. Other product and company names are trademarks or registered trademarks of their respective holders.

IMITED

Limited Warranty Statement: SMC Networks, Inc. (“SMC”) warrants its products to be free from defects in workmanship and materials, under normal use and service, for the applicable warranty term. All SMC products carry a standard 90-day limited warranty from the date of purchase from SMC or its Authorized Reseller. SMC may, at its own discretion, repair or replace any product not operating as warranted with a similar or functionally equivalent product, during the applicable warranty term. SMC will endeavor to repair or replace any product returned under warranty within 30 days of receipt of the product.

The standard limited warranty can be upgraded to a Limited Lifetime* warranty by registering new products within 30 days of purchase from SMC or its Authorized Reseller. Registration can be accomplished via the enclosed product registration card or online via the SMC web site. Failure to register will not affect the standard limited warranty. The Limited Lifetime warranty covers a product during the Life of that Product, which is defined as the period of time during which the product is an “Active” SMC product. A product is considered to be “Active” while it is listed on the current SMC price list. As new technologies emerge, older technologies become obsolete and SMC will, at its discretion, replace an older product in its product line with one that incorporates these newer technologies. At that point, the obsolete product is discontinued and is no longer an “Active” SMC product. A list of discontinued products with their respective dates of discontinuance can be found at: http://www.smc.com/index.cfm?action=customer_service_warranty.

All products that are replaced become the property of SMC. Replacement products may be either new or reconditioned. Any replaced or repaired product carries either a 30-day limited warranty or the remainder of the initial warranty, whichever is longer. SMC is not responsible for any custom software or firmware, configuration information, or memory data of Customer contained in, stored on, or integrated with any products returned to SMC pursuant to any warranty. Products returned to SMC should have any customer-installed accessory or add-on components, such as expansion modules, removed prior to returning the product for replacement. SMC is not responsible for these items if they are returned with the product.

Customers must contact SMC for a Return Material Authorization number prior to returning any product to SMC. Proof of purchase may be required. Any product returned to SMC without a valid Return Material Authorization (RMA) number clearly marked on the outside of the package will be returned to customer at customer’s expense. For warranty claims within North America, please call our toll-free customer support number at (800) 762-4968. Customers are responsible for all shipping charges from their facility to SMC. SMC is responsible for return shipping charges from SMC to customer.

ARRANTY

IMITED WARRANTY

WARRANTIES EXCLUSIVE: IF AN SMC PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER’S SOLE REMEDY SHALL BE REPAIR OR REPLACEMENT OF THE PRODUCT IN QUESTION, AT SMC’S OPTION. THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES OR CONDITIONS, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING WARRANTIES OR CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. SMC NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF ITS PRODUCTS. SMC SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THE ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER’S OR ANY THIRD PERSON’S MISUSE, NEGLECT, IMPROPER INSTALLATION OR TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING, OR OTHER HAZARD.

LIMITATION OF LIABILITY: IN NO EVENT, WHETHER BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE), SHALL SMC BE LIABLE FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE, LOSS OF BUSINESS, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF ITS PRODUCTS, EVEN IF SMC OR ITS AUTHORIZED RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

SOME STATES DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES OR THE LIMITATION OF INCIDENTAL OR CONSEQUENTIAL DAMAGES FOR CONSUMER PRODUCTS, SO THE ABOVE LIMITATIONS AND EXCLUSIONS MAY NOT APPLY TO YOU. THIS WARRANTY GIVES YOU SPECIFIC LEGAL RIGHTS, WHICH MAY VARY FROM STATE TO STATE. NOTHING IN THIS WARRANTY SHALL BE TAKEN TO AFFECT YOUR STATUTORY RIGHTS.

* SMC will provide warranty service for one year following discontinuance from the active SMC price list. Under the limited lifetime warranty, internal and external power supplies, fans, and cables are covered by a standard one-year warranty from date of purchase.

SMC Networks, Inc.

38 Tesla

Irvine, CA 92618

ONTENTS

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Description of Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

2 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Connecting to the Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Required Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Console Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Setting Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Setting an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Enabling SNMP Management Access . . . . . . . . . . . . . . . . . . . . . 2-9

Saving Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Managing System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

3 Configuring the Switch . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Using the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Navigating the Web Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Panel Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Displaying System Information . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Displaying Switch Hardware/Software Versions . . . . . . . . . . . 3-14

Displaying Bridge Extension Capabilities . . . . . . . . . . . . . . . . . 3-16

Setting the Switch’s IP Address . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Enabling Jumbo Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Managing Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Saving or Restoring Configuration Settings . . . . . . . . . . . . . . . . 3-25

Console Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

Telnet Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

iii

ONTENTS

Configuring Event Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

Resetting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

Setting the System Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

Simple Network Management Protocol . . . . . . . . . . . . . . . . . . . . . . . . 3-42

Enabling the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45

Setting Community Access Strings . . . . . . . . . . . . . . . . . . . . . . 3-45

Specifying Trap Managers and Trap Types . . . . . . . . . . . . . . . 3-47

Configuring SNMPv3 Management Access . . . . . . . . . . . . . . . 3-50

User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

Configuring User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-66

Configuring Local/Remote Logon Authentication . . . . . . . . . 3-67

Configuring HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

Configuring the Secure Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

Configuring Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81

Configuring 802.1x Port Authentication . . . . . . . . . . . . . . . . . . 3-83

Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

Configuring Access Control Lists . . . . . . . . . . . . . . . . . . . . . . . 3-92

Binding a Port to an Access Control List . . . . . . . . . . . . . . . . . 3-97

Filtering Management Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98

Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

Displaying Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

Configuring Interface Connections . . . . . . . . . . . . . . . . . . . . . 3-104

Creating Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106

Setting Broadcast Storm Thresholds . . . . . . . . . . . . . . . . . . . . 3-121

Configuring Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123

Configuring Rate Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124

Showing Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126

Address Table Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132

Setting Static Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132

Displaying the Address Table . . . . . . . . . . . . . . . . . . . . . . . . . 3-134

Changing the Aging Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135

Spanning Tree Algorithm Configuration . . . . . . . . . . . . . . . . . . . . . . 3-136

Displaying Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138

Configuring Global Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141

Displaying Interface Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 3-146

Configuring Interface Settings . . . . . . . . . . . . . . . . . . . . . . . . . 3-150

Configuring Multiple Spanning Trees . . . . . . . . . . . . . . . . . . . 3-153

ONTENTS

Displaying Interface Settings for MSTP . . . . . . . . . . . . . . . . . 3-157

Configuring Interface Settings for MSTP . . . . . . . . . . . . . . . . 3-159

VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-161

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-161

Enabling or Disabling GVRP (Global Setting) . . . . . . . . . . . 3-165

Displaying Basic VLAN Information . . . . . . . . . . . . . . . . . . . 3-165

Displaying Current VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-166

Creating VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-168

Adding Static Members to VLANs (VLAN Index) . . . . . . . . 3-170

Adding Static Members to VLANs (Port Index) . . . . . . . . . . 3-172

Configuring VLAN Behavior for Interfaces . . . . . . . . . . . . . . 3-173

Configuring Private VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-177

Configuring Protocol VLANs . . . . . . . . . . . . . . . . . . . . . . . . . 3-185

Class of Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-187

Setting the Default Priority for Interfaces . . . . . . . . . . . . . . . . 3-187

Mapping CoS Values to Egress Queues . . . . . . . . . . . . . . . . . 3-188

Selecting the Queue Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-191

Setting the Service Weight for Traffic Classes . . . . . . . . . . . . 3-192

Mapping Layer 3/4 Priorities to CoS Values . . . . . . . . . . . . . . 3-193

Selecting IP DSCP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-193

Mapping DSCP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-194

Mapping CoS Values to ACLs . . . . . . . . . . . . . . . . . . . . . . . . . 3-196

Multicast Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-198

Layer 2 IGMP (Snooping and Query) . . . . . . . . . . . . . . . . . . . 3-199

Configuring Domain Name Service . . . . . . . . . . . . . . . . . . . . . 3-207

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-2

Entering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Keywords and Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

Minimum Abbreviation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Command Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Getting Help on Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Partial Keyword Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

ONTENTS

Negating the Effect of Commands . . . . . . . . . . . . . . . . . . . . . . . 4-6

Using Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6

Understanding Command Modes . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Exec Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Command Line Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Command Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

timeout login response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

exec-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

password-thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

silent-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

databits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20

parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21

speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22

stopbits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

disconnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

show line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24

General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

show history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30

System Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31

Device Designation Commands . . . . . . . . . . . . . . . . . . . . . . . . 4-32

User Access Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

IP Filter Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36

Web Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38

Telnet Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Secure Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44

ONTENTS

Event Logging Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

SMTP Alert Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64

Time Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69

System Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75

Frame Size Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81

Flash/File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83

copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83

delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86

dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87

whichboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-88

boot system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89

Authentication Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90

Authentication Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90

RADIUS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-93

TACACS+ Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98

Port Security Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100

802.1X Port Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103

Access Control List Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-112

IP ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-113

ACL Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122

SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123

Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143

interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144

description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-144

speed-duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-145

negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-146

capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-147

flowcontrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-148

shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-149

clear counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-150

show interfaces status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-151

show interfaces counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-152

show interfaces switchport . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-154

Broadcast Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-156

broadcast packet-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-156

switchport broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-157

Mirror Port Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158

vii

ONTENTS

port monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158

show port monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-159

Rate Limit Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-160

rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-160

Link Aggregation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-162

channel-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164

lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164

lacp system-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-167

lacp admin-key (Ethernet Interface) . . . . . . . . . . . . . . . . . . . . 4-168

lacp admin-key (Port Channel) . . . . . . . . . . . . . . . . . . . . . . . . . 4-169

lacp port-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-170

show lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-171

Address Table Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-175

mac-address-table static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-176

clear mac-address-table dynamic . . . . . . . . . . . . . . . . . . . . . . . 4-177

show mac-address-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-178

mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . 4-179

show mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . 4-180

Spanning Tree Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-180

spanning-tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-182

spanning-tree mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-183

spanning-tree forward-time . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-184

spanning-tree hello-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-185

spanning-tree max-age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-186

spanning-tree priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187

spanning-tree pathcost method . . . . . . . . . . . . . . . . . . . . . . . . 4-187

spanning-tree transmission-limit . . . . . . . . . . . . . . . . . . . . . . . 4-188

spanning-tree mst-configuration . . . . . . . . . . . . . . . . . . . . . . . 4-189

mst vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-189

mst priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-190

name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-191

revision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-192

max-hops . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-193

spanning-tree spanning-disabled . . . . . . . . . . . . . . . . . . . . . . . 4-193

spanning-tree cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194

spanning-tree port-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-195

spanning-tree edge-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-196

viii

ONTENTS

spanning-tree portfast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-197

spanning-tree link-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-198

spanning-tree mst cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-198

spanning-tree mst port-priority . . . . . . . . . . . . . . . . . . . . . . . . 4-200

spanning-tree protocol-migration . . . . . . . . . . . . . . . . . . . . . . 4-201

show spanning-tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-202

show spanning-tree mst configuration . . . . . . . . . . . . . . . . . . . 4-204

VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204

Editing VLAN Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-205

Configuring VLAN Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . 4-207

Displaying VLAN Information . . . . . . . . . . . . . . . . . . . . . . . . 4-215

Configuring Private VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-216

GVRP and Bridge Extension Commands . . . . . . . . . . . . . . . . . . . . . 4-224

bridge-ext gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-225

show bridge-ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-225

switchport gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-226

show gvrp configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-227

garp timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-227

show garp timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-229

Priority Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-229

Priority Commands (Layer 2) . . . . . . . . . . . . . . . . . . . . . . . . . . 4-230

Priority Commands (Layer 3 and 4) . . . . . . . . . . . . . . . . . . . . . 4-237

Multicast Filtering Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-240

IGMP Snooping Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-241

IGMP Query Commands (Layer 2) . . . . . . . . . . . . . . . . . . . . . 4-245

Static Multicast Routing Commands . . . . . . . . . . . . . . . . . . . . 4-249

IP Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-251

Basic IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-251

DNS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-257

A Software Specifications . . . . . . . . . . . . . . . . . . . . . . . . A-1

Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Management Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2

Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

Management Information Bases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-3

ONTENTS

B Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Problems Accessing the Management Interface . . . . . . . . . . . . . . . . . . B-1

Using System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3

Glossary

Index

ONTENTS

ABLES

Table 1-1. Key Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Table 1-2. System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Table 3-1. Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Table 3-2. Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Table 3-3. Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

Table 3-4 SNMPv3 Security Models and Levels . . . . . . . . . . . . . . . . 3-44

Table 3-5 Supported Notification Messages . . . . . . . . . . . . . . . . . . . 3-59

Table 3-6. HTTPS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

Table 3-7. 802.1x Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90

Table 3-8. LACP Port Counter Information . . . . . . . . . . . . . . . . . . . 3-114

Table 3-9. LACP Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116

Table 3-10. LACP Remote Side Settings . . . . . . . . . . . . . . . . . . . . . . . 3-119

Table 3-11. Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-126

Table 3-12. Egress Queue Priority Mapping . . . . . . . . . . . . . . . . . . . . 3-189

Table 3-13. CoS Priority Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-189

Table 3-14. Mapping DSCP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . 3-195

Table 3-15. CoS to ACL Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-196

Table 4-1 Command Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Table 4-2 Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Table 4-3 Keystroke Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Table 4-4 Command Group Index . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Table 4-5 Line Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Table 4-6 General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Table 4-7 System Management Commands . . . . . . . . . . . . . . . . . . . . 4-31

Table 4-8 Device Designation Commands . . . . . . . . . . . . . . . . . . . . . 4-32

Table 4-9 User Access Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

Table 4-10 Default Login Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

Table 4-11 IP Filter Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36

Table 4-12 Web Server Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-38

Table 4-13 HTTPS System Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41

Table 4-14 Telnet Server Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Table 4-15 Secure Shell Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45

Table 4-16 show ssh - display description . . . . . . . . . . . . . . . . . . . . . . 4-54

xii

ABLES

Table 4-17 Event Logging Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4-56

Table 4-18 Logging Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57

Table 4-19 show logging flash/ram - display description . . . . . . . . . . 4-62

Table 4-20 show logging trap - display description . . . . . . . . . . . . . . . 4-63

Table 4-21 SMTP Alert Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64

Table 4-22 Time Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69

Table 4-23 System Status Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75

Table 4-24 Frame Size Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81

Table 4-25 Flash/File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-83

Table 4-26 File Directory Information . . . . . . . . . . . . . . . . . . . . . . . . . 4-88

Table 4-27 Authentication Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4-90

Table 4-28 Authentication Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90

Table 4-29 RADIUS Client Commands . . . . . . . . . . . . . . . . . . . . . . . . 4-93

Table 4-30 TACACS+ Client Commands . . . . . . . . . . . . . . . . . . . . . . 4-98

Table 4-31 Port Security Commands . . . . . . . . . . . . . . . . . . . . . . . . . 4-101

Table 4-32 802.1X Port Authentication Commands . . . . . . . . . . . . . 4-103

Table 4-33 Access Control List Commands . . . . . . . . . . . . . . . . . . . . 4-113

Table 4-34 IP ACL Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-113

Table 4-35 Egress Queue Priority Mapping . . . . . . . . . . . . . . . . . . . . 4-120

Table 4-36 ACL Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-122

Table 4-37 SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-123

Table 4-38 show snmp engine-id - display description . . . . . . . . . . . 4-135

Table 4-39 show snmp view - display description . . . . . . . . . . . . . . . 4-137

Table 4-40 show snmp group - display description . . . . . . . . . . . . . . 4-139

Table 4-41 show snmp user - display description . . . . . . . . . . . . . . . 4-142

Table 4-42 Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-143

Table 4-43 show interfaces switchport - display description . . . . . . . 4-155

Table 4-44 Broadcast Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-156

Table 4-45 Mirror Port Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-158

Table 4-46 Rate Limit Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-160

Table 4-47 Link Aggregation Commands . . . . . . . . . . . . . . . . . . . . . . 4-162

Table 4-48 show lacp counters - display description . . . . . . . . . . . . . 4-172

Table 4-49 show lacp internal - display description . . . . . . . . . . . . . . 4-172

Table 4-50 show lacp neighbors - display description . . . . . . . . . . . . 4-174

Table 4-52 Address Table Commands . . . . . . . . . . . . . . . . . . . . . . . . 4-175

Table 4-51 show lacp sysid - display description . . . . . . . . . . . . . . . . 4-175

Table 4-53 Spanning Tree Commands . . . . . . . . . . . . . . . . . . . . . . . . 4-180

xiii

ABLES

Table 4-54 VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204

Table 4-55 Editing VLAN Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-205

Table 4-56 Configuring VLAN Interfaces . . . . . . . . . . . . . . . . . . . . . 4-207

Table 4-57 Displaying VLAN Information . . . . . . . . . . . . . . . . . . . . 4-215

Table 4-58 Private VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . 4-217

Table 4-59 GVRP and Bridge Extension Commands . . . . . . . . . . . . 4-224

Table 4-61 Priority Commands (Layer 2) . . . . . . . . . . . . . . . . . . . . . . 4-230

Table 4-60 Priority Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-230

Table 4-62 Default CoS Priority Levels . . . . . . . . . . . . . . . . . . . . . . . 4-234

Table 4-63 Priority Commands (Layer 3 and 4) . . . . . . . . . . . . . . . . . 4-237

Table 4-64 Mapping IP DSCP to CoS Values . . . . . . . . . . . . . . . . . . 4-238

Table 4-65 Multicast Filtering Commands . . . . . . . . . . . . . . . . . . . . . 4-240

Table 4-66 IGMP Snooping Commands . . . . . . . . . . . . . . . . . . . . . . 4-241

Table 4-67 IGMP Query Commands (Layer 2) . . . . . . . . . . . . . . . . . 4-245

Table 4-68 Static Multicast Routing Commands . . . . . . . . . . . . . . . . 4-249

Table 4-69 IP Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . 4-251

Table 4-70 DNS Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-257

Table 4-71 Show DNS Output Description . . . . . . . . . . . . . . . . . . . . 4-265

Table B-1 Troubleshooting Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

xiv

ABLES

IGURES

Figure 3-1. Homepage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Figure 3-2. Panel Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Figure 3-3. System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

Figure 3-4. Switch Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Figure 3-5. Bridge Extension Configuration . . . . . . . . . . . . . . . . . . . 3-17

Figure 3-6. Manual IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Figure 3-7. DHCP IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 3-20

Figure 3-8. Enabling Jumbo Frames . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Figure 3-9. Copy Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

Figure 3-10. Setting the Startup Code . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Figure 3-11. Deleting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Figure 3-12. Downloading Configuration Settings for Startup . . . . . 3-26

Figure 3-13. Setting the Startup Configuration Settings . . . . . . . . . . . 3-27

Figure 3-14. Console Port Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Figure 3-15. Enabling Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

Figure 3-16. Displaying Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

Figure 3-17. System Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

Figure 3-18. Remote Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Figure 3-19. Enabling and Configuring SMTP . . . . . . . . . . . . . . . . . . 3-38

Figure 3-20. Resetting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

Figure 3-21. SNTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

Figure 3-22. Setting the Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

Figure 3-23 Enabling the SNMP Agent . . . . . . . . . . . . . . . . . . . . . . . 3-45

Figure 3-24 Configuring SNMP Community Strings . . . . . . . . . . . . 3-46

Figure 3-25 Configuring SNMP Trap Managers . . . . . . . . . . . . . . . . 3-49

Figure 3-26 Setting an Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

Figure 3-27 Setting an Engine ID . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

Figure 3-28 Configuring SNMPv3 Users . . . . . . . . . . . . . . . . . . . . . . 3-54

Figure 3-29 Configuring Remote SNMPv3 Users . . . . . . . . . . . . . . . 3-57

Figure 3-30 Configuring SNMPv3 Groups . . . . . . . . . . . . . . . . . . . . 3-62

Figure 3-31 Configuring SNMPv3 Views . . . . . . . . . . . . . . . . . . . . . 3-64

Figure 3-32. Access Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

Figure 3-33. Authentication Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

xvi

IGURES

Figure 3-34. HTTPS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73

Figure 3-35. SSH Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78

Figure 3-36. SSH Host-Key Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80

Figure 3-37. Configuring Port Security . . . . . . . . . . . . . . . . . . . . . . . . 3-83

Figure 3-38. 802.1x Global Information . . . . . . . . . . . . . . . . . . . . . . . 3-85

Figure 3-39. 802.1x Global Configuration . . . . . . . . . . . . . . . . . . . . . 3-86

Figure 3-40. 802.1x Port Configuration . . . . . . . . . . . . . . . . . . . . . . . 3-88

Figure 3-41. Displaying 802.1x Port Statistics . . . . . . . . . . . . . . . . . . 3-91

Figure 3-42. Naming and Choosing ACLs . . . . . . . . . . . . . . . . . . . . . 3-94

Figure 3-43. Configuring Standard IP ACLs . . . . . . . . . . . . . . . . . . . 3-95

Figure 3-44. Configuring Extended IP ACLs . . . . . . . . . . . . . . . . . . . 3-96

Figure 3-45. Mapping ACLs to Port Ingress Queues . . . . . . . . . . . . . 3-98

Figure 3-46. Filtering Management Access . . . . . . . . . . . . . . . . . . . . 3-100

Figure 3-47. Port Status Information . . . . . . . . . . . . . . . . . . . . . . . . 3-101

Figure 3-48. Configuring Port Attributes . . . . . . . . . . . . . . . . . . . . . 3-105

Figure 3-49. Static Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . 3-108

Figure 3-50. LACP Port Configuratio . . . . . . . . . . . . . . . . . . . . . . . . 3-110

Figure 3-51. LACP Aggregation Port Configuration . . . . . . . . . . . . 3-113

Figure 3-52. Displaying LACP Port Counters Information . . . . . . . 3-115

Figure 3-53. Displaying LACP Port Information . . . . . . . . . . . . . . . 3-118

Figure 3-54. Displaying Remote LACP Port Information . . . . . . . . 3-120

Figure 3-55. Enabling Port Broadcast Control . . . . . . . . . . . . . . . . . 3-122

Figure 3-56. Configuring a Mirror Port . . . . . . . . . . . . . . . . . . . . . . . 3-124

Figure 3-57. Configuring Input Port Rate Limiting . . . . . . . . . . . . . 3-125

Figure 3-58. Displaying Port Statistics . . . . . . . . . . . . . . . . . . . . . . . 3-130

Figure 3-59. Displaying Etherlike and RMON Statistics . . . . . . . . . 3-131

Figure 3-60. Mapping Ports to Static Addresses . . . . . . . . . . . . . . . . 3-133

Figure 3-61. Displaying the MAC Dynamic Address Table . . . . . . . 3-135

Figure 3-62. Setting the Aging Time . . . . . . . . . . . . . . . . . . . . . . . . . 3-136

Figure 3-63. Displaying the Spanning Tree Algorithm . . . . . . . . . . . 3-140

Figure 3-64. Configuring the Spanning Tree Algorithm . . . . . . . . . 3-145

Figure 3-65. Displaying STA - Port Status Information . . . . . . . . . . 3-149

Figure 3-66. Configuring Spanning Tree Algorithm per Port . . . . . 3-153

Figure 3-67. Configuring Multiple Spanning Trees . . . . . . . . . . . . . 3-155

Figure 3-68. Displaying MSTP Interface Settings . . . . . . . . . . . . . . . 3-157

Figure 3-69. MSTP Port Configuration . . . . . . . . . . . . . . . . . . . . . . . 3-160

Figure 3-70. Enabling GVRP Status . . . . . . . . . . . . . . . . . . . . . . . . . 3-165

xvii

IGURES

Figure 3-71. Displaying Basic VLAN Information . . . . . . . . . . . . . 3-166

Figure 3-72. Displaying VLAN Information by Port Membership . 3-167

Figure 3-73. Creating Virtual LANs . . . . . . . . . . . . . . . . . . . . . . . . . 3-169

Figure 3-74. Configuring VLAN Port Attributes . . . . . . . . . . . . . . . 3-171

Figure 3-75. Assigning VLAN Port and Trunk Groups . . . . . . . . . 3-173

Figure 3-76. Configuring VLAN Ports . . . . . . . . . . . . . . . . . . . . . . . 3-176

Figure 3-77. Private VLAN Information . . . . . . . . . . . . . . . . . . . . . 3-179

Figure 3-78. Private VLAN Configuration . . . . . . . . . . . . . . . . . . . . 3-180

Figure 3-79. Private VLAN Association . . . . . . . . . . . . . . . . . . . . . . 3-181

Figure 3-80. Private VLAN Port Information . . . . . . . . . . . . . . . . . 3-183

Figure 3-81. Private VLAN Port Configuration . . . . . . . . . . . . . . . . 3-184

Figure 3-82. Protocol VLAN Configuration . . . . . . . . . . . . . . . . . . 3-186

Figure 3-83. Protocol VLAN Port Configuration . . . . . . . . . . . . . . 3-186

Figure 3-84. Port Priority Configuration . . . . . . . . . . . . . . . . . . . . . . 3-188

Figure 3-85. Configuring Ports and Trunks for Class of Service . . . 3-190

Figure 3-86. Setting the Queue Mode . . . . . . . . . . . . . . . . . . . . . . . . 3-191

Figure 3-87. Configuring Queue Scheduling . . . . . . . . . . . . . . . . . . 3-192

Figure 3-88. IP DSCP Priority Status . . . . . . . . . . . . . . . . . . . . . . . . 3-194

Figure 3-89. Mapping IP DSCP Priority to Class of Service Values 3-195 Figure 3-90. Configuring Internet Group Management Protocol . . 3-201

Figure 3-91. Mapping Multicast Switch Ports to VLANs . . . . . . . . 3-202

Figure 3-92. Static Multicast Router Port Configuration . . . . . . . . . 3-203

Figure 3-93. Displaying Port Members of Multicast Services . . . . . 3-204

Figure 3-94. Specifying Multicast Port Membership . . . . . . . . . . . . 3-206

Figure 3-95. Configuring DNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-208

Figure 3-96. Mapping IP Addresses to a Host Name . . . . . . . . . . . 3-210

Figure 3-97. Displaying the DNS Cache . . . . . . . . . . . . . . . . . . . . . . 3-211

xviii

HAPTER

NTRODUCTION

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

Feature Description

Configuration Backup and Restore

Authentication Console, Telnet, web – User name / password, RADIUS,

Access Control Lists

DHCP Client Supported

Port Configuration Speed, duplex mode and flow control

Rate Limiting Input rate limiting per port

Port Mirroring One port mirrored to single analysis port

Backup to TFTP server

TACACS+

Web – HTTPS; Telnet – SSH

SNMP v1/v2c/v3– Community strings

Port – IEEE 802.1x, MAC address filtering

Supports up to 32 IP

1-1

NTRODUCTION

Table 1-1. Key Features (Continued)

Feature Description

Port Trunking Supports up to 6 trunks using either static or dynamic

Broadcast Storm Control

Static Address Up to 8K MAC addresses in the forwarding table

IEEE 802.1D Bridge

Store-and-Forward Switching

Spanning Tree Protocol

Virtual LANs Up to 255 using IEEE 802.1Q, port-based, protocol-based, or

Traffic Prioritization

Multicast Filtering Supports IGMP snooping and query

trunking (LACP)

Supported

Supports dynamic data switching and addresses learning

Supported to ensure wire-speed switching while eliminating bad frames

Supports standard STP, Rapid Spanning Tree Protocol (RSTP), and Multiple Spanning Trees (MSTP)

private VLANs

Default port priority, traffic class map, queue scheduling, Differentiated Services Code Point (DSCP), and TCP/UDP Port

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.

1-2

ESCRIPTION OF SOFTWARE FEATURES

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 a user name and password 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, SNMP Version 3, 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 by 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.

1-3

NTRODUCTION

Rate Limiting – This feature controls the maximum rate for traffic received on an interface. Rate limiting is configured on interfaces at the edge of a network to limit traffic into the network. Packets that exceed the acceptable amount of traffic are dropped.

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 6 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.

1-4

ESCRIPTION OF SOFTWARE FEATURES

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 1.5 MB for frame buffering. This buffer can queue packets awaiting transmission on congested networks.

Spanning Tree Protocol – The switch supports these spanning tree protocols:

Spanning Tree Protocol (STP, IEEE 802.1D) – This protocol adds a level of fault tolerance 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 about 10% of that required by 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.

Multiple Spanning Tree Protocol (MSTP, IEEE 802.1s) – This protocol is a direct extension of RSTP. It can provide an independent spanning tree for different VLANs. It simplifies network management, provides for even faster convergence than RSTP by limiting the size of each region, and prevents VLAN members from being segmented from the rest of the group (as sometimes occurs with IEEE 802.1D STP).

1-5

NTRODUCTION

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 eight 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 data and best-effort data.

be used to provide independent priorities for delay-sensitive

This switch also supports several common methods of prioritizing layer 3/ 4 traffic to meet application requirements. Traffic can be prioritized based on the DSCP field in the IP frame. 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.

1-6

YSTEM DEFAULTS

Multicast Filtering – Multicast filtering is a system where network devices forward multicast traffic only to the ports that are registered with the multicast group. Without mulicast filtering the data packet will be broadcast to all endstations within a LAN or VLAN. The purpose is to keep the non-multicast group members from receiving unsolicited packets and to prevent a possible reduction in network performance. The switch uses IGMP Snooping and Query at Layer 2 and IGMP at Layer 3 to manage multicast group registration.

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-25).

The following table lists some of the basic system defaults.

Table 1-2. System Defaults

Function Parameter Default

Console Port Connection

Authentication Privileged Exec Level Username “admin”

Baud Rate 9600

Data bits 8

Stop bits 1

Parity none

Local Console Timeout 0 (disabled)

Password “admin”

Normal Exec Level Username “guest”

Enable Privileged Exec from Normal Exec Level

RADIUS Authentication Disabled

TACACS Authentication Disabled

802.1x Port Authentication Disabled

HTTPS Enabled

SSH Disabled

Port Security Disabled

Password “guest”

Password “super”

1-7

NTRODUCTION

Table 1-2. System Defaults (Continued)

Function Parameter Default

IP Filtering Disabled

Web Management HTTP Server Enabled

HTTP Port Number 80

HTTP Secure Server Enabled

HTTP Secure Port Number 443

SNMP Community Strings “public” (read only)

Traps Authentication traps: enabled

SNMP V3 View: defaultview

Port Configuration

Rate Limiting Input limits Disabled

Port Trunking Static Trunks None

Broadcast Storm Protection

Spanning Tree Protocol

Address Table Aging Time 300 seconds

Virtual LANs Default VLAN 1

Admin Status Enabled

Auto-negotiation Enabled

Flow Control Disabled

LACP (all ports) Disabled

Status Enabled (all ports)

Broadcast Limit Rate 500 packets per second

Status Enabled, RSTP

Fast Forwarding (Edge Port) Disabled

PVID 1

Acceptable Frame Type All

Ingress Filtering Enabled

Switchport Mode (Egress Mode)

GVRP (global) Disabled

GVRP (port interface) Disabled

“private” (read/write)

Link-up-down events:

Group: public (read only); private (read/write)

(Defaults: All values based on IEEE 802.1w)

Hybrid: tagged/untagged frames

enabled

1-8

YSTEM DEFAULTS

Table 1-2. System Defaults (Continued)

Function Parameter Default

Traffic Prioritization

IP Settings IP Address 0.0.0.0

Multicast Filtering IGMP Snooping Snooping: Enabled

System Log Status Enabled

SMTP Email Alerts

SNTP Clock Synchronization Disabled

Ingress Port Priority 0

Weighted Round Robin Queue: 0 1 2 3 4 5 6 7

Weight: 1 2 4 6 8 10 12 14

IP DSCP Priority Disabled

Subnet Mask 255.0.0.0

Default Gateway 0.0.0.0

DHCP Enabled

BOOTP Disabled

Querier: Enabled

Messages Logged Levels 0-6 (all)

Messages Logged to Flash Levels 0-3

Event Handler Enabled (but no server

defined)

1-9

NTRODUCTION

1-10

HAPTER

NITIAL

ONFIGURATION

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 unassigned by default. To change

this address, see “Setting an IP Address” on page 2-6.

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 SMC EliteView.

2-1

NITIAL CONFIGURATION

The switch’s Web interface, CLI configuration program, and SNMP agent allow you to perform the following management functions:

• Set user names and passwords

• 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 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

• Configure up to 6 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.

2-2

ONNECTING TO THE SWITCH

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 to any of these baud rates: 9600, 19200, 38400, 57600, 115200 (Note: Set to 9600 baud to view all system initialization messages.)

• 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.

• With HyperTerminal, select Terminal keys, not Windows keys.

Notes: 1. When using HyperTerminal with Microsoft

make sure that 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-13 for a complete description of console configuration options.

3. Once you have set up the terminal correctly, the console login screen will be displayed.

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-11.

Windows® 2000,

2-3

NITIAL CONFIGURATION

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-6.

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 only allow you to display information and use basic utilities. To fully configure the switch parameters, you must access the CLI at the Privileged Exec level.

2-4

ASIC CONFIGURATION

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.

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.

2-5

NITIAL CONFIGURATION

Username: admin Password:

CLI session with the SMC8728L2 is opened. To end the CLI session, enter [Exit].

Console#configure Console(config)#username guest password 0 [password] Console(config)#username admin password 0 [password] Console(config)#

Setting an IP Address

You must establish IP address information for the switch to obtain management access through the network. This can be done in either of the following ways:

Manual — You have to input the information, including IP address and subnet mask. If your management station is not in the same IP subnet as the switch, you will also need to specify the default gateway router.

Dynamic — The switch 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 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.

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

2-6

ASIC CONFIGURATION

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>.

Console(config)#interface vlan 1 Console(config-if)#ip address 192.168.1.5 255.255.255.0 Console(config-if)#exit Console(config)#ip default-gateway 192.168.1.254 Console(config)#

Dynamic Configuration

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 client” 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:

2-7

NITIAL CONFIGURATION

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 client” to begin broadcasting service requests. Press <Enter>.

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>.

2-8

Console(config)#interface vlan 1 Console(config-if)#ip address dhcp Console(config-if)#end Console#ip dhcp restart client 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.

ASIC CONFIGURATION

Enabling SNMP Management Access

The switch can be configured to accept management commands from Simple Network Management Protocol (SNMP) applications such as SMC EliteView. 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 page 3-63).

Community Strings (for SNMP version 1 and 2c clients)

Community strings are used to control management access to SNMP version 1 and 2c stations, as well as to authorize SNMP stations to receive trap messages from the switch. You therefore need to assign community strings to specified users, and set the access level.

The default strings are:

• public - Specifies read-only access. Authorized management stations are only able to retrieve MIB objects.

• private - Specifies read-write access. Authorized management stations are able to both retrieve and modify MIB objects.

2-9

NITIAL CONFIGURATION

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 rw Console(config)#snmp-server community private Console(config)#

Note: If you do not intend to support access to SNMP version 1 and 2c

clients, we 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,

2-10

ASIC CONFIGURATION

see “snmp-server host” on page 4-129. The following example creates a trap host for each type of SNMP client.

Console(config)#snmp-server host 10.1.19.23 batman Console(config)#snmp-server host 10.1.19.98 robin version 2c Console(config)#snmp-server host 10.1.19.34 barbie version 3 auth Console(config)#

Configuring Access for SNMP Version 3 Clients

To configure management access for SNMPv3 clients, you need to first create a view that defines the portions of MIB that the client can read or write, assign the view to a group, and then assign the user to a group. The following example creates one view called “mib-2” that includes the entire MIB-2 tree branch, and then another view that includes the IEEE 802.1d bridge MIB. It assigns these respective read and read/write views to a group call “r&d” and specifies group authentication via MD5 or SHA. In the last step, it assigns a v3 user to this group, indicating that MD5 will be used for authentication, provides the password “greenpeace” for authentication, and the password “einstien” for encryption.

Console(config)#snmp-server view mib-2 1.3.6.1.2.1 included Console(config)#snmp-server view 802.1d 1.3.6.1.2.1.17 included Console(config)#snmp-server group r&d v3 auth mib-2 802.1d Console(config)#snmp-server user steve group r&d v3 auth md5

greenpeace priv des56 einstien

Console(config)#

For a more detailed explanation on how to configure the switch for access from SNMP v3 clients, refer to “Simple Network Management Protocol” on page 3-42, or refer to the specific CLI commands for SNMP starting on page 4-123.

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.

2-11

NITIAL CONFIGURATION

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#

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-25 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-22 for more information.

• Diagnostic Code — Software that is run during system boot-up, also

known as POST (Power On Self-Test).

2-12

ANAGING SYSTEM FILES

Due to the size limit of the flash memory, the switch supports only two operation code files. However, you can have as many diagnostic code files and configuration files as available flash memory space allows.

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-13

NITIAL CONFIGURATION

2-14

HAPTER

ONFIGURING THE

WITCH

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-6.)

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-5.)

3. After you enter a user name and password, you will have access to the system configuration program.

3-1

ONFIGURING THE SWITCH

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-150.

3-2

AVIGATING THE WEB BROWSER INTERFACE

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. Homepage

3-3

ONFIGURING THE SWITCH

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.

Button Action

Revert Cancels specified values and restores current values

Apply Sets specified values to the system.

Help Links 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.

Table 3-1. Configuration Options

prior to pressing “Apply.”

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-104. The web agent display also includes a “LogOut” button to that will close the web browser if pressed.

Figure 3-2. Panel Display

3-4

AVIGATING THE WEB BROWSER INTERFACE

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

Menu Description Page

System 3-11

System Information Provides basic system description, including

contact information

Switch Information Shows the number of ports, hardware/

firmware version numbers, and power status

Bridge Extension Configuration

IP Configuration Sets the IP address for management access 3-17

Jumbo Frames Enables or disables jumbo frames 3-21

File Management 3-23

Copy Operation Allows the transfer and copying files 3-23

Delete Allows deletion of files from the flash

Set Start-Up Sets the start-up file 3-23

Line 3-27

Console Sets console port connection parameters 3-27

Telnet Sets Telnet connection parameters 3-30

Log 3-32

Logs Stores and displays error messages 3-32

System Logs Sends error messages to a logging process 3-33

Remote Logs Configures the logging of messages to a

Shows the bridge extension parameters 3-16

memory

remote logging process

3-11

3-14

3-25

3-35

3-5

ONFIGURING THE SWITCH

Table 3-2. Main Menu (Continued)

Menu Description Page

SMTP Sends an SMTP client message to a

participating server.

Reset Restarts the switch 3-39

SNTP 3-40

Configuration Configures SNTP client settings, including

broadcast mode or a specified list of servers

Clock Time Zone Sets the local time zone for the system clock 3-41

SNMP 3-42

Configuration Configures community strings and related

trap functions

Agent Status Enables or disables SNMP Agent Status 3-45

SNMPv3 3-50

Engine ID Sets SNMPv3 Engine ID 3-50

Remote Engine ID Adds a Remote Engine ID and IP Host 3-51

Users Creates or deletes user accounts 3-52

Remote Users Creates or deletes remote user accounts 3-55

Groups Creates or deletes SNMPv3 Groups 3-58

Views Creates or deletes SNMPv3 Views 3-63

Security 3-65

User Accounts Assigns a new password for the current user 3-66

Authentication Settings Configures authentication sequence,

RADIUS and TACACS

HTTPS Settings Configures secure HTTP settings 3-72

SSH 3-74

Settings Configures Secure Shell server settings 3-81

Host-Key Settings Generates the host key pair (public and

private)

3-37

3-40

3-45

3-67

3-79

3-6

AVIGATING THE WEB BROWSER INTERFACE

Table 3-2. Main Menu (Continued)

Menu Description Page

Port Security Configures per port security, including

status, response for security breach, and maximum allowed MAC addresses

802.1x 3-83

Information Displays global configuration settings 3-85

Configuration Configures protocol parameters 3-86

Port Configuration Sets the authentication mode for individual

ports

Statistics Displays protocol statistics for the selected

port

ACL 3-92

Configuration Configures packet filtering based on IP or

MAC addresses

Port Binding Binds a port to the specified ACL 3-97

IP Filter Sets IP addresses of clients allowed

management access

Port 3-98

Port Information Displays port connection status 3-100

Trunk Information Displays trunk connection status 3-100

Port Configuration Configures port connection settings 3-104

Trunk Configuration Configures trunk connection settings 3-104

Trunk Membership Specifies ports to group into static trunks 3-107

LACP 3-109

Configuration Allows ports to dynamically join trunks 3-109

Aggregation Port Configures system priority, admin key, and

port priority

Port Counters Information

Port Internal Information

Displays statistics for LACP protocol messages

Displays settings and operational state for local side

3-81

3-87

3-90

3-92

3-98

3-111

3-114

3-116

3-7

ONFIGURING THE SWITCH

Table 3-2. Main Menu (Continued)

Menu Description Page

Port Neighbors Information

Port Broadcast Control Sets the broadcast storm threshold for each

Trunk Broadcast Control

Mirror Port Configuration

Rate Limit 3-124

Input Port Configuration

Port Statistics Lists Ethernet and RMON port statistics 3-126

Address Table 3-132

Static Addresses Displays entries for interface, address or

Dynamic Addresses Displays or edits static entries in the

Address Aging Sets timeout for dynamically learned entries 3-135

Spanning Tree 3-136

STA 3-138

Information Displays STA values used for the bridge 3-138

Configuration Configures global bridge settings for STA,

Port Information Displays individual port settings for STA 3-146

Trunk Information Displays individual trunk settings for STA 3-146

Port Configuration Configures individual port settings for STA 3-150

Trunk Configuration Configures individual trunk settings for

Displays settings and operational state for remote side

port

Sets the broadcast storm threshold for each trunk

Sets the source and target ports for mirroring

Sets the input rate limit for each port 3-124

VLAN

Address Table

RSTP, and MSTP

STA

3-119

3-121

3-123

3-132

3-134

3-141

3-150

3-8

AVIGATING THE WEB BROWSER INTERFACE

Table 3-2. Main Menu (Continued)

Menu Description Page

MSTP 3-153

VLAN Configuration Configures priority and VLANs for a

spanning tree instance

Port Information Displays port settings for a specified MST

instance

Trunk Information Displays trunk settings for a specified MST

instance

Port Configuration Configures port settings for a specified

MST instance

Trunk Configuration Configures trunk settings for a specified

MST instance

VLAN 3-161

802.1Q VLAN 3-161

GVRP Status Enables GVRP VLAN registration

protocol

Basic Information Displays information on the VLAN type

supported by this switch

Current Table Shows the current port members of each

VLAN and whether or not the port is tagged or untagged

Static List Used to create or remove VLAN groups 3-168

Static Table Modifies the settings for an existing VLAN 3-170

Static Membership by Port

Port Configuration Specifies default PVID and VLAN

Trunk Configuration Specifies default trunk VID and VLAN

Private VLAN 3-177

Information Displays Private VLAN feature information 3-178

Configures membership type for interfaces, including tagged, untagged or forbidden

attributes

3-153

3-157

3-159

3-165

3-166

3-172

3-173

3-9

ONFIGURING THE SWITCH

Table 3-2. Main Menu (Continued)

Menu Description Page

Configuration This page is used to create/remove primary

or community VLANs

Association Each community VLAN must be associated

with a primary VLAN

Port Information Shows VLAN port type, and associated

primary or secondary VLANs

Port Configuration Sets the private VLAN interface type, and

associates the interfaces with a private VLAN

Protocol VLAN 3-185

Configuration Configures protocol VLANs. 3-185

Port Configuration Configures protocol VLAN port type, and

associated protocol VLANs.

Priority 3-187

Default Port Priority Sets the default priority for each port 3-187

Default Trunk Priority Sets the default priority for each trunk 3-187

Traffic Classes Maps IEEE 802.1p priority tags to output

queues

Queue Mode Sets queue mode to strict priority or

Weighted Round-Robin

Queue Scheduling Configures Weighted Round Robin

queueing

IP DSCP Priority Status Globally selects IP DSCP Priority, or

disables it.

IP DSCP Priority Sets IP Differentiated Services Code Point

priority, mapping a DSCP tag to a class-of-service value

ACL CoS Priority Sets the CoS value and corresponding

output queue for packets matching an ACL rule

3-179

3-181

3-182

3-183

3-186

3-188

3-191

3-192

3-193

3-194

3-196

3-10

ASIC CONFIGURATION

Table 3-2. Main Menu (Continued)

Menu Description Page

IGMP Snooping 3-198

IGMP Configuration Enables multicast filtering; configures

parameters for multicast query

Multicast Router Port Information

Static Multicast Router Port Configuration

IP Multicast Registration Table

IGMP Member Port Table

DNS 3-207

General Configuration Configures DNS settings. 3-207

Static Host Table Add static host tables. 3-209

Cache Displays system cache information. 3-210

Displays the ports that are attached to a neighboring multicast router for each VLAN ID

Assigns ports that are attached to a neighboring multicast router

Displays all multicast groups active on this switch, including multicast IP addresses and VLAN ID

Indicates multicast addresses associated with the selected VLAN

3-199

3-202

3-203

3-204

3-205

Basic Configuration

Displaying System Information

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.

3-11

ONFIGURING THE SWITCH

• 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 Command Line Interface via Telnet.)

includes a Telnet button that allows access to the

3-12

ASIC CONFIGURATION

Figure 3-3. System Information

CLI – Specify the hostname, location and contact information.

Console(config)#hostname R&D 5 4-33 Console(config)#snmp-server location WC 9 4-128 Console(config)#snmp-server contact Geoff 4-127 Console(config)#exit Console#show system 4-79 System Description: SMC8728L2 L2 GE Switch System OID String: 1.3.6.1.4.1.202.20.58 System Information System Up Time: 0 days, 0 hours, 3 minutes, and 7.12 seconds System Name: [NONE] System Location: [NONE] System Contact: [NONE] MAC Address (Unit1): 00-13-F7-27-57-02 Web Server: Enabled Web Server Port: 80 Web Secure Server: Enabled Web Secure Server Port: 443 Telnet Server: Enable Telnet Server Port: 23 Jumbo Frame: Disabled

POST Result:

UART Loopback Test ........... PASS

DRAM Test .................... PASS

Timer Test ................... PASS

PCI Device 1 Test ............ PASS

I2C Bus Initialization ....... PASS

Switch Int Loopback Test ..... PASS

Fan Speed Test ............... PASS

Done All Pass. Console#

3-13

ONFIGURING THE SWITCH

Displaying Switch Hardware/Software Versions

Use the Switch Information page to display hardware/firmware version numbers for power status of the system.

Field Attributes

Main Board

• Serial Number – The serial number of the switch.

• Number of Ports – Number of built-in RJ-45 ports and expansion ports.

• Hardware Version – Hardware version of the main board.

• Internal Power Status – Displays the status of the internal power supply.

• Redundant Power Status – Displays the status of the redundant power supply.

Management Software

•EPLD Version – Version number of the Electronically

Programmable Logic Device code.

• 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.

the main board and management software, as well as the

Expansion Slot

• Expansion Slot 1/2 – 10GBASE module slots.

These additional parameters are displayed for the CLI.

• Redundant Power Status – Displays the status of the redundant power supply.

3-14

ASIC CONFIGURATION

Web – Click System, Switch Information.

Figure 3-4. Switch Information

CLI – Use the following command to display version information.

Console#show version 4-80 Serial Number: A613004238 Service Tag: Hardware Version: R01 EPLD Version: 15.15 Module A Type: Not present Module B Type: Not present Number of Ports: 30 Main Power Status: Up Redundant Power Status: Not present Loader Version: 1.0.0.6 Boot ROM Version: 1.0.0.8 Operation Code Version: 3.0.0.0

Console#

3-15

ONFIGURING THE SWITCH

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 “Displaying Private VLAN Interface Information” on page 3-182.)

• Static Entry Individual Port – This switch allows static filtering for unicast and multicast addresses. (Refer to “Setting Static Addresses” on page 3-132.)

• VLAN Learning – This switch uses Shared VLAN Learning (SVL), where all VLANs share the same address table.

• 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-161.)

• Local VLAN Capable – This switch supports multiple local bridges; i.e., multiple spanning trees. (Refer to “VLAN Configuration” on page 3-161.)

• 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.

3-16

ASIC CONFIGURATION

Web – Click System, Bridge Extension Configuration.

Figure 3-5. Bridge Extension Configuration

CLI – Enter the following command.

Console#show bridge-ext 4-225 Max support VLAN numbers: 255 Max support VLAN ID: 4093 Extended multicast filtering services: No Static entry individual port: Yes VLAN learning: SVL 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 unassigned 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.

3-17

ONFIGURING THE SWITCH

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-4093, 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-18

ASIC 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.

Console#config Console(config)#interface vlan 1 4-144 Console(config-if)#ip address 10.1.0.254 255.255.255.0 4-252 Console(config-if)#exit Console(config)#ip default-gateway 192.168.1.254 4-254 Console(config)#

3-19

ONFIGURING THE SWITCH

Using DHCP/BOOTP

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. DHCP IP Configuration

Note: If you lose your management connection, use a console

connection and enter “show ip interface” to determine the new switch address.

3-20

ASIC CONFIGURATION

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 1 4-144 Console(config-if)#ip address dhcp 4-252 Console(config-if)#end Console#ip dhcp restart 4-253 Console#show ip interface 4-255 IP address and netmask: 192.168.1.54 255.255.255.0 on VLAN 1, and address mode: User specified. 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.

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 restart 4-253 Console#

Enabling Jumbo Frames

You can enable jumbo frames to support data packets up to 9000 bytes in size.

Command Attributes

• Jumbo Packet Status – Check the box to enable jumbo frames.

3-21

ONFIGURING THE SWITCH

Web – Click System, Jumbo Frames.

Figure 3-8. Enabling Jumbo Frames

CLI – Specify the jumbo frame status.

Console#config Console(config)#jumbo frame Console(config)#

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.

Note: Runtime code can also be upgraded by using Batch Upgrade.

Batch Upgrade can discover switches on local, or other networks. After discovering the switches, Batch Upgrade can then be set to automatically upgrade the runtime code on all discovered switches. Batch Upgrade is provided in the Batch Upgrade folder in the CD provided with this switch. For details see the Batch Upgrade document in this Batch Upgrade folder.

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.

3-22

ASIC CONFIGURATION

• TFTP Server IP Address – The IP address of a TFTP server.

•File Type – Specify opcode (operational code) to copy firmware.

• File Name – leading letter of 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: 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 file name should not contain slashes (\ or /),

the

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. Copy Firmware

3-23

ONFIGURING THE SWITCH

If you download to a new destination file, go to the System, File Management, 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. Setting the Startup Code

To delete a file select System, File Management, Delete. Select the file name from the given list by checking the tick box and click Apply. Note that the file currently designated as the startup code cannot be deleted.

Figure 3-11. Deleting Files

CLI – Enter the IP address of the TFTP server, select “config” or

“opcode” file type, then enter the source and destination file names, set the new file to start up the system, and then restart the switch.

Console#copy tftp file 4-83 TFTP server ip address: 10.1.0.19 Choose file type:

1. config: 2. opcode: <1-2>: 2 Source file name: v1000-18.bix Destination file name: V1.0 \Write to FLASH Programming.

-Write to FLASH finish. Success. Console#config Console(config)#boot system opcode:V1.0 4-89 Console(config)#exit Console#reload 4-29

3-24

ASIC CONFIGURATION

Saving or Restoring Configuration Settings

You can upload/download configuration settings to/from a TFTP server. The configuration file can be later downloaded to restore the switch’s settings.

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 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.

• TFTP Server IP Address – The IP address of a TFTP server.

3-25

ONFIGURING THE SWITCH

• File Type – Specify config (configuration) to copy configuration file.

File Name

• (\ or /), 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: The maximum number of user-defined configuration files is

limited only by available flash memory space.

— The configuration file name should not contain slashes

the leading letter of the file name should not be a period (.),

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 Management, Copy Operation. 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. Downloading Configuration Settings for Startup

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.

3-26

ASIC CONFIGURATION

Note: You can also select any configuration file as the start-up

configuration by using the System/File Management/Set Start-Up page.

Figure 3-13. Setting the Startup Configuration Settings

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-config 4-83 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-new 4-89 Console(config)#exit Console#reload 4-29

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.

3-27

ONFIGURING THE SWITCH

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 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: 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)

• 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; Default: 9600 bps)

• Stop Bits – Sets the number of the stop bits transmitted per byte. (Range: 1-2; Default: 1 stop bit)

3-28

ASIC CONFIGURATION

Available in CLI only:

•Password – Specifies a password for the line connection. When a connection is 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 – Enables password checking at login. You can select authentication by a 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.

Figure 3-14. Console Port Setting

3-29

ONFIGURING THE SWITCH

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.

Console(config)#line console 4-14 Console(config-line)#login local 4-15 Console(config-line)#password 0 secret 4-16 Console(config-line)#timeout login response 0 4-17 Console(config-line)#exec-timeout 0 4-18 Console(config-line)#password-thresh 3 4-19 Console(config-line)#silent-time 60 4-20 Console(config-line)#databits 8 4-20 Console(config-line)#parity none 4-21 Console(config-line)#speed 115200 4-22 Console(config-line)#stopbits 1 4-23 Console(config-line)#end Console#show line 4-24 Console configuration: Password threshold: 3 times Interactive timeout: Disabled Login timeout: Disabled Silent time: 60 Baudrate: 115200 Databits: 8 Parity: none Stopbits: 1

VTY configuration: Password threshold: 3 times Interactive timeout: 600 sec Login timeout: 300 sec Console#

Telnet Settings

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)

3-30

ASIC CONFIGURATION

• 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)

Available in CLI only:

• Login – Enables password checking at login. You can select authentication by a 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..

Figure 3-15. Enabling Telnet

3-31

ONFIGURING THE SWITCH

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.

Console(config)#line vty 4-14 Console(config-line)#login local 4-15 Console(config-line)#password 0 secret 4-16 Console(config-line)#timeout login response 300 4-17 Console(config-line)#exec-timeout 600 4-18 Console(config-line)#password-thresh 3 4-19 Console(config-line)#end Console#show line 4-24 Console configuration: Password threshold: 3 times Interactive timeout: Disabled Login timeout: Disabled Silent time: Disabled Baudrate: 9600 Databits: 8 Parity: none Stopbits: 1

VTY configuration: Password threshold: 3 times Interactive timeout: 600 sec Login timeout: 300 sec Console#

Configuring Event Logging

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.

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.

3-32

ASIC CONFIGURATION

Figure 3-16. Displaying Logs

CLI – This example shows the event message stored in RAM.

Console#show log ram 4-63 [1] 00:01:37 2001-01-01 "DHCP request failed - will retry later." level: 4, module: 9, function: 0, and event no.: 10 [0] 00:00:35 2001-01-01 "System coldStart notification." level: 6, module: 6, function: 1, and event no.: 1 Console#

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)

3-33

ONFIGURING THE SWITCH

• 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)

Table 3-3. Logging Levels

Level Severity Name Description

7 Debug Debugging messages

6 Informational Informational messages only

5 Notice Normal but significant condition, such as cold

start

4 Warning Warning conditions (e.g., return false,

unexpected return)

3 Error Error conditions (e.g., invalid input, default used)

2 Critical Critical conditions (e.g., memory allocation, or

free memory error - resource exhausted)

1 Alert Immediate action needed

0 Emergency System unusable

* There are only Level 2, 5 and 6 error messages for the current firmware release.

• 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)

Note: The Flash Level must be equal to or less than the RAM Level.

Web – Click System, Log, System Logs. Specify System Log Status, set the

level of event messages to be logged to RAM and flash memory, then click Apply.

3-34

ASIC CONFIGURATION

Figure 3-17. 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 on 4-56 Console(config)#logging history ram 0 4-57 Console(config)#end Console#show logging flash 4-61 Syslog logging: Enabled History logging in FLASH: level emergencies Console#

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 s yslog messa ges. (See RFC 3164.) This type has no effect o n the kind of messages reported by the switch. However, it may be used by

3-35

ONFIGURING THE SWITCH

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-36

Figure 3-18. Remote Logs

ASIC CONFIGURATION

CLI – Enter the syslog server host IP address, choose the facility type and set the logging trap.

Console(config)#logging host 192.168.1.15 4-58 Console(config)#logging facility 23 4-59 Console(config)#logging trap 4 4-60 Console(config)#end Console#show logging trap 4-61 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#

Simple Mail Transfer Protocol

SMTP (Simple Mail Transfer Protocol) is used to send email messages between servers. The messages can be retrieved using POP or IMAP clients.

Command Attributes

• Admin Status – Enables/disables the SMTP function. (Default: Enabled)

• Email Source Address – This command specifies SMTP servers email addresses that can send alert messages.

• Severity – Specifies the degree of urgency that the message carries.

- Debugging – Sends a debugging notification. (Level 7)

- Information – Sends informatative notification only. (Level 6)

- Notifice – Sends notification of a normal but significant condition,

such as a cold start. (Level 5)

- Warning – Sends notification of a warning condition such as return

false, or unexpected return. (Level 4)

- Error – Sends notification that an error conditions has occurred,

such as invalid input, or default used. (Level 3)

3-37

ONFIGURING THE SWITCH

- Critical – Sends notification that a critical condition has occurred, such as memory allocation, or free memory error - resource exhausted. (Level 2)

- Alert – Sends urgent notification that immediate action must be taken. (Level 1)

- Emergency – Sends an emergency notification that the system is now unusable. (Level 0)

• SMTP Server List – Specifies a list of recipient SMTP servers.

• SMTP Server – Specifies a new SMTP server address to add to the SMTP Server List.

• Email Destination Address List – Specifies a list of recipient Email Destination Address.

• Email Destination Address – This command specifies SMTP servers that may receive alert messages.

Web – Click System, Log, SMTP. To add an IP address to the Server IP List, type the new IP address in the Server IP Address box, and then click Add. To delete an IP address, click the entry in the Server IP List, and then click Remove.

3-38

Figure 3-19. Enabling and Configuring SMTP

ASIC CONFIGURATION

CLI – Enter the host ip address, followed by the mail severity level, source and destination email addresses and enter the sendmail command to complete the action. Use the show logging command to display SMTP information.

Console(config)#logging sendmail host 192.168.1.19 Console(config)#logging sendmail level 3 Console(config)#logging sendmail source-email bill@this-company.com Console(config)#logging sendmail destination-email ted@this-company.com Console(config)#logging sendmail Console#

Resetting the System

Web – Click System, Reset. Click the Reset button 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#reload 4-29 System will be restarted, continue <y/n>?

Note: When restarting the system, it will always run the Power-On

Self-Test.

3-39

ONFIGURING THE SWITCH

Setting the System Clock

Simple Network Time Protocol (SNTP) allows the switch to set its internal clock based on periodic updates from a time server (SNTP or NTP). 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-73.) 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.

Configuring SNTP

You can configure the switch to send time synchronization requests to specific 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.

3-40

ASIC CONFIGURATION

Web – Select SNTP, Configuration. Modify any of the required parameters, and click Apply.

Figure 3-21. SNTP Configuration

CLI – This example configures the switch to operate as an SNTP unicast

client and then displays the current time and settings.

Console(config)#sntp client 4-70 Console(config)#sntp poll 604-71 Console(config)#sntp server 10.1.0.19 137.82.140.80 128.250.36.2

4-70

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#

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)

3-41

ONFIGURING THE SWITCH

• Hours (0-13) – 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-22. Setting the Time Zone

CLI - This example shows how to set the time zone for the system clock.

Console(config)#clock timezone Dhaka hours 6 minute 0 after-UTC4-72 Console#

Simple Network Management Protocol

Simple Network Management Protocol (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

3-42

IMPLE NETWORK MANAGEMENT PROTOCOL

information controlled by the agent. SNMP defines both 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 clients. 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 SMC EliteView. 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.

3-43

ONFIGURING THE SWITCH

Table 3-4 SNMPv3 Security Models and Levels

Model Level Group Read

v1 noAuth

NoPriv

v1 noAuth

NoPriv

v1 noAuth

NoPriv

v2c noAuth

NoPriv

v2c noAuth

NoPriv

v2c noAuth

NoPriv

v3 noAuth

NoPriv

v3 Auth

NoPriv

v3 Auth

Priv

Write

View

public

defaultview none none Community string (read only)

private

defaultview defaultview none Community string (read/ write)

user

user defined user defined user defined

public

defaultview none none Community string (read only)

private

defaultview defaultview none Community string (read/ write)

user

user defined user defined user defined

user

user defined user defined user defined

user

user defined user defined user defined

user

user defined user defined user defined

View

Notify View

defined

Security

only

Community string only

only

Community string only

A user name match only

Provides user authentication via MD5 or SHA algorithms

Provides user 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-44

IMPLE NETWORK MANAGEMENT PROTOCOL

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-23 Enabling the SNMP Agent

CLI – The following example enables SNMP on the switch.

Console(config)#snmp-server 4-124 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.

Default strings: “public” (read-only access), “private” (read/write access)

Range: 1-32 characters, case sensitive

3-45

ONFIGURING THE SWITCH

• 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.

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-24 Configuring SNMP Community Strings

CLI – The following example adds the string “spiderman” with read/write

access.

Console(config)#snmp-server community spiderman rw 4-127 Console(config)#

3-46

IMPLE NETWORK MANAGEMENT PROTOCOL

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 SMC EliteView). You can specify up to five management stations that will receive authentication failure messages and other notification 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-52). 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.

To send an inform to a SNMPv2c host, complete these steps:

1. Enable the SNMP agent (page 3-45).

2. Enable trap informs as described in the following pages.

3. Create a view with the required notification messages (page 3-63).

4. Create a group that includes the required notify view (page 3-58).

To send an inform to a SNMPv3 host, complete these steps:

1. Enable the SNMP agent (page 3-45).

2. Enable trap informs as described in the following pages.

3-47

ONFIGURING THE SWITCH

3. Create a view with the required notification messages (page 3-63).

4. Create a group that includes the required notify view (page 3-58).

5. Specify a remote engine ID where the user resides (page 3-51).

6. Then configure a remote user (page 3-55).

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)

3-48

IMPLE NETWORK MANAGEMENT PROTOCOL

- Retry times – The maximum number of times to resend an inform message if the recipient does not acknowledge receipt. (Range: 0-255; Default: 3)

• Enable Authentication Traps

– 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, 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.

Figure 3-25 Configuring SNMP Trap Managers

CLI – This example adds a trap manager and enables authentication traps.

Console(config)#snmp-server host 10.1.19.23 inform private

version 2c udp-port 160 4-129 Console(config)#snmp-server enable traps authentication 4-132 Console(config)#

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-58).

3-49

ONFIGURING THE SWITCH

Configuring SNMPv3 Management Access

To configure SNMPv3 management access to the switch, follow these steps:

1. If you want to change the default engine ID, it must be changed first before configuring other 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, 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 the 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 engine ID 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.

3-50

IMPLE NETWORK MANAGEMENT PROTOCOL

Web – Click SNMP, SNMPv3, Engine ID. Enter an ID of up to 26 hexadecimal characters and then click Save.

Figure 3-26 Setting an Engine ID

CLI – This example sets an SNMPv3 engine ID.

Console(config)#snmp-server engine-id local 12345abcdef 4-133 Console(config)#exit Console#show snmp engine-id 4-134 Local SNMP engineID: 12345abcdef000000000000000 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 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-47 and “Configuring Remote SNMPv3 Users” on page 3-55.)

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.

3-51

ONFIGURING THE SWITCH

Web – Click SNMP, SNMPv3, Remote Engine ID. Enter an ID of up to 26 hexadecimal characters and then click Save.

Figure 3-27 Setting an Engine ID

CLI – This example specifies a remote SNMPv3 engine ID.

Console(config)#snmp-server engineID remote 54321 192.168.1.19 4-133 Console(config)#exit Console#show snmp engine-id Local SNMP engineID: 8000002a8000000000e8666672 Local SNMP engineBoots: 1

Remote SNMP engineID IP address 80000000030004e2b316c54321 192.168.1.19 Console#

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, and notify view.

4-134

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).

3-52

IMPLE NETWORK MANAGEMENT PROTOCOL

- AuthPriv – SNMP communications use both authentication and

encryption (only available for the SNMPv3 security model).

• Authentication Protocol – The method used for user authentication. (Options: MD5, SHA; Default: MD5)

• Authentication Password – A minimum of eight plain text characters is required.

• Privacy Protocol – The encryption algorithm use for data privacy; only 56-bit DES is currently available.

• Privacy Password – A minimum of eight plain text characters is required.

• Actions – Enables the user to be assigned to another SNMPv3 group.

3-53

ONFIGURING THE SWITCH

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-54

Figure 3-28 Configuring SNMPv3 Users

Smc 8728L2 Management Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Key Features

Description of Software Features

System Defaults

Connecting to the Switch

Configuration Options

Required Connections

Remote Connections

Basic Configuration

Console Connection

Setting Passwords

Setting an IP Address

Manual Configuration

Dynamic Configuration

Enabling SNMP Management Access

Community Strings (for SNMP version 1 and 2c clients)

Trap Receivers

Configuring Access for SNMP Version 3 Clients

Saving Configuration Settings

Managing System Files

Using the Web Interface

Navigating the Web Browser Interface

Home Page

Configuration Options

Panel Display

Main Menu

Basic Configuration

Displaying System Information

Displaying Switch Hardware/Software Versions

Displaying Bridge Extension Capabilities

Setting the Switch’s IP Address

Manual Configuration

Using DHCP/BOOTP

Enabling Jumbo Frames

Managing Firmware

Downloading System Software from a Server

Saving or Restoring Configuration Settings

Downloading Configuration Settings from a Server

Console Port Settings

Telnet Settings

Configuring Event Logging

Displaying Log Messages

System Log Configuration

Remote Log Configuration

Simple Mail Transfer Protocol

Resetting the System

Setting the System Clock

Configuring SNTP

Setting the Time Zone

Simple Network Management Protocol

Enabling the SNMP Agent

Setting Community Access Strings

Specifying Trap Managers and Trap Types

Configuring SNMPv3 Management Access

Setting the Local Engine ID

Specifying a Remote Engine ID

Configuring SNMPv3 Users