SMC Networks TigerSwitch 100 User Manual

Download

Page 1

TigerSwitch 10/100/1000

Gigabit Ethernet Switch

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

◆ 4 ports shared with 4 SFP transceiver slots

◆ Non-blocking switching architecture

◆ Support for a redundant power unit

◆ Spanning Tree Protocol

◆ Up to six LACP or static 4-port trunks

◆ Layer 2/3/4 CoS support through four priority queues

◆ Full support for VLANs with GVRP

◆ IGMP multicast filtering and snooping

◆ Support for jumbo frames up to 9 KB

◆ Manageable via console, Web, SNMP/RMON

Management Guide

SMC8624T

Page 2

Page 3

TigerSwitch 10/100/1000 Management Guide

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

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

February 2003

Pub. # 150200016900A

Page 4

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.

Page 5

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.

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

ARRANTY

Page 6

IMITED WARRANTY

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

Page 7

ONTENTS

1 Switch Management . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

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

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

Required Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Console Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Setting Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Setting an IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Enabling SNMP Management Access . . . . . . . . . . . . . . . . . . . . . 1-9

Saving Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Managing System Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

System Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

2 Configuring the Switch . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Using the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Navigating the Web Browser Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Panel Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Displaying System Information . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Setting the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

Configuring the Logon Password . . . . . . . . . . . . . . . . . . . . . . . 2-13

Configuring RADIUS/TACACS Logon Authentication . . . . . 2-15

HTTPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

SSH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Managing Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22

Downloading System Software from a Server . . . . . . . . . . . . . . 2-23

Saving or Restoring Configuration Settings . . . . . . . . . . . . . . . . 2-24

Copying the Running Configuration to a File . . . . . . . . . . . . . . 2-26

Displaying Bridge Extension Capabilities . . . . . . . . . . . . . . . . . . . . . . . 2-27

Displaying Switch Hardware/Software Versions . . . . . . . . . . . . . . . . 2-30

Port Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

vii

Page 8

ONTENTS

Displaying Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

Configuring Interface Connections . . . . . . . . . . . . . . . . . . . . . . 2-34

Setting Broadcast Storm Thresholds . . . . . . . . . . . . . . . . . . . . . 2-36

Configuring Port Mirroring . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38

Configuring Port Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Address Table Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

Setting Static Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41

Displaying the Address Table . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42

Changing the Aging Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

Spanning Tree Protocol Configuration . . . . . . . . . . . . . . . . . . . . . . . . . 2-44

STP Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46

STP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

STP Port and Trunk Information . . . . . . . . . . . . . . . . . . . . . . . 2-54

STP Port and Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . 2-58

VLAN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-61

Assigning Ports to VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-62

Forwarding Tagged/Untagged Frames . . . . . . . . . . . . . . . . . . . 2-64

Displaying Basic VLAN Information . . . . . . . . . . . . . . . . . . . . 2-65

Displaying Current VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66

Creating VLANs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68

Adding Interfaces Based on Membership Type . . . . . . . . . . . . 2-70

Adding Interfaces Based on Static Membership . . . . . . . . . . . . 2-72

Configuring VLAN Behavior for Interfaces . . . . . . . . . . . . . . . 2-73

Class of Service Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-77

Setting the Default Priority for Interfaces . . . . . . . . . . . . . . . . . 2-77

Mapping CoS Values to Egress Queues . . . . . . . . . . . . . . . . . . 2-78

Setting the Service Weight for Traffic Classes . . . . . . . . . . . . . 2-81

Mapping Layer 3/4 Priorities to CoS Values . . . . . . . . . . . . . . 2-82

Selecting IP Precedence/DSCP Priority . . . . . . . . . . . . . . . . . 2-82

Mapping IP Precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-83

Mapping DSCP Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-86

Port Trunk Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-88

Dynamically Configuring a Trunk with LACP . . . . . . . . . . . . . 2-90

Statically Configuring a Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . 2-92

Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94

Setting Community Access Strings . . . . . . . . . . . . . . . . . . . . . . 2-95

Specifying Trap Managers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96

viii

Page 9

ONTENTS

SNMP IP Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-97

Multicast Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99

Configuring IGMP Parameters . . . . . . . . . . . . . . . . . . . . . . . . 2-100

Interfaces Attached to a Multicast Router . . . . . . . . . . . . . . . . 2-103

Displaying Port Members of Multicast Services . . . . . . . . . . . 2-105

Adding Multicast Addresses to VLANs . . . . . . . . . . . . . . . . . 2-107

Showing Device Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-108

3 Command Line Interface . . . . . . . . . . . . . . . . . . . . . . 3-1

Using the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Console Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Telnet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

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

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

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

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

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

Partial Keyword Lookup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

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

Using Command History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Understanding Command Modes . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Exec Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Configuration Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8

Command Line Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Command Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13

configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

show history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

quit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Flash/File Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Page 10

ONTENTS

delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

dir . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

whichboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23

boot system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

System Management Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

hostname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

username . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27

enable password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

jumbo frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

ip http port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

ip http server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

ip http secure-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

ip http secure-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

ip ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34

ip ssh server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

disconnect ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

show ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

show ip ssh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38

logging history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

logging host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

logging facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

logging trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

clear logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

show logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

show startup-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44

show running-config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46

show system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

show users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48

show version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

Authentication Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

authentication login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51

radius-server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

radius-server port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

radius-server key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

radius-server retransmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

radius-server timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

Page 11

ONTENTS

show radius-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

tacacs-server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

tacacs-server port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56

tacacs-server key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

show tacacs-server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

SNMP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

snmp-server community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

snmp-server contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60

snmp-server location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60

snmp-server host . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61

snmp-server enable traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63

snmp ip filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64

show snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65

IP Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

ip address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67

ip dhcp restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69

ip default-gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

show ip interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70

show ip redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-71

ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72

Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73

line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74

password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76

exec-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77

password-thresh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78

silent-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79

databits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80

parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-81

speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82

stopbits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83

show line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83

Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-84

interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85

description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86

speed-duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-86

negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88

Page 12

ONTENTS

capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-89

flowcontrol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-90

shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-91

switchport broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92

port security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93

clear counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94

show interfaces status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95

show interfaces counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97

show interfaces switchport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-98

Address Table Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

mac-address-table static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100

show mac-address-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102

clear mac-address-table dynamic . . . . . . . . . . . . . . . . . . . . . . . 3-103

mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . . . . . . 3-103

show mac-address-table aging-time . . . . . . . . . . . . . . . . . . . . . 3-104

Spanning Tree Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-105

spanning-tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-106

spanning-tree mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-107

spanning-tree forward-time . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-108

spanning-tree hello-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109

spanning-tree max-age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-109

spanning-tree priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-110

spanning-tree pathcost method . . . . . . . . . . . . . . . . . . . . . . . . 3-111

spanning-tree transmission-limit . . . . . . . . . . . . . . . . . . . . . . . 3-112

spanning-tree cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-113

spanning-tree port-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-114

spanning-tree portfast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-115

spanning-tree edge-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-116

spanning-tree protocol-migration . . . . . . . . . . . . . . . . . . . . . . 3-117

spanning-tree link-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-118

show spanning-tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-119

VLAN Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-121

vlan database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-122

vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-123

interface vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-124

switchport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-125

switchport acceptable-frame-types . . . . . . . . . . . . . . . . . . . . . 3-126

xii

Page 13

ONTENTS

switchport ingress-filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-127

switchport native vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-128

switchport allowed vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-129

switchport forbidden vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-130

show vlan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-131

GVRP and Bridge Extension Commands . . . . . . . . . . . . . . . . . . . . . 3-132

switchport gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-132

show gvrp configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-133

garp timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-134

show garp timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-135

bridge-ext gvrp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-136

show bridge-ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-137

IGMP Snooping Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-138

ip igmp snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-139

ip igmp snooping vlan static . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-140

ip igmp snooping version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141

show ip igmp snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-141

show mac-address-table multicast . . . . . . . . . . . . . . . . . . . . . . 3-142

ip igmp snooping querier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143

ip igmp snooping query-count . . . . . . . . . . . . . . . . . . . . . . . . . 3-144

ip igmp snooping query-interval . . . . . . . . . . . . . . . . . . . . . . . 3-145

ip igmp snooping query-max-response-time . . . . . . . . . . . . . . 3-145

ip igmp snooping router-port-expire-time . . . . . . . . . . . . . . . . 3-147

ip igmp snooping vlan mrouter . . . . . . . . . . . . . . . . . . . . . . . . 3-148

show ip igmp snooping mrouter . . . . . . . . . . . . . . . . . . . . . . . 3-149

Priority Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-150

switchport priority default . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-151

queue bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-152

queue cos-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-153

show queue bandwidth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

show queue cos-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-155

map ip precedence (Global Configuration) . . . . . . . . . . . . . . . 3-156

map ip precedence (Interface Configuration) . . . . . . . . . . . . . 3-157

map ip dscp (Global Configuration) . . . . . . . . . . . . . . . . . . . . 3-158

map ip dscp (Interface Configuration) . . . . . . . . . . . . . . . . . . . 3-159

show map ip precedence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-160

show map ip dscp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-161

xiii

Page 14

ONTENTS

Mirror Port Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-163

port monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-163

show port monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-164

Port Trunking Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-166

channel-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-167

lacp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-168

A Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Troubleshooting Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

B Upgrading Firmware via the Serial Port . . . . . . . . . . .B-1

C Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

Console Port Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

DB-9 Port Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Console Port to 9-Pin DTE Port on PC . . . . . . . . . . . . . . . . . . . C-2

Console Port to 25-Pin DTE Port on PC . . . . . . . . . . . . . . . . . . C-2

Glossary

Index

xiv

Page 15

HAPTER

WITCH

ANAGEMENT

Connecting to the Switch

Configuration Options

The TigerSwitch 10/100/1000 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 assigned via DHCP by default. To

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

The switch’s HTTP Web agent allows you to configure switch parameters, monitor port connections, and display statistics graphically 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 switch’s management agent is based on SNMP (Simple Network Management Protocol). This SNMP agent permits the switch to be managed from any system in the network using management software.

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.

1-1

Page 16

WITCH MANAGEMENT

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

• Set user names and passwords for up to 16 users

• Set an IP interface for a management VLAN

• Configure SNMP parameters

• Enable/disable any port

• Set the speed/duplex mode for any port

• Configure up to 255 IEEE 802.1Q VLANs

• Enable GVRP automatic VLAN registration

• Configure IGMP multicast filtering

• Upload and download of system firmware via TFTP

• Upload and download of switch configuration files via TFTP

• Configure Spanning Tree parameters

• Configure Class of Service (CoS) priority queuing

• Configure up to six static or LACP trunks

• Enable jumbo frame support

• Enable port mirroring

• Set broadcast storm control on any port

• Display system information and statistics

1-2

Page 17

ONNECTING TO THE SWITCH

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

To connect a terminal to the console port, complete the following steps:

1. Connect the console cable to the serial port on a terminal, or a PC

running terminal emulation software, and tighten the captive retaining screws on the DB-9 connector.

2. Connect the other end of the cable to the RS-232 serial port on the

switch.

3. Make sure the terminal emulation software is set as follows:

• Select the appropriate serial port (COM port 1 or COM port 2).

• Set the data rate to 9600 baud.

• Set the data format to 8 data bits, 1 stop bit, and no parity.

• Set flow control to none.

• Set the emulation mode to VT100.

• When using HyperTerminal, select Terminal keys, not Windows keys.

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

Windows® 2000,

1-3

Page 18

WITCH MANAGEMENT

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

Note: Refer to “Line Commands” on page 3-73 for a complete

description of console configuration options.

For a description of how to use the CLI, see “Using the Command Line Interface” on page 3-1. For a list of all the CLI commands and detailed information on using the CLI, refer to “Command Groups” on page 3-10.

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

Note: This switch supports four concurrent Telnet 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 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.

1-4

Page 19

ASIC CONFIGURATION

Basic Configuration

Console Connection

The CLI program provides two different command levels — normal access level (Normal Exec) and privileged access level (Privileged Exec). The commands available at the Normal Exec level are a limited subset of those available at the Privileged Exec level and allow you to only display information and use basic utilities. To fully configure switch parameters, you must access the CLI at the Privileged Exec level.

Access to both CLI levels are controlled by user names and passwords. The switch has a default user name and password for each level. To log into the CLI at the Privileged Exec level using the default user name and password, perform these steps:

1. To initiate your console connection, press <Enter>. The “User Access Verification” procedure starts.

2. At the Username prompt, enter “admin.”

3. At the Password prompt, also enter “admin.” (The password characters are not displayed on the console screen.)

4. The session is opened and the CLI displays the “Console#” prompt indicating you have access at the Privileged Exec level.

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.

1-5

Page 20

WITCH MANAGEMENT

Passwords can consist of up to eight 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>.

Username: admin Password: CLI session with the SMC8624T 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.

1-6

Page 21

ASIC CONFIGURATION

Note: Only one VLAN interface can be assigned an IP address (the

default is VLAN 1). This defines the management VLAN, the only VLAN through which you can gain management access to the switch. If you assign an IP address to any other VLAN, the new IP address overrides the original IP address and this becomes the new management VLAN.

Manual Configuration

You can manually assign an IP address to the switch. You may also need to specify a default gateway that resides between this device and management stations that exist on another network segment. Valid IP addresses consist of four decimal numbers, 0 to 255, separated by periods. Anything outside this format will not be accepted by the CLI program.

Note: The IP address for this switch is assigned 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

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

1-7

Page 22

WITCH MANAGEMENT

4. To set the IP address of the default gateway for the network to which the switch belongs, type “ip default-gateway gateway,” where “gateway” is the IP address of the default gateway. Press <Enter>.

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” 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, then the switch will start broadcasting service requests as soon as it is powered on.

To automatically configure the switch by communicating with BOOTP or DHCP address allocation servers on the network, complete the following steps:

1. From the Privileged Exec level 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 through DHCP, type “ip address dhcp” and

press <Enter>.

• To obtain IP settings through BOOTP, type “ip address bootp”

and press <Enter>.

1-8

Page 23

ASIC CONFIGURATION

3. Type “exit” to return to the global configuration mode. Press <Enter>.

4. Type “ip dhcp restart” 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>.

Console(config)#interface vlan 1 Console(config-if)#ip address dhcp Console(config-if)#exit Console#ip dhcp restart Console#show ip interface IP interface vlan

IP address and netmask: 10.1.0.54 255.255.255.0 on VLAN 1,

and address mode: User specified. Console#copy running-config startup-config Startup configuration file name []: startup

Console#

Enabling SNMP Management Access

The switch can be configured to accept management commands from Simple Network Management Protocol (SNMP) applications. 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.

1-9

Page 24

WITCH MANAGEMENT

Community Strings

Community strings are used to control management access to SNMP 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 or user groups, and set the access level.

The default strings are:

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

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

Note: If you do not intend to utilize SNMP, it is recommended that you

delete both of the default community strings. If there are no community strings, then SNMP management access to the switch is disabled.

To prevent unauthorized access to the switch via SNMP, 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>.

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

1-10

Page 25

ASIC CONFIGURATION

Trap Receivers

You can also specify SNMP stations that are to receive traps from the switch.

To configure a trap receiver, complete the following steps:

1. From the Privileged Exec level global configuration mode prompt, type “snmp-server host host-address community-string,” where “host-address” is the IP address for the trap receiver and “community-string” is the string associated with that host. Press <Enter>.

2. In order to configure the switch to send SNMP notifications, you must enter at least one snmp-server enable traps command. Type “snmp-server enable traps type,” where “type” is either authentication or link-up-down. Press <Enter>.

Console(config)#snmp-server enable traps link-up-down Console(config)#

Saving Configuration Settings

Configuration commands only modify the running configuration file and are not saved when the switch is rebooted. To save all your configuration changes in nonvolatile storage, you must copy the running configuration file to the start-up configuration file using the “copy” command.

To save the current configuration settings, enter the following command:

1. From the Privileged Exec mode prompt, type “copy running-config startup-config” and press <Enter>.

2. Enter the name of the start-up file. Press <Enter>.

1-11

Page 26

WITCH MANAGEMENT

Console#copy running-config startup-config Startup configuration file name []: startup

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 — These files store system configuration information and are 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 2-24 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, Web and SNMP management interfaces. See “Managing Firmware” on page 2-22 for more information.

• Diagnostic Code — Software that is run during system boot-up, also known as POST (Power On Self-Test). This code also provides a facility to upload firmware files to the system directly through the console port. See“Upgrading Firmware via the Serial Port” on page B-1.

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.

1-12

Page 27

YSTEM DEFAULTS

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.

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. See “Saving or Restoring Configuration Settings” on page 2-24.

The following table lists some of the basic system defaults.

Function Parameter Default

IP Settings Management VLAN 1

DHCP Enabled

BOOTP Disabled

User Specified Disabled

IP Address 0.0.0.0

Subnet Mask 255.0.0.0

Default Gateway 0.0.0.0

Web Management HTTP Server Enabled

HTTP Port Number 80

SNMP Community Strings “public” (read only)

“private” (read/write)

Authentication Failure Traps

Link-up-Down Traps Enabled

Enabled

1-13

Page 28

WITCH MANAGEMENT

Function Parameter Default

Security Privileged Exec Level Username “admin”

Normal Exec Level Username “guest”

Enable Privileged Exec from Normal Exec Level

Authentication local

Console Port Connection

Port Status Admin Status Enabled

Link Aggregation Static Trunks none

Spanning Tree Protocol

Address Table Aging Time 300 seconds

Baud Rate 9600

Data bits 8

Stop bits 1

Parity none

Local Console Timeout 0 (disabled)

Auto-negotiation Enabled

Flow Control Disabled

10/100/1000 Mbps Port Capability

LACP (all ports) Disabled

Status Enabled

Fast Forwarding Disabled

Password “admin”

Password “guest”

Password “super”

10 Mbps half duplex 10 Mbps full duplex 100 Mbps half duplex 100 Mbps full duplex 1000 Mbps full duplex Full-duplex flow control disabled Symmetric flow control disabled

(Defaults: All parameters based on IEEE 802.1w)

1-14

Page 29

Function Parameter Default

Virtual LANs Default VLAN 1

PVID 1

Acceptable Frame Type All

Ingress Filtering Disabled

GVRP (global) Disabled

GVRP (port interface) Disabled

Class of Service Ingress Port Priority 0

Weighted Round Robin Class 0: 16

Class 1: 64 Class 2: 128 Class 3: 240

IP Precedence Priority Disabled

IP DSCP Priority Disabled

Multicast Filtering IGMP Snooping Enabled

Act as Querier Enabled

Broadcast Storm Protection

System Log Status Enabled

Jumbo Frames Status Disabled

Status Enabled (all ports)

Broadcast Limit Rate 256 packets per second

Messages Logged Levels 0-7 (all)

Messages Logged to Flash Levels 0-3

YSTEM DEFAULTS

1-15

Page 30

WITCH MANAGEMENT

1-16

Page 31

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 3 “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 the IP Address” on page 2-10.)

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 “Configuring the Logon Password” on page 2-13.)

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

2-1

Page 32

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 page information but only change the guest password. If you log in as “admin” (Privileged Exec level), you can apply changes on all pages.

3. If the path between your management station and this switch does not pass through any device that uses the Spanning Tree Protocol, then you can set the switch port attached to your management station to fast forwarding to improve the switch’s response time to management commands issued through the Web interface. (See “STP Port and Trunk Configuration” on page 2-58.)

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.

2-2

Page 33

AVIGATING THE WEB BROWSER INTERFACE

The Main Menu links are used to navigate to other menus, and display configuration parameters and statistics.

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” or “Apply Changes” 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

prior to pressing “Apply” or “Apply Changes.”

Refresh Immediately updates values for the current page.

Apply Sets specified values to the system.

Apply Changes Sets specified values to the system.

2-3

Page 34

ONFIGURING THE SWITCH

Notes: 1. To ensure proper screen refresh, be sure that Internet Explorer

5.x is configured as follows: Under the menu “Tools / Internet Options / General / Temporary Internet Files / Settings,” the setting for item “Check for newer versions of stored pages” should be “Every visit to the page.”

2. When using Internet Explorer 5.0, you may have to manually refresh the screen after making configuration changes by pressing the browser’s refresh button.

Panel Display

The Web agent displays an image of the switch’s ports, indicating whether each link is up or down. Clicking on the image of a port opens the Port Configuration page as described on page 2-34.

2-4

Page 35

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.

Menu Description Page

System

System Information Provides basic system description, including

contact information

IP Sets the IP address for management access 2-10

Passwords Assigns a new password for the logon user name 2-13

Authentication Settings

HTTPS Settings Configures secure HTTP settings. 2-19

SSH Settings Configures Secure Shell settings. 2-21

Firmware Manages code image files 2-23

Configuration Manages switch configuration files 2-24

Reset Restarts the switch

Bridge Extension Shows the configuration for bridge extension

Switch Information Shows the number of ports, hardware/firmware

Port

Port Information Displays port connection status 2-32

Trunk Information Displays trunk connection status 2-32

Port Configuration Configures port connection settings 2-34

Trunk Configuration Configures trunk connection settings 2-34

Broadcast Storm Protect Configuration

Mirror Sets the source and target ports for mirroring 2-38

Configures RADIUS and TACACS+ authentication parameters

commands; enables GVRP multicast protocol

version numbers, and power status

Sets the broadcast storm threshold for each port 2-36

AIN MENU

2-8

2-15

2-27

2-30

2-5

Page 36

ONFIGURING THE SWITCH

Menu Description Page

Port Security Action Configures the port intrusion action globally for

the switch

Port Security Status Enables port security on specified ports 2-40

Address Table

Static Addresses Displays entries for interface, address or VLAN 2-41

Dynamic Addresses Displays or edits static entries in the Address

Table

Address Aging Sets timeout for dynamically learned entries 2-44

Spanning Tree

STP Information Displays STP values used for the bridge 2-46

STP Configuration Configures global bridge settings for STP 2-50

STP Port Information Configures individual port settings for STP 2-54

STP Trunk Information

STP Port Configuration

STP Trunk Configuration

VLAN

VLAN Basic Information

VLAN Current Table Shows the current port members of each VLAN

VLAN Static List Used to create or remove VLAN groups 2-68

VLAN Static Table Modifies the settings for an existing VLAN 2-70

VLAN Static Membership by Port

VLAN Port Configuration

VLAN Trunk Configuration

Configures individual trunk settings for STP 2-54

Configures individual port settings for STP 2-58

Configures individual trunk settings for STP 2-58

Displays basic information on the VLAN type supported by this switch

and whether or not the port supports VLAN tagging

Configures membership type for interfaces including tagged and untagged

Specifies default PVID and VLAN attributes 2-73

Specifies default trunk VID and VLAN attributes

2-40

2-42

2-65

2-66

2-72

2-73

2-6

Page 37

AIN MENU

Menu Description Page

Priority

Default Port Priority Sets the default priority for each port 2-77

Default Trunk Priority Sets the default priority for each trunk 2-77

Traffic Class Maps IEEE 802.1p priority tags to output

queues

Queue Scheduling Configures Weighted Round Robin queueing 2-81

IP Precedence/DSCP Priority Status

IP Precedence Priority Sets IP Type of Service priority, mapping the

IP DSCP Priority Sets IP Differentiated Services Code Point

Trunk

LACP Configuration Allows ports to dynamically join trunks 2-90

Trunk Configuration Specifies ports to group into static trunks 2-92

SNMP

SNMP Configuration Configures community strings and related trap

SNMP IP Filtering Configures IP filtering for SNMP access. 2-97

IGMP

IGMP Configuration Enables multicast filtering; configures

Multicast Router Port Information

Static Multicast Router Port Configuration

IP Multicast Registration Table

Globally selects IP Precedence or DSCP Priority, or disables both

precedence tag to a class-of-service value

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

functions.

parameters for multicast query

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

Assigns ports that are attached to a neighboring multicast router/switch

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

2-78

2-82

2-83

2-86

2-94

2-100

2-103

2-104

2-107

2-7

Page 38

ONFIGURING THE SWITCH

Menu Description Page

IGMP Member Port Table

Statistics Lists Ethernet and RMON port statistics 2-108

Indicates multicast addresses associated with the selected VLAN

Basic Configuration

Displaying System Information

You can easily identify the system by providing a descriptive name, location and contact information.

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

2-105

• Contact – Administrator responsible for the system.

• System Up Time – Length of time the management agent has been up.

• MAC Address

• Web server

– The physical layer address for the switch.

– Shows if management access via HTTP is enabled or

disabled.

• Web server port

– Shows the TCP port number used by the Web

interface.

• Web secure server

– Shows if management access via secure HTTP

(HTTPS) is enabled or disabled.

2-8

Page 39

ASIC CONFIGURATION

• Web secure server port* – Shows the TCP port number used by the HTTPS server.

• POST result

* CLI Only

– Shows results of the power-on self-test

Web – Click System, System Information. Specify the system name, location, and contact information for the system administrator, then click Apply. (This page also includes

a Telnet button that allows you to access the

Command Line Interface via Telnet.)

2-9

Page 40

ONFIGURING THE SWITCH

CLI – Specify the hostname, location and contact information.

Console(config)#hostname Test Switch 3-27 Console(config)#snmp-server location TPS - 3rd Floor 3-60 Console(config)#snmp-server contact Chris 3-60 Console#show system 3-47 System description: SMC Networks SMC8624T System OID string: 1.3.6.1.4.1.1991.1.5.1.1.4.1.1 System information

System Up time: 0 days, 2 hours, 4 minutes, and 7.13 seconds System Name : Test Switch System Location : TPS - 3rd Floor System Contact : Chris MAC address : 00-30-f1-47-58-3a Web server : enable Web server port : 80 Web secure server : enable Web secure server port : 443 POST result

--- Performing Power-On Self Tests (POST) ---

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

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

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

I2C Initialization ..................... PASS

Runtime Image Check .................... PASS

PCI Device Check ....................... PASS

Switch Driver Initialization ........... PASS

Switch Internal Loopback Test .......... PASS

------------------- DONE -------------------Console#

Setting the IP Address

An IP address may be used for management access to the switch over your network. By default, the switch uses DHCP to assign IP settings to VLAN 1 on the switch. If you wish to manually configure IP settings, you need to change the switch’s user-specified defaults (IP address 0.0.0.0 and netmask 255.0.0.0) to values that are compatible with your network. You may also need to a establish a default gateway between the switch and management stations that exist on another network segment.

You can manually configure a specific IP address, or direct the device to obtain an address from a BOOTP or DHCP server when it is powered on. 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.

2-10

Page 41

ASIC CONFIGURATION

• Management VLAN – This is the only VLAN through which you can gain management access to the switch. By default, all ports on the switch are members of VLAN 1, so a management station can be connected to any port on the switch. However, if other VLANs are configured and you change the Management VLAN, you may lose management access to the switch. In this case, you should reconnect the management station to a port that is a member of the Management VLAN.

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

• Subnet Mask – This mask identifies the host address bits used for routing to specific subnets.

• Gateway IP Address – IP address of the gateway router between this device and management stations that exist on other network segments.

• MAC Address – The MAC address of this switch.

2-11

Page 42

ONFIGURING THE SWITCH

Manual Configuration

Web – Click System, IP. Specify the management interface, IP address and

default gateway, then click Apply.

CLI – Specify the management interface, IP address and default gateway.

Console#config Console(config)#interface vlan 1 3-85 Console(config-if)#ip address 10.2.13.30 255.255.255.0 3-67 Console(config-if)#exit Console(config)#ip default-gateway 192.168.1.254 3-70 Console(config)#

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. Specify the Management VLAN, set the IP Address Mode to DHCP or BOOTP. Then click “Apply” to save your changes. The switch will broadcast a request for IP configuration settings on the next power reset. Otherwise, you can click “Restart DHCP” to immediately request a new address.

2-12

Page 43

ECURITY

If you lose your management connection, use a console connection and enter “show ip interface” to determine the new switch address.

CLI – Specify the management interface, and set the IP Address Mode to DHCP or BOOTP.

Console(config)#interface vlan 1 3-85 Console(config-if)#ip address dhcp 3-67 Console(config-if)#end Console#ip dhcp restart 3-69 Console#show ip interface 3-70 IP address and netmask: 10.1.0.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.

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 3-69

Security

Configuring the Logon Password

The guest only has read access for most configuration parameters. However, the administrator has write access for parameters governing the onboard agent. You should therefore assign a new administrator password

2-13

Page 44

ONFIGURING THE SWITCH

as soon as possible, and store it in a safe place. (If for some reason your password is lost, you can reload the factory deafults file to restore the default passwords as described in “Troubleshooting Chart” on page A-1.)

The default guest name is “guest” with the password “guest.” The default administrator name is “admin” with the password “admin.” Note that user names can only be assigned via the CLI.

Command Attributes

• User Name* – The name of the user. (Maximum length: 8 characters, case sensitive; maximum number of users: 16)

• Access Level* – Specifies the user level. (Options: 0 - Normal, 15 - Privileged.)

• Password – Specifies the user password. (Range: 0-8 characters plain text, case sensitive)

* CLI only.

Web – Click System/Passwords. To change the password for the current user, enter the old password, then enter the new password, confirm it by entering it again, then click “Apply.”

2-14

Page 45

CLI – Assign a user name to access-level 15 (i.e., administrator), then specify the password.

Console(config)#username bob access-level 15 3-27 Console(config)#username bob password 0 smith Console(config)#

Configuring RADIUS/TACACS Logon Authentication

You can configure this switch to authenticate users logging into the system for management access using local, RADIUS, or TACACS+ authentication methods.

RADIUS and TACACS+ are logon authentication protocols that use software running on a central server to control access to RADIUS-aware or TACACS+-aware devices on the network. An authentication server contains a database of multiple user name, password pairs with associated privilege levels for each user that requires management access to a switch.

Like RADIUS, Terminal Access Controller Access Control System Plus (TACACS+) is a system that uses a central server to control authentication for access to switches on the network.

ECURITY

RADIUS uses UDP while TACACS+ uses TCP. UDP only offers best effort delivery, while TCP offers a connection-oriented transport. Also, note that RADIUS encrypts only the password in the access-request packet from the client to the server, while TACACS+ encrypts the entire body of the packet.

Command Usage

• By default, management access is always checked against the authentication database stored on the local switch. If a remote authentication server is used, you must specify the authentication sequence and the corresponding parameters for the remote authentication protocol.

2-15

Page 46

ONFIGURING THE SWITCH

• RADIUS uses UDP while TACACS+ uses TCP. UDP only offers best effort delivery, while TCP offers a connection-oriented transport. Also, note that RADIUS encrypts only the password in the access-request packet from the client to the server, while TACACS+ encrypts the entire body of the packet.

• RADIUS and TACACS+ logon authentication control management access via the console port, Web browser, or Telnet. These access options must be configured on the authentication server.

• RADIUS and TACACS+ logon authentication assign a specific privilege level for each user name/password pair. The user name, password, and privilege level must be configured on the authentication server.

• You can specify up to three authentication methods for any user to indicate the authentication sequence. For example, if you select (1) RADIUS, (2) TACACS and (3) Local, the user name and password on the RADIUS server is verified first. If the RADIUS server is not available, then authentication is attempted using the TACACS+ server, and finally the local user name and password is checked.

Command Attributes

• Authentication – Select the authentication, or authentication sequence required:

- RADIUS – User authentication is performed using a RADIUS server only.

- TACACS – User authentication is performed using a TACACS+ server only.

- Local – User authentication is performed only locally by the switch.

- [authentication sequence] – User authentication is performed by up to three authentication methods in the indicated sequence.

2-16

Page 47

ECURITY

The local switch user database has to be set up by manually entering user names and passwords using the CLI.

RADIUS Settings

• Server IP Address – Address of the RADIUS server. (Default: 10.1.0.1)

• Server Port Number – Network (UDP) port of the RADIUS server used for authentication messages. (Range: 1-65535; Default: 1812)

• Secret Text String – Encryption key used to authenticate logon access for client. Do not use blank spaces in the string. (Maximum length: 20 characters)

• Number of Server Transmits – Number of times the switch will try to authenticate logon access via the RADIUS server. (Range: 1-30; Default: 2)

• Timeout for a reply (secs) – The number of seconds the switch waits for a reply from the RADIUS server before it resends the request. (Range: 1-65535; Default: 5)

TACACS+ Settings

• Server IP Address – Address of the TACACS+ server. (Default: 10.1.0.1)

• Server Port Number – Network (TCP) port of TACACS+ server used for authentication messages. (Range: 1-65535; Default: 1812)

• Secret Text String – Encryption key used to authenticate logon access for client. Do not use blank spaces in the string. (Maximum length: 20 characters)

Note: The local switch user database has to be set up by manually

entering user names and passwords using the CLI.

2-17

Page 48

ONFIGURING THE SWITCH

Web – Click System, Authentication Settings. To configure local or remote authentication preferences, specify the authentication sequence (i.e., one to three methods), fill in the parameters for RADIUS or TACACS+ authentication if selected, and click Apply.

2-18

Page 49

CLI Commands

CLI – Specify all the required parameters to enable logon authentication.

Console(config)#authentication login radius 3-51 Console(config)#radius-server host 192.168.1.25 3-52 Console(config)#radius-server port 181 3-53 Console(config)#radius-server key green 3-53 Console(config)#radius-server retransmit 5 3-54 Console(config)#radius-server timeout 10 3-55 Console#show radius-server 3-55 Server IP address: 192.168.1.25

Communication key with radius server: green Server port number: 181 Retransmit times: 5

Request timeout: 10 Console(config)#authentication login tacacs 3-51 Console(config)#tacacs-server host 10.20.30.40 3-56 Console(config)#tacacs-server port 200 3-56 Console(config)#tacacs-server key green 3-57 Console#show tacacs-server 3-57 Server IP address: 10.20.30.40

Communication key with tacacs server: green

Server port number: 200 Console(config)#

HTTPS

You can configure the switch to enable the Secure Hypertext Transfer Protocol (HTTPS) over the Secure Socket Layer (SSL), providing secure access (i.e., an encrypted connection) to the switch’s Web interface.

ECURITY

Both the HTTP and HTTPS service can be enabled independently on the switch. However, you cannot configure the HTTP and HTTPS servers to use the same UDP port. If you change the HTTPS port number, clients attempting to connect to the HTTPS server must specify the port number in the URL, in this format: https://device:port_number.

Note: If you enable HTTPS, you must indicate this in the URL.

For example: https://device [:port_number]

2-19

Page 50

ONFIGURING THE SWITCH

The following Web browsers and operating systems currently support HTTPS:

Web Browser Operating System

Internet Explorer 5.0 or later Windows 98, Windows NT (with service pack

6a), Windows 2000

Netscape Navigator 4.76 or later Windows 98, Windows NT (with service pack

6a), Windows 2000, Solaris 2.6

When you start HTTPS, the client and server establish a secure encrypted connection. A padlock icon should appear in the status bar for Internet Explorer 5.x and Netscape Navigator 4.x.

Command Attributes

• HTTPS Status — Allows you to enable/disable the HTTPS server feature on the switch.

•

HTTPS Port — Specifies the UDP port number used for HTTPS/ SSL connection to the switch’s Web interface. The default is port 443.

(Default: Enabled)

Web – Click System/HTTPS Settings. Select “Enabled” for the HTTPS Status and specify the port number, then click “Apply.”

2-20

Page 51

CLI Commands

CLI – Enter the following commands to specify the secure port number and to enable HTTPS.

Console(config)#ip http secure-server 3-32 Console(config)#ip http secure-port 441 3-33 Console(config)#

SSH

The Secure Shell (SSH) server feature provides remote management access via encrypted paths between the switch and SSH-enabled management station clients.

Note: There are two versions of the SSH protocol currently available,

SSH v1.x and SSH v2.x. The switch supports only SSH v1.5.

Command Attributes

• SSH Server Status — Allows you to enable/disable the SSH server feature on the switch.

(Default: enabled)

ECURITY

• SSH authentication timeout — Specifies the time interval in seconds that the SSH server waits for a response from a client during an authentication attempt. (Range: 1 to 120 seconds; Default: 120 seconds)

• SSH authentication retries — Specifies the number of authentication attempts that a client is allowed before authentication fails and the client has to restart the authentication process. (Range: 1 to 5 times; Default: 3)

Web – Click System, SSH Settings. Select “Enabled” for the SSH Server Status, specify the authentication timeout and number of retries, then click Apply.

2-21

Page 52

ONFIGURING THE SWITCH

CLI Commands

CLI – Enter the following commands to configure the SSH service.

Console(config)#ip ssh server 3-35 Console(config)#ip ssh timeout 100 3-34 Console(config)#ip ssh authentication-retries 5 3-34 Console(config)# Console#show ip ssh 3-37 Information of secure shell SSH status: enable SSH authentication timeout: 100 SSH authentication retries: 5 Console#show ssh 3-37 Information of secure shell Session Username Version Encrypt method Negotiation state

------- -------- ------- -------------- ----------------0 admin 1.5 cipher-3des session-started

Console#disconnect ssh 0 3-36 Console#

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.

Command Attributes

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

2-22

Page 53

ANAGING FIRMWARE

•

Destination File Name

name should not contain slashes (\ or /), the 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: The maximum number of runtime code files is 2.

—

File names are case-sensitive. The file

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, Firmware. Enter the IP address of the TFTP server, 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 “Transfer from Server.”

When you download a file using a different name from the current runtime code file, you need to select the new file name from the drop-down box for the operation code used at startup, and then click Apply Changes.

2-23

Page 54

ONFIGURING THE SWITCH

To start the new firmware, reboot the system.

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 3-18 TFTP server ip address: 10.1.0.99 Choose file type:

1. config: 2. opcode: <1-2>: 2 Source file name: v10.bix Destination file name: V10000 / Console#config Console(config)#boot system opcode: V10000 3-24 Console(config)#exit Console#reload 3-16

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

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

•

Destination File Name

name should not contain slashes (\ or /), the leading letter of the file name should not be a period (.), and the maximum length for file

—

File names are case-sensitive. The file

2-24

Page 55

ANAGING FIRMWARE

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.

You can save 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 a destination file name on the switch.

Web – Click System, Configuration. Enter the IP address of the TFTP server, enter the name of the file to download, select a file on the switch to overwrite or specify a new file name, and then click “Transfer from Server.”

When you download a file using a different name from the current startup configuration file, you need to select the new file name from from the drop-down box for Startup Configuration File, and press Apply Changes. To use the new settings, reboot the system via the System, Reset menu.

2-25

Page 56

ONFIGURING THE SWITCH

CLI – Enter the IP address of the TFTP server, specify the source file on the server, and set the startup file name on the switch. If you download the startup configuration file under a new file name, you can set this file as the startup file at a later time, and then restart the switch.

Console#copy tftp startup-config 3-18 TFTP server ip address: 192.168.1.19 Source configuration file name: startup2.0 Startup configuration file name [startup] : startup2.0 \Write to FLASH Programming.

-Write to FLASH finish. Success.

Console#config Console(config)#boot system config: startup2.0 3-24 Console(config)#exit Console#reload

Copying the Running Configuration to a File

You can save the current running configuration to a new file name and then set it as the startup file. Enter a name for the new configuration file, and then click Copy to File.

2-26

Page 57

ISPLAYING BRIDGE EXTENSION CAPABILITIES

CLI – If you copy the running configuration to a file, you can set this file as the startup file at a later time, and then restart the switch.

Console#copy running-config file 3-18 destination file name : 051902.cfg / Console# Console#config Console(config)#boot system config: 051902.cfg 3-24 Console(config)#exit Console#reload 3-16

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, or to configure the global setting for GARP VLAN Registration Protocol (GVRP).

Command Attributes

• Extended Multicast Filtering Services – This switch does not

support the filtering of individual multicast addresses based on GMRP (GARP Multicast Registration Protocol).

• Traffic Classes – This switch provides mapping of user priorities to

multiple traffic classes. (Refer to “Class of Service Configuration” on page 2-77.)

2-27

Page 58

ONFIGURING THE SWITCH

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

• VLAN Learning – This switch uses Independent VLAN Learning (IVL), where each port maintains its own filtering database.

• Configurable PVID Tagging – This switch allows you to override the default Port VLAN ID (PVID used in frame tags) and egress status (VLAN-Tagged or Untagged) on each port. (Refer to “VLAN Configuration” on page 2-61.)

• Local VLAN Capable – This switch does not support multiple local bridges (i.e., multiple Spanning Trees).

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

• GVRP – GARP VLAN Registration Protocol (GVRP) defines a way for switches to exchange VLAN information in order to register necessary VLAN members on ports across the network. This function should be enabled to permit VLANs groups which extend beyond the local switch.

2-28

Page 59

ISPLAYING BRIDGE EXTENSION CAPABILITIES

Web – Click System, Bridge Extension.

CLI – Enter the following command.

Console#show bridge-ext 3-137

Max support vlan numbers: 255 Max support vlan ID: 4094 Extended multicast filtering services: No Static entry individual port: Yes VLAN learning: IVL Configurable PVID tagging: Yes Local VLAN capable: No Traffic classes: Enabled Global GVRP status: Enabled GMRP: Disabled

Console#

2-29

Page 60

ONFIGURING THE SWITCH

Displaying Switch Hardware/Software Versions

Command Attributes

Main Board

• Serial Number – The serial number of the switch.

• Service Tag* – Not implemented.

• Number of Ports – Number of built-in RJ-45 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.

* CLI only.

Management Software

• Loader Version – Version number of loader code.

• Boot-ROM Version – Version number of Power-On Self-Test (POST) and boot code.

• Operation Code Version – Version number of runtime code.

• Role – Shows that this switch is operating as Master (i.e., operating stand-alone).

2-30

Page 61

ISPLAYING SWITCH HARDWARE/SOFTWARE VERSIONS

Web – Click System, Switch Information.

CLI – Use the following command to display version information.

Console#show version 3-49 Unit1

Serial number :A217056372 Service tag :[NONE] Hardware version :R0C Number of ports :24 Main power status :up Redundant power status :not present

Agent(master)

Unit id :1 Loader version :1.0.0.0 Boot rom version :1.0.0.0 Operation code version :2.0.0.19

Console#

2-31

Page 62

ONFIGURING THE SWITCH

Port Configuration

Displaying Connection Status

You can use the Port Information or Trunk Information pages to display the current connection status, including link state, speed/duplex mode, flow control, and auto-negotiation.

Command Attributes

• Name – Interface label.

• Type – Indicates the of port type (1000Base-TX or 1000Base-SFP).

• Admin Status – Shows if the interface is enabled or disabled.

• Oper Status – Indicates if the link is Up or Down.

• Speed/Duplex Status – Shows the current speed and duplex mode.

• Flow Control Status – Indicates the type of flow control currently in use.

• Autonegotiation – Shows if auto-negotiation is enabled or disabled.

• Trunk Member – Shows if port is a trunk member. (Port Information only.)

• Creation – Shows if a trunk is manually configured or dynamically set via LACP. (Trunk Information only.)

2-32

Page 63

ORT CONFIGURATION

Web – Click Port, Port Information or Trunk Information. Modify the required interface settings, and click Apply.

CLI – This example shows the connection status for Port 13.

Console#show interfaces status ethernet 1/13 3-95 Information of Eth 1/13

Basic information:

Port type: 1000T Mac address: 00-00-11-11-22-2F

Configuration:

Name: Port admin: Up Speed-duplex: Auto Capabilities: 10half, 10full, 100half, 100full, 1000full, Broadcast storm: Enabled Broadcast storm limit: 256 packets/second Flow control: Disabled Lacp: Disabled Port security: Disabled Port security action: None

Current status:

Link status: Down Operation speed-duplex: 1000full Flow control type: None

Console#

2-33

Page 64

ONFIGURING THE SWITCH

Configuring Interface Connections

You can use the Trunk Configuration or Port Configuration page to enable/disable an interface, manually fix the speed and duplex mode, set flow control, set auto-negotiation, and set the interface capabilities to advertise.

Command Attributes

• Name – Allows you to label an interface. (Range: 1-64 characters)

• Admin – Allows you to manually disable an interface. You can disable an interface due to abnormal behavior (e.g., excessive collisions), and then reenable it after the problem has been resolved. You may also disable an interface for security reasons.

• Speed/Duplex – Allows manual selection of port speed and duplex mode (i.e., with auto-negotiation disabled).

• Flow Control – Allows automatic or manual selection of flow control.

• Autonegotiation/Port Capabilities – Allows auto-negotiation to be enabled/disabled. Specifies the capabilities to be advertised for a port during auto-negotiation. The following capabilities are supported.

- 10half - Supports 10 Mbps half-duplex operation

- 10full - Supports 10 Mbps full-duplex operation

- 100half - Supports 100 Mbps half-duplex operation

- 100full - Supports 100 Mbps full-duplex operation

- 1000full - Supports 1000 Mbps full-duplex operation

- Sym (Gigabit only) – Check this item to transmit and receive pause frames, or clear it to auto-negotiate the sender and receiver for asymmetric pause frames.(The current switch chip only supports symmetric pause frames.)

- FC - Supports flow control. Flow control can eliminate frame loss by “blocking” traffic from end stations or segments connected directly to the switch when its buffers fill. When enabled, back pressure is

2-34

Page 65

ORT CONFIGURATION

used for half-duplex operation and IEEE 802.3x for full-duplex operation. (Avoid using flow control on a port connected to a hub unless it is actually required to solve a problem. Otherwise back pressure jamming signals may degrade overall performance for the segment attached to the hub.)

- (Default: Autonegotiation enabled; Advertised capabilities for

100BASE-TX – 10half, 10full, 100half, 100full; 1000BASE-T – 10half, 10full, 100half, 100full, 1000full; 1000BASE-SX/LX/LH – 1000full)

• Trunk – Indicates if a port is a member of a trunk. To create trunks and select port members, see “Port Trunk Configuration” on page 2-88.

Note: Autonegotiation must be disabled before you can configure or

force the interface to use the Speed/Duplex Mode or Flow Control options.

Web – Click Port, Port Configuration or Trunk Configuration. Modify the required interface settings, and click Apply.

2-35

Page 66

ONFIGURING THE SWITCH

CLI – Select the interface, and then enter the required settings.

Console(config)#interface ethernet 1/13 3-85 Console(config-if)#description RD SW#13 3-86 Console(config-if)#shutdown 3-91 . Console(config-if)#no shutdown Console(config-if)#no negotiation 3-88 Console(config-if)#speed-duplex 100half 3-86 Console(config-if)#flowcontrol 3-90 . Console(config-if)#negotiation Console(config-if)#capabilities 100half 3-89 Console(config-if)#capabilities 100full Console(config-if)#capabilities flowcontrol

Setting Broadcast Storm Thresholds

Broadcast storms may occur when a device on your network is malfunctioning, or if application programs are not well designed or properly configured. If there is too much broadcast traffic on your network, performance can be severely degraded or everything can come to complete halt.

You can protect your network from broadcast storms by setting a threshold for broadcast traffic for each port. Any broadcast packets exceeding the specified threshold will then be dropped.

Command Usage

• Broadcast Storm Control is enabled by default.

• The default threshold is 500 packets per second.

• Broadcast control does not effect IP multicast traffic.

• The specified threshold applies to all ports on the switch.

Command Attributes

• Threshold – Threshold as percentage of port bandwidth. (Options:

2-36

Page 67

ORT CONFIGURATION

500-262143

packets per second; Default: 500 packets per second)

• Broadcast Control Status – Shows whether or not broadcast storm control

has been enabled. (Default: Enabled)

Web – Click Port, Port Broadcast Control. Set the threshold for all ports, and then click Apply.

CLI – Specify the required interface, and then enter the threshold. The following sets broadcast suppression at 128 packets per second on port 1.

Console(config)#interface ethernet 1/1 3-85 Console(config-if)#switchport broadcast packet-rate 128 3-92 Console(config-if)#

2-37

Page 68

ONFIGURING THE SWITCH

Configuring Port Mirroring

You can mirror traffic from any source port to a target port for real-time analysis. You can then attach a logic analyzer or RMON probe to the target port and study the traffic crossing the source port in a completely unobtrusive manner.

Command Usage

• The mirror port and monitor port speeds must match, otherwise traffic may be dropped from the monitor port.

• The switch supports only one port mirror session.

• The source and target port have to be either both in the port group of 1 to 12 or both in the port group of 13 to 24.

Web – Click Port, Mirror. Specify the source port, the traffic type to be mirrored, and the target port, then click Add.

CLI – Use the interface command to select the target port, then use the port monitor command to specify the source port. Note that default mirroring under the CLI is for both received and transmitted packets.

2-38

Page 69

ORT CONFIGURATION

Console(config)#interface ethernet 1/10 3-85 Console(config-if)#port monitor ethernet 1/11 3-163 Console(config-if)#

Configuring Port Security

Port security is a feature that allows you to configure a switch port with one or more device MAC addresses that are authorized to access the network through that port.

When port security is enabled on a port, the switch stops learning new MAC addresses on the specified port. Only incoming traffic with source addresses already stored in the dynamic or static address table will be accepted as authorized to access the network through that port. If a device with an unauthorized MAC address attempts to use the switch port, the intrusion will be detected and the switch can automatically take action by disabling the port and sending a trap message.

To use port security, first allow the switch to dynamically learn the <source MAC address, VLAN> pair for frames received on a port for an initial period, and then enable port security to stop address learning. Be sure you enable the learning function long enough to ensure that all valid VLAN members have been registered on the selected port.

Note that a secure port has the following restrictions:

• It should not be connected to a network interconnection device.

• It cannot be configured as a member of a static trunk.

• It can be configured as an LACP trunk port, but the switch does not allow the LACP trunk to be enabled.

Note: A port that is already configured as an LACP or static trunk port

cannot be enabled as a secure port.

2-39

Page 70

ONFIGURING THE SWITCH

Port Security Action

The switch allows you to set the security action to be taken when a port intrusion is detected. This setting applies to all ports on the switch.

• Shutdown and Trap — Indicates the action to be taken when a port security violation is detected:

- None: Indicates that no action should be taken. (This is the default.)

- Trap and Shutdown: Indicates that the port is to be disabled and an SNMP trap message sent.

Web – Click Port, Port Security Action. Specify the security action for a port intrusion, then click Apply.

Port Security Configuration

On the Port, Port Security Status page, you can enable/disable security for any switch port. For each port number listed in the “Port” column, you can configure the following parameter:

• Security Status — Enables or disables port security on the port. (Default: disabled)

Note: If a port is disabled due to a security violation, it must be manually

re-enabled from the Port/Port Configuration page.

Web – Click Port, Port Security Status. Check the checkbox in the “Security Status” column to enable security for a port, then click Apply.

2-40

Page 71

DDRESS TABLE SETTINGS

CLI Configuration

Use the interface command to select the target port, then use the port security action command to configure the port intrusion action (applies

to all ports). Use the port security command to enable security for the port.

Console(config)#interface ethernet 1/5 Console(config-if)#port security action trap-and-shutdown 3-93 Console(config-if)#port security Console(config-if)#

Address Table Settings

Switches store the addresses for all known devices. This information is used to route traffic directly between the inbound and outbound ports. All the addresses learned by monitoring traffic are stored in the dynamic address table. You can also manually configure static addresses that are bound to a specific port.

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

2-41

Page 72

ONFIGURING THE SWITCH

Command Usage

Entries specified via the Web interface are permanent. Entries specified via the CLI can be made permanent or can be set to be deleted on reset.

Web – Click Address Table, Static Addresses. Specify the interface, the MAC address and VLAN, then click “Add Static Address.”

CLI – This example adds an address to the static address table, but sets it to be deleted when the switch is reset.

Console(config)#mac-address-table address 00-e0-29-94-34-de ethernet 1/1 vlan 1 delete-on-reset 3-100 Console(config)#

Displaying the Address Table

The Dynamic Address Table contains the MAC addresses learned by monitoring the source address for traffic entering the switch. When the destination address for inbound traffic is found in the database, the packets intended for that address is forwarded directly to the associated port. Otherwise, the traffic is flooded to all ports.

2-42

Page 73

DDRESS TABLE SETTINGS

Command Usage

• You can display entries in the dynamic address table by selecting an interface (either port or trunk), MAC address, or VLAN.

• You can sort the information displayed based on interface (port or trunk), MAC address, or VLAN.

Web – Click Address Table, Dynamic Addresses. Specify the search type (i.e., Interface, MAC Address, or VLAN), the method of sorting the displayed addresses, then click Query.

For example, the following screen shows the dynamic addresses for port 5.

CLI – This example displays the address table entries for port 11.

Console#show mac-address-table interface ethernet 1/11 3-102

Interface Mac Address Vlan Type

--------- ----------------- ---- ----------------Eth 1/11 00-10-b5-62-03-74 1 Learned

Console#

2-43

Page 74

ONFIGURING THE SWITCH

Changing the Aging Time

You can set the aging time for entries in the dynamic address table.

Command Usage

The range for the aging time is 17 - 2184 seconds. (The default is 300 seconds.)

Web – Click Address Table, Address Aging. Specify the new aging time, then click Apply.

CLI – This example sets the aging time to 400 seconds.

Console(config)#mac-address-table aging-time 400 3-103 Console(config)#

Spanning Tree Protocol Configuration

The Spanning Tree Protocol (STP) can be used to detect and disable network loops, and to provide backup links between switches, bridges or routers. This allows the switch to interact with other bridging devices (i.e., an STP-compliant switch, bridge or router) in your network to ensure that only one route exists between any two stations on the network, and provide backup links that automatically take over when a primary link goes down.

2-44

Page 75

PANNING TREE PROTOCOL CONFIGURATION

The Spanning Tree Protocols supported by the switch include the following standards:

• STP – Spanning Tree Protocol (IEEE 802.1D).

• RSTP – Rapid Spanning Tree Protocol (IEEE 802.1w).

STP uses a distributed algorithm to select a bridging device (STP-compliant switch, bridge or router) that serves as the root of the spanning tree network. It selects a root port on each bridging device (except for the root device) which incurs the lowest path cost when forwarding a packet from that device to the root device. Then it selects a designated bridging device from each LAN which incurs the lowest path cost when forwarding a packet from that LAN to the root device. All ports connected to designated bridging devices are assigned as designated ports. After determining the lowest cost spanning tree, it enables all root ports and designated ports, and disables all other ports. Network packets are therefore only forwarded between root ports and designated ports, eliminating any possible network loops.

Once a stable network topology has been established, all bridges listen for Hello BPDUs (Bridge Protocol Data Units) transmitted from the Root Bridge. If a bridge does not get a Hello BPDU after a predefined interval (Maximum Age), the bridge assumes that the link to the Root Bridge is down. This bridge will then initiate negotiations with other bridges to reconfigure the network to reestablish a valid network topology.

RSTP is designed as a general replacement for the slower, legacy STP. RSTP achieves much faster reconfiguration (around one tenth of that required by STP) by reducing the number of state changes before active ports start learning, predefining an alternate route that can be used when a node or port fails, and retaining the forwarding database for ports insensitive to changes in the tree structure when reconfiguration occurs.

2-45

Page 76

ONFIGURING THE SWITCH

STP Information

The Spanning Tree, STP Information page contains information on the current status of the Spanning Tree.

Command Attributes

• Spanning Tree State — Indicates if the Spanning Tree Protocol is currently enabled on the switch.

• Bridge ID — Identifies a unique identifier for the switch in the Spanning Tree. The ID is calculated using the defined Spanning Tree priority of the switch and its MAC address. The lower the Bridge ID, the more likely the switch will act as the root.

• Max Age — The maximum time (in seconds) the switch can wait without receiving a configuration message before attempting to reconfigure. All device ports (except for designated ports) should receive configuration messages at regular intervals. If the root port ages out STP information (provided in the last configuration message), a new root port is selected from among the device ports attached to the network. (References to “ports” in this section means “interfaces,” which includes both ports and trunks.)

• Hello Time — Specifies the time interval (in seconds) at which the root device transmits a configuration message.

• Forward Delay — The maximum time (in seconds) the switch will wait before changing states (i.e., discarding to learning to forwarding). This delay is required because every device must receive information about topology changes before it starts to forward frames. In addition, each port needs time to listen for conflicting information that would make it return to a discarding state; otherwise, temporary data loops might result.

2-46

Page 77

PANNING TREE PROTOCOL CONFIGURATION

• Designated Root — Identifies the priority and MAC address of the device in the Spanning Tree that the switch has accepted as the root device.

- Root Port — Specifies the port number on the switch that is closest

to the root. The switch communicates with the root device through this port. If there is no root port, the switch has been accepted as the root device of the Spanning Tree network.

- Root Path Cost — Identifies the path cost from the root port on

the switch to the root device.

• Root Hello Time* – Interval (in seconds) at which this device transmits a configuration message.

• Root Maximum Age* – The maximum time (in seconds) this device can wait without receiving a configuration message before attempting to reconfigure. All device ports (except for designated ports) should receive configuration messages at regular intervals. If the root port ages out STA information (provided in the last configuration message), a new root port is selected from among the device ports attached to the network. (References to “ports” in this section means “interfaces,” which includes both ports and trunks.)

• Root Forward Delay* – The maximum time (in seconds) this device will wait before changing states (i.e., discarding to learning to forwarding). This delay is required because every device must receive information about topology changes before it starts to forward frames. In addition, each port needs time to listen for conflicting information that would make it return to a discarding state; otherwise, temporary data loops might result.

• Configuration Changes — Specifies the number of times the Spanning Tree has been reconfigured.

• Last Topology Change — Identifies the time since the Spanning Tree was last reconfigured.

2-47

Page 78

ONFIGURING THE SWITCH

* CLI only.

Web – Click Spanning Tree, STP Information to display current Spanning Tree information.

2-48

Page 79

PANNING TREE PROTOCOL CONFIGURATION

CLI – This example shows the current Spanning Tree settings.

Console#show spanning-tree 3-119 Spanning-tree information

--------------------------------------------------------------Spanning tree mode :RSTP Spanning tree enable/disable :enable Priority :32768 Bridge Hello Time (sec.) :2 Bridge Max Age (sec.) :20 Bridge Forward Delay (sec.) :15 Root Hello Time (sec.) :2 Root Max Age (sec.) :20 Root Forward Delay (sec.) :15 Designated Root :32768.000011112222 Current root port :0 Current root cost :0 Number of topology changes :1 Last topology changes time (sec.):10811 Transmission limit :3 Path Cost Method :long

---------------------------------------------------------------

Eth 1/ 1 information

--------------------------------------------------------------Admin status : enable Role : disable State : discarding Path cost : 10000 Priority : 128 Designated cost : 0 Designated port : 128.1 Designated root : 32768.000011112222 Designated bridge : 32768.000011112222 Fast forwarding : disable Forward transitions : 0 Admin edge port : disable Oper edge port : disable Admin Link type : auto Oper Link type : point-to-point

Eth 1/ 2 information

--------------------------------------------------------------Admin status : enable Role : disable State : discarding Path cost : 10000

Console#

2-49

Page 80

ONFIGURING THE SWITCH

STP Configuration

Global settings apply to the entire switch.

Command Usage

RSTP supports connections to either STP or RSTP nodes by monitoring the incoming protocol messages and dynamically adjusting the type of protocol messages the RSTP node transmits, as described below:

• STP Mode – If the switch receives an 802.1D BPDU (i.e., STP BPDU) after a port’s migration delay timer expires, the switch assumes it is connected to an 802.1D bridge and starts using only 802.1D BPDUs.

• RSTP Mode – If RSTP is using 802.1D BPDUs on a port and receives an RSTP BPDU after the migration delay expires, RSTP restarts the migration delay timer and begins using RSTP BPDUs on that port.

Command Attributes

• Spanning Tree State — Enables or disables the Spanning Tree. If you enable the Spanning Tree, you must complete the other fields. (Default: enabled)

• Spanning Tree Type — Specifies the type of Spanning Tree Protocol used on the switch: (Default: RSTP)

• STP: Spanning Tree Protocol (IEEE 802.1D; i.e., when this

option is selected, the switch will use RSTP set to STP forced compatibility mode))

• RSTP: Rapid Spanning Tree (IEEE 802.1w)

• Priority — Bridge priority is used in selecting the root device, root port, and designated port. The device with the highest priority becomes the STP root device. However, if all devices have the same

2-50

Page 81

PANNING TREE PROTOCOL CONFIGURATION

priority, the device with the lowest MAC address will then become the root device.

- Default: 32768

- Range: 0-61440, in steps of 4096

- Options: 0, 4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, 61440

• Hello Time — Interval (in seconds) at which the switch transmits a configuration message.

- Default: 2

- Minimum: 1

- Maximum: The lower of 10 or [(Max. Message Age / 2) -1]

• Maximum Age — The maximum time (in seconds) the switch can wait without receiving a configuration message before attempting to reconfigure. All device ports (except for designated ports) should receive configuration messages at regular intervals. Any port that ages out STP information (provided in the last configuration message) becomes the designated port for the attached LAN. If it is a root port, a new root port is selected from among the device ports attached to the network. (References to “ports” in this section means “interfaces,” which includes both ports and trunks.)

- Default: 20

- Minimum: The higher of 6 or [2 x (Hello Time + 1)].

- Maximum: The lower of 40 or [2 x (Forward Delay - 1)]

2-51

Page 82

ONFIGURING THE SWITCH

- Default: 15

- Minimum: The higher of 4 or [(Max. Message Age / 2) + 1]

- Maximum: 30

• Path Cost Method — The path cost is used to determine the best path between devices. The path cost method is used to determine the range of values that can be assigned to each interface.

- Long: Specifies 32-bit based values that range from 1-200,000,000.

- Short: Specifies 16-bit based values that range from 1-65535. (This is the default.)

• Transmission Limit — The maximum transmission rate for BPDUs is specified by setting the minimum interval between the transmission of consecutive protocol messages. (Range: 1-10; Default: 3)

2-52

Page 83

PANNING TREE PROTOCOL CONFIGURATION

Web – Click Spanning Tree, STP Configuration. Modify the required attributes, then click Apply.

CLI – This example enables Spanning Tree Protocol, and then sets the indicated attributes.

Console(config)#spanning-tree mode rstp 3-107 Console(config)#spanning-tree 3-106 Console(config)#spanning-tree forward-time 15 3-108 Console(config)#spanning-tree hello-time 2 3-109 Console(config)#spanning-tree max-age 20 3-109 Console(config)#spanning-tree priority 40000 3-110 Console(config)#spanning-tree pathcost method long 3-111 Console(config)#spanning-tree transmission-limit 5 3-112 Console(config)#

2-53

Page 84

ONFIGURING THE SWITCH

STP Port and Trunk Information

The Spanning Tree, STP Port Information and Spanning Tree, STP Trunk Information display the current status of ports and trunks in the Spanning Tree.

Command Attributes

• STP Status — Displays current state of this port within the Spanning Tree:

- Discarding — Port receives STP configuration messages, but does not forward packets.

- Learning — Port has transmitted configuration messages for an interval set by the Forward Delay parameter without receiving contradictory information. Port address table is cleared, and the port begins learning addresses.

- Forwarding — Port forwards packets, and continues learning addresses.

The rules defining port status are:

- A port on a network segment with no other STA compliant bridging device is always forwarding.

- If two ports of a switch are connected to the same segment and there is no other STA device attached to this segment, the port with the smaller ID forwards packets and the other is discarding.

- All ports are discarding when the switch is booted, then some of them change state to learning, and then to forwarding.

• Forward Transitions – The number of times this port has transitioned from the Learning state to the Forwarding state.

• Designated Cost — The cost for a packet to travel from this port to the root in the current Spanning Tree configuration. The slower the media, the higher the cost.

2-54

Page 85

PANNING TREE PROTOCOL CONFIGURATION

• Designated Bridge — The priority and MAC address of the device through which this port must communicate to reach the root of the Spanning Tree.

• Designated Port — The priority and number of the port on the designated bridging device through which this switch must communicate with the root of the Spanning Tree.

• Oper Link Type – The operational point-to-point status of the LAN segment attached to this interface. This parameter is determined by manual configuration or by auto-detection, as described for “Admin Link Type” in the STP Port/Trunk Configuration page.

• Oper Edge Port – This parameter is initialized to the setting for “Admin Edge Port” in the STP Port/Trunk Configuration page (i.e., true or false), but will be set to false if a BPDU is received, indicating that another bridge is attached to this port.

• Port Role – Roles are assigned according to whether the port is part of the active Spanning Tree topology:

- Root: The port is connecting the bridge to the root bridge.

- Designated: The port is connecting a LAN through the bridge to the root bridge.

- Alternate or Backup: A port that may provide connectivity if other bridges, bridge ports, or LANs fail or are removed.

- Disabled: The role is set to disabled if a port has no role within the Spanning Tree.

• Trunk Member — Indicates whether the port is configured as a trunk member. (STP Port Information page only)

These additional parameters are only displayed for the CLI:

• Admin status – Shows if STA has been enabled on this interface.

2-55

Page 86

ONFIGURING THE SWITCH

• Path Cost – This parameter is used by the STA to determine the best path between devices. Therefore, lower values should be assigned to ports attached to faster media, and higher values assigned to ports with slower media. (Path cost takes precedence over port priority.)

• Priority – Defines the priority used for this port in the Spanning Tree Algorithm. If the path cost for all ports on a switch is the same, the port with the highest priority (i.e., lowest value) will be configured as an active link in the Spanning Tree. This makes a port with higher priority less likely to be blocked if the Spanning Tree Algorithm is detecting network loops. Where more than one port is assigned the highest priority, the port with the lowest numeric identifier will be enabled.

• Designated root – The priority and MAC address of the device in the Spanning Tree that this switch has accepted as the root device.

• Fast forwarding – This field provides the same information as Admin Edge port, and is only included for backward compatibility with earlier products.

• Admin Link Type – The link type attached to this interface.

• Point-to-Point – A connection to exactly one other bridge.

• Shared – A connection to two or more bridges.

• Auto – The switch automatically determines if the interface is attached to a point-to-point link or to shared media.

• Admin Edge Port – You can enable this option if an interface is attached to a LAN segment that is at the end of a bridged LAN or to an end node. Since end nodes cannot cause forwarding loops, they can pass directly through to the spanning tree forwarding state. Specifying Edge Ports provides quicker convergence for devices such as workstations or servers, retains the current forwarding database to reduce the amount of frame flooding required to rebuild address tables

2-56

Page 87

PANNING TREE PROTOCOL CONFIGURATION

during reconfiguration events, does not cause the spanning tree to reconfigure when the interface changes state, and also overcomes other STA-related timeout problems. However, remember that Edge Port should only be enabled for ports connected to an end-node device.

Web – Click Spanning Tree, STP Port Information or Spanning Tree, STP Trunk Information.

2-57

Page 88

ONFIGURING THE SWITCH

CLI – This example displys the current Spanning Tree status of a port.

Console#show spanning-tree ethernet 1/5 3-119 Eth 1/ 5 information

-------------------------------------------------------------Admin status : enable Role : designate State : forwarding Path cost : 100000 Priority : 128 Designated cost : 0 Designated port : 128.5 Designated root : 32768.000011112222 Designated bridge : 32768.000011112222 Fast forwarding : disable Forward transitions : 1 Admin edge port : disable Oper edge port : disable Admin Link type : auto Oper Link type : point-to-point

Console#

STP Port and Trunk Configuration

You can configure RSTP attributes for specific interfaces, including port priority, path cost, link type, and edge port. You may use a different priority or path cost for ports of same media type to indicate the preferred path, link type to indicate a point-to-point connection or shared-media connection, and edge port to indicate if the attached device can support fast forwarding. (References to “ports” in this section means “interfaces,” which includes both ports and trunks.)

Command Attributes

• STP State — Displays current state of this port within the Spanning Tree:

- Discarding — Port receives STP configuration messages, but does not forward packets.

- Learning — Port has transmitted configuration messages for an interval set by the Forward Delay parameter without receiving contradictory information. Port address table is cleared, and the port

2-58

Page 89

PANNING TREE PROTOCOL CONFIGURATION

begins learning addresses.

- Forwarding — Port forwards packets, and continues learning

addresses.

• Priority — Defines the priority used for this port in the Spanning Tree Protocol. If the path cost for all ports on a switch is the same, the port with the highest priority (i.e., lowest value) will be configured as an active link in the Spanning Tree. This makes a port with higher priority less likely to be blocked if the Spanning Tree Protocol is detecting network loops. Where more than one port is assigned the highest priority, the port with lowest numeric identifier will be enabled. (Default: 128; Range: 0-240, in steps of 16)

• Path Cost — This parameter is used by the STP to determine the best path between devices. Therefore, lower values should be assigned to ports attached to faster media, and higher values assigned to ports with slower media. (Path cost takes precedence over port priority.)

- Range — Ethernet: 200,000-20,000,000 Fast Ethernet: 20,000-2,000,000 Gigabit Ethernet: 2,000-200,000

- Defaults — Ethernet — half duplex: 2,000,000; full duplex: 1,000,000; trunk: 500,000 Fast Ethernet — half duplex: 200,000; full duplex: 100,000; trunk: 50,000 Gigabit Ethernet — full duplex: 10,000; trunk: 5,000

Note: When the Path Cost Method is set to short, the maximum path

cost is 65,535.

• Admin Link Type — The link type attached to this interface. (Default: Auto)

- Point-to-Point — A connection to exactly one other bridge.

- Shared — A connection to two or more bridges.

2-59

Page 90

ONFIGURING THE SWITCH

- Auto — The switch automatically determines if the interface is attached to a point-to-point link or to shared media.

• Admin Edge Port — You can enable this option if an interface is attached to a LAN segment that is at the end of a bridged LAN or to an end node. Since end nodes cannot cause forwarding loops, they can pass directly through to the Spanning Tree forwarding state. Specifying Edge Ports provides quicker convergence for devices such as workstations or servers, retains the current forwarding database to reduce the amount of frame flooding required to rebuild address tables during reconfiguration events, does not cause the Spanning Tree to initiate reconfiguration when the interface changes state, and also overcomes other STP-related timeout problems. However, remember that Edge Port should only be enabled for ports connected to an end-node device.

• Migration — Re-checks the appropriate BPDU format to send on the selected interface. If at any time the switch detects STP BPDUs, including Configuration or Topology Change Notification BPDUs, it will automatically set the selected interface to forced STP-compatible mode. However, you can also check this Migration check box to manually re-check the appropriate BPDU format (RSTP or STP-compatible) to send on the selected interfaces.

• Trunk – Specifies if a port is member of a trunk.

2-60

Page 91

VLAN C

ONFIGURATION

Web – Click Spanning Tree, STP Port Configuration or STP Trunk Configuration. Modify the required attributes, then click Apply.

CLI – This example sets STP attributes for port 5.

Console(config)#interface ethernet 1/5 Console(config-if)#spanning-tree port-priority 128 3-114 Console(config-if)#spanning-tree cost 19 3-113 Console(config-if)#spanning-tree link-type auto 3-118 Console(config-if)#no spanning-tree edge-port 3-116 Console#spanning-tree protocol-migration ethernet 1/5 3- 117 Console#

VLAN Configuration

In conventional networks with routers, broadcast traffic is split up into separate domains. Switches do not inherently support broadcast domains. This can lead to broadcast storms in large networks that handle traffic such as IPX or NetBEUI. By using IEEE 802.1Q-compliant VLANs, you can organize any group of network nodes into separate broadcast domains, thus confining broadcast traffic to the originating group. This also provides a more secure and cleaner network environment.

2-61

Page 92

ONFIGURING THE SWITCH

An IEEE 802.1Q VLAN is a group of ports that can be located anywhere in the network, but communicate as though they belong to the same physical segment.

VLANs help to simplify network management by allowing you to move devices to a new VLAN without having to change any physical connections. VLANs can be easily organized to reflect departmental groups (such as Marketing or R&D), usage groups (such as e-mail), or multicast groups (used for multimedia applications such as videoconferencing).

VLANs provide greater network efficiency by reducing broadcast traffic, and allow you to make network changes without having to update IP addresses or IP subnets. VLANs inherently provide a high level of network security since traffic must pass through a configured Layer 3 link to reach a different VLAN.

• Up to 255 VLANs based on the IEEE 802.1Q standard

• Distributed VLAN learning across multiple switches using explicit or implicit tagging and GVRP protocol

• Port overlapping, allowing a port to participate in multiple VLANs

• End stations can belong to multiple VLANs

• Passing traffic between VLAN-aware and VLAN-unaware devices

• Priority tagging

Assigning Ports to VLANs

Before enabling VLANs for the switch, you must first assign each port to the VLAN group(s) in which it will participate. By default all ports are assigned to VLAN 1 as untagged ports. Add a port as a tagged port if you want it to carry traffic for one or more VLANs, and any intermediate network devices or the host at the other end of the connection supports VLANs. Then assign ports on the other VLAN-aware network devices

2-62

Page 93

VLAN C

along the path that will carry this traffic to the same VLAN(s), either manually or dynamically using GVRP. However, if you want a port on this switch to participate in one or more VLANs, but none of the intermediate network devices nor the host at the other end of the connection supports VLANs, then you should add this port to the VLAN as an untagged port.

Note: VLAN-tagged frames can pass through VLAN-aware or

VLAN-unaware network interconnection devices, but the VLAN tags should be stripped off before passing it on to any end-node host that does not support VLAN tagging.

VLAN Classification – When the switch receives a frame, it classifies the frame in one of two ways. If the frame is untagged, the switch assigns the frame to an associated VLAN (based on the PVID of the receiving port. But if the frame is tagged, the switch uses the tagged VLAN ID to identify the port broadcast domain of the frame.

Port Overlapping – Port overlapping can be used to allow access to commonly shared network resources among different VLAN groups, such as file servers or printers. Note that if you implement VLANs which do not overlap, but still need to communicate, you can connect them by using a Layer-3 router or switch.

ONFIGURATION

Untagged VLANs – Untagged VLANs – Untagged (or static) VLANs are typically used to reduce broadcast traffic and to increase security. A group of network users assigned to a VLAN form a broadcast domain that is separate from other VLANs configured on the switch. Packets are forwarded only between ports that are designated for the same VLAN. Untagged VLANs can be used to manually isolate user groups or subnets. However, you should use IEEE 802.3 tagged VLANs with GVRP whenever possible to fully automate VLAN registration.

Automatic VLAN Registration – GVRP (GARP VLAN Registration Protocol) defines a system whereby the switch can automatically learn the VLANs to which each endstation should be assigned. If an endstation (or its network adapter) supports the IEEE 802.1Q VLAN protocol, it can be

2-63

Page 94

ONFIGURING THE SWITCH

configured to broadcast a message to your network indicating the VLAN groups it wants to join. When this switch receives these messages, it will automatically place the receiving port in the specified VLANs, and then forward the message to all other ports. When the message arrives at another switch that supports GVRP, it will also place the receiving port in the specified VLANs, and pass the message on to all other ports. VLAN requirements are propagated in this way throughout the network. This allows GVRP-compliant devices to be automatically configured for VLAN groups based solely on endstation requests.

To implement GVRP in a network, first add the host devices to the required VLANs (using the operating system or other application software), so that these VLANs can be propagated onto the network. For both the edge switches attached directly to these hosts, and core switches in the network, enable GVRP on the links between these devices. You should also determine security boundaries in the network and disable GVRP on ports to prevent advertisements being propagated, or forbid ports from joining restricted VLANs.

Note: If you have host devices that do not support GVRP, you must

configure static VLANs for the switch ports connected to these devices. You also still need to enable GVRP on these edge switches, as well as on the core switches in the network.

Forwarding Tagged/Untagged Frames

If you want to create a small port-based VLAN for devices attached directly to a single switch, you can assign ports to the same untagged VLAN. However, to participate in a VLAN group that crosses several switches, you need to create a VLAN for that group and enable tagging on all ports.

Ports can be assigned to multiple tagged or untagged VLANs. Each port on the switch is therefore capable of passing tagged or untagged frames. When forwarding a frame from this switch along a path that contains any VLAN-aware devices, the switch should include VLAN tags. When

2-64

Page 95

VLAN C

forwarding a frame from this switch along a path that does not contain any VLAN-aware devices (including the destination host), the switch must first strip off the VLAN tag before forwarding the frame. When the switch receives a tagged frame, it will pass this frame onto the VLAN(s) indicated by the frame tag. However, when this switch receives an untagged frame from a VLAN-unaware device, it first decides where to forward the frame, and then inserts a VLAN tag reflecting the ingress port’s default VID..

Displaying Basic VLAN Information

Command Attributes

• VLAN Version Number – The VLAN version used by this switch as specified in the IEEE 802.1Q standard. (Web interface only.)

• Maximum VLAN ID – Maximum VLAN ID recognized by this switch.

• Maximum Number of Supported VLANs – Maximum number of VLANs that can be configured on this switch.

Web – Click VLAN, VLAN Basic Information.

ONFIGURATION

CLI – Enter the following command.

2-65

Page 96

ONFIGURING THE SWITCH

Console#show bridge-ext 3-137

Console#

Displaying Current VLANs

The VLAN Current Table shows the current port members of each VLAN and whether or not the port supports VLAN tagging. Ports assigned to a large VLAN group that crosses several switches should use VLAN tagging. However, if you just want to create a small port-based VLAN for one or two switches, you can disable tagging.

Command Attributes for Web Interface

• VLAN ID – ID of configured VLAN (1-4094, no leading zeroes).

• Up Time at Creation – Time this VLAN was created; i.e., System Up Time.

• Status – Shows how this VLAN was added to the switch.

- Dynamic GVRP: Automatically learned via GVRP.

- Permanent: Added as a static entry.

• Tagged Ports – Shows the tagged VLAN port members.

• Untagged Ports – Shows the untagged VLAN port members

2-66

Page 97

VLAN C

Web – Click VLAN, VLAN Current Table. Select any ID from the scroll-down list.

ONFIGURATION

Command Attributes for CLI Interface

• VLAN – ID of configured VLAN (1-4094, no leading zeroes).

• Type – Shows how this VLAN was added to the switch.

- Dynamic: Automatically learned via GVRP.

- Static: Added as a static entry.

• Name – Name of the VLAN (1 to 32 characters).

• Status – Shows if this VLAN is enabled or disabled.

- Active: VLAN is operational.

- Suspend: VLAN is suspended; i.e., does not pass packets.

2-67

Page 98

ONFIGURING THE SWITCH

• Ports / Channel groups – Shows the VLAN interface members.

CLI – Current VLAN information can be displayed with the following

command.

Console#show vlan id 1 3-131 VLAN Type Name Status Ports/Channel groups

---- ------- ---------------- --------- --------------------------------------1 Static DefaultVlan Active Eth1/ 1 Eth1/ 2 Eth1/ 3 Eth1/ 4 Eth1/ 5

Console#

Eth1/ 6 Eth1/ 7 Eth1/ 8 Eth1/ 9 Eth1/10 Eth1/11 Eth1/12 Eth1/13 Eth1/14 Eth1/15 Eth1/16 Eth1/17 Eth1/18 Eth1/19 Eth1/20

Eth1/21 Eth1/22 Eth1/23 Eth1/24

Creating VLANs

Use The VLAN Static List to create or remove VLAN groups. To propagate information about VLAN groups used on this switch to external network devices, you must specify a VLAN ID for each of these groups.

Command Attributes

• Current – Lists all the current VLAN groups created for this system. Up to 255 VLAN groups can be defined. VLAN 1 is the default untagged VLAN.

• New – Allows you to specify the name and numeric identifier for a new VLAN group. (The VLAN name is only used for management on this system; it is not added to the VLAN tag.)

• VLAN ID – ID of configured VLAN (1-4094, no leading zeroes).

• Name – Name of the VLAN (1 to 32 characters).

• Status – Shows if this VLAN is enabled or disabled (Web).

- Enable: VLAN is operational.

- Disable: VLAN is suspended; i.e., does not pass packets.

2-68

Page 99

VLAN C

ONFIGURATION

• State – Shows if this VLAN is enabled or disabled (CLI).

- Active: VLAN is operational.

- Suspend: VLAN is suspended; i.e., does not pass packets.

• Add – Adds a new VLAN group to the current list.

• Remove – Removes a VLAN group from the current list. If any port is assigned to this group as untagged, it will be reassigned to VLAN group 1 as untagged.

Web – Click VLAN, VLAN Static List. Enter the VLAN ID and VLAN name, mark the Enable checkbox to activate the VLAN, and then click Add.

CLI – This example creates a new VLAN.

Console(config)#vlan database 3-122 Console(config-vlan)#vlan 5 name R&D media ethernet state active 3-123 Console(config-vlan)#

2-69

Page 100

ONFIGURING THE SWITCH

Adding Interfaces Based on Membership Type

Use the VLAN Static Table to modify the settings for an existing VLAN. You can add or delete port members for a VLAN, disable or enable VLAN tagging for any port, or prevent a port from being automatically added to a VLAN via the GVRP protocol. (Note that VLAN 1 is the default untagged VLAN containing all ports on the switch, and cannot be modified via this page.)

You can use the VLAN Static Table to assign ports to the specified VLAN group as an IEEE 802.1Q tagged port. Assign ports as tagged if they are connected to 802.1Q VLAN-compliant devices. If the port is connected to VLAN-unaware devices, frames will be passed to the untagged VLAN group this port has been assigned to under the VLAN Port Configuration page.

Command Attributes

• Port – Port identifier.

• Trunk – Trunk identifier.

• VLAN – ID of configured VLAN (1-4094, no leading zeroes).

• Name – Name of the VLAN (1 to 32 characters).

• Status – Shows if this VLAN is enabled or disabled.

- Enable: VLAN is operational.

- Disable: VLAN is suspended; i.e., does not pass packets.

• Membership Type – Select VLAN membership for each interface by marking the appropriate radio button for a port or trunk:

- Tagged: Interface is a member of the VLAN. All packets

transmitted by the port will be tagged, that is, carry a tag and therefore carry VLAN or CoS information.

- Untagged: Interface is a member of the VLAN. All packets

transmitted by the port will be untagged, that is, not carry a tag and

2-70

SMC Networks TigerSwitch 100 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Connecting to the Switch

Configuration Options

Required Connections

Remote Connections

Basic Configuration

Console Connection

Setting Passwords

Setting an IP Address

Enabling SNMP Management Access

Saving Configuration Settings

Managing System Files

System Defaults

Using the Web Interface

Navigating the Web Browser Interface

Home Page

Configuration Options

Panel Display

Main Menu

Basic Configuration

Displaying System Information

Setting the IP Address

Security

Configuring the Logon Password

Configuring RADIUS/TACACS Logon Authentication

HTTPS

Managing Firmware

Downloading System Software from a Server

Saving or Restoring Configuration Settings

Copying the Running Configuration to a File

Displaying Bridge Extension Capabilities

Displaying Switch Hardware/Software Versions

Port Configuration

Displaying Connection Status

Configuring Interface Connections

Setting Broadcast Storm Thresholds

Configuring Port Mirroring

Configuring Port Security

Address Table Settings

Setting Static Addresses

Displaying the Address Table

Changing the Aging Time

Spanning Tree Protocol Configuration

STP Information

STP Configuration

STP Port and Trunk Information

STP Port and Trunk Configuration

VLAN Configuration

Assigning Ports to VLANs

Forwarding Tagged/Untagged Frames

Displaying Basic VLAN Information

Displaying Current VLANs

Creating VLANs

Adding Interfaces Based on Membership Type