Switch 4200G
Switch 4200G
Switch 4200G
Switch 4200G 12-Port Switch 4200G 24-Port Switch 4200G 48-Port Switch 4200G PWR 24-Port
Copyright 2006-2009, 3Com Corporation. All rights reserved. No part of this documentation may be reproduced in any form or by any means or used to make any derivative work (such as translation, transformation, or adaptation) without written permission from 3Com Corporation. 3Com Corporation reserves the right to revise this documentation and to make changes in content from time to time without obligation on the part of 3Com Corporation to provide notification of such revision or change. 3Com Corporation provides this documentation without warranty, term, or condition of any kind, either implied or expressed, including, but not limited to, the implied warranties, terms or conditions of merchantability, satisfactory quality, and fitness for a particular purpose. 3Com may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. If there is any software on removable media described in this documentation, it is furnished under a license agreement included with the product as a separate document, in the hard copy documentation, or on the removable media in a directory file named LICENSE.TXT or !LICENSE.TXT. If you are unable to locate a copy, please contact 3Com and a copy will be provided to you. UNITED STATES GOVERNMENT LEGEND If you are a United States government agency, then this documentation and the software described herein are provided to you subject to the following: All technical data and computer software are commercial in nature and developed solely at private expense. Software is delivered as Commercial Computer Software as defined in DFARS 252.227-7014 (June 1995) or as a commercial item as defined in FAR 2.101(a) and as such is provided with only such rights as are provided in 3Coms standard commercial license for the Software. Technical data is provided with limited rights only as provided in DFAR 252.227-7015 (Nov 1995) or FAR 52.227-14 (June 1987), whichever is applicable. You agree not to remove or deface any portion of any legend provided on any licensed program or documentation contained in, or delivered to you in conjunction with, this User Guide. Unless otherwise indicated, 3Com registered trademarks are registered in the United States and may or may not be registered in other countries. 3Com and the 3Com logo are registered trademarks of 3Com Corporation. All other company and product names may be trademarks of the respective companies with which they are associated.
ENVIRONMENTAL STATEMENT
It is the policy of 3Com Corporation to be environmentally-friendly in all operations. To uphold our policy, we are committed to: Establishing environmental performance standards that comply with national legislation and regulations. Conserving energy, materials and natural resources in all operations. Reducing the waste generated by all operations. Ensuring that all waste conforms to recognized environmental standards. Maximizing the recyclable and reusable content of all products. Ensuring that all products can be recycled, reused and disposed of safely. Ensuring that all products are labelled according to recognized environmental standards. Improving our environmental record on a continual basis.
Part 28 File System Management 29 FTP-SFTP-TFTP 30 Information Center 31 System Maintenance and Debugging 32 Remote-ping 33 PoE-PoE Profile 34 Smart Link-Monitor Link 35 IPv6 Management 36 UDP Helper 37 Access Management 38 Appendix
Contents Introduces basic configuration for file system management. Introduces basic configuration for FTP, SFTP and TFTP, and the applications. Introduces information center configuration. Introduces daily system maintenance and debugging. Introduces Remote-ping and the related configuration. Introduces PoE, PoE profile and the related configuration. Introduces Smart Link, Monitor Link and the related configuration. Introduces IPv6 and the related configuration. Introduces UDP helper and the related configuration. Introduces Access Management and the related configuration. Lists the acronyms used in this manual
Conventions
The manual uses the following conventions:
Command conventions
Convention Boldface italic [] { x | y | ... } [ x | y | ... ] { x | y | ... } * [ x | y | ... ] * &<1-n> # Description The keywords of a command line are in Boldface. Command arguments are in italic. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected. Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected. Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected. The argument(s) before the ampersand (&) sign can be entered 1 to n times. A line starting with the # sign is comments.
GUI conventions
Convention <> [] / Description Button names are inside angle brackets. For example, click <OK>. Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window. Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].
Symbols
Convention Description Means reader be extremely careful. Improper operation may cause bodily injury. Means reader be careful. Improper operation may cause data loss or damage to equipment. Means a complementary description.
Related Documentation
In addition to this manual, each 3com Switch 4200G documentation set includes the following: Manual 3Com Switch 4200G Family Command Reference Guide 3Com Switch 4200G Family Quick Reference Guide 3Com Switch 4200G Family Getting Started Guide 3Com Switch 4200G 10G Interface Module Installation Guide 3Com Switch 4200G Family Release Notes Description Provide detailed descriptions of command line interface (CLI) commands, that you require to manage your switch. Provide a summary of command line interface (CLI) commands that are required for you to manage your Stackable Switch. This guide provides all the information you need to install and use the 3Com Switch 4200G Family. Provide detailed descriptions of the 10G Interface Modules used by 3Com Switch 4200G Family. Contain the latest information about your product. If information in this guide differs from information in the release notes, use the information in the Release Notes.
Obtaining Documentation
You can access the most up-to-date 3Com product documentation on the World Wide Web at this URL: http://www.3com.com.
Table of Contents
1 Logging In to an Ethernet Switch 1-1 Logging In to an Ethernet Switch 1-1 Introduction to the User Interface1-1 Supported User Interfaces 1-1 Relationship Between a User and a User Interface 1-2 User Interface Index 1-2 Common User Interface Configuration1-2 2 Logging In Through the Console Port2-1 Introduction 2-1 Setting Up a Login Environment for Login Through the Console Port2-1 Console Port Login Configuration 2-3 Common Configuration2-3 Console Port Login Configurations for Different Authentication Modes 2-5 Console Port Login Configuration with Authentication Mode Being None2-6 Configuration Procedure2-6 Configuration Example 2-6 Console Port Login Configuration with Authentication Mode Being Password 2-7 Configuration Procedure2-7 Configuration Example 2-8 Console Port Login Configuration with Authentication Mode Being Scheme 2-9 Configuration Procedure2-9 Configuration Example 2-10 3 Logging In Through Telnet 3-1 Introduction 3-1 Common Configuration to Control Telnet Access 3-2 Telnet Configurations for Different Authentication Modes3-3 Telnet Configuration with Authentication Mode Being None 3-4 Configuration Procedure3-4 Configuration Example 3-4 Telnet Configuration with Authentication Mode Being Password 3-5 Configuration Procedure3-5 Configuration Example 3-6 Telnet Configuration with Authentication Mode Being Scheme3-7 Configuration Procedure3-7 Configuration Example 3-8 Telnetting to a Switch3-9 Telnetting to a Switch from a Terminal3-9 Telnetting to another Switch from the Current Switch3-11 4 Logging In Using a Modem4-1 Introduction 4-1 Configuration on the Switch Side4-1 Modem Configuration 4-1
i
Switch Configuration4-2 Modem Connection Establishment 4-2 5 CLI Configuration 5-1 Introduction to the CLI5-1 Command Hierarchy 5-1 Command Level and User Privilege Level 5-1 Modifying the Command Level5-2 Switching User Level 5-3 CLI Views 5-7 CLI Features 5-10 Online Help5-10 Terminal Display5-11 Command History5-12 Error Prompts 5-12 Command Edit5-13 6 Logging In Through the Web-based Network Management Interface 6-1 Introduction 6-1 Establishing an HTTP Connection 6-1 Configuring the Login Banner 6-2 Configuration Procedure6-2 Configuration Example 6-3 Enabling/Disabling the WEB Server 6-3 7 Logging In Through NMS7-1 Introduction 7-1 Connection Establishment Using NMS 7-1 8 Configuring Source IP Address for Telnet Service Packets 8-1 Overview 8-1 Configuring Source IP Address for Telnet Service Packets 8-1 Displaying Source IP Address Configuration8-2 9 User Control 9-1 Introduction 9-1 Controlling Telnet Users 9-1 Introduction9-1 Controlling Telnet Users by ACL 9-2 Configuration Example 9-3 Controlling Network Management Users by Source IP Addresses 9-3 Prerequisites9-4 Controlling Network Management Users by Source IP Addresses9-4 Configuration Example 9-4 Controlling Web Users by Source IP Address 9-5 Prerequisites9-5 Controlling Web Users by Source IP Addresses9-5 Logging Out a Web User 9-6 Configuration Example 9-6
ii
1
Logging In to an Ethernet Switch
Go to these sections for information you are interested in: Logging In to an Ethernet Switch Introduction to the User Interface
The auxiliary (AUX) port and the console port of a 3Com low-end and mid-range Ethernet switch are the same port (referred to as console port in the following part). You will be in the AUX user interface if you log in through this port.
Switch 4200G supports two types of user interfaces: AUX and VTY. AUX user interface: A view when you log in through the AUX port. AUX port is a line device port. Virtual type terminal (VTY) user interface: A view when you log in through VTY. VTY port is a logical terminal line used when you access the device by means of Telnet or SSH.
1-1
Table 1-1 Description on user interface User interface AUX Applicable user Users logging in through the console port Port used Console port Remarks Each switch can accommodate one AUX user. Each switch can accommodate up to five VTY users.
VTY
Ethernet port
One user interface corresponds to one user interface view, where you can configure a set of parameters, such as whether to authenticate users at login and the user level after login. When the user logs in through a user interface, the connection follows these parameter settings, thus implementing centralized management of various sessions.
1-2
To do
Remarks
lock
Specify to send messages to all user interfaces/a specified user interface Free a user interface Enter system view Set the banner Set a system name for the switch
Optional Available in user view Optional Available in user view Optional By default, no banner is configured Optional Optional
free user-interface [ type ] number system-view header [ incoming | legal | login | shell ] text sysname string
copyright-info enable
By default, copyright displaying is enabled. That is, the copy right information is displayed on the terminal after a user logs in successfully.
Enter user interface view Display the information about the current user interface/all user interfaces Display the physical attributes and configuration of the current/a specified user interface Display the information about the current web users
1-3
2
Logging In Through the Console Port
Go to these sections for information you are interested in: Introduction Setting Up a Login Environment for Login Through the Console Port Console Port Login Configuration Console Port Login Configuration with Authentication Mode Being None Console Port Login Configuration with Authentication Mode Being Password Console Port Login Configuration with Authentication Mode Being Scheme
Introduction
To log in through the console port is the most common way to log in to a switch. It is also the prerequisite to configure other login methods. By default, you can locally log in to Switch 4200G through its console port only. Table 2-1 lists the default settings of a console port. Table 2-1 The default settings of a console port Setting Baud rate Flow control Check mode (Parity) Stop bits Data bits 19,200 bps None None 1 8 Default
To log in to a switch through the console port, make sure the settings of both the console port and the user terminal are the same. After logging in to a switch, you can perform configuration for AUX users. Refer to Console Port Login Configuration for more.
2-1
2)
If you use a PC to connect to the console port, launch a terminal emulation utility (such as Terminal in Windows 3.X or HyperTerminal in Windows 9X/Windows 2000/Windows XP. The following assumes that you are running Windows XP) and perform the configuration shown in Figure 2-2 through Figure 2-4 for the connection to be created. Normally, both sides (that is, the serial port of the PC and the console port of the switch) are configured as those listed in Table 2-1.
2-2
3) 4)
Turn on the switch. You will be prompted to press the Enter key if the switch successfully completes POST (power-on self test). The prompt appears after you press the Enter key. You can then configure the switch or check the information about the switch by executing the corresponding commands. You can also acquire help by typing the ? character. Refer to related parts in this manual for information about the commands used for configuring the switch.
Data bits Configure the command level available to the users logging in to the AUX user interface Make terminal services available
Optional By default, commands of level 3 are available to the users logging in to the AUX user interface.
Terminal configuration
2-3
Configuration Set the maximum number of lines the screen can contain Set history command buffer size Set the timeout time of a user interface Optional
Remarks
By default, the screen can contain up to 24 lines. Optional By default, the history command buffer can contain up to 10 commands. Optional The default timeout time is 10 minutes.
The change to console port configuration takes effect immediately, so the connection may be disconnected when you log in through a console port and then configure this console port. To configure a console port, you are recommended to log in to the switch in other ways. To log in to a switch through its console port after you modify the console port settings, you need to modify the corresponding settings of the terminal emulation utility running on your PC accordingly in the dialog box shown in Figure 2-4.
Follow these steps to set common configuration of console port login: To do Enter system view Enter AUX user interface view Set the baud rate Use the command system-view user-interface aux 0 speed speed-value Optional The default baud rate of a console port is 19,200 bps. Optional Configure the console port Set the check mode parity { even | none | odd } By default, the check mode of a console port is none, that is, no check is performed. Optional The stop bits of a console port is 1. Optional Set the databits databits { 7 | 8 } The default databits of a console port is 8. Optional Configure the command level available to users logging in to the user interface user privilege level level By default, commands of level 3 are available to users logging in to the AUX user interface, and commands of level 0 are available to users logging in to the VTY user interface. Optional Enable terminal services shell By default, terminal services are available in all user interfaces. Remarks
stopbits { 1 | 1.5 | 2 }
2-4
To do
Remarks
screen-length screen-length
By default, the screen can contain up to 24 lines. You can use the screen-length 0 command to disable the function to display information in pages. Optional
The default history command buffer size is 10, that is, a history command buffer of a user can store up to 10 commands by default. Optional The default timeout time of a user interface is 10 minutes.
With the timeout time being 10 minutes, the connection to a user interface is terminated if no operation is performed in the user interface within 10 minutes. You can use the idle-timeout 0 command to disable the timeout function.
Set the authentication mode to local password authentication Password Set the password for local authentication Set the authentication mode to scheme Specify to perform local authentication or remote authentication Set user names and passwords locally or on AAA Server
Scheme
Refer to Console Port Login Configuration with Authentication Mode Being Scheme.
2-5
Changes made to the authentication mode for console port login takes effect after you quit the command-line interface and then log in again.
Configuration Example
Network requirements
Assume that the switch is configured to allow users to log in through Telnet, and the current user level is set to the administrator level (level 3). Perform the following configurations for users logging in through the console port (AUX user interface). Do not authenticate the users. Commands of level 2 are available to the users logging in to the AUX user interface. The baud rate of the console port is 19,200 bps. The screen can contain up to 30 lines. The history command buffer can contain up to 20 commands. The timeout time of the AUX user interface is 6 minutes.
2-6
Network diagram
Figure 2-5 Network diagram for AUX user interface configuration (with the authentication mode being none)
GE1/0/1 Ethernet
Configuration procedure
# Enter system view.
<Sysname> system-view
# Specify commands of level 2 are available to users logging in to the AUX user interface.
[Sysname-ui-aux0] user privilege level 2
# Set the maximum number of lines the screen can contain to 30.
[Sysname-ui-aux0] screen-length 30
# Set the maximum number of commands the history command buffer can store to 20.
[Sysname-ui-aux0] history-command max-size 20
After the above configuration, you need to modify the configuration of the terminal emulation utility running on the PC accordingly in the dialog box shown in Figure 2-4 to log in to the switch successfully.
2-7
Remarks
authentication-mode password
By default, users logging in to a switch through the console port are not authenticated; while those logging in through Modems or Telnet are authenticated. Required
Configuration Example
Network requirements
Assume the switch is configured to allow users to log in through Telnet, and the user level is set to the administrator level (level 3). Perform the following configurations for users logging in through the console port (AUX user interface). Authenticate the users using passwords. Set the local password to 123456 (in plain text). The commands of level 2 are available to the users. The baud rate of the console port is 19,200 bps. The screen can contain up to 30 lines. The history command buffer can store up to 20 commands. The timeout time of the AUX user interface is 6 minutes.
Network diagram
Figure 2-6 Network diagram for AUX user interface configuration (with the authentication mode being password)
GE1/0/1 Ethernet
Configuration procedure
# Enter system view.
2-8
<Sysname> system-view
# Specify to authenticate users logging in through the console port using the local password.
[Sysname-ui-aux0] authentication-mode password
# Specify commands of level 2 are available to users logging in to the AUX user interface.
[Sysname-ui-aux0] user privilege level 2
# Set the maximum number of lines the screen can contain to 30.
[Sysname-ui-aux0] screen-length 30
# Set the maximum number of commands the history command buffer can store to 20.
[Sysname-ui-aux0] history-command max-size 20
After the above configuration, you need to modify the configuration of the terminal emulation utility running on the PC accordingly in the dialog box shown in Figure 2-4 to log in to the switch successfully.
quit
2-9
To do Enter the default ISP domain view Specify the AAA scheme to be applied to the domain
Use the command Optional domain domain-name scheme { local | none | radius-scheme radius-scheme-name [ local ] | hwtacacs-scheme hwtacacs-scheme-name [ local ] }
Remarks
By default, the local AAA scheme is applied. If you specify to apply the local AAA scheme, you need to perform the configuration concerning local user as well. If you specify to apply a RADIUS or HWTACACS scheme, you need to perform the following configuration as well: Perform RADIUS and HWTACACS configuration on the switch. (Refer to the AAA part for more.) Configure the user name and password accordingly on the AAA server. (Refer to the user manual of AAA server.) Required No local user exists by default. Required Required
quit
Create a local user (Enter local user view.) Set the authentication password for the local user Specify the service type for AUX users
local-user user-name password { simple | cipher } password service-type terminal [ level level ]
Note that: If you configure to authenticate the users in the scheme mode, the command level available to users logging in to a switch depends on the command level specified in the AAA scheme: When the AAA scheme is local authentication, the command level available to users depends on the service-type terminal [ level level ] command. When the AAA scheme is RADIUS or HWTACACS authentication, you need to set the corresponding user level on the RADIUS or HWTACACS server.
For the introduction to AAA, RADIUS, and HWTACACS, refer to the AAA part of this manual.
Configuration Example
Network requirements
Assume the switch is configured to allow users to log in through Telnet, and the user level is set to the administrator level (level 3). Perform the following configurations for users logging in through the console port (AUX user interface). Configure the local user name as guest.
2-10
Set the authentication password of the local user to 123456 (in plain text). Set the service type of the local user to Terminal and the command level to 2. Configure to authenticate the users in the scheme mode. The baud rate of the console port is 19,200 bps. The screen can contain up to 30 lines. The history command buffer can store up to 20 commands. The timeout time of the AUX user interface is 6 minutes.
Network diagram
Figure 2-7 Network diagram for AUX user interface configuration (with the authentication mode being scheme)
GE1/0/1 Ethernet
Configuration procedure
# Enter system view.
<Sysname> system-view
# Create a local user named guest and enter local user view.
[Sysname] local-user guest
# Set the service type to Terminal, Specify commands of level 2 are available to users logging in to the AUX user interface.
[Sysname-luser-guest] service-type terminal level 2 [Sysname-luser-guest] quit
# Configure to authenticate users logging in through the console port in the scheme mode.
[Sysname-ui-aux0] authentication-mode scheme
# Set the maximum number of lines the screen can contain to 30.
[Sysname-ui-aux0] screen-length 30
2-11
# Set the maximum number of commands the history command buffer can store to 20.
[Sysname-ui-aux0] history-command max-size 20
After the above configuration, you need to modify the configuration of the terminal emulation utility running on the PC accordingly in the dialog box shown in Figure 2-4 to log in to the switch successfully.
2-12
3
Logging In Through Telnet
Go to these sections for information you are interested in: Introduction Telnet Configuration with Authentication Mode Being None Telnet Configuration with Authentication Mode Being Password
Introduction
Switch 4200G supports Telnet. You can manage and maintain a switch remotely by Telnetting to the switch. To log in to a switch through Telnet, the corresponding configuration is required on both the switch and the Telnet terminal. You can also log in to a switch through SSH. SSH is a secure shell added to Telnet. Refer to the SSH Operation for related information. Table 3-1 Requirements for Telnetting to a switch Item Requirement The IP address is configured for the VLAN of the switch, and the route between the switch and the Telnet terminal is reachable. (Refer to the IP Address Configuration IP Performance Configuration and Routing Protocol parts for more.) The authentication mode and other settings are configured. Refer to Table 3-2 and Table 3-3. Telnet is running. Telnet terminal The IP address of the VLAN interface of the switch is available.
Switch
Telnetting to a switch using IPv6 protocols is similar to Telnetting to a switch using IPv4 protocols. Refer to the IPv6 Management part for related information.
3-1
Follow these steps to set common telnet configuration: To do Enter system view Enter one or more VTY user interface views Configure the command level available to users logging in to VTY user interface Configure the protocols to be supported by the VTY user interface Set the commands to be executed automatically after a user logs in to the user interface successfully Use the command system-view user-interface vty first-number [ last-number ] Optional user privilege level level By default, commands of level 0 are available to users logging in to VTY user interfaces. Optional By default, both Telnet protocol and SSH protocol are supported. Optional auto-execute command text By default, no command is executed automatically after a user logs into the VTY user interface. Optional Enable terminal services shell By default, terminal services are available in all user interfaces. Remarks
3-2
To do
Remarks
screen-length screen-length
By default, the screen can contain up to 24 lines. You can use the screen-length 0 command to disable the function to display information in pages. Optional
The default history command buffer size is 10, that is, the history command buffer of a user can store up to 10 commands by default. Optional The default timeout time of a user interface is 10 minutes.
With the timeout time being 10 minutes, the connection to a user interface is terminated if no operation is performed in the user interface within 10 minutes. You can use the idle-timeout 0 command to disable the timeout function.
None
Password
Set the authentication mode to local password authentication Set the password for local authentication Set the authentication mode to scheme
Scheme
Specify to perform local authentication or remote authentication Set user names and passwords locally or on AAA Server
3-3
To improve security and prevent attacks to the unused Sockets, TCP 23 and TCP 22, ports for Telnet and SSH services respectively, will be enabled or disabled after corresponding configurations. If the authentication mode is none, TCP 23 will be enabled, and TCP 22 will be disabled. If the authentication mode is password, and the corresponding password has been set, TCP 23 will be enabled, and TCP 22 will be disabled. If the authentication mode is scheme, there are three scenarios: when the supported protocol is specified as telnet, TCP 23 will be enabled; when the supported protocol is specified as ssh, TCP 22 will be enabled; when the supported protocol is specified as all, both the TCP 23 and TCP 22 port will be enabled.
Note that if you configure not to authenticate the users, the command level available to users logging in to a switch depends on the user privilege level level command
Configuration Example
Network requirements
Assume current user logins through the console port, and the current user level is set to the administrator level (level 3). Perform the following configurations for users logging in through VTY 0 using Telnet. Do not authenticate the users. Commands of level 2 are available to the users. Telnet protocol is supported. The screen can contain up to 30 lines. The history command buffer can contain up to 20 commands. The timeout time of VTY 0 is 6 minutes.
3-4
Network diagram
Figure 3-1 Network diagram for Telnet configuration (with the authentication mode being none)
Configuration procedure
# Enter system view.
<Sysname> system-view
# Set the maximum number of lines the screen can contain to 30.
[Sysname-ui-vty0] screen-length 30
# Set the maximum number of commands the history command buffer can store to 20.
[Sysname-ui-vty0] history-command max-size 20
Required
Required
3-5
When the authentication mode is password, the command level available to users logging in to the user interface is determined by the user privilege level command.
Configuration Example
Network requirements
Assume current user logins through the console port and the current user level is set to the administrator level (level 3). Perform the following configurations for users logging in to VTY 0 using Telnet. Authenticate users using the local password. Set the local password to 123456 (in plain text). Commands of level 2 are available to the users. Telnet protocol is supported. The screen can contain up to 30 lines. The history command buffer can contain up to 20 commands. The timeout time of VTY 0 is 6 minutes.
Network diagram
Figure 3-2 Network diagram for Telnet configuration (with the authentication mode being password)
Configuration procedure
# Enter system view.
<Sysname> system-view
# Set the maximum number of lines the screen can contain to 30.
[Sysname-ui-vty0] screen-length 30
# Set the maximum number of commands the history command buffer can store to 20.
[Sysname-ui-vty0] history-command max-size 20
3-6
quit
Create a local user and enter local user view Set the authentication password for the local user Specify the service type for VTY users
local-user user-name password { simple | cipher } password service-type telnet [ level level ]
Note that: If you configure to authenticate the users in the scheme mode, the command level available to the users logging in to the switch depends on the user level defined in the AAA scheme. When the AAA scheme is local, the user level depends on the service-type { ftp | lan-access | { ssh | telnet | terminal }* [ level level ] } command. When the AAA scheme is RADIUS or HWTACACS, you need to specify the user level of a user on the corresponding RADIUS or HWTACACS server.
3-7
Refer to the AAA part of this manual for information about AAA, RADIUS, and HWTACACS.
Configuration Example
Network requirements
Assume current user logins through the console port and the user level is set to the administrator level (level 3). Perform the following configurations for users logging in to VTY 0 using Telnet. Configure the local user name as guest. Set the authentication password of the local user to 123456 (in plain text). Set the service type of VTY users to Telnet and the command level to 2. Configure to authenticate users logging in to VTY 0 in scheme mode. Only Telnet protocol is supported in VTY 0. The screen can contain up to 30 lines. The history command buffer can store up to 20 commands. The timeout time of VTY 0 is 6 minutes.
Network diagram
Figure 3-3 Network diagram for Telnet configuration (with the authentication mode being scheme)
Configuration procedure
# Enter system view.
<Sysname> system-view
# Create a local user named guest and enter local user view.
[Sysname] local-user guest
# Set the authentication password of the local user to 123456 (in plain text).
[Sysname-luser-guest] password simple 123456
# Set the service type to Telnet, Specify commands of level 2 are available to users logging in to VTY 0..
[Sysname-luser-guest] service-type telnet level 2 [Sysname-luser-guest] quit
3-8
# Set the maximum number of lines the screen can contain to 30.
[Sysname-ui-vty0] screen-length 30
# Set the maximum number of commands the history command buffer can store to 20.
[Sysname-ui-vty0] history-command max-size 20
Telnetting to a Switch
Telnetting to a Switch from a Terminal
1) Assign an IP address to VLAN-interface 1 of the switch (VLAN 1 is the default VLAN of the switch). Connect the serial port of your PC/terminal to the console port of the switch, as shown in Figure 3-4 Figure 3-4 Diagram for establishing connection to a console port
Launch a terminal emulation utility (such as Terminal in Windows 3.X or HyperTerminal in Windows 95/Windows 98/Windows NT/Windows 2000/Windows XP) on the PC terminal, with the baud rate set to 19,200 bps, data bits set to 8, parity check set to none, and flow control set to none. Turn on the switch and press Enter as prompted. The prompt appears. Perform the following operations in the terminal window to assign IP address 202.38.160.92/24 to VLAN-interface 1 of the switch.
<Sysname> system-view [Sysname] interface Vlan-interface 1 [Sysname-Vlan-interface1] ip address 202.38.160.92 255.255.255.0
2)
Perform Telnet-related configuration on the switch. Refer to Telnet Configuration with Authentication Mode Being None, Telnet Configuration with Authentication Mode Being Password, and Telnet Configuration with Authentication Mode Being Scheme for more.
3)
Connect your PC/terminal and the Switch to an Ethernet, as shown in Figure 3-5. Make sure the port through which the switch is connected to the Ethernet belongs to VLAN 1 and the route between your PC and VLAN-interface 1 is reachable.
3-9
Server
4)
Launch Telnet on your PC, with the IP address of VLAN-interface 1 of the switch as the parameter, as shown in Figure 3-6.
5)
If the password authentication mode is specified, enter the password when the Telnet window displays Login authentication and prompts for login password. The CLI prompt (such as <Sysname>) appears if the password is correct. If all VTY user interfaces of the switch are in use, you will fail to establish the connection and receive the message that says All user interfaces are used, please try later!. A 3Com switch can accommodate up to five Telnet connections at same time.
6)
After successfully Telnetting to the switch, you can configure the switch or display the information about the switch by executing corresponding commands. You can also type ? at any time for help. Refer to the relevant parts in this manual for the information about the commands.
A Telnet connection is terminated if you delete or modify the IP address of the VLAN interface in the Telnet session. By default, commands of level 0 are available to Telnet users authenticated by password. Refer to the CLI part for information about command hierarchy.
3-10
1)
Perform Telnet-related configuration on the switch operating as the Telnet server. Refer to Telnet Configuration with Authentication Mode Being None, Telnet Configuration with Authentication Mode Being Password, and Telnet Configuration with Authentication Mode Being Scheme for more.
2) 3)
Telnet to the switch operating as the Telnet client. Execute the following command on the switch operating as the Telnet client:
Note that xxxx is the IP address or the host name of the switch operating as the Telnet server. You can use the ip host to assign a host name to a switch. 1) After successful login, the CLI prompt (such as <Sysname>) appears. If all the VTY user interfaces of the switch are in use, you will fail to establish the connection and receive the message that says All user interfaces are used, please try later!. 2) After successfully Telnetting to the switch, you can configure the switch or display the information about the switch by executing corresponding commands. You can also type ? at any time for help. Refer to the following chapters for the information about the commands.
3-11
4
Logging In Using a Modem
Go to these sections for information you are interested in: Introduction Configuration on the Switch Side Modem Connection Establishment
Introduction
The administrator can log in to the console port of a remote switch using a modem through public switched telephone network (PSTN) if the remote switch is connected to the PSTN through a modem to configure and maintain the switch remotely. When a network operates improperly or is inaccessible, you can manage switches in the network remotely in this way. To log in to a switch in this way, you need to configure the administrator side and the switch properly, as listed in the following table. Table 4-1 Requirements for logging in to a switch using a modem Item Administrator side Requirement The PC can communicate with the modem connected to it. The modem is properly connected to PSTN. The telephone number of the switch side is available. The modem is connected to the console port of the switch properly. The modem is properly configured. Switch side The modem is properly connected to PSTN and a telephone set. The authentication mode and other related settings are configured on the switch. Refer to Table 2-3.
ATS0=1 ----------------------- Configure to answer automatically after the first ring AT&D AT&K0 AT&R1 AT&S0 ATEQ1&W ----------------------- Ignore DTR signal ----------------------- Disable flow control ----------------------- Ignore RTS signal ----------------------- Set DSR to high level by force ----------------------- Disable the Modem from returning command response and the
4-1
The configuration commands and the output of different modems may differ. Refer to the user manual of the modem when performing the above configuration.
Switch Configuration
After logging in to a switch through its console port by using a modem, you will enter the AUX user interface. The corresponding configuration on the switch is the same as those when logging in to the switch locally through its console port except that: When you log in through the console port using a modem, the baud rate of the console port is usually set to a value lower than the transmission speed of the modem. Otherwise, packets may get lost. Other settings of the console port, such as the check mode, the stop bits, and the data bits, remain the default.
The configuration on the switch depends on the authentication mode the user is in. Refer to Table 2-3 for the information about authentication mode configuration.
Telephone line
Modem
PSTN
Modem
4)
Launch a terminal emulation utility on the PC and set the telephone number to call the modem directly connected to the switch, as shown in Figure 4-2 through Figure 4-4. Note that you need to set the telephone number to that of the modem directly connected to the switch.
4-3
5)
If the password authentication mode is specified, enter the password when prompted. If the password is correct, the prompt (such as <Sysname>) appears. You can then configure or manage the switch. You can also enter the character ? at anytime for help. Refer to the related parts in this manual for information about the configuration commands.
If you perform no AUX user-related configuration on the switch, the commands of level 3 are available to modem users. Refer to the CLI part for information about command level.
4-4
5
CLI Configuration
When configuring CLI, go to these sections for information you are interested in: Introduction to the CLI Command Hierarchy CLI Views CLI Features
Command Hierarchy
Command Level and User Privilege Level
To restrict the different users access to the device, the system manages the login users and all the commands by their privilege levels. All the commands and login users are categorized into four levels, which are visit, monitor, system, and manage from low to high, and identified respectively by 0 through 3. After users at different privilege levels log in, they can only use commands at their own, or lower, levels. For example, level 2 users can only use level 0 through level 2 commands, not level 3 commands.
Command level
Based on user privilege, commands are classified into four levels, which default to: Visit level (level 0): Commands at this level are mainly used to diagnose network, and they cannot be saved in configuration file. For example, ping, tracert and telnet are level 0 commands.
5-1
Monitor level (level 1): Commands at this level are mainly used to maintain the system and diagnose service faults, and they cannot be saved in configuration file. Such commands include debugging and terminal. System level (level 2): Commands at this level are mainly used to configure services. Commands concerning routing and network layers are at this level. These commands can be used to provide network services directly. Manage level (level 3): Commands at this level are associated with the basic operation modules and support modules of the system. These commands provide support for services. Commands concerning file system, FTP/TFTP/XModem downloading, user management, and level setting are at this level. By using the command-privilege level command, the administrator can change the level of a command in a specific view as required. For details, refer to Modifying the Command Level.
If a user logs in using AAA authentication, the user privilege level depends on the configuration of the AAA scheme. For details, refer to AAA Operation.
Users can switch their user privilege level temporarily without logging out and disconnecting the current connection; after the switch, users can continue to configure the device without the need of relogin and reauthentication, but the commands that they can execute have changed. For details, refer to Switching User Level.
5-2
Remarks Required
You are recommended to use the default command level or modify the command level under the guidance of professional staff; otherwise, the change of command level may bring inconvenience to your maintenance and operation, or even potential security problem. When you change the level of a command with multiple keywords or arguments, you should input the keywords or arguments one by one in the order they appear in the command syntax. Otherwise, your configuration will not take effect. The values of the arguments should be within the specified ranges. After you change the level of a command in a certain view to be lower than the default level, change the level of the command used to enter the view accordingly.
Configuration example
The network administrator (a level 3 user) wants to change some TFTP commands (such as tftp get) from level 3 to level 0, so that general Telnet users (level 0 users) are able to download files through TFTP. # Change the tftp get command in user view (shell) from level 3 to level 0. (Originally, only level 3 users can change the level of a command.)
<Sysname> system-view [Sysname] command-privilege level 0 view shell tftp [Sysname] command-privilege level 0 view shell tftp 192.168.0.1 [Sysname] command-privilege level 0 view shell tftp 192.168.0.1 get [Sysname] command-privilege level 0 view shell tftp 192.168.0.1 get bootrom.btm
After the above configuration, general Telnet users can use the tftp get command to download file bootrom.btm and other files from TFTP server 192.168.0.1 and other TFTP servers.
can switch to a higher level temporarily; when the administrators need to leave for a while or ask someone else to manage the device temporarily, they can switch to a lower privilege level before they leave to restrict the operation by others. The high-to-low user level switching is unlimited. However, the low-to-high user level switching requires the corresponding authentication. Generally, two authentication modes are available: the super password authentication mode and HWTACACS authentication mode. Complete the following tasks to configure user level switching: Task Specifying the authentication mode for user level switching Adopting super password authentication for user level switching Adopting HWTACACS authentication for user level switching Switching to a specific user level Remarks Optional Required Required Required
HWTACACS authentication Specify the authentication mode for user level switching Super password authentication preferred (with the HWTACACS authentication as the backup authentication mode) HWTACACS authentication preferred (with the super password authentication as the backup authentication mode)
5-4
When both the super password authentication and the HWTACACS authentication are specified, the device adopts the preferred authentication mode first. If the preferred authentication mode cannot be implemented (for example, the super password is not configured or the HWTACACS authentication server is unreachable), the backup authentication mode is adopted.
The super password is for level switching only and is different from the login password..
To do Enter system view Enter ISP domain view Set the HWTACACS authentication scheme for user level switching
Use the command system-view domain domain-name authentication super hwtacacs-scheme hwtacacs-scheme-name Required
Remarks
By default, the HWTACACS authentication scheme for user level switching is not set.
When setting the HWTACACS authentication scheme for user level switching using the authentication super hwtacacs-scheme command, make sure the HWTACACS authentication scheme identified by the hwtacacs-scheme-name argument already exists. Refer to AAA Operation for information about HWTACACS authentication scheme.
If no user level is specified in the super password command or the super command, level 3 is used by default. For security purpose, the password entered is not displayed when you switch to another user level. You will remain at the original user level if you have tried three times but failed to enter the correct authentication information.
Configuration examples
After a general user telnets to the switch, his/her user level is 0. Now, the network administrator wants to allow general users to switch to level 3, so that they are able to configure the switch. 1) Super password authentication configuration example The administrator configures the user level switching authentication policies. # Set the user level switching authentication mode for VTY 0 users to super password authentication.
<Sysname> system-view [Sysname] user-interface vty 0 [Sysname-ui-vty0] super authentication-mode super-password [Sysname-ui-vty0] quit
5-6
A VTY 0 user switches its level to level 3 after logging in. # A VTY 0 user telnets to the switch, and then uses the set password to switch to user level 3.
<Sysname> super 3 Password: User privilege level is 3, and only those commands can be used whose level is equal or less than this. Privilege note: 0-VISIT, 1-MONITOR, 2-SYSTEM, 3-MANAGE
# After configuring the switch, the general user switches back to user level 0.
<Sysname> super 0 User privilege level is 0, and only those commands can be used whose level is equal or less than this. Privilege note: 0-VISIT, 1-MONITOR, 2-SYSTEM, 3-MANAGE
2)
HWTACACS authentication configuration example The administrator configures the user level switching authentication policies.
# Configure a HWTACACS authentication scheme named acs, and specify the user name and password used for user level switching on the HWTACACS server defined in the scheme. Refer to AAA Operation for detailed configuration procedures. # Enable HWTACACS authentication for VTY 0 user level switching.
<Sysname> system-view [Sysname] user-interface vty 0 [Sysname-ui-vty0] super authentication-mode scheme [Sysname-ui-vty0] quit
# Specify to adopt the HWTACACS authentication scheme named acs for user level switching in the ISP domain named system.
[Sysname] domain system [Sysname-isp-system] authentication super hwtacacs-scheme acs
A VTY 0 user switches its level to level 3 after logging in. # Switch to user level 3 (assuming that you log into the switch as a VTY 0 user by Telnet).
<Sysname> super 3 Username: user@system Password: User privilege level is 3, and only those commands can be used whose level is equal or less than this. Privilege note: 0-VISIT, 1-MONITOR, 2-SYSTEM, 3-MANAGE
CLI Views
CLI views are designed for different configuration tasks. These are how commands are organized, with groupings of tasks for related operations. For example, once a user logs into a switch successfully, the user enters user view, where the user can perform some simple operations such as checking the operation status and statistics information of the switch. After executing the system-view command, the user enters system view, and there are other views below this accessible by entering corresponding commands.
5-7
Table 5-1 lists the CLI views provided by the 3com switch 4200G, operations that can be performed in different CLI views and the commands used to enter specific CLI views. Table 5-1 CLI views View Available operation Display operation status and statistical information of the switch Prompt example Enter method Enter user view once logging into the switch. Execute the system-view command in user view. Execute the interface gigabitethernet command in system view. Execute the interface tengigabitethern et command in system view. Execute the interface aux 1/0/0 command in system view Execute the vlan command in system view. Execute the interface Vlan-interface command in system view. Execute the interface loopback command in system view. Execute the interface null command in system view. Execute the local-user command in system view. Quit method Execute the quit command to log out of the switch. Execute the quit or return command to return to user view. Execute the quit command to return to system view. Execute the return command to return to user view.
User view
<Sysname>
System view
[Sysname]
1000 Mbps Ethernet port view: [Sysname-Gigabi tEthernet1/0/1] Ethernet port view Configure Ethernet port parameters 10 Gigabit Ethernet port view: [Sysname-TenGi gabitEthernet1/1/ 1] Aux1/0/0 port (the console port) view The 3com switch 4200G does not support configuration on port Aux1/0/0 Configure VLAN parameters Configure VLAN interface parameters, including the management VLAN parameters [Sysname-Aux1/ 0/0]
VLAN view
[Sysname-vlan1]
[Sysname-Vlan-i nterface1]
[Sysname-LoopB ack0]
[Sysname-NULL 0]
[Sysname-luser-u ser1]
5-8
Enter method Execute the user-interface command in system view. Execute the ftp command in user view. Execute the sftp command in system view. Execute the stp region-configurat ion command in system view. Execute the cluster command in system view. Execute the rsa peer-public-key command in system view. Execute the public-key peer command in system view. Execute the public-key-code begin command in public key view.
Quit method
[ftp]
sftp-client>
[Sysname-mst-re gion]
Cluster view
Configure cluster parameters Configure the RSA public key for SSH users
[Sysname-cluster ]
[Sysname-rsa-pu blic-key]
Public key view Configure the RSA or DSA public key for SSH users Edit the RSA public key for SSH users Public key editing view Edit the RSA or DSA public key for SSH users Define rules for a basic ACL (with ID ranging from 2000 to 2999) Define rules for an advanced ACL (with ID ranging from 3000 to 3999) Define rules for an layer 2 ACL (with ID ranging from 4000 to 4999) Configure RADIUS scheme parameters [Sysname-peer-p ublic-key] [Sysname-rsa-ke y-code] [Sysname-peer-k ey-code]
Execute the public-key-cod e end command to return to public key view. Execute the quit command to return to system view. Execute the return command to return to user view.
[Sysname-aclbasic-2000]
Execute the acl number command in system view. Execute the acl number command in system view. Execute the acl number command in system view. Execute the radius scheme command in system view. Execute the domain command in system view.
[Sysname-acl-ad v-3000]
[Sysname-acl-eth ernetframe-4000]
[Sysname-radius1]
[Sysname-isp-aa a123.net]
5-9
Available operation Configure remote-ping test group parameters Configure HWTACACS parameters
Enter method Execute the remote-ping command in system view. Execute the hwtacacs scheme command in system view. Execute the poe-profile command in system view. Execute the smart-link group command in system view. Execute the monitor-link group command in system view.
Quit method
HWTACACS view
[Sysname-hwtac acs-a123]
[Sysname-poe-pr ofile-a123]
[Sysname-smlk-g roup1]
[Sysname-mtlk-gr oup1]
CLI Features
Online Help
When configuring the switch, you can use the online help to get related help information. The CLI provides two types of online help: complete and partial.
5-10
<Other information is omitted> 2) Enter a command, a space, and a question mark (?).
If the question mark ? is at a keyword position in the command, all available keywords at the position and their descriptions will be displayed on your terminal.
<Sysname> clock ? datetime summer-time timezone Specify the time and date Configure summer time Configure time zone
If the question mark ? is at an argument position in the command, the description of the argument will be displayed on your terminal.
[Sysname] interface vlan-interface ? <1-4094> VLAN interface number
If only <cr> is displayed after you enter ?, it means no parameter is available at the ? position, and you can enter and execute the command directly.
[Sysname] interface vlan-interface 1 ? <cr>
2)
Enter a command, a space, a character/string and a question mark (?) next to it. All the keywords beginning with the character/string (if available) are displayed on your terminal. For example:
3)
Enter the first several characters of a keyword of a command and then press <Tab>. If there is a unique keyword beginning with the characters just typed, the unique keyword is displayed in its complete form. If there are multiple keywords beginning with the characters, you can have them displayed one by one (in complete form) by pressing <Tab> repeatedly.
Terminal Display
The CLI provides the screen splitting feature to have display output suspended when the screen is full. When display output pauses, you can perform the following operations as needed (see Table 5-2). Table 5-2 Display-related operations Operation Press <Ctrl+C> Press any character except <Space>, <Enter>, /, +, and - when the display output pauses Press the space key
5-11
Function Stop the display output and execution of the command. Stop the display output. Get to the next page.
Command History
The CLI provides the command history function. You can use the display history-command command to view a specific number of latest executed commands and execute them again in a convenient way. By default, the CLI can store up to 10 latest executed commands for each user. You can view the command history by performing the operations listed in the following table: Follow these steps to view history commands: Purpose Display the latest executed history commands Recall the previous history command Recall the next history command Operation Execute the display history-command command Press the up arrow key or <Ctrl+P> Press the down arrow key or <Ctrl+N> Remarks This command displays the command history. This operation recalls the previous history command (if available). This operation recalls the next history command (if available).
The Windows 9x HyperTerminal explains the up and down arrow keys in a different way, and therefore the two keys are invalid when you access history commands in such an environment. However, you can use <Ctrl+ P> and <Ctrl+ N> instead to achieve the same purpose. When you enter the same command multiple times consecutively, only one history command entry is created by the command line interface.
Error Prompts
If a command passes the syntax check, it will be successfully executed; otherwise, an error message will be displayed. Table 5-3 lists the common error messages. Table 5-3 Common error messages Error message Remarks The command does not exist. The keyword does not exist. Unrecognized command The parameter type is wrong. The parameter value is out of range. Incomplete command Too many parameters Ambiguous command The command entered is incomplete. The parameters entered are too many. The parameters entered are ambiguous.
5-12
Command Edit
The CLI provides basic command edit functions and supports multi-line editing. The maximum number of characters a command can contain is 254. Table 5-4 lists the CLI edit operations. Table 5-4 Edit operations Press A common key To Insert the corresponding character at the cursor position and move the cursor one character to the right if the command is shorter than 254 characters. Delete the character on the left of the cursor and move the cursor one character to the left. Move the cursor one character to the left. Move the cursor one character to the right. Display history commands. Use the partial online help. That is, when you input an incomplete keyword and press <Tab>, if the input parameter uniquely identifies a complete keyword, the system substitutes the complete keyword for the input parameter; if more than one keywords match the input parameter, you can display them one by one (in complete form) by pressing <Tab> repeatedly; if no keyword matches the input parameter, the system displays your original input on a new line without any change.
Backspace key Left arrow key or <Ctrl+B> Right arrow key or <Ctrl+F> Up arrow key or <Ctrl+P> Down arrow key or <Ctrl+N>
<Tab>
5-13
6
Logging In Through the Web-based Network Management Interface
Go to these sections for information you are interested in: Introduction Establishing an HTTP Connection Configuring the Login Banner Enabling/Disabling the WEB Server
Introduction
Switch 4200G has a Web server built in. It enables you to log in to Switch 4200G through a Web browser and then manage and maintain the switch intuitively by interacting with the built-in Web server. To log in to Switch 4200G through the built-in Web-based network management interface, you need to perform the related configuration on both the switch and the PC operating as the network management terminal. Table 6-1 Requirements for logging in to a switch through the Web-based network management system Item Requirement The VLAN interface of the switch is assigned an IP address, and the route between the switch and the Web network management terminal is reachable. (Refer to the IP Address Configuration IP Performance Configuration and Routing Protocol parts for related information.) The user name and password for logging in to the Web-based network management system are configured. PC operating as the network management terminal IE is available. The IP address of the VLAN interface of the switch, the user name, and the password are available.
Switch
6-1
3)
Establish an HTTP connection between your PC and the switch, as shown in Figure 6-1.
Figure 6-1 Establish an HTTP connection between your PC and the switch
4)
Log in to the switch through IE. Launch IE on the Web-based network management terminal (your PC) and enter the IP address of the management VLAN interface of the switch in the address bar. (Make sure the route between the Web-based network management terminal and the switch is available.)
5)
When the login authentication interface (as shown in Figure 6-2) appears, enter the user name and the password configured in step 2 and click <Login> to bring up the main page of the Web-based network management system.
Figure 6-2 The login page of the Web-based network management system
6-2
Configuration Example
Network requirements
A user logs in to the switch through Web. The banner page is desired when a user logs into the switch.
Network diagram
Figure 6-3 Network diagram for login banner configuration
Configuration Procedure
# Enter system view.
<Sysname> system-view
# Configure the banner Welcome to be displayed when a user logs into the switch through Web.
[Sysname] header login %Welcome%
Assume that a route is available between the user terminal (the PC) and the switch. After the above-mentioned configuration, if you enter the IP address of the switch in the address bar of the browser running on the user terminal and press <Enter>, the browser will display the banner page, as shown in Figure 6-4. Figure 6-4 Banner page displayed when a user logs in to the switch through Web
Click <Continue> to enter user login authentication page. You will enter the main page of the Web-based network management system if the authentication succeeds.
6-3
To do Enter system view Enable the Web server Disable the Web server
Use the command system-view ip http shutdown undo ip http shutdown Required
Remarks
To improve security and prevent attack to the unused Sockets, TCP 80 port (which is for HTTP service) is enabled/disabled after the corresponding configuration. Enabling the Web server (by using the undo ip http shutdown command) opens TCP 80 port. Disabling the Web server (by using the ip http shutdown command) closes TCP 80 port.
6-4
7
Logging In Through NMS
Go to these sections for information you are interested in: Introduction Connection Establishment Using NMS
Introduction
You can also log in to a switch through a Network Management Station (NMS), and then configure and manage the switch through the agent software on the switch. Simple Network Management Protocol (SNMP) is applied between the NMS and the agent. Refer to the SNMP-RMON part for related information. To log in to a switch through an NMS, you need to perform related configuration on both the NMS and the switch. Table 7-1 Requirements for logging in to a switch through an NMS Item Requirement The IP address of the VLAN interface of the switch is configured. The route between the NMS and the switch is reachable. (Refer to the IP Address Configuration IP Performance Configuration and Routing Protocol parts for related information.) The basic SNMP functions are configured. (Refer to the SNMP-RMON part for related information.) NMS The NMS is properly configured. (Refer to the user manual of your NMS for related information.)
Switch
Switch
Network
NMS
7-1
8
Configuring Source IP Address for Telnet Service Packets
Go to these sections for information you are interested in: Overview Configuring Source IP Address for Telnet Service Packets Displaying Source IP Address Configuration
Overview
You can configure source IP address or source interface for the Telnet server and Telnet client. This provides a way to manage services and enhances security. The source IP address specified for Telnet service packets is the IP address of an Loopback interface or VLAN interface. After you specify the IP address of a virtual Loopback interface or an unused VLAN interface as the source IP address of Telnet service packets, the IP address is used as the source IP address no matter which interface of the switch is used to transmit packets between the Telnet client and the Telnet server. This conceals the IP address of the actual interface used. As a result, external attacks are guarded and the security is improved. On the other hand, you can configure the Telnet server to accept only Telnet service packets with specific source IP addresses to make sure specific users can log into the switch.
8-1
Operation Specify a source interface for Telnet server Specify source IP address for Telnet client Specify a source interface for Telnet client
Command telnet-server source-interface interface-type interface-number telnet source-ip ip-address telnet source-interface interface-type interface-number
To perform the configurations listed in Table 8-1 and Table 8-2, make sure that: The IP address specified is that of the local device. The interface specified exists. If a source IP address (or source interface) is specified, you need to make sure that the route between the IP addresses (or interface) of both sides is reachable.
8-2
9
User Control
Go to these sections for information you are interested in: Introduction Controlling Telnet Users Controlling Network Management Users by Source IP Addresses Controlling Web Users by Source IP Address
Introduction
You can control users logging in through Telnet, SNMP and WEB by defining Access Control List (ACL), as listed in Table 9-1. Table 9-1 Ways to control different types of login users Login mode Control method By source IP address Telnet By source and destination IP address By source MAC address SNMP By source IP addresses By source IP addresses WEB Disconnect Web users by force By executing commands in CLI Logging Out a Web User Implementation Through basic ACL Through advanced ACL Through Layer 2 ACL Controlling Network Management Users by Source IP Addresses Controlling Web Users by Source IP Address Controlling Telnet Users Related section
9-1
If no ACL is configured on the VTY user interface, users are not controlled when establishing a Telnet connection using this user interface. If an ACL is configured on the VTY user interface, there will be two possibilities: if the packets for establishing a Telnet connection match the ACL rule configured on the VTY user interface, the connection will be permitted or denied according to the ACL rule; if not, the connection will be denied directly.
Source and destination in this manual refer to a Telnet client and a Telnet server respectively. If the inbound keyword is specified, the Telnet client is the user telnetting to the local switch and the Telnet server is the local switch. If the outbound keyword is specified, the Telnet client is the local switch, and the Telnet server is another device to which the user is telnetting.
Follow these steps to control Telnet users by ACL: To do Enter system view Create a basic ACL or enter basic ACL view Define rules for the ACL Quit to system view Enter user interface view Use the command system-view acl number acl-number [ match-order { auto | config } ] rule [ rule-id ] { deny | permit } [ rule-string ] quit user-interface [ type ] first-number [ last-number ] As for the acl number command, the config keyword is specified by default. Required Remarks
9-2
To do Apply a basic or advanced ACL to control Telnet users Apply a Layer 2 ACL to control Telnet users
Remarks
Use either command The inbound keyword specifies to filter the users trying to Telnet to the current switch. The outbound keyword specifies to filter users trying to Telnet to other switches from the current switch.
Configuration Example
Network requirements
Only the Telnet users sourced from the IP address of 10.110.100.52 are permitted to access the switch.
Network diagram
Figure 9-1 Network diagram for controlling Telnet users using ACLs
10.110.100.46 Host A
IP network
Switch
Host B 10.110.100.52
Configuration procedure
# Define a basic ACL.
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule 1 permit source 10.110.100.52 0 [Sysname-acl-basic-2000] quit
Defining an ACL Applying the ACL to control users accessing the switch through SNMP To control whether an NMS can manage the switch, you can use this function.
Prerequisites
The controlling policy against network management users is determined, including the source IP addresses to be controlled and the controlling actions (permitting or denying).
Configuration Example
Network requirements
Only SNMP users sourced from the IP addresses of 10.110.100.52 are permitted to log in to the switch.
9-4
Network diagram
Figure 9-2 Network diagram for controlling SNMP users using ACLs
10.110.100.46 Host A
IP network
Switch
Host B 10.110.100.52
Configuration procedure
# Define a basic ACL.
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule 1 permit source 10.110.100.52 0 [Sysname-acl-basic-2000] quit
# Apply the ACL to only permit SNMP users sourced from the IP addresses of 10.110.100.52 to access the switch.
[Sysname] snmp-agent community read aaa acl 2000 [Sysname] snmp-agent group v2c groupa acl 2000 [Sysname] snmp-agent usm-user v2c usera groupa acl 2000
Prerequisites
The controlling policy against Web users is determined, including the source IP addresses to be controlled and the controlling actions (permitting or denying).
9-5
To do Enter system view Create a basic ACL or enter basic ACL view Define rules for the ACL Quit to system view Apply the ACL to control Web users
Use the command system-view acl number acl-number [ match-order { config | auto } ] rule [ rule-id ] { deny | permit } [ rule-string ] quit ip http acl acl-number
Remarks
As for the acl number command, the config keyword is specified by default. Required Optional By default, no ACL is applied for Web users.
Configuration Example
Network requirements
Only the Web users sourced from the IP address of 10.110.100.52 are permitted to access the switch.
Network diagram
Figure 9-3 Network diagram for controlling Web users using ACLs
10.110.100.46 Host A
IP network
Switch
Host B 10.110.100.52
Configuration procedure
# Define a basic ACL.
<Sysname> system-view [Sysname] acl number 2030 [Sysname-acl-basic-2030] rule 1 permit source 10.110.100.52 0
9-6
[Sysname-acl-basic-2030] quit
# Apply ACL 2030 to only permit the Web users sourced from the IP address of 10.110.100.52 to access the switch.
[Sysname] ip http acl 2030
9-7
Table of Contents
1 Configuration File Management1-1 Introduction to Configuration File 1-1 Configuration Task List 1-2 Saving the Current Configuration 1-2 Erasing the Startup Configuration File 1-3 Specifying a Configuration File for Next Startup 1-4 Displaying Switch Configuration1-5
Types of configuration
The configuration of a switch falls into two types: Saved configuration, a configuration file used for initialization. If this file does not exist, the switch starts up without loading any configuration file. Current configuration, which refers to the users configuration during the operation of a switch. This configuration is stored in Dynamic Random-Access Memory (DRAM). It is removed when rebooting.
When saving the current configuration, you can specify the file to be a main or backup or normal configuration file. When removing a configuration file from a switch, you can specify to remove the main or backup configuration file. Or, if it is a file having both main and backup attribute, you can specify to erase the main or backup attribute of the file. When setting the configuration file for next startup, you can specify to use the main or backup configuration file.
1-2
When you use the save safely command to save the configuration file, if the switch reboots or the power fails during the saving process, the switch initializes itself in the following two conditions when it starts up next time: If a configuration file with the extension .cfg exists in the Flash, the switch uses the configuration file to initialize itself when it starts up next time. If there is no .cfg configuration file in the Flash, but there is a configuration file with the extension .cfgbak (backup configuration file containing the original configuration information) or/and a configuration file with the extension .cfgtmp (temporary configuration file containing the current configuration information) in the Flash, you can change the extension .cfgbak or .cfgtmp to .cfg using the rename command. The switch will use the renamed configuration file to initialize itself when it starts up next time. For details of the rename command, refer to the File System Management part of the manual.
It is recommended to adopt the fast saving mode in the conditions of stable power and adopt the safe mode in the conditions of unstable power or remote maintenance. The extension name of the configuration file must be .cfg.
1-3
Remarks
You may need to erase the configuration file for one of these reasons: After you upgrade software, the old configuration file does not match the new software. The startup configuration file is corrupted or not the one you needed. The following two situations exist: While the reset saved-configuration [ main ] command erases the configuration file with main attribute, it only erases the main attribute of a configuration file having both main and backup attribute. While the reset saved-configuration backup command erases the configuration file with backup attribute, it only erases the backup attribute of a configuration file having both main and backup attribute.
This command will permanently delete the configuration file from the switch.
You can specify a configuration file to be used for the next startup and configure the main/backup attribute for the configuration file.
1-4
The configuration file must use .cfg as its extension name and the startup configuration file must be saved at the root directory of the switch.
1-5
Table of Contents
1 VLAN Overview 1-1 VLAN Overview1-1 Introduction to VLAN 1-1 Advantages of VLANs 1-2 VLAN Fundamentals 1-2 VLAN Interface 1-4 VLAN Classification 1-4 Port-Based VLAN1-4 Link Types of Ethernet Ports 1-4 Assigning an Ethernet Port to Specified VLANs 1-5 Configuring the Default VLAN ID for a Port1-5 2 VLAN Configuration 2-1 VLAN Configuration 2-1 VLAN Configuration Task List 2-1 Basic VLAN Configuration 2-1 Basic VLAN Interface Configuration2-2 Displaying VLAN Configuration 2-3 Configuring a Port-Based VLAN 2-3 Port-Based VLAN Configuration Task List 2-3 Configuring the Link Type of an Ethernet Port 2-3 Assigning an Ethernet Port to a VLAN 2-4 Configuring the Default VLAN for a Port 2-5 Displaying and Maintaining Port-Based VLAN 2-5 Port-Based VLAN Configuration Example2-5
VLAN Overview
This chapter covers these topics: VLAN Overview Port-Based VLAN
VLAN Overview
Introduction to VLAN
The traditional Ethernet is a broadcast network, where all hosts are in the same broadcast domain and connected with each other through hubs or switches. Hubs and switches, which are the basic network connection devices, have limited forwarding functions. A hub is a physical layer device without the switching function, so it forwards the received packet to all ports except the inbound port of the packet. A switch is a link layer device which can forward a packet according to the MAC address of the packet. A switch builds a table of MAC addresses mapped to associated ports with that address and only sends a known MACs traffic to one port. When the switch receives a broadcast packet or an unknown unicast packet whose MAC address is not included in the MAC address table of the switch, it will forward the packet to all the ports except the inbound port of the packet. The above scenarios could result in the following network problems. Large quantity of broadcast packets or unknown unicast packets may exist in a network, wasting network resources. A host in the network receives a lot of packets whose destination is not the host itself, causing potential serious security problems. Related to the point above, someone on a network can monitor broadcast packets and unicast packets and learn of other activities on the network. Then they can attempt to access other resources on the network, whether or not they are authorized to do this. Isolating broadcast domains is the solution for the above problems. The traditional way is to use routers, which forward packets according to the destination IP address and does not forward broadcast packets in the link layer. However, routers are expensive and provide few ports, so they cannot split the network efficiently. Therefore, using routers to isolate broadcast domains has many limitations. The Virtual Local Area Network (VLAN) technology is developed for switches to control broadcasts in LANs. A VLAN can span multiple physical spaces. This enables hosts in a VLAN to be located in different physical locations. By creating VLANs in a physical LAN, you can divide the LAN into multiple logical LANs, each of which has a broadcast domain of its own. Hosts in the same VLAN communicate in the traditional Ethernet way. However, hosts in different VLANs cannot communicate with each other directly but need the help of network layer devices, such as routers and Layer 3 switches. Figure 1-1 illustrates a VLAN implementation.
1-1
Advantages of VLANs
Compared with traditional Ethernet technology, VLAN technology delivers the following benefits: Confining broadcast traffic within individual VLANs. This saves bandwidth and improves network performance. Improving LAN security. By assigning user groups to different VLANs, you can isolate them at Layer 2. To enable communication between VLANs, routers or Layer 3 switches are required. Flexible virtual workgroup creation. As users from the same workgroup can be assigned to the same VLAN regardless of their physical locations, network construction and maintenance is much easier and more flexible.
VLAN Fundamentals
VLAN tag
To enable a network device to identify frames of different VLANs, a VLAN tag field is inserted into the data link layer encapsulation. The format of VLAN-tagged frames is defined in IEEE 802.1Q issued by IEEE in 1999. In the header of a traditional Ethernet data frame, the field after the destination MAC address and the source MAC address (DA&SA) is the Type field indicating the upper layer protocol type, as shown in Figure 1-2. Figure 1-2 Encapsulation format of traditional Ethernet frames
IEEE 802.1Q inserts a four-byte VLAN tag after the DA&SA field, as shown in Figure 1-3.
1-2
A VLAN tag comprises four fields: tag protocol identifier (TPID), priority, canonical format indicator (CFI), and VLAN ID. The 16-bit TPID field with a value of 0x8100 indicates that the frame is VLAN tagged. On the Switch 4200G series Ethernet switches, the default TPID is 0x8100. The 3-bit priority field indicates the 802.1p priority of the frame. Refer to the QoS part of this manual for details. The 1-bit CFI field specifies whether the MAC addresses are encapsulated in the canonical format for the receiving device to correctly interpret the MAC addresses. Value 0 indicates that the MAC addresses are encapsulated in canonical format; value 1 indicates that the MAC addresses are encapsulated in non-canonical format. The field is set to 0 by default. The 12-bit VLAN ID field identifies the VLAN the frame belongs to. The VLAN ID range is 0 to 4095. As 0 and 4095 are reserved by the protocol, a VLAN ID actually ranges from 1 to 4094.
The Ethernet II encapsulation format is used here. Besides the Ethernet II encapsulation format, other encapsulation formats such as 802.2 LLC and 802.2 SNAP are also supported by Ethernet. The VLAN tag fields are also added to frames encapsulated in these formats for VLAN identification.
VLAN ID identifies the VLAN to which a packet belongs. When a switch receives a packet carrying no VLAN tag, the switch encapsulates a VLAN tag with the default VLAN ID of the inbound port for the packet, and sends the packet to the default VLAN of the inbound port for transmission. For the details about setting the default VLAN of a port, refer to Configuring the Default VLAN ID for a Port.
1-3
Independent VLAN learning (IVL), where the switch maintains an independent MAC address forwarding table for each VLAN. The source MAC address of a packet received in a VLAN on a port is recorded to the MAC address forwarding table of this VLAN only, and packets received in a VLAN are forwarded according to the MAC address forwarding table for the VLAN. Currently, the Switch 4200G series Ethernet switches adopt the IVL mode only. For more information about the MAC address forwarding table, refer to the MAC Address Forwarding Table Management part of the manual.
VLAN Interface
Hosts in different VLANs cannot communicate with each other directly unless routers or Layer 3 switches are used to do Layer 3 forwarding. The Switch 4200G series Ethernet switches support VLAN interfaces configuration to forward packets in Layer 3. VLAN interface is a virtual interface in Layer 3 mode, used to realize the layer 3 communication between different VLANs, and does not exist on a switch as a physical entity. Each VLAN has a VLAN interface, which can forward packets of the local VLAN to the destination IP addresses at the network layer. Normally, since VLANs can isolate broadcast domains, each VLAN corresponds to an IP network segment. And a VLAN interface serves as the gateway of the segment to forward packets in Layer 3 based on IP addresses.
VLAN Classification
Depending on how VLANs are established, VLANs fall into the following six categories. Port-based VLANs MAC address-based VLANs Protocol-based VLANs IP-subnet-based VLANs Policy-based VLANs Other types At present, the Switch 4200G series switches support the port-based VLANs.
Port-Based VLAN
Port-based VLAN technology introduces the simplest way to classify VLANs. You can assign the ports on the device to different VLANs. Thus packets received on a port will be transmitted through the corresponding VLAN only, so as to isolate hosts to different broadcast domains and divide them into different virtual workgroups. Ports on Ethernet switches have the three link types: access, trunk, and hybrid. For the three types of ports, the process of being added into a VLAN and the way of forwarding packets are different. Port-based VLANs are easy to implement and manage and applicable to hosts with relatively fixed positions.
1-4
An access port can belong to only one VLAN. Usually, ports directly connected to PCs are configured as access ports. A trunk port can carry multiple VLANs to receive and send traffic for them. Except traffic of the default VLAN, traffic passes through a trunk port will be VLAN tagged. Usually, ports connecting network devices are configured as trunk ports to allow members of the same VLAN to communicate with each other across multiple network devices. Like a trunk port, a hybrid port can carry multiple VLANs to receive and send traffic for them. Unlike a trunk port, a hybrid port allows traffic of all VLANs to pass through VLAN untagged. You can configure a port connected to a network device or user terminal as a hybrid port for access link connectivity or trunk connectivity.
A hybrid port allows the packets of multiple VLANs to be sent untagged, but a trunk port only allows the packets of the default VLAN to be sent untagged.
Before assigning an access or hybrid port to a VLAN, create the VLAN first.
1-5
Table 1-1 Packet processing of an access port Processing of an incoming packet For an untagged packet Receive the packet and tag the packet with the default VLAN tag. For a tagged packet If the VLAN ID is just the default VLAN ID, receive the packet. If the VLAN ID is not the default VLAN ID, discard the packet. Processing of an outgoing packet Strip the tag from the packet and send the packet.
Table 1-2 Packet processing of a trunk port Processing of an incoming packet For an untagged packet If the port has already been added to its default VLAN, tag the packet with the default VLAN tag and then forward the packet. If the port has not been added to its default VLAN, discard the packet. For a tagged packet If the VLAN ID is one of the VLAN IDs allowed to pass through the port, receive the packet. If the VLAN ID is not one of the VLAN IDs allowed to pass through the port, discard the packet. Processing of an outgoing packet If the VLAN ID is just the default VLAN ID, strip off the tag and send the packet. If the VLAN ID is not the default VLAN ID, keep the original tag unchanged and send the packet.
Table 1-3 Packet processing of a hybrid port Processing of an incoming packet For an untagged packet If the port has already been added to its default VLAN, tag the packet with the default VLAN tag and then forward the packet. If the port has not been added to its default VLAN, discard the packet. For a tagged packet If the VLAN ID is one of the VLAN IDs allowed to pass through the port, receive the packet. If the VLAN ID is not one of the VLAN IDs allowed to pass through the port, discard the packet. Processing of an outgoing packet Send the packet if the VLAN ID is allowed to pass through the port. Use the port hybrid vlan command to configure whether the port keeps or strips off the tags when sending packets of a VLAN (including the default VLAN).
1-6
VLAN Configuration
When configuring a VLAN, go to these sections for information you are interested in: VLAN Configuration Configuring a Port-Based VLAN
VLAN Configuration
VLAN Configuration Task List
Complete the following tasks to configure VLAN: Task Basic VLAN Configuration Basic VLAN Interface Configuration Displaying VLAN Configuration Required Optional Optional Remarks
2-1
VLAN 1 is the system default VLAN, which needs not to be created and cannot be removed, either. The VLAN you created in the way described above is a static VLAN. On the switch, there are dynamic VLANs which are registered through GVRP. For details, refer to GVRP part of this manual. When you use the vlan command to create VLANs, if the destination VLAN is an existing dynamic VLAN, it will be transformed into a static VLAN and the switch will output the prompt information.
Configuration procedure
Follow these steps to perform basic VLAN interface configuration: To do... Enter system view Create a VLAN interface and enter VLAN interface view Use the command... system-view interface Vlan-interface vlan-id Required By default, there is no VLAN interface on a switch. Optional Specify the description string for the current VLAN interface description text By default, the description string of a VLAN interface is the name of this VLAN interface. Vlan-interface1 Interface for example. Remarks
2-2
To do...
Remarks
shutdown
undo shutdown
By default, the VLAN interface is enabled. In this case, the VLAN interfaces status is determined by the status of the ports in the VLAN, that is, if all ports of the VLAN are down, the VLAN interface is down (disabled); if one or more ports of the VLAN are up, the VLAN interface is up (enabled). If you disable the VLAN interface, the VLAN interface will always be down, regardless of the status of the ports in the VLAN.
The operation of enabling/disabling a VLANs VLAN interface does not influence the physical status of the Ethernet ports belonging to this VLAN.
2-3
Use the command system-view interface interface-type interface-number port link-type { access | hybrid | trunk } Required
Remarks
To change the link type of a port from trunk to hybrid or vice versa, you need to set the link type to access first.
Follow these steps to assign an Ethernet port to one or multiple VLANs: To do Enter system view Enter Ethernet port view Assign the port to one or multiple VLANs Access port Trunk port Hybrid port system-view interface interface-type interface-number port access vlan vlan-id port trunk permit vlan { vlan-id-list | all } port hybrid vlan vlan-id-list { tagged | untagged } Use the command Optional By default, all Ethernet ports belong to VLAN 1. Remarks
When assigning an access or hybrid port to a VLAN, make sure the VLAN already exists.
2)
In VLAN view
Follow these steps to assign one or multiple access ports to a VLAN in VLAN view: To do Enter system view Use the command system-view Required Enter VLAN view vlan vlan-id If the specified VLAN does not exist, this command creates the VLAN first. Remarks
2-4
Remarks
After configuring the default VLAN for a trunk or hybrid port, you need to use the port trunk permit command or the port hybrid vlan command to configure the port to allow traffic of the default VLAN to pass through. Otherwise, the port cannot forward traffic of the default VLAN, nor can it receive VLAN untagged packets. The local and remote trunk (or hybrid) ports must use the same default VLAN ID for the traffic of the default VLAN to be transmitted properly.
2-5
The devices within each VLAN can communicate with each other but that in different VLANs cannot communicate with each other directly.
Network diagram
Figure 2-1 Network diagram for VLAN configuration
Configuration procedure
Configure Switch A. # Create VLAN 101, specify its descriptive string as DMZ, and add GigabitEthernet1/0/1 to VLAN 101.
<SwitchA> system-view [SwitchA] vlan 101 [SwitchA-vlan101] description DMZ [SwitchA-vlan101] port GigabitEthernet 1/0/1 [SwitchA-vlan101] quit
Configure Switch B. # Create VLAN 101, specify its descriptive string as DMZ, and add GigabitEthernet1/0/11 to VLAN 101.
<SwitchB> system-view [SwitchB] vlan 101 [SwitchB-vlan101] description DMZ [SwitchB-vlan101] port GigabitEthernet 1/0/11 [SwitchB-vlan101] quit
Configure the link between Switch A and Switch B. Because the link between Switch A and Switch B need to transmit data of both VLAN 101 and VLAN 102, you can configure the ports at the end of the link as trunk ports and permit packets of the two VLANs to pass through.
2-6
2-7
Table of Contents
1 Static Routing Configuration1-1 Introduction 1-1 Routing Table 1-1 Static Route 1-2 Default Route1-2 Configuring a Static Route 1-3 Displaying and Maintaining a Routing Table1-3 Static Route Configuration Example 1-4 Basic Static Route Configuration Example1-4
Introduction
Routing Table
Routing table
Routing tables play a key role in routing. Each router maintains a routing table, and each entry in the table specifies which physical interface a packet destined for a certain destination should go out to reach the next hop or the directly connected destination. Routes in a routing table can be divided into three categories by origin: Direct routes: Routes discovered by data link protocols, also known as interface routes. Static routes: Routes that are manually configured. Dynamic routes: Routes that are discovered dynamically by routing protocols.
1-1
17.0.0.0
17.0.0.3
Switch F
11.0.0.2
16.0.0.0
14.0.0.3 16.0.0.1 14.0.0.2 Switch B 15.0.0.2 Switch E 14.0.0.1 14.0.0.4
11.0.0.0
11.0.0.1
14.0.0.0
Switch G 12.0.0.1
15.0.0.0
13.0.0.2 15.0.0.1 13.0.0.3 Switch C
12.0.0.0
12.0.0.2
13.0.0.0
13.0.0.1 Switch H
Interface 2 1 1 3 3 3 2
Static Route
A static route is a manually configured. If a networks topology is simple, you only need to configure static routes for the network to work normally. The proper configuration and usage of static routes can improve network performance and ensure bandwidth for important network applications. The disadvantage of using static routes is that they cannot adapt to network topology changes. If a fault or a topological change occurs in the network, the routes will be unreachable and the network breaks. In this case, the network administrator has to modify the static routes manually.
Default Route
If the destination address of a packet fails to match any entry in the routing table, the packet will be discarded. After a default route is configured on a switch, any packet whose destination IP address matches no entry in the routing table can be forwarded to a designated upstream switch. A switch selects the default route only when it cannot find any matching entry in the routing table. If the destination address of a packet fails to match any entry in the routing table, the switch selects the default route to forward the packet.
1-2
If there is no default route and the destination address of the packet fails to match any entry in the routing table, the packet will be discarded and an ICMP packet will be sent to the source to report that the destination or the network is unreachable. The network administrator can configure a default route with both destination and mask being 0.0.0.0. The router forwards any packet whose destination address fails to match any entry in the routing table to the next hop of the default static route.
ip route-static ip-address { mask | mask-length } { interface-type interface-number | next-hop } [ preference preference-value ] [ reject | blackhole ] [ description text ]
Required
Display detailed information about the routing table Display the routes leading to a specified IP address Display the routes leading to a specified IP address range Display the routing information of the specified protocol Display the routes that match a specified basic access control list (ACL) Display the routes that match a specified IP prefix Display the routing table in a tree structure
display ip routing-table verbose display ip routing-table ip-address [ mask ] [ longer-match ] [ verbose ] display ip routing-table ip-address1 mask1 ip-address2 mask2 [ verbose ] display ip routing-table protocol protocol [ inactive | verbose ] display ip routing-table acl acl-number [ verbose ] display ip routing-table ip-prefix ip-prefix-name [ verbose ] display ip routing-table radix
1-3
To do Display the statistics on the routing table Clear statistics about a routing table Delete all static routes
Use the command display ip routing-table statistics reset ip routing-table statistics protocol { all | protocol } delete static-routes all
Remarks
Use the reset command in user view Use the delete command in system view.
Configuration procedure
1) 2) Configuring IP addresses for interfaces (omitted) Configuring static routes
3)
1-4
The default gateways for the three hosts A, B and C are 1.1.2.3, 1.1.6.1 and 1.1.3.1 respectively. The configuration procedure is omitted. 4) Display the configuration.
1-5
Table of Contents
1 Voice VLAN Configuration1-1 Voice VLAN Overview1-1 How an IP Phone Works 1-1 How Switch 4200G Series Switches Identify Voice Traffic 1-3 Setting the Voice Traffic Transmission Priority 1-3 Configuring Voice VLAN Assignment Mode of a Port 1-4 Support for Voice VLAN on Various Ports1-4 Security Mode of Voice VLAN 1-6 Voice VLAN Configuration 1-7 Configuration Prerequisites 1-7 Configuring the Voice VLAN to Operate in Automatic Voice VLAN Assignment Mode1-7 Configuring the Voice VLAN to Operate in Manual Voice VLAN Assignment Mode 1-8 Displaying and Maintaining Voice VLAN1-10 Voice VLAN Configuration Example 1-11 Voice VLAN Configuration Example (Automatic Mode) 1-11 Voice VLAN Configuration Example (Manual Mode) 1-13
The following part only describes the common way for an IP phone to acquire an IP address. The detailed process may vary by manufacture. Refer to the corresponding user manual for the detailed information.
When an IP phone applies for an IP address from a DHCP server, the IP phone can also apply for the following extensive information from the DHCP server through the Option184 field: IP address of the network call processor (NCP) IP address of the secondary NCP server Voice VLAN configuration Failover call routing Following describes the way a typical IP phone acquires an IP address.
1-1
As shown in Figure 1-1, the IP phone needs to work in conjunction with the DHCP server and the NCP to establish a path for voice data transmission. An IP phone goes through the following three phases to become capable of transmitting voice data. 2) After the IP phone is powered on, it sends an untagged DHCP request message containing four special requests in the Option 184 field besides the request for an IP address. The message is broadcast in the default VLAN of the receiving port. After receiving the DHCP request message, DHCP Server 1, which resides in the default VLAN of the port receiving the message, responds as follows: If DHCP Server 1 does not support Option 184, it returns the IP address assigned to the IP phone but ignores the other four special requests in the Option 184 field. Without information about voice VLAN, the IP phone can only send untagged packets in the default VLAN of the port the IP phone is connected to. In this case, you need to manually configure the default VLAN of the port as a voice VLAN.
In cases where an IP phone obtains an IP address from a DHCP server that does not support Option 184, the IP phone directly communicates through the gateway after it obtains an IP address. It does not go through the steps described below.
If DHCP Server 1 supports Option 184, it returns the IP address assigned to the IP phone, the IP address of the NCP, the voice VLAN ID, and so on. 3) On acquiring the voice VLAN ID and NCP address from DHCP Server 1, the IP phone communicates with the specified NCP to download software, ignores the IP address assigned by DHCP Server 1, and sends a new DHCP request message carrying the voice VLAN tag to the voice VLAN. 4) After receiving the DHCP request, DHCP Server 2 residing in the voice VLAN assigns a new IP address to the IP phone and sends a tagged response message to the IP phone. After the IP phone receives the tagged response message, it sends voice data packets tagged with the voice VLAN tag to communicate with the voice gateway. In this case, the port connecting to the IP phone must be configured to allow the packets tagged with the voice VLAN tag to pass.
1-2
An untagged packet carries no VLAN tag. A tagged packet carries the tag of a VLAN.
To set an IP address and a voice VLAN for an IP phone manually, just make sure that the voice VLAN ID to be set is consistent with that of the switch and the NCP is reachable to the IP address to be set.
An OUI address is a globally unique identifier assigned to a vendor by IEEE. You can determine which vendor a device belongs to according to the OUI address which forms the first 24 bits of a MAC address. Switch 4200G series Ethernet switches support OUI address mask configuration. You can adjust the matching depth of MAC address by setting different OUI address masks.
The following table lists the five default OUI addresses on Switch 4200G series switches. Table 1-1 Default OUI addresses pre-defined on the switch Number 1 2 3 4 5 OUI address 0003-6b00-0000 000f-e200-0000 00d0-1e00-0000 00e0-7500-0000 00e0-bb00-0000 Vendor Cisco phones H3C Aolynk phones Pingtel phones Polycom phones 3Com phones
1-3
For more information about CoS and DSCP precedence values, refer to the QoS part of the manual.
If the voice traffic transmitted by an IP voice device carries VLAN tags, and 802.1x authentication and guest VLAN is enabled on the port which the IP voice device is connected to, assign different VLAN IDs for the voice VLAN, the default VLAN of the port, and the 802.1x guest VLAN to ensure the effective operation of these functions.
1-4
Table 1-2 Matching relationship between port types and voice devices capable of acquiring IP address and voice VLAN automatically Voice VLAN assignment mode Voice traffic type Port type Access Not supported Supported Tagged voice traffic Automatic Hybrid Trunk Make sure the default VLAN of the port exists and is not a voice VLAN, and the access port permits the traffic of the default VLAN. Supported Make sure the default VLAN of the port exists and is not a voice VLAN, and the default VLAN is in the list of the VLANs whose traffic is permitted by the access port. Not supported, because the default VLAN of the port must be a voice VLAN and the access port is in the voice VLAN. This can be done by adding the port to the voice VLAN manually. Not supported Supported Trunk Tagged voice traffic Hybrid Manual Access Make sure the default VLAN of the port exists and is not a voice VLAN, and the access port permits the traffic of the default VLAN and the voice VLAN. Supported Make sure the default VLAN of the port exists and is not a voice VLAN, the traffic of the default VLAN is permitted to pass through the port, and the voice VLAN is in the list of the tagged VLANs whose traffic is permitted by the port. Supported Make sure the default VLAN of the port is a voice VLAN. Supported Untagge d voice traffic Trunk Make sure the default VLAN of the port is a voice VLAN and the port permits the traffic of the VLAN. Supported Hybrid Make sure the default VLAN of the port is a voice VLAN and is in the list of untagged VLANs whose traffic is permitted by the port. Supported or not
IP phones acquiring IP address and voice VLAN through manual configuration can forward only tagged traffic, so the matching relationship is relatively simple, as shown in Table 1-3:
1-5
Table 1-3 Matching relationship between port types and voice devices acquiring voice VLAN through manual configuration Voice VLAN assignment mode Access Port type Supported or not Not supported Supported Trunk Make sure the default VLAN of the port exists and is not a voice VLAN, and the access port permits the traffic of the default VLAN. Supported Make sure the default VLAN of the port exists and is not a voice VLAN, and the default VLAN is in the list of the tagged VLANs whose traffic is permitted by the access port. Not supported Supported Trunk Make sure the default VLAN of the port exists and is not a voice VLAN, and the access port permits the traffic of the default VLAN. Supported Make sure the default VLAN of the port exists and is not a voice VLAN, and the default VLAN and the voice VLAN is in the list of the tagged VLANs whose traffic is permitted by the access port.
Automatic
Hybrid
Access
Manual
Hybrid
1-6
The following table presents how a packet is handled when the voice VLAN is operating in security mode and normal mode. Table 1-4 How a packet is handled when the voice VLAN is operating in different modes Voice VLAN Mode Packet Type Untagged packet Packet carrying the voice VLAN tag Security Packet carrying any other VLAN tag Processing Method If the source MAC address of the packet matches the OUI list, the packet is transmitted in the voice VLAN. Otherwise, the packet is dropped. The packet is forwarded or dropped based on whether the receiving port is assigned to the carried VLAN. The processing method is irrelevant to the voice VLAN mode (security or normal). The source MAC address of the packet is not checked. All such packets can be transmitted in the voice VLAN. The packet is forwarded or dropped based on whether the port is assigned to the carried VLAN. The processing method is irrelevant to the voice VLAN mode (security or normal).
Untagged packet Packet carrying the voice VLAN tag Normal Packet carrying any other VLAN tag
Configuring the Voice VLAN to Operate in Automatic Voice VLAN Assignment Mode
Follow these steps to configure a voice VLAN to operate in automatic voice VLAN assignment mode: To do Enter system view Use the command system-view voice vlan mac-address oui mask oui-mask [ description text ] Optional Set an OUI address that can be identified by the voice VLAN By default, the switch determines the voice traffic according to the default OUI address. Optional voice vlan security enable By default, the voice VLAN security mode is enabled. Remarks
1-7
To do Set the voice VLAN aging timer Enable the voice VLAN function globally Enter Ethernet port view Enable the voice VLAN function on a port
Remarks
voice vlan vlan-id enable interface interface-type interface-number voice vlan enable
A port working in automatic voice VLAN assignment mode cannot be assigned to the voice VLAN manually. Therefore, if a VLAN is configured as the voice VLAN and a protocol-based VLAN at the same time, the protocol-based VLAN function cannot be bound with the port. For information about protocol-based VLANs, refer to VLAN Configuration in this manual. For a port operating in automatic voice VLAN assignment mode, its default VLAN cannot be configured as the voice VLAN; otherwise the system prompts you for unsuccessful configuration.
When the voice VLAN is working normally, if the device restarts, in order to make the established voice connections work normally, the system does not need to be triggered by the voice traffic to add the port in automatic voice VLAN assignment mode to the local devices of the voice VLAN but does so immediately after the restart.
Configuring the Voice VLAN to Operate in Manual Voice VLAN Assignment Mode
Follow these steps to configure a voice VLAN to operate in manual voice VLAN assignment mode:
1-8
To do Enter system view Set an OUI address that can be identified by the voice VLAN
Use the command system-view voice vlan mac-address oui mask oui-mask [ description text ]
Remarks
Optional Without this address, the default OUI address is used. Optional
Set the voice VLAN aging timer Enable the voice VLAN function globally Enter port view
voice vlan aging minutes voice vlan vlan-id enable interface interface-type interface-number voice vlan enable
Quit to system view Enter VLAN view Access port Add a port in manual voice VLAN assignm ent mode to the voice VLAN Add the port to the VLAN Enter port view
quit vlan vlan-id port interface-list interface interface-type interface-num port trunk permit vlan vlan-id port hybrid vlan vlan-id { tagged | untagged }
Optional port trunk pvid vlan vlan-id port hybrid pvid vlan vlan-id Refer to Table 1-2 to determine whether or not this operation is needed.
1-9
The voice VLAN function can be enabled for only one VLAN at one time. If the Link Aggregation Control Protocol (LACP) is enabled on a port, voice VLAN feature cannot be enabled on it. Voice VLAN function can be enabled only for the static VLAN. A dynamic VLAN cannot be configured as a voice VLAN. When ACL number applied to a port reaches to its threshold, voice VLAN cannot be enabled on this port. You can use the display voice vlan error-info command to locate such ports. When a voice VLAN operates in security mode, the device in it permits only the packets whose source addresses are the identified voice OUI addresses. Packets whose source addresses cannot be identified, including certain authentication packets (such as 802.1x authentication packets), will be dropped. Therefore, you are suggested not to transmit both voice data and service data in a voice VLAN. If you have to do so, make sure that the voice VLAN does not operate in security mode. The voice VLAN legacy feature realizes the communication between 3Com device and other vendor's voice device by automatically adding the voice VLAN tag to the voice data coming from other vendors voice device. The voice vlan legacy command can be executed before voice VLAN is enabled globally and on a port, but it takes effect only after voice VLAN is enabled globally and on the port.
To assign a trunk port or a hybrid port to the voice VLAN, refer to VLAN Configuration of this manual for the related command.
display voice vlan status display voice vlan oui display vlan vlan-id
In any view
1-10
Network diagram
Device A Device B
Internet
GE1/0/1 GE1/0/2 VLAN 2 GE1/0/1
0755-2002
PC A MAC: 0022-1100-0002
PC B MAC: 0022-2200-0002
Figure 1-2 Network diagram for voice VLAN configuration (automatic mode)
Configuration procedure
# Create VLAN 2.
<DeviceA> system-view [DeviceA] vlan 2
# Since GigabitEthernet 1/0/1 may receive both voice traffic and data traffic at the same time, to ensure the quality of voice packets and effective bandwidth use, configure voice VLANs to work in security mode, that is, configure the voice VLANs to transmit only voice packets. (Optional. By default, voice VLANs work in security mode.)
[DeviceA] voice vlan security enable
1-11
# Configure the allowed OUI addresses as MAC addresses prefixed by 0011-1100-0000 or 0011-2200-0000. In this way, Device A identifies packets whose MAC addresses match any of the configured OUI addresses as voice packets.
[DeviceA] voice vlan mac-address 0011-1100-0001 mask ffff-ff00-0000 description IP phone A [DeviceA] voice vlan mac-address 0011-2200-0001 mask ffff-ff00-0000 description IP phone B
# Configure GigabitEthernet 1/0/1 to operate in automatic voice VLAN assignment mode. (Optional. By default, a port operates in automatic voice VLAN assignment mode.)
[DeviceA] interface gigabitethernet 1/0/1 [DeviceA-GigabitEthernet1/0/1] voice vlan mode auto
Verification
# Display the OUI addresses, OUI address masks, and description strings supported currently.
<DeviceA> display voice vlan oui Oui Address 0003-6b00-0000 000f-e200-0000 0011-1100-0000 0011-2200-0000 00d0-1e00-0000 00e0-7500-0000 00e0-bb00-0000 Mask ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 Description Cisco phone H3C Aolynk phone IP phone A IP phone B Pingtel phone Polycom phone 3Com phone
1-12
Network diagram
Figure 1-3 Network diagram for voice VLAN configuration (manual mode)
Device A Device B
Internet
VLAN 2 GE1/0/1 VLAN 2
Configuration procedure
# Enable the security mode for the voice VLAN so that the ports in the voice VLAN permit valid voice packets only. This operation is optional. The security mode is enabled by default.
<DeviceA> system-view [DeviceA] voice vlan security enable
# Add a user-defined OUI address 0011-2200-000 and set the description string to test.
[DeviceA] voice vlan mac-address 0011-2200-0000 mask ffff-ff00-0000 description test
# Configure the voice VLAN as the default VLAN of GigabitEthernet 1/0/1, and add the voice VLAN to the list of untagged VLANs whose traffic is permitted by the port.
[DeviceA-GigabitEthernet1/0/1] port hybrid pvid vlan 2 [DeviceA-GigabitEthernet1/0/1] port hybrid vlan 2 untagged
1-13
Verification
# Display the OUI addresses, the corresponding OUI address masks and the corresponding description strings that the system supports.
<DeviceA> display voice vlan oui Oui Address 0003-6b00-0000 000f-e200-0000 0011-2200-0000 00d0-1e00-0000 00e0-7500-0000 00e0-bb00-0000 Mask ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 ffff-ff00-0000 Description Cisco phone H3C Aolynk phone test Pingtel phone Polycom phone 3Com phone
-------------------------------GigabitEthernet1/0/1 MANUAL
1-14
Table of Contents
1 GVRP Configuration 1-1 Introduction to GVRP 1-1 GARP1-1 GVRP1-4 Protocol Specifications 1-4 GVRP Configuration1-4 GVRP Configuration Tasks 1-4 Enabling GVRP 1-4 Configuring GVRP Timers 1-5 Configuring GVRP Port Registration Mode 1-6 Displaying and Maintaining GVRP1-7 GVRP Configuration Example 1-7 GVRP Configuration Example1-7
GVRP Configuration
When configuring GVRP, go to these sections for information you are interested in: Introduction to GVRP GVRP Configuration Displaying and Maintaining GVRP GVRP Configuration Example
Introduction to GVRP
GARP VLAN registration protocol (GVRP) is an implementation of generic attribute registration protocol (GARP). GARP is introduced as follows.
GARP
The generic attribute registration protocol (GARP), provides a mechanism that allows participants in a GARP application to distribute, propagate, and register with other participants in a bridged LAN the attributes specific to the GARP application, such as the VLAN or multicast attribute. GARP itself does not exist on a device as an entity. GARP-compliant application entities are called GARP applications. One example is GVRP. When a GARP application entity is present on a port on your device, this port is regarded a GARP application entity.
GARP members communicate with each other through the messages exchanged between them. The messages performing important functions for GARP fall into three types: Join, Leave and LeaveAll. When a GARP entity wants its attribute information to be registered on other devices, it sends Join messages to these devices. A GARP entity also sends Join messages when it receives Join messages from other entities or it wants some of its statically configured attributes to be registered on other GARP entities. When a GARP entity wants some of its attributes to be deregistered on other devices, it sends Leave messages to these devices. A GARP entity also sends Leave messages when it receives Leave messages from other entities for deregistering some attributes or it has some attributes statically deregistered. Once a GARP entity is launched, the LeaveAll timer is triggered at the same time. The GARP entity sends out LeaveAll messages after the timer times out. LeaveAll messages deregister all the attributes, through which the attribute information of the entity can be registered again on the other GARP entities. Leave messages, LeaveAll messages, together with Join messages ensure attribute information can be deregistered and re-registered. Through message exchange, all the attribute information to be registered can be propagated to all the GARP-enabled switches in the same LAN.
1-1
2)
GARP timers
Timers determine the intervals of sending different types of GARP messages. GARP defines four timers to control the period of sending GARP messages. Hold: When a GARP entity receives a piece of registration information, it does not send out a Join message immediately. Instead, to save the bandwidth resources, it starts the Hold timer and puts all received registration information before the timer times out into one Join message and sends out the message after the timer times out. Join: To make sure the devices can receive Join messages, each Join message is sent twice. If the first Join message sent is not responded for a specific period, a second one is sent. The period is determined by this timer. Leave: When a GARP entity expects to deregister a piece of attribute information, it sends out a Leave message. Any GARP entity receiving this message starts its Leave timer, and deregisters the attribute information if it does not receives a Join message again before the timer times out. LeaveAll: Once a GARP entity starts up, it starts the LeaveAll timer, and sends out a LeaveALL message after the timer times out, so that other GARP entities can re-register all the attribute information on this entity. After that, the entity restarts the LeaveAll timer to begin a new cycle.
The settings of GARP timers apply to all GARP applications, such as GVRP, on a LAN. Unlike other three timers, which are set on a port basis, the LeaveAll timer is set in system view and takes effect globally. A GARP application entity may send LeaveAll messages at the interval set by its LeaveAll timer or the LeaveAll timer on another device on the network, whichever is smaller. This is because each time a device on the network receives a LeaveAll message it resets its LeaveAll timer.
1-2
The following table describes the fields of a GARP packet. Table 1-1 Description of GARP packet fields Field Protocol ID Message Description Protocol ID Each message consists of two parts: Attribute Type and Attribute List. Defined by the specific GARP application It contains multiple attributes. Each general attribute consists of three parts: Attribute Length, Attribute Event, and Attribute Value. Each LeaveAll attribute consists of two parts: Attribute Length and LeaveAll Event. Attribute Length The length of the attribute 2 to 255 (in bytes) 0: LeaveAll Event 1: JoinEmpty Attribute Event The event described by the attribute 2: JoinIn 3: LeaveEmpty 4: LeaveIn 5: Empty For GVRP packets, the value of this field is the VLAN ID; however, for LeaveAll messages, this field is invalid. The value of this field is fixed to 0x00. 1 The attribute type of GVRP is 0x01. Value
Attribute
Attribute Value
End Mark
1-3
GVRP
As an implementation of GARP, GARP VLAN registration protocol (GVRP) maintains dynamic VLAN registration information and propagates the information to the other switches through GARP. With GVRP enabled on a device, the VLAN registration information received by the device from other devices is used to dynamically update the local VLAN registration information, including the information about the VLAN members, the ports through which the VLAN members can be reached, and so on. The device also propagates the local VLAN registration information to other devices so that all the devices in the same LAN can have the same VLAN information. VLAN registration information propagated by GVRP includes static VLAN registration information, which is manually configured locally on each device, and dynamic VLAN registration information, which is received from other devices. GVRP has the following three port registration modes: Normal, Fixed, and Forbidden, as described in the following. Normal. A port in this mode can dynamically register/deregister VLANs and propagate dynamic/static VLAN information. Fixed. A port in this mode cannot register/deregister VLANs dynamically. It only propagates static VLAN information. Besides, the port permits only static VLANs, that is, it propagates only static VLAN information to the other GARP members. Forbidden. A port in this mode cannot register/deregister VLANs dynamically. It permits only the default VLAN (namely, VLAN 1), that is, the port propagates only the information about VLAN 1 to the other GARP members.
Protocol Specifications
GVRP is defined in IEEE 802.1Q standard.
GVRP Configuration
GVRP Configuration Tasks
Complete the following tasks to configure GVRP: Task Enabling GVRP Configuring GVRP Timers Configuring GVRP Port Registration Mode Required Optional Optional Remarks
Enabling GVRP
Configuration Prerequisite
The port on which GVRP will be enabled must be set to a trunk port.
Configuration procedure
Follow these steps to enable GVRP:
1-4
Use the command ... system-view gvrp interface interface-type interface-number gvrp Required
Remarks
s After you enable GVRP on a trunk port, you cannot change the port to a different type. Use the port trunk permit all command to permit the traffic of all dynamically registered VLANs to pass through a trunk port with GVRP enabled.
Note that: The setting of each timer must be a multiple of 5 (in centiseconds). The timeout ranges of the timers vary depending on the timeout values you set for other timers. If you want to set the timeout time of a timer to a value out of the current range, you can set the timeout time of the associated timer to another value to change the timeout range of this timer. The following table describes the relations between the timers:
1-5
Table 1-2 Relations between the timers Timer Lower threshold Upper threshold This upper threshold is less than or equal to one-half of the timeout time of the Join timer. You can change the threshold by changing the timeout time of the Join timer. This upper threshold is less than one-half of the timeout time of the Leave timer. You can change the threshold by changing the timeout time of the Leave timer. This upper threshold is less than the timeout time of the LeaveAll timer. You can change the threshold by changing the timeout time of the LeaveAll timer.
Hold
10 centiseconds
Join
This lower threshold is greater than or equal to twice the timeout time of the Hold timer. You can change the threshold by changing the timeout time of the Hold timer. This lower threshold is greater than twice the timeout time of the Join timer. You can change the threshold by changing the timeout time of the Join timer. This lower threshold is greater than the timeout time of the Leave timer. You can change threshold by changing the timeout time of the Leave timer.
Leave
LeaveAll
32,765 centiseconds
The following are recommended GVRP timer settings: GARP hold timer: 100 centiseconds (1 second) GARP Join timer: 600 centiseconds (6 seconds) GARP Leave timer: 3000 centiseconds (30 seconds) GARP LeaveAll timer: 120000 centiseconds (2 minutes)
1-6
Network diagram
Figure 1-2 Network diagram for GVRP configuration
Configuration procedure
1) Configure Switch A
# Configure GigabitEthernet1/0/1 to be a trunk port and to permit the packets of all the VLANs.
[SwitchA] interface GigabitEthernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] port link-type trunk
1-7
# Configure GigabitEthernet1/0/2 to be a trunk port and to permit the packets of all the VLANs.
[SwitchA] interface GigabitEthernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] port link-type trunk [SwitchA-GigabitEthernet1/0/2] port trunk permit vlan all
# Configure GigabitEthernet1/0/3 to be a trunk port and to permit the packets of all the VLANs.
[SwitchA] interface GigabitEthernet 1/0/3 [SwitchA-GigabitEthernet1/0/3] port link-type trunk [SwitchA-GigabitEthernet1/0/3] port trunk permit vlan all
2)
Configure Switch B
# The configuration procedure of Switch B is similar to that of Switch A and is thus omitted. 3) Configure Switch C
# Enable GVRP on Switch C, which is similar to that of Switch A and is thus omitted. # Create VLAN 5.
[SwitchC] vlan 5 [SwitchC-vlan5] quit
4)
Configure Switch D
# Enable GVRP on Switch D, which is similar to that of Switch A and is thus omitted. # Create VLAN 8.
[SwitchD] vlan 8 [SwitchD-vlan8] quit
5)
Configure Switch E
# Enable GVRP on Switch E, which is similar to that of Switch A and is thus omitted. # Create VLAN 5 and VLAN 7.
[SwitchE] vlan 5 [SwitchE-vlan5] quit [SwitchE] vlan 7 [SwitchE-vlan7] quit
6)
Display the VLAN information dynamically registered on Switch A, Switch B, and Switch E.
1-8
5, 7, 8,
7)
Configure GigabitEthernet1/0/1 on Switch E to operate in fixed GVRP registration mode and display the VLAN information dynamically registered on Switch A, Switch B, and Switch E.
8)
Configure GigabitEthernet1/0/1 on Switch E to operate in forbidden GVRP registration mode and display the VLAN registration information dynamically registered on Switch A, Switch B, and Switch E.
1-9
5, 8,
1-10
Table of Contents
1 Port Basic Configuration 1-1 Ethernet Port Configuration 1-1 Combo Port Configuration 1-1 Initially Configuring a Port 1-1 Configuring Port Auto-Negotiation Speed 1-2 Limiting Traffic on individual Ports1-3 Enabling Flow Control on a Port1-3 Duplicating the Configuration of a Port to Other Ports 1-4 Configuring Loopback Detection for an Ethernet Port1-4 Enabling Loopback Test1-5 Enabling the System to Test Connected Cable 1-6 Configuring the Interval to Perform Statistical Analysis on Port Traffic1-7 Disabling Up/Down Log Output on a Port 1-7 Configuring a Port Group1-8 Displaying and Maintaining Basic Port Configuration 1-9
1-1
To do... Set the speed of the Ethernet port Set the medium dependent interface (MDI) mode of the Ethernet port
Remarks
By default, the speed of an Ethernet port is determined through auto-negotiation (the auto keyword). Optional
Set the maximum frame size allowed on the Ethernet port to 9,216 bytes
jumboframe enable
By default, the maximum frame size allowed on an Ethernet is 9,216 bytes. To set the maximum frame size allowed on an Ethernet port to 1,522 bytes, use the undo jumboframe enable command.
The speed and mdi commands are not available on the combo port. The mdi command is not available on the Ethernet ports of the expansion interface card.
1-2
Only ports on the front panel of the device support the auto-negotiation speed configuration feature. And ports on the extended interface card do not support this feature currently. After you configure auto-negotiation speed(s) for a port, if you execute the undo speed command or the speed auto command, the auto-negotiation speed setting of the port restores to the default setting. The effect of executing speed auto 10 100 1000 equals to that of executing speed auto, that is, the port is configured to support all the auto-negotiation speeds: 10 Mbps, 100 Mbps, and 1000 Mbps.
Remarks
Required
If you specify a source aggregation group ID, the system will use the port with the smallest port number in the aggregation group as the source. If you specify a destination aggregation group ID, the configuration of the source port will be copied to all ports in the aggregation group and all ports in the group will have the same configuration as that of the source port.
1-4
To do... Enter system view Enable loopback detection globally Set the interval for performing port loopback detection Enter Ethernet port view Enable loopback port control on the trunk or hybrid port
Remarks
By default, loopback detection is disabled globally. Optional The default is 30 seconds. Optional By default, loopback port control is not enabled. Optional
Configure the system to run loopback detection on all VLANs of the current trunk or hybrid port
By default, the system runs loopback detection only on the default VLAN of the current trunk or hybrid port.
To enable loopback detection on a specific port, you must use the loopback-detection enable command in both system view and the specific port view. After you use the undo loopback-detection enable command in system view, loopback detection will be disabled on all ports. The commands of loopback detection feature cannot be configured with the commands of port link aggregation at the same time. The loopback-detection control enable command and the loopback-detection per-vlan enable command are not applicable to access ports. When the link type of a non-access port changes to access, the two commands already configured on the port become invalid automatically.
1-5
To do... Enter system view Enter Ethernet port view Enable loopback test
Use the command... system-view interface interface-type interface-number loopback { external | internal }
Remarks
Required
external: Performs external loop test. In the external loop test, self-loop headers must be used on the port of the switch ( for 1000M port, the self-loop header are made from eight cores of the 8-core cables, then the packets forwarded by the port will be received by itself.). The external loop test can locate the hardware failures on the port. internal: Performs internal loop test. In the internal loop test, self loop is established in the switching chip to locate the chip failure which is related to the port.
Note that: After you use the shutdown command on a port, the port cannot run loopback test. You cannot use the speed, duplex, mdi and shutdown commands on the ports running loopback test. Some ports do not support loopback test, and corresponding prompts will be given when you perform loopback test on them.
Optical port (including Combo optical port) does not support VCT (virtual-cable-test) function. Combo electrical port supports VCT function only when it is in UP condition (using undo shutdown command), normal Ethernet electrical port always supports this function.
1-6
Follow these steps to set the interval to perform statistical analysis on port traffic: To do... Enter system view Enter Ethernet port view Set the interval to perform statistical analysis on port traffic Use the command... system-view interface interface-type interface-number flow-interval interval Optional By default, this interval is 300 seconds. Remarks
1-7
Configuration examples
# In the default conditions, where UP/DOWN log output is enabled, execute the shutdown command or the undo shutdown command on GigabitEthernet 1/0/1. The Up/Down log information for GigabitEthernet 1/0/1 is generated and displayed on the terminal.
<Sysname> system-view System View: return to User View with Ctrl+Z. [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] shutdown %Apr 5 07:25:37:634 2000 Sysname L2INF/5/PORT LINK STATUS CHANGE:- 1 -
GigabitEthernet1/0/1 is DOWN [Sysname-GigabitEthernet1/0/1] undo shutdown %Apr 5 07:25:56:244 2000 Sysname L2INF/5/PORT LINK STATUS CHANGE:- 1 -
GigabitEthernet1/0/1 is UP
# Disable GigabitEthernet 1/0/1 from generating Up/Down log information and execute the shutdown command or the undo shutdown command on GigabitEthernet 1/0/1. No Up/Down log information is generated or output for GigabitEthernet 1/0/1.
[Sysname-GigabitEthernet1/0/1] undo enable log updown [Sysname-GigabitEthernet1/0/1] shutdown [Sysname-GigabitEthernet1/0/1] undo shutdown
A port can not be added to a port group if it has been added to an aggregation group, and vice versa.
1-8
display port-group group-id display brief interface [ interface-type [ interface-number ] ] [ | { begin | include | exclude } regular-expression ] display port combo
Available in user view Clear port statistics reset counters interface [ interface-type | interface-type interface-number ] After 802.1x is enabled on a port, clearing the statistics on the port will not work.
1-9
Table of Contents
1 Link Aggregation Configuration 1-1 Overview 1-1 Introduction to Link Aggregation1-1 Introduction to LACP 1-1 Consistency Considerations for the Ports in Aggregation1-1 Link Aggregation Classification1-2 Manual Aggregation Group 1-2 Static LACP Aggregation Group1-3 Dynamic LACP Aggregation Group1-3 Aggregation Group Categories 1-4 Link Aggregation Configuration1-6 Configuring a Manual Aggregation Group1-6 Configuring a Static LACP Aggregation Group 1-7 Configuring a Dynamic LACP Aggregation Group 1-8 Configuring a Description for an Aggregation Group 1-8 Displaying and Maintaining Link Aggregation Configuration 1-9 Link Aggregation Configuration Example1-9 Ethernet Port Aggregation Configuration Example 1-9
Overview
Introduction to Link Aggregation
Link aggregation aggregates multiple physical Ethernet ports into one logical link, also called an aggregation group. It allows you to increase bandwidth by distributing traffic across the member ports in the aggregation group. In addition, it provides reliable connectivity because these member ports can dynamically back up each other.
Introduction to LACP
The Link Aggregation Control Protocol (LACP) is defined in IEEE 802.3ad. It uses link aggregation control protocol data units (LACPDUs) for information exchange between LACP-enabled devices. With LACP enabled on a port, LACP notifies the following information of the port to its peer by sending LACPDUs: priority and MAC address of this system, priority, number and operation key of the port. Upon receiving the information, the peer compares the information with the information of other ports on the peer device to determine the ports that can be aggregated. In this way, the two parties can reach an agreement in adding/removing the port to/from a dynamic aggregation group. When aggregating ports, link aggregation control automatically assigns each port an operational key based on the port speed, duplex mode, and basic configurations described in Consistency Considerations for the Ports in Aggregation. In a manual or static link aggregation group, the selected ports are assigned the same operational key. In a dynamic link aggregation group, all member ports are assigned the same operational key.
1-1
Table 1-1 Consistency considerations for ports in an aggregation Category Considerations State of port-level STP (enabled or disabled) Attribute of the link (point-to-point or otherwise) connected to the port Port path cost STP STP priority STP packet format Loop protection Root protection Port type (whether the port is an edge port) QoS Link type 802.1p priority Traffic accounting Link type of the ports (trunk, hybrid, or access) GVRP state on ports (enabled or disabled) GVRP GVRP registration type GARP timer settings
There is a limit on the number of selected ports in an aggregation group. Therefore, if the number of the selected ports in an aggregation group exceeds the maximum number supported by the device, those with lower port numbers operate as the selected ports, and others as unselected ports. Among the selected ports in an aggregation group, the one with smallest port number operates as the master port. Other selected ports are the member ports.
are connected to the same peer device and have the same speed, duplex mode, and basic configurations, and their peer ports have the same configurations. Besides multiple-port aggregation groups, the system is also able to create single-port aggregation groups, each of which contains only one port. LACP is enabled on the member ports of dynamic aggregation groups.
For an aggregation group: When the rate or duplex mode of a port in the aggregation group changes, packet loss may occur on this port; When the rate of a port decreases, if the port belongs to a manual or static LACP aggregation group, the port will be switched to the unselected state; if the port belongs to a dynamic LACP aggregation group, deaggregation will occur on the port.
1-4
In general, the system only provides limited load-sharing aggregation resources, so the system needs to reasonably allocate the resources among different aggregation groups. The system always allocates hardware aggregation resources to the aggregation groups with higher priorities. When load-sharing aggregation resources are used up by existing aggregation groups, newly-created aggregation groups will be non-load-sharing ones. Load-sharing aggregation resources are allocated to aggregation groups in the following order: An aggregation group containing special ports which require hardware aggregation resources has higher priority than any aggregation group containing no special port. A manual or static aggregation group has higher priority than a dynamic aggregation group (unless the latter contains special ports while the former does not). For aggregation groups, the one that might gain higher speed if resources were allocated to it has higher priority than others. If the groups can gain the same speed, the one with smallest master port number has higher priority than other groups. When an aggregation group of higher priority appears, the aggregation groups of lower priorities release their hardware resources. For single-port aggregation groups, they can transceive packets normally without occupying aggregation resources
A load-sharing aggregation group contains at least two selected ports, but a non-load-sharing aggregation group can only have one selected port at most, while others are unselected ports.
1-5
The commands of link aggregation cannot be configured with the commands of port loopback detection feature at the same time. The ports where the mac-address max-mac-count command is configured cannot be added to an aggregation group. Contrarily, the mac-address max-mac-count command cannot be configured on a port that has already been added to an aggregation group. MAC-authentication-enabled ports and 802.1x-enabled ports cannot be added to an aggregation group. Mirroring destination ports and mirroring reflector ports cannot be added to an aggregation group. Ports configured with blackhole MAC addresses, static MAC addresses, multicast MAC addresses, or the static ARP protocol cannot be added to an aggregation group. Ports where the IP-MAC address binding is configured cannot be added to an aggregation group. Port-security-enabled ports cannot be added to an aggregation group. The port with Voice VLAN enabled cannot be added to an aggregation group. A port belonging to a port group cannot be added to an aggregation group. Conversely, a port belonging to an aggregation group cannot be added to a port group.
Note that: 1) When creating an aggregation group: If the aggregation group you are creating already exists but contains no port, its type will change to the type you set.
1-6
If the aggregation group you are creating already exists and contains ports, the possible type changes may be: changing from dynamic or static to manual, and changing from dynamic to static; and no other kinds of type change can occur. When you change a dynamic/static group to a manual group, the system will automatically disable LACP on the member ports. When you change a dynamic group to a static group, the system will remain the member ports LACP-enabled. 2) When a manual or static aggregation group contains only one port, you cannot remove the port unless you remove the whole aggregation group.
When you add an LACP-enabled port to a manual aggregation group, the system will automatically disable LACP on the port. Similarly, when you add an LACP-disabled port to a static aggregation group, the system will automatically enable LACP on the port.
Follow these steps to configure a static LACP aggregation group: To do Enter system view Create a static aggregation group Enter Ethernet port view Add the port to the aggregation group Use the command system-view link-aggregation group agg-id mode static interface interface-type interface-number port link-aggregation group agg-id Required Required Remarks
For a static LACP aggregation group or a manual aggregation group, you are recommended not to cross cables between the two devices at the two ends of the aggregation group. For example, suppose port 1 of the local device is connected to port 2 of the peer device. To avoid cross-connecting cables, do not connect port 2 of the local device to port 1 of the peer device. Otherwise, packets may be lost.
1-7
You cannot enable LACP on a port which is already in a manual aggregation group.
Follow these steps to configure a dynamic LACP aggregation group: To do Enter system view Configure the system priority Use the command system-view lacp system-priority system-priority interface interface-type interface-number lacp enable Optional By default, the system priority is 32,768. Required Enable LACP on the port By default, LACP is disabled on a port. Optional By default, the port priority is 32,768. Remarks
Changing the system priority may affect the priority relationship between the aggregation peers, and thus affect the selected/unselected status of member ports in the dynamic aggregation group.
1-8
If you have saved the current configuration with the save command, after system reboot, the configuration concerning manual and static aggregation groups and their descriptions still exists, but that of dynamic aggregation groups and their descriptions gets lost.
Network diagram
Figure 1-1 Network diagram for link aggregation configuration
1-9
Configuration procedure
The following only lists the configuration on Switch A; you must perform the similar configuration on Switch B to implement link aggregation.
1)
2)
3)
1-10
The three LACP-enabled ports can be aggregated into one dynamic aggregation group to implement load sharing only when they have the same basic configuration (such as rate, duplex mode, and so on).
1-11
Table of Contents
1 Port Isolation Configuration 1-1 Port Isolation Overview 1-1 Port Isolation Configuration1-1 Displaying and Maintaining Port Isolation Configuration 1-2 Port Isolation Configuration Example1-2
Currently, you can create only one isolation group on an 4200G Ethernet switch. The number of Ethernet ports in an isolation group is not limited. An isolation group only isolates the member ports in it.
1-1
When a member port of an aggregation group joins/leaves an isolation group, the other ports in the same aggregation group will join/leave the isolation group at the same time. For ports that belong to an aggregation group and an isolation group simultaneously, removing a port from the aggregation group has no effect on the other ports. That is, the rest ports remain in the aggregation group and the isolation group. Ports that belong to an aggregation group and an isolation group simultaneously are still isolated even when you remove the aggregation group in system view. Adding an isolated port to an aggregation group causes all the ports in the aggregation group on the local unit to be added to the isolation group.
Network diagram
Figure 1-1 Network diagram for port isolation configuration
1-2
Configuration procedure
# Add GigabitEthernet1/0/2, GigabitEthernet1/0/3, and GigabitEthernet1/0/4 to the isolation group.
<Sysname> system-view System View: return to User View with Ctrl+Z. [Sysname] interface GigabitEthernet1/0/2 [Sysname-GigabitEthernet1/0/2] port isolate [Sysname-GigabitEthernet1/0/2] quit [Sysname] interface GigabitEthernet1/0/3 [Sysname-GigabitEthernet1/0/3] port isolate [Sysname-GigabitEthernet1/0/3] quit [Sysname] interface GigabitEthernet1/0/4 [Sysname-GigabitEthernet1/0/4] port isolate [Sysname-GigabitEthernet1/0/4] quit [Sysname] quit
1-3
Table of Contents
1 Port Security Configuration1-1 Port Security Overview1-1 Introduction1-1 Port Security Features1-1 Port Security Modes 1-1 Port Security Configuration Task List1-4 Enabling Port Security 1-5 Setting the Maximum Number of MAC Addresses Allowed on a Port 1-5 Setting the Port Security Mode1-6 Configuring Port Security Features 1-7 Ignoring the Authorization Information from the RADIUS Server1-8 Configuring Security MAC Addresses 1-9 Displaying and Maintaining Port Security Configuration1-10 Port Security Configuration Example 1-10 Port Security Configuration Example 1-10 2 Port Binding Configuration 2-1 Port Binding Overview2-1 Introduction2-1 Configuring Port Binding 2-1 Displaying and Maintaining Port Binding Configuration2-1 Port Binding Configuration Example 2-2 Port Binding Configuration Example 2-2
1-1
Table 1-1 Description of port security modes Security mode Description In this mode, access to the port is not restricted. In this mode, the port automatically learns MAC addresses and changes them to security MAC addresses. This security mode will automatically change to the secure mode after the amount of security MAC addresses on the port reaches the maximum number configured with the port-security max-mac-count command. After the port security mode is changed to the secure mode, only those packets whose source MAC addresses are security MAC addresses learned or dynamic MAC addresses configured can pass through the port. In this mode, the port is disabled from learning MAC addresses. secure Only those packets whose source MAC addresses are security MAC addresses learned and static or dynamic MAC addresses can pass through the port. In either mode, the device will trigger NTK and intrusion protection upon detecting an illegal packet. Feature In this mode, neither the NTK nor the intrusion protection feature is triggered.
noRestriction
autolearn
1-2
Description In this mode, port-based 802.1x authentication is performed for access users. MAC-based 802.1x authentication is performed on the access user. The port is enabled only after the authentication succeeds. When the port is enabled, only the packets of the successfully authenticated user can pass through the port.
Feature In this mode, neither NTK nor intrusion protection will be triggered.
userLoginSecure
In this mode, only one 802.1x-authenticated user is allowed to access the port. When the port changes from the noRestriction mode to this security mode, the system automatically removes the existing dynamic MAC address entries and authenticated MAC address entries on the port.
In any of these modes, the device triggers the NTK and Intrusion Protection features upon detecting an illegal packet or illegal event.
userLoginSecureExt
This mode is similar to the userLoginSecure mode, except that there can be more than one 802.1x-authenticated user on the port. This mode is similar to the userLoginSecure mode, except that, besides the packets of the single 802.1x-authenticated user, the packets whose source MAC addresses have a particular OUI are also allowed to pass through the port. When the port changes from the normal mode to this security mode, the system automatically removes the existing dynamic/authenticated MAC address entries on the port.
userLoginWithOUI
macAddressWithRa dius
In this mode, MAC addressbased authentication is performed for access users. In this mode, both MAC authentication and 802.1x authentication can be performed, but 802.1x authentication has a higher priority. 802.1x authentication can still be performed on an access user who has passed MAC authentication. No MAC authentication is performed on an access user who has passed 802.1x authentication. In this mode, there can be only one 802.1x-authenticated user on the port, but there can be several MAC-authenticated users.
macAddressOrUser LoginSecure
macAddressOrUser LoginSecureExt
This mode is similar to the macAddressOrUserLoginSecure mode, except that there can be more than one 802.1x-authenticated user on the port. .
1-3
Security mode
Description In this mode, a port performs MAC authentication of an access user first. If the authentication succeeds, the user is authenticated. Otherwise, the port performs 802.1x authentication of the user. In this mode, there can be only one 802.1x-authenticated user on the port, but there can be several MAC-authenticated users. This mode is similar to the macAddressElseUserLoginSecure mode, except that there can be more than one 802.1x-authenticated user on the port. In this mode, a port firstly performs MAC authentication for a user and then performs 802.1x authentication for the user if the user passes MAC authentication. The user can access the network after passing the two authentications. In this mode, up to one user can access the network.
Feature
macAddressElseUs erLoginSecure
macAddressElseUs erLoginSecureExt
macAddressAndUs erLoginSecure
macAddressAndUs erLoginSecureExt
This mode is similar to the macAddressAndUserLoginSecure mode, except that more than one user can access the network.
When the port operates in the userlogin-withoui mode, Intrusion Protection will not be triggered even if the OUI address does not match. On a port operating in either the macAddressElseUserLoginSecure mode or the macAddressElseUserLoginSecureExt mode, Intrusion Protection is triggered only after both MAC-based authentication and 802.1x authentication on the same packet fail.
1-4
Task Ignoring the Authorization Information from the RADIUS Server Configuring Security MAC Addresses Optional Optional
Remarks
Enabling port security resets the following configurations on the ports to the defaults (shown in parentheses below): 802.1x (disabled), port access control method (macbased), and port access control mode (auto) MAC authentication (disabled) In addition, you cannot perform the above-mentioned configurations manually because these configurations change with the port security mode automatically.
For details about 802.1x configuration, refer to the sections covering 802.1x and System-Guard. For details about MAC authentication configuration, refer to the sections covering MAC authentication configuration.
1-5
This configuration is different from that of the maximum number of MAC addresses that can be leaned by a port in MAC address management. Follow these steps to set the maximum number of MAC addresses allowed on a port: To do... Enter system view Enter Ethernet port view Set the maximum number of MAC addresses allowed on the port Use the command... system-view interface interface-type interface-number port-security max-mac-count count-value Required Not limited by default Remarks
interface interface-type interface-number port-security port-mode { autolearn | mac-and-userlogin-secure | mac-and-userlogin-secure-e xt | mac-authentication | mac-else-userlogin-secure | mac-else-userlogin-secure-e xt | secure | userlogin | userlogin-secure | userlogin-secure-ext | userlogin-secure-or-mac | userlogin-secure-or-mac-ext | userlogin-withoui }
Required By default, a port operates in noRestriction mode. In this mode, access to the port is not restricted. You can set a port security mode as needed.
1-6
Before setting the port security mode to autolearn, you need to set the maximum number of MAC addresses allowed on the port with the port-security max-mac-count command. When the port operates in the autoLearn mode, you cannot change the maximum number of MAC addresses allowed on the port. After you set the port security mode to autolearn, you cannot configure any static or blackhole MAC addresses on the port. If the port is in a security mode other than noRestriction, before you can change the port security mode, you need to restore the port security mode to noRestriction with the undo port-security port-mode command.
If the port-security port-mode mode command has been executed on a port, none of the following can be configured on the same port: Maximum number of MAC addresses that the port can learn Reflector port for port mirroring Link aggregation
1-7
The port-security timer disableport command is used in conjunction with the port-security intrusion-mode disableport-temporarily command to set the length of time during which the port remains disabled.
If you configure the NTK feature and execute the port-security intrusion-mode blockmac command on the same port, the switch will be unable to disable the packets whose destination MAC address is illegal from being sent out that port; that is, the NTK feature configured will not take effect on the packets whose destination MAC address is illegal.
Follow these steps to configure a port to ignore the authorization information from the RADIUS server: To do... Enter system view Enter Ethernet port view Ignore the authorization information from the RADIUS server Use the command... system-view interface interface-type interface-number port-security authorization ignore Required By default, a port uses the authorization information from the RADIUS server. Remarks
The security MAC addresses manually configured are written to the configuration file; they will not get lost when the port is up or down. As long as the configuration file is saved, the security MAC addresses can be restored after the switch reboots.
Configuration prerequisites
Port security is enabled. The maximum number of security MAC addresses allowed on the port is set. The security mode of the port is set to autolearn.
1-9
To do... In system view Add a security MAC address In Ethernet port view
Use the command... mac-address security mac-address interface interface-type interface-number vlan vlan-id interface interface-type interface-number mac-address security mac-address vlan vlan-id
Network diagram
Figure 1-1 Network diagram for port security configuration
Configuration procedure
# Enter system view.
<Switch> system-view
# Set the maximum number of MAC addresses allowed on the port to 80.
[Switch-GigabitEthernet1/0/1] port-security max-mac-count 80
# Add the MAC address 0001-0002-0003 of Host as a security MAC address to the port in VLAN 1.
[Switch-GigabitEthernet1/0/1] mac-address security 0001-0002-0003 vlan 1
# Configure the port to be silent for 30 seconds after intrusion protection is triggered.
[Switch-GigabitEthernet1/0/1] port-security intrusion-mode disableport-temporarily [Switch-GigabitEthernet1/0/1] quit [Switch] port-security timer disableport 30
1-11
An IP address can be bound to only one port at a time. A MAC address can be bound to only one port at a time.
Network diagram
Figure 2-1 Network diagram for port binding configuration
Configuration procedure
Configure Switch A as follows: # Enter system view.
<SwitchA> system-view
# Bind the MAC address and the IP address of Host A to GigabitEthernet 1/0/1.
[SwitchA-GigabitEthernet1/0/1] am user-bind mac-addr 0001-0002-0003 ip-addr 10.12.1.1
2-2
Table of Contents
1 MAC Address Table Management1-1 Overview 1-1 Introduction to MAC Address Table 1-1 Introduction to MAC Address Learning 1-1 Managing MAC Address Table 1-3 Configuring MAC Address Table Management 1-4 Configuration Task List1-4 Configuring a MAC Address Entry 1-5 Setting the Aging Time of MAC Address Entries 1-6 Setting the Maximum Number of MAC Addresses a Port Can Learn 1-6 Displaying MAC Address Table Information 1-7 Configuration Example1-7 Adding a Static MAC Address Entry Manually 1-7
This chapter describes the management of static, dynamic, and blackhole MAC address entries. For information about the management of multicast MAC address entries, refer to the part related to multicast protocol.
Overview
Introduction to MAC Address Table
An Ethernet switch is mainly used to forward packets at the data link layer, that is, transmit the packets to the corresponding ports according to the destination MAC address of the packets. To forward packets quickly, a switch maintains a MAC address table, which is a Layer 2 address table recording the MAC address-to-forwarding port association. Each entry in a MAC address table contains the following fields: Destination MAC address ID of the VLAN which a port belongs to Forwarding egress port numbers on the local switch When forwarding a packet, an Ethernet switch adopts one of the two forwarding methods based upon the MAC address table entries. Unicast forwarding: If the destination MAC address carried in the packet is included in a MAC address table entry, the switch forwards the packet through the forwarding egress port in the entry. Broadcast forwarding: If the destination MAC address carried in the packet is not included in the MAC address table, the switch broadcasts the packet to all ports except the one receiving the packet.
1-1
2)
After learning the MAC address of User A, the switch starts to forward the packet. Because there is no MAC address and port information of User B in the existing MAC address table, the switch forwards the packet to all ports except GigabitEthernet 1/0/1 to ensure that User B can receive the packet.
3)
Because the switch broadcasts the packet, both User B and User C can receive the packet. However, User C is not the destination device of the packet, and therefore does not process the packet. Normally, User B will respond to User A, as shown in Figure 1-4. When the response packet from User B is sent to GigabitEthernet 1/0/4, the switch records the association between the MAC address of User B and the corresponding port to the MAC address table of the switch.
1-2
4)
At this time, the MAC address table of the switch includes two forwarding entries shown in Figure 1-5. When forwarding the response packet, the switch unicasts the packet instead of broadcasting it to User A through GigabitEthernet 1/0/1, because MAC-A is already in the MAC address table.
5)
After this interaction, the switch directly unicasts the communication packets between User A and User B based on the corresponding MAC address table entries.
Under some special circumstances, for example, User B is unreachable or User B receives the packet but does not respond to it, the switch cannot learn the MAC address of User B. Hence, the switch still broadcasts the packets destined for User B. The switch learns only unicast addresses by using the MAC address learning mechanism but directly drops any packet with a broadcast source MAC address.
1-3
Aging time
Static MAC address entry Dynamic MAC address entry Blackhole MAC address entry
Manually configured Manually configured or generated by MAC address learning mechanism Manually configured
Unavailable
Available
No
Unavailable
Yes
1-4
Required
When you add a MAC address entry, the port specified by the interface argument must belong to the VLAN specified by the vlan argument in the command. Otherwise, the entry will not be added. If the VLAN specified by the vlan argument is a dynamic VLAN, after a static MAC address is added, it will become a static VLAN.
Required
When you add a MAC address entry, the current port must belong to the VLAN specified by the vlan argument in the command. Otherwise, the entry will not be added. If the VLAN specified by the vlan argument is a dynamic VLAN, after a static MAC address is added, it will become a static VLAN.
1-5
Normally, you are recommended to use the default aging time, namely, 300 seconds. The no-aging keyword specifies that MAC address entries do not age out.
MAC address aging configuration applies to all ports, but only takes effect on dynamic MAC addresses that are learnt or configured to age.
1-6
Operation Set the maximum number of MAC addresses the port can learn
Description
By default, the number of the MAC addresses a port can learn is not limited.
Configuration Example
Adding a Static MAC Address Entry Manually
Network requirements
The server connects to the switch through GigabitEthernet 1/0/2. To prevent the switch from broadcasting packets destined for the server, it is required to add the MAC address of the server to the MAC address table of the switch, which then forwards packets destined for the server through GigabitEthernet 1/0/2. The MAC address of the server is 000f-e20f-dc71. Port GigabitEthernet 1/0/2 belongs to VLAN 1.
Configuration procedure
# Enter system view.
<Sysname> system-view [Sysname]
# Add a MAC address, with the VLAN, ports, and states specified.
[Sysname] mac-address static 000f-e20f-dc71 interface GigabitEthernet 1/0/2 vlan 1
Config static GigabitEthernet1/0/2 NOAGED Learned Learned Learned GigabitEthernet1/0/2 AGING GigabitEthernet1/0/2 AGING GigabitEthernet1/0/2 AGING
1-7
---
1-8
Table of Contents
1 MSTP Configuration 1-1 STP Overview 1-1 MSTP Overview 1-9 Background of MSTP 1-9 Basic MSTP Terminologies 1-10 Principle of MSTP1-13 MSTP Implementation on Switches 1-14 STP-related Standards 1-15 Configuring Root Bridge1-15 Configuration Prerequisites 1-16 Configuring an MST Region 1-16 Specifying the Current Switch as a Root Bridge/Secondary Root Bridge1-17 Configuring the Bridge Priority of the Current Switch1-19 Configuring How a Port Recognizes and Sends MSTP Packets 1-19 Configuring the MSTP Operation Mode 1-21 Configuring the Maximum Hop Count of an MST Region 1-21 Configuring the Network Diameter of the Switched Network 1-22 Configuring the MSTP Time-related Parameters 1-23 Configuring the Timeout Time Factor1-24 Configuring the Maximum Transmitting Rate on the Current Port 1-24 Configuring the Current Port as an Edge Port 1-25 Specifying Whether the Link Connected to a Port Is Point-to-point Link 1-26 Enabling MSTP1-28 Configuring Leaf Nodes 1-28 Configuration Prerequisites 1-29 Configuring the MST Region 1-29 Configuring How a Port Recognizes and Sends MSTP Packets 1-29 Configuring the Timeout Time Factor1-29 Configuring the Maximum Transmitting Rate on the Current Port 1-29 Configuring a Port as an Edge Port1-29 Configuring the Path Cost for a Port 1-30 Configuring Port Priority 1-32 Specifying Whether the Link Connected to a Port Is a Point-to-point Link 1-33 Enabling MSTP1-33 Performing mCheck Operation 1-33 Configuration Prerequisites 1-33 Configuration Procedure1-33 Configuration Example 1-34 Configuring Guard Functions 1-34 Introduction1-34 Configuration Prerequisites 1-36 Configuring BPDU Guard 1-36 Configuring Root Guard1-36
i
Configuring Loop Guard 1-37 Configuring TC-BPDU Attack Guard 1-37 Configuring Digest Snooping 1-38 Introduction1-38 Configuring Digest Snooping1-38 Configuring Rapid Transition 1-39 Introduction1-39 Configuring Rapid Transition1-41 STP Maintenance Configuration 1-42 Introduction1-42 Enabling Log/Trap Output for Ports of MSTP Instance1-42 Configuration Example 1-42 Enabling Trap Messages Conforming to 802.1d Standard1-43 Displaying and Maintaining MSTP 1-43 MSTP Configuration Example1-43
ii
MSTP Configuration
Go to these sections for information you are interested in: MSTP Overview Configuring Root Bridge Configuring Leaf Nodes Performing mCheck Operation Configuring Guard Functions Configuring Digest Snooping Configuring Rapid Transition STP Maintenance Configuration Enabling Trap Messages Conforming to 802.1d Standard Displaying and Maintaining MSTP MSTP Configuration Example
STP Overview
Functions of STP
Spanning tree protocol (STP) is a protocol conforming to IEEE 802.1d. It aims to eliminate loops on data link layer in a local area network (LAN). Devices running this protocol detect loops in the network by exchanging packets with one another and eliminate the loops detected by blocking specific ports until the network is pruned into one with tree topology. As a network with tree topology is loop-free, it prevents packets in it from being duplicated and forwarded endlessly and prevents device performance degradation. Currently, in addition to the protocol conforming to IEEE 802.1d, STP also refers to the protocols based on IEEE 802.1d, such as RSTP, and MSTP.
A tree network must have a root; hence the concept of root bridge has been introduced in STP.
1-1
There is one and only one root bridge in the entire network, and the root bridge can change alone with changes of the network topology. Therefore, the root bridge is not fixed. Upon network convergence, the root bridge generates and sends out configuration BPDUs periodically. Other devices just forward the configuration BPDUs received. This mechanism ensures the topological stability. 2) Root port
On a non-root bridge device, the root port is the port with the lowest path cost to the root bridge. The root port is used for communicating with the root bridge. A non-root-bridge device has one and only one root port. The root bridge has no root port. 3) Designated bridge and designated port
Refer to the following table for the description of designated bridge and designated port. Table 1-1 Designated bridge and designated port Classification Designated bridge A designated bridge is a device that is directly connected to a switch and is responsible for forwarding BPDUs to this switch. A designated bridge is a device responsible for forwarding BPDUs to this LAN segment. Designated port The port through which the designated bridge forwards BPDUs to this device The port through which the designated bridge forwards BPDUs to this LAN segment
For a device
For a LAN
Figure 1-1 shows designated bridges and designated ports. In the figure, AP1 and AP2, BP1 and BP2, and CP1 and CP2 are ports on Device A, Device B, and Device C respectively. If Device A forwards BPDUs to Device B through AP1, the designated bridge for Device B is Device A, and the designated port is the port AP1 on Device A. Two devices are connected to the LAN: Device B and Device C. If Device B forwards BPDUs to the LAN, the designated bridge for the LAN is Device B, and the designated port is the port BP2 on Device B. Figure 1-1 A schematic diagram of designated bridges and designated ports
1-2
4)
Path cost
Path cost is a value used for measuring link capacity. By comparing the path costs of different links, STP selects the most robust links and blocks the other links to prune the network into a tree.
For the convenience of description, the description and examples below involve only four parts of a configuration BPDU: Root bridge ID (in the form of device priority) Root path cost Designated bridge ID (in the form of device priority) Designated port ID (in the form of port name)
1)
Upon initialization of a device, each device generates a BPDU with itself as the root bridge, in which the root path cost is 0, designated bridge ID is the device ID, and the designated port is the local port. Selection of the optimum configuration BPDU Each device sends out its configuration BPDU and receives configuration BPDUs from other devices. The process of selecting the optimum configuration BPDU is as follows:
1-3
Table 1-2 Selection of the optimum configuration BPDU Step Description Upon receiving a configuration BPDU on a port, the device performs the following processing: If the received configuration BPDU has a lower priority than that of the configuration BPDU generated by the port, the device will discard the received configuration BPDU without doing any processing on the configuration BPDU of this port. If the received configuration BPDU has a higher priority than that of the configuration BPDU generated by the port, the device will replace the content of the configuration BPDU generated by the port with the content of the received configuration BPDU. The device compares the configuration BPDUs of all the ports and chooses the optimum configuration BPDU.
Principle for configuration BPDU comparison: The configuration BPDU that has the lowest root bridge ID has the highest priority. If all configuration BPDUs have the same root bridge ID, they will be compared for their root path costs. If the root path cost in a configuration BPDU plus the path cost corresponding to this port is S, the configuration BPDU with the smallest S value has the highest priority. If all configuration BPDUs have the same root path cost, the following configuration BPDU priority is compared sequentially: designated bridge IDs, designated port IDs, and then the IDs of the ports on which the configuration BPDUs are received. The switch with a higher priority is elected as the root bridge.
Selection of the root bridge At network initialization, each STP-compliant device on the network assumes itself to be the root bridge, with the root bridge ID being its own bridge ID. By exchanging configuration BPDUs, the devices compare one anothers root bridge ID. The device with the smallest root bridge ID is elected as the root bridge. Selection of the root port and designated ports The process of selecting the root port and designated ports is as follows: Table 1-3 Selection of the root port and designated ports Step 1 Description A non-root-bridge device takes the port on which the optimum configuration BPDU was received as the root port. Based on the configuration BPDU and the path cost of the root port, the device calculates a designated port configuration BPDU for each of the rest ports. 2 The root bridge ID is replaced with that of the configuration BPDU of the root port. The root path cost is replaced with that of the configuration BPDU of the root port plus the path cost corresponding to the root port. The designated bridge ID is replaced with the ID of this device. The designated port ID is replaced with the ID of this port.
1-4
Step
Description The device compares the calculated configuration BPDU with the configuration BPDU on the port whose role is to be determined, and acts as follows based on the comparison result:
If the calculated configuration BPDU is superior, this port will serve as the designated port, and the configuration BPDU on the port will be replaced with the calculated configuration BPDU, which will be sent out periodically. If the configuration BPDU on the port is superior, the device stops updating the configuration BPDUs of the port and blocks the port, so that the port only receives configuration BPDUs, but does not forward data or send configuration BPDUs.
When the network topology is stable, only the root port and designated ports forward traffic, while other ports are all in the blocked state they only receive STP packets but do not forward user traffic.
Once the root bridge, the root port on each non-root bridge and designated ports have been successfully elected, the entire tree-shaped topology has been constructed. The following is an example of how the STP algorithm works. The specific network diagram is shown in Figure 1-2. The priority of Device A is 0, the priority of Device B is 1, the priority of Device C is 2, and the path costs of these links are 5, 10 and 4 respectively. Figure 1-2 Network diagram for STP algorithm
Initial state of each device The following table shows the initial state of each device. Table 1-4 Initial state of each device Device Device A AP1 AP2 BP1 BP2
1-5
Port name
BPDU of port {0, 0, 0, AP1} {0, 0, 0, AP2} {1, 0, 1, BP1} {1, 0, 1, BP2}
Device B
Port name
Comparison process and result on each device The following table shows the comparison process and result on each device. Table 1-5 Comparison process and result on each device Device Comparison process Port AP1 receives the configuration BPDU of Device B {1, 0, 1, BP1}. Device A finds that the configuration BPDU of the local port {0, 0, 0, AP1} is superior to the configuration received message, and discards the received configuration BPDU. Port AP2 receives the configuration BPDU of Device C {2, 0, 2, CP1}. Device A finds that the BPDU of the local port {0, 0, 0, AP2} is superior to the received configuration BPDU, and discards the received configuration BPDU. Device A finds that both the root bridge and designated bridge in the configuration BPDUs of all its ports are Device A itself, so it assumes itself to be the root bridge. In this case, it does not make any change to the configuration BPDU of each port, and starts sending out configuration BPDUs periodically. Port BP1 receives the configuration BPDU of Device A {0, 0, 0, AP1}. Device B finds that the received configuration BPDU is superior to the configuration BPDU of the local port {1, 0,1, BP1}, and updates the configuration BPDU of BP1. Port BP2 receives the configuration BPDU of Device C {2, 0, 2, CP2}. Device B finds that the configuration BPDU of the local port {1, 0, 1, BP2} is superior to the received configuration BPDU, and discards the received configuration BPDU. Device B Device B compares the configuration BPDUs of all its ports, and determines that the configuration BPDU of BP1 is the optimum configuration BPDU. Then, it uses BP1 as the root port, the configuration BPDUs of which will not be changed. Based on the configuration BPDU of BP1 and the path cost of the root port (5), Device B calculates a designated port configuration BPDU for BP2 {0, 5, 1, BP2}. Device B compares the calculated configuration BPDU {0, 5, 1, BP2} with the configuration BPDU of BP2. If the calculated BPDU is superior, BP2 will act as the designated port, and the configuration BPDU on this port will be replaced with the calculated configuration BPDU, which will be sent out periodically. Port CP1 receives the configuration BPDU of Device A {0, 0, 0, AP2}. Device C finds that the received configuration BPDU is superior to the configuration BPDU of the local port {2, 0, 2, CP1}, and updates the configuration BPDU of CP1. Port CP2 receives the configuration BPDU of port BP2 of Device B {1, 0, 1, BP2} before the message was updated. Device C finds that the received configuration BPDU is superior to the configuration BPDU of the local port {2, 0, 2, CP2}, and updates the configuration BPDU of CP2. BPDU of port after comparison
Device A
Root port BP1: {0, 0, 0, AP1} Designated port BP2: {0, 5, 1, BP2}
Device C
1-6
Device By comparison:
Comparison process
The configuration BPDUs of CP1 is elected as the optimum configuration BPDU, so CP1 is identified as the root port, the configuration BPDUs of which will not be changed. Device C compares the calculated designated port configuration BPDU {0, 10, 2, CP2} with the configuration BPDU of CP2, and CP2 becomes the designated port, and the configuration BPDU of this port will be replaced with the calculated configuration BPDU. Next, port CP2 receives the updated configuration BPDU of Device B {0, 5, 1, BP2}. Because the received configuration BPDU is superior to its old one, Device C launches a BPDU update process. At the same time, port CP1 receives configuration BPDUs periodically from Device A. Device C does not launch an update process after comparison. By comparison: Because the root path cost of CP2 (9) (root path cost of the BPDU (5) + path cost corresponding to CP2 (4)) is smaller than the root path cost of CP1 (10) (root path cost of the BPDU (0) + path cost corresponding to CP2 (10)), the BPDU of CP2 is elected as the optimum BPDU, and CP2 is elected as the root port, the messages of which will not be changed. After comparison between the configuration BPDU of CP1 and the calculated designated port configuration BPDU, port CP1 is blocked, with the configuration BPDU of the port remaining unchanged, and the port will not receive data from Device A until a spanning tree calculation process is triggered by a new condition, for example, the link from Device B to Device C becomes down.
Root port CP1: {0, 0, 0, AP2} Designated port CP2: {0, 10, 2, CP2}
Blocked port CP2: {0, 0, 0, AP2} Root port CP2: {0, 5, 1, BP2}
After the comparison processes described in the table above, a spanning tree with Device A as the root bridge is stabilized, as shown in Figure 1-3. Figure 1-3 The final calculated spanning tree
1-7
To facilitate description, the spanning tree calculation process in this example is simplified, while the actual process is more complicated.
2)
The BPDU forwarding mechanism in STP Upon network initiation, every switch regards itself as the root bridge, generates configuration BPDUs with itself as the root, and sends the configuration BPDUs at a regular interval of hello time. If it is the root port that received the configuration BPDU and the received configuration BPDU is superior to the configuration BPDU of the port, the device will increase message age carried in the configuration BPDU by a certain rule and start a timer to time the configuration BPDU while it sends out this configuration BPDU through the designated port. If the configuration BPDU received on the designated port has a lower priority than the configuration BPDU of the local port, the port will immediately sends out its better configuration BPDU in response. If a path becomes faulty, the root port on this path will no longer receive new configuration BPDUs and the old configuration BPDUs will be discarded due to timeout. In this case, the device generates configuration BPDUs with itself as the root bridge and sends configuration BPDUs and TCN BPDUs. This triggers a new spanning tree calculation so that a new path is established to restore the network connectivity.
However, the newly calculated configuration BPDU will not be propagated throughout the network immediately, so the old root ports and designated ports that have not detected the topology change continue forwarding data through the old path. If the new root port and designated port begin to forward data as soon as they are elected, a temporary loop may occur. 3) STP timers
The following three time parameters are important for STP calculation: Forward delay, the period a device waits before state transition. A link failure triggers a new round of spanning tree calculation and results in changes of the spanning tree. However, as new configuration BPDUs cannot be propagated throughout the network immediately, if the new root port and designated port begin to forward data as soon as they are elected, loops may temporarily occur. For this reason, the protocol uses a state transition mechanism. Namely, a newly elected root port and the designated ports must go through a period, which is twice the forward delay time, before they transit to the forwarding state. The period allows the new configuration BPDUs to be propagated throughout the entire network. Hello time, the interval for sending hello packets. Hello packets are used to check link state. A switch sends hello packets to its neighboring devices at a regular interval (the hello time) to check whether the links are faulty. Max time, lifetime of the configuration BPDUs stored in a switch. A configuration BPDU that has expired is discarded by the switch.
1-8
MSTP Overview
Background of MSTP
Disadvantages of STP and RSTP
STP does not support rapid state transition of ports. A newly elected root port or designated port must wait twice the forward delay time before transiting to the forwarding state, even if it is a port on a point-to-point link or it is an edge port (an edge port refers to a port that directly connects to a user terminal rather than to another device or a shared LAN segment.) The rapid spanning tree protocol (RSTP) is an optimized version of STP. RSTP allows a newly elected root port or designated port to enter the forwarding state much quicker under certain conditions than in STP. As a result, it takes a shorter time for the network to reach the final topology stability.
In RSTP, the state of a root port can transit fast under the following conditions: the old root port on the device has stopped forwarding data and the upstream designated port has started forwarding data. In RSTP, the state of a designated port can transit fast under the following conditions: the designated port is an edge port or a port connected with a point-to-point link. If the designated port is an edge port, it can enter the forwarding state directly; if the designated port is connected with a point-to-point link, it can enter the forwarding state immediately after the device undergoes handshake with the downstream device and gets a response.
RSTP supports rapid convergence. Like STP, it is of the following disadvantages: all bridges in a LAN are on the same spanning tree; redundant links cannot be blocked by VLAN; the packets of all VLANs are forwarded along the same spanning tree.
Features of MSTP
The multiple spanning tree protocol (MSTP) overcomes the shortcomings of STP and RSTP. In addition to support for rapid network convergence, it also allows data flows of different VLANs to be forwarded along their own paths, thus providing a better load sharing mechanism for redundant links. MSTP features the following: MSTP supports mapping VLANs to MST instances (MSTIs) by means of a VLAN-to-MSTI mapping table. MSTP introduces instance (integrates multiple VLANs into a set) and can bind multiple VLANs to an instance, thus saving communication overhead and improving resource utilization. MSTP divides a switched network into multiple regions, each containing multiple spanning trees that are independent of one another. MSTP prunes a ring network into a network with tree topology, preventing packets from being duplicated and forwarded in a network endlessly. Furthermore, it offers multiple redundant paths for forwarding data, and thus achieves load balancing for forwarding VLAN data. MSTP is compatible with STP and RSTP.
1-9
Region A0: VLAN 1 mapped to MSTI 1 VLAN 2 mapped to MSTI 2 Other VLANs mapped to CIST
BPDU CST
BPDU
B D
C BPDU Region B0: VLAN 1 mapped to MSTI 1 VLAN 2 mapped to MSTI 2 Other VLANs mapped to CIST Region C0: VLAN 1 mapped to MSTI 1 VLAN 2 and 3 mapped to MSTI 2 Other VLANs mapped to CIST
Region D0: VLAN 1 mapped to MSTI 1, B as the regional root bridge VLAN 2 mapped to MSTI 2, C as the regional root bridge Other VLANs mapped to CIST
MST region
A multiple spanning tree region (MST region) comprises multiple physically-interconnected MSTP-enabled switches and the corresponding network segments connected to these switches. These switches have the same region name, the same VLAN-to-MSTI mapping configuration and the same MSTP revision level. A switched network can contain multiple MST regions. You can group multiple switches into one MST region by using the corresponding MSTP configuration commands. As shown in Figure 1-4, all the switches in region A0 are of the same MST region-related configuration, including: Region name VLAN-to-MSTI mapping (that is, VLAN 1 is mapped to MSTI 1, VLAN 2 is mapped to MSTI 2, and the other VLANs are mapped to CIST.) MSTP revision level (not shown in Figure 1-4)
MSTI
A multiple spanning tree instance (MSTI) refers to a spanning tree in an MST region. Multiple spanning trees can be established in one MST region. These spanning trees are independent of each other. For example, each region in Figure 1-4 contains multiple spanning trees known as MSTIs. Each of these spanning trees corresponds to a VLAN.
region A0 contains these mappings: VLAN 1 to MSTI 1; VLAN 2 to MSTI 2, and other VLANs to CIST. In an MST region, load balancing is implemented according to the VLAN-to-MSTI mapping table.
IST
An internal spanning tree (IST) is a spanning tree in an MST region. ISTs together with the common spanning tree (CST) form the common and internal spanning tree (CIST) of the entire switched network. An IST is a special MSTI; it is a branch of CIST in the MST region. In Figure 1-4, each MST region has an IST, which is a branch of the CIST.
CST
A CST is a single spanning tree in a switched network that connects all MST regions in the network. If you regard each MST region in the network as a switch, then the CST is the spanning tree generated by STP or RSTP running on the "switches".
CIST
A CIST is the spanning tree in a switched network that connects all switches in the network. It comprises the ISTs and the CST. In Figure 1-4, the ISTs in the MST regions and the CST connecting the MST regions form the CIST.
Region root
A region root is the root of the IST or an MSTI in an MST region. Different spanning trees in an MST region may have different topologies and thus have different region roots. In region D0 shown in Figure 1-4, the region root of MSTI 1 is switch B, and the region root of MSTI 2 is switch C.
Port role
MSTP calculation involves the following port roles: root port, designated port, master port, region boundary port, alternate port, and backup port. A root port is used to forward packets to the root. A designated port is used to forward packets to a downstream network segment or switch. A master port connects an MST region to the common root. The path from the master port to the common root is the shortest path between the MST region and the common root. In the CST, the master port is the root port of the region, which is considered as a node. The master port is a special boundary port. It is a root port in the IST/CIST while a master port in the other MSTIs. A region boundary port is located on the boundary of an MST region and is used to connect one MST region to another MST region, an STP-enabled region or an RSTP-enabled region. An alternate port is a secondary port of a root port or master port and is used for rapid transition. With the root port or master port being blocked, the alternate port becomes the new root port or master port. A backup port is the secondary port of a designated port and is used for rapid transition. With the designated port being blocked, the backup port becomes the new designated port fast and begins to forward data seamlessly. When two ports of an MSTP-enabled switch are interconnected, the
1-11
switch blocks one of the two ports to eliminate the loop that occurs. The blocked port is the backup port. In Figure 1-5, switch A, switch B, switch C, and switch D form an MST region. Port 1 and port 2 on switch A connect upstream to the common root. Port 5 and port 6 on switch C form a loop. Port 3 and port 4 on switch D connect downstream to other MST regions. This figure shows the roles these ports play.
A port can play different roles in different MSTIs. The role a region boundary port plays in an MSTI is consistent with the role it plays in the CIST. The master port, which is a root port in the CIST while a master port in the other MSTIs, is an exception. For example, in Figure 1-5, port 1 on switch A is a region boundary port. It is a root port in the CIST while a master port in all the other MSTIs in the region.
Port state
In MSTP, a port can be in one of the following three states: Forwarding state. Ports in this state can forward user packets and receive/send BPDU packets. Learning state. Ports in this state can receive/send BPDU packets but do not forward user packets. Discarding state. Ports in this state can only receive BPDU packets. Port roles and port states are not mutually dependent. Table 1-6 lists possible combinations of port states and port roles.
1-12
Table 1-6 Combinations of port states and port roles Port role Root/master port Port state Forwarding Learning Discarding Designated port Region Boundary port Alternate port Backup port
Principle of MSTP
MSTP divides a Layer 2 network into multiple MST regions. The CSTs are generated between these MST regions, and multiple spanning trees (also called MSTIs) can be generated in each MST region. As well as RSTP, MSTP uses configuration BPDUs for spanning tree calculation. The only difference is that the configuration BPDUs for MSTP carry the MSTP configuration information on the switches.
Calculate an MSTI
In an MST region, different MSTIs are generated for different VLANs based on the VLAN-to-MSTI mappings. Each spanning tree is calculated independently, in the same way as how STP/RSTP is calculated.
1-13
For configuration BPDUs with both the same Root bridge ID and the same External path costs, Master bridge ID, Internal path cost, Designated bridge ID,ID of sending port,ID of receiving port are compared in turn. For MSTP, MSTI configuration information is generally expressed as follows: (Instace bridge ID, Internal path costs, Designated bridge ID,ID of sending port,ID of receiving port),so the compared as follows The smaller the Instance bridge ID of the configuration BPDU is, the higher the priority of the configuration BPDU is. For configuration BPDUs with the same Instance bridge IDs, Internal path costs are compared. For configuration BPDUs with both the same Instance bridge ID and the same Internal path costs, Designated bridge ID,ID of sending port,ID of receiving port are compared in turn. 3) A spanning tree is calculated as follows: Determining the root bridge Root bridges are selected by configuration BPDU comparing. The switch with the smallest root ID is chosen as the root bridge. Determining the root port For each switch in a network, the port on which the configuration BPDU with the highest priority is received is chosen as the root port of the switch. Determining the designated port First, the switch calculates a designated port configuration BPDU for each of its ports using the root port configuration BPDU and the root port path cost, with the root ID being replaced with that of the root port configuration BPDU, root path cost being replaced with the sum of the root path cost of the root port configuration BPDU and the path cost of the root port, the ID of the designated bridge being replaced with that of the switch, and the ID of the designated port being replaced with that of the port. The switch then compares the calculated configuration BPDU with the original configuration BPDU received from the corresponding port on another switch. If the latter takes precedence over the former, the switch blocks the local port and keeps the port's configuration BPDU unchanged, so that the port can only receive configuration messages and cannot forward packets. Otherwise, the switch sets the local port to the designated port, replaces the original configuration BPDU of the port with the calculated one and advertises it regularly.
1-14
STP-related Standards
STP-related standards include the following. IEEE 802.1D: spanning tree protocol IEEE 802.1w: rapid spanning tree protocol IEEE 802.1s: multiple spanning tree protocol
Configuring an MST Region Specifying the Current Switch as a Root Bridge/Secondary Root Bridge
1-15
In a network containing switches with both GVRP and MSTP enabled, GVRP messages travel along the CIST. If you want to advertise a VLAN through GVRP, be sure to map the VLAN to the CIST (MSTI 0) when configuring the VLAN-to-MSTI mapping table.
Configuration Prerequisites
The role (root, branch, or leaf) of each switch in each MSTI is determined.
instance instance-id vlan vlan-list Configure the VLAN-to-MSTI mapping table for the MST region vlan-mapping modulo modulo
Configure the MSTP revision level for the MST region Activate the configuration of the MST region manually Display the configuration of the current MST region Display the currently valid configuration of the MST region
NTDP packets sent by devices in a cluster can only be transmitted within the MSTI where the management VLAN of the cluster resides.
Configuring MST region-related parameters (especially the VLAN-to-MSTI mapping table) results in spanning tree recalculation and network topology jitter. To reduce network topology jitter caused by the
1-16
configuration, MSTP does not recalculate spanning trees immediately after the configuration; it does this only after you perform one of the following operations, and then the configuration can really takes effect: Activate the new MST region-related settings by using the active region-configuration command Enable MSTP by using the stp enable command
MSTP-enabled switches are in the same region only when they have the same format selector (a 802.1s-defined protocol selector, which is 0 by default and cannot be configured), MST region name, VLAN-to-MSTI mapping table, and revision level. The 3com switches support only the MST region name, VLAN-to-MSTI mapping table, and revision level. Switches with the settings of these parameters being the same are assigned to the same MST region.
Configuration example
# Configure an MST region named info, the MSTP revision level being level 1, VLAN 2 through VLAN 10 being mapped to MSTI 1, and VLAN 20 through VLAN 30 being mapped to MSTI 2.
<Sysname> system-view [Sysname] stp region-configuration [Sysname-mst-region] region-name info [Sysname-mst-region] instance 1 vlan 2 to 10 [Sysname-mst-region] instance 2 vlan 20 to 30 [Sysname-mst-region] revision-level 1 [Sysname-mst-region] active region-configuration
Instance 0 1 2
To do... Enter system view Specify the current switch as the root bridge of a spanning tree
Use the command... system-view stp [ instance instance-id ] root primary [ bridge-diameter bridgenumber [ hello-time centi-seconds ] ]
Remarks
Required
Specify the current switch as the secondary root bridge of a spanning tree
Follow these steps to specify the current switch as the secondary root bridge of a spanning tree: To do... Enter system view Specify the current switch as the secondary root bridge of a specified spanning tree Use the command... system-view stp [ instance instance-id ] root secondary [ bridge-diameter bridgenumber [ hello-time centi-seconds ] ] Remarks
Required
Using the stp root primary/stp root secondary command, you can specify the current switch as the root bridge or the secondary root bridge of the MSTI identified by the instance-id argument. If the value of the instance-id argument is set to 0, the stp root primary/stp root secondary command specify the current switch as the root bridge or the secondary root bridge of the CIST. A switch can play different roles in different MSTIs. That is, it can be the root bridges in an MSTI and be a secondary root bridge in another MSTI at the same time. But in the same MSTI, a switch cannot be the root bridge and the secondary root bridge simultaneously. When the root bridge fails or is turned off, the secondary root bridge becomes the root bridge if no new root bridge is configured. If you configure multiple secondary root bridges for an MSTI, the one with the smallest MAC address replaces the root bridge when the latter fails. You can specify the network diameter and the hello time parameters while configuring a root bridge/secondary root bridge. Refer to Configuring the Network Diameter of the Switched Network and Configuring the MSTP Time-related Parameters for information about the network diameter parameter and the hello time parameter.
You can configure a switch as the root bridges of multiple MSTIs. But you cannot configure two or more root bridges for one MSTI. So, do not configure root bridges for the same MSTI on two or more switches using the stp root primary command. You can configure multiple secondary root bridges for one MSTI. That is, you can configure secondary root bridges for the same MSTI on two or more switches using the stp root secondary command. You can also configure the current switch as the root bridge by setting the priority of the switch to 0. Note that once a switch is configured as the root bridge or a secondary root bridge, its priority cannot be modified.
1-18
Configuration example
# Configure the current switch as the root bridge of MSTI 1 and a secondary root bridge of MSTI 2.
<Sysname> system-view [Sysname] stp instance 1 root primary [Sysname] stp instance 2 root secondary
Configuration procedure
Follow these steps to configure the bridge priority of the current switch: To do... Enter system view Set the bridge priority for the current switch Use the command... system-view stp [ instance instance-id ] priority priority Required The default bridge priority of a switch is 32,768. Remarks
Once you specify a switch as the root bridge or a secondary root bridge by using the stp root primary or stp root secondary command, the bridge priority of the switch cannot be configured any more. During the selection of the root bridge, if multiple switches have the same bridge priority, the one with the smallest MAC address becomes the root bridge.
Configuration example
# Set the bridge priority of the current switch to 4,096 in MSTI 1.
<Sysname> system-view [Sysname] stp instance 1 priority 4096
1-19
The port automatically determines the format (legacy or dot1s) of received MSTP packets and then determines the format of the packets to be sent accordingly, thus communicating with the peer devices. If the format of the received packets changes repeatedly, MSTP will shut down the corresponding port to prevent network storm. A port shut down in this way can only be brought up by the network administrator. When a port operates in the legacy mode: The port recognizes and sends MSTP packets in legacy format. In this case, the port can only communicate with the peer through packets in legacy format. If packets in dot1s format are received, the port turns to discarding state to prevent network storm. When a port operates in the 802.1s mode: The port recognizes and sends MSTP packets in dot1s format. In this case, the port can only communicate with the peer through packets in dot1s format. If packets in legacy format are received, the port turns to discarding state to prevent network storm.
Configuration procedure
Follow these steps to configure how a port recognizes and sends MSTP packets (in system view): To do... Enter system view Use the command... system-view stp interface interface-type interface-number compliance { auto | dot1s | legacy } Required Configure how a port recognizes and sends MSTP packets By default, a port recognizes and sends MSTP packets in the automatic mode. That is, it determines the format of packets to be sent according to the format of the packets received. Remarks
Follow these steps to configure how a port recognizes and sends MSTP packets (in Ethernet port view): To do... Enter system view Enter Ethernet port view Use the command... system-view interface interface-type interface-number Required Configure how a port recognizes and sends MSTP packets stp compliance { auto | dot1s | legacy } By default, a port recognizes and sends MSTP packets in the automatic mode. That is, it determines the format of packets to be sent according to the format of the packets received. Remarks
Configuration example
# Configure GigabitEthernet 1/0/1 to recognize and send packets in dot1s format.
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] stp compliance dot1s
# Restore the default mode for GigabitEthernet 1/0/1 to recognize/send MSTP packets.
1-20
Configuration procedure
Follow these steps to configure the MSTP operation mode: To do... Enter system view Configure the MSTP operation mode Use the command... system-view Required stp mode { stp | rstp | mstp } An MSTP-enabled switch operates in the MSTP mode by default. Remarks
Configuration example
# Specify the MSTP operation mode as STP-compatible.
<Sysname> system-view [Sysname] stp mode stp
1-21
Configuration procedure
Follow these steps to configure the maximum hop count for an MST region: To do... Enter system view Configure the maximum hop count of the MST region Use the command... system-view stp max-hops hops Required By default, the maximum hop count of an MST region is 20. Remarks
The bigger the maximum hop count, the larger the MST region is. Note that only the maximum hop settings on the switch operating as a region root can limit the size of the MST region.
Configuration example
# Configure the maximum hop count of the MST region to be 30.
<Sysname> system-view [Sysname] stp max-hops 30
Configuration procedure
Follow these steps to configure the network diameter of the switched network: To do... Enter system view Configure the network diameter of the switched network Use the command... system-view stp bridge-diameter bridgenumber Required The default network diameter of a network is 7. Remarks
The network diameter parameter indicates the size of a network. The bigger the network diameter is, the larger the network size is. After you configure the network diameter of a switched network, an MSTP-enabled switch adjusts its hello time, forward delay, and max age settings accordingly to better values. The network diameter setting only applies to CIST; it is invalid for MSTIs.
Configuration example
# Configure the network diameter of the switched network to 6.
<Sysname> system-view [Sysname] stp bridge-diameter 6
1-22
Configuration procedure
Follow these steps to configure MSTP time-related parameters: To do... Enter system view Configure the forward delay parameter Use the command... system-view stp timer forward-delay centiseconds Required The forward delay parameter defaults to 1,500 centiseconds (namely, 15 seconds). Required Configure the hello time parameter stp timer hello centiseconds The hello time parameter defaults to 200 centiseconds (namely, 2 seconds). Required Configure the max age parameter stp timer max-age centiseconds The max age parameter defaults to 2,000 centiseconds (namely, 20 seconds). Remarks
All switches in a switched network adopt the three time-related parameters configured on the CIST root bridge.
The forward delay parameter and the network diameter are correlated. Normally, a large network diameter corresponds to a large forward delay. A too small forward delay parameter may result in temporary redundant paths. And a too large forward delay parameter may cause a network unable to resume the normal state in time after changes occurred to the network. The default value is recommended. An adequate hello time parameter enables a switch to detect link failures in time without occupying too many network resources. And a too small hello time parameter may result in duplicated configuration BPDUs being sent frequently, which increases the work load of the switches and wastes network resources. The default value is recommended. As for the max age parameter, if it is too small, network congestion may be falsely regarded as link failures, which results in frequent spanning tree recalculation. If it is too large, link problems may be unable to be detected in time, which prevents spanning trees being recalculated in time and makes the network less adaptive. The default value is recommended.
As for the configuration of the three time-related parameters (that is, the hello time, forward delay, and max age parameters), the following formulas must be met to prevent frequent network jitter. 2 x (forward delay 1 second) >= max age Max age >= 2 x (hello time + 1 second)
1-23
You are recommended to specify the network diameter of the switched network and the hello time by using the stp root primary or stp root secondary command. After that, the three proper time-related parameters are determined automatically.
Configuration example
# Configure the forward delay parameter to be 1,600 centiseconds, the hello time parameter to be 300 centiseconds, and the max age parameter to be 2,100 centiseconds (assuming that the current switch operates as the CIST root bridge).
<Sysname> system-view [Sysname] stp timer forward-delay 1600 [Sysname] stp timer hello 300 [Sysname] stp timer max-age 2100
Configuration procedure
Follow these steps to configure the timeout time factor: To do... Enter system view Configure the timeout time factor for the switch Use the command... system-view stp timer-factor number Required The timeout time factor defaults to 3. Remarks
For a steady network, the timeout time can be five to seven times of the hello time.
Configuration example
# Configure the timeout time factor to be 6.
<Sysname> system-view [Sysname] stp timer-factor 6
1-24
Configure the maximum transmitting rate for specified ports in system view
Follow these steps to configure the maximum transmitting rate for specified ports in system view: To do... Enter system view Configure the maximum transmitting rate for specified ports Use the command... system-view stp interface interface-list transmit-limit packetnum Required The maximum transmitting rate of all Ethernet ports on a switch defaults to 10. Remarks
As the maximum transmitting rate parameter determines the number of the configuration BPDUs transmitted in each hello time, set it to a proper value to prevent MSTP from occupying too many network resources. The default value is recommended.
Configuration example
# Set the maximum transmitting rate of GigabitEthernet 1/0/1 to 15. 1) Configure the maximum transmitting rate in system view
2)
To do... Enter system view Configure the specified ports as edge ports
Use the command... system-view stp interface interface-list edged-port enable Required
Remarks
On a switch with BPDU guard disabled, an edge port becomes a non-edge port again once it receives a BPDU from another port.
You are recommended to configure the Ethernet ports connected directly to terminals as edge ports and enable the BPDU guard function at the same time. This not only enables these ports to turn to the forwarding state rapidly but also secures your network.
Configuration example
# Configure GigabitEthernet 1/0/1 as an edge port. 1) Configure GigabitEthernet 1/0/1 as an edge port in system view
2)
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] stp edged-port enable
You can determine whether or not the link connected to a port is a point-to-point link in one of the following two ways.
Specify whether the link connected to a port is point-to-point link in system view
Follow these steps to specify whether the link connected to a port is point-to-point link in system view: To do... Enter system view Specify whether the link connected to a port is point-to-point link Use the command... system-view stp interface interface-list point-to-point { force-true | force-false | auto } Required The auto keyword is adopted by default. Remarks
Specify whether the link connected to a port is point-to-point link in Ethernet port view
Follow these steps to specify whether the link connected to a port is point-to-point link in Ethernet port view: To do... Enter system view Enter Ethernet port view Specify whether the link connected to a port is a point-to-point link Use the command... system-view interface interface-type interface-number stp point-to-point { force-true | force-false | auto } Required The auto keyword is adopted by default. Remarks
If you configure the link connected to a port in an aggregation group as a point-to-point link, the configuration will be synchronized to the rest ports in the same aggregation group. If an auto-negotiating port operates in full duplex mode after negotiation, you can configure the link of the port as a point-to-point link.
After you configure the link of a port as a point-to-point link, the configuration applies to all the MSTIs the port belongs to. If the actual physical link of a port is not a point-to-point link and you forcibly configure the link as a point-to-point link, loops may occur temporarily.
Configuration example
# Configure the link connected to GigabitEthernet 1/0/1 as a point-to-point link. 1) Perform this configuration in system view
2)
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] stp point-to-point force-true
1-27
Enabling MSTP
Configuration procedure
Follow these steps to enable MSTP in system view: To do... Enter system view Enable MSTP Use the command... system-view stp enable Required MSTP is enabled by default. Optional By default, MSTP is enabled on all ports. Disable MSTP on specified ports stp interface interface-list disable To enable a switch to operate more flexibly, you can disable MSTP on specific ports. As MSTP-disabled ports do not participate in spanning tree calculation, this operation saves CPU resources of the switch. Remarks
Follow these steps to enable MSTP in Ethernet port view: To do... Enter system view Enable MSTP Enter Ethernet port view Use the command... system-view stp enable interface interface-type interface-number Required MSTP is enabled by default. Optional By default, MSTP is enabled on all ports. Disable MSTP on the port stp disable To enable a switch to operate more flexibly, you can disable MSTP on specific ports. As MSTP-disabled ports do not participate in spanning tree calculation, this operation saves CPU resources of the switch. Remarks
Other MSTP-related settings can take effect only after MSTP is enabled on the switch.
Configuration example
# Disable MSTP on GigabitEthernet 1/0/1. 1) Perform this configuration in system view
2)
1-28
Remarks To prevent network topology jitter caused by other related configurations, you are recommended to enable MSTP after performing other configurations. Required Optional Optional Optional The default value is recommended. Optional Optional Optional Optional
Configuring an MST Region Configuring How a Port Recognizes and Sends MSTP Packets Configuring the Timeout Time Factor Configuring the Maximum Transmitting Rate on the Current Port Configuring the Current Port as an Edge Port Configuring the Path Cost for a Port Configuring Port Priority Specifying Whether the Link Connected to a Port Is Point-to-point Link
In a network containing switches with both GVRP and MSTP enabled, GVRP messages travel along the CIST. If you want to advertise a VLAN through GVRP, be sure to map the VLAN to the CIST (MSTI 0) when configuring the VLAN-to-MSTI mapping table.
Configuration Prerequisites
The role (root, branch, or leaf) of each switch in each MSTI is determined.
Table 1-7 Transmission rates vs. path costs Rate 0 Half-duplex/Full-duplex 10 Mbps Aggregated link 2 ports Aggregated link 3 ports Aggregated link 4 ports Half-duplex/Full-duplex 100 Mbps Aggregated link 2 ports Aggregated link 3 ports Aggregated link 4 ports Full-duplex 1,000 Mbps Aggregated link 2 ports Aggregated link 3 ports Aggregated link 4 ports Full-duplex 10 Gbps Aggregated link 2 ports Aggregated link 3 ports Aggregated link 4 ports Operation mode (half-/full-duplex) 802.1D-1998 65,535 100 95 95 95 19 15 15 15 4 3 3 3 2 1 1 1 IEEE 802.1t 200,000,000 2,000,000 1,000,000 666,666 500,000 200,000 100,000 66,666 50,000 20,000 10,000 6,666 5,000 2,000 1,000 666 500 Latency standard 200,000 2,000 1,800 1,600 1,400 200 180 160 140 20 18 16 14 2 1 1 1
Normally, the path cost of a port operating in full-duplex mode is slightly less than that of the port operating in half-duplex mode.
1-30
When calculating the path cost of an aggregated link, the 802.1D-1998 standard does not take the number of the ports on the aggregated link into account, whereas the 802.1T standard does. The following formula is used to calculate the path cost of an aggregated link: Path cost = 200,000,000 / link transmission rate Where, link transmission rate is the sum of the rates of all the unblocked ports on the aggregated link measured in 100 Kbps.
Follow these steps to configure the path cost for a port in Ethernet port view: To do... Enter system view Enter Ethernet port view Use the command... system-view interface interface-type interface-number stp [ instance instance-id ] cost cost Required Configure the path cost for the port An MSTP-enabled switch can calculate path costs for all its ports automatically. Remarks
Changing the path cost of a port may change the role of the port and put it in state transition. Executing the stp cost command with the instance-id argument being 0 sets the path cost on the CIST for the port.
<Sysname> system-view [Sysname] stp interface GigabitEthernet 1/0/1 instance 1 cost 2000
2)
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] stp instance 1 cost 2000
<Sysname> system-view [Sysname] undo stp interface GigabitEthernet 1/0/1 instance 1 cost
1-31
2)
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] undo stp instance 1 cost [Sysname-GigabitEthernet1/0/1] quit [Sysname] stp pathcost-standard dot1d-1998
Changing port priority of a port may change the role of the port and put the port into state transition. A smaller port priority value indicates a higher possibility for the port to become the root port. If all the ports of a switch have the same port priority value, the port priorities are determined by the port indexes. Changing the priority of a port will cause spanning tree recalculation. You can configure port priorities according to actual networking requirements.
Configuration example
# Configure the port priority of GigabitEthernet 1/0/1 in MSTI 1 to be 16. 1) Perform this configuration in system view
1-32
<Sysname> system-view
2)
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] stp instance 1 port priority 16
Enabling MSTP
Refer to Enabling MSTP.
Configuration Prerequisites
MSTP runs normally on the switch.
Configuration Procedure
You can perform the mCheck operation in the following two ways.
1-33
To do... Enter system view Enter Ethernet port view Perform the mCheck operation
Use the command... system-view interface interface-type interface-number stp mcheck Required
Remarks
Configuration Example
# Perform the mCheck operation on GigabitEthernet 1/0/1. 1) Perform this configuration in system view
2)
BPDU guard
Normally, the access ports of the devices operating on the access layer are directly connected to terminals (such as PCs) or file servers. These ports are usually configured as edge ports to achieve rapid transition. But they resume non-edge ports automatically upon receiving configuration BPDUs, which causes spanning tree recalculation and network topology jitter. Normally, no configuration BPDU will reach edge ports. But malicious users can attack a network by sending configuration BPDUs deliberately to edge ports to cause network jitter. You can prevent this type of attacks by utilizing the BPDU guard function. With this function enabled on a switch, the switch shuts down the edge ports that receive configuration BPDUs and then reports these cases to the administrator. Ports shut down in this way can only be restored by the administrator.
Root guard
A root bridge and its secondary root bridges must reside in the same region. The root bridge of the CIST and its secondary root bridges are usually located in the high-bandwidth core region. Configuration errors or attacks may result in configuration BPDUs with their priorities higher than that of a root bridge, which causes a new root bridge to be elected and network topology jitter to occur. In this case, flows that should travel along high-speed links may be led to low-speed links, and network congestion may occur. You can avoid this problem by utilizing the root guard function. Ports with this function enabled can only be kept as designated ports in all MSTIs. When a port of this type receives configuration BPDUs with higher priorities, it turns to the discarding state (rather than become a non-designated port) and stops forwarding packets (as if it is disconnected from the link). It resumes the normal state if it does not receive any configuration BPDUs with higher priorities for a specified period.
1-34
Loop guard
A switch maintains the states of the root port and other blocked ports by receiving and processing BPDUs from the upstream switch. These BPDUs may get lost because of network congestions or unidirectional link failures. If a switch does not receive BPDUs from the upstream switch for certain period, the switch selects a new root port; the original root port becomes a designated port; and the blocked ports turns to the forwarding state. This may cause loops in the network. The loop guard function suppresses loops. With this function enabled, if link congestions or unidirectional link failures occur, both the root port and the blocked ports become designated ports and turn to the discarding state. In this case, they stop forwarding packets, and thereby loops can be prevented.
With the loop guard function enabled, the root guard function and the edge port configuration are mutually exclusive.
BPDU dropping
In a STP-enabled network, some users may send BPDU packets to the switch continuously in order to destroy the network. When a switch receives the BPDU packets, it will forward them to other switches. As a result, STP calculation is performed repeatedly, which may occupy too much CPU of the switches or cause errors in the protocol state of the BPDU packets. In order to avoid this problem, you can enable BPDU dropping on Ethernet ports. Once the function is enabled on a port, the port will not receive or forward any BPDU packets. In this way, the switch is protected against the BPDU packet attacks so that the STP calculation is assured to be right.
1-35
Configuration Prerequisites
MSTP runs normally on the switch.
Configuration example
# Enable the BPDU guard function.
<Sysname> system-view [Sysname] stp bpdu-protection
Follow these steps to enable the root guard function in Ethernet port view: To do... Enter system view Enter Ethernet port view Enable the root guard function on the current port Use the command... system-view Interface interface-type interface-number stp root-protection Required The root guard function is disabled by default. Remarks
Configuration example
# Enable the root guard function on GigabitEthernet 1/0/1. 1) Perform this configuration in system view
<Sysname> system-view
1-36
2)
Configuration example
# Enable the loop guard function on GigabitEthernet 1/0/1.
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] stp loop-protection
Configuration procedure
Follow these steps to configure the TC-BPDU attack guard function: To do... Enter system view Enable the TC-BPDU attack guard function Set the maximum times that a switch can remove the MAC address table and ARP entries within each 10 seconds Use the command... system-view stp tc-protection enable Required The TC-BPDU attack guard function is disabled by default. Remarks
Optional
Configuration example
# Enable the TC-BPDU attack guard function
1-37
# Set the maximum times for the switch to remove the MAC address table and ARP entries within 10 seconds to 5.
<Sysname> system-view [Sysname] stp tc-protection threshold 5
Configuration prerequisites
The switch to be configured is connected to another manufacturer's switch adopting a proprietary spanning tree protocol. MSTP and the network operate normally.
Configuration procedure
Follow these steps to configure digest snooping:
1-38
To do... Enter system view Enter Ethernet port view Enable the digest snooping feature Return to system view Enable the digest snooping feature globally Display the current configuration
Use the command... system-view interface interface-type interface-number stp config-digest-snooping quit stp config-digest-snooping Required
Remarks
The digest snooping feature is disabled on a port by default. Required The digest snooping feature is disabled globally by default. Available in any view
display current-configuration
When the digest snooping feature is enabled on a port, the port state turns to the discarding state. That is, the port will not send BPDU packets. The port is not involved in the STP calculation until it receives BPDU packets from the peer port. The digest snooping feature is needed only when your switch is connected to another manufacturers switches adopting proprietary spanning tree protocols. To enable the digest snooping feature successfully, you must first enable it on all the ports of your switch that are connected to another manufacturers switches adopting proprietary spanning tree protocols and then enable it globally.
To enable the digest snooping feature, the interconnected switches and another manufacturers switch adopting proprietary spanning tree protocols must be configured with exactly the same MST region-related configurations (including region name, revision level, and VLAN-to-MSTI mapping). The digest snooping feature must be enabled on all the switch ports that connect to another manufacturers switches adopting proprietary spanning tree protocols in the same MST region. When the digest snooping feature is enabled globally, the VLAN-to-MSTI mapping table cannot be modified. The digest snooping feature is not applicable to boundary ports in an MST region. The digest snooping feature is not applicable to edge ports in an MST region.
Proposal packets: Packets sent by designated ports to request rapid transition Agreement packets: Packets used to acknowledge rapid transition requests Both RSTP and MSTP specify that the upstream switch can perform rapid transition operation on the designated port only when the port receives an agreement packet from the downstream switch. The difference between RSTP and MSTP are: For MSTP, the upstream switch sends agreement packets to the downstream switch; and the downstream switch sends agreement packets to the upstream switch only after it receives agreement packets from the upstream switch. For RSTP, the upstream switch does not send agreement packets to the downstream switch. Figure 1-6 and Figure 1-7 illustrate the rapid transition mechanisms on designated ports in RSTP and MSTP. Figure 1-6 The RSTP rapid transition mechanism
Upstream switch Downstream switch
Proposal for rapid transition Root port blocks other nonedge ports, changes to forwarding state and sends Agreement to upstream device
eme Agre
nt
Root port blocks other non- edge ports Root port changes to forwarding state and sends Agreement to upstream switch
The cooperation between MSTP and RSTP is limited in the process of rapid transition. For example, when the upstream switch adopts RSTP, the downstream switch adopts MSTP and the downstream switch does not support RSTP-compatible mode, the root port on the downstream switch receives no agreement packet from the upstream switch and thus sends no agreement packets to the upstream switch. As a result, the designated port of the upstream switch fails to transit rapidly and can only turn to the forwarding state after a period twice the forward delay.
1-40
Some other manufacturers' switches adopt proprietary spanning tree protocols that are similar to RSTP in the way to implement rapid transition on designated ports. When a switch of this kind operating as the upstream switch connects with a 3com switch running MSTP, the upstream designated port fails to change its state rapidly. The rapid transition feature is developed to resolve this problem. When a 3com switch running MSTP is connected in the upstream direction to another manufacturer's switch running proprietary spanning tree protocols, you can enable the rapid transition feature on the ports of the 3com switch operating as the downstream switch. Among these ports, those operating as the root ports will then send agreement packets to their upstream ports after they receive proposal packets from the upstream designated ports, instead of waiting for agreement packets from the upstream switch. This enables designated ports of the upstream switch to change their states rapidly.
Configuration procedure
1) Configure the rapid transition feature in system view
Follow these steps to configure the rapid transition feature in system view: To do... Enter system view Enable the rapid transition feature Use the command... system-view stp interface interface-type interface-number no-agreement-check Required By default, the rapid transition feature is disabled on a port. Remarks
2)
Follow these steps to configure the rapid transition feature in Ethernet port view:
1-41
To do... Enter system view Enter Ethernet port view Enable the rapid transition feature
Use the command... system-view interface interface-type interface-number stp no-agreement-check Required
Remarks
The rapid transition feature can be enabled on only root ports or alternate ports. If you configure the rapid transition feature on a designated port, the feature does not take effect on the port.
Configuration Example
# Enable log/trap output for the ports of instance 1.
<Sysname> system-view [Sysname] stp instance 1 portlog
1-42
Configuration procedure
Follow these steps to enable trap messages conforming to 802.1d standard: To do... Enter system view Enable trap messages conforming to 802.1d standard in an instance Use the command... system-view stp [ instance instance-id ] dot1d-trap [ newroot | topologychange ] enable Required Remarks
Configuration example
# Enable a switch to send trap messages conforming to 802.1d standard to the network management device when the switch becomes the root bridge of instance 1.
<Sysname> system-view [Sysname] stp instance 1 dot1d-trap newroot enable
1-43
All switches in the network belong to the same MST region. Packets of VLAN 10, VLAN 30, VLAN 40, and VLAN 20 are forwarded along MSTI 1, MSTI 3, MSTI 4, and MSTI 0 respectively. In this network, Switch A and Switch B operate on the convergence layer; Switch C and Switch D operate on the access layer. VLAN 10 and VLAN 30 are limited in the convergence layer and VLAN 40 is limited in the access layer. Switch A and Switch B are configured as the root bridges of MSTI 1 and MSTI 3 respectively. Switch C is configured as the root bridge of MSTI 4.
Network diagram
Figure 1-9 Network diagram for MSTP configuration
The word permit shown in Figure 1-9 means the corresponding link permits packets of specific VLANs.
Configuration procedure
1) Configure Switch A
# Configure the region name, VLAN-to-MSTI mapping table, and revision level for the MST region.
[Sysname-mst-region] region-name example [Sysname-mst-region] instance 1 vlan 10 [Sysname-mst-region] instance 3 vlan 30 [Sysname-mst-region] instance 4 vlan 40 [Sysname-mst-region] revision-level 0
2)
Configure Switch B
1-44
# Configure the region name, VLAN-to-MSTI mapping table, and revision level for the MST region.
[Sysname-mst-region] region-name example [Sysname-mst-region] instance 1 vlan 10 [Sysname-mst-region] instance 3 vlan 30 [Sysname-mst-region] instance 4 vlan 40 [Sysname-mst-region] revision-level 0
3)
Configure Switch C.
4)
Configure Switch D
1-45
Table of Contents
1 802.1x Configuration 1-1 Introduction to 802.1x1-1 Architecture of 802.1x Authentication1-1 The Mechanism of an 802.1x Authentication System 1-3 Encapsulation of EAPoL Messages 1-3 802.1x Authentication Procedure 1-5 Timers Used in 802.1x1-9 Additional 802.1x Features on Switch 4200G 1-10 Introduction to 802.1x Configuration 1-13 Basic 802.1x Configuration 1-14 Configuration Prerequisites 1-14 Configuring Basic 802.1x Functions1-14 Timer and Maximum User Number Configuration1-15 Advanced 802.1x Configuration1-16 Configuring Proxy Checking1-16 Configuring Client Version Checking1-17 Enabling DHCP-triggered Authentication 1-18 Configuring Guest VLAN 1-18 Configuring 802.1x Re-Authentication1-19 Configuring the 802.1x Re-Authentication Timer 1-19 Displaying and Maintaining 802.1x Configuration1-20 Configuration Example1-20 802.1x Configuration Example 1-20 2 Quick EAD Deployment Configuration2-1 Introduction to Quick EAD Deployment 2-1 Quick EAD Deployment Overview2-1 Operation of Quick EAD Deployment2-1 Configuring Quick EAD Deployment2-2 Configuration Prerequisites 2-2 Configuration Procedure2-2 Displaying and Maintaining Quick EAD Deployment 2-3 Quick EAD Deployment Configuration Example2-3 Troubleshooting 2-5 3 HABP Configuration 3-1 Introduction to HABP3-1 HABP Server Configuration 3-1 HABP Client Configuration3-2 Displaying and Maintaining HABP Configuration3-2 4 System Guard Configuration4-1 System-Guard Overview 4-1 Configuring the System-Guard Feature 4-1 Configuring the System-Guard Feature 4-1
i
ii
802.1x Configuration
When configuring 802.1x, go to these sections for information you are interested in: Introduction to 802.1x Introduction to 802.1x Configuration Basic 802.1x Configuration Advanced 802.1x Configuration Displaying and Maintaining 802.1x Configuration Configuration Example
Introduction to 802.1x
The 802.1x protocol (802.1x for short) was developed by IEEE802 LAN/WAN committee to address security issues of wireless LANs. It was then used in Ethernet as a common access control mechanism for LAN ports to address mainly authentication and security problems. 802.1x is a port-based network access control protocol. It is used to perform port-level authentication and control of devices connected to the 802.1x-enabled ports. With the 802.1x protocol employed, a user-side device can access the LAN only when it passes the authentication. Those devices that fail to pass the authentication are denied access to the LAN. This section covers these topics: Architecture of 802.1x Authentication The Mechanism of an 802.1x Authentication System Encapsulation of EAPoL Messages 802.1x Authentication Procedure Timers Used in 802.1x Additional 802.1x Features on Switch 4200G
1-1
The supplicant system is the entity seeking access to the LAN. It resides at one end of a LAN segment and is authenticated by the authenticator system at the other end of the LAN segment. The supplicant system is usually a user terminal device. An 802.1x authentication is triggered when a user launches an 802.1x-capable client program on the supplicant system. Note that the client program must support the extensible authentication protocol over LAN (EAPoL). The authenticator system, residing at the other end of the LAN segment, is the entity that authenticates the connected supplicant system. The authenticator system is usually an 802.1x-supported network device, such as a 3Com series switch. It provides the port (physical or logical) for the supplicant system to access the LAN. The authentication server system is the entity that provides authentication services to the authenticator system. The authentication server system, usually a RADIUS server, serves to perform Authentication, Authorization, and Accounting (AAA) services to users. It also stores user information, such as user name, password, the VLAN a user should belong to, priority, and any Access Control Lists (ACLs) to be applied. There are four additional basic concepts related 802.1x: port access entity (PAE), controlled port and uncontrolled port, the valid direction of a controlled port and the access control method on ports.
I. PAE
A port access entity (PAE) is responsible for implementing algorithms and performing protocol-related operations in the authentication mechanism. The authenticator system PAE authenticates the supplicant systems when they log into the LAN and controls the status (authorized/unauthorized) of the controlled ports according to the authentication result. The supplicant system PAE responds to the authentication requests received from the authenticator system and submits user authentication information to the authenticator system. It also sends authentication requests and disconnection requests to the authenticator system PAE.
1-2
The controlled port can be used to pass service packets when it is in authorized state. It is blocked when not in authorized state. In this case, no packets can pass through it. Controlled port and uncontrolled port are two properties of a port. Packets reaching a port are visible to both the controlled port and uncontrolled port of the port.
EAP protocol packets transmitted between the supplicant system PAE and the authenticator system PAE are encapsulated as EAPoL packets. EAP protocol packets transmitted between the authenticator system PAE and the RADIUS server can either be encapsulated as EAP over RADIUS (EAPoR) packets or be terminated at system PAEs. The system PAEs then communicate with RADIUS servers through Password Authentication Protocol (PAP) or Challenge-Handshake Authentication Protocol (CHAP) packets. When a supplicant system passes the authentication, the authentication server passes the information about the supplicant system to the authenticator system. The authenticator system in turn determines the state (authorized or unauthorized) of the controlled port according to the instructions (accept or reject) received from the RADIUS server.
In an EAPoL packet: The PAE Ethernet type field holds the protocol identifier. The identifier for 802.1x is 0x888E. The Protocol version field holds the version of the protocol supported by the sender of the EAPoL packet. The Type field can be one of the following: 00: Indicates that the packet is an EAP-packet, which carries authentication information. 01: Indicates that the packet is an EAPoL-start packet, which initiates the authentication. 02: Indicates that the packet is an EAPoL-logoff packet, which sends logging off requests. 03: Indicates that the packet is an EAPoL-key packet, which carries key information. 04: Indicates that the packet is an EAPoL-encapsulated-ASF-Alert packet, which is used to support the alerting messages of Alerting Standards Forum (ASF). The Length field indicates the size of the Packet body field. A value of 0 indicates that the Packet Body field does not exist. The Packet body field differs with the Type field. Note that EAPoL-Start, EAPoL-Logoff, and EAPoL-Key packets are only transmitted between the supplicant system and the authenticator system. EAP packets are encapsulated by RADIUS protocol to allow them successfully reach the authentication servers. Network management-related information (such as alarming information) is encapsulated in EAPoL-Encapsulated-ASF-Alert packets, which are terminated by authenticator systems.
In an EAP packet: The Code field indicates the EAP packet type, which can be Request, Response, Success, or Failure. The Identifier field is used to match a Response packet with the corresponding Request packet.
1-4
The Length field indicates the size of an EAP packet, which includes the Code, Identifier, Length, and Data fields. The Data field carries the EAP packet, whose format differs with the Code field. A Success or Failure packet does not contain the Data field, so the Length field of it is 4. Figure 1-5 shows the format of the Data field of a Request packet or a Response packet. Figure 1-5 The format of the Data field of a Request packet or a Response packet
The Type field indicates the EAP authentication type. A value of 1 indicates Identity and that the packet is used to query the identity of the peer. A value of 4 represents MD5-Challenge (similar to PPP CHAP) and indicates that the packet includes query information. The Type Date field differs with types of Request and Response packets.
EAP packets
The Message-authenticator field, whose format is shown in Figure 1-7, is used to prevent unauthorized interception to access requesting packets during authentications using CHAP, EAP, and so on. A packet with the EAP-message field must also have the Message-authenticator field. Otherwise, the packet is regarded as invalid and is discarded. Figure 1-7 The format of an Message-authenticator field
1-5
1-6
EAPOL Start EAP- Request / Identity EAP- Response / Identity RADIUS Access - Request (EAP- Response / Identity)
RADIUS Access -Challenge ( EAP- Request /MD5 challenge) RADIUS Access - Request ( EAP- Response /MD5 challenge) RADIUS Access -Accept (EAP-Success)
EAP-Success
Port authorized
Handshake timer Handshake request [ EAP- Request / Identity] Handshake response [ EAP- Response / Identity] ...... EAPOL -Logoff Port unauthorized
The detailed procedure is as follows: A supplicant system launches an 802.1x client to initiate an access request by sending an EAPoL-start packet to the switch, with its user name and password provided. The 802.1x client program then forwards the packet to the switch to start the authentication process. Upon receiving the authentication request packet, the switch sends an EAP-request/identity packet to ask the 802.1x client for the user name. The 802.1x client responds by sending an EAP-response/identity packet to the switch with the user name contained in it. The switch then encapsulates the packet in a RADIUS Access-Request packet and forwards it to the RADIUS server. Upon receiving the packet from the switch, the RADIUS server retrieves the user name from the packet, finds the corresponding password by matching the user name in its database, encrypts the password using a randomly-generated key, and sends the key to the switch through an RADIUS access-challenge packet. The switch then sends the key to the 802.1x client. Upon receiving the key (encapsulated in an EAP-request/MD5 challenge packet) from the switch, the client program encrypts the password of the supplicant system with the key and sends the encrypted password (contained in an EAP-response/MD5 challenge packet) to the RADIUS server through the switch. (Normally, the encryption is irreversible.) The RADIUS server compares the received encrypted password (contained in a RADIUS access-request packet) with the locally-encrypted password. If the two match, it will then send
1-7
feedbacks (through a RADIUS access-accept packet and an EAP-success packet) to the switch to indicate that the supplicant system is authenticated. The switch changes the state of the corresponding port to accepted state to allow the supplicant system to access the network. The supplicant system can also terminate the authenticated state by sending EAPoL-Logoff packets to the switch. The switch then changes the port state from accepted to rejected.
In EAP relay mode, packets are not modified during transmission. Therefore if one of the four ways are used (that is, PEAP, EAP-TLS, EAP-TTLS or EAP-MD5) to authenticate, ensure that the authenticating ways used on the supplicant system and the RADIUS server are the same. However for the switch, you can simply enable the EAP relay mode by using the dot1x authentication-method eap command.
1-8
......
EAPOL- Logoff Port unauthorized
The authentication procedure in EAP terminating mode is the same as that in the EAP relay mode except that the randomly-generated key in the EAP terminating mode is generated by the switch, and that it is the switch that sends the user name, the randomly-generated key, and the supplicant system-encrypted password to the RADIUS server for further authentication.
1-9
Re-authentication timer (reauth-period). The switch initiates 802.1x re-authentication at the interval set by the re-authentication timer. RADIUS server timer (server-timeout). This timer sets the server-timeout period. After sending an authentication request packet to the RADIUS server, the switch sends another authentication request packet if it does not receive the response from the RADIUS server when this timer times out. Supplicant system timer (supp-timeout). This timer sets the supp-timeout period and is triggered by the switch after the switch sends a request/challenge packet to a supplicant system. The switch sends another request/challenge packet to the supplicant system if the switch does not receive the response from the supplicant system when this timer times out. Transmission timer (tx-period). This timer sets the tx-period and is triggered by the switch in two cases. The first case is when the client requests for authentication. The switch sends a unicast request/identity packet to a supplicant system and then triggers the transmission timer. The switch sends another request/identity packet to the supplicant system if it does not receive the reply packet from the supplicant system when this timer times out. The second case is when the switch authenticates the 802.1x client who cannot request for authentication actively. The switch sends multicast request/identity packets periodically through the port enabled with 802.1x function. In this case, this timer sets the interval to send the multicast request/identity packets. Client version request timer (ver-period). This timer sets the version period and is triggered after a switch sends a version request packet. The switch sends another version request packet if it does receive version response packets from the supplicant system when the timer expires.
H3C's CAMS Server is a service management system used to manage networks and to secure networks and user information. With the cooperation of other networking devices (such as switches) in the network, a CAMS server can implement the AAA functions and rights management.
Only disconnects the supplicant system but sends no Trap packets. Sends Trap packets without disconnecting the supplicant system. This function needs the cooperation of 802.1x client and a CAMS server. The 802.1x client needs to be capable of detecting multiple network adapters, proxies, and IE proxies. The CAMS server is configured to disable the use of multiple network adapters, proxies, or IE proxies. By default, an 802.1x client program allows use of multiple network adapters, proxies, and IE proxies. In this case, if the CAMS server is configured to disable use of multiple network adapters, proxies, or IE proxies, it prompts the 802.1x client to disable use of multiple network adapters, proxies, or IE proxies through messages after the supplicant system passes the authentication.
The client-checking function needs the support of H3Cs 802.1x client program. To implement the proxy detecting function, you need to enable the function on both the 802.1x client program and the CAMS server in addition to enabling the client version detecting function on the switch by using the dot1x version-check command.
The 802.1x client version-checking function needs the support of H3Cs 802.1x client program.
After the maximum number retries have been made and there are still ports that have not sent any response back, the switch will then add these ports to the guest VLAN. Users belonging to the guest VLAN can access the resources of the guest VLAN without being authenticated. But they need to be authenticated when accessing external resources. Normally, the guest VLAN function is coupled with the dynamic VLAN delivery function. Refer to AAA Operation for detailed information about the dynamic VLAN delivery function.
When re-authenticating a user, a switch goes through the complete authentication process. It transmits the username and password of the user to the server. The server may authenticate the username and password, or, however, use re-authentication for only accounting and user connection status checking and therefore does not authenticate the username and password any more. An authentication server running CAMS authenticates the username and password during re-authentication of a user in the EAP authentication mode but does not in PAP or CHAP authentication mode.
Internet
PC
PC
PC
1-12
The RADIUS server has the switch perform 802.1x re-authentication of users. The RADIUS server sends the switch an Access-Accept packet with the Termination-Action attribute field of 1. Upon receiving the packet, the switch re-authenticates the user periodically. You enable 802.1x re-authentication on the switch. With 802.1x re-authentication enabled, the switch re-authenticates users periodically.
802.1x re-authentication will fail if a CAMS server is used and configured to perform authentication but not accounting. This is because a CAMS server establishes a user session after it begins to perform accounting. Therefore, to enable 802.1x re-authentication, do not configure the accounting none command in the domain. This restriction does not apply to other types of servers.
802.1x users use domain names to associate with the ISP domains configured on switches Configure the AAA scheme (a local authentication scheme or a RADIUS scheme) to be adopted in the ISP domain. If you specify to use a local authentication scheme, you need to configure the user names and passwords manually on the switch. Users can pass the authentication through 802.1x client if they provide user names and passwords that match those configured on the switch. If you specify to adopt the RADIUS scheme, the supplicant systems are authenticated by a remote RADIUS server. In this case, you need to configure user names and passwords on the RADIUS server and perform RADIUS client-related configuration on the switches. You can also specify to adopt the RADIUS authentication scheme, with a local authentication scheme as a backup. In this case, the local authentication scheme is adopted when the RADIUS server fails. Refer to the AAA Operation for detailed information about AAA scheme configuration.
1-13
dot1x interface interface-list interface interface-type interface-number Required By default, 802.1x is disabled on all ports.
In port view
dot1x quit
dot1x port-control { authorized-force | unauthorized-force | auto } [ interface interface-list ] interface interface-type interface-number Optional By default, an 802.1x-enabled port operates in the auto mode.
In port view
Optional The default access control method on a port is MAC-based (that is, the macbased keyword is used by default).
In port view
1-14
Use the command Optional dot1x handshake enable interface interface-type interface-number
Remarks
802.1x configurations take effect only after you enable 802.1x both globally and for specified ports. The settings of 802.1x and MAC address learning limit are mutually exclusive. Enabling 802.1x on a port will prevent you from setting the limit on MAC address learning on the port and vice versa. The settings of 802.1x and aggregation group member are mutually exclusive. Enabling 802.1x on a port will prevent you from adding the port to an aggregation group and vice versa. When the switch itself operates as an authentication server, its authentication method for 802.1x users cannot be configured as EAP. Handshake packets are used to test whether a user is online or not. Users need to run the proprietary client software of H3C to respond to the handshake packets. As clients not running the H3C client software do not support the online user handshaking function, switches cannot receive handshake acknowledgement packets from them in handshaking periods. To prevent users being falsely considered offline, you need to disable the online user handshaking function in this case.
quit Optional Set the maximum retry times to send request packets By default, the maximum retry times to send a request packet is 2. That is, the authenticator system sends a request packet to a supplicant system for up to two times by default.
1-15
To do
Use the command... Optional dot1x timer { handshake-period handshake-period-value | quiet-period quiet-period-value | server-timeout server-timeout-value | supp-timeout supp-timeout-value | tx-period tx-period-value | ver-period ver-period-value }
Remarks
The settings of 802.1x timers are as follows. 1) 2) 3) 4) 5) 6) handshake-period-value: 15 seconds quiet-period-value: 60 seconds server-timeout-value: 100 seconds supp-timeout-value: 30 seconds tx-period-value: 30 seconds ver-period-value: 30 seconds
As for the dot1x max-user command, if you execute it in system view without specifying the interface-list argument, the command applies to all ports. You can also use this command in port view. In this case, this command applies to the current port only and the interface-list argument is not needed. As for the configuration of 802.1x timers, the default values are recommended.
1-16
Use the command... Required dot1x supp-proxy-check { logoff | trap } dot1x supp-proxy-check { logoff | trap } [ interface interface-list ] interface interface-type interface-number Required
Remarks
In port view
The proxy checking function needs the cooperation of H3C's 802.1x client (iNode) program. The proxy checking function depends on the online user handshaking function. To enable the proxy detecting function, you need to enable the online user handshaking function first. The configuration listed in the above table takes effect only when it is performed on CAMS as well as on the switch. In addition, the client version checking function needs to be enabled on the switch too (by using the dot1x version-check command).
In port view
1-17
As for the dot1x version-user command, if you execute it in system view without specifying the interface-list argument, the command applies to all ports. You can also execute this command in port view. In this case, this command applies to the current port only and the interface-list argument is not needed.
dot1x guest-vlan vlan-id [ interface interface-list ] interface interface-type interface-number Required By default, the guest VLAN function is disabled.
In port view
1-18
The guest VLAN function is available only when the switch operates in the port-based access control mode. Only one guest VLAN can be configured for each switch. The guest VLAN function cannot be implemented if you configure the dot1x dhcp-launch command on the switch to enable DHCP-triggered authentication. This is because the switch does not send authentication packets in that case.
To enable 802.1x re-authentication on a port, you must first enable 802.1x globally and on the port. When re-authenticating a user, a switch goes through the complete authentication process. It transmits the username and password of the user to the server. The server may authenticate the username and password, or, however, use re-authentication for only accounting and user connection status checking and therefore does not authenticate the username and password any more. An authentication server running CAMS authenticates the username and password during re-authentication of a user in the EAP authentication mode but does not in PAP or CHAP authentication mode.
1-19
During re-authentication, the switch always uses the latest re-authentication interval configured, no matter which of the above-mentioned two ways is used to determine the re-authentication interval. For example, if you configure a re-authentication interval on the switch and the switch receives an Access-Accept packet whose Termination-Action attribute field is 1, the switch will ultimately use the value of the Session-timeout attribute field as the re-authentication interval. The following introduces how to configure the 802.1x re-authentication timer on the switch. Follow these steps to configure the re-authentication interval: To do... Enter system view Configure a re-authentication interval Use the command... system-view dot1x timer reauth-period reauth-period-value Optional By default, the re-authentication interval is 3,600 seconds. Remarks
Configuration Example
802.1x Configuration Example
Network requirements
Authenticate users on all ports to control their accesses to the Internet. The switch operates in MAC-based access control mode. All supplicant systems that pass the authentication belong to the default domain named aabbcc.net. The domain can accommodate up to 30 users. As for authentication, a supplicant system is authenticated locally if the RADIUS server fails. And as for accounting, a supplicant system is disconnected by force if the RADIUS server fails. The name of an authenticated supplicant system is not suffixed with the domain name. A connection is terminated if the total size of the data passes through it during a period of 20 minutes is less than 2,000 bytes. The switch is connected to a server comprising of two RADIUS servers whose IP addresses are 10.11.1.1 and 10.11.1.2. The RADIUS server with an IP address of 10.11.1.1 operates as the primary authentication server and the secondary accounting server. The other operates as the secondary authentication server and primary accounting server. The password for the switch and the authentication RADIUS servers to exchange message is name. And the password for the switch and the accounting RADIUS servers to exchange message is money. The switch sends another packet to the RADIUS servers again if it sends a packet to the RADIUS server and does not receive response for 5 seconds, with the maximum number of retries of 5. And the switch sends
1-20
a real-time accounting packet to the RADIUS servers once in every 15 minutes. A user name is sent to the RADIUS servers with the domain name truncated. The user name and password for local 802.1x authentication are localuser and localpass (in plain text) respectively. The idle disconnecting function is enabled.
Network diagram
Figure 1-12 Network diagram for AAA configuration with 802.1x and RADIUS enabled
Configuration procedure
Following configuration covers the major AAA/RADIUS configuration commands. Refer to AAA Operation for the information about these commands. Configuration on the client and the RADIUS servers is omitted.
# Set the access control method to MAC-based (This operation can be omitted, as MAC-based is the default).
[Sysname] dot1x port-method macbased interface GigabitEthernet 1/0/1
# Create a RADIUS scheme named radius1 and enter RADIUS scheme view.
[Sysname] radius scheme radius1
# Set the password for the switch and the authentication RADIUS servers to exchange messages.
[Sysname-radius-radius1] key authentication name
# Set the password for the switch and the accounting RADIUS servers to exchange messages.
[Sysname-radius-radius1] key accounting money
# Set the interval and the number of the retries for the switch to send packets to the RADIUS servers.
[Sysname-radius-radius1] timer 5 [Sysname-radius-radius1] retry 5
# Set the timer for the switch to send real-time accounting packets to the RADIUS servers.
[Sysname-radius-radius1] timer realtime-accounting 15
# Configure to send the user name to the RADIUS server with the domain name truncated.
[Sysname-radius-radius1] user-name-format without-domain [Sysname-radius-radius1] quit
# Specify to adopt radius1 as the RADIUS scheme of the user domain. If RADIUS server is invalid, specify to adopt the local authentication scheme.
[Sysname-isp-aabbcc.net] scheme radius-scheme radius1 local
# Specify the maximum number of users the user domain can accommodate to 30.
[Sysname-isp-aabbcc.net] access-limit enable 30
# Enable the idle disconnecting function and set the related parameters.
[Sysname-isp-aabbcc.net] idle-cut enable 20 2000 [Sysname-isp-aabbcc.net] quit
1-22
Restricted access
Before passing 802.1x authentication, a user is restricted (through ACLs) to a specific range of IP addresses or a specific server. Services like EAD client upgrading/download and dynamic address assignment are available on the specific server.
HTTP redirection
In the HTTP redirection approach, when the terminal users that have not passed 802.1x authentication access the Internet through Internet Explorer, they are redirected to a predefined URL for EAD client download. The two functions ensure that all the users without an EAD client have downloaded and installed one from the specified server themselves before they can access the Internet, thus decreasing the complexity and effort that EAD client deployment may involve.
The quick EAD deployment feature takes effect only when the authorization mode of an 802.1x-enabled port is set to auto.
2-1
Configuration Procedure
Configuring a free IP range
A free IP range is an IP range that users can access before passing 802.1x authentication. Follow these steps to configure a free IP range: To do... Enter system view Configure the URL for HTTP redirection Configure a free IP range Use the command... system-view dot1x url url-string dot1x free-ip ip-address { mask-address | mask-length } Required Required By default, no free IP range is configured. Remarks
You must configure the URL for HTTP redirection before configuring a free IP range. A URL must start with http:// and the segment where the URL resides must be in the free IP range. Otherwise, the redirection function cannot take effect. You must disable the DHCP-triggered authentication function of 802.1x before configuring a free IP range. With dot1x enabled but quick EAD deployment disabled, users cannot access the DHCP server if they fail 802.1x authentication. With quick EAD deployment enabled, users can obtain IP addresses dynamically before passing authentication if the IP address of the DHCP server is in the free IP range. The quick EAD deployment function applies to only ports with the authorization mode set to auto through the dot1x port-control command. At present, 802.1x is the only access approach that supports quick EAD deployment. Currently, the quick EAD deployment function does not support port security. The configured free IP range cannot take effect if you enable port security. The quick EAD deployment function and the MAC address authentication function are mutually exclusive. You cannot configure both the functions on the switch.
large number of users log in but cannot pass authentication, the switch may run out of ACL resources, preventing other users from logging in. A timer called ACL timer is designed to solve this problem. You can control the usage of ACL resources by setting the ACL timer. The ACL timer starts once a user gets online. If the user has not passed authentication when the ACL timer expires, the occupied ACL resources are released for other users to use. When a tremendous of access requests are present, you can decrease the timeout period of the ACL timer appropriately for higher utilization of ACL resources. Follow these steps to configure the ACL timer: To do... Enter system view Set the ACL timer Use the command... system-view dot1x timer acl-timeout acl-timeout-value Required By default, the ACL timeout period is 30 minutes. Remarks
2-3
Network diagram
Figure 2-1 Network diagram for quick EAD deployment
IP network
GE1/0/1
Switch 192.168.0.110/24
Host 192.168.0.109/24
Configuration procedure
Before enabling quick EAD deployment, make sure sure that: The Web server is configured properly. The default gateway of the PC is configured as the IP address of the Layer-3 virtual interface of the VLAN to which the port that is directly connected with the PC belongs.
2-4
Troubleshooting
Symptom: A user cannot be redirected to the specified URL server, no matter what URL the user enters in the IE address bar. Solution: If a user enters an IP address in a format other than the dotted decimal notation, the user may not be redirected. This is related with the operating system used on the PC. In this case, the PC considers the IP address string a name and tries to resolve the name. If the resolution fails, the PC will access a specific website. Generally, this address is not in dotted decimal notation. As a result, the PC cannot receive any ARP response and therefore cannot be redirected. To solve this problem, the user needs to enter an IP address that is not in the free IP range in dotted decimal notation. If a user enters an address in the free IP range, the user cannot be redirected. This is because the switch considers that the user wants to access a host in the free IP range, unconcerned about whether this PC exists or not. To solve this problem, the user needs to enter an address not in the free IP range. Check that you have configured an IP address in the free IP range for the Web server and a correct URL for redirection, and that the server provides Web services properly.
2-5
HABP Configuration
When configuring HABP, go to these sections for information you are interested in: Introduction to HABP HABP Server Configuration HABP Client Configuration Displaying and Maintaining HABP Configuration
Introduction to HABP
When a switch is configured with the 802.1x function, 802.1x will authenticate and authorize 802.1x-enabled ports and allow only the authorized ports to forward packets. In case a port fails 802.1x authentication and authorization, service packets from and to that port will be blocked, making it impossible to manage the switch attached to the port. The Huawei Authentication Bypass Protocol (HABP) aims at solving this problem. An HABP packet carries the MAC addresses of the attached switches with it. It can bypass the 802.1x authentications when traveling between HABP-enabled switches, through which management devices can obtain the MAC addresses of the attached switches and thus the management of the attached switches is feasible. HABP is built on the client-server model. Typically, the HABP server sends HABP requests to the client periodically to collect the MAC address(es) of the attached switch(es). The client responds to the requests, and forwards the HABP requests to the attached switch(es). The HABP server usually runs on the administrative device while the HABP client runs on the attached switches. For ease of switch management, it is recommended that you enable HABP for 802.1x-enabled switches.
3-1
To do...
Remarks
By default, a switch operates as an HABP client after you enable HABP on the switch. If you want to use the switch as a management switch, you need to configure the switch to be an HABP server. Optional
The default interval for an HABP server to send HABP request packets is 20 seconds.
3-2
System-Guard Overview
At first, you must determine whether the CPU is under attack to implement system guard for the CPU. You should not determine whether the CPU is under attack just according to whether congestion occurs in a queue. Instead, you must do that in the following ways: According to the number of packets processed in the CPU in a time range. Or according to the time for one hundred packets to be processed. If the CPU is under attack, the rate of packets to be processed in the CPU in a certain queue will exceed the threshold value. In this case, you can determine that the CPU is under attack. Through analyzing these packets , you get to know the characteristics of the attack source, and then you can adopt different filtering rules according the characteristics of the attack source. Thus, system guard is implemented.
4-1
Table 4-2 Display and maintain system-guard Operation Display the record of detected attacks Display the state of the system-guard feature Command display system-guard attack-record display system-guard state
4-2
Table of Contents
1 AAA Overview 1-1 Introduction to AAA 1-1 Authentication1-1 Authorization1-1 Accounting1-1 Introduction to ISP Domain 1-2 Introduction to AAA Services 1-2 Introduction to RADIUS 1-2 Introduction to HWTACACS 1-6 2 AAA Configuration 2-1 AAA Configuration Task List 2-1 Creating an ISP Domain and Configuring Its Attributes 2-2 Configuring an AAA Scheme for an ISP Domain 2-3 Configuring Dynamic VLAN Assignment2-6 Configuring the Attributes of a Local User2-7 Cutting Down User Connections Forcibly2-9 RADIUS Configuration Task List2-9 Creating a RADIUS Scheme 2-11 Configuring RADIUS Authentication/Authorization Servers 2-11 Configuring RADIUS Accounting Servers 2-12 Configuring Shared Keys for RADIUS Messages 2-13 Configuring the Maximum Number of RADIUS Request Transmission Attempts2-14 Configuring the Type of RADIUS Servers to be Supported 2-14 Configuring the Status of RADIUS Servers2-15 Configuring the Attributes of Data to be Sent to RADIUS Servers 2-16 Configuring the Local RADIUS Server 2-17 Configuring Timers for RADIUS Servers2-18 Enabling Sending Trap Message when a RADIUS Server Goes Down 2-19 Enabling the User Re-Authentication at Restart Function2-19 HWTACACS Configuration Task List2-21 Creating a HWTACACS Scheme 2-21 Configuring TACACS Authentication Servers 2-21 Configuring TACACS Authorization Servers 2-22 Configuring TACACS Accounting Servers 2-23 Configuring Shared Keys for HWTACACS Messages 2-23 Configuring the Attributes of Data to be Sent to TACACS Servers 2-24 Configuring the Timers Regarding TACACS Servers 2-25 Displaying and Maintaining AAA Configuration 2-26 Displaying and Maintaining AAA Configuration2-26 Displaying and Maintaining RADIUS Protocol Configuration 2-26 Displaying and Maintaining HWTACACS Protocol Configuration 2-26 AAA Configuration Examples2-27 Remote RADIUS Authentication of Telnet/SSH Users 2-27
i
Local Authentication of FTP/Telnet Users2-28 HWTACACS Authentication and Authorization of Telnet Users 2-30 Troubleshooting AAA 2-31 Troubleshooting RADIUS Configuration2-31 Troubleshooting HWTACACS Configuration 2-31 3 EAD Configuration3-1 Introduction to EAD 3-1 Typical Network Application of EAD 3-1 EAD Configuration 3-1 EAD Configuration Example 3-2
ii
AAA Overview
Introduction to AAA
AAA is the acronym for the three security functions: authentication, authorization and accounting. It provides a uniform framework for you to configure these three functions to implement network security management. Authentication: Defines what users can access the network, Authorization: Defines what services can be available to the users who can access the network, and Accounting: Defines how to charge the users who are using network resources. Typically, AAA operates in the client/server model: the client runs on the managed resources side while the server stores the user information. Thus, AAA is well scalable and can easily implement centralized management of user information.
Authentication
AAA supports the following authentication methods: None authentication: Users are trusted and are not checked for their validity. Generally, this method is not recommended. Local authentication: User information (including username, password, and some other attributes) is configured on this device, and users are authenticated on this device instead of on a remote device. Local authentication is fast and requires lower operational cost, but has the deficiency that information storage capacity is limited by device hardware. Remote authentication: Users are authenticated remotely through RADIUS or HWTACACS protocol. This device (for example, a 3Com switch) acts as the client to communicate with the RADIUS or TACACS server. Remote authentication allows convenient centralized management and is feature-rich. However, to implement remote authentication, a server is needed and must be configured properly.
Authorization
AAA supports the following authorization methods: Direct authorization: Users are trusted and directly authorized. Local authorization: Users are authorized according to the related attributes configured for their local accounts on this device. RADIUS authorization: Users are authorized after they pass RADIUS authentication. In RADIUS protocol, authentication and authorization are combined together, and authorization cannot be performed alone without authentication. HWTACACS authorization: Users are authorized by a TACACS server.
Accounting
AAA supports the following accounting methods:
1-1
None accounting: No accounting is performed for users. Remote accounting: User accounting is performed on a remote RADIUS or TACACS server.
What is RADIUS
Remote Authentication Dial-in User Service (RADIUS) is a distributed service based on client/server structure. It can prevent unauthorized access to your network and is commonly used in network environments where both high security and remote user access service are required. The RADIUS service involves three components: Protocol: Based on the UDP/IP layer, RFC 2865 and 2866 define the message format and message transfer mechanism of RADIUS, and define 1812 as the authentication port and 1813 as the accounting port. Server: RADIUS Server runs on a computer or workstation at the center. It stores and maintains user authentication information and network service access information. Client: RADIUS Client runs on network access servers throughout the network. RADIUS operates in the client/server model. A switch acting as a RADIUS client passes user information to a specified RADIUS server, and takes appropriate action (such as establishing/terminating user connection) depending on the responses returned from the server. The RADIUS server receives user connection requests, authenticates users, and returns all required information to the switch. Generally, a RADIUS server maintains the following three databases (see Figure 1-1): Users: This database stores information about users (such as username, password, protocol adopted and IP address). Clients: This database stores information about RADIUS clients (such as shared key). Dictionary: The information stored in this database is used to interpret the attributes and attribute values in the RADIUS protocol.
1-2
In addition, a RADIUS server can act as a client of some other AAA server to provide authentication or accounting proxy service.
The basic message exchange procedure of RADIUS is as follows: 1) 2) 3) The user enters the username and password. The RADIUS client receives the username and password, and then sends an authentication request (Access-Request) to the RADIUS server. The RADIUS server compares the received user information with that in the Users database to authenticate the user. If the authentication succeeds, the RADIUS server sends back to the RADIUS client an authentication response (Access-Accept), which contains the users authorization information. If the authentication fails, the server returns an Access-Reject response.
1-3
4)
The RADIUS client accepts or denies the user depending on the received authentication result. If it accepts the user, the RADIUS client sends a start-accounting request (Accounting-Request, with the Status-Type attribute value = start) to the RADIUS server.
5) 6) 7) 8) 9)
The RADIUS server returns a start-accounting response (Accounting-Response). The user starts to access network resources. The RADIUS client sends a stop-accounting request (Accounting-Request, with the Status-Type attribute value = stop) to the RADIUS server. The RADIUS server returns a stop-accounting response (Accounting-Response). The access to network resources is ended.
1)
The Code field (one byte) decides the type of RADIUS message, as shown in Table 1-1.
Table 1-1 Description on the major values of the Code field Code Message type Message description Direction: client->server. The client transmits this message to the server to determine if the user can access the network. 1 Access-Request This message carries user information. It must contain the User-Name attribute and may contain the following attributes: NAS-IP-Address, User-Password and NAS-Port. Direction: server->client. 2 Access-Accept The server transmits this message to the client if all the attribute values carried in the Access-Request message are acceptable (that is, the user passes the authentication). Direction: server->client. 3 Access-Reject The server transmits this message to the client if any attribute value carried in the Access-Request message is unacceptable (that is, the user fails the authentication).
1-4
Code
Message type
Message description Direction: client->server. The client transmits this message to the server to request the server to start or end the accounting (whether to start or to end the accounting is determined by the Acct-Status-Type attribute in the message). This message carries almost the same attributes as those carried in the Access-Request message. Direction: server->client.
Accounting-Request
Accounting-Response
The server transmits this message to the client to notify the client that it has received the Accounting-Request message and has correctly recorded the accounting information.
2)
The Identifier field (one byte) is used to match requests and responses. It changes whenever the content of the Attributes field changes, and whenever a valid response has been received for a previous request, but remains unchanged for message retransmission.
3)
The Length field (two bytes) specifies the total length of the message (including the Code, Identifier, Length, Authenticator and Attributes fields). The bytes beyond the length are regarded as padding and are ignored upon reception. If a received message is shorter than what the Length field indicates, it is discarded.
4)
The Authenticator field (16 bytes) is used to authenticate the response from the RADIUS server; and is used in the password hiding algorithm. There are two kinds of authenticators: Request Authenticator and Response Authenticator.
5)
The Attributes field contains specific authentication/authorization/accounting information to provide the configuration details of a request or response message. This field contains a list of field triplet (Type, Length and Value): The Type field (one byte) specifies the type of an attribute. Its value ranges from 1 to 255. Table 1-2 lists the attributes that are commonly used in RADIUS authentication/authorization. The Length field (one byte) specifies the total length of the attribute in bytes (including the Type, Length and Value fields). The Value field (up to 253 bytes) contains the information of the attribute. Its format is determined by the Type and Length fields.
Table 1-2 RADIUS attributes Type field value 1 2 3 4 5 6 7 8 9 Attribute type User-Name User-Password CHAP-Password NAS-IP-Address NAS-Port Service-Type Framed-Protocol Framed-IP-Address Framed-IP-Netmask
1-5
Attribute type Framed-IPX-Network State Class Vendor-Specific Session-Timeout Idle-Timeout Termination-Action Called-Station-Id Calling-Station-Id
Attribute type Framed-Routing Filter-ID Framed-MTU Framed-Compression Login-IP-Host Login-Service Login-TCP-Port (unassigned) Reply-Message Callback-Number Callback-ID (unassigned) Framed-Route
Attribute type NAS-Identifier Proxy-State Login-LAT-Service Login-LAT-Node Login-LAT-Group Framed-AppleTalk-Link Framed-AppleTalk-Network Framed-AppleTalk-Zone (reserved for accounting) CHAP-Challenge NAS-Port-Type Port-Limit Login-LAT-Port
The RADIUS protocol has good scalability. Attribute 26 (Vender-Specific) defined in this protocol allows a device vendor to extend RADIUS to implement functions that are not defined in standard RADIUS. Figure 1-4 depicts the format of attribute 26. The Vendor-ID field used to identify a vendor occupies four bytes, where the first byte is 0, and the other three bytes are defined in RFC 1700. Here, the vendor can encapsulate multiple customized sub-attributes (containing vendor-specific Type, Length and Value) to implement a RADIUS extension. Figure 1-4 Vendor-specific attribute format
0 Type Vendor-ID 7 Length 15 7 Vendor-ID Type (specified) Length (specified) 31
Introduction to HWTACACS
What is HWTACACS
Huawei Terminal Access Controller Access Control System (HWTACACS) is an enhanced security protocol based on TACACS (RFC 1492). Similar to the RADIUS protocol, it implements AAA for different types of users (such as PPP, VPDN, and terminal users) through communicating with TACACS server in client-server mode.
1-6
Compared with RADIUS, HWTACACS provides more reliable transmission and encryption, and therefore is more suitable for security control. Table 1-3 lists the primary differences between HWTACACS and RADIUS. Table 1-3 Differences between HWTACACS and RADIUS HWTACACS Adopts TCP, providing more reliable network transmission. Encrypts the entire message except the HWTACACS header. Separates authentication from authorization. For example, you can use one TACACS server for authentication and another TACACS server for authorization. Is more suitable for security control. Supports configuration command authorization. Adopts UDP. Encrypts only the password field in authentication message. Combines authentication and authorization. Is more suitable for accounting. Does not support. RADIUS
In a typical HWTACACS application (as shown in Figure 1-50), a terminal user needs to log into the switch to perform some operations. As a HWTACACS client, the switch sends the username and password to the TACACS server for authentication. After passing authentication and being authorized, the user successfully logs into the switch to perform operations. Figure 1-5 Network diagram for a typical HWTACACS application
HWTACACS server
Host
HWTACACS client
HWTACACS server
1-7
The basic message exchange procedure is as follows: 1) 2) 3) 4) 5) 6) 7) 8) A user sends a login request to the switch acting as a TACACS client, which then sends an authentication start request to the TACACS server. The TACACS server returns an authentication response, asking for the username. Upon receiving the response, the TACACS client requests the user for the username. After receiving the username from the user, the TACACS client sends an authentication continuance message carrying the username. The TACACS server returns an authentication response, asking for the password. Upon receiving the response, the TACACS client requests the user for the login password. After receiving the password, the TACACS client sends an authentication continuance message carrying the password to the TACACS server. The TACACS server returns an authentication response, indicating that the user has passed the authentication. The TACACS client sends a user authorization request to the TACACS server. The TACACS server returns an authorization response, indicating that the user has passed the authorization.
1-8
9)
After receiving the response indicating an authorization success, the TACACS client pushes the configuration interface of the switch to the user.
10) The TACACS client sends an accounting start request to the TACACS server. 11) The TACACS server returns an accounting response, indicating that it has received the accounting start request. 12) The user logs out; the TACACS client sends an accounting stop request to the TACACS server. 13) The TACACS server returns an accounting response, indicating that it has received the accounting stop request.
1-9
AAA Configuration
Complete the following tasks to configure AAA (configuring separate AAA schemes for an ISP domain):
2-1
Task Creating an ISP Domain and Configuring Its Attributes Configuring separate AAA schemes Required Required
Remarks
Required With separate AAA schemes, you can specify authentication, authorization and accounting schemes respectively. You need to configure RADIUS or HWATACACS before performing RADIUS or HWTACACS authentication.
AAA configuration
Configuring Dynamic VLAN Assignment Configuring the Attributes of a Local User Cutting Down User Connections Forcibly
2-2
Remarks
By default, the accounting-optional switch is off. Optional By default, the messenger function is disabled.
Note that: On a Switch 4200G, each access user belongs to an ISP domain. You can configure up to 16 ISP domains on the switch. When a user logs in, if no ISP domain name is carried in the username, the switch assumes that the user belongs to the default ISP domain. If you have configured to use "." as the delimiter, for a username that contains multiple ".", the first "." will be used as the domain delimiter. If you have configured to use "@" as the delimiter, the "@" must not appear more than once in the username. If . is the delimiter, the username must not contain any @. If the system does not find any available accounting server or fails to communicate with any accounting server when it performs accounting for a user, it does not disconnect the user as long as the accounting optional command has been executed, though it cannot perform accounting for the user in this case.
H3C's CAMS Server is a service management system used to manage networks and ensure network and user information security. With the cooperation of other networking devices (such as switches) in a network, a CAMS server can implement the AAA functions and right management.
Remarks Required Required By default, an ISP domain uses the local AAA scheme.
You can execute the scheme radius-scheme radius-scheme-name command to adopt an already configured RADIUS scheme to implement all the three AAA functions. If you adopt the local scheme, only the authentication and authorization functions are implemented, the accounting function cannot be implemented. If you execute the scheme radius-scheme radius-scheme-name local command, the local scheme is used as the secondary scheme in case no RADIUS server is available. That is, if the communication between the switch and a RADIUS server is normal, the local scheme is not used; otherwise, the local scheme is used. If you execute the scheme hwtacacs-scheme hwtacacs-scheme-name local command, the local scheme is used as the secondary scheme in case no TACACS server is available. That is, if the communication between the switch and a TACACS server is normal, the local scheme is not used; if the TACACS server is not reachable or there is a key error or NAS IP error, the local scheme is used. If you execute the scheme local or scheme none command to adopt local or none as the primary scheme, the local authentication is performed or no authentication is performed. In this case you cannot specify any RADIUS scheme or HWTACACS scheme at the same time. If you configure to use none as the primary scheme, FTP users of the domain cannot pass authentication. Therefore, you cannot specify none as the primary scheme if you want to enable FTP service.
Only authentication is supported for FTP users. Authentication: RADIUS, local, or HWTACACS. Follow these steps to configure separate AAA schemes: To do Enter system view Create an ISP domain and enter its view, or enter the view of an existing ISP domain Use the command system-view domain isp-name Required Remarks
2-4
To do
Use the command authentication { radius-scheme radius-scheme-name [ local ] | hwtacacs-scheme hwtacacs-scheme-name [ local ] | local | none } authentication super hwtacacs-scheme hwtacacs-scheme-name Optional
Remarks
By default, no separate authentication scheme is configured. Optional By default, no HWTACACS authentication scheme is configured. Optional By default, no separate authorization scheme is configured. Optional By default, no separate accounting scheme is configured.
authorization { none | hwtacacs-scheme hwtacacs-scheme-name } accounting { none | radius-scheme radius-scheme-name | hwtacacs-scheme hwtacacs-scheme-name }
RADIUS scheme and local scheme do not support the separation of authentication and authorization. Therefore, pay attention when you make authentication and authorization configuration for a domain: When the scheme radius-scheme or scheme local command is executed and the authentication command is not executed, the authorization information returned from the RADIUS or local scheme still takes effect even if the authorization none command is executed. The Switch 4200G adopts hierarchical protection for command lines so as to inhibit users at lower levels from using higher level commands to configure the switches. For details about configuring a HWTACACS authentication scheme for low-to-high user level switching, refer to Switching User Level in the Command Line Interface Operation.
Configuration guidelines
Suppose a combined AAA scheme is available. The system selects AAA schemes according to the following principles: If authentication, authorization, accounting each have a separate scheme, the separate schemes are used. If you configure only a separate authentication scheme (that is, there are no separate authorization and accounting schemes configured), the combined scheme is used for authorization and accounting. In this case, if the combined scheme uses RADIUS or HWTACACS, the system never uses the secondary scheme for authorization and accounting. If you configure no separate scheme, the combined scheme is used for authentication, authorization, and accounting. In this case, if the system uses the secondary local scheme for authentication, it also does so for authorization and accounting; if the system uses the first scheme
2-5
for authentication, it also does so for authorization and accounting, even if authorization and accounting fail.
name string
2-6
In string mode, if the VLAN ID assigned by the RADIUS server is a character string containing only digits (for example, 1024), the switch first regards it as an integer VLAN ID: the switch transforms the string to an integer value and judges if the value is in the valid VLAN ID range; if it is, the switch adds the authenticated port to the VLAN with the integer value as the VLAN ID (VLAN 1024, for example). To implement dynamic VLAN assignment on a port where both MSTP and 802.1x are enabled, you must set the MSTP port to an edge port.
2-7
Remarks
By default, the password display mode of all access users is auto, indicating the passwords of access users are displayed in the modes set by the password command. Required
Add a local user and enter local user view Set a password for the local user
By default, the user is in active state, that is, the user is allowed to request network services.
Required By default, the system does not authorize the user to access any service.
Optional level level By default, the privilege level of the user is 0. Required authorization vlan string By default, no authorized VLAN is configured for the local user. Optional attribute { ip ip-address | mac mac-address | idle-cut second | access-limit max-user-number | vlan vlan-id | location { nas-ip ip-address port port-number | port port-number } }* When binding the user to a remote port, you must use nas-ip ip-address to specify a remote access server IP address (here, ip-address is 127.0.0.1 by default, representing this device). When binding the user to a local port, you need not use nas-ip ip-address.
2-8
The following characters are not allowed in the user-name string: /:*?<>. And you cannot input more than one @ in the string. After the local-user password-display-mode cipher-force command is executed, any password will be displayed in cipher mode even though you specify to display a user password in plain text by using the password command. If a username and password is required for user authentication (RADIUS authentication as well as local authentication), the command level that a user can access after login is determined by the privilege level of the user. For SSH users using RSA shared key for authentication, the commands they can access are determined by the levels set on their user interfaces. If the configured authentication method is none or password authentication, the command level that a user can access after login is determined by the level of the user interface. If the clients connected to a port have different authorized VLANs, only the first client passing the MAC address authentication can be assigned with an authorized VLAN. The switch will not assign authorized VLANs for subsequent users passing MAC address authentication. In this case, you are recommended to connect only one MAC address authentication user or multiple users with the same authorized VLAN to a port. For local RADIUS authentication to take effect, the VLAN assignment mode must be set to string after you specify authorized VLANs for local users.
Required
You can use the display connection command to view the connections of Telnet users, but you cannot use the cut connection command to cut down their connections.
Task Creating a RADIUS Scheme Configuring RADIUS Authentication/Authorization Servers Configuring RADIUS Accounting Servers Configuring Shared Keys for RADIUS Messages Configuring the Maximum Number of RADIUS Request Transmission Attempts Configuring the RADIUS client Configuring the Type of RADIUS Servers to be Supported Configuring the Status of RADIUS Servers Configuring the Attributes of Data to be Sent to RADIUS Servers Configuring Timers for RADIUS Servers Enabling Sending Trap Message when a RADIUS Server Goes Down Enabling the User Re-Authentication at Restart Function Configuring the RADIUS server Refer to the configuration of the RADIUS Server.
Remarks Required Required Required Optional Optional Optional Optional Optional Optional Optional Optional
Complete the following tasks to configure RADIUS (the switch functions as a local RADIUS server): Task Creating a RADIUS Scheme Configuring RADIUS Authentication/Authorization Servers Configuring RADIUS Accounting Servers Configuring Shared Keys for RADIUS Messages Configuring the Maximum Number of RADIUS Request Transmission Attempts Configuring the RADIUS server Configuring the Type of RADIUS Servers to be Supported Configuring the Status of RADIUS Servers Configuring the Attributes of Data to be Sent to RADIUS Servers Configuring the Local RADIUS Server Configuring Timers for RADIUS Servers Enabling Sending Trap Message when a RADIUS Server Goes Down Configuring the RADIUS client Refer to the configuration of the RADIUS client Remarks Required Required Required Optional Optional Optional Optional Optional Required Optional Optional
The RADIUS service configuration is performed on a RADIUS scheme basis. In an actual network environment, you can either use a single RADIUS server or two RADIUS servers (primary and secondary servers with the same configuration but different IP addresses) in a RADIUS scheme. After
2-10
creating a new RADIUS scheme, you should configure the IP address and UDP port number of each RADIUS server you want to use in this scheme. These RADIUS servers fall into two types: authentication/authorization, and accounting. And for each type of server, you can configure two servers in a RADIUS scheme: primary server and secondary server. A RADIUS scheme has some parameters such as IP addresses of the primary and secondary servers, shared keys, and types of the RADIUS servers. In an actual network environment, you can configure the above parameters as required. But you should configure at least one authentication/authorization server and one accounting server, and you should keep the RADIUS server port settings on the switch consistent with those on the RADIUS servers.
Actually, the RADIUS service configuration only defines the parameters for information exchange between switch and RADIUS server. To make these parameters take effect, you must reference the RADIUS scheme configured with these parameters in an ISP domain view (refer to AAA Configuration).
2-11
Remarks
By default, a RADIUS scheme named "system" has already been created in the system. Required
Set the IP address and port number of the primary RADIUS authentication/authorization server
By default, the IP address and UDP port number of the primary server are 0.0.0.0 and 1812 respectively for a newly created RADIUS scheme. Optional
Set the IP address and port number of the secondary RADIUS authentication/authorization server
By default, the IP address and UDP port number of the secondary server are 0.0.0.0 and 1812 respectively for a newly created RADIUS scheme.
The authentication response sent from the RADIUS server to the RADIUS client carries authorization information. Therefore, you need not (and cannot) specify a separate RADIUS authorization server. In an actual network environment, you can specify one server as both the primary and secondary authentication/authorization servers, as well as specifying two RADIUS servers as the primary and secondary authentication/authorization servers respectively. The IP address and port number of the primary authentication server used by the default RADIUS scheme "system" are 127.0.0.1 and 1645.
Set the IP address and port number of the primary RADIUS accounting server
2-12
To do Set the IP address and port number of the secondary RADIUS accounting server
Remarks
By default, the IP address and UDP port number of the secondary accounting server are 0.0.0.0 and 1813 for a newly created RADIUS scheme. Optional By default, stop-accounting request buffering is enabled. Optional
Enable stop-accounting request buffering Set the maximum number of transmission attempts of a buffered stop-accounting request.
stop-accounting-buffer enable
By default, the system tries at most 500 times to transmit a buffered stop-accounting request. Optional
By default, the maximum allowed number of continuous real-time accounting failures is five. If five continuous failures occur, the switch cuts down the user connection.
In an actual network environment, you can specify one server as both the primary and secondary accounting servers, as well as specifying two RADIUS servers as the primary and secondary accounting servers respectively. In addition, because RADIUS adopts different UDP ports to exchange authentication/authorization messages and accounting messages, you must set a port number for accounting different from that set for authentication/authorization. With stop-accounting request buffering enabled, the switch first buffers the stop-accounting request that gets no response from the RADIUS accounting server, and then retransmits the request to the RADIUS accounting server until it gets a response, or the maximum number of transmission attempts is reached (in this case, it discards the request). You can set the maximum allowed number of continuous real-time accounting failures. If the number of continuously failed real-time accounting requests to the RADIUS server reaches the set maximum number, the switch cuts down the user connection. The IP address and port number of the primary accounting server of the default RADIUS scheme "system" are 127.0.0.1 and 1646 respectively. Currently, RADIUS does not support the accounting of FTP users.
2-13
To do Enter system view Create a RADIUS scheme and enter its view
Remarks
By default, a RADIUS scheme named "system" has already been created in the system. Required
Set a shared key for RADIUS authentication/authorization messages Set a shared key for RADIUS accounting messages
The authentication/authorization shared key and the accounting shared key you set on the switch must be respectively consistent with the shared key on the authentication/authorization server and the shared key on the accounting server.
2-14
To do Create a RADIUS scheme and enter its view Configure the type of RADIUS servers to be supported
Use the command Required radius scheme radius-scheme-name server-type { extended | standard }
Remarks
By default, a RADIUS scheme named "system" has already been created in the system. Optional
If you change the RADIUS server type, the units of data flows sent to RADIUS servers will be restored to the defaults. When the third party RADIUS server is used, you can select standard or extended as the server-type in a RADIUS scheme; when the CAMS server is used, you can select extended as the server-type in a RADIUS scheme.
2-15
To do Set the status of the secondary RADIUS authentication/authorization server Set the status of the secondary RADIUS accounting server
Use the command state secondary authentication { block | active } state secondary accounting { block | active }
Remarks
data-flow-format data { byte | giga-byte | kilo-byte | mega-byte } packet { giga-packet | kilo-packet | mega- packet | one-packet }
Set the MAC address format of the Calling-Station-Id (Type 31) field in RADIUS packets
2-16
Generally, the access users are named in the userid@isp-name or userid.isp-name format. Here, isp-name after the @ or . character represents the ISP domain name, by which the device determines which ISP domain a user belongs to. However, some old RADIUS servers cannot accept the usernames that carry ISP domain names. In this case, it is necessary to remove domain names from usernames before sending the usernames to RADIUS server. For this reason, the user-name-format command is designed for you to specify whether or not ISP domain names are carried in the usernames to be sent to RADIUS server. For a RADIUS scheme, if you have specified to remove ISP domain names from usernames, you should not use this RADIUS scheme in more than one ISP domain. Otherwise, such errors may occur: the RADIUS server regards two different users having the same name but belonging to different ISP domains as the same user (because the usernames sent to it are the same). In the default RADIUS scheme "system", ISP domain names are removed from usernames by default. The purpose of setting the MAC address format of the Calling-Station-Id (Type 31) field in RADIUS packets is to improve the switchs compatibility with different RADIUS servers. This setting is necessary when the format of Calling-Station-Id field recognizable to RADIUS servers is different from the default MAC address format on the switch. For details about field formats recognizable to RADIUS servers, refer to the corresponding RADIUS server manual.
2-17
If
you
adopt
the
local
RADIUS
server
function,
the
UDP
port
number
of
the
authentication/authorization server must be 1645, the UDP port number of the accounting server must be 1646, and the IP addresses of the servers must be set to the addresses of this switch. The message encryption key set by the local-server nas-ip ip-address key password command must be identical with the authentication/authorization message encryption key set by the key authentication command in the RADIUS scheme view of the RADIUS scheme on the specified NAS that uses this switch as its authentication server. The switch supports IP addresses and shared keys for up to 16 network access servers (NAS). That is, when acting as the local RADIUS server, the switch can provide authentication service to up to 16 network access servers (including the switch itself) at the same time. When acting as the local RADIUS server, the switch does not support EAP authentication (that is you cannot set the 802.1x authentication method as eap by using the dot1x authentication-method eap command).
2-18
Remarks
By default, the response timeout time of RADIUS servers is three seconds. Optional
Set the time that the switch waits before it try to re-communicate with primary server and restore the status of the primary server to active
By default, the switch waits five minutes before it restores the status of the primary server to active. Optional
This configuration takes effect on all RADIUS schemes. The switch considers a RADIUS server as being down if it has tried the configured maximum times to send a message to the RADIUS server but does not receive any response.
The user re-authentication at restart function applies only to the environment where the RADIUS authentication/authorization and accounting server is CAMS.
In an environment that a CAMS server is used to implement AAA functions, if the switch reboots after an exclusive user (a user whose concurrent online number is set to 1 on the CAMS) gets authenticated and authorized and begins being charged, the switch will give a prompt that the user has already been
2-19
online when the user re-logs into the network before the CAMS performs online user detection, and the user cannot get authenticated. In this case, the user can access the network again only when the CAMS administrator manually removes the user's online information. The user re-authentication at restart function is designed to resolve this problem. After this function is enabled, every time the switch restarts: 1) 2) 3) The switch generates an Accounting-On message, which mainly contains the following information: NAS-ID, NAS-IP-address (source IP address), and session ID. The switch sends the Accounting-On message to the CAMS at regular intervals. Once the CAMS receives the Accounting-On message, it sends a response to the switch. At the same time it finds and deletes the original online information of the users who were accessing the network through the switch before the restart according to the information (NAS-ID, NAS-IP-address and session ID) contained in the message, and ends the accounting for the users depending on the last accounting update message. 4) 5) Once the switch receives the response from the CAMS, it stops sending Accounting-On messages. If the switch does not receive any response from the CAMS after it has tried the configured maximum number of times to send the Accounting-On message, it will not send the Accounting-On message any more.
The switch can automatically generate the main attributes (NAS-ID, NAS-IP-address and session ID) contained in Accounting-On messages. However, you can also manually configure the NAS-IP-address with the nas-ip command. If you choose to manually configure the attribute, be sure to configure an appropriate valid IP address. If this attribute is not configured, the switch will automatically choose the IP address of a VLAN interface as the NAS-IP-address.
Follow these steps to enable the user re-authentication at restart function: To do Enter system view Enter RADIUS scheme view Use the command system-view radius scheme radius-scheme-name By default, this function is disabled. Enable the user re-authentication at restart function accounting-on enable [ send times | interval interval ] If you use this command without any parameter, the system will try at most 15 times to send an Accounting-On message at the interval of three seconds. Remarks
2-20
The system supports up to 16 HWTACACS schemes. You can delete a HWTACACS scheme only when it is not referenced.
2-21
To do Set the IP address and port number of the primary TACACS authentication server
Remarks
By default, the IP address of the primary authentication server is 0.0.0.0, and the port number is 0. Optional
Set the IP address and port number of the secondary TACACS authentication server
By default, the IP address of the secondary authentication server is 0.0.0.0, and the port number is 0.
You are not allowed to configure the same IP address for both primary and secondary authentication servers. If you do this, the system will prompt that the configuration fails. You can remove an authentication server setting only when there is no active TCP connection that is sending authentication messages to the server.
2-22
You are not allowed to configure the same IP address for both primary and secondary authorization servers. If you do this, the system will prompt that the configuration fails. You can remove a server only when it is not used by any active TCP connection for sending authorization messages.
Enable the stop-accounting message retransmission function and set the maximum number of transmission attempts of a buffered stop-accounting message
You are not allowed to configure the same IP address for both primary and secondary accounting servers. If you do this, the system will prompt that the configuration fails. You can remove a server only when it is not used by any active TCP connection for sending accounting messages.
The TACACS client and server adopt MD5 algorithm to encrypt HWTACACS messages before they are exchanged between the two parties. The two parties verify the validity of the HWTACACS messages received from each other by using the shared keys that have been set on them, and can accept and respond to the messages only when both parties have the same shared key. Follow these steps to configure shared keys for HWTACACS messages: To do Enter system view Create a HWTACACS scheme and enter its view Set a shared key for HWTACACS authentication, authorization or accounting messages Use the command system-view hwtacacs scheme hwtacacs-scheme-name key { accounting | authorization | authentication } string Required By default, no HWTACACS scheme exists. Required By default, no such key is set. Remarks
2-24
Generally, the access users are named in the userid@isp-name or userid.isp-name format. Where, isp-name after the @ or . character represents the ISP domain name. If the TACACS server does not accept the usernames that carry ISP domain names, it is necessary to remove domain names from usernames before they are sent to TACACS server.
Set the time that the switch must wait before it can restore the status of the primary server to active
To control the interval at which users are charge in real time, you can set the real-time accounting interval. After the setting, the switch periodically sends online users' accounting information to the TACACS server at the set interval. The real-time accounting interval must be a multiple of 3. The setting of real-time accounting interval somewhat depends on the performance of the TACACS client and server devices: A shorter interval requires higher device performance.
2-25
display radius scheme [ radius-scheme-name ] Available in any view display radius statistics display stop-accounting-buffer { radius-scheme radius-scheme-name | session-id session-id | time-range start-time stop-time | user-name user-name } reset stop-accounting-buffer { radius-scheme radius-scheme-name | session-id session-id | time-range start-time stop-time | user-name user-name } reset radius statistics
2-26
To do Display buffered non-response stop-accounting requests Clear HWTACACS message statistics Delete buffered non-response stop-accounting requests
Use the command display stop-accounting-buffer { hwtacacs-scheme hwtacacs-scheme-name reset hwtacacs statistics { accounting | authentication | authorization | all } reset stop-accounting-buffer hwtacacs-scheme hwtacacs-scheme-name
Remarks
The configuration procedure for remote authentication of SSH users by RADIUS server is similar to that for Telnet users. The following text only takes Telnet users as example to describe the configuration procedure for remote authentication.
Network requirements
In the network environment shown in Figure 2-1, you are required to configure the switch so that the Telnet users logging into the switch are authenticated by the RADIUS server. A RADIUS authentication server with IP address 10.110.91.164 is connected to the switch. On the switch, set the shared key it uses to exchange messages with the authentication RADIUS server to aabbcc. A CAMS server is used as the RADIUS server. You can select extended as the server-type in a RADIUS scheme. On the RADIUS server, set the shared key it uses to exchange messages with the switch to aabbcc, set the authentication port number, and add Telnet usernames and login passwords. The Telnet usernames added to the RADIUS server must be in the format of userid@isp-name if you have configured the switch to include domain names in the usernames to be sent to the RADIUS server in the RADIUS scheme.
2-27
Network diagram
Figure 2-1 Remote RADIUS authentication of Telnet users
RADIUS server
10.110.91.164/16
Internet
Telnet user
Configuration procedure
# Enter system view.
<Sysname> system-view
A Telnet user logging into the switch by a name in the format of userid @cams belongs to the cams domain and will be authenticated according to the configuration of the cams domain.
2-28
The configuration procedure for local authentication of FTP users is similar to that for Telnet users. The following text only takes Telnet users as example to describe the configuration procedure for local authentication.
Network requirements
In the network environment shown in Figure 2-2, you are required to configure the switch so that the Telnet users logging into the switch are authenticated locally.
Network diagram
Figure 2-2 Local authentication of Telnet users
Configuration procedure
Method 1: Using local authentication scheme. # Enter system view.
<Sysname> system-view
A Telnet user logging into the switch with the name telnet@system belongs to the "system" domain and will be authenticated according to the configuration of the "system" domain. Method 2: using local RADIUS server This method is similar to the remote authentication method described in Remote RADIUS Authentication of Telnet/SSH Users. However, you need to: Change the server IP address, and the UDP port number of the authentication server to 127.0.0.1, and 1645 respectively in the configuration step "Configure a RADIUS scheme" in Remote RADIUS Authentication of Telnet/SSH Users.
2-29
Enable the local RADIUS server function, set the IP address and shared key for the network access server to 127.0.0.1 and aabbcc, respectively. Configure local users.
Network diagram
Figure 2-3 Remote HWTACACS authentication and authorization of Telnet users
Authentication server
10.110.91.164/16
Internet
Telnet user
Configuration procedure
# Add a Telnet user. (Omitted here) # Configure a HWTACACS scheme.
<Sysname> system-view [Sysname] hwtacacs scheme hwtac [Sysname-hwtacacs-hwtac] primary authentication 10.110.91.164 49 [Sysname-hwtacacs-hwtac] primary authorization 10.110.91.164 49 [Sysname-hwtacacs-hwtac] key authentication aabbcc [Sysname-hwtacacs-hwtac] key authorization aabbcc [Sysname-hwtacacs-hwtac] user-name-format without-domain [Sysname-hwtacacs-hwtac] quit
2-30
Troubleshooting AAA
Troubleshooting RADIUS Configuration
The RADIUS protocol operates at the application layer in the TCP/IP protocol suite. This protocol prescribes how the switch and the RADIUS server of the ISP exchange user information with each other. Symptom 1: User authentication/authorization always fails. Possible reasons and solutions: The username is not in the userid@isp-name or userid.isp-name format, or the default ISP domain is not correctly specified on the switch Use the correct username format, or set a default ISP domain on the switch. The user is not configured in the database of the RADIUS server Check the database of the RADIUS server, make sure that the configuration information about the user exists. The user input an incorrect password Be sure to input the correct password. The switch and the RADIUS server have different shared keys Compare the shared keys at the two ends, make sure they are identical. The switch cannot communicate with the RADIUS server (you can determine by pinging the RADIUS server from the switch) Take measures to make the switch communicate with the RADIUS server normally. Symptom 2: RADIUS packets cannot be sent to the RADIUS server. Possible reasons and solutions: The communication links (physical/link layer) between the switch and the RADIUS server is disconnected/blocked Take measures to make the links connected/unblocked. None or incorrect RADIUS server IP address is set on the switch Be sure to set a correct RADIUS server IP address. One or all AAA UDP port settings are incorrect Be sure to set the same UDP port numbers as those on the RADIUS server. Symptom 3: The user passes the authentication and gets authorized, but the accounting information cannot be transmitted to the RADIUS server. Possible reasons and solutions: The accounting port number is not properly set Be sure to set a correct port number for RADIUS accounting. The switch requests that both the authentication/authorization server and the accounting server use the same device (with the same IP address), but in fact they are not resident on the same device Be sure to configure the RADIUS servers on the switch according to the actual situation.
2-31
EAD Configuration
Introduction to EAD
Endpoint Admission Defense (EAD) is an attack defense solution. Using this solution, you can enhance the active defense capability of network endpoints, prevents viruses and worms from spreading on the network, and protects the entire network by limiting the access rights of insecure endpoints. With the cooperation of switch, AAA sever, security policy server and security client, EAD is able to evaluate the security compliance of network endpoints and dynamically control their access rights. With EAD, a switch: Verifies the validity of the session control packets it receives according to the source IP addresses of the packets: It regards only those packets sourced from authentication or security policy server as valid. Dynamically adjusts the VLAN, rate and packet scheduling priority for user terminals according to session control packets, whereby to control the access rights of users dynamically.
EAD Configuration
The EAD configuration includes: Configuring the attributes of access users (such as username, user type, and password). For local authentication, you need to configure these attributes on the switch; for remote authentication, you need to configure these attributes on the AAA sever. Configuring a RADIUS scheme.
3-1
Configuring the IP address of the security policy server. Associating the ISP domain with the RADIUS scheme. EAD is commonly used in RADIUS authentication environment. This section mainly describes the configuration of security policy server IP address. For other related configuration, refer to AAA Overview. Follow these steps to configure EAD: To do Enter system view Enter RADIUS scheme view Configure the RADIUS server type to extended Configure the IP address of a security policy server Use the command system-view radius scheme radius-scheme-name server-type extended Required Required security-policy-server ip-address Each RADIUS scheme supports up to eight IP addresses of security policy servers. Remarks
3-2
Network diagram
Figure 3-2 EAD configuration
Configuration procedure
# Configure 802.1x on the switch. Refer to Configuring 802.1x in 802.1x and System Guard Configuration. # Configure a domain.
<Sysname> system-view [Sysname] domain system [Sysname-isp-system] quit
3-3
Table of Contents
1 MAC Address Authentication Configuration 1-1 MAC Address Authentication Overview 1-1 Performing MAC Address Authentication on a RADIUS Server 1-1 Performing MAC Address Authentication Locally 1-1 Related Concepts1-2 MAC Address Authentication Timers 1-2 Quiet MAC Address1-2 Configuring Basic MAC Address Authentication Functions 1-2 MAC Address Authentication Enhanced Function Configuration 1-3 MAC Address Authentication Enhanced Function Configuration Task List 1-3 Configuring a Guest VLAN 1-4 Configuring the Maximum Number of MAC Address Authentication Users Allowed to Access a Port 1-6 Displaying and Maintaining MAC Address Authentication Configuration 1-7 MAC Address Authentication Configuration Examples1-7
1-1
format
configured
with
the
mac-authentication
authmode
usernameasmacaddress
usernameformat command; otherwise, the authentication will fail. In fixed mode, all users MAC addresses are automatically mapped to the configured local passwords and usernames. The service type of a local user needs to be configured as lan-access.
Related Concepts
MAC Address Authentication Timers
The following timers function in the process of MAC address authentication: Offline detect timer: At this interval, the switch checks to see whether an online user has gone offline. Once detecting that a user becomes offline, the switch sends a stop-accounting notice to the RADIUS server. Quiet timer: Whenever a user fails MAC address authentication, the switch does not initiate any MAC address authentication of the user during a period defined by this timer. Server timeout timer: During authentication of a user, if the switch receives no response from the RADIUS server in this period, it assumes that its connection to the RADIUS server has timed out and forbids the user from accessing the network.
If the quiet MAC is the same as the static MAC configured or an authentication-passed MAC, then the quiet function is not effective.
1-2
To do...
Remarks
Set the user name in MAC address mode for MAC address authentication
mac-authentication authmode usernameasmacaddress [ usernameformat { with-hyphen | without-hyphen } { lowercase | uppercase } | fixedpassword password ] Set the user name in fixed mode for MAC address authentication Configure the user name Configure the password
Optional By default, the MAC address of a user is used as the user name.
Set the user name in fixed mode for MAC address authentication
Required mac-authentication domain isp-name The default ISP domain (default domain) is used by default. Optional The default timeout values are as follows:
300 seconds for offline detect timer; 60 seconds for quiet timer; and 100 seconds for server timeout timer
If MAC address authentication is enabled on a port, you cannot configure the maximum number of dynamic MAC address entries for that port (through the mac-address max-mac-count command), and vice versa. If MAC address authentication is enabled on a port, you cannot configure port security (through the port-security enable command) on that port, and vice versa. You can configure MAC address authentication on a port before enabling it globally. However, the configuration will not take effect unless MAC address authentication is enabled globally.
1-3
Task Configuring a Guest VLAN Configuring the Maximum Number of MAC Address Authentication Users Allowed to Access a Port
Different from Guest VLANs described in the 802.1x and System-Guard manual, Guest VLANs mentioned in this section refer to Guests VLANs dedicated to MAC address authentication.
After completing configuration tasks in Configuring Basic MAC Address Authentication Functions for a switch, this switch can authenticate access users according to their MAC addresses or according to fixed user names and passwords. The switch will not learn MAC addresses of the clients failing in the authentication into its local MAC address table, thus prevent illegal users from accessing the network. In some cases, if the clients failing in the authentication are required to access some restricted resources in the network (such as the virus library update server), you can use the Guest VLAN. You can configure a Guest VLAN for each port of the switch. When a client connected to a port fails in MAC address authentication, this port will be added into the Guest VLAN automatically. The MAC address of this client will also be learned into the MAC address table of the Guest VLAN, and thus the user can access the network resources of the Guest VLAN.
1-4
After a port is added to a Guest VLAN, the switch will re-authenticate the first access user of this port (namely, the first user whose unicast MAC address is learned by the switch) periodically. If this user passes the re-authentication, this port will exit the Guest VLAN, and thus the user can access the network normally.
Guest VLANs are implemented in the mode of adding a port to a VLAN. For example, when multiple users are connected to a port, if the first user fails in the authentication, the other users can access only the contents of the Guest VLAN. The switch will re-authenticate only the first user accessing this port, and the other users cannot be authenticated again. Thus, if more than one client is connected to a port, you cannot configure a Guest VLAN for this port. After users that are connected to an existing port failed to pass authentication, the switch adds the port to the Guest VLAN. Therefore, the Guest VLAN can separate unauthenticated users on an access port. When it comes to a trunk port or a hybrid port, if a packet itself has a VLAN tag and be in the VLAN that the port allows to pass, the packet will be forwarded perfectly without the influence of the Guest VLAN. That is, packets can be forwarded to the VLANs other than the Guest VLAN through the trunk port and the hybrid port, even users fail to pass authentication.
Follow these steps to configure a Guest VLAN: To do... Enter system view Enter Ethernet port view Configure the Guest VLAN for the current port Return to system view Configure the interval at which the switch re-authenticates users in Guest VLANs Use the command... system-view interface interface-type interface-number mac-authentication guest-vlan vlan-id quit Required By default, no Guest VLAN is configured for a port by default. Optional mac-authentication timer guest-vlan-reauth interval By default, the switch re-authenticates the users in Guest VLANs at the interval of 30 seconds by default. Remarks
1-5
If more than one client are connected to a port, you cannot configure a Guest VLAN for this port. When a Guest VLAN is configured for a port, only one MAC address authentication user can access the port. Even if you set the limit on the number of MAC address authentication users to more than one, the configuration does not take effect. The undo vlan command cannot be used to remove the VLAN configured as a Guest VLAN. If you want to remove this VLAN, you must remove the Guest VLAN configuration for it. Refer to the VLAN module in this manual for the description on the undo vlan command. Only one Guest VLAN can be configured for a port, and the VLAN configured as the Guest VLAN must be an existing VLAN. Otherwise, the Guest VLAN configuration does not take effect. If you want to change the Guest VLAN for a port, you must remove the current Guest VLAN and then configure a new Guest VLAN for this port. 802.1x authentication cannot be enabled for a port configured with a Guest VLAN. The Guest VLAN function for MAC address authentication does not take effect when port security is enabled.
Configuring the Maximum Number of MAC Address Authentication Users Allowed to Access a Port
You can configure the maximum number of MAC address authentication users for a port in order to control the maximum number of users accessing a port. After the number of access users has exceeded the configured maximum number, the switch will not trigger MAC address authentication for subsequent access users, and thus these subsequent access users cannot access the network normally. Follow these steps to configure the maximum number of MAC address authentication users allowed to access a port: To do... Enter system view Enter Ethernet port view Configure the maximum number of MAC address authentication users allowed to access a port Use the command... system-view interface interface-type interface-number mac-authentication max-auth-num user-number Required By default, the maximum number of MAC address authentication users allowed to access a port is 256. Remarks
1-6
If both the limit on the number of MAC address authentication users and the limit on the number of users configured in the port security function are configured for a port, the smaller value of the two configured limits is adopted as the maximum number of MAC address authentication users allowed to access this port. Refer to the Port Security manual for the description on the port security function. You cannot configure the maximum number of MAC address authentication users for a port if any user connected to this port is online.
Network Diagram
Figure 1-1 Network diagram for MAC address authentication configuration
Configuration Procedure
# Enable MAC address authentication on port GigabitEthernet 1/0/2.
<Sysname> system-view [Sysname] mac-authentication interface GigabitEthernet 1/0/2
1-7
# Set the user name in MAC address mode for MAC address authentication, requiring hyphened lowercase MAC addresses as the usernames and passwords.
[Sysname] mac-authentication authmode usernameasmacaddress usernameformat with-hyphen lowercase
# Enable MAC address authentication globally (This is usually the last step in configuring access control related features. Otherwise, a user may be denied of access to the networks because of incomplete configuaration.)
[Sysname] mac-authentication
After doing so, your MAC address authentication configuration will take effect immediately. Only users with the MAC address of 00-0d-88-f6-44-c1 are allowed to access the Internet through port GigabitEthernet 1/0/2.
1-8
Table of Contents
1 IP Addressing Configuration1-1 IP Addressing Overview1-1 IP Address Classes 1-1 Special IP Addresses 1-2 Subnetting and Masking 1-2 Protocols and Standards 1-3 Configuring IP Addresses 1-3 Displaying IP Addressing Configuration1-4 VLAN Interface IP Address Configuration Examples1-4 2 IP Performance Optimization Configuration2-1 IP Performance Overview 2-1 Introduction to IP Performance Configuration 2-1 Introduction to FIB 2-1 Protocols and Standards 2-1 Configuring IP Performance Optimization2-1 IP Performance Optimization Configuration Task List 2-1 Configuring TCP Attributes2-1 Disabling Sending of ICMP Error Packets2-2 Displaying and Maintaining IP Performance Optimization Configuration 2-3
IP Addressing Configuration
The term IP address used throughout this chapter refers to IPv4 address. For details about IPv6 address, refer to IPv6 Management.
When configuring IP addressing, go to these sections for information you are interested in: IP Addressing Overview Configuring IP Addresses Displaying IP Addressing Configuration VLAN Interface IP Address Configuration Examples
IP Addressing Overview
IP Address Classes
On an IP network, a 32-bit address is used to identify a host. An example is
01010000100000001000000010000000 in binary. To make IP addresses in 32-bit form easier to read, they are written in dotted decimal notation, each being four octets in length, for example, 10.1.1.1 for the address just mentioned. Each IP address breaks down into two parts: Net ID: The first several bits of the IP address defining a network, also known as class bits. Host ID: Identifies a host on a network. IP addresses are divided into five classes, as shown in the following figure (in which the blue parts represent the address class). Figure 1-1 IP address classes
1-1
Table 1-1 IP address classes and ranges Class Address range Remarks The IP address 0.0.0.0 is used by a host at bootstrap for temporary communication. This address is never a valid destination address. A 0.0.0.0 to 127.255.255.255 Addresses starting with 127 are reserved for loopback test. Packets destined to these addresses are processed locally as input packets rather than sent to the link. Multicast addresses Reserved for future use except for the broadcast address 255.255.255.255.
B C D E
Special IP Addresses
The following IP addresses are for special use, and they cannot be used as host IP addresses: IP address with an all-zero net ID: Identifies a host on the local network. For example, IP address 0.0.0.16 indicates the host with a host ID of 16 on the local network. IP address with an all-zero host ID: Identifies a network. IP address with an all-one host ID: Identifies a directed broadcast address. For example, a packet with the destination address of 192.168.1.255 will be broadcasted to all the hosts on the network 192.168.1.0.
In the absence of subnetting, some special addresses such as the addresses with the net ID of all zeros and the addresses with the host ID of all ones, are not assignable to hosts. The same is true for
1-2
subnetting. When designing your network, you should note that subnetting is somewhat a tradeoff between subnets and accommodated hosts. For example, a Class B network can accommodate 65,534 (216 2. Of the two deducted Class B addresses, one with an all-ones host ID is the broadcast address and the other with an all-zero host ID is the network address) hosts before being subnetted. After you break it down into 512 (29) subnets by using the first 9 bits of the host ID for the subnet, you have only 7 bits for the host ID and thus have only 126 (27 2) hosts in each subnet. The maximum number of hosts is thus 64,512 (512 126), 1022 less after the network is subnetted. Class A, B, and C networks, before being subnetted, use these default masks (also called natural masks): 255.0.0.0, 255.255.0.0, and 255.255.255.0 respectively.
Configuring IP Addresses
S4200G Series Ethernet Switches support assigning IP addresses to loopback interfaces and VLAN interfaces. A loopback interface is a virtual interface. The physical layer state and link layer protocols of a loopback interface are always up unless the loopback interface is manually shut down. A loopback interface can be configured with an IP address, so routing protocols can be enabled on a loopback interface, and a loopback interface is capable of sending and receiving routing protocol packets. Each VLAN needs an IP address so that it can be addressed. For more information about VLAN interfaces, refer to VLAN Operation in this manual. Besides directly assigning an IP address to a VLAN interface, you may configure a VLAN interface to obtain an IP address through BOOTP or DHCP as alternatives. If you change the way an interface obtains an IP address, from manual assignment to BOOTP for example, the IP address obtained from BOOTP will overwrite the old one manually assigned.
This chapter only covers how to assign an IP address manually. For the other two approaches, refer to the part discussing DHCP.
Follow these steps to configure an IP address for an interface: To do Enter system view Enter interface view Assign an IP address to the Interface Use the command system-view interface interface-type interface-number ip address ip-address { mask | mask-length } Required No IP address is assigned by default. Remarks
1-3
For saving IP address resources, the IP address of a Loopback interface is automatically configured with a 32-bit mask.
Network diagram
Figure 1-3 Network diagram for IP address configuration
Configuration procedure
# Configure an IP address for VLAN-interface 1.
<Switch> system-view [Switch] interface vlan-interface 1 [Switch-Vlan-interface1] ip address 129.2.2.1 255.255.255.0
1-4
IP Performance Overview
Introduction to IP Performance Configuration
In some network environments, you can adjust the IP parameters to achieve best network performance. The IP performance optimization configuration supported by S4200G Series Ethernet Switches includes: Configuring TCP attributes Disabling ICMP to send error packets
Introduction to FIB
Every switch stores a forwarding information base (FIB). FIB is used to store the forwarding information of the switch and guide Layer 3 packet forwarding. You can know the forwarding information of the switch by viewing the FIB table. Each FIB entry includes: destination address/mask length, next hop, current flag, timestamp, and outbound interface. When the switch runs normally, its FIB table and routing table have the same contents.
2-1
synwait timer: When sending a SYN packet, TCP starts the synwait timer. If no response packet is received within the synwait timer interval, the TCP connection cannot be created. finwait timer: When a TCP connection is changed into FIN_WAIT_2 state, the finwait timer is started. If no FIN packet is received within the timer timeout, the TCP connection will be terminated. If a FIN packet is received, the TCP connection state changes to TIME_WAIT. If a non-FIN packet is received, the system restarts the timer upon receiving the last non-FIN packet. The connection is broken after the timer expires. Size of TCP receive/send buffer Follow these steps to configure TCP attributes: To do Enter system view Configure the TCP synwait timer Configure the TCP finwait timer Configure the size of TCP receive/send buffer Use the command system-view tcp timer syn-timeout time-value tcp timer fin-timeout time-value tcp window window-size Optional 75 seconds by default. Optional 675 seconds by default. Optional 8 kilobytes by default. Remarks
A host may have only a default route to the default gateway in its routing table after startup. The default gateway will send an ICMP redirect packet to the source host, telling it to reselect a better next hop to send the subsequent packets, if the following conditions are satisfied: The receiving and forwarding interfaces are the same. The selected route has not been created or modified by any ICMP redirect packet. The selected route is not the default route. There is no source route option in the data packet. ICMP redirect packets simplify host administration and enables a host to gradually establish a sound routing table. 2) Sending ICMP destination unreachable packets
If a device receives an IP packet with an unreachable destination, it will drop the packet and send an ICMP destination unreachable error packet to the source. Conditions for sending an ICMP unreachable packet: If neither a route nor the default route for forwarding a packet is available, the device will send a network unreachable ICMP error packet.
2-2
If the destination of a packet is local while the transport layer protocol of the packet is not supported by the local device, the device sends a protocol unreachable ICMP error packet to the source. When receiving a packet with the destination being local and transport layer protocol being UDP, if the packets port number does not match the running process, the device will send the source a port unreachable ICMP error packet. If the source uses strict source routing" to send packets, but the intermediate device finds that the next hop specified by the source is not directly connected, the device will send the source a source routing failure ICMP error packet. When forwarding a packet, if the MTU of the sending interface is smaller than the packet but the packet has Dont Fragment set, the device will send the source a fragmentation needed and Dont Fragment (DF)-set ICMP error packet.
Use the command display fib display fib ip_address1 [ { mask1 | mask-length1 } [ ip_address2 { mask2 | mask-length2 } | longer ] | longer ] display fib acl number display fib | { begin | include | exclude } regular-expression display fib statistics reset ip statistics reset tcp statistics reset udp statistics
Remarks
Display the FIB entries permitted by a specific ACL Display the FIB entries in the buffer which begin with, include or exclude the specified character string. Display FIB statistics Clear IP traffic statistics Clear TCP traffic statistics Clear UDP traffic statistics
2-4
Table of Contents
1 ARP Configuration 1-1 Introduction to ARP 1-1 ARP Function 1-1 ARP Message Format 1-1 ARP Table 1-3 ARP Process 1-3 Introduction to Gratuitous ARP1-4 Configuring ARP 1-4 Configuring Gratuitous ARP1-5 Displaying and Debugging ARP1-5 ARP Configuration Examples 1-6
1
ARP Configuration
When configuring ARP, go to these sections for information you are interested in: Introduction to ARP Configuring ARP Configuring Gratuitous ARP Displaying and Debugging ARP ARP Configuration Examples
Introduction to ARP
ARP Function
Address Resolution Protocol (ARP) is used to resolve an IP address into a data link layer address. An IP address is the address of a host at the network layer. To send a network layer packet to a destination host, the device must know the data link layer address (MAC address, for example) of the destination host or the next hop. To this end, the IP address must be resolved into the corresponding data link layer address.
Unless otherwise stated, a data link layer address in this chapter refers to a 48-bit Ethernet MAC address.
1-1
Hardware type (16 bits) Protocol type (16 bits) Length of hardware address Length of protocol address Operator (16 bits) Hardware address of the sender IP address of the sender Hardware address of the receiver IP address of the receiver
Table 1-1 describes the fields of an ARP packet. Table 1-1 Description on the fields of an ARP packet Field Hardware Type Protocol type Length of hardware address Length of protocol address Description Type of the hardware interface. Refer to Table 1-2 for the information about the field values. Type of protocol address to be mapped. 0x0800 indicates an IP address. Hardware address length (in bytes) Protocol address length (in bytes) Indicates the type of a data packets, which can be: 1: ARP request packets Operator 2: ARP reply packets 3: RARP request packets 4: RARP reply packets Hardware address of the sender IP address of the sender Hardware address of the receiver IP address of the receiver Hardware address of the sender IP address of the sender For an ARP request packet, this field is null. For an ARP reply packet, this field carries the hardware address of the receiver. IP address of the receiver
Table 1-2 Description on the values of the hardware type field Value 1 2 3 4
1-2
Description
ARP Table
In an Ethernet, the MAC addresses of two hosts must be available for the two hosts to communicate with each other. Each host in an Ethernet maintains an ARP table, where the latest used IP address-to-MAC address mapping entries are stored. S4200G series Ethernet switches provide the display arp command to display the information about ARP mapping entries. ARP entries in an S4200G series Ethernet switch can either be static entries or dynamic entries, as described in Table 1-3. Table 1-3 ARP entries ARP entry Static ARP entry Dynamic ARP entry Generation Method Manually configured Dynamically generated Maintenance Mode Manual maintenance ARP entries of this type age with time. The aging period is set by the ARP aging timer.
ARP Process
Figure 1-2 ARP process
Suppose that Host A and Host B are on the same subnet and that Host A sends a message to Host B. The resolution process is as follows: 1) Host A looks in its ARP mapping table to see whether there is an ARP entry for Host B. If Host A finds it, Host A uses the MAC address in the entry to encapsulate the IP packet into a data link layer frame and sends the frame to Host B. 2) If Host A finds no entry for Host B, Host A buffers the packet and broadcasts an ARP request, in which the source IP address and source MAC address are respectively the IP address and MAC address of Host A and the destination IP address and MAC address are respectively the IP address of Host B and an all-zero MAC address. Because the ARP request is sent in broadcast
1-3
mode, all hosts on this subnet can receive the request, but only the requested host (namely, Host B) will process the request. 3) Host B compares its own IP address with the destination IP address in the ARP request. If they are the same, Host B saves the source IP address and source MAC address into its ARP mapping table, encapsulates its MAC address into an ARP reply, and unicasts the reply to Host A. 4) After receiving the ARP reply, Host A adds the MAC address of Host B into its ARP mapping table for subsequent packet forwarding. Meanwhile, Host A encapsulates the IP packet and sends it out. Usually ARP dynamically implements and automatically seeks mappings from IP addresses to MAC addresses, without manual intervention.
Configuring ARP
Follow these steps to configure ARP basic functions: To do Enter system view Use the command system-view arp static ip-address mac-address [ vlan-id interface-type interface-number ] arp timer aging aging-time Optional By default, the ARP mapping table is empty, and entries are created dynamically by ARP. Optional 20 minutes by default. Remarks
Configure the ARP aging timer Enable the ARP entry checking function (that is, disable the switch from learning ARP entries with multicast MAC addresses)
1-4
Static ARP entries are valid as long as the Ethernet switch operates normally. But some operations, such as removing a VLAN, or removing a port from a VLAN, will make the corresponding ARP entries invalid and therefore removed automatically. As for the arp static command, the value of the vlan-id argument must be the ID of an existing VLAN, and the port identified by the interface-type and interface-number arguments must belong to the VLAN. Currently, static ARP entries cannot be configured on the ports of an aggregation group.
The sending of gratuitous ARP packets is enabled as long as an S4200G switch operates. No command is needed for enabling this function. That is, the device sends gratuitous ARP packets whenever a VLAN interface is enabled (such as when a link is enabled or an IP address is configured for the VLAN interface) or whenever the IP address of a VLAN interface is changed.
1-5
Use the command reset arp [ dynamic | static | interface interface-type interface-number ]
Configuration procedure
<Sysname> system-view [Sysname] undo arp check enable [Sysname] arp timer aging 10 [Sysname] arp static 192.168.1.1 000f-e201-0000 1 GigabitEthernet 1/0/10
1-6
Table of Contents
1 DHCP Overview1-1 Introduction to DHCP 1-1 DHCP IP Address Assignment 1-1 IP Address Assignment Policy 1-1 Obtaining IP Addresses Dynamically 1-2 Updating IP Address Lease1-3 DHCP Packet Format1-3 Protocol Specification1-4 2 DHCP Relay Agent Configuration 2-1 Introduction to DHCP Relay Agent 2-1 Usage of DHCP Relay Agent 2-1 DHCP Relay Agent Fundamentals2-1 Option 82 Support on DHCP Relay Agent 2-2 Configuring the DHCP Relay Agent2-3 DHCP Relay Agent Configuration Task List2-3 Correlating a DHCP Server Group with a Relay Agent Interface2-4 Configuring DHCP Relay Agent Security Functions 2-5 Configuring the DHCP Relay Agent to Support Option 822-6 Displaying and Maintaining DHCP Relay Agent Configuration2-7 DHCP Relay Agent Configuration Example2-7 Troubleshooting DHCP Relay Agent Configuration2-8 3 DHCP/BOOTP Client Configuration 3-1 Introduction to DHCP Client3-1 Introduction to BOOTP Client 3-1 Configuring a DHCP/BOOTP Client3-1 Displaying DHCP/BOOTP Client Configuration3-2 DHCP/BOOTP Client Configuration Example 3-2 DHCP Client Configuration Example3-2 BOOTP Client Configuration Example 3-3
DHCP Overview
When configuring DHCP, go to these sections for information you are interested in: Introduction to DHCP DHCP IP Address Assignment DHCP Packet Format Protocol Specification
Introduction to DHCP
With networks getting larger in size and more complicated in structure, lack of available IP addresses becomes the common situation the network administrators have to face, and network configuration becomes a tough task for the network administrators. With the emerging of wireless networks and the using of laptops, the position change of hosts and frequent change of IP addresses also require new technology. Dynamic Host Configuration Protocol (DHCP) is developed to solve these issues. DHCP adopts a client/server model, where the DHCP clients send requests to DHCP servers for configuration parameters; and the DHCP servers return the corresponding configuration information such as IP addresses to implement dynamic allocation of network resources. A typical DHCP application includes one DHCP server and multiple clients (such as PCs and laptops), as shown in Figure 1-1. Figure 1-1 Typical DHCP application
1-1
Manual assignment. The administrator configures static IP-to-MAC bindings for some special clients, such as a WWW server. Then the DHCP server assigns these fixed IP addresses to the clients. Automatic assignment. The DHCP server assigns IP addresses to DHCP clients. The IP addresses will be occupied by the DHCP clients permanently. Dynamic assignment. The DHCP server assigns IP addresses to DHCP clients for predetermined period of time. In this case, a DHCP client must apply for an IP address again at the expiration of the period. This policy applies to most clients.
After the client receives the DHCP-ACK message, it will probe whether the IP address assigned by the server is in use by broadcasting a gratuitous ARP packet. If the client receives no response within specified time, the client can use this IP address. Otherwise, the client sends a DHCP-DECLINE message to the server and requests an IP address again. If there are multiple DHCP servers, IP addresses offered by other DHCP servers are assignable to other clients.
1-2
The fields are described as follows: op: Operation types of DHCP packets, 1 for request packets and 2 for response packets. htype, hlen: Hardware address type and length of the DHCP client. hops: Number of DHCP relay agents which a DHCP packet passes. For each DHCP relay agent that the DHCP request packet passes, the field value increases by 1. xid: Random number that the client selects when it initiates a request. The number is used to identify an address-requesting process. secs: Elapsed time after the DHCP client initiates a DHCP request. flags: The first bit is the broadcast response flag bit, used to identify that the DHCP response packet is a unicast (set to 0) or broadcast (set to 1). Other bits are reserved. ciaddr: IP address of a DHCP client. yiaddr: IP address that the DHCP server assigns to a client.
1-3
siaddr: IP address of the DHCP server. giaddr: IP address of the first DHCP relay agent that the DHCP client passes after it sent the request packet. chaddr: Hardware address of the DHCP client. sname: Name of the DHCP server. file: Path and name of the boot configuration file that the DHCP server specifies for the DHCP client. option: Optional variable-length fields, including packet type, valid lease time, IP address of a DNS server, and IP address of the WINS server.
Protocol Specification
Protocol specifications related to DHCP include: RFC2131: Dynamic Host Configuration Protocol RFC2132: DHCP Options and BOOTP Vendor Extensions RFC1542: Clarifications and Extensions for the Bootstrap Protocol RFC3046: DHCP Relay Agent Information option
1-4
Currently, the interface-related DHCP relay agent configurations can only be made on VLAN interfaces.
2-1
In the process of dynamic IP address assignment through the DHCP relay agent, the DHCP client and DHCP server interoperate with each other in a similar way as they do without the DHCP relay agent. The following sections only describe the forwarding process of the DHCP relay agent. For the interaction process of the packets, see section Obtaining IP Addresses Dynamically. 1) After receiving the DHCP-DISCOVER or DHCP-REQUEST broadcast from the client, the network device providing the DHCP relay agent function unicasts the message to the designated DHCP server based on the configuration. 2) The DHCP server selects an IP address and other parameters and sends the configuration information to the DHCP relay agent that relays the information to the client (the sending mode is decided by the flag filed in the clients DHCP-DISCOVER packet, refer to section DHCP Packet Format for details).
2-2
Request packets sent by a DHCP client fall into two categories: DHCP-DISCOVER packets and DHCP-REQUEST packets. As DHCP servers coming from different manufacturers process DHCP request packets in different ways (that is, some DHCP servers process Option 82 in DHCP-DISCOVER packets, whereas the rest process Option 82 in DHCP-REQUEST packets), a DHCP relay agent adds Option 82 to both types of packets to accommodate to DHCP servers of different manufacturers.
Task Correlating a DHCP Server Group with a Relay Agent Interface Configuring DHCP Relay Agent Security Functions Configuring the DHCP Relay Agent to Support Option 82
To improve security and avoid malicious attack to the unused SOCKETs, S4200G Ethernet switches provide the following functions: UDP 67 and UDP 68 ports used by DHCP are enabled only when DHCP is enabled. UDP 67 and UDP 68 ports are disabled when DHCP is disabled. The corresponding implementation is as follows: When a VLAN interface is mapped to a DHCP server group with the dhcp-server command, the DHCP relay agent is enabled. At the same time, UDP 67 and UDP 68 ports used by DHCP are enabled. When the mapping between a VLAN interface and a DHCP server group is removed with the undo dhcp-server command, DHCP services are disabled. At the same time, UDP 67 and UDP 68 ports are disabled.
2-4
You can configure up to eight DHCP server IP addresses in a DHCP server group. You can map multiple VLAN interfaces to one DHCP server group. But one VLAN interface can be mapped to only one DHCP server group. If you execute the dhcp-server groupNo command repeatedly, the new configuration overwrites the previous one. You need to configure the group number specified in the dhcp-server groupNo command in VLAN interface view by using the command dhcp-server groupNo ip ip-address&<1-8> in advance.
2-5
The address-check enable command is independent of other commands of the DHCP relay agent. That is, the invalid address check takes effect when this command is executed, regardless of whether other commands (such as the command to enable DHCP) are used. Before executing the address-check enable command on the interface connected to the DHCP server, you need to configure the static binding of the IP address to the MAC address of the DHCP server. Otherwise, the DHCP client will fail to obtain an IP address.
With the unauthorized DHCP server detection enabled, the relay agent will log all DHCP servers, including authorized ones, and each server is recorded only once until such information is removed and is recorded again. The administrator needs to find unauthorized DHCP servers from the system log information.
To do Enter system view Enable Option 82 support on the DHCP relay agent Configure the strategy for the DHCP relay agent to process request packets containing Option 82
Use the command system-view dhcp relay information enable dhcp relay information strategy { drop | keep | replace } Required
Remarks
By default, with the Option 82 support function enabled on the DHCP relay agent, the DHCP relay agent will adopt the replace strategy to process the request packets containing Option 82. However, if other strategies are configured before, then enabling the 82 support on the DHCP relay agent will not change the configured strategies. To enable Option 82, you need to perform the corresponding configuration on the DHCP server and the DHCP relay agent.
2-7
Network diagram
Figure 2-4 Network diagram for DHCP relay agent
DHCP client DHCP client
Vlan-int1 10.10.1.1/24
DHCP client
DHCP client
Configuration procedure
# Create DHCP server group 1 and configure an IP address of 10.1.1.1 for it.
<SwitchA> system-view [SwitchA] dhcp-server 1 ip 10.1.1.1
You need to perform corresponding configurations on the DHCP server to enable the DHCP clients to obtain IP addresses from the DHCP server. The DHCP server configurations vary with different DHCP server devices, so the configurations are omitted. The DHCP relay agent and DHCP server must be reachable to each other.
Analysis
This problem may be caused by improper DHCP relay agent configuration. When a DHCP relay agent operates improperly, you can locate the problem by enabling debugging and checking the information about debugging and interface state (You can display the information by executing the corresponding display command.)
Solution
Check if DHCP is enabled on the DHCP server and the DHCP relay agent.
2-8
Check if an address pool that is on the same network segment with the DHCP clients is configured on the DHCP server. Check if a reachable route is configured between the DHCP relay agent and the DHCP server. Check the DHCP relay agent. Check if the correct DHCP server group is configured on the interface connecting the network segment where the DHCP client resides. Check if the IP address of the DHCP server group is correct. If the address-check enable command is configured on the interface connected to the DHCP server, verify the DHCP servers IP-to-MAC address binding entry is configured on the DHCP relay agent; otherwise the DHCP client cannot obtain an IP address.
2-9
Because a DHCP server can interact with a BOOTP client, you can use the DHCP server to assign an IP address to the BOOTP client, without needing to configure any BOOTP server.
3-1
To do Enter system view Enter VLAN interface view Configure the VLAN interface to obtain IP address through DHCP or BOOTP
Use the command system-view interface vlan-interface vlan-id ip address { bootp-alloc | dhcp-alloc } Required
Remarks
Currently, an S4200G Ethernet switch functioning as the DHCP client can use an IP address for 24 days at most. That is, the DHCP client can obtain an address lease for no more than 24 days even though the DHCP server offers a longer lease period.
To improve security and avoid malicious attack to the unused SOCKETs, S4200G Ethernet switches provide the following functions: UDP 67 and UDP 68 ports used by DHCP are enabled only when DHCP is enabled. UDP 67 and UDP 68 ports are disabled when DHCP is disabled. The specific implementation is: Using the ip address dhcp-alloc command enables the DHCP client, and UDP port 68. Using the undo ip address dhcp-alloc command disables the DHCP client, and UDP port 68.
3-2
Network diagram
Figure 3-1 A DHCP network
Client WINS server
DHCP server
Vlan-int1
DNS server
Switch A Client
Configuration procedure
The following describes only the configuration on Switch A serving as a DHCP client. # Configure VLAN-interface 1 to dynamically obtain an IP address by using DHCP.
<SwitchA> system-view [SwitchA] interface Vlan-interface 1 [SwitchA-Vlan-interface1] ip address dhcp-alloc
Network diagram
See Figure 3-1.
Configuration procedure
The following describes only the configuration on Switch A serving as a client. # Configure VLAN-interface 1 to dynamically obtain an IP address from the DHCP server.
<SwitchA> system-view [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] ip address bootp-alloc
3-3
Table of Contents
1 DNS Configuration1-1 DNS Overview1-1 Static Domain Name Resolution 1-1 Dynamic Domain Name Resolution 1-1 Configuring Domain Name Resolution1-2 Configuring Static Domain Name Resolution 1-2 Configuring Dynamic Domain Name Resolution1-3 Displaying and Maintaining DNS 1-3 DNS Configuration Examples 1-4 Static Domain Name Resolution Configuration Example1-4 Dynamic Domain Name Resolution Configuration Example1-5 Troubleshooting DNS1-6
DNS Configuration
When configuring DNS, go to these sections for information you are interested in: DNS Overview Configuring Domain Name Resolution Displaying and Maintaining DNS DNS Configuration Examples Troubleshooting DNS
This chapter covers only IPv4 DNS configuration. For details about IPv6 DNS, refer to IPv6 Management Operation.
DNS Overview
Domain Name System (DNS) is a mechanism used for TCP/IP applications to provide domain name-to-IP address translation. With DNS, you can use memorizable and meaningful domain names in some applications and let the DNS server resolve it into correct IP addresses. There are two types of DNS services, static and dynamic. Each time the DNS server receives a name query, it checks its static DNS database before looking up the dynamic DNS database. Reduction of the searching time in the dynamic DNS database would increase efficiency. Some frequently used addresses can be put in the static DNS database. Currently, S4200G series Ethernet switches support both static and dynamic DNS clients.
1-1
2)
The DNS resolver looks up the local domain name cache for a match. If a match is found, it sends the corresponding IP address back. If not, it sends the query to the DNS server.
3)
The DNS server looks up its DNS database for a match. If no match is found, it sends a query to a higher-level DNS server. This process continues until a result, success or failure, is returned.
4)
The DNS client performs the next operation according to the result.
Figure 1-1 shows the relationship between user program, DNS client, and DNS server. The resolver and cache comprise the DNS client. The user program and DNS client run on the same device, while the DNS server and the DNS client usually run on different devices. Dynamic domain name resolution allows the DNS client to store latest mappings between name and IP address in the dynamic domain name cache of the DNS client. There is no need to send a request to the DNS server for a repeated query request next time. The aged mappings are removed from the cache after some time, and latest entries are required from the DNS server. The DNS server decides how long a mapping is valid, and the DNS client gets the information from DNS messages.
DNS suffixes
The DNS client normally holds a list of suffixes which can be defined by users. It is used when the name to be resolved is not complete. The resolver can supply the missing part (automatic domain name addition). For example, a user can configure com as the suffix for aabbcc.com. The user only needs to type aabbcc to get the IP address of aabbcc.com. The resolver can add the suffix and delimiter before passing the name to the DNS server. If there is no dot in the domain name, such as aabbcc, the resolver will consider this as a host name and add a DNS suffix before processing. The original name such as aabbcc is used if all DNS lookups fail. If there is a dot in the domain name, such as www.aabbcc and aabbcc., the resolver will directly use this domain name to do DNS lookup first. If the lookup fails, the resolver adds a DNS suffix for another lookup.
To do Enter system view Configure a mapping between a host name and an IP address
Remarks
The IP address you assign to a host name last time will overwrite the previous one if there is any. You may create up to 50 static mappings between domain names and IP addresses.
You may configure up to six DNS servers and ten DNS suffixes.
1-3
To do Display the DNS resolution result Clear the information in the dynamic domain name cache
Use the command nslookup type { ptr ip-address | a domain-name } reset dns dynamic-host
Remarks
Network diagram
Figure 1-2 Network diagram for static DNS configuration
Configuration procedure
# Configure a mapping between host name host.com and IP address 10.1.1.2.
<Sysname> system-view [Sysname] ip host host.com 10.1.1.2
# Execute the ping host.com command to verify that the device can use static domain name resolution to get the IP address 10.1.1.2 corresponding to host.com.
[Sysname] ping host.com PING host.com (10.1.1.2): 56 data bytes, press CTRL_C to break
Reply from 10.1.1.2: bytes=56 Sequence=1 ttl=127 time=3 ms Reply from 10.1.1.2: bytes=56 Sequence=2 ttl=127 time=3 ms Reply from 10.1.1.2: bytes=56 Sequence=3 ttl=127 time=2 ms Reply from 10.1.1.2: bytes=56 Sequence=4 ttl=127 time=5 ms Reply from 10.1.1.2: bytes=56 Sequence=5 ttl=127 time=3 ms
--- host.com ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 2/3/5 ms
1-4
Network diagram
Figure 1-3 Network diagram for dynamic DNS configuration
Configuration procedure
Before doing the following configuration, make sure that: The routes between the DNS server, Switch, and Host are reachable. Necessary configurations are done on the devices. For the IP addresses of the interfaces, see the figure above. There is a mapping between domain name host and IP address 3.1.1.1/16 on the DNS server. The DNS server works normally.
Execute the ping host command on Switch to verify that the communication between Switch and Host is normal and that the corresponding IP address is 3.1.1.1.
[Sysname] ping host Trying DNS server (2.1.1.2) PING host.com (3.1.1.1): 56 data bytes, press CTRL_C to break
1-5
Reply from 3.1.1.1: bytes=56 Sequence=1 ttl=125 time=4 ms Reply from 3.1.1.1: bytes=56 Sequence=2 ttl=125 time=4 ms Reply from 3.1.1.1: bytes=56 Sequence=3 ttl=125 time=4 ms Reply from 3.1.1.1: bytes=56 Sequence=4 ttl=125 time=4 ms Reply from 3.1.1.1: bytes=56 Sequence=5 ttl=125 time=5 ms
--- host.com ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 4/4/5 ms
Troubleshooting DNS
Symptom
After enabling the dynamic domain name resolution, the user cannot get the correct IP address.
Solution
Use the display dns dynamic-host command to check that the specified domain name is in the cache. If there is no defined domain name, check that dynamic domain name resolution is enabled and the DNS client can communicate with the DNS server. If the specified domain name exists in the cache but the IP address is incorrect, check that the DNS client has the correct IP address of the DNS server. Check that the mapping between the domain name and IP address is correct on the DNS server.
1-6
Table of Contents
1 ACL Configuration1-1 ACL Overview 1-1 ACL Matching Order1-1 Ways to Apply an ACL on a Switch1-2 Types of ACLs Supported by Switch 4200G Series1-3 ACL Configuration1-3 Configuring Time Range1-3 Configuring Basic ACL 1-4 Configuring Advanced ACL 1-5 Configuring Layer 2 ACL 1-7 ACL Assignment 1-8 Assigning an ACL Globally1-9 Assigning an ACL to a VLAN 1-9 Assigning an ACL to a Port Group 1-10 Assigning an ACL to a Port 1-10 Displaying ACL Configuration 1-11 Example for Upper-layer Software Referencing ACLs 1-12 Example for Controlling Telnet Login Users by Source IP 1-12 Example for Controlling Web Login Users by Source IP1-12 Example for Applying ACLs to Hardware1-13 Basic ACL Configuration Example 1-13 Advanced ACL Configuration Example 1-14 Layer 2 ACL Configuration Example 1-14 Example for Applying an ACL to a VLAN 1-15
ACL Configuration
ACL Overview
As the network scale and network traffic are increasingly growing, security control and bandwidth assignment play a more and more important role in network management. Filtering data packets can prevent a network from being accessed by unauthorized users efficiently while controlling network traffic and saving network resources. Access control lists (ACL) are often used to filter packets with configured matching rules. Upon receiving a packet, the switch compares the packet with the rules of the ACL applied on the current port to permit or discard the packet. The rules of an ACL can be referenced by other functions that need traffic classification, such as QoS. ACLs classify packets using a series of conditions known as rules. The conditions can be based on source addresses, destination addresses and port numbers carried in the packets. According to their application purposes, ACLs fall into the following four types. Basic ACL. Rules are created based on source IP addresses only. Advanced ACL. Rules are created based on the Layer 3 and Layer 4 information such as the source and destination IP addresses, type of the protocols carried by IP, protocol-specific features, and so on. Layer 2 ACL. Rules are created based on the Layer 2 information such as source and destination MAC addresses, VLAN priorities, type of Layer 2 protocol, and so on. User-defined ACL. An ACL of this type matches packets by comparing the strings retrieved from the packets with specified strings. It defines the byte it begins to perform and operation with the mask on the basis of packet headers.
1-1
If rule A and rule B are still the same after comparison in the above order, the weighting principles will be used in deciding their priority order. Each parameter is given a fixed weighting value. This weighting value and the value of the parameter itself will jointly decide the final matching order. Involved parameters with weighting values from high to low are icmp-type, established, dscp, tos, precedence, fragment. Comparison rules are listed below. The smaller the weighting value left, which is a fixed weighting value minus the weighting value of every parameter of the rule, the higher the match priority. If the types of parameter are the same for multiple rules, then the sum of parameters weighting values of a rule determines its priority. The smaller the sum, the higher the match priority.
1-2
When an ACL is directly applied to hardware for packet filtering, the switch will permit packets if the packets do not match the ACL. When an ACL is referenced by upper-layer software to control Telnet, SNMP and Web login users, the switch will deny packets if the packets do not match the ACL.
ACL Configuration
Configuring Time Range
Time ranges can be used to filter packets. You can specify a time range for each rule in an ACL. A time range-based ACL takes effect only in specified time ranges. Only after a time range is configured and the system time is within the time range, can an ACL rule take effect. Two types of time ranges are available: Periodic time range, which recurs periodically on the day or days of the week. Absolute time range, which takes effect only in a period of time and does not recur.
An absolute time range on a Switch 4200G can be within the range 1970/1/1 00:00 to 2100/12/31 24:00.
Configuration Procedure
Table 1-1 Configure a time range Operation Enter system view system-view time-range time-name { start-time to end-time days-of-the-week [ from start-time start-date ] [ to end-time end-date ] | from start-time start-date [ to end-time end-date ] | to end-time end-date } Command Description
Required
Note that:
1-3
If only a periodic time section is defined in a time range, the time range is active only when the system time is within the defined periodic time section. If multiple periodic time sections are defined in a time range, the time range is active only when the system time is within one of the periodic time sections. If only an absolute time section is defined in a time range, the time range is active only when the system time is within the defined absolute time section. If multiple absolute time sections are defined in a time range, the time range is active only when the system time is within one of the absolute time sections. If both a periodic time section and an absolute time section are defined in a time range, the time range is active only when the periodic time range and the absolute time range are both matched. Assume that a time range contains an absolute time section ranging from 00:00 January 1, 2004 to 23:59 December 31, 2004, and a periodic time section ranging from 12:00 to 14:00 on every Wednesday. This time range is active only when the system time is within the range from 12:00 to 14:00 on every Wednesday in 2004. If the start time is not specified, the time section starts from 1970/1/1 00:00 and ends on the specified end date. If the end date is not specified, the time section starts from the specified start date to 2100/12/31 23:59.
Configuration Example
# Define a periodic time range that spans from 8:00 to 18:00 on Monday through Friday.
<Sysname> system-view [Sysname] time-range test 8:00 to 18:00 working-day [Sysname] display time-range test Current time is 13:27:32 Apr/16/2005 Saturday
# Define an absolute time range spans from 15:00 1/28/2006 to 15:00 1/28/2008.
<Sysname> system-view [Sysname] time-range test from 15:00 1/28/2006 to 15:00 1/28/2008 [Sysname] display time-range test Current time is 13:30:32 Apr/16/2005 Saturday
Configuration Prerequisites
To configure a time range-based basic ACL rule, you need to create the corresponding time range first. For information about time range configuration, refer to section Configuring Time Range. The source IP addresses based on which the ACL filters packets are determined.
1-4
Configuration Procedure
Table 1-2 Define a basic ACL rule Operation Enter system view Create an ACL and enter basic ACL view system-view acl number acl-number [ match-order { auto | config } ] Command Required config by default Required Define an ACL rule rule [ rule-id ] { deny | permit } [ rule-string ] For information about rule-string, refer to ACL Command. Optional Not configured by default Description
description text
Note that: With the config match order specified for the basic ACL, you can modify any existent rule. The unmodified part of the rule remains. With the auto match order specified for the basic ACL, you cannot modify any existent rule; otherwise the system prompts error information. If you do not specify the rule-id argument when creating an ACL rule, the rule will be numbered automatically. If the ACL has no rules, the rule is numbered 0; otherwise, the number of the rule will be the greatest rule number plus one. If the current greatest rule number is 65534, however, the system will display an error message and you need to specify a number for the rule. The content of a modified or created rule cannot be identical with the content of any existing rule; otherwise the rule modification or creation will fail, and the system prompts that the rule already exists. With the auto match order specified, the newly created rules will be inserted in the existent ones by depth-first principle, but the numbers of the existent rules are unaltered.
Configuration Example
# Configure ACL 2000 to deny packets whose source IP addresses are 192.168.0.1.
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule deny source 192.168.0.1 0
Advanced ACLs support analysis and processing of three packet priority levels: type of service (ToS) priority, IP priority and differentiated services codepoint (DSCP) priority. Using advanced ACLs, you can define classification rules that are more accurate, more abundant, and more flexible than those defined for basic ACLs.
Configuration Prerequisites
To configure a time range-based advanced ACL rule, you need to create the corresponding time ranges first. For information about of time range configuration, refer to section Configuring Time Range. The settings to be specified in the rule, such as source and destination IP addresses, the protocols carried by IP, and protocol-specific features, are determined.
Configuration Procedure
Table 1-3 Define an advanced ACL rule Operation Enter system view Create an advanced ACL and enter advanced ACL view Define an ACL rule Command system-view acl number acl-number [ match-order { auto | config } ] rule [ rule-id ] { permit | deny } protocol [ rule-string ] Required config by default Required For information about protocol and rule-string, refer to ACL Commands. Optional No description by default Optional No description by default Description
Assign a description string to the ACL rule Assign a description string to the ACL
description text
Note that: With the config match order specified for the advanced ACL, you can modify any existent rule. The unmodified part of the rule remains. With the auto match order specified for the ACL, you cannot modify any existent rule; otherwise the system prompts error information. If you do not specify the rule-id argument when creating an ACL rule, the rule will be numbered automatically. If the ACL has no rules, the rule is numbered 0; otherwise, the number of the rule will be the greatest rule number plus one. If the current greatest rule number is 65534, however, the system will display an error message and you need to specify a number for the rule. The content of a modified or created rule cannot be identical with the content of any existing rules; otherwise the rule modification or creation will fail, and the system prompts that the rule already exists. If the ACL is created with the auto keyword specified, the newly created rules will be inserted in the existent ones by depth-first principle, but the numbers of the existent rules are unaltered.
Configuration Example
# Configure ACL 3000 to permit the TCP packets sourced from the network 129.9.0.0/16 and destined for the network 202.38.160.0/24 and with the destination port number being 80.
<Sysname> system-view
1-6
[Sysname] acl number 3000 [Sysname-acl-adv-3000] rule permit tcp source 129.9.0.0 0.0.255.255 destination 202.38.160.0 0.0.0.255 destination-port eq 80
Acl's step is 1 rule 0 permit tcp source 129.9.0.0 0.0.255.255 destination 202.38.160.0 0.0.0.255
destination-port eq www
Configuration Prerequisites
To configure a time range-based Layer 2 ACL rule, you need to create the corresponding time ranges first. For information about time range configuration, refer to section Configuring Time Range The settings to be specified in the rule, such as source and destination MAC addresses, VLAN priorities, and Layer 2 protocol types, are determined.
Configuration Procedure
Table 1-4 Define a Layer 2 ACL rule Operation Enter system view Create a Layer 2 ACL and enter layer 2 ACL view Define an ACL rule Command system-view acl number acl-number Required Required For information about rule-string, refer to ACL Commands. Optional No description by default Optional No description by default Description
Assign a description string to the ACL rule Assign a description string to the ACL
description text
Note that: You can modify any existent rule of the Layer2 ACL and the unmodified part of the ACL remains. If you do not specify the rule-id argument when creating an ACL rule, the rule will be numbered automatically. If the ACL has no rules, the rule is numbered 0; otherwise, the number of the rule will be the greatest rule number plus one. If the current greatest rule number is 65534, however, the system will display an error message and you need to specify a number for the rule.
1-7
The content of a modified or created rule cannot be identical with the content of any existing rules; otherwise the rule modification or creation will fail, and the system prompts that the rule already exists.
Configuration Example
# Configure ACL 4000 to deny packets sourced from the MAC address 000d-88f5-97ed, destined for the MAC address 0011-4301-991e, and with their 802.1p priority being 3.
<Sysname> system-view [Sysname] acl number 4000 [Sysname-acl-ethernetframe-4000] rule deny cos 3 source 000d-88f5-97ed ffff-ffff-ffff dest 0011-4301-991e ffff-ffff-ffff
ACL Assignment
On a Switch 4200G, you can assign ACLs to the hardware for packet filtering. As for ACL assignment, the following four ways are available. Assigning ACLs globally, for filtering the inbound packets on all the ports. Assigning ACLs to a VLAN, for filtering the inbound packets on all the ports and belonging to a VLAN. Assigning ACLs to a port group, for filtering the inbound packets on all the ports in a port group. For information about port group, refer to Port Basic Configuration. Assigning ACLs to a port, for filtering the inbound packets on a port. You can assign ACLs in the above-mentioned ways as required.
ACLs assigned globally take precedence over those that are assigned to VLANs. That is, when a packet matches a rule of a globally assigned ACL and a rule of an ACL assigned to a VLAN, the device will perform the action defined in the rule of the globally assigned ACL if the actions defined in the two rules conflict. When a packet matches a rule of an ACL assigned globally (or assigned to a VLAN) and a rule of an ACL assigned to a port (or port group), the device will deny the packets if the actions defined in the two rules conflict. ACLs assigned globally or to a VLAN take precedence over the default ACL. However, assigning ACLs globally or to a VLAN may affect device management that is implemented through Telnet and so on.
1-8
Configure procedure
Table 1-5 Assign an ACL globally Operation Enter system view Assign an ACL globally Command system-view packet-filter inbound acl-rule Required For description on the acl-rule argument, refer to ACL Command. Description
Configuration example
# Apply ACL 2000 globally to filter the inbound packets on all the ports.
<Sysname> system-view [Sysname] packet-filter inbound ip-group 2000
Configuration procedure
Table 1-6 Assign an ACL to a VLAN Operation Enter system view Apply an ACL to a VLAN Command system-view packet-filter vlan vlan-id inbound acl-rule Required For description on the acl-rule argument, refer to ACL Command. Description
An ACL assigned to a VLAN takes effect only for the packets tagged with 802.1Q header. For more information about 802.1Q header, refer to the VLAN part.
1-9
Configuration example
# Apply ACL 2000 to VLAN 10 to filter the inbound packets of VLAN 10 on all the ports.
<Sysname> system-view [Sysname] packet-filter vlan 10 inbound ip-group 2000
Configuration procedure
Table 1-7 Assign an ACL to a port group Operation Enter system view Enter port group view Apply an ACL to the port group Command system-view port-group group-id Required packet-filter inbound acl-rule For description on the acl-rule argument, refer to ACL Command. Description
After an ACL is assigned to a port group, it will be automatically assigned to the ports that are subsequently added to the port group.
Configuration example
# Apply ACL 2000 to port group 1 to filter the inbound packets on all the ports in the port group.
<Sysname> system-view [Sysname] port-group 1 [Sysname-port-group-1] packet-filter inbound ip-group 2000
1-10
Configuration procedure
Table 1-8 Apply an ACL to a port Operation Enter system view Enter Ethernet port view Command system-view interface interface-type interface-number Required Apply an ACL to the port packet-filter inbound acl-rule For description on the acl-rule argument, refer to ACL Command. Description
Configuration example
# Apply ACL 2000 to GigabitEthernet 1/0/1 to filter the inbound packets.
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] packet-filter inbound ip-group 2000
1-11
Network diagram
Figure 1-1 Network diagram for controlling Telnet login users by source IP
Internet
Switch
PC
10.110.100.52
Configuration procedure
# Define ACL 2000.
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule 1 permit source 10.110.100.52 0 [Sysname-acl-basic-2000] quit
# Reference ACL 2000 on VTY user interface to control Telnet login users.
[Sysname] user-interface vty 0 4 [Sysname-ui-vty0-4] acl 2000 inbound
Network diagram
Figure 1-2 Network diagram for controlling Web login users by source IP
Internet
Switch
PC
10.110.100.46
1-12
Configuration procedure
# Define ACL 2001.
<Sysname> system-view [Sysname] acl number 2001 [Sysname-acl-basic-2001] rule 1 permit source 10.110.100.46 0 [Sysname-acl-basic-2001] quit
Network diagram
Figure 1-3 Network diagram for basic ACL configuration
Configuration procedure
# Define a periodic time range that is active from 8:00 to 18:00 everyday.
<Sysname> system-view [Sysname] time-range test 8:00 to 18:00 daily
# Define ACL 2000 to filter packets with the source IP address of 10.1.1.1.
[Sysname] acl number 2000 [Sysname-acl-basic-2000] rule 1 deny source 10.1.1.1 0 time-range test [Sysname-acl-basic-2000] quit
1-13
Network diagram
Figure 1-4 Network diagram for advanced ACL configuration
Configuration procedure
# Define a periodic time range that is active from 8:00 to 18:00 everyday.
<Sysname> system-view [Sysname] time-range test 8:00 to 18:00 working-day
# Define ACL 3000 to filter packets destined for wage query server.
[Sysname] acl number 3000 [Sysname-acl-adv-3000] rule 1 deny ip destination 192.168.1.2 0 time-range test [Sysname-acl-adv-3000] quit
1-14
Network diagram
Figure 1-5 Network diagram for Layer 2 ACL
Configuration procedure
# Define a periodic time range that is active from 8:00 to 18:00 everyday.
<Sysname> system-view [Sysname] time-range test 8:00 to 18:00 daily
# Define ACL 4000 to filter packets with the source MAC address of 0011-0011-0011 and the destination MAC address of 0011-0011-0012.
[Sysname] acl number 4000 [Sysname-acl-ethernetframe-4000] rule 1 deny source 0011-0011-0011 ffff-ffff-ffff dest 0011-0011-0012 ffff-ffff-ffff time-range test [Sysname-acl-ethernetframe-4000] quit
1-15
Network diagram
Figure 1-6 Network diagram for applying an ACL to a VLAN
Database server
192.168.1.2
GE1/0/1
GE1/0/3
GE1/0/2
VLAN 10
PC 1
PC 2
PC 3
Configuration procedure
# Define a periodic time range that is active from 8:00 to 18:00 in working days.
<Sysname> system-view [Sysname] time-range test 8:00 to 18:00 working-day
1-16
Table of Contents
1 QoS Configuration1-1 Overview 1-1 Introduction to QoS1-1 Traditional Packet Forwarding Services1-1 New Requirements from Emerging Applications1-1 Major Traffic Control Technologies 1-2 QoS Features Supported by the Switch 4200G series 1-2 Introduction to QoS Features1-3 Traffic Classification 1-3 Priority Trust Mode 1-4 Protocol Priority 1-8 Traffic Policing and Traffic Shaping1-8 Queue Scheduling 1-10 Flow-Based Traffic Accounting1-12 Burst 1-12 QoS Configuration1-13 QoS Configuration Task List 1-13 Configuring Priority Trust Mode1-13 Configuring Priority Mapping 1-14 Setting the Priority of Protocol Packets 1-17 Configuring Traffic Policing 1-18 Configuring Traffic Shaping1-20 Configuring Queue Scheduling 1-20 Configuring Traffic Accounting 1-22 Enabling the Burst Function 1-24 Displaying and Maintaining QoS 1-24 QoS Configuration Examples1-25 Traffic Policing Configuration Example 1-25
QoS Configuration
When configuring QoS, go to these sections for information you are interested in: Overview QoS Features Supported by the Switch 4200G series Introduction to QoS Features QoS Configuration QoS Configuration Examples
Overview
Introduction to QoS
Quality of Service (QoS) is a concept concerning service demand and supply. It reflects the ability to meet customer needs. Generally, QoS focuses on improving services under certain conditions rather than grading services precisely. In an internet, QoS evaluates the ability of the network to forward packets of different services. The evaluation can be based on different criteria because the network may provide various services. Generally, QoS refers to the ability to provide improved service by solving the core issues such as delay, jitter, and packet loss ratio in the packet forwarding process.
1-1
and jitter. As for mission-critical applications, such as transactions and Telnet, they may not require high bandwidth but do require low delay and preferential service during congestion. The emerging applications demand higher service performance of IP networks. Better network services during packets forwarding are required, such as providing dedicated bandwidth, reducing packet loss ratio, managing and avoiding congestion, regulating network traffic, and setting the precedence of packets. To meet these requirements, networks must provide more improved services.
As shown in Figure 1-1, traffic classification, traffic policing, traffic shaping, congestion management, and congestion avoidance form the foundation for differentiated service provisioning. They deal with different issues of QoS: Traffic classification identifies traffic based on certain match criteria. It is the foundation for providing differentiated services and is usually applied in the inbound direction of a port. Traffic policing confines traffic to a specific specification and is usually applied in the inbound direction of a port. You can configure restriction or penalty measures against the exceeding traffic to protect carrier benefits and network resources. Traffic shaping adapts output traffic rate, usually to the input capability of the receiving device, to avoid packet drop and port congestion. Traffic shaping is usually applied in the outbound direction of a port. Congestion management handles resource competition during network congestion. Generally, it assigns packets to queues first, and then forwards the packets by using a scheduling algorithm. Congestion management is usually applied in the outbound direction of a port. Congestion avoidance monitors the use of network resources and drops packets actively when congestion reaches a certain degree. It relieves network load by adjusting traffic size. Congestion avoidance is usually applied in the outbound direction of a port. Among these QoS technologies, traffic classification is the foundation for providing differentiated services by classifying packets with certain match criteria. Traffic policing, traffic shaping, congestion management, and congestion avoidance manage network traffic and resources in different ways to realize differentiated services.
1-2
Table 1-1 QoS features supported by the Switch 4200G series QoS Feature Description Classify incoming traffic based on ACLs. The Switch 4200G series support the following types of ACLs: Basic ACLs Advanced ACLs Layer 2 ACLs Reference For information about ACLs, refer to the ACL Operation and ACL Command manuals. For information about traffic classification, refer to Traffic Classification. For information about traffic policing, refer to Traffic Policing and Traffic Shaping. For information about traffic shaping, refer to Traffic Policing and Traffic Shaping. For information about traffic accounting, refer to Flow-Based Traffic Accounting. For information about priority trust mode, refer to Priority Trust Mode. For information about specifying priority for protocol packets, refer to Protocol Priority. For information about the burst function, refer to Burst.
Traffic classification
The Switch 4200G series support performing the following QoS actions on traffic matching the specified ACL: Traffic policing Traffic shaping Traffic accounting QoS actions
You can configure the following QoS actions for traffic separately as required on the Switch 4200G series: Priority trust mode Protocol packet priority Burst
Congestion management
The Switch 4200G series support SP, WRR, and SDWRR for queuing and support the following three queue scheduling modes: SP SDWRR SP+SDWRR
For information about SP, WRR, and SDWRR, refer to Queue Scheduling.
As shown in Figure 1-2, the ToS field of the IP header contains eight bits: the first three bits (0 to 2) represent IP precedence from 0 to 7 and the subsequent four bits (3 to 6) represent a ToS value from 0 to 15. According to RFC 2474, the ToS field of the IP header is redefined as the DS field, where a DiffServ code point (DSCP) precedence is represented by the first six bits (0 to 5) and is in the range 0 to 63. The remaining two bits (6 and 7) are reserved. Table 1-2 Description on IP precedence IP precedence value (decimal) 0 1 2 3 4 5 6 7 IP precedence value (binary) 000 001 010 011 100 101 110 111 Routine priority immediate flash flash-override critical internet network Description
In a Diff-Serv network, traffic is grouped into the following four classes, and packets are processed according to their DSCP values. Expedited Forwarding (EF) class: In this class, packets are forwarded regardless of link share of other traffic. The class is suitable for preferential services with low delay, low packet loss ratio, low jitter, and assured bandwidth (such as the virtual leased line service). Assured Forwarding (AF) class: This class is divided into four subclasses (AF1 to AF4), each containing three drop priorities for more granular classification. The QoS level of the AF class is lower than that of the EF class. Class Selector (CS) class: This class is derived from the IP ToS field and includes eight subclasses.
1-4
Best Effort (BE) class: This class is a special CS class that does not provide any assurance. AF traffic exceeding the limit is degraded to the BE class. Currently, all IP network traffic belongs to this class by default. Table 1-3 Description on DSCP values DSCP value (decimal) 46 10 12 14 18 20 22 26 28 30 34 36 38 8 16 24 32 40 48 56 0 DSCP value (binary) 101110 001010 001100 001110 010010 010100 010110 011010 011100 011110 100010 100100 100110 001000 010000 011000 100000 101000 110000 111000 000000 ef af11 af12 af13 af21 af22 af23 af31 af32 af33 af41 af42 af43 cs1 cs2 cs3 cs4 cs5 cs6 cs7 be (default) Description
2)
802.1p precedence
802.1p precedence lies in Layer 2 packet headers and is applicable to occasions where Layer 3 packet analysis is not needed and QoS must be assured at Layer 2. Figure 1-3 An Ethernet frame with an 802.1q tag header
As shown in Figure 1-3, each host supporting the 802.1q protocol adds a 4-byte 802.1q tag header after the source address field of the former Ethernet frame header when sending packets.
1-5
The 4-byte 802.1q tag header consists of a two-byte tag protocol identifier (TPID) field, whose value is 0x8100, and a two-byte tag control information (TCI) field. Figure 1-4 presents the format of the 802.1q tag header. Figure 1-4 802.1q tag header
Byte 1 Byte 2 Byte 3 Byte 4
1 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 Priority
VLAN ID
7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0
In Figure 1-4, the three-bit priority field in TCI is 802.1p precedence (also known as CoS precedence), which ranges from 0 to 7. Table 1-4 Description on 802.1p precedence 802.1p precedence value (decimal) 0 1 2 3 4 5 6 7 802.1p precedence value (binary) 000 001 010 011 100 101 110 111 Description best-effort background spare excellent-effort controlled-load video voice network-management
The precedence in the 802.1q tag header is called 802.1p precedence because its use is defined in IEEE 802.1p. 3) Local precedence
Local precedence is a locally significant precedence that the switch assigns to a packet. A local precedence value corresponds to one hardware output queue on the egress port. Packets with the highest local precedence are processed preferentially. As local precedence is used only for internal queuing, a packet does not carry it after leaving the queue. 4) Drop precedence
Drop precedence is used for making packet drop decisions. Packets with the highest drop precedence are dropped preferentially.
1-6
When a packet carrying no 802.1q tag reaches a port, the switch uses the port priority as the 802.1p precedence value of the received packet, searches for the set of precedence values corresponding to the port priority of the receiving port in the 802.1p-precedence-to-other-precedence mapping table, and assigns the set of matching precedence values to the packet. 2) For an 802.1q-tagged packet
For incoming 802.1q tagged packets, you can configure the switch to trust packet priority with the priority-trust command or to trust port priority (the default). The priority mapping process is as shown in Figure 1-5. Figure 1-5 Assign precedence to received packets in different trust modes
Trusting port priority In this mode, the switch replaces the 802.1p precedence value of the received packet with the port priority, looks up the 802.1p-precedence-to-other-precedence mapping table for the set of precedence values corresponding to the port priority of the receiving port and assigns the matching precedence value set to the packet. Trusting packet priority After configuring the switch to trust packet priority on a port, you can specify the trusted priority type, which can be 802.1p precedence or DSCP precedence. Table 1-5 describes how your switch handles a packet received on the port. Table 1-5 Actions performed when packet priority is trusted Trusted priority type 802.1p precedence Description The switch looks up the 802.1p-precedence-to-other-precedence mapping table for the set of precedence values corresponding to the 802.1p precedence of the packet. The switch looks up the DSCP-precedence-to-other-precedence mapping table for the set of precedence values corresponding to the DSCP value of the packet.
DSCP
The
Switch
4200G
series
provide
CoS-precedence-to-other-precedence,
and
DSCP-precedence-to-other-precedence mapping tables for priority mapping. Table 1-6 through Table 1-7 list the default settings of these tables.
1-7
Table 1-6 The default CoS-precedence-to-other-precedence mapping table of Switch 4200G series 802.1p precedence value 0 1 2 3 4 5 6 7 2 0 1 3 4 5 6 7 Target local precedence value Target drop precedence value 0 0 0 0 0 0 0 0
Table 1-7 The default DSCP -to-other-precedence mapping table of Switch 4200G series DSCP values 0 to 7 8 to 15 16 to 23 24 to 31 32 to 39 40 to 47 48 to 55 56 to 63 0 1 2 3 4 5 6 7 Target local precedence value Target drop precedence value 1 1 1 1 0 0 0 0
Protocol Priority
Protocol packets generated by your switch carry their own priority. You can set a new IP precedence or DSCP value for the locally generated traffic of a particular protocol to implement QoS.
1-8
Token bucket
A token bucket can be considered as a container holding a certain number of tokens. The system puts tokens into the bucket at a set rate. When the token bucket is full, the extra tokens will overflow. Figure 1-6 Evaluate the traffic with the token bucket
Put tokens in the bucket at the set rate
Continue to send
Drop
Traffic policing
A typical application of traffic policing is to supervise the specification of certain traffic entering a network and limit it within a reasonable range, or to "discipline" the exceeding traffic. In this way, the network resources and the interests of the carrier are protected. For example, you can limit the bandwidth for HTTP packets to less than 50% of the total. If the traffic of a certain session exceeds the limit, traffic policing can drop the packets or to re-mark the priority of the packets.
1-9
Traffic policing is widely used for policing traffic entering the network of internet service providers (ISPs). It can classify the policed traffic and perform pre-defined policing actions based on different evaluation results. These actions include: Dropping the nonconforming packets. Forwarding the conforming packets.
Traffic shaping
Traffic shaping provides measures to adjust the rate of outbound traffic actively. A typical traffic shaping application is to limit the local traffic output rate according to the downstream traffic policing parameters. The major difference between traffic shaping and traffic policing is that the packets to be dropped in traffic policing are cached in a buffer or queue in traffic shaping, as shown in Figure 1-7. When there are enough tokens in the token bucket, the cached packets are sent out at an even rate. Traffic shaping may introduce an additional delay while traffic policing does not. Figure 1-7 Diagram for traffic shaping
For example, Device A sends packets to Device B. Device B performs traffic policing on packets from Device A and drops the packets exceeding the limit. To avoid unnecessary packet loss, you can perform traffic shaping for the packets destined for Device B on the outgoing interface of Device A. Thus, packets exceeding the limit are cached in Device A and sent when enough resources are available. This ensures that all traffic sent to Device B conforms to the traffic specification defined on Device B.
Queue Scheduling
When the network is congested, the problem that many packets compete for resources must be solved, usually through queue scheduling. A Switch 4200G supports strict priority (SP) queuing, weighted round robin (WRR) queuing, and shaped deficit WRR (SDWRR) queuing. 1) SP queuing
1-10
SP queuing is specially designed for mission-critical applications. The key feature of mission-critical applications is that they require preferential service to reduce the response delay when congestion occurs. Assume that there are eight output queues on the port and SP queuing classifies the eight output queues on the port into eight classes, which are queue 7, queue 6, queue 5, queue 4, queue 3, queue 2, queue 1, and queue 0 in the descending order of priority. SP queuing schedules the eight queues strictly in the descending order of priority. It sends packets in the queue with the highest priority first. When the queue with the highest priority is empty, it sends packets in the queue with the second highest priority, and so on. By assigning mission-critical packets to high priority queues and common service packets to low priority queues, you can ensure that the mission-critical packets are always served prior to common service packets. The disadvantage of SP queuing is that packets in the lower priority queues cannot get served if there are packets in the higher priority queues for a long time when congestion occurs. This may cause low priority traffic to starve to death. 2) WRR queuing
1-11
WRR queuing schedules all the queues in turn and ensure that all of them can be served for a certain time by assigning each queue a weight representing a certain amount of resources. Assume there are eight output queues on the port. WRR assigns queues 7 through 0 the weights w7, w6, w5, w4, w3, w2, w1, and w0. For example, on a 100 Mbps port, you can configure the weights for WRR queuing to 50, 50, 30, 30, 10, 10, 10, and 10 (corresponding to w7, w6, w5, w4, w3, w2, w1, and w0 in order). In this way, the queue with the lowest priority can get 5 Mbps (100 Mbps 1/(5 + 5 + 3 + 3 + 1 + 1 + 1 + 1)) bandwidth at least, thus avoiding the disadvantage of SP queuing that the packets in low-priority queues may failed to be served for a long time. Another advantage of WRR queuing is that though the queues are scheduled in order, the service time for each queue is not fixed. With WRR, if a queue is empty, the next queue will be scheduled immediately. In this way, the bandwidth resources are fully utilized. 3) SDWRR
Compared with WRR, SDWRR reduces scheduling delay and smoothes jitter for lower priority queues. For example, set the weight values of queue 0 and queue 1 to 5 and 3 respectively. WRR and SDWRR schedule the queues as follows: WRR: dequeues the number of packets identical to weight 3 from queue 1 only after the number of packets identical to weight 5 are dequeued from queue 0. If there is a wide difference between the weight values of two queues, great delay and jitter will result for the lower-weight queue. SDWRR: schedules the two queues in turn in such a way that packets identical to one weight are dequeued from queue 0 first and then from queue 1. The procedure is repeated until the scheduling for one queue is over. Then, SDWRR schedules the queue with remaining weights to dequeue the number of packets identical to the remaining weights. The detailed scheduling sequence is described in the Table 1-8. Table 1-8 Queue-scheduling sequence of SDWRR Queue scheduling algorithm WRR Queue scheduling sequence 0, 0, 0, 0, 0, 1, 1, 1, 0, 0, 0, 0, 0, 1, 1, 1 Remarks 0 indicates packets identical to one weight in queue 0. 1 indicates packets identical to one weight in queue 1.
SDWRR
0, 1, 0, 1, 0, 1, 0, 0, 1, 0, 1, 0, 1, 0, 0, 0
Burst
The burst function improves packet buffering and forwarding performance in the following scenarios: Dense broadcast or multicast traffic and massive burst traffic are present. High-speed traffic is forwarded over a low-speed link or traffic received from multiple interfaces at the same speed is forwarded through an interface at the same speed.
1-12
By enabling the burst function on your device, you can improve the processing performance of the device operating in the above scenarios and thus reduce packet loss rate. Because the burst function may affect the QoS performance of your device, you must make sure that you are fully aware of the impacts when enabling the burst function.
QoS Configuration
QoS Configuration Task List
Complete the following tasks to configure QoS: Task Configuring Priority Trust Mode Configuring Priority Mapping Setting the Priority of Protocol Packets Configuring Traffic Policing Configuring Traffic Shaping Configuring Queue Scheduling Configuring Traffic Accounting Enabling the Burst Function Optional Optional Optional Optional Optional Optional Optional Optional Remarks
Configuration prerequisites
The priority trust mode to be used has been determined. The port where priority trust mode is to be configured has been determined. The port priority value has been determined.
Configuration procedures
1) Configuring a port to trust port priority
Follow these steps to configure a port to trust port priority: To do Enter system view Enter Ethernet port view Use the command system-view interface interface-type interface-number Optional Configure to trust port priority and configure the port priority priority priority-level By default, the switch trusts port priority and the priority of a port is 0. Remarks
2)
1-13
Follow these steps to configure a port to trust 802.1p precedence: To do Enter system view Enter Ethernet port view Configure to trust 802.1p precedence Use the command system-view interface interface-type interface-number priority-trust cos Required By default, port priority is trusted. Remarks
3)
Follow these steps to configure a port to trust DSCP value of traffic: To do Enter system view Enter Ethernet port view Configure to trust DSCP values Use the command system-view interface interface-type interface-number priority-trust dscp Required By default, port priority is trusted. Remarks
Configuration examples
# Configure trusting port priority on GigabitEthernet 1/0/1 and set the priority of GigabitEthernet 1/0/1 to 7.
<Sysname> system-view [Sysname] interface GigabitEthernet1/0/1 [Sysname-GigabitEthernet1/0/1] priority 7
Configuration prerequisites
The target CoS-precedence-to-other-precedence, and DSCP-precedence-to-other-precedence
1-14
Configuration procedures
1) Configuring the CoS-precedence-to-other-precedence mapping table
Follow these steps to configure the CoS-precedence-to-other-precedence mapping table: To do Enter system view Configure the CoS-precedence-to-local-p recedence mapping table Use the command system-view qos cos-local-precedence-map cos0-map-local-prec cos1-map-local-prec cos2-map-local-prec cos3-map-local-prec cos4-map-local-prec cos5-map-local-prec cos6-map-local-prec cos7-map-local-prec qos cos-drop-precedence-map cos0-map-drop-prec cos1-map-drop-prec cos2-map-drop-prec cos3-map-drop-prec cos4-map-drop-prec cos5-map-drop-prec cos6-map-drop-prec cos7-map-drop-prec Remarks
Required
Required
2)
Follow these steps to configure the DSCP-precedence-to-other-precedence mapping table: To do Enter system view Configure DSCP-precedence-to-local -precedence mapping table Configure DSCP-precedence-to-drop -precedence mapping table Use the command system-view qos dscp-local-precedence-map dscp-list : local-precedence qos dscp-drop-precedence-map dscp-list : drop-precedence Required Remarks
Required
Configuration examples
# Configure the CoS-precedence-to-local-precedence mapping table for a Switch 4200G as follows: 0 to 2, 1 to 3, 2 to 4, 3 to 1, 4 to 7, 5 to 0, 6 to 5, and 7 to 6. Then display the CoS-precedence-to-local-precedence mapping table.
<Sysname> system-view [Sysname] qos cos-local-precedence-map 2 3 4 1 7 0 5 6 [Sysname] display qos cos-local-precedence-map cos-local-precedence-map: cos(802.1p) : 0 1 2 3 4 5 6 7
-------------------------------------------------------------------------local precedence(queue) : 2 3 4 1 7 0 5 6
# Configure the DSCP-precedence-to-local-precedence mapping table for a Switch 4200G as follows: 0 through 7 to 2, 8 through 15 to 3, 16 through 23 to 4, 24 through 31 to 1, 32 through 39 to 7, 40 through 47 to 0, 48 through 55 to 5, and 56 through 63 to 6. Then display the DSCP-precedence-to-local-precedence mapping table.
<Sysname> system-view [Sysname] qos dscp-local-precedence-map 0 1 2 3 4 5 6 7 : 2
1-15
[Sysname] qos dscp-local-precedence-map 8 9 10 11 12 13 14 15 : 3 [Sysname] qos dscp-local-precedence-map 16 17 18 19 20 21 22 23 : 4 [Sysname] qos dscp-local-precedence-map 24 25 26 27 28 29 30 31 : 1 [Sysname] qos dscp-local-precedence-map 32 33 34 35 36 37 38 39 : 7 [Sysname] qos dscp-local-precedence-map 40 41 42 43 44 45 46 47 : 0 [Sysname] qos dscp-local-precedence-map 48 49 50 51 52 53 54 55 : 5 [Sysname] qos dscp-local-precedence-map 56 57 58 59 60 61 62 63 : 6 <Sysname> display qos dscp-local-precedence-map dscp-local-precedence-map: dscp : local-precedence(queue) ---------------------------------------------0 : 1 : 2 : 3 : 4 : 5 : 6 : 7 : 8 : 9 : 10 : 11 : 12 : 13 : 14 : 15 : 16 : 17 : 18 : 19 : 20 : 21 : 22 : 23 : 24 : 25 : 26 : 27 : 28 : 29 : 30 : 31 : 32 : 33 : 34 : 35 : 2 2 2 2 2 2 2 2 3 3 3 3 3 3 3 3 4 4 4 4 4 4 4 4 1 1 1 1 1 1 1 1 7 7 7 7
1-16
36 : 37 : 38 : 39 : 40 : 41 : 42 : 43 : 44 : 45 : 46 : 47 : 48 : 49 : 50 : 51 : 52 : 53 : 54 : 55 : 56 : 57 : 58 : 59 : 60 : 61 : 62 : 63 :
7 7 7 7 0 0 0 0 0 0 0 0 5 5 5 5 5 5 5 5 6 6 6 6 6 6 6 6
Configuration prerequisites
The protocol type has been determined. The priority type (IP or DSCP) and priority value have been determined.
Configuration procedure
Follow these steps to set the priority of the specific protocol packets: To do Enter system view Use the command system-view protocol-priority protocol-type protocol-type { ip-precedence ip-precedence | dscp dscp-value } Required Set the priority of the specific type of protocol packets You can modify the IP precedence values or DSCP values of the corresponding protocol packets. On a Switch 4200G, you can set the priority for protocol packets of Telnet, SNMP, and ICMP. Remarks
1-17
Configuration examples
# Set the IP precedence value of ICMP packets to 3.
<Sysname> system-view [Sysname] protocol-priority protocol-type icmp ip-precedence 3
# After completing the above configuration, display the list of protocol priorities manually specified.
[Sysname] display protocol-priority Protocol: icmp IP-Precedence: flash(3)
Configuration prerequisites
The ACL rules used for traffic classification have been defined. Refer to the ACL module of this manual for information about defining ACL rules. The rate limit for traffic policing and the actions for the packets exceeding the rate limit have been determined.
Configuration procedures
You can configure traffic policing for the incoming packets matching the specific ACL rules globally, in a VLAN, in a port group, or on a port. 1) Configuring traffic policing globally
Follow these steps to configure traffic policing for the incoming packets matching the specific ACL rules globally: To do Enter system view Configure traffic policing Use the command system-view traffic-limit inbound acl-rule target-rate Required Disabled by default. Remarks
2)
Follow these steps to configure traffic policing for the incoming packets matching the specific ACL rules in a VLAN: To do Enter system view Configure traffic policing Use the command system-view traffic-limit vlan vlan-id inbound acl-rule target-rate Required Disabled by default. Remarks
3)
Follow these steps to configure traffic policing for the incoming packets matching the specific ACL rules in a port group:
1-18
To do Enter system view Enter port group view Configure traffic policing
Use the command system-view port-group group-id traffic-limit inbound acl-rule target-rate Required
Remarks
Disabled by default.
4)
Follow these steps to configure traffic policing for the incoming packets matching the specific ACL rules on a port: To do Enter system view Enter Ethernet port view Configure traffic policing system-view interface interface-type interface-number traffic-limit inbound acl-rule target-rate Use the command Required Disabled by default. Remarks
User-defined traffic classification rules configured for traffic policing in the global scope or for a VLAN take precedence over the default rules used for processing protocol packets. The device will execute traffic policing preferentially, which may affect device management implemented through Telnet and so on.
Configuration example
# Configure traffic policing for the packets from network segment 10.1.1.0/24, setting the rate limit to 128 kbps. 1) Method I
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule permit source 10.1.1.0 0.0.0.255 [Sysname-acl-basic-2000] quit [Sysname] interface GigabitEthernet1/0/1 [Sysname-GigabitEthernet1/0/1] traffic-limit inbound ip-group 2000 128
2)
Method II
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule permit source 10.1.1.0 0.0.0.255 [Sysname-acl-basic-2000] quit [Sysname] traffic-limit vlan 2 inbound ip-group 2000 128
1-19
Configuration prerequisites
The queue for which traffic shaping is to be performed has been determined. The maximum traffic rate and the burst size have been determined. The port where traffic shaping is to be configured has been determined.
Configuration procedure
Follow these steps to configure traffic shaping: To do Enter system view Enter Ethernet port view Use the command system-view interface interface-type interface-number Required Disabled by default. traffic-shape [ queue queue-id ] max-rate burst-size Traffic shaping can be configured in one of the following two modes: Without queue queue-id specified, traffic shaping applies to all traffic. With queue queue-id specified, traffic shaping applies to traffic in the specified queue. Remarks
Configuration example
# Configure traffic shaping for all the traffic to be transmitted through GigabitEthernet 1/0/1, with the maximum traffic rate being 640 kbps and the burst size being 16 kbytes.
<Sysname> system-view [Sysname] interface GigabitEthernet1/0/1 [Sysname-GigabitEthernet1/0/1] traffic-shape 640 16
Configuration prerequisites
The queue scheduling algorithm to be used and the related parameters have been determined.
Configuration procedures
1) Configuring SP queuing
Follow these steps to configure SP queuing: To do Enter system view Use the command system-view Remarks
1-20
To do
Remarks Optional
Configure SP queuing
2)
Follow these steps to configure SDWRR queuing: To do Enter system view system-view queue-scheduler wrr { group1 { queue-id queue-weight } &<1-8> | group2 { queue-id queue-weight } &<1-8> }* Use the command Required Configure SDWRR queuing By default, SP queuing is used on all the output queues of a port. Remarks
The port of a Switch 4200G provides up to eight output queues. You can configure SP queuing, SDWRR queuing, or SP queuing in combination with SDWRR queuing on a port as required. With SDWRR queuing adopted, the output queues of a port can be assigned to group 1 and group 2. The two groups are scheduled using the SP algorithm. For example, you can assign queues 0 through 3 to group 1, and queues 4 through 7 to group 2. The queues in group 2 are scheduled preferentially using WRR. The queues in group 1 are scheduled using WRR only when all the queues in group 2 are empty. With both SP queuing and SDWRR queuing adopted, groups are scheduled using the SP algorithm. Assume that queue 0 and queue 1 are scheduled using SP queuing; queues 2 through 4 are assigned to group 1; queues 5 through 7 are assigned to group 2. The queues in group 2 are scheduled preferentially using WRR. When all the queues in group 2 are empty, the queues in group 1 are scheduled using WRR. Then, queue 1 is scheduled, and then queue 0.
When using SDWRR or SP+SDWRR for queue scheduling, you are recommended to assign queues with successive queue numbers to the same scheduling group.
Configuration example
# Configure a Switch 4200G to use SP+SDWRR for queue scheduling, assigning queue 3, queue 4, and queue 5 to WRR scheduling group 1, with the weigh of 20, 20 and 30; assigning queue 0, queue 1, and queue 2 to WRR group 2, with the weight of 20, 20, and 40; using SP for scheduling queue 6 and queue 7. Display queue scheduling configuration information after the configuration.
<Sysname> system-view [Sysname] queue-scheduler wrr group1 3 20 4 20 5 30 group2 0 20 1 20 2 40 [Sysname] display queue-scheduler
1-21
QID:
scheduling-group
weight
----------------------------------0 : 1 : 2 : 3 : 4 : 5 : 6 : 7 : wrr , group2 wrr , group2 wrr , group2 wrr , group1 wrr , group1 wrr , group1 sp sp 20 20 40 20 20 30 0 0
Configuration prerequisites
The ACL rules for traffic classification have been defined. Refer to the ACL module of this manual for information about defining ACL rules.
Configuration procedures
You can collect/clear traffic statistics about incoming ACL matching packets globally, in a VLAN, in a port group, or on a port. 1) Configuring traffic accounting globally
Follow these steps to collect/clear statistics about the incoming ACL matching packets globally: To do Enter system view Collect statistics of the packets matching a specific ACL rule Clear statistics of the packets matching a specific ACL rule Use the command system-view traffic-statistic inbound acl-rule reset traffic-statistic inbound acl-rule Required Optional Remarks
2)
Follow these steps to collect/clear statistics about the incoming ACL matching packets in a VLAN: To do Enter system view Collect statistics about incoming ACL matching packets Clear statistics about the packets matching a specific ACL rule Use the command system-view traffic-statistic vlan vlan-id inbound acl-rule reset traffic-statistic vlan vlan-id inbound acl-rule Required Optional Remarks
3)
Follow these steps to collect/clear statistics about incoming ACL matching packets in a port group:
1-22
To do Enter system view Enter port group view Collect statistics about ACL matching packets Clear statistics about ACL matching packets
Use the command system-view port-group group-id traffic-statistic inbound acl-rule reset traffic-statistic inbound acl-rule
Remarks
4)
Follow these steps to collect/clear statistics about incoming ACL matching packets on a port: To do Enter system view Enter Ethernet port view Collect statistics about incoming ACL matching packets Clear statistics about incoming ACL matching packets Use the command system-view interface interface-type interface-number traffic-statistic inbound acl-rule Remarks
Required
Optional
User-defined traffic classification rules configured for traffic accounting in the global scope or for a VLAN take precedence over the default rules used for processing protocol packets. The device will collect traffic statistics preferentially, which may affect device management implemented through Telnet and so on.
Configuration examples
# Collect and then clear the statistics about the incoming packets sourced from network segment 10.1.1.0/24 (assume that GigabitEthernet 1/0/1 is connected to network segment 10.1.1.0/24 and carries VLAN 2). 1) Method I
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule permit source 10.1.1.0 0.0.0.255 [Sysname-acl-basic-2000] quit [Sysname] interface GigabitEthernet1/0/1 [Sysname-GigabitEthernet1/0/1] traffic-statistic inbound ip-group 2000 [Sysname-GigabitEthernet1/0/1] reset traffic-statistic inbound ip-group 2000
2)
Method II
1-23
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule permit source 10.1.1.0 0.0.0.255 [Sysname-acl-basic-2000] quit [Sysname] traffic-statistic vlan 2 inbound ip-group 2000 [Sysname] reset traffic-statistic vlan 2 inbound ip-group 2000
Configuration prerequisites
The burst function is required.
Configuration procedure
Follow these steps to enable the burst function: To do Enter system view Enable the burst function Use the command system-view burst-mode enable Required Disabled by default Remarks
Configuration example
# Enable the burst function on a Switch 4200G.
<Sysname> system-view [Sysname] burst-mode enable
1-24
To do Display QoS-related configuration of a port or all the ports Display the priority trust mode of a port or all the ports
Use the command display qos-interface { interface-type interface-number | unit-id } all display qos-interface { interface-type interface-number | unit-id } priority-trust display qos-interface { interface-type interface-number | unit-id } traffic-shape display qos-interface { interface-type interface-number | unit-id } traffic-limit display qos-interface { interface-type interface-number | unit-id } traffic-statistic display qos-global { all | traffic-limit | traffic-statistic } display qos-vlan [ vlan-id ] { all | traffic-limit | traffic-statistic } display qos-port-group [ group-id ] { all | traffic-limit | traffic-statistic }
Display traffic shaping configuration of a port or all the ports Display traffic policing configuration of a port or all the ports Display traffic accounting configuration of a port or all the ports Display global QoS configuration of traffic policing or traffic accounting Display VLAN-level QoS configuration of traffic policing or traffic accounting Display port group-level QoS configuration of traffic policing or traffic accounting
1-25
Configuration procedure
1) Define an ACL for traffic classification
# Create ACL 2000 and enter basic ACL view to match packets sourced from network segment 192.168.1.0/24.
<Sysname> system-view [Sysname] acl number 2000 [Sysname-acl-basic-2000] rule permit source 192.168.1.0 0.0.0.255 [Sysname-acl-basic-2000] quit
# Create ACL 2001 and enter basic ACL view to match packets sourced from network segment 192.168.2.0/24.
[Sysname] acl number 2001 [Sysname-acl-basic-2001] rule permit source 192.168.2.0 0.0.0.255 [Sysname-acl-basic-2001] quit
2)
# Set the maximum rate of outbound IP packets sourced from the marketing department to 64 kbps.
[Sysname] traffic-limit vlan 2 inbound ip-group 2001 64
# Set the maximum rate of outbound IP packets sourced from the R&D department to 128 kbps.
[Sysname] traffic-limit vlan 1 inbound ip-group 2000 128
1-26
Table of Contents
1 Mirroring Configuration 1-1 Mirroring Overview 1-1 1.1.1 Local Port Mirroring 1-1 Remote Port Mirroring 1-2 Mirroring Configuration 1-3 1.1.2 Configuring Local Port Mirroring 1-4 Configuring Remote Port Mirroring 1-5 Displaying Port Mirroring 1-8 Mirroring Configuration Examples 1-8 Local Port Mirroring Configuration Example 1-8 Remote Port Mirroring Configuration Example 1-9
Mirroring Configuration
When configuring mirroring, go to these sections for information you are interested in: Mirroring Overview Mirroring Configuration Displaying Port Mirroring Mirroring Configuration Examples
Mirroring Overview
Mirroring is to duplicate packets from a port to another port connected with a data monitoring device for network monitoring and diagnosis. The port where packets are duplicated is called the source mirroring port or monitored port and the port to which duplicated packets are sent is called the destination mirroring port or the monitor port, as shown in the following figure. Figure 1-1 Mirroring
The Switch 4200G series support five two types of port mirroring: Local Port Mirroring Remote Port Mirroring They are described in the following sections.
The switches involved in remote port mirroring function as follows: Source switch The source switch is the device where the monitored port is located. It copies traffic passing through the monitored port to the reflector port. The reflector port then transmits the traffic to an intermediate switch (if any) or destination switch through the remote-probe VLAN. Intermediate switch Intermediate switches are switches between the source switch and destination switch on the network. An intermediate switch forwards mirrored traffic flows to the next intermediate switch or the destination switch through the remote-probe VLAN. No intermediate switch is present if the source and destination switches directly connect to each other. Destination switch The destination switch is where the monitor port is located. The destination switch forwards the mirrored traffic flows it received from the remote-probe VLAN to the monitoring device through the destination port. Table 1-1 describes how the ports on various switches are involved in the mirroring operation.
1-2
Table 1-1 Ports involved in the mirroring operation Switch Ports involved Function Port monitored. It copies packets to the reflector port through local port mirroring. There can be more than one source port. Receives packets from the source port and broadcasts the packets in the remote-probe VLAN. Sends mirrored packets to the intermediate switch or the destination switch. Sends mirrored packets to the destination switch. Intermediate switch Trunk port Two trunk ports are necessary for the intermediate switch to connect the devices at the source switch side and the destination switch side. Receives remote mirrored packets. Receives packets forwarded from the trunk port and transmits the packets to the data detection device.
Source port
Trunk port
Do not configure a default VLAN, a management VLAN, or a dynamic VLAN as the remote-probe VLAN. Configure all ports connecting the devices in the remote-probe VLAN as trunk ports, and ensure the Layer 2 connectivity from the source switch to the destination switch over the remote-probe VLAN. Do not configure a Layer 3 interface for the remote-probe VLAN, run other protocol packets, or carry other service packets on the remote-prove VLAN and do not use the remote-prove VLAN as the voice VLAN and protocol VLAN; otherwise, remote port mirroring may be affected.
Mirroring Configuration
Complete the following tasks to configure mirroring:
1-3
Task Configuring Local Port Mirroring Configuring Remote Port Mirroring Optional Optional
Remarks
On a Switch 4200G, only one destination port for local port mirroring or one reflector port for remote port mirroring can be configured, and the two kinds of ports cannot both exist.
Configuration procedure
Table 1-2 Follow these steps to configure port mirroring: To do Enter system view Create a port mirroring group In system view Configure the source port for the port mirroring group Use the command system-view mirroring-group group-id local mirroring-group group-id mirroring-port mirroring-port-list { both | inbound | outbound } interface interface-type interface-number In port view mirroring-group group-id mirroring-port { both | inbound | outbound } quit Configure the destination port for the port mirroring group In system view mirroring-group group-id monitor-port monitor-port-id interface interface-type interface-number mirroring-group group-id monitor-port Use either approach The configurations in the two views have the same effect. Required Remarks
Use either approach You can configure multiple source ports at a time in system view, or you can configure the source port in specific port view. The configurations in the two views have the same effect.
In port view
1-4
When configuring local port mirroring, note that: You need to configure the source and destination ports for the local port mirroring to take effect. The source port and the destination port cannot be a member port of an existing mirroring group; besides, the destination port cannot be a member port of an aggregation group or a port enabled with LACP or STP.
A Switch 4200G can serve as a source switch, an intermediate switch, or a destination switch in a remote port mirroring networking environment.
Table 1-3 Follow these steps to perform configurations on the source switch: To do Enter system view Create a VLAN and enter the VLAN view Configure the current VLAN as the remote-probe VLAN Return to system view Enter the view of the Ethernet port that connects to the intermediate switch or destination switch Configure the current port as trunk port Configure the trunk port to permit packets from the remote-probe VLAN Use the command system-view vlan vlan-id remote-probe vlan enable quit interface interface-type interface-number vlan-id is the ID of the remote-probe VLAN. Required Remarks
Required port link-type trunk By default, the port type is Access. Required
1-5
To do Return to system view Create a remote source mirroring group Configure source port(s) for the remote source mirroring group Configure the reflector port for the remote source mirroring group Configure the remote-probe VLAN for the remote source mirroring group
Use the command quit mirroring-group group-id remote-source mirroring-group group-id mirroring-port mirroring-port-list { both | inbound | outbound } mirroring-group group-id reflector-port reflector-port mirroring-group group-id remote-probe vlan remote-probe-vlan-id Required
Remarks
Required
Required
Required
When configuring the source switch, note that: All ports of a remote source mirroring group are on the same device. Each remote source mirroring group can be configured with only one reflector port. The reflector port cannot be a member port of an existing mirroring group, a member port of an aggregation group, or a port enabled with LACP or STP. It must be an access port and cannot be configured with the functions like VLAN-VPN, port loopback detection, port security, and so on. You cannot modify the duplex mode, port rate, and MDI attribute of a reflector port. Only an existing static VLAN can be configured as the remote-probe VLAN. To remove a remote-probe VLAN, you need to restore it to a normal VLAN first. A remote port mirroring group gets invalid if the corresponding remote port mirroring VLAN is removed. Do not configure a port connecting the intermediate switch or destination switch as the mirroring source port. Otherwise, traffic disorder may occur in the network.
Table 1-4 Follow these steps to perform configurations on the intermediate switch: To do Enter system view Create a VLAN and enter VLAN view Configure the current VLAN as the remote-probe VLAN Use the command system-view vlan vlan-id remote-probe vlan enable
1-6
To do Return to system view Enter the view of the Ethernet port connecting to the source switch, destination switch or other intermediate switch Configure the current port as trunk port Configure the trunk port to permit packets from the remote-probe VLAN
Remarks
Required port link-type trunk By default, the port type is Access. Required
Table 1-5 Follow these steps to configure remote port mirroring on the destination switch: To do Enter system view Create a VLAN and enter VLAN view Configure the current VLAN as a remote-probe VLAN Return to system view Enter the view of the Ethernet port connecting to the source switch or an intermediate switch Configure the current port as trunk port Configure trunk port to permit packets from the remote-probe VLAN Return to system view Create a remote destination mirroring group Use the command system-view vlan vlan-id remote-probe vlan enable quit interface interface-type interface-number vlan-id is the ID of the remote-probe VLAN. Required Remarks
Required port link-type trunk By default, the port type is Access. Required Required
1-7
To do Configure the destination port for the remote destination mirroring group Configure the remote-probe VLAN for the remote destination mirroring group
Use the command mirroring-group group-id monitor-port monitor-port mirroring-group group-id remote-probe vlan remote-probe-vlan-id
Remarks Required
Required
When configuring a destination switch, note that: The destination port of remote port mirroring cannot be a member port of an existing mirroring group, a member port of an aggregation group, or a port enabled with LACP or STP. Only an existing static VLAN can be configured as the remote-probe VLAN. To remove a remote-probe VLAN, you need to restore it to a normal VLAN first. A remote port mirroring group gets invalid if the corresponding remote port mirroring VLAN is removed.
1-8
Network diagram
Figure 1-3 Network diagram for local port mirroring
Configuration procedure
Configure Switch C: # Create a local mirroring group.
<Sysname> system-view [Sysname] mirroring-group 1 local
# Configure the source ports and destination port for the local mirroring group.
[Sysname] mirroring-group 1 mirroring-port GigabitEthernet 1/0/1 GigabitEthernet 1/0/2 both [Sysname] mirroring-group 1 monitor-port GigabitEthernet 1/0/3
After the configurations, you can monitor all packets received on and sent from the R&D department and the marketing department on the data detection device.
Department 1 is connected to GigabitEthernet 1/0/1 of Switch A. Department 2 is connected to GigabitEthernet 1/0/2 of Switch A. GigabitEthernet 1/0/3 of Switch A connects to GigabitEthernet 1/0/1 of Switch B. GigabitEthernet 1/0/2 of Switch B connects to GigabitEthernet 1/0/1 of Switch C. The data detection device is connected to GigabitEthernet 1/0/2 of Switch C. The administrator wants to monitor the packets sent from Department 1 and 2 through the data detection device. Use the remote port mirroring function to meet the requirement. Perform the following configurations: Use Switch A as the source switch, Switch B as the intermediate switch, and Switch C as the destination switch. On Switch A, create a remote source mirroring group, configure VLAN 10 as the remote-probe VLAN, ports GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 as the source ports, and port GigabitEthernet 1/0/4 as the reflector port. On Switch B, configure VLAN 10 as the remote-probe VLAN. Configure GigabitEthernet 1/0/3 of Switch A, GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 of Switch B, and GigabitEthernet 1/0/1 of Switch C as trunk ports, allowing packets of VLAN 10 to pass. On Switch C, create a remote destination mirroring group, configure VLAN 10 as the remote-probe VLAN, and configure GigabitEthernet 1/0/2 connected with the data detection device as the destination port.
Network diagram
Figure 1-4 Network diagram for remote port mirroring
Configuration procedure
1) Configure the source switch (Switch A)
# Configure the source ports, reflector port, and remote-probe VLAN for the remote source mirroring group.
[Sysname] mirroring-group 1 mirroring-port GigabitEthernet 1/0/1 GigabitEthernet 1/0/2 inbound [Sysname] mirroring-group 1 reflector-port GigabitEthernet 1/0/4 [Sysname] mirroring-group 1 remote-probe vlan 10
2)
# Configure GigabitEthernet 1/0/1 as the trunk port, allowing packets of VLAN 10 to pass.
[Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] port link-type trunk [Sysname-GigabitEthernet1/0/1] port trunk permit vlan 10 [Sysname-GigabitEthernet1/0/1] quit
# Configure GigabitEthernet 1/0/2 as the trunk port, allowing packets of VLAN 10 to pass.
[Sysname] interface GigabitEthernet 1/0/2 [Sysname-GigabitEthernet1/0/2] port link-type trunk [Sysname-GigabitEthernet1/0/2] port trunk permit vlan 10
3)
# Configure the destination port and remote-probe VLAN for the remote destination mirroring group.
[Sysname] mirroring-group 1 monitor-port GigabitEthernet 1/0/2 [Sysname] mirroring-group 1 remote-probe vlan 10
# Configure GigabitEthernet 1/0/1 as the trunk port, allowing packets of VLAN 10 to pass.
[Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] port link-type trunk [Sysname-GigabitEthernet1/0/1] port trunk permit vlan 10 [Sysname-GigabitEthernet1/0/1] quit
After the configurations, you can monitor all packets sent from Department 1 and 2 on the data detection device.
1-12
Table of Contents
1 Stack 1-1 Stack Function Overview 1-1 The Main Switch of a Stack1-1 The Slave Switches of a Stack1-1 Creating a Stack 1-1 Main Switch Configuration 1-2 Configuring the IP Address Pool and Creating the Stack 1-2 Switching to Slave Switch View1-3 Slave Switch Configuration 1-3 Displaying and Debugging a Stack 1-4 Stack Configuration Example1-4 2 Cluster 2-1 Cluster Overview2-1 Introduction to HGMP 2-1 Roles in a Cluster 2-2 How a Cluster Works2-3 Cluster Configuration Tasks2-8 Configuring the Management Device 2-9 Configuring Member Devices 2-13 Managing a Cluster through the Management Device2-15 Configuring the Enhanced Cluster Features 2-16 Configuring the Cluster Synchronization Function 2-18 Displaying and Maintaining Cluster Configuration 2-22 Cluster Configuration Example 2-23 Basic Cluster Configuration Example2-23 Enhanced Cluster Feature Configuration Example2-26
Stack
The Switch 4200G series switches can form a stack only when connected through interfaces on 10 GE stack boards.
Creating a Stack
The following are the phases undergone when a stack is created.
1-1
Connect the intended main switch and slave switches through stack modules and dedicated stack cables. (Refer to 3Com Switch 4200G 10G Interface Module Installation Guide for the information about stack modules and stack cables.) Configure the IP address pool for the stack and enable the stack function. The main switch then automatically adds the switches connected to its stack ports to the stack. When adding a switch joins in a stack, the main switch automatically assigns an IP address to it. The main switch automatically adds any switches that are newly connected to the stack through their stack ports to the stack.
Remove the IP address configured for the existing Layer 3 interface first if you want to cancel the stack-related configuration, otherwise, IP address conflicts may occur.
As for the stack-related configurations performed on a main switch, note that: After a stack is created, the main switch automatically adds the switches connected to its stack ports to the stack. If a stack port connection is disconnected, the corresponding slave switch quits the stack automatically. The IP address pool of an existing stack cannot be modified.
1-2
To add a switch to a stack successfully, make sure the IP address pool contains at least one unoccupied IP address. Make sure the IP addresses in the IP address pool of a stack are successive so that they can be assigned successively. For example, the IP addresses in an IP address pool with its start IP address something like 223.255.255.254 are not successive. In this case, errors may occur when adding a switch to the stack. IP addresses in the IP address pool of a stack must be of the same network segment. For example, the 1.1.255.254 is not a qualified start address for a stack IP address pool. If the IP address of the management VLAN interface of the main switch (or a slave switch) is not of the same network segment as that of the stack address pool, the main switch (or the slave switch) automatically removes the existing IP address and picks a new one from the stack address pool as its IP address. Since both stack and cluster use the management VLAN and only one VLAN interface is available on the Switch 4200G switch, stack and cluster must share the same management VLAN if you want to configure stack within a cluster.
You can quit slave switch view after slave switch configuration. Table 1-3 Quit slave switch view Operation Command Description You can quit slave switch view only by executing this command in user view of a slave switch.
quit
1-3
1-4
Network diagram
Figure 1-1 Network diagram for stack configuration
Configuration procedure
# Configure the IP address pool for the stack on Switch A.
<Sysname> system-view [Sysname] stacking ip-pool 129.10.1.15 3
Member number: 1 Name:stack_1.Sysname Device: 4200G PWR 24-Port MAC Address: 000f-e200-3130 Member status:Up
1-5
IP: 129.10.1.16/16
Member number: 2 Name:stack_2.Sysname Device: 4200G PWR 24-Port MAC Address: 000f-e200-3135 Member status:Up IP: 129.10.1.17/16
1-6
Cluster
Cluster Overview
Introduction to HGMP
A cluster contains a group of switches. Through cluster management, you can manage multiple geographically dispersed in a centralized way. Cluster management is implemented through Huawei group management protocol (HGMP). HGMP version 2 (HGMPv2) is used at present. A switch in a cluster plays one of the following three roles: Management device Member device Candidate device A cluster comprises of a management device and multiple member devices. To manage the devices in a cluster, you need only to configure an external IP address for the management switch. Cluster management enables you to configure and manage remote devices in batches, reducing the workload of the network configuration. Normally, there is no need to configure external IP addresses for member devices. Figure 2-1 illustrates a cluster implementation. Figure 2-1 A cluster implementation
HGMP V2 has the following advantages: It eases the configuration and management of multiple switches: You just need to configure a public IP address for the management device instead of for all the devices in the cluster; and then
2-1
you can configure and manage all the member devices through the management device without the need to log onto them one by one. It provides the topology discovery and display function, which assists in monitoring and maintaining the network. It allows you to configure and upgrade multiple switches at the same time. It enables you to manage your remotely devices conveniently regardless of network topology and physical distance. It saves IP address resource.
Roles in a Cluster
The switches in a cluster play different roles according to their functions and status. You can specify the role a switch plays. A switch in a cluster can also switch to other roles under specific conditions. As mentioned above, the three cluster roles are management device, member device, and candidate device. Table 2-1 Description on cluster roles Role Configuration Function Provides an interface for managing all the switches in a cluster Manages member devices through command redirection, that is, it forwards the commands intended for specific member devices. Discovers neighbors, collects the information about network topology, manages and maintains the cluster. Management device also supports FTP server and SNMP host proxy. Processes the commands issued by users through the public network Members of a cluster Discovers the information about its neighbors, processes the commands forwarded by the management device, and reports log. The member devices of a luster are under the management of the management device. Candidate device refers to the devices that do not belong to any clusters but are cluster-capable.
Management device
Member device
Candidate device
2-2
A candidate device becomes a management device when you create a cluster on it. Note that a cluster must have one (and only one) management device. On becoming a management device, the device collects network topology information and tries to discover and determine candidate devices, which can then be added to the cluster through configurations. A candidate device becomes a member device after being added to a cluster. A member device becomes a candidate device after it is removed from the cluster. A management device becomes a candidate device only after the cluster is removed.
After you create a cluster on an Switch 4200G switch, the switch collects the network topology information periodically and adds the candidate switches it finds to the cluster. The interval for a management device to collect network topology information is determined by the NTDP timer. If you do not want the candidate switches to be added to a cluster automatically, you can set the topology collection interval to 0 by using the ntdp timer command. In this case, the switch does not collect network topology information periodically.
The management device adds the candidate devices to the cluster or removes member devices from the cluster according to the candidate device information collected through NTDP.
Introduction to NDP
NDP is a protocol used to discover adjacent devices and provide information about them. NDP operates on the data link layer, and therefore it supports different network layer protocols. NDP is able to discover directly connected neighbors and provide the following neighbor information: device type, software/hardware version, and connecting port. In addition, it may provide the following neighbor information: device ID, port full/half duplex mode, product version, the Boot ROM version and so on. An NDP-enabled device maintains an NDP neighbor table. Each entry in the NDP table can automatically ages out. You can also clear the current NDP information manually to have neighbor information collected again. An NDP-enabled device regularly broadcasts NDP packet through all its active ports. An NDP packet carries a holdtime field, which indicates how long the receiving devices will keep the NDP packet data. The receiving devices store the information carried in the NDP packet into the NDP table but do not forward the NDP packet. When they receive another NDP packet, if the information carried in the packet is different from the stored one, the corresponding entry in the NDP table is updated, otherwise only the holdtime of the entry is updated.
Introduction to NTDP
NTDP is a protocol used to collect network topology information. NTDP provides information required for cluster management: it collects topology information about the switches within the specified hop count, so as to provide the information of which devices can be added to a cluster. Based on the neighbor information stored in the neighbor table maintained by NDP, NTDP on the management device advertises NTDP topology collection requests to collect the NDP information of each device in a specific network range as well as the connection information of all its neighbors. The information collected will be used by the management device or the network management software to implement required functions. When a member device detects a change on its neighbors through its NDP table, it informs the management device through handshake packets, and the management device triggers its NTDP to perform specific topology collection, so that its NTDP can discover topology changes timely. The management device collects the topology information periodically. You can also launch an operation of topology information collection by executing related commands. The process of topology information collection is as follows. The management device sends NTDP topology collection requests periodically through its NTDP-enabled ports. Upon receiving an NTDP topology collection request, the device returns a NTDP topology collection response to the management device and forwards the request to its neighbor devices through its NTDP-enable ports. The topology collection response packet contains the information about the local device and the NDP information about all the neighbor devices. The neighbor devices perform the same operation until the NTDP topology collection request is propagated to all the devices within the specified hops. When an NTDP topology collection request is propagated in the network, it is received and forwarded by large numbers of network devices, which may cause network congestion and the management
2-4
device busy processing of the NTDP topology collection responses. To avoid such cases, the following methods can be used to control the NTDP topology collection request advertisement speed. Configuring the devices not to forward the NTDP topology collection request immediately after they receive an NTDP topology collection request. That is, configure the devices to wait for a period before they forward the NTDP topology collection request. Configuring each NTDP-enabled port on a device to forward an NTDP topology collection request after a specific period since the previous port on the device forwards the NTDP topology collection request.
To implement NTDP, you need to enable NTDP both globally and on specific ports on the management device, and configure NTDP parameters. On member/candidate devices, you only need to enable NTDP globally and on specific ports. Member and candidate devices adopt the NTDP settings of the management device.
Introduction to Cluster
A cluster must have one and only one management device. Note the following when creating a cluster: You need to designate a management device for the cluster. The management device of a cluster is the portal of the cluster. That is, any operations from outside the network intended for the member devices of the cluster, such as accessing, configuring, managing, and monitoring, can only be implemented through the management device. The management device of the cluster recognizes and controls all the member devices in the cluster, no matter where they are located in the network and how they are connected. The management device collects topology information about all member/candidate devices to provide useful information for you to establish the cluster. By collecting NDP/NTDP information, the management device learns network topology, so as to manage and monitor network devices. Before performing any cluster-related configuration task, you need to enable the cluster function first.
On the management device, you need to enable the cluster function and configure cluster parameters. On the member/candidate devices, however, you only need to enable the cluster function so that they can be managed by the management device.
Cluster maintenance
1) Adding a candidate device to a cluster
2-5
To create a cluster, you need to determine the device to operate as the management device first. The management device discovers and determines candidate devices through NDP and NTDP, and adds them to the cluster. You can also add candidate devices to a cluster manually. After a candidate device is added to a cluster, the management device assigns a member number and a private IP address (used for cluster management) to it. 2) Communications within a cluster
In a cluster, the management device maintains the connections to the member devices through handshake packets. Figure 2-3 illustrates the state machine of the connection between the management device and a member device. Figure 2-3 State machine of the connection between the management device and a member device
Active
Receives the handshake or management packets Fails to receive handshake packets in three consecutive intervals State holdtime exceeds the specified value
Connect
Disconnect
After a cluster is created and a candidate device is added to the cluster as a member device, both the management device and the member device store the state information of the member device and mark the member device as Active. The management device and the member devices exchange handshake packets periodically. Note that the handshake packets exchanged keep the states of the member devices to be Active and are not responded. If the management device does not receive a handshake packet from a member device after a period three times of the interval to send handshake packets, it changes the state of the member device from Active to Connect. Likewise, if a member device fails to receive a handshake packet from the management device after a period three times of the interval to send handshake packets, the state of the member device will also be changed from Active to Connect. If the management device receives a handshake packet or management packet from a member device that is in Connect state within the information holdtime, it changes the state of the member device to Active; otherwise, it changes the state of the member device (in Connect state) to Disconnect, in which case the management device considers the member device disconnected. Likewise, if this member device, which is in Connect state, receives a handshake packet or management packet from the management device within the information holdtime, it changes its state to Active; otherwise, it changes its state to Disconnect. If the connection between the management device and a member device in Disconnect state is recovered, the member device will be added to the cluster again. After that, the state of the member device will turn to Active both locally and on the management device. Besides, handshake packets are also used by member devices to inform the management device of topology changes.
2-6
Additionally, on the management device, you can configure the FTP server, TFTP server, logging host and SNMP host to be shared by the whole cluster. When a member device in the cluster communicates with an external server, the member device first transmits data to the management device, which then forwards the data to the external server. The management device is the default shared FTP/TFTP server for the cluster; it serves as the shared FTP/TFTP server when no shared FTP/TFTP server is configured for the cluster.
Management VLAN
Management VLAN limits the range of cluster management. Through management VLAN configuration, the following functions can be implemented: Enabling the management packets (including NDP packets, NTDP packets, and handshake packets) to be transmitted in the management VLAN only, through which the management packets are isolated from other packets and network security is improved. Enabling the management device and the member devices to communicate with each other in the management VLAN. Cluster management requires the packets of the management VLAN be permitted on ports connecting the management device and the member/candidate devices. Therefore: If the packets of management VLAN are not permitted on a candidate device port connecting to the management device, the candidate device cannot be added to the cluster. In this case, you can enable the packets of the management VLAN to be permitted on the port through the management VLAN auto-negotiation function. Packets of the management VLAN can be exchanged between the management device and a member device/candidate device without carrying VLAN tags only when the default VLAN ID of both the two ports connecting the management device and the member/candidate device is the management VLAN. If the VLAN IDs of the both sides are not that of the management VLAN, packets of the management VLAN need to be tagged.
By default, the management VLAN interface is used as the network management interface. There is only one network management interface on a management device; any newly configured network management interface will overwrite the old one.
1)
Determine whether the destination MAC address or destination IP address is used to trace a device in the cluster If you use the tracemac command to trace the device by its MAC address, the switch will query its MAC address table according to the MAC address and VLAN ID in the command to find out the port connected with the downstream switch. If you use the tracemac command to trace the device by its IP address, the switch will query the corresponding ARP entry of the IP address to find out the corresponding MAC address and VLAN ID, and thus find out the port connected with the downstream switch.
2)
After finding out the port connected with the downstream switch, the switch will send a multicast packet with the VLAN ID and specified hops to the port. Upon receiving the packet, the downstream switch compares its own MAC address with the destination MAC address carried in the multicast packet: If the two MAC addresses are the same, the downstream switch sends a response to the switch sending the tracemac command, indicating the success of the tracemac command. If the two MAC addresses are different, the downstream switch will query the port connected with its downstream switch based on the MAC address and VLAN ID, and then forward the packet to its downstream switch. If within the specified hops, a switch with the specified destination MAC address is found, this switch sends a response to the switch sending the tracemac command, indicating the success of the tracemac command. If no switch with the specified destination MAC address (or IP address) is found, the multicast packet will not be forwarded to the downstream any more.
If the queried IP address has a corresponding ARP entry, but the MAC address entry corresponding to the IP address does not exist, the trace of the device fails. To trace a specific device using the tracemac command, make sure that all the devices passed support the tracemac function. To trace a specific device in a management VLAN using the tracemac command, make sure that all the devices passed are within the same management VLAN as the device to be traced.
Remarks
To reduce the risk of being attacked by malicious users against opened socket and enhance switch security, the Switch 4200G series Ethernet switches provide the following functions, so that a cluster socket is opened only when it is needed: Opening UDP port 40000 (used for cluster) only when the cluster function is implemented, Closing UDP port 40000 at the same time when the cluster function is closed. On the management device, the preceding functions are implemented as follows: When you create a cluster by using the build or auto-build command, UDP port 40000 is opened at the same time. When you remove a cluster by using the undo build or undo cluster enable command, UDP port 40000 is closed at the same time.
2-9
Operation In system view Enable NDP on specified Ethernet ports Enter Ethernet port view Enable NDP on the port
Description
ndp enable
2-10
Operation Configure the device forward delay of topology collection requests Configure the port forward delay of topology collection requests Configure the interval to collect topology information periodically Quit system view Launch topology information collection manually
Description
Table 2-9 Establish a cluster and configure cluster parameters in manual mode Operation Enter system view Specify the management VLAN Enter cluster view Configure a IP address pool for the cluster Build a cluster Command system-view management-vlan vlan-id cluster ip-pool administrator-ip-address { ip-mask | ip-mask-length } build name Required By default, VLAN 1 is used as the management VLAN. Required Required name: cluster name. Description
2-11
Description
Set the interval for the management device to send multicast packets
holdtime seconds
timer interval
2)
Table 2-10 Establish a cluster in automatic mode Operation Enter system view Enter cluster view Configure the IP address range for the cluster Start automatic cluster establishment Command system-view cluster ip-pool administrator-ip-address { ip-mask | ip-mask-length } auto-build [ recover ] Required Required Follow prompts to establish a cluster. Description
After a cluster is established automatically, ACL 3998 and ACL 3999 will be generated automatically. After a cluster is established automatically, ACL 3998 and ACL 3999 can neither be modified nor removed.
2-12
Description
By default, the management device acts as the shared FTP server. Optional
tftp-server ip-address
logging-host ip-address
snmp-host ip-address
2-13
To reduce the risk of being attacked by malicious users against opened socket and enhance switch security, the Switch 4200G series Ethernet switches provide the following functions, so that a cluster socket is opened only when it is needed: Opening UDP port 40000 (used for cluster) only when the cluster function is implemented, Closing UDP port 40000 at the same time when the cluster function is closed. On member devices, the preceding functions are implemented as follows: When you execute the add-member command on the management device to add a candidate device to a cluster, the candidate device changes to a member device and its UDP port 40000 is opened at the same time. When you execute the auto-build command on the management device to have the system automatically add candidate devices to a cluster, the candidate devices change to member devices and their UDP port 40000 is opened at the same time. When you execute the administrator-address command on a device, the device's UDP port 40000 is opened at the same time. When you execute the delete-member command on the management device to remove a member device from a cluster, the member device's UDP port 40000 is closed at the same time. When you execute the undo build command on the management device to remove a cluster, UDP port 40000 of all the member devices in the cluster is closed at the same time. When you execute the undo administrator-address command on a member device, UDP port 40000 of the member device is closed at the same time.
ndp enable
2-14
Description
Optional
Optional
2-15
Operation Reboot a specified member device Return to system view Return to user view
Command reboot member { member-number | mac-address H-H-H } [ eraseflash ] quit quit cluster switch-to { member-number | mac-address H-H-H | administrator | sysname sysname } tracemac { by-mac mac-address vlan vlan-id | by-ip ip-address } [ nondp ]
Description
Optional
Optional You can use this command switch to the view of a member device and switch back. Optional These commands can be executed in any view.
After the cluster topology becomes stable, you can use the topology management commands on the cluster administrative device to save the topology of the current cluster as the standard topology and back up the standard topology on the Flash memory of the administrative device . When errors occur to the cluster topology, you can replace the current topology with the standard cluster topology and restore the administrative device using the backup topology on the Flash memory, so that the devices in the cluster can resume normal operation. With the display cluster current-topology command, the switch can display the topology of the current cluster in a tree structure. The output formats include: Display the tree structure three layers above or below the specified node. Display the topology between two connected nodes.
The topology information is saved as a topology.top file in the Flash memory to the administrative device. You cannot specify the file name manually.
2)
To ensure stability and security of the cluster, you can use the blacklist to restrict the devices to be added to the cluster. After you add the MAC address of the device that you need to restrict into the cluster blacklist, even if the cluster function is enabled on this device and the device is normally connected to the current cluster, this device cannot join the cluster and participate in the unified management and configuration of the cluster.
2-16
Before configuring the cluster topology management function, make sure that: The basic cluster configuration is completed. Devices in the cluster work normally. 2) Configuration procedure
Perform the following configuration on the management device. Table 2-19 Configure cluster topology management function Operation Enter system view Enter cluster view Check the current topology and save it as the standard topology. Save the standard topology to the Flash memory of the administrative device Restore the standard topology from the Flash memory of the administrative device Display the detailed information about a single device Command system-view cluster topology accept { all [ save-to { ftp-server | local-flash } ] | mac-address mac-address | member-id member-id | administrator } topology save-to local-flash Description
Required
Required
topology restore-from local-flash display ntdp single-device mac-address mac-address display cluster current-topology [ mac-address mac-address1 [ to-mac-address mac-address2 ] | member-id member-id1 [ to-member-id member-id2 ] ] display cluster base-topology [ mac-address mac-address | member member-id ] display cluster base-members
Optional
Display the information about the base topology of the cluster Display the information about all the devices in the base cluster topology
2-17
Optional Optional
For the SNMP configurations, refer to the SNMP-RMON Operation part in this manual.
1)
Configuration prerequisites NDP and NTDP have been enabled on the management device and member devices, and NDPand NTDP-related parameters have been configured. A cluster is established, and you can manage the member devices through the management device.
2)
Configuration procedure
Perform the following operations on the management device to synchronize SNMP configurations:
2-18
To do Enter system view Enter cluster view Create a public SNMP community for the cluster
Use the command system-view cluster cluster-snmp-agent community { read | write } community-name [ mib-view view-name ] cluster-snmp-agent group v3 group-name [ authentication | privacy ] [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] cluster-snmp-agent usm-user v3 username groupname [ authentication-mode { md5 | sha } authpassstring [ privacy-mode { des56 privpassstring } ] ] cluster-snmp-agent mib-view included view-name oid-tree Required
Remarks
Create or update the public MIB view information for the cluster
Perform the above operations on the management device of the cluster. Configuring the public SNMP information is equal to executing these configurations on both the management device and the member devices (refer to the SNMP-RMON Operation part in this manual), and these configurations will be saved to the configuration files of the management device and the member devices. The public SNMP configurations cannot be synchronized to the devices that are on the cluster blacklist. If a member device leaves the cluster, the public SNMP configurations will not be removed.
3)
Configuration example
# Configure the public SNMP information for the cluster on the management device, including the following: The read community name is read_a The write community name is write_a The group name is group_a The MIB view name is mib_a, which includes all objects of the subtree org The SNMPv3 user is user_a, which belongs to the group group_a. # Create a community with the name of read_a, allowing read-only access right using this community name.
<test_0.Sysname> system-view [test_0.Sysname] cluster
2-19
[test_0.Sysname-cluster] cluster-snmp-agent community read read_a Member 2 succeeded in the read-community configuration. Member 1 succeeded in the read-community configuration. Finish to synchronize the command.
# Create a community with the name of write_a, allowing read and write access right using this community name.
[test_0.Sysname-cluster] cluster-snmp-agent community write write_a Member 2 succeeded in the write-community configuration. Member 1 succeeded in the write-community configuration. Finish to synchronize the command.
# Create a MIB view mib_a, which includes all objects of the subtree org.
[test_0.Sysname-cluster] cluster-snmp-agent mib-view included mib_a org Member 2 succeeded in the mib-view configuration. Member 1 succeeded in the mib-view configuration. Finish to synchronize the command.
# After the above configuration, you can see that the public SNMP configurations for the cluster are saved to the management device and member devices by viewing the configuration files. Configuration file content on the management device (only the SNMP-related information is displayed)
[test_0.Sysname-cluster] display current-configuration # cluster cluster-snmp-agent community read read_a cluster-snmp-agent community write write_a cluster-snmp-agent group v3 group_a cluster-snmp-agent mib-view included mib_a org cluster-snmp-agent usm-user v3 user_a group_a # snmp-agent snmp-agent local-engineid 800007DB000FE22405626877 snmp-agent community read read_a@cm0 snmp-agent community write write_a@cm0 snmp-agent sys-info version all snmp-agent group v3 group_a snmp-agent mib-view included mib_a org
2-20
Configuration file content on a member device (only the SNMP-related information is displayed)
<test_2.Sysname> display current-configuration # snmp-agent snmp-agent local-engineid 800007DB000FE224055F6877 snmp-agent community read read_a@cm2 snmp-agent community write write_a@cm2 snmp-agent sys-info version all snmp-agent group v3 group_a snmp-agent mib-view included mib_a org snmp-agent usm-user v3 user_a group_a
Perform the following operations on the management device to synchronize local user configurations: To do Enter system view Enter cluster view Create a public local user Use the command system-view cluster cluster-local-user username passward { cipher | simple } passwardstring Required Not configured by default. Remarks
2-21
Perform the above operations on the management device of the cluster. Creating a public local user is equal to executing these configurations on both the management device and the member devices (refer to the AAA Operation part in this manual), and these configurations will be saved to the configuration files of the management device and the member devices. The public local user configurations cannot be synchronized to the devices that are on the cluster blacklist. If a member device leaves the cluster, the public local user configurations will not be removed.
display ndp
display ndp interface port-list You can execute the display command in any view.
display ntdp display ntdp device-list [ verbose ] display cluster display cluster candidates [ mac-address H-H-H | verbose ] display cluster members [ member-number | verbose ] reset ndp statistics [ interface port-list ]
2-22
Network diagram
Figure 2-4 Network diagram for HGMP cluster configuration
Configuration procedure
1) Configure the member devices (taking one member as an example)
2-23
2)
# Set the member device forward delay for topology collection requests to 150 ms.
[Sysname] ntdp timer hop-delay 150
# Set the member port forward delay for topology collection requests to 15 ms.
[Sysname] ntdp timer port-delay 15
# Configure a private IP address pool for the cluster. The IP address pool contains six IP addresses, starting from 172.16.0.1.
2-24
# Configure the shared FTP server, TFTP server, Logging host and SNMP host for the cluster.
[aaa_0.Sysname-cluster] ftp-server 63.172.55.1 [aaa_0.Sysname-cluster] tftp-server 63.172.55.1 [aaa_0.Sysname-cluster] logging-host 69.172.55.4 [aaa_0.Sysname-cluster] snmp-host 69.172.55.4
3)
Perform the following operations on the member devices (taking one member as an example)
After adding the devices under the management device to the cluster, perform the following operations on a member device. # Connect the member device to the remote shared FTP server of the cluster.
<aaa_1.Sysname> ftp cluster
# Download the file named aaa.txt from the shared TFTP server of the cluster to the member device.
<aaa_1.Sysname> tftp cluster get aaa.txt
# Upload the file named bbb.txt from the member device to the shared TFTP server of the cluster.
<aaa_1.Sysname> tftp cluster put bbb.txt
After
completing
the
above
configuration,
you
can
execute
the
cluster
switch-to
{ member-number | mac-address H-H-H } command on the management device to switch to member device view to maintain and manage a member device. After that, you can execute the cluster switch-to administrator command to return to management device view. In addition, you can execute the reboot member { member-number | mac-address H-H-H } [ eraseflash ] command on the management device to reboot a member device. For detailed information about these operations, refer to the preceding description in this chapter. After the above configuration, you can receive logs and SNMP trap messages of all cluster members on the NMS.
2-25
Network diagram
Figure 2-5 Network diagram for the enhanced cluster feature configuration
Configuration procedure
# Enter cluster view.
<aaa_0.Sysname> system-view [aaa_0.Sysname] cluster
2-26
Table of Contents
1 SNMP Configuration1-1 SNMP Overview1-1 SNMP Operation Mechanism1-1 SNMP Versions 1-1 Supported MIBs1-2 Configuring Basic SNMP Functions1-2 Configuring Trap-Related Functions 1-5 Configuring Basic Trap Functions 1-5 Configuring Extended Trap Function1-5 Enabling Logging for Network Management1-6 Displaying SNMP 1-6 SNMP Configuration Example 1-7 SNMP Configuration Example1-7 2 RMON Configuration 2-1 Introduction to RMON 2-1 Working Mechanism of RMON2-1 Commonly Used RMON Groups 2-2 RMON Configuration2-3 Displaying RMON2-4 RMON Configuration Example2-4
SNMP Configuration
When configuring SNMP, go to these sections for information you are interested in: SNMP Overview Configuring Basic SNMP Functions Configuring Trap-Related Functions Enabling Logging for Network Management Displaying SNMP SNMP Configuration Example
SNMP Overview
The Simple Network Management Protocol (SNMP) is used for ensuring the transmission of the management information between any two network nodes. In this way, network administrators can easily retrieve and modify the information about any node on the network. In the meantime, they can locate faults promptly and implement the fault diagnosis, capacity planning and report generating. As SNMP adopts the polling mechanism and provides basic function set, it is suitable for small-sized networks with fast-speed and low-cost. SNMP is based on User Datagram Protocol (UDP) and is thus widely supported by many products.
SNMP Versions
Currently, SNMP agent on a switch supports SNMPv3, and is compatible with SNMPv1 and SNMPv2c. SNMPv3 adopts user name and password authentication. SNMPv1 and SNMPv2c adopt community name authentication. The SNMP packets containing invalid community names are discarded. SNMP community name is used to define the relationship between SNMP NMS and SNMP agent. Community name functions as password. It can limit accesses made by SNMP NMS to SNMP agent. You can perform the following community name-related configuration. Specifying MIB view that a community can access.
1-1
Set the permission for a community to access an MIB object to be read-only or read-write. Communities with read-only permissions can only query the switch information, while those with read-write permission can configure the switch as well. Set the basic ACL specified by the community name.
Supported MIBs
An SNMP packet carries management variables with it. Management variable is used to describe the management objects of a switch. To uniquely identify the management objects of the switch, SNMP adopts a hierarchical naming scheme to organize the managed objects. It is like a tree, with each tree node representing a managed object, as shown in Figure 1-1. Each node in this tree can be uniquely identified by a path starting from the root. Figure 1-1 Architecture of the MIB tree
1 1 1 1 5 A B 6 2 2 2
MIB describes the hierarchical architecture of the tree and it is the set defined by the standard variables of the monitored network devices. In the above figure, the managed object B can be uniquely identified by a string of numbers {1.2.1.1}. The number string is the object identifier (OID) of the managed object.
1-2
To do
Remarks Required
Set system information, and specify to enable SNMPv1 or SNMPv2c on the switch
By default, the contact information for system maintenance is " 3Com Corporation.", the system location is " Marlborough, MA 01752 USA ", and the SNMP version is SNMPv3. Required You can set an SNMPv1/SNMPv2c community name through direct configuration. Indirect configuration is compatible with SNMPv3. The added user is equal to the community name for SNMPv1 and SNMPv2c. You can choose either of them as needed. Optional 1,500 bytes by default. Optional
snmp-agent community { read | write } community-name [ acl acl-number | mib-view view-name ]* snmp-agent group { v1 | v2c } group-name [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ] snmp-agent usm-user { v1 | v2c } user-name group-name [ acl acl-number ] snmp-agent packet max-size byte-count
Set the maximum size of an SNMP packet for SNMP agent to receive or send
By default, the device engine ID is enterprise number + device information. Optional By default, the view name is ViewDefault and OID is 1.
Follow these steps to configure basic SNMP functions (SNMPv3): To do Enter system view Use the command system-view Optional Disabled by default. Enable SNMP agent snmp-agent You can enable SNMP agent by executing this command or any of the commands used to configure SNMP agent. Remarks
1-3
To do
Remarks
By default, the contact information for system maintenance is " 3Com Corporation.", the system location is " Marlborough, MA 01752 USA ", and the SNMP version is SNMPv3.
snmp-agent group v3 group-name [ authentication | privacy ] [ read-view read-view ] [ write-view write-view ] [ notify-view notify-view ] [ acl acl-number ] snmp-agent calculate-password plain-password mode { md5 | sha } { local-engineid | specified-engineid engineid } snmp-agent usm-user v3 user-name group-name [ [ cipher ] authentication-mode { md5 | sha } auth-password [ privacy-mode { des56 | aes128 } priv-password ] ] [ acl acl-number ] snmp-agent packet max-size byte-count
Required
Optional This command is used if password in cipher-text is needed for adding a new user.
Required
Set the maximum size of an SNMP packet for SNMP agent to receive or send
snmp-agent local-engineid engineid snmp-agent mib-view { included | excluded } view-name oid-tree [ mask mask-value ]
By default, the device engine ID is enterprise number + device information. Optional By default, the view name is ViewDefault and OID is 1.
A Switch 4200G provides the following functions to prevent attacks through unused UDP ports. Executing the snmp-agent command or any of the commands used to configure SNMP agent enables the SNMP agent, and at the same opens UDP port 161 used by SNMP agents and the UDP port used by SNMP trap respectively. Executing the undo snmp-agent command disables the SNMP agent and closes UDP ports used by SNMP agent and SNMP trap as well.
1-4
quit snmp-agent target-host trap address udp-domain { ip-address } [ udp-port port-number ] params securityname security-string [ v1 | v2c | v3 [ authentication | privacy ] ] snmp-agent trap source interface-type interface-number snmp-agent trap queue-size size
Required
Set the source address for traps Set the size of the queue used to hold the traps to be sent to the destination host Set the aging time for traps
1-5
Follow these steps to configure extended trap function: To do Enter system view Use the command system-view Optional Configure the extended trap function snmp-agent trap ifmib link extended By default, the linkUp/linkDown trap adopts the standard format defined in IF-MIB. For details, refer to RFC 1213. Remarks
When SNMP logging is enabled on a device, SNMP logs are output to the information center of the device. With the output destinations of the information center set, the output destinations of SNMP logs will be decided. The severity level of SNMP logs is informational, that is, the logs are taken as general prompt information of the device. To view SNMP logs, you need to enable the information center to output system information with informational level. For detailed description on system information and information center, refer to the Information Center Configuration part in this manual.
Displaying SNMP
To do Display the SNMP information about the current device Display SNMP packet statistics Display the engine ID of the current device Display group information about the device Display SNMP user information Use the command display snmp-agent sys-info [ contact | location | version ]* display snmp-agent statistics display snmp-agent { local-engineid | remote-engineid } display snmp-agent group [ group-name ] display snmp-agent usm-user [ engineid engineid | username user-name | group group-name ]* Remarks Available in any view.
1-6
To do Display trap list information Display the currently configured community name Display the currently configured MIB view
Use the command display snmp-agent trap-list display snmp-agent community [ read | write ] display snmp-agent mib-view [ exclude | include | viewname view-name ]
Remarks
Network diagram
Figure 1-2 Network diagram for SNMP configuration
Switch A 10.10.10.2/16
NMS 10.10.10.1/16
Network procedure
# Enable SNMP agent, and set the SNMPv1 and SNMPv2c community names.
<Sysname> system-view [Sysname] snmp-agent [Sysname] snmp-agent sys-info version all [Sysname] snmp-agent community read public [Sysname] snmp-agent community write private
# Set the access right of the NMS to the MIB of the SNMP agent.
[Sysname] snmp-agent mib-view include internet 1.3.6.1
# For SNMPv3, set: SNMPv3 group and user security to the level of needing authentication and encryption authentication protocol to HMAC-MD5 authentication password to passmd5 encryption protocol to DES encryption password to cfb128cfb128
[Sysname] snmp-agent group v3 managev3group privacy write-view internet
1-7
[Sysname] snmp-agent usm-user v3 managev3user managev3group authentication-mode md5 passmd5 privacy-mode des56 cfb128cfb128
# Set the VLAN-interface 2 as the interface used by NMS. Add port GigabitEthernet 1/0/2, which is to be used for network management, to VLAN 2. Set the IP address of VLAN-interface 2 as 10.10.10.2.
[Sysname] vlan 2 [Sysname-vlan2] port GigabitEthernet 1/0/2 [Sysname-vlan2] quit [Sysname] interface Vlan-interface 2 [Sysname-Vlan-interface2] ip address 10.10.10.2 255.255.255.0 [Sysname-Vlan-interface2] quit
# Enable the SNMP agent to send traps to the NMS whose IP address is 10.10.10.1. The SNMP community name to be used is public.
[Sysname] snmp-agent trap enable standard authentication [Sysname] snmp-agent trap enable standard coldstart [Sysname] snmp-agent trap enable standard linkup [Sysname] snmp-agent trap enable standard linkdown [Sysname] snmp-agent target-host trap address udp-domain 10.10.10.1 udp-port 5000 params securityname public
1-8
RMON Configuration
When configuring RMON, go to these sections for information you are interested in: Introduction to RMON RMON Configuration Displaying RMON RMON Configuration Example
Introduction to RMON
Remote Monitoring (RMON) is a kind of MIB defined by Internet Engineering Task Force (IETF). It is an important enhancement made to MIB II standards. RMON is mainly used to monitor the data traffic across a network segment or even the entire network, and is currently a commonly used network management standard. An RMON system comprises of two parts: the network management station (NMS) and the agents running on network devices. RMON agents operate on network monitors or network probes to collect and keep track of the statistics of the traffic across the network segments to which their ports connect, such as the total number of the packets on a network segment in a specific period of time and the total number of packets successfully sent to a specific host. RMON is fully based on SNMP architecture. It is compatible with the current SNMP implementations. RMON enables SNMP to monitor remote network devices more effectively and actively, thus providing a satisfactory means of monitoring remote subnets. With RMON implemented, the communication traffic between NMS and SNMP agents can be reduced, thus facilitating the management of large-scale internetworks.
2-1
error statistics and performance statistics of the network segments to which the ports of the managed network devices are connected. Thus, the NMS can further manage the networks.
Alarm group
RMON alarm management enables monitoring on specific alarm variables (such as the statistics of a port). When the value of a monitored variable exceeds the threshold, an alarm event is generated, which then triggers the network device to act in the way defined in the events. Events are defined in event groups. With an alarm entry defined in an alarm group, a network device performs the following operations accordingly: Sampling the defined alarm variables periodically Comparing the samples with the threshold and triggering the corresponding events if the former exceed the latter
History group
After a history group is configured, the Ethernet switch collects network statistics information periodically and stores the statistics information temporarily for later use. A history group can provide the history data of the statistics on network segment traffic, error packets, broadcast packets, and bandwidth utilization. With the history data management function, you can configure network devices to collect history data, sample and store data of a specific port periodically.
2-2
Statistics group
Statistics group contains the statistics of each monitored port on a switch. An entry in a statistics group is an accumulated value counting from the time when the statistics group is created. The statistics include the number of the following items: collisions, packets with Cyclic Redundancy Check (CRC) errors, undersize (or oversize) packets, broadcast packets, multicast packets, and received bytes and packets. With the RMON statistics management function, you can monitor the use of a port and make statistics on the errors occurred when the ports are being used.
RMON Configuration
Before performing RMON configuration, make sure the SNMP agents are correctly configured. For the information about SNMP agent configuration, refer to section Configuring Basic SNMP Functions. Follow these steps to configure RMON: To do Enter system view Use the command system-view rmon event event-entry [ description string ] { log | trap trap-community | log-trap log-trapcommunity | none } [ owner text ] rmon alarm entry-number alarm-variable sampling-time { delta | absolute } rising_threshold threshold-value1 event-entry1 falling_threshold threshold-value2 event-entry2 [ owner text ] rmon prialarm entry-number prialarm-formula prialarm-des sampling-timer { delta | absolute | changeratio } rising_threshold threshold-value1 event-entry1 falling_threshold threshold-value2 event-entry2 entrytype { forever | cycle cycle-period } [ owner text ] interface interface-type interface-number rmon history entry-number buckets number interval sampling-interval [ owner text ] rmon statistics entry-number [ owner text ] Remarks
Optional
Optional Before adding an alarm entry, you need to use the rmon event command to define the event to be referenced by the alarm entry. Optional Before adding an extended alarm entry, you need to use the rmon event command to define the event to be referenced by the extended alarm entry.
Enter Ethernet port view Add a history entry Add a statistics entry
Optional
Optional
2-3
The rmon alarm and rmon prialarm commands take effect on existing nodes only. For each port, only one RMON statistics entry can be created. That is, if an RMON statistics entry is already created for a given port, you will fail to create another statistics entry with a different index for the same port.
Displaying RMON
To do Display RMON statistics Display RMON history information Display RMON alarm information Display extended RMON alarm information Display RMON events Display RMON event logs Use the command display rmon statistics [ interface-type interface-number | unit unit-number ] display rmon history [ interface-type interface-number | unit unit-number ] display rmon alarm [ entry-number ] display rmon prialarm [ prialarm-entry-number ] display rmon event [ event-entry ] display rmon eventlog [ event-entry ] Available in any view. Remarks
Network diagram
Figure 2-1 Network diagram for RMON configuration
Configuration procedures
# Add the statistics entry numbered 1 to take statistics on GigabitEthernet 1/0/1.
<Sysname> system-view [Sysname] interface GigabitEthernet 1/0/1 [Sysname-GigabitEthernet1/0/1] rmon statistics 1
2-4
[Sysname-GigabitEthernet1/0/1] quit
# Add the event entries numbered 1 and 2 to the event table, which will be triggered by the following extended alarm.
[Sysname] rmon event 1 log [Sysname] rmon event 2 trap 10.21.30.55
# Add an entry numbered 2 to the extended alarm table to allow the system to calculate the alarm variables with the (.1.3.6.1.2.1.16.1.1.1.9.1+.1.3.6.1.2.1.16.1.1.1.10.1) formula to get the numbers of all the oversize and undersize packets received by GigabitEthernet 1/0/1 that are in correct data format and sample it in every 10 seconds. When the change ratio between samples reaches the rising threshold of 50, event 1 is triggered; when the change ratio drops under the falling threshold, event 2 is triggered.
[Sysname] rmon prialarm 2 (.1.3.6.1.2.1.16.1.1.1.9.1+.1.3.6.1.2.1.16.1.1.1.10.1) test 10 changeratio rising_threshold 50 1 falling_threshold 5 2 entrytype forever owner user1
Variable formula : (.1.3.6.1.2.1.16.1.1.1.9.1+.1.3.6.1.2.1.16.1.1.1.10.1) Description Sampling interval Rising threshold Falling threshold When startup enables : test : 10(sec) : 100(linked with event 1) : 10(linked with event 2) : risingOrFallingAlarm
2-5
Table of Contents
1 Multicast Overview 1-1 Multicast Overview 1-1 Information Transmission in the Unicast Mode 1-1 Information Transmission in the Broadcast Mode1-2 Information Transmission in the Multicast Mode1-2 Roles in Multicast 1-3 Common Notations in Multicast1-4 Advantages and Applications of Multicast1-4 Multicast Models 1-5 Multicast Architecture1-5 Multicast Protocols 1-9 Multicast Packet Forwarding Mechanism 1-10 Implementation of the RPF Mechanism 1-11 RPF Check 1-11 2 IGMP Snooping Configuration 2-1 IGMP Snooping Overview2-1 Principle of IGMP Snooping 2-1 Basic Concepts in IGMP Snooping 2-1 Work Mechanism of IGMP Snooping 2-2 IGMP Snooping Configuration 2-4 Enabling IGMP Snooping 2-5 Configuring the Version of IGMP Snooping 2-5 Configuring Timers 2-6 Configuring Fast Leave Processing 2-6 Configuring a Multicast Group Filter2-7 Configuring the Maximum Number of Multicast Groups on a Port2-8 Configuring IGMP Querier2-9 Suppressing Flooding of Unknown Multicast Traffic in a VLAN 2-10 Configuring Static Member Port for a Multicast Group2-10 Configuring a Static Router Port2-11 Configuring a Port as a Simulated Group Member 2-12 Configuring a VLAN Tag for Query Messages 2-13 Configuring Multicast VLAN 2-13 Displaying and Maintaining IGMP Snooping2-15 IGMP Snooping Configuration Examples 2-15 Configuring IGMP Snooping2-15 Configuring Multicast VLAN 2-17 Troubleshooting IGMP Snooping2-20 3 Common Multicast Configuration3-1 Common Multicast Configuration3-1 Configuring a Multicast MAC Address Entry 3-1 Configuring Dropping Unknown Multicast Packets 3-2
i
ii
Multicast Overview
Multicast Overview
With the development of the Internet, more and more interaction services such as data, voice, and video services are running on the network. In addition, highly bandwidth- and time-critical services, such as e-commerce, Web conferencing, online auctions, video on demand (VoD), and tele-education have come into being. These services have higher requirements for information security, legal use of paid services, and network bandwidth. In the network, packets are sent in three modes: unicast, broadcast and multicast. The following sections describe and compare data interaction processes for unicast, broadcast, and multicast traffic.
Assume that Hosts B, D, and E need the information. The source server broadcasts this information through the routers, reaching the targets, but also information. This is an efficient way to send the same content to densely distributed users. However, as we can see from the information transmission process, security and restricted use of paid services cannot be guaranteed. In addition, when only a small number of users on the same network need the information, the utilization ratio of the network resources is very low and the bandwidth resources are greatly wasted.
1-1
Therefore, broadcast is disadvantageous in transmitting data to specific users, and is more bandwidth intensive.
Assume that Hosts B, D, and E need the information. The source server broadcasts this information through routers, and Hosts A and C on the network also receive this information. As we can see from the information transmission process, the security and legal use of paid service cannot be guaranteed. In addition, when only a small number of users on the same network need the information, the utilization ratio of the network resources is very low and the bandwidth resources are greatly wasted. Therefore, broadcast is disadvantageous in transmitting data to specific users; moreover, broadcast occupies large bandwidth.
1-2
Assume that Hosts B, D and E need the information. To transmit the information to the right users, it is necessary to group Hosts B, D and E into a receiver set. The routers on the network duplicate and distribute the information based on the distribution of the receivers in this set. Finally, the information is correctly delivered to Hosts B, D, and E. The advantages of multicast over unicast are as follows: No matter how many receivers exist, there is only one copy of the same multicast data flow on each link. With the multicast mode used to transmit information, an increase of the number of users does not add to the network burden remarkably. The advantages of multicast over broadcast are as follows: A multicast data flow can be sent only to the receiver that requires the data. Multicast brings no waste of network resources and makes proper use of bandwidth.
Roles in Multicast
The following roles are involved in multicast transmission: An information sender is referred to as a multicast source (Source in Figure 1-3). Each receiver is a multicast group member (Receiver in Figure 1-3). All receivers interested in the same information form a multicast group. Multicast groups are not subject to geographic restrictions. A router that supports Layer 3 multicast is called multicast router or Layer 3 multicast device. In addition to providing multicast routing, a multicast router can also manage multicast group members. For a better understanding of the multicast concept, you can assimilate multicast transmission to the transmission of TV programs, as shown in Table 1-1.
1-3
Table 1-1 An analogy between TV transmission and multicast transmission Step 1 2 3 4 TV transmission A TV station transmits a TV program through a television channel. A user tunes the TV set to the channel. The user starts to watch the TV program transmitted by the TV station via the channel. The user turns off the TV set. Multicast transmission A multicast source sends multicast data to a multicast group. A receiver joins the multicast group. The receiver starts to receive the multicast data that the source sends to the multicast group. The receiver leaves the multicast group.
A multicast source does not necessarily belong to a multicast group. Namely, a multicast source is not necessarily a multicast data receiver. A multicast source can send data to multiple multicast groups at the same time, and multiple multicast sources can send data to the same multicast group at the same time.
Application of multicast
The multicast technology effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission, over an IP network, multicast greatly saves network bandwidth and reduces network load. Multicast provides the following applications: Applications of multimedia and flow media, such as Web TV, Web radio, and real-time video/audio conferencing.
1-4
Communication for training and cooperative operations, such as remote education. Database and financial applications (stock), and so on. Any point-to-multiple-point data application.
Multicast Models
Based on the multicast source processing modes, there are three multicast models: Any-Source Multicast (ASM) Source-Filtered Multicast (SFM) Source-Specific Multicast (SSM)
ASM model
In the ASM model, any sender can become a multicast source and send information to a multicast group; numbers of receivers can join a multicast group identified by a group address and obtain multicast information addressed to that multicast group. In this model, receivers are not aware of the position of a multicast source in advance. However, they can join or leave the multicast group at any time.
SFM model
The SFM model is derived from the ASM model. From the view of a sender, the two models have the same multicast group membership architecture. Functionally, the SFM model is an extension of the ASM model. In the SFM model, the upper layer software checks the source address of received multicast packets so as to permit or deny multicast traffic from specific sources. Therefore, receivers can receive the multicast data from only part of the multicast sources. From the view of a receiver, multicast sources are not all valid: they are filtered.
SSM model
In the practical life, users may be interested in the multicast data from only certain multicast sources. The SSM model provides a transmission service that allows users to specify the multicast sources they are interested in at the client side. The radical difference between the SSM model and the ASM model is that in the SSM model, receivers already know the locations of the multicast sources by some means. In addition, the SSM model uses a multicast address range that is different from that of the ASM model, and dedicated multicast forwarding paths are established between receivers and the specified multicast sources.
Multicast Architecture
The purpose of IP multicast is to transmit information from a multicast source to receivers in the multicast mode and to satisfy information requirements of receivers. You should be concerned about: Host registration: What receivers reside on the network? Technologies of discovering a multicast source: Which multicast source should the receivers receive information from? Multicast addressing mechanism: Where should the multicast source transports information? Multicast routing: How is information transported? IP multicast is a kind of peer-to-peer service. Based on the protocol layer sequence from bottom to top, the multicast mechanism contains addressing mechanism, host registration, multicast routing, and multicast application:
1-5
Addressing mechanism: Information is sent from a multicast source to a group of receivers through multicast addresses. Host registration: A receiving host joins and leaves a multicast group dynamically using the membership registration mechanism. Multicast routing: A router or switch transports packets from a multicast source to receivers by building a multicast distribution tree with multicast routes. Multicast application: A multicast source must support multicast applications, such as video conferencing. The TCP/IP protocol suite must support the function of sending and receiving multicast information. Multicast Address As receivers are multiple hosts in a multicast group, you should be concerned about the following questions: What destination should the information source send the information to in the multicast mode? How to select the destination address? These questions are about multicast addressing. To enable the communication between the information source and members of a multicast group (a group of information receivers), network-layer multicast addresses, namely, IP multicast addresses must be provided. In addition, a technology must be available to map IP multicast addresses to link-layer MAC multicast addresses. The following sections describe these two types of multicast addresses:
IP multicast address
Internet Assigned Numbers Authority (IANA) categorizes IP addresses into five classes: A, B, C, D, and E. Unicast packets use IP addresses of Class A, B, and C based on network scales. Class D IP addresses are used as destination addresses of multicast packets. Class D address must not appear in the IP address field of a source IP address of IP packets. Class E IP addresses are reserved for future use. In unicast data transport, a data packet is transported hop by hop from the source address to the destination address. In an IP multicast environment, there are a group of destination addresses (called group address), rather than one address. All the receivers join a group. Once they join the group, the data sent to this group of addresses starts to be transported to the receivers. All the members in this group can receive the data packets. This group is a multicast group. A multicast group has the following characteristics: The membership of a group is dynamic. A host can join and leave a multicast group at any time. A multicast group can be either permanent or temporary. A multicast group whose addresses are assigned by IANA is a permanent multicast group. It is also called reserved multicast group. Note that: The IP addresses of a permanent multicast group keep unchanged, while the members of the group can be changed. There can be any number of, or even zero, members in a permanent multicast group. Those IP multicast addresses not assigned to permanent multicast groups can be used by temporary multicast groups. Class D IP addresses range from 224.0.0.0 to 239.255.255.255. For details, see Table 1-2.
1-6
Table 1-2 Range and description of Class D IP addresses Class D address range Description Reserved multicast addresses (IP addresses for permanent multicast groups). The IP address 224.0.0.0 is reserved. Other IP addresses can be used by routing protocols. Available any-source multicast (ASM) multicast addresses (IP addresses for temporary groups). They are valid for the entire network. Available source-specific multicast (SSM) multicast group addresses. Administratively scoped multicast addresses, which are for specific local use only.
224.0.0.0 to 224.0.0.255
As specified by IANA, the IP addresses ranging from 224.0.0.0 to 224.0.0.255 are reserved for network protocols on local networks. The following table lists commonly used reserved IP multicast addresses: Table 1-3 Reserved IP multicast addresses Class D address range 224.0.0.1 224.0.0.2 224.0.0.3 224.0.0.4 224.0.0.5 224.0.0.6 224.0.0.7 224.0.0.8 224.0.0.9 224.0.0.11 224.0.0.12 224.0.0.13 224.0.0.14 224.0.0.15 224.0.0.16 224.0.0.17 224.0.0.18 224.0.0.19 to 224.0.0.255 Address of all hosts Address of all multicast routers Unassigned Distance vector multicast routing protocol (DVMRP) routers Open shortest path first (OSPF) routers Open shortest path first designated routers (OSPF DR) Shared tree routers Shared tree hosts RIP-2 routers Mobile agents DHCP server/relay agent All protocol independent multicast (PIM) routers Resource reservation protocol (RSVP) encapsulation All core-based tree (CBT) routers The specified subnetwork bandwidth management (SBM) All SBMS Virtual router redundancy protocol (VRRP) Other protocols Description
1-7
Like having reserved the private network segment 10.0.0.0/8 for unicast, IANA has also reserved the network segment 239.0.0.0/8 for multicast. These are administratively scoped addresses. With the administratively scoped addresses, you can define the range of multicast domains flexibly to isolate IP addresses between different multicast domains, so that the same multicast address can be used in different multicast domains without causing collisions.
XXXX XXXX
The high-order four bits of the IP multicast address are 1110, representing the multicast ID. Only 23 bits of the remaining 28 bits are mapped to a MAC address. Thus, five bits of the multicast IP address are lost. As a result, 32 IP multicast addresses are mapped to the same MAC address.
1-8
Multicast Protocols
Generally, we refer to IP multicast working at the network layer as Layer 3 multicast and the corresponding multicast protocols as Layer 3 multicast protocols, which include IGMP, PIM, and MSDP; we refer to IP multicast working at the data link layer as Layer 2 multicast and the corresponding multicast protocols as Layer 2 multicast protocols, which include IGMP Snooping. This section provides only general descriptions about applications and functions of the Layer 2 and Layer 3 multicast protocols in a network. For details about these protocols, refer to the related chapters of this manual.
Receiver
IGMP
IGMP
PIM
PIM MSDP
IGMP
Source
Receiver
1)
Typically, the Internet Group Management Protocol (IGMP) is used between hosts and Layer 3 multicast devices directly connected with the hosts. These protocols define the mechanism of establishing and maintaining group memberships between hosts and Layer 3 multicast devices. 2) Multicast routing protocols
A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain multicast routes and forward multicast packets correctly and efficiently. Multicast routes constitute a loop-free data transmission path from a data source to multiple receivers, namely a multicast distribution tree. In the ASM model, multicast routes come in intra-domain routes and inter-domain routes.
1-9
An intra-domain multicast routing protocol is used to discover multicast sources and build multicast distribution trees within an autonomous system (AS) so as to deliver multicast data to receivers. Among a variety of mature intra-domain multicast routing protocols, protocol independent multicast (PIM) is a popular one. Based on the forwarding mechanism, PIM comes in two modes dense mode (often referred to as PIM-DM) and sparse mode (often referred to as PIM-SM). An inter-domain multicast routing protocol is used for delivery of multicast information between two ASs. So far, mature solutions include multicast source discovery protocol (MSDP). For the SSM model, multicast routes are not divided into inter-domain routes and intra-domain routes. Since receivers know the position of the multicast source, channels established through PIM-SM are sufficient for multicast information transport.
1)
IGMP Snooping
Running on Layer 2 devices, Internet Group Management Protocol Snooping (IGMP Snooping) are multicast constraining mechanisms that manage and control multicast groups by listening to and analyzing IGMP messages exchanged between the hosts and Layer 3 multicast devices, thus effectively controlling the flooding of multicast data in a Layer 2 network. 2) Multicast VLAN
In the traditional multicast-on-demand mode, when users in different VLANs on a Layer 2 device need multicast information, the upstream Layer 3 device needs to forward a separate copy of the multicast data to each VLAN of the Layer 2 device. With the multicast VLAN feature enabled on the Layer 2 device, the Layer 3 multicast device needs to send only one copy of multicast to the multicast VLAN on the Layer 2 device. This avoids waste of network bandwidth and extra burden on the Layer 3 device.
need to forward multicast packets received on one incoming interface to multiple outgoing interfaces. Compared with a unicast model, a multicast model is more complex in the following aspects. In the network, multicast packet transmission is based on the guidance of the multicast forwarding table derived from the unicast routing table or the multicast routing table specially provided for multicast. To process the same multicast information from different peers received on different interfaces of the same device, every multicast packet is subject to a reverse path forwarding (RPF) check on the incoming interface. The result of the RPF check determines whether the packet will be forwarded or discarded. The RPF check mechanism is the basis for most multicast routing protocols to implement multicast forwarding. The RPF mechanism enables multicast devices to forward multicast packets correctly based on the multicast route configuration. In addition, the RPF mechanism also helps avoid data loops caused by various reasons.
RPF Check
The basis for an RPF check is a unicast route. A unicast routing table contains the shortest path to each destination subnet. A multicast routing protocol does not independently maintain any type of unicast route; instead, it relies on the existing unicast routing information in creating multicast routing entries. When performing an RPF check, a router searches its unicast routing table. The specific process is as follows: The router automatically chooses an optimal unicast route by searching its unicast routing table,
1-11
using the IP address of the packet source as the destination address. The outgoing interface in the corresponding routing entry is the RPF interface and the next hop is the RPF neighbor. The router considers the path along which the packet from the RPF neighbor arrived on the RPF interface to be the shortest path that leads back to the source. Assume that unicast routes exist in the network, as shown in Figure 1-7. Multicast packets travel along the SPT from the multicast source to the receivers. Figure 1-7 RPF check process
Switch B Receiver
Vlan-int2 Vlan-int1
Source
192.168.0.1/24
Switch A
Vlan-int1 Vlan-int2
Receiver
Switch C
A multicast packet from Source arrives to VLAN-interface 1 of Switch C, and the corresponding forwarding entry does not exist in the multicast forwarding table of Switch C. Switch C performs an RPF check, and finds in its unicast routing table that the outgoing interface to 192.168.0.0/24 is VLAN-interface 2. This means that the interface on which the packet actually arrived is not the RPF interface. The RPF check fails and the packet is discarded. A multicast packet from Source arrives to VLAN-interface 2 of Switch C, and the corresponding forwarding entry does not exist in the multicast forwarding table of Switch C. The router performs an RPF check, and finds in its unicast routing table that the outgoing interface to 192.168.0.0/24 is the interface on which the packet actually arrived. The RPF check succeeds and the packet is forwarded.
1-12
Multicast router
Layer 2 switch
Layer 2 switch
Host C Receiver
Host C Receiver
2-1
Switch A
Eth1/0/2
Receiver
Eth1/0/3
Host A
Host B
Eth1/0/1
Receiver
Eth1/0/2
Source
Host C
Host D
Ports involved in IGMP Snooping, as shown in Figure 2-2, are described as follows: Router port: A router port is a port on the Layer 3 multicast device (DR or IGMP querier) side of the Ethernet switch. In the figure, Ethernet 1/0/1 of Switch A and Ethernet 1/0/1 of Switch B are router ports. A switch registers all its local router ports in its router port list. Member port: A member port is a port on the multicast group member side of the Ethernet switch. In the figure, Ethernet 1/0/2 and Ethernet 1/0/3 of Switch A and Ethernet 1/0/2 of Switch B are member ports. The switch records all member ports on the local device in the IGMP Snooping forwarding table.
Port aging timers in IGMP Snooping and related messages and actions
Table 2-1 Port aging timers in IGMP Snooping and related messages and actions Timer Description For each router port, the switch sets a timer initialized to the aging time of the route port When a port joins a multicast group, the switch sets a timer for the port, which is initialized to the member port aging time Message before expiry IGMP general query or PIM hello Action after expiry The switch removes this port from its router port list
The switch removes this port from the multicast group forwarding table
2-2
A switch will not forward an IGMP report through a non-router port for the following reason: Due to the IGMP report suppression mechanism, if member hosts of that multicast group still exist under non-router ports, the hosts will stop sending reports when they receive the message, and this prevents the switch from knowing if members of that multicast group are still attached to these ports.
2-3
immediately delete the forwarding entry corresponding to that port from the forwarding table; instead, it resets the aging timer of the member port. Upon receiving the IGMP leave message from a host, the IGMP querier resolves from the message the address of the multicast group that the host just left and sends an IGMP group-specific query to that multicast group through the port that received the leave message. Upon receiving the IGMP group-specific query, a switch forwards it through all the router ports in the VLAN and all member ports of that multicast group, and performs the following to the receiving port: If any IGMP report in response to the group-specific query arrives to the member port before its aging timer expires, this means that some other members of that multicast group still exist under that port: the switch resets the aging timer of the member port. If no IGMP report in response to the group-specific query arrives to the member port before its aging timer expires as a response to the IGMP group-specific query, this means that no members of that multicast group still exist under the port: the switch deletes the forwarding entry corresponding to the port from the forwarding table when the aging timer expires.
After an Ethernet switch enables IGMP Snooping, when it receives the IGMP leave message sent by a host in a multicast group, it judges whether the multicast group exists automatically. If the multicast group does not exist, the switch drops this IGMP leave message.
2-4
Before enabling IGMP Snooping in a VLAN, be sure to enable IGMP Snooping globally in system view; otherwise the IGMP Snooping settings will not take effect. If IGMP Snooping and VLAN VPN are enabled on a VLAN at the same time, IGMP queries are likely to fail to pass the VLAN. You can solve this problem by configuring VLAN tags for queries. For details, see Configuring a VLAN Tag for Query Messages.
2-5
Before configuring related IGMP Snooping functions, you must enable IGMP Snooping in the specified VLAN. Different multicast group addresses should be configured for different multicast sources because IGMPv3 Snooping cannot distinguish multicast data from different sources to the same multicast group.
Configuring Timers
This section describes how to configure the aging timer of the router port, the aging timer of the multicast member ports, and the query response timer. Table 2-5 Configure timers Operation Enter system view Configure the aging timer of the router port Command system-view igmp-snooping router-aging-time seconds Optional By default, the aging time of the router port is 105 seconds. Optional By default, the query response timeout time is 10 seconds. Optional Configure the aging timer of the multicast member port igmp-snooping host-aging-time seconds By default, the aging time of multicast member ports is 260 seconds Remarks
2-6
Remarks
The fast leave processing function works for a port only if the host attached to the port runs IGMPv2 or IGMPv3. The configuration performed in system view takes effect on all ports of the switch if no VLAN is specified; if one or more VLANs are specified, the configuration takes effect on all ports in the specified VLAN(s). The configuration performed in Ethernet port view takes effect on the port no matter which VLAN it belongs to if no VLAN is specified; if one or more VLANs are specified, the configuration takes effect on the port only if the port belongs to the specified VLAN(s).
2-7
A port can belong to multiple VLANs, you can configure only one ACL rule per VLAN on a port. If no ACL rule is configured, all the multicast groups will be filtered. Since most devices broadcast unknown multicast packets by default, this function is often used together with the function of dropping unknown multicast packets to prevent multicast streams from being broadcast as unknown multicast packets to a port blocked by this function. The configuration performed in system view takes effect on all ports of the switch if no VLAN is specified; if one or more VLANs are specified, the configuration takes effect on all ports in the specified VLAN(s). The configuration performed in Ethernet port view takes effect on the port no matter which VLAN it belongs to if no VLAN is specified; if one or more VLANs are specified, the configuration takes effect on the port only if the port belongs to the specified VLAN(s).
2-8
Table 2-10 Configure the maximum number of multicast groups on a port Operation Enter system view Enter Ethernet port view Command system-view interface interface-type interface-number igmp-snooping group-limit limit [ vlan vlan-list [ overflow-replace ] ] Required Limit the number of multicast groups on a port The system default for Switch 4200G series is 256. Remarks
To prevent bursting traffic in the network or performance deterioration of the device caused by excessive multicast groups, you can set the maximum number of multicast groups that the switch should process. When the number of multicast groups exceeds the configured limit, the switch removes its multicast forwarding entries starting from the oldest one. In this case, the multicast packets for the removed multicast group(s) will be flooded in the VLAN as unknown multicast packets. As a result, non-member ports can receive multicast packets within a period of time. To avoid this from happening, enable the function of dropping unknown multicast packets.
Remarks
By default, the interval of sending general queries is 60 seconds. Optional By default, the source IP address of general queries is 0.0.0.0.
If the function of dropping unknown multicast packets is enabled, you cannot enable unknown multicast flooding suppression.
Remarks
Operation Enter Ethernet port view Configure the current port as a static member port for a multicast group in a VLAN
Command interface interface-type interface-number multicast static-group group-address vlan vlan-id Required
Remarks
In VLAN view
Table 2-16 Configure a static router port in VLAN view Operation Enter system view Enter VLAN view Command system-view vlan vlan-id Remarks
2-11
Remarks
Before configuring a simulated host, enable IGMP Snooping in VLAN view first. The port to be configured must belong to the specified VLAN; otherwise the configuration does not take effect. You can use the source-ip source-address command to specify a multicast source address that the port will join as a simulated host. This configuration takes effect when IMGPv3 Snooping is enabled in the VLAN.
2-12
It is not recommended to configure this function while the multicast VLAN function is in effect.
Remarks
Operation Enable IGMP Return to system view Enter Ethernet port view for the Layer 2 switch to be configured Define the port as a trunk or hybrid port
Command Required igmp enable quit interface interface-type interface-number port link-type { trunk | hybrid } port hybrid vlan vlan-id-list { tagged | untagged }
Remarks
By default, the IGMP feature is disabled. Required Required The multicast VLAN defined on the Layer 2 switch must be included, and the port must be configured to forward tagged packets for the multicast VLAN if the port type is hybrid.
Table 2-20 Configure multicast VLAN on the Layer 2 switch Operation Enter system view Enable IGMP Snooping Enter VLAN view Enable IGMP Snooping Enable multicast VLAN Return to system view Enter Ethernet port view for the Layer 3 switch Define the port as a trunk or hybrid port Command system-view igmp-snooping enable vlan vlan-id igmp-snooping enable service-type multicast quit interface interface-type interface-number port link-type { trunk | hybrid } port hybrid vlan vlan-list { tagged | untagged } Required Required Required Required The multicast VLAN must be included, and the port must be configured to forward tagged packets for the multicast VLAN if the port type is hybrid. Required Required Specify the VLANs to be allowed to pass the port port hybrid vlan vlan-id-list { tagged | untagged } The multicast VLAN must be included, and the port must be configured to forward tagged packets for the multicast VLAN. Remarks
Enter Ethernet port view for a user device Define the port as a hybrid port
2-14
One port can belong to only one multicast VLAN. The port connected to a user terminal must be a hybrid port. The multicast member ports must be in the same VLAN with the router port. Otherwise, the multicast member port cannot receive multicast packets. If a router port is in a multicast VLAN, the router port must be configured as a trunk port or a hybrid port that allows tagged packets to pass for the multicast VLAN. Otherwise, all the multicast member ports in this multicast VLAN cannot receive multicast packets. When the multicast VLAN is set up, all IGMP report messages are forwarded to the router ports in the multicast VLAN. If no router ports exist in the multicast VLAN, all IGMP report messages are flooded within the multicast VLAN.
Network diagram
Figure 2-3 Network diagram for IGMP Snooping configuration
Receiver Host A
Source
GE1/0/2 1.1.1.2/24 GE1/0/1 10.1.1.1/24 VLAN100 GE1/0/1 GE1/0/4 GE1/0/3
Receiver
1.1.1.1/24
Switch A
GE1/0/2
Host B
Multicast packets
Host C
Configuration procedure
1) Configure the IP address of each interface
Configure an IP address and subnet mask for each interface as per Figure 2-3. The detailed configuration steps are omitted. 2) Configure Router A
# Enable IP multicast routing, enable PIM-DM on each interface, and enable IGMP on GigabitEthernet1/0/1.
<RouterA> system-view [RouterA] multicast routing-enable [RouterA] interface GigabitEthernet 1/0/1 [RouterA-GigabitEthernet1/0/1] igmp enable [RouterA-GigabitEthernet1/0/1] quit [RouterA] interface GigabitEthernet 1/0/2 [RouterA-GigabitEthernet1/0/2] pim dm [RouterA-GigabitEthernet1/0/2] quit
3)
Configure Switch A
# Create VLAN 100, assign GigabitEthernet1/0/1 through GigabitEthernet1/0/4 to this VLAN, and enable IGMP Snooping in the VLAN.
[SwitchA] vlan 100 [SwitchA-vlan100] port GigabitEthernet 1/0/1 to GigabitEthernet 1/0/4 [SwitchA-vlan100] igmp-snooping enable [SwitchA-vlan100] quit
4)
# View the detailed information of the multicast group in VLAN 100 on Switch A.
<SwitchA> display igmp-snooping group vlan100 Total 1 IP Group(s). Total 1 MAC Group(s).
Vlan(id):100. Total 1 IP Group(s). Total 1 MAC Group(s). Static Router port(s): Dynamic Router port(s): GigabitEthernet1/0/1 IP group(s):the following ip group(s) match to one mac group. IP group address: 224.1.1.1 Static host port(s): Dynamic host port(s): GigabitEthernet1/0/3 MAC group(s): MAC group address: 0100-5e01-0101 Host port(s):GigabitEthernet1/0/3 GigabitEthernet1/0/4 GigabitEthernet1/0/4
As shown above, the multicast group 224.1.1.1 is established on Switch A, with the dynamic router port GigabitEthernet1/0/1 and dynamic member ports GigabitEthernet1/0/3 and GigabitEthernet1/0/4. This means that Host A and Host B have joined the multicast group 224.1.1.1.
Switch A
Layer 3 switch
2-17
Device
Device description
Networking description VLAN 2 contains GigabitEthernet 1/0/1 and VLAN 3 contains GigabitEthernet 1/0/2. The default VLANs of GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 are VLAN 2 and VLAN 3 respectively. VLAN 10 contains GigabitEthernet 1/0/10, GigabitEthernet 1/0/1, and GigabitEthernet 1/0/2. GigabitEthernet 1/0/10 is connected to Switch A. VLAN 10 is a multicast VLAN. GigabitEthernet 1/0/1 sends untagged packets for VLAN 2 and VLAN 10. GigabitEthernet 1/0/2 sends untagged packets for VLAN 3 and VLAN 10. Host A is connected to GigabitEthernet 1/0/1 on Switch B. Host B is connected to GigabitEthernet 1/0/2 on Switch B.
Switch B
Layer 2 switch
Host A Host B
User 1 User 2
In this configuration example, you need to configure the ports that connect Switch A and Switch B to each other as hybrid ports. The following text describes the configuration details. You can also configure these ports as trunk ports. The configuration procedure is omitted here. For details, see Configuring Multicast VLAN. Configure a multicast VLAN, so that users in VLAN 2 and VLAN 3 can receive multicast streams through the multicast VLAN.
Network diagram
Figure 2-4 Network diagram for multicast VLAN configuration
Configuration procedure
The following configuration is based on the prerequisite that the devices are properly connected and all the required IP addresses are already configured. 1) Configure Switch A:
# Set the interface IP address of VLAN 20 to 168.10.1.1 and enable PIM DM on the VLAN interface.
<SwitchA> system-view [SwitchA] multicast routing-enable [SwitchA] vlan 20 [SwitchAvlan20]port GigabitEthernet 1/0/1 [SwitchA-vlan20] quit [SwitchA] interface Vlan-interface 20
2-18
# Define GigabitEthernet 1/0/10 as a hybrid port, add the port to VLAN 10, and configure the port to forward tagged packets for VLAN 10.
[SwitchA] interface GigabitEthernet 1/0/10 [SwitchA-GigabitEthernet1/0/10] port link-type hybrid [SwitchA-GigabitEthernet1/0/10] port hybrid vlan 10 tagged [SwitchA-GigabitEthernet1/0/10] quit
# Configure the interface IP address of VLAN 10 as 168.10.2.1, and enable PIM-DM and IGMP.
[SwitchA] interface Vlan-interface 10 [SwitchA-Vlan-interface10] ip address 168.10.2.1 255.255.255.0 [SwitchA-Vlan-interface10] igmp enable
2)
Configure Switch B:
# Configure VLAN 10 as the multicast VLAN and enable IGMP Snooping on it.
[SwitchB] vlan 10 [SwitchB-vlan10] service-type multicast [SwitchB-vlan10] igmp-snooping enable [SwitchB-vlan10] quit
# Define GigabitEthernet 1/0/10 as a hybrid port, add the port to VLAN 2, VLAN 3, and VLAN 10, and configure the port to forward tagged packets for VLAN 2, VLAN 3, and VLAN 10.
[SwitchB] interface GigabitEthernet 1/0/10 [SwitchB-GigabitEthernet1/0/10] port link-type hybrid [SwitchB-GigabitEthernet1/0/10] port hybrid vlan 2 3 10 tagged [SwitchB-GigabitEthernet1/0/10] quit
# Define GigabitEthernet 1/0/1 as a hybrid port, add the port to VLAN 2 and VLAN 10, configure the port to forward untagged packets for VLAN 2 and VLAN 10, and set VLAN 2 as the default VLAN of the port.
[SwitchB] interface GigabitEthernet 1/0/1 [SwitchB-GigabitEthernet1/0/1] port link-type hybrid [SwitchB-GigabitEthernet1/0/1] port hybrid vlan 2 10 untagged [SwitchB-GigabitEthernet1/0/1] port hybrid pvid vlan 2 [SwitchB-GigabitEthernet1/0/1] quit
# Define GigabitEthernet 1/0/2 as a hybrid port, add the port to VLAN 3 and VLAN 10, configure the port to forward untagged packets for VLAN 3 and VLAN 10, and set VLAN 3 as the default VLAN of the port.
[SwitchB] interface GigabitEthernet 1/0/2 [SwitchB-GigabitEthernet1/0/2] port link-type hybrid [SwitchB-GigabitEthernet1/0/2] port hybrid vlan 3 10 untagged
2-19
2-20
Table 3-2 Configure a multicast MAC address entry in Ethernet port view Operation Enter system view Enter Ethernet port view Command system-view interface interface-type interface-number mac-address multicast mac-address vlan vlan-id Required Create a multicast MAC address entry. The mac-address argument must be a multicast MAC address. Remarks
3-1
If the multicast MAC address entry to be created already exists, the system gives you a prompt. If you want to add a port to a multicast MAC address entry created through the mac-address multicast command, you need to remove the entry first, create this entry again, and then add the specified port to the forwarding ports of this entry. You cannot enable link aggregation on a port on which you have configured a multicast MAC address, and you cannot configure a multicast MAC address on an aggregation port. You cannot configure a multicast MAC address starting with 01005e in an IGMP-Snooping-enabled VLAN. You can do that if IGMP Snooping is not enabled in the VLAN.
3-2
Table of Contents
1 NTP Configuration 1-1 Introduction to NTP 1-1 Applications of NTP 1-1 Implementation Principle of NTP1-2 NTP Implementation Modes1-4 NTP Configuration Task List 1-6 Configuring NTP Implementation Modes 1-6 Configuring NTP Server/Client Mode 1-7 Configuring the NTP Symmetric Peer Mode 1-7 Configuring NTP Broadcast Mode1-8 Configuring NTP Multicast Mode1-9 Configuring Access Control Right 1-10 Configuration Prerequisites 1-10 Configuration Procedure1-10 Configuring NTP Authentication1-11 1.1.1 Configuration Prerequisites 1-11 Configuration Procedure1-12 Configuring Optional NTP Parameters 1-13 Configuring an Interface on the Local Switch to Send NTP Messages 1-14 Configuring the Number of Dynamic Sessions Allowed on the Local Switch1-14 Disabling an Interface from Receiving NTP Messages1-15 Displaying NTP Configuration1-15 Configuration Examples 1-15 Configuring NTP Server/Client Mode 1-15 Configuring NTP Symmetric Peer Mode 1-16 Configuring NTP Broadcast Mode1-18 Configuring NTP Multicast Mode1-19 Configuring NTP Server/Client Mode with Authentication1-21
NTP Configuration
When configuring NTP, go to these sections for information you are interested in: Introduction to NTP NTP Configuration Task List Configuring NTP Implementation Modes Configuring Access Control Right Configuring NTP Authentication Configuring Optional NTP Parameters Displaying NTP Configuration Configuration Examples
Introduction to NTP
Network Time Protocol (NTP) is a time synchronization protocol defined in RFC 1305. It is used for time synchronization between a set of distributed time servers and clients. Carried over UDP, NTP transmits packets through UDP port 123. NTP is intended for time synchronization between all devices that have clocks in a network so that the clocks of all devices can keep consistent. Thus, the devices can provide multiple unified-time-based applications (see section Applications of NTP). A local system running NTP can not only be synchronized by other clock sources, but also serve as a clock source to synchronize other clocks. Besides, it can synchronize, or be synchronized by other systems by exchanging NTP messages.
Applications of NTP
As setting the system time manually in a network with many devices leads to a lot of workload and cannot ensure accuracy, it is unfeasible for an administrator to perform the operation. However, an administrator can synchronize the clocks of devices in a network with required accuracy by performing NTP configuration. NTP is mainly applied to synchronizing the clocks of all devices in a network. For example: In network management, the analysis of the log information and debugging information collected from different devices is meaningful and valid only when network devices that generate the information adopts the same time. The billing system requires that the clocks of all network devices be consistent. Some functions, such as restarting all network devices in a network simultaneously require that they adopt the same time. When multiple systems cooperate to handle a rather complex transaction, they must adopt the same time to ensure a correct execution order. To perform incremental backup operations between a backup server and a host, you must make sure they adopt the same time. NTP has the following advantages:
1-1
Defining the accuracy of clocks by stratum to synchronize the clocks of all devices in a network quickly Supporting access control and MD5 encrypted authentication Sending protocol packets in unicast, multicast, or broadcast mode
The clock stratum determines the accuracy, which ranges from 1 to 16. The stratum of a reference clock ranges from 1 to 15. The clock accuracy decreases as the stratum number increases. A stratum 16 clock is in the unsynchronized state and cannot serve as a reference clock. The local clock of an S4200G Ethernet switch cannot be set as a reference clock. It can serve as a reference clock source to synchronize the clock of other devices only after it is synchronized.
1-2
IP network
1. Device A NTP message 10:00:00 am Device B 11:00:01 am
IP network
2. Device A NTP message 10:00:00 am 11:00:01 am Device B
11:00:02 am
IP network
3. Device A NTP message received at 10:00:03 am Device B
IP network
4. Device A Device B
The procedure of synchronizing the system clock is as follows: Device A sends an NTP message to Device B, with a timestamp 10:00:00 am (T1) identifying when it is sent. When the message arrives at Device B, Device B inserts its own timestamp 11:00:01 am (T2) into the packet. When the NTP message leaves Device B, Device B inserts its own timestamp 11:00:02 am (T3) into the packet. When Device A receives the NTP message, the local time of Device A is 10:00:03am (T4). At this time, Device A has enough information to calculate the following two parameters: Delay for an NTP message to make a round trip between Device A and Device B: Delay = (T4 -T1)-(T3 -T2). Time offset of Device A relative to Device B: Offset = ((T2 -T1) + (T3 -T4))/2. Device A can then set its own clock according to the above information to synchronize its clock to that of Device B. For detailed information, refer to RFC 1305.
1-3
Server/client mode
Figure 1-2 Server/client mode
Network
Clock synchronization request packet In peer mode, both sides can be synchronized to each other Response packet Synchronize
In the symmetric peer mode, the local S4200G Ethernet switch serves as the symmetric-active peer and sends clock synchronization request first, while the remote server serves as the symmetric-passive peer automatically. If both of the peers have reference clocks, the one with a smaller stratum number is adopted.
1-4
Broadcast mode
Figure 1-4 Broadcast mode
Multicast mode
Figure 1-5 Multicast mode
Table 1-1 describes how the above mentioned NTP modes are implemented on 3Com S4200G series Ethernet switches. Table 1-1 NTP implementation modes on 3Com S4200G series Ethernet switches NTP implementation mode Configuration on S4200G series switches Configure the local S4200G Ethernet switch to work in the NTP client mode. In this mode, the remote server serves as the local time server, while the local switch serves as the client. Configure the local S4200G switch to work in NTP symmetric peer mode. In this mode, the remote server serves as the symmetric-passive peer of the S4200G switch, and the local switch serves as the symmetric-active peer. Configure the local S4200G Ethernet switch to work in NTP broadcast server mode. In this mode, the local switch broadcasts NTP messages through the VLAN interface configured on the switch. Configure the S4200G switch to work in NTP broadcast client mode. In this mode, the local S4200G switch receives broadcast NTP messages through the VLAN interface configured on the switch.
Server/client mode
Broadcast mode
1-5
Configuration on S4200G series switches Configure the local S4200G Ethernet switch to work in NTP multicast server mode. In this mode, the local switch sends multicast NTP messages through the VLAN interface configured on the switch. Configure the local S4200G Ethernet switch to work in NTP multicast client mode. In this mode, the local switch receives multicast NTP messages through the VLAN interface configured on the switch.
Multicast mode
When a 3Com S4200G Ethernet switch works in server mode or symmetric passive mode, you need not to perform related configurations on this switch but do that on the client or the symmetric-active peer. The NTP server mode, NTP broadcast mode, or NTP multicast mode takes effect only after the local clock of the 3Com S4200G Ethernet switch has been synchronized. When symmetric peer mode is configured on two Ethernet switches, to synchronize the clock of the two switches, make sure at least one switchs clock has been synchronized.
To protect unused sockets against attacks by malicious users and improve security, 3Com S4200G series Ethernet switches provide the following functions:
1-6
UDP port 123 is opened only when the NTP feature is enabled. UDP port 123 is closed as the NTP feature is disabled. These functions are implemented as follows: Execution of one of the ntp-service unicast-server, ntp-service unicast-peer, ntp-service broadcast-client, ntp-service broadcast-server, ntp-service multicast-client, and ntp-service multicast-server commands enables the NTP feature and opens UDP port 123 at the same time. Execution of the undo form of one of the above six commands disables all implementation modes of the NTP feature and closes UDP port 123 at the same time.
The remote server specified by remote-ip or server-name serves as the NTP server, and the local switch serves as the NTP client. The clock of the NTP client will be synchronized by but will not synchronize that of the NTP server. remote-ip cannot be a broadcast address, a multicast address or the IP address of the local clock. After you specify an interface for sending NTP messages through the source-interface keyword, the source IP address of the NTP message will be configured as the primary IP address of the specified interface. A switch can act as a server to synchronize the clock of other switches only after its clock has been synchronized. If the clock of a server has a stratum level lower than or equal to that of a clients clock, the client will not synchronize its clock to the servers. You can configure multiple servers by repeating the ntp-service unicast-server command. The client will choose the optimal reference source.
1-7
Use the command system-view ntp-service unicast-peer { remote-ip | peer-name } [ authentication-keyid key-id | priority | source-interface Vlan-interface vlan-id | version number ]* Required
Remarks
In the symmetric peer mode, you need to execute the related NTP configuration commands (refer to section Configuring NTP Implementation Modes for details) to enable NTP on a symmetric-passive peer; otherwise, the symmetric-passive peer will not process NTP messages from the symmetric-active peer. The remote device specified by remote-ip or peer-name serves as the peer of the local Ethernet switch, and the local switch works in the symmetric-active mode. In this case, the clock of the local switch and that of the remote device can be synchronized to each other. remote-ip must not be a broadcast address, a multicast address or the IP address of the local clock. After you specify an interface for sending NTP messages through the source-interface keyword, the source IP address of the NTP message will be configured as the IP address of the specified interface. Typically, the clock of at least one of the symmetric-active and symmetric-passive peers should be synchronized first; otherwise the clock synchronization will not proceed. You can configure multiple symmetric-passive peers for the local switch by repeating the ntp-service unicast-peer command. The clock of the peer with the smallest stratum will be chosen to synchronize with the local clock of the switch.
A broadcast server can synchronize broadcast clients only after its clock has been synchronized.
1-8
To do Enter system view Enter VLAN interface view Configure the switch to work in the NTP broadcast server mode
Use the command system-view interface Vlan-interface vlan-id ntp-service broadcast-server [ authentication-keyid key-id | version number ]* Required
Remarks
A multicast server can synchronize multicast clients only after its clock has been synchronized. An S4200G series switch working in the multicast server mode supports up to 1,024 multicast clients.
Remarks
Configuration Prerequisites
Prior to configuring the NTP service access-control right to the local switch for peer devices, you need to create and configure an ACL associated with the access-control right. For the configuration of ACL, refer to ACL Configuration in Security Volume.
Configuration Procedure
Follow these steps to configure the NTP service access-control right to the local device for peer devices: To do Enter system view Use the command system-view Remarks
1-10
To do Configure the NTP service access-control right to the local switch for peer devices
Use the command ntp-service access { peer | server | synchronization | query } acl-number Optional
Remarks
peer by default
The access-control right mechanism provides only a minimum degree of security protection for the local switch. A more secure method is identity authentication.
1-11
In addition, for the server/client mode and the symmetric peer mode, you need to associate a specific key on the client (the symmetric-active peer in the symmetric peer mode) with the corresponding NTP server (the symmetric-passive peer in the symmetric peer mode); for the NTP broadcast/multicast mode, you need to associate a specific key on the broadcast/multicast server with the corresponding NTP broadcast/multicast client. Otherwise, NTP authentication cannot be enabled normally. Configurations on the server and the client must be consistent.
Configuration Procedure
Configuring NTP authentication on the client
Follow these steps to configure NTP authentication on the client: To do Enter system view Enable the NTP authentication function Use the command system-view ntp-service authentication enable ntp-service authentication-keyid key-id authentication-model md5 value ntp-service reliable authentication-keyid key-id ntp-service unicast-server { remote-ip | server-name } authentication-keyid key-id Required Disabled by default. Required By default, no NTP authentication key is configured. Required By default, no trusted key is configured. Remarks
Configure the specified key as a trusted key Associat e the specified key with the correspo nding NTP server Configure on the client in the server/client mode Configure on the symmetric-active peer in the symmetric peer mode
Required For the client in the NTP broadcast/multicast mode, you just need to associate the specified key with the client on the corresponding server.
NTP authentication requires that the authentication keys configured for the server and the client be the same. Besides, the authentication keys must be trusted keys. Otherwise, the clock of the client cannot be synchronized with that of the server.
1-12
Use the command ntp-service authentication enable ntp-service authentication-keyid key-id authentication-mode md5 value Required
Remarks
Configure the specified key as a trusted key Enter VLAN interface view Configure on the NTP broadcast server Associate the specified key with the correspondi ng broadcast/m ulticast client
ntp-service reliable authentication-keyid key-id interface Vlan-interface vlan-id ntp-service broadcast-server authentication-keyid key-id
By default, no trusted authentication key is configured. In NTP broadcast server mode and NTP multicast server mode, you need to associate the specified key with the corresponding broadcast/multicast client You can associate an NTP broadcast/multicast client with an authentication key while configuring NTP mode. You can also use this command to associate them after configuring the NTP mode.
The procedure for configuring NTP authentication on the server is the same as that on the client. Besides, the client and the server must be configured with the same authentication key. In NTP server mode and NTP peer mode, you need to associate the specified key with the corresponding NTP server (symmetric-active peer) on the client (symmetric-passive peer). In these two modes, multiple NTP servers (symmetric-active peers) may be configured for a client/passive peer, and therefore, the authentication key is required to determine which NTP server the local clock is synchronized to.
1-13
Task Configuring an Interface on the Local Switch to Send NTP Messages Configuring the Number of Dynamic Sessions Allowed on the Local Switch Disabling an Interface from Receiving NTP Messages
If you have specified an interface in the ntp-service unicast-server or ntp-service unicast-peer command, this interface will be used for sending NTP messages.
1-14
Configuration Examples
Configuring NTP Server/Client Mode
Network requirements
The local clock of Device A (a switch) is to be used as a master clock, with the stratum level of 2. Device A is used as the NTP server of Device B (an S4200G Ethernet switch) Configure Device B to work in the client mode, and then Device A will automatically work in the server mode.
Network diagram
Figure 1-6 Network diagram for the NTP server/client mode configuration
Configuration procedure
Perform the following configurations on Device B. # View the NTP status of Device B before synchronization.
<DeviceB> display ntp-service status Clock status: unsynchronized Clock stratum: 16
1-15
Reference clock ID: none Nominal frequency: 60.0002 Hz Actual frequency: 60.0002 Hz Clock precision: 2^18 Clock offset: 0.0000 ms Root delay: 0.00 ms Root dispersion: 0.00 ms Peer dispersion: 0.00 ms Reference time: 00:00:00.000 UTC Jan 1 1900 (00000000.00000000)
# (After the above configurations, Device B is synchronized to Device A.) View the NTP status of Device B.
[DeviceB] display ntp-service status Clock status: synchronized Clock stratum: 3 Reference clock ID: 1.0.1.11 Nominal frequency: 60.0002 Hz Actual frequency: 60.0002 Hz Clock precision: 2^18 Clock offset: 0.66 ms Root delay: 27.47 ms Root dispersion: 208.39 ms Peer dispersion: 9.63 ms Reference time: 17:03:32.022 UTC Apr 2 2007 (BF422AE4.05AEA86C)
The above output information indicates that Device B is synchronized to Device A, and the stratum level of its clock is 3, one level lower than that of Device A. # View the information about NTP sessions of Device B. (You can see that Device B establishes a connection with Device A.)
[DeviceB] display ntp-service sessions source reference stra reach poll now offset delay disper
source(master),2 1
source(peer),3
selected,4
candidate,5
associations :
1-16
Network diagram
Figure 1-7 Network diagram for NTP peer mode configuration
Device A
3.0.1.31/24
3.0.1.32/24
3.0.1.33/24
Device B
Device C
Configuration procedure
1) Configure Device C.
2)
Device C and Device B are symmetric peers after the above configuration. Device B works in symmetric active mode, while Device C works in symmetric passive mode. Because the stratum level of the local clock of Device B is 1, and that of Device C is 3, the clock of Device C is synchronized to that of Device B. View the status of Device C after the clock synchronization.
[DeviceC] display ntp-service status Clock status: synchronized Clock stratum: 2 Reference clock ID: 3.0.1.32 Nominal frequency: 60.0002 Hz Actual frequency: 60.0002 Hz Clock precision: 2^18 Clock offset: 0.66 ms Root delay: 27.47 ms Root dispersion: 208.39 ms Peer dispersion: 9.63 ms Reference time: 17:03:32.022 UTC Apr 2 2007 (BF422AE4.05AEA86C)
The output information indicates that the clock of Device C is synchronized to that of Device B and the stratum level of its local clock is 2, one level lower than Device B.
1-17
# View the information about the NTP sessions of Device C (you can see that a connection is established between Device C and Device B).
[DeviceC] display ntp-service sessions source reference stra reach poll now offset delay disper
************************************************************************* [1234]3.0.1.32 [25]3.0.1.31 LOCL 127.127.1.0 1 2 95 1 64 64 42 -14.3 12.9 38.7 2.7 0.0
1 4408.6
Network diagram
Figure 1-8 Network diagram for the NTP broadcast mode configuration
Vlan-int2 3.0.1.31/24
Device C
Vlan-int2 1.0.1.31/24
Device A
Device B
Vlan-int2 3.0.1.32/24
Device D
Configuration procedure
1) Configure Device C.
# Set Device C as the broadcast server, which sends broadcast messages through VLAN-interface 2.
[DeviceC] interface Vlan-interface 2 [DeviceC-Vlan-interface2] ntp-service broadcast-server
2)
1-18
After the above configurations, Device A and Device D will listen to broadcast messages through their own VLAN-interface 2, and Device C will send broadcast messages through VLAN-interface 2. Because Device A and Device C do not share the same network segment, Device A cannot receive broadcast messages from Device C, while Device D is synchronized to Device C after receiving broadcast messages from Device C. View the NTP status of Device D after the clock synchronization.
[DeviceD] display ntp-service status Clock status: synchronized Clock stratum: 3 Reference clock ID: 3.0.1.31 Nominal frequency: 60.0002 Hz Actual frequency: 60.0002 Hz Clock precision: 2^18 Clock offset: 198.7425 ms Root delay: 27.47 ms Root dispersion: 208.39 ms Peer dispersion: 9.63 ms Reference time: 17:03:32.022 UTC Apr 2 2007 (BF422AE4.05AEA86C)
The output information indicates that Device D is synchronized to Device C, with the clock stratum level of 3, one level lower than that of Device C. # View the information about the NTP sessions of Device D and you can see that a connection is established between Device D and Device C.
[DeviceD] display ntp-service sessions source reference stra reach poll now offset delay disper
************************************************************************** [1234]3.0.1.31 note: 1 127.127.1.0 2 1 64 377 26.1 199.53 9.7 configured Total
source(master),2 1
source(peer),3
selected,4
candidate,5
associations :
1-19
Network diagram
Figure 1-9 Network diagram for NTP multicast mode configuration
Vlan-int2 3.0.1.31/24
Device C
Vlan-int2 1.0.1.31/24
Device A
Device B
Vlan-int2 3.0.1.32/24
Device D
Configuration procedure
1) Configure Device C.
2)
After the above configurations, Device A and Device D respectively listen to multicast messages through their own VLAN-interface 2, and Device C advertises multicast messages through VLAN-interface 2. Because Device A and Device C do not share the same network segment, Device A cannot receive multicast messages from Device C, while Device D is synchronized to Device C after receiving multicast messages from Device C. View the NTP status of Device D after the clock synchronization.
[DeviceD] display ntp-service status Clock status: synchronized Clock stratum: 3 Reference clock ID: 3.0.1.31 Nominal frequency: 60.0002 Hz Actual frequency: 60.0002 Hz Clock precision: 2^18 Clock offset: 198.7425 ms Root delay: 27.47 ms
1-20
Root dispersion: 208.39 ms Peer dispersion: 9.63 ms Reference time: 17:03:32.022 UTC Apr 2 2007 (BF422AE4.05AEA86C)
The output information indicates that Device D is synchronized to Device C, with a clock stratum level of 3, one stratum level lower than that Device C. # View the information about the NTP sessions of Device D (you can see that a connection is established between Device D and Device C).
[DeviceD] display ntp-service sessions source reference stra reach poll now offset delay disper
************************************************************************** [1234]3.0.1.31 note: 1 127.127.1.0 2 1 64 377 26.1 199.53 9.7 configured Total
source(master),2 1
source(peer),3
selected,4
candidate,5
associations :
Network diagram
Figure 1-10 Network diagram for NTP server/client mode with authentication configuration
Configuration procedure
1) Configure Device B.
# Configure an MD5 authentication key, with the key ID being 42 and the key being aNiceKey.
[DeviceB] ntp-service authentication-keyid 42 authentication-mode md5 aNiceKey
# Associate the trusted key with the NTP server (Device A).
[DeviceB] ntp-service unicast-server 1.0.1.11 authentication-keyid 42
1-21
After the above configurations, Device B is ready to synchronize with Device A. Because the NTP authentication function is not enabled on Device A, the clock of Device B will fail to be synchronized to that of Device A. 2) To synchronize Device B, you need to perform the following configurations on Device A.
# Configure an MD5 authentication key, with the key ID being 42 and the key being aNiceKey.
[DeviceA] ntp-service authentication-keyid 42 authentication-mode md5 aNiceKey
(After the above configurations, the clock of Device B can be synchronized to that of Device A.) View the status of Device B after synchronization.
[DeviceB] display ntp-service status Clock status: synchronized Clock stratum: 3 Reference clock ID: 1.0.1.11 Nominal frequence: 60.0002 Hz Actual frequence: 60.0002 Hz Clock precision: 2^18 Clock offset: 0.66 ms Root delay: 27.47 ms Root dispersion: 208.39 ms Peer dispersion: 9.63 ms Reference time: 17:03:32.022 UTC Apr 2 2007 (BF422AE4.05AEA86C)
The output information indicates that the clock of Device B is synchronized to that of Device A, with a clock stratum level of 3, one stratum level lower than that Device A. # View the information about NTP sessions of Device B (you can see that a connection is established between Device B and Device A).
<DeviceB> display ntp-service sessions source reference stra reach poll now offset delay disper [12345]
1-22
Table of Contents
1 SSH Configuration1-1 SSH Overview1-1 Introduction to SSH 1-1 Algorithm and Key 1-1 SSH Operating Process 1-2 SSH Server and Client 1-4 Configuring the SSH Server1-5 Configuring the User Interfaces for SSH Clients1-6 Configuring the SSH Management Functions1-7 Configuring the SSH Server to Be Compatible with SSH1 Clients 1-8 Configuring Key Pairs1-8 Creating an SSH User and Specifying an Authentication Type 1-9 Specifying a Service Type for an SSH User on the Server1-11 Configuring the Public Key of a Client on the Server 1-12 Assigning a Public Key to an SSH User1-12 Exporting the Host Public Key to a File 1-13 Configuring the SSH Client 1-14 SSH Client Configuration Task List 1-14 Configuring an SSH Client that Runs SSH Client Software 1-14 Configuring an SSH Client Assumed by an SSH2-Capable Switch1-20 Displaying and Maintaining SSH Configuration 1-23 Comparison of SSH Commands with the Same Functions 1-24 SSH Configuration Examples 1-25 When Switch Acts as Server for Local Password Authentication 1-25 When Switch Acts as Server for Password and RADIUS Authentication 1-27 When Switch Acts as Server for Password and HWTACACS Authentication 1-32 When Switch Acts as Server for Publickey Authentication 1-34 When Switch Acts as Client for Password Authentication 1-40 When Switch Acts as Client for Publickey Authentication1-41 When Switch Acts as Client and First-Time Authentication is not Supported1-44
SSH Configuration
When configuring SSH, go to these sections for information you are interested: SSH Overview SSH Server and Client Displaying and Maintaining SSH Configuration Comparison of SSH Commands with the Same Functions SSH Configuration Examples
SSH Overview
Introduction to SSH
Secure Shell (SSH) is a protocol that provides secure remote login and other security services in insecure network environments, allowing for secure access to the Command Line Interface (CLI) of a switch for configuration and management. In an SSH connection, data are encrypted before being sent out and decrypted after they reach the destination. This prevents attacks such as plain text password interception. SSH also provides powerful user authentication functions that prevent attacks such as DNS and IP spoofing. Besides, SSH can also provide data compression to increase transmission speed, take the place of Telnet and provide a secure channel for transfers using File Transfer Protocol FTP . SSH adopts the client-server model. The switch can be configured as an SSH client, an SSH server, or both at the same time. As an SSH server, the switch provides secure connections to multiple clients. As an SSH client, the switch allows the remote server to establish a secure SSH connection for remote login.
1-1
The same key is used for both encryption and decryption. Supported symmetric key algorithms include DES, 3DES, and AES, which can effectively prevent data eavesdropping. Asymmetric key algorithm Asymmetric key algorithm is also called public key algorithm. Both ends have their own key pair, consisting of a private key and a public key. The private key is kept secret while the public key may be distributed widely. The private key cannot be practically derived from the public key. The information encrypted with the public key/private key can be decrypted only with the corresponding private key/public key. Asymmetric key algorithm encrypts data using the public key and decrypts the data using the private key, thus ensuring data security. You can also use the asymmetric key algorithm for data signature. For example, user 1 adds his signature to the data using the private key, and then sends the data to user 2. User 2 verifies the signature using the public key of user 1. If the signature is correct, this means that the data originates from user 1. Both Revest-Shamir-Adleman Algorithm (RSA) and Digital Signature Algorithm (DSA) are asymmetric key algorithms. RSA is used for data encryption and signature, whereas DSA is used for adding signature. Currently the switch supports RSA and DSA.
Symmetric key algorithms are used for encryption and decryption of the data transferred on the SSH channel while asymmetric key algorithms are used for digital signature and identity authentication.
1-2
Currently, the switch that serves as an SSH server supports two SSH versions: SSH2 and SSH1, and the switch that serves as an SSH client supports only SSH2. Unless otherwise noted, SSH refers to SSH2 throughout this document.
Version negotiation
The server opens port 22 to listen to connection requests from clients. The client sends a TCP connection request to the server. After the TCP connection is established, the server sends the first packet to the client, which includes a version identification string in the format of SSH-<primary protocol version number>.<secondary protocol version number>-<software version number>. The primary and secondary protocol version numbers constitute the protocol version number, while the software version number is used for debugging. The client receives and resolves the packet. If the protocol version of the server is lower but supportable, the client uses the protocol version of the server; otherwise, the client uses its own protocol version. The client sends to the server a packet that contains the number of the protocol version it decides to use. The server compares the version carried in the packet with that of its own to determine whether it can cooperate with the client. If the negotiation is successful, the server and the client go on to the key and algorithm negotiation. If not, the server breaks the TCP connection.
Key negotiation
The server and the client send algorithm negotiation packets to each other, which contain public key algorithm lists supported by the server and the client, encrypted algorithm list, message authentication code (MAC) algorithm list, and compressed algorithm list. The server and the client calculate the final algorithm according to the algorithm lists supported. The server and the client generate the session key and session ID based on the Diffie-Hellman (DH) exchange algorithm and the host key pair. Then, the server and the client get the same session key and use it for data encryption and decryption to secure data communication.
Authentication negotiation
The negotiation steps are as follows: The client sends an authentication request to the server. The authentication request contains username, authentication type, and authentication-related information. For example, if the authentication type is password, the content is the password.
1-3
The server starts to authenticate the user. If authentication fails, the server sends an authentication failure message to the client, which contains the list of methods used for a new authentication process. The client selects an authentication type from the method list to perform authentication again. The above process repeats until the authentication succeeds, or the connection is torn down when the authentication times reach the upper limit. SSH provides two authentication methods: password authentication and publickey authentication. In password authentication, the client encrypts the username and password, encapsulates them into a password authentication request, and sends the request to the server. Upon receiving the request, the server decrypts the username and password, compares them with those it maintains, and then informs the client of the authentication result. The publickey authentication method authenticates clients using digital signatures. Currently, the device supports two publickey algorithms to implement digital signatures: RSA and DSA. The client sends to the server a publickey authentication request containing its user name, public key and algorithm. The server verifies the public key. If the public key is invalid, the authentication fails; otherwise, the server generates a digital signature to authenticate the client, and then sends back a message to inform the success or failure of the authentication.
Session request
After passing authentication, the client sends a session request to the server, while the server listens to and processes the request from the client. If the client passes authentication, the server sends back to the client an SSH_SMSG_SUCCESS packet and goes on to the interactive session stage with the client. Otherwise, the server sends back to the client an SSH_SMSG_FAILURE packet, indicating that the processing fails or it cannot resolve the request. The client sends a session request to the server, which processes the request and establishes a session.
Data exchange
In this stage, the server and the client exchanges data in this way: The client encrypts and sends the command to be executed to the server. The server decrypts and executes the command, and then encrypts and sends the result to the client. The client decrypts and displays the result on the terminal.
1-4
Configure the devices accordingly This document describes two cases: The 3Com switch acts as the SSH server to cooperate with software that supports the SSH client functions. The 3Com switch acts as the SSH server to cooperate with another 3Com switch that acts as an SSH client. Complete the following tasks to configure the SSH server and clients: Server Client Software that supports the SSH client functions Another 3Com switch Server side configuration Configuring the SSH Server Configuring the SSH Server Client side configuration Configuring an SSH Client that Runs SSH Client Software Configuring an SSH Client Assumed by an SSH2-Capable Switch
An 3Com switch
An 3Com switch
An SSH server forms a secure connection with each SSH client. The following describe steps for configuring an SSH client and an SSH server to form an SSH connection in between. If multiple SSH servers need to form connections with multiple SSH clients, configure each client and each server accordingly.
Task Configuring the User Interfaces for SSH Clients Preparation Configuring the SSH Management Functions Optional Optional Version Configuring the SSH Server to Be Compatible with SSH1 Clients Required
Remarks
This task determines which SSH versions the server should support. By default, the SSH server is compatible with SSH1 clients.
Key Authentication
Configuring Key Pairs Creating an SSH User and Specifying an Authentication Type Specifying a Service Type for an SSH User on the Server
Required Required Optional By default, an SSH user can use the service type of stelnet. Not necessary when the authentication mode is password. Required when the authentication mode is publickey. Not necessary when the authentication mode is password. Required when the authentication mode is publickey. Optional If a client does not support first-time authentication, you need to export the servers public key and configure the key on the client.
Authorization
Data exchange
The SSH server needs to cooperate with an SSH client to complete the interactions between them. For SSH client configuration, refer to Configuring the SSH Client.
1-6
Remarks
supported
If you have configured a user interface to support SSH protocol, you must configure AAA authentication for the user interface by using the authentication-mode scheme command to ensure successful login. On a user interface, if the authentication-mode password or authentication-mode none command has been executed, the protocol inbound ssh command is not available. Similarly, if the protocol inbound ssh command has been executed, the authentication-mode password and authentication-mode none commands are not available.
1-7
Use the command... ssh-server source-ip ip-address ssh-server source-interface interface-type interface-number Optional
Remarks
You can configure a login header only when the service type is stelnet. For configuration of service types, refer to Specifying a Service Type for an SSH User on the Server For details of the header command, refer to the corresponding section in Login Command.
1-8
To do...
Remarks
Generate an RSA key pairs Generate key pair(s) Generate a DSA key pair
public-key local create rsa Required By default, no key pairs are generated. public-key local create dsa
The command for generating a key pair can survive a reboot. You only need to configure it once. It takes more time to encrypt and decrypt data with a longer key, which, however, ensures higher security. Therefore, specify the length of the key pair accordingly. Some third-party software, for example, WinSCP, requires that the modulo of a public key must be greater than or equal to 768. Therefore, a local key pair of more than 768 bits is recommended.
1-9
SSH uses the authentication function of AAA to authenticate the password of the user that is logging in. Based on the AAA authentication scheme, password authentication can be done locally or remotely. For local authentication, the SSH server saves the user information and implements the authentication. For remote authentication, the user information is saved on an authentication server (such as a RADIUS server) and authentication is implemented through the cooperation of the SSH server and the authentication server. For AAA details, refer to AAA Operation. Publickey authentication Publickey authentication provides more secure SSH connections than password authentication does. At present, the device supports RSA and DSA for publickey authentication. After configuration, authentication is implemented automatically without asking you to enter the password. In this mode, you need to create a key pair on each client, and configure each client's public key on the server. This may be complicated when multiple SSH clients want to access one SSH server in the network. Password-publickey authentication An SSH user must pass both types of authentication before logging in. In this mode, you do not need to create a key pair on each client. You can configure the clients to use the same key pair that is created on one client for publickey authentication. With the AAA function in password authentication, the level of commands available to a logged-in SSH user is determined by the AAA scheme.. Follow these steps to configure an SSH user and specify an authentication type for the user: To do... Enter system view Use the command... system-view
ssh authentication-type default { all | password | password-publickey | publickey }
Remarks Use either command. By default, no SSH user is created and no authentication type is specified. Note that: If both commands are used and different authentication types are specified, the authentication type specified with the ssh user authentication-type command takes precedence.
1-10
For password authentication type, the username argument must be consistent with the valid user name defined in AAA; for publickey authentication, the username argument is the SSH local user name, so that there is no need to configure a local user in AAA. If the default authentication type for SSH users is password and local AAA authentication is adopted, you need not use the ssh user command to create an SSH user. Instead, you can use the local-user command to create a user name and its password and then set the service type of the user to SSH. If the default authentication type for SSH users is password and remote authentication (RADIUS authentication, for example) is adopted, you need not use the ssh user command to create an SSH user, because it is created on the remote server. And the user can use its username and password configured on the remote server to access the network. Under the publickey authentication mode, the level of commands available to a logged-in SSH user can be configured using the user privilege level command on the server, and all the users with this authentication mode will enjoy this level. Under the password or password-publickey authentication mode, the level of commands available to a logged-in SSH user is determined by the AAA scheme. Meanwhile, for different users, the available levels of commands are also different. Under the all authentication mode, the level of commands available to a logged-in SSH user is determined by the actual authentication method used for the user.
If the ssh user service-type command is executed with a username that does not exist, the system will automatically create the SSH user. However, the user cannot log in unless you specify an authentication type for it.
1-11
This configuration is not necessary if the password authentication mode is configured for SSH users.
With the publickey authentication mode configured for an SSH client, you must configure the clients RSA or DSA host public key(s) on the server for authentication. You can manually configure the public key or import it from a public key file. In the former case, you can manually copy the clients public key to the server. In the latter case, the system automatically converts the format of the public key generated by the client to complete the configuration on the server, but the clients public key should be transferred from the client to the server beforehand through FTP/TFTP. Follow these steps to configure the public key of a client manually: To do... Enter system view Enter public key view Enter public key edit view Use the command... system-view public-key peer keyname public-key-code begin Required When you input the key, spaces are allowed between the characters you input (because the system can remove the spaces automatically); you can also press Enter to continue your input at the next line. But the key you input should be a hexadecimal digit string coded in the public key format. Remarks
Return to public key view from public key edit view Exit public key view and return to system view
Follow these steps to import the public key from a public key file: To do... Enter system view Import the public key from a public key file Use the command... system-view public-key peer keyname import sshkey filename Required Remarks
1-12
This configuration task is unnecessary if the SSH users authentication mode is password.
For the publickey authentication mode, you must specify the clients public key on the server for authentication. Follow these steps to assign a public key for an SSH user: To do... Enter system view Use the command... system-view Required Assign a public key to an SSH user ssh user username assign publickey keyname If you issue this command multiple times, the last command overrides the previous ones. Remarks
Follow these steps to export the DSA host public key: To do... Enter system view Export the DSA host public key to a specified file Use the command... system-view public-key local export dsa { openssh | ssh2 } [ filename ] Required Remarks
1-13
With the filename argument specified, you can export the RSA or DSA host public key to a file so that you can configure the key at a remote end by importing the file. If the filename argument is not specified, this command displays the host public key information on the screen in a specified format. The RSA host public key format can be SSH1, SSH2 and OpenSSH, while the DSA host public key format can be SSH2 and OpenSSH. DSA does not support the format of SSH1.
The authentication mode is password The authentication mode is publickey Whether first-authentication is supported
1-14
Task Opening an SSH connection with password authentication Opening an SSH connection with publickey authentication
Remarks Required for password authentication; unnecessary for publickey authentication Required for publickey authentication; unnecessary for password authentication
For putty, it is recommended to use PuTTY release 0.53; PuTTY release 0.58 is also supported. For OpenSSH, it is recommended to use OpenSSH_3.1p1; OpenSSH_4.2p1 is also supported. Any other version or other client, please be careful to use. Selecting the protocol for remote connection as SSH. Usually, a client can use a variety of remote connection protocols, such as Telnet, Rlogin, and SSH. To establish an SSH connection, you must select SSH Selecting the SSH version. Since the device supports SSH2.0 now, select 2.0 or lower for the client. Specifying the private key file. On the server, if public key authentication is enabled for an SSH user and a public key is set for the user, the private key file corresponding to the public key must be specified on the client. RSA key pairs and DSA key pairs are generated by a tool of the client software.
The following takes the client software of PuTTY Version 0.58 as an example to illustrate how to configure the SSH client:
1-15
Note that while generating the key pair, you must move the mouse continuously and keep the mouse off the green process bar in the blue box of shown in Figure 1-4. Otherwise, the process bar stops moving and the key pair generating process is stopped. Figure 1-4 Generate the client keys (2)
1-16
After the key pair is generated, click Save public key and enter the name of the file for saving the public key (public in this case) to save the public key. Figure 1-5 Generate the client keys (3)
Likewise, to save the private key, click Save private key. A warning window pops up to prompt you whether to save the private key without any precaution. Click Yes and enter the name of the file for saving the private key (private in this case) to save the private key. Figure 1-6 Generate the client keys (4)
To generate RSA public key in PKCS format, run SSHKEY.exe, click Browse and select the public key file, and then click Convert.
1-17
1-18
In the Host Name (or IP address) text box, enter the IP address of the server. Note that there must be a route available between the IP address of the server and the client.
Some SSH client software, for example, Tectia client software, supports the DES algorithm only when the ssh1 version is selected. The PuTTY client software supports DES algorithm negotiation ssh2.
Click Browse to bring up the file selection window, navigate to the private key file and click Open. If the connection is normal, a user will be prompted for a username. Once passing the authentication, the user can log in to the server.
1-20
Follow these steps to disable first-time authentication support: To do... Enter system view Disable first-time authentication support Use the command... system-view Required undo ssh client first-time By default, the client is enabled to run first-time authentication. Required Configure server public key Refer to Configuring the Public Key of a Client on the Server The method of configuring server public key on the client is similar to that of configuring client public key on the server. Required Remarks
1-21
With first-time authentication enabled, an SSH client that is not configured with the SSH server's host public key saves the host public key sent by the server without authenticating the server. Attackers may exploit the vulnerability to initiate man-in-middle attacks by acting as an SSH server. Therefore, it is recommended to disable first-time authentication unless you are sure that the SSH server is reliable.
1-22
To do...
Remarks
ssh2 { host-ip | host-name } [ port-num ] [ identity-key { dsa | rsa } | prefer_kex { dh_group1 | dh_exchange_group } | prefer_ctos_cipher { 3des | des | aes128 } | prefer_stoc_cipher { 3des | des | aes128 } | prefer_ctos_hmac { sha1 | sha1_96 | md5 | md5_96 } | prefer_stoc_hmac { sha1 | sha1_96 | md5 | md5_96 } ] *
In this command, you can also specify the preferred key exchange algorithm, encryption algorithms and HMAC algorithms between the server and client. HMAC: Hash-based message authentication code Note that: The identity-key keyword is unnecessary in password authentication and optional in public key authentication. Support for the 3des keyword depends on the number of encryption bits of the software version. The 168-bit version supports this keyword, while the 56-bit version does not.
When logging into the SSH server using public key authentication, an SSH client needs to read its local private key for authentication. As two algorithms (RSA or DSA) are available, the identity-key keyword must be used to specify one algorithm in order to get the correct private key.
user-information
1-23
To do... Display the mappings between host public keys and SSH servers saved on a client Display the current source IP address or the IP address of the source interface specified for the SSH Client.
Remarks
1-24
After RSA key pairs are generated, the display rsa local-key-pair public command displays two public keys (the host public key and server public key) when the switch is working in SSH1-compatible mode, but only one public key (the host public key) when the switch is working in SSH2 mode. The results of the display rsa local-key-pair public command or the public key converted with the SSHKEY tool contains no information such as the authentication type, so they cannot be directly used as parameters in the public-key peer command. For the same reason, neither can the results of the display public-key local rsa public command be used in the rsa peer-public-key command directly.
Network diagram
Figure 1-11 Switch acts as server for local password authentication
Configuration procedure
Configure the SSH server # Create a VLAN interface on the switch and assign an IP address, which the SSH client will use as the destination for SSH connection.
<Switch> system-view [Switch] interface vlan-interface 1 [Switch-Vlan-interface1] ip address 192.168.0.1 255.255.255.0 [Switch-Vlan-interface1] quit
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
1-25
# Create local client client001, and set the authentication password to abc, protocol type to SSH, and command privilege level to 3 for the client.
[Switch] local-user client001 [Switch-luser-client001] password simple abc [Switch-luser-client001] service-type ssh level 3 [Switch-luser-client001] quit
Configure the SSH client # Configure an IP address (192.168.0.2 in this case) for the SSH client. This IP address and that of the VLAN interface on the switch must be in the same network segment. # Configure the SSH client software to establish a connection to the SSH server. Take SSH client software Putty (version 0.58) as an example: 1) Run PuTTY.exe to enter the following configuration interface.
1-26
In the Host Name (or IP address) text box, enter the IP address of the SSH server. 2) From the category on the left pane of the window, select SSH under Connection. The window as shown in Figure 1-13 appears. Figure 1-13 SSH client configuration interface (2)
Under Protocol options, select 2 from Preferred SSH protocol version. 3) As shown in Figure 1-13, click Open. If the connection is normal, you will be prompted to enter the user name client001 and password abc. Once authentication succeeds, you will log in to the server.
1-27
Network diagram
Figure 1-14 Switch acts as server for password and RADIUS authentication
Configuration procedure
4) Configure the RADIUS server
This document takes CAMS Version 2.10 as an example to show the basic RADIUS server configurations required.
# Add an access device. Log in to the CAMS management platform and select System Management > System Configuration from the navigation tree. In the System Configuration page, click Modify of the Access Device item, and then click Add to enter the Add Access Device page and perform the following configurations: Specify the IP address of the switch as 192.168.1.70. Set both the shared keys for authentication and accounting packets to expert. Select LAN Access Service as the service type. Specify the ports for authentication and accounting as 1812 and 1813 respectively. Select Extensible Protocol as the protocol type. Select Standard as the RADIUS packet type.
1-28
# Add a user account for device management. From the navigation tree, select User Management > User for Device Management, and then in the right pane, click Add to enter the Add Account page and perform the following configurations: Add a user named hello, and specify the password. Select SSH as the service type. Specify the IP address range of the hosts to be managed. Figure 1-16 Add an account for device management
5)
# Create a VLAN interface on the switch and assign it an IP address. This address will be used as the IP address of the SSH server for SSH connections.
<Switch> system-view [Switch] interface vlan-interface 2 [Switch-Vlan-interface2] ip address 192.168.1.70 255.255.255.0 [Switch-Vlan-interface2] quit
1-29
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
# Configure an SSH user, specifying the switch to perform password authentication for the user.
[Switch] ssh user hello authentication-type password
6)
# Configure an IP address (192.168.1.1 in this case) for the SSH client. This IP address and that of the VLAN interface on the switch must be in the same network segment. # Configure the SSH client software to establish a connection to the SSH server. Take SSH client software Putty Version 0.58 as an example: Run PuTTY.exe to enter the following configuration interface.
1-30
In the Host Name (or IP address) text box, enter the IP address of the SSH server. From the category on the left pane of the window, select Connection > SSH. The window as shown in Figure 1-18 appears. Figure 1-18 SSH client configuration interface (2)
Under Protocol options, select 2 from Preferred SSH protocol version. Then, click Open. If the connection is normal, you will be prompted to enter the user name hello and the password. Once
1-31
authentication succeeds, you will log in to the server. The level of commands that you can access after login is authorized by the CAMS server. You can specify the level by setting the EXEC Privilege Level argument in the Add Account window shown in Figure 1-16.
Network diagram
Figure 1-19 Switch acts as server for password and HWTACACS authentication
Configuration procedure
Configure the SSH server # Create a VLAN interface on the switch and assign it an IP address. This address will be used as the IP address of the SSH server for SSH connections.
<Switch> system-view [Switch] interface vlan-interface 2 [Switch-Vlan-interface2] ip address 192.168.1.70 255.255.255.0 [Switch-Vlan-interface2] quit
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
1-32
# Configure an SSH user, specifying the switch to perform password authentication for the user.
[Switch] ssh user client001 authentication-type password
Configure the SSH client # Configure an IP address (192.168.1.1 in this case) for the SSH client. This IP address and that of the VLAN interface on the switch must be in the same network segment. # Configure the SSH client software to establish a connection to the SSH server. Take SSH client software Putty Version 0.58 as an example: 1) Run PuTTY.exe to enter the following configuration interface.
In the Host Name (or IP address) text box, enter the IP address of the SSH server.
1-33
2)
From the category on the left pane of the window, select Connection > SSH. The window as shown in Figure 1-21 appears.
Under Protocol options, select 2 from Preferred SSH protocol version. Then, click Open. If the connection is normal, you will be prompted to enter the user name client001 and the password. Once authentication succeeds, you will log in to the server. The level of commands that you can access after login is authorized by the HWTACACS server. For authorization configuration of the HWTACACS server, refer to relevant HWTACACS server configuration manuals.
Network diagram
Figure 1-22 Switch acts as server for publickey authentication
1-34
Configuration procedure
Under the publickey authentication mode, either the RSA or DSA public key can be generated for the server to authenticate the client. Here takes the RSA public key as an example.
Configure the SSH server # Create a VLAN interface on the switch and assign an IP address, which the SSH client will use as the destination for SSH connection.
<Switch> system-view [Switch] interface vlan-interface 1 [Switch-Vlan-interface1] ip address 192.168.0.1 255.255.255.0 [Switch-Vlan-interface1] quit
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
# Configure the authentication type of the SSH client named client 001 as publickey.
[Switch] ssh user client001 authentication-type publickey
Before performing the following steps, you must generate an RSA public key pair (using the client software) on the client, save the key pair in a file named public, and then upload the file to the SSH server through FTP or TFTP. For details, refer to the SSH client configuration part. .
1-35
# Import the clients public key named Switch001 from file public.
[Switch] public-key peer Switch001 import sshkey public
Configure the SSH client (taking PuTTY version 0.58 as an example) # Generate an RSA key pair. 1) Run PuTTYGen.exe, choose SSH2(RSA) and click Generate.
While generating the key pair, you must move the mouse continuously and keep the mouse off the green process bar shown in Figure 1-24. Otherwise, the process bar stops moving and the key pair generating process is stopped.
1-36
After the key pair is generated, click Save public key and enter the name of the file for saving the public key (public in this case). Figure 1-25 Generate a client key pair (3)
1-37
Likewise, to save the private key, click Save private key. A warning window pops up to prompt you whether to save the private key without any protection. Click Yes and enter the name of the file for saving the private key (private.ppk in this case). Figure 1-26 Generate a client key pair (4)
After a public key pair is generated, you need to upload the pubic key file to the server through FTP or TFTP, and complete the server end configuration before you continue to configure the client.
# Establish a connection with the SSH server 2) Launch PuTTY.exe to enter the following interface.
In the Host Name (or IP address) text box, enter the IP address of the server. 3) From the category on the left pane of the window, select SSH under Connection. The window as shown in Figure 1-28 appears.
1-38
Under Protocol options, select 2 from Preferred SSH protocol version. 4) Select Connection/SSH/Auth. The following window appears.
1-39
Click Browse to bring up the file selection window, navigate to the private key file and click OK. 5) From the window shown in Figure 1-29, click Open. If the connection is normal, you will be prompted to enter the username.
Network diagram
Figure 1-30 Switch acts as client for password authentication
Configuration procedure
Configure Switch B # Create a VLAN interface on the switch and assign an IP address, which the SSH client will use as the destination for SSH connection.
<SwitchB> system-view [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] ip address 10.165.87.136 255.255.255.0 [SwitchB-Vlan-interface1] quit
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
# Create local user client001, and set the authentication password to abc, the login protocol to SSH, and user command privilege level to 3.
1-40
[SwitchB] local-user client001 [SwitchB-luser-client001] password simple abc [SwitchB-luser-client001] service-type ssh level 3 [SwitchB-luser-client001] quit
Configure Switch A # Create a VLAN interface on the switch and assign an IP address, which serves as the SSH clients address in an SSH connection.
<SwitchA> system-view [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] ip address 10.165.87.137 255.255.255.0 [SwitchA-Vlan-interface1] quit
The Server is not authenticated. Do you continue to access it?(Y/N):y Do you want to save the server's public key?(Y/N):n Enter password:
************************************************************************** * * * Copyright(c) 2004-2008 3Com Corp. and its licensors. All rights reserved. Without the owner's prior written consent, no decompiling or reverse-engineering shall be allowed. * *
**************************************************************************
<SwitchB>
Network diagram
Figure 1-31 Switch acts as client for publickey authentication
1-41
Configuration procedure
In public key authentication, you can use either RSA or DSA public key. Here takes the DSA public key as an example.
Configure Switch B # Create a VLAN interface on the switch and assign an IP address, which the SSH client will use as the destination for SSH connection.
<SwitchB> system-view [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] ip address 10.165.87.136 255.255.255.0 [SwitchB-Vlan-interface1] quit
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
Before doing the following steps, you must first generate a DSA public key pair on the client and save the key pair in a file named Switch001, and then upload the file to the SSH server through FTP or TFTP. For details, refer to Configure Switch A.
1-42
# Import the client public key pair named Switch001 from the file Switch001.
[SwitchB] public-key peer Switch001 import sshkey Switch001
Configure Switch A # Create a VLAN interface on the switch and assign an IP address, which serves as the SSH clients address in an SSH connection.
<SwitchA> system-view [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] ip address 10.165.87.137 255.255.255.0 [SwitchA-Vlan-interface1] quit
After the key pair is generated, you need to upload the pubic key file to the server through FTP or TFTP and complete the server end configuration before you continue to configure the client.
The Server is not authenticated. Do you continue to access it?(Y/N):y Do you want to save the server's public key?(Y/N):n
************************************************************************** * * * Copyright(c) 2004-2008 3Com Corp. and its licensors. All rights reserved. Without the owner's prior written consent, no decompiling or reverse-engineering shall be allowed. * *
**************************************************************************
<SwitchB>
1-43
Network diagram
Figure 1-32 Switch acts as client and first-time authentication is not supported
Configuration procedure
Configure Switch B # Create a VLAN interface on the switch and assign an IP address for it to serve as the destination of the client.
<SwitchB> system-view [SwitchB] interface vlan-interface 1 [SwitchB-Vlan-interface1] ip address 10.165.87.136 255.255.255.0 [SwitchB-Vlan-interface1] quit
Generating the RSA and DSA key pairs on the server is prerequisite to SSH login.
1-44
Before doing the following steps, you must first generate a DSA key pair on the client and save the key pair in a file named Switch001, and then upload the file to the SSH server through FTP or TFTP. For details, refer to the following Configure Switch A.
# Import the clients public key file Switch001 and name the public key as Switch001.
[SwitchB] public-key peer Switch001 import sshkey Switch001
# Export the generated DSA host public key pair to a file named Switch002.
[SwitchB] public-key local export dsa ssh2 Switch002
When first-time authentication is not supported, you must first generate a DSA key pair on the server and save the key pair in a file named Switch002, and then upload the file to the SSH client through FTP or TFTP.
Configure Switch A # Create a VLAN interface on the switch and assign an IP address, which serves as the SSH clients address in an SSH connection.
<SwitchA> system-view [SwitchA] interface vlan-interface 1 [SwitchA-Vlan-interface1] ip address 10.165.87.137 255.255.255.0 [SwitchA-Vlan-interface1] quit
After generating the key pair, you need to upload the key pair file to the server through FTP or TFTP and complete the server end configuration before you continue to configure the client.
1-45
When first-time authentication is not supported, you must first generate a DSA key pair on the server and save the key pair in a file named Switch002, and then upload the file to the SSH client through FTP or TFTP. For details, refer to the above part Configure Switch B.
# Import the public key pair named Switch002 from the file Switch002.
[SwitchA] public-key peer Switch002 import sshkey Switch002
************************************************************************** * * * Copyright(c) 2004-2008 3Com Corp. and its licensors. All rights reserved. Without the owner's prior written consent, no decompiling or reverse-engineering shall be allowed. * *
**************************************************************************
<SwitchB>
1-46
Table of Contents
1 File System Management Configuration 1-1 File System Configuration1-1 Introduction to File System 1-1 File System Configuration Tasks1-1 Directory Operations1-1 File Operations 1-2 Flash Memory Operations 1-3 Prompt Mode Configuration 1-3 File System Configuration Example 1-4 File Attribute Configuration 1-5 Introduction to File Attributes1-5 Booting with the Startup File 1-6 Configuring File Attributes 1-6
3com switches 4200G allow you to input a file path and file name in one of the following ways: In universal resource locator (URL) format and starting with unit1>flash:/. or flash:/ This method is used to specify a file in the current Flash memory. For example, the URL of a file named text.txt in the root directory of the switch is unit1>flash:/text.txt or flash:/text.txt. Entering the path name or file name directly. This method can be used to specify a path or a file in the current work directory. For example, to access file text.txt in the current directory, you can directly input the file name text.txt as the file URL.
Directory Operations
The file system provides directory-related functions, such as: Creating/deleting a directory Displaying the current work directory, or contents in a specified directory Table 1-2 describes the directory-related operations. Perform the following configuration in user view.
1-1
Table 1-2 Directory operations To do Create a directory Delete a directory Display the current work directory Display the information about specific directories and files Enter a specified directory Use the command mkdir directory rmdir directory pwd dir [ /all ] [ file-url ] cd directory Remarks Optional Optional Optional Optional Optional
Only empty directories can be deleted by using the rmdir command. In the output information of the dir /all command, deleted files (that is, those stored in the recycle bin) are embraced in brackets.
File Operations
The file system also provides file-related functions listed in Table 1-3. Perform the following configuration in user view. Note that the execute command should be executed in system view. Table 1-3 File operations To do Use the command Optional delete [ /unreserved ] file-url Delete a file delete { running-files | standby-files } [ /unreserved ] A deleted file can be restored by using the undelete command if you delete it by executing the delete command without specifying the /unreserved keyword. Optional Optional Optional Optional Optional Optional Display the content of a file more file-url Currently, the file system only supports displaying the contents of text files. Optional Remarks
Restore a file in the recycle bin Delete a file from the recycle bin Rename a file Copy a file Move a file
undelete file-url reset recycle-bin [ file-url ] [ /force ] rename fileurl-source fileurl-dest copy fileurl-source fileurl-dest move fileurl-source fileurl-dest
1-2
Remarks
For deleted files whose names are the same, only the latest deleted file is kept in the recycle bin and can be restored. The files which are deleted by the delete command without the /unreserved keyword are actually moved to the recycle bin and thus still take storage space. You can clear the recycle bin by using the reset recycle-bin command. The dir /all command displays the files in the recycle bin in square brackets. If the configuration files are deleted, the switch adopts the null configuration when it starts up next time.
The format operation leads to the loss of all files, including the configuration files, on the Flash memory and is irretrievable.
Remarks
Remarks
1 (*) 2 (*) 3 4 5 6 7
Mar 28 2007 10:51:22 Apr 03 2000 16:04:52 Apr 03 2000 16:04:55 Apr 04 2000 17:27:35 Apr 04 2000 17:27:41 Apr 04 2000 17:30:06 Apr 04 2000 23:04:21
# Copy the file flash:/config.cfg to flash:/test/, with 1.cfg as the name of the new file.
<Sysname> copy flash:/config.cfg flash:/test/1.cfg Copy unit1>flash:/config.cfg to unit1>flash:/test/1.cfg?[Y/N]:y .. %Copy file unit1>flash:/config.cfg to unit1>flash:/test/1.cfg...Done.
1 (*) 2 (*) 3 4 5 6 7
Mar 28 2007 10:51:22 Apr 03 2000 16:04:52 Apr 03 2000 16:04:55 Apr 04 2000 17:27:35 Apr 04 2000 17:27:41 Apr 04 2000 17:30:06 Apr 04 2000 23:04:21
(*b) -with both main and backup attribute <Sysname> dir unit1>flash:/test/ Directory of unit1>flash:/test/
1-4
1 2
-rw-rw-
1235 1235
test.cfg 1.cfg
main
(*)
backup
(b)
none
None
A file can have both the main and backup attributes. Files of this kind are labeled *b.
Note that, there can be only one app file, one configuration file and one Web file with the main attribute in the Flash memory. If a newly created file is configured to be with the main attribute, the existing file with the main attribute in the Flash memory will lose its main attribute. This circumstance also applies to the file with the backup attribute in the Flash memory. File operations and file attribute operations are independent. For example, if you delete a file with the main attribute from the Flash memory, the other files in the flash memory will not possess the main
1-5
attribute. If you download a valid file with the same name as the deleted file to the flash memory, the file will possess the main attribute. After the Boot ROM of a switch is upgraded, the original default app file has the main attribute.
boot boot-loader backup-attribute file-url boot web-package webfile { backup | main } boot attribute-switch { all | app | configuration | web }
Optional
By default, the user is enabled to use the customized password to enter the BOOT menu.
1-6
To do Display the information about the app file used as the startup file Display information about the Web file used by the device
Use the command display boot-loader [ unit unit-id ] display web package
Remarks
Before configuring the main or backup attribute for a file, make sure the file already exists on the device. The configuration of the main or backup attribute of a Web file takes effect immediately without restarting the switch. After upgrading a Web file, you need to specify the new Web file in the Boot menu after restarting the switch or specify a new Web file by using the boot web-package command. Otherwise, Web server cannot function normally. Currently, a configuration file has the extension of cfg and resides in the root directory of the Flash memory. For the detailed configuration of configuration file attributes, refer to the Configuration File Management module in this manual.
1-7
Table of Contents
1 FTP and SFTP Configuration1-1 Introduction to FTP and SFTP 1-1 Introduction to FTP 1-1 Introduction to SFTP1-1 FTP Configuration 1-2 FTP Configuration: A Switch Operating as an FTP Server 1-2 FTP Configuration: A Switch Operating as an FTP Client 1-6 Configuration Example: A Switch Operating as an FTP Server1-8 FTP Banner Display Configuration Example1-10 FTP Configuration: A Switch Operating as an FTP Client 1-11 SFTP Configuration1-13 SFTP Configuration: A Switch Operating as an SFTP Server 1-13 SFTP Configuration: A Switch Operating as an SFTP Client1-14 SFTP Configuration Example1-16 2 TFTP Configuration 2-1 Introduction to TFTP 2-1 TFTP Configuration2-1 TFTP Configuration: A Switch Operating as a TFTP Client 2-2 TFTP Configuration Example 2-3
FTP server
FTP client
Introduction to SFTP
Secure FTP (SFTP) is established based on an SSH2 connection. It allows a remote user to log in to a switch to manage and transmit files, providing a securer guarantee for data transmission. In addition, since the switch can be used as a client, you can log in to remote devices to transfer files securely.
1-1
FTP Configuration
Complete the following tasks to configure FTP: Task Creating an FTP user Enabling an FTP server Configuring connection idle time FTP Configuration: A Switch Operating as an FTP Server Specifying the source interface and source IP address for an FTP server Disconnecting a specified user Configuring the banner for an FTP server Displaying FTP server information FTP Configuration: A Switch Operating as an FTP Client Basic configurations on an FTP client Specifying the source interface and source IP address for an FTP client Remarks Required Required Optional Optional Optional Optional Optional Optional
1-2
Only one user can access a 3com switch 4200G at a given time when the latter operates as an FTP server. Operating as an FTP server, a 3com switch 4200G cannot receive a file whose size exceeds its storage space. The clients that attempt to upload such a file will be disconnected with the FTP server due to lack of storage space on the FTP server.
To protect unused sockets against attacks, the 3com switch 4200G provides the following functions: TCP 21 is enabled only when you start the FTP server. TCP 21 is disabled when you shut down the FTP server.
Specifying the source interface and source IP address for an FTP server
You can specify the source interface and source IP address for an FTP server to enhance server security. After this configuration, FTP clients can access this server only through the IP address of the specified interface or the specified IP address.
Source interface refers to the existing VLAN interface or Loopback interface on the device. Source IP address refers to the IP address configured for the interface on the device. Each source interface corresponds to a source IP address. Therefore, specifying a source interface for the FTP server is the same as specifying the IP address of this interface as the source IP address.
Follow these steps to specify the source interface and source IP address for an FTP server:
1-3
To do Enter system view Specify the source interface for an FTP server Specifying the source IP address for an FTP server
Use the command system-view ftp-server source-interface interface-type interface-number ftp-server source-ip ip-address
Remarks
The specified interface must be an existing one. Otherwise a prompt appears to show that the configuration fails. The value of the ip-address argument must be an IP address on the device where the configuration is performed. Otherwise a prompt appears to show that the configuration fails. You can specify only one source interface or source IP address for the FTP at one time. That is, only one of the commands ftp-server source-interface and ftp-server source-ip can be valid at one time. If you execute both of them, the new setting will overwrite the original one. If the switch (FTP server) is the command switch or member switch in a cluster, do not use the ftp-server source-ip command to specify the private IP address of the cluster as the source IP address of the FTP server. Otherwise, FTP does not take effect.
With a 3com switch 4200G acting as the FTP server, if a network administrator attempts to disconnect a user that is uploading/downloading data to/from the FTP server the 3com switch 4200G will disconnect the user after the data transmission is completed.
1-4
Login banner: After the connection between an FTP client and an FTP server is established, the FTP server outputs the configured login banner to the FTP client terminal. Figure 1-1 Process of displaying a login banner
Shell banner: After the connection between an FTP client and an FTP server is established and correct user name and password are provided, the FTP server outputs the configured shell banner to the FTP client terminal. Figure 1-2 Process of displaying a shell banner
Follow these steps to configure the banner display for an FTP server: To do Enter system view Configure a login banner Configure a shell banner Use the command system-view header login text header shell text Required Use either command or both. By default, no banner is configured. Remarks
For details about the header command, refer to the Login part of the manual.
1-5
1-6
To do
Remarks
If no file name is specified, all the files in the current directory are displayed. Query a specified file on the FTP server ls [ remotefile ] [ localfile ] The difference between these two commands is that the dir command can display the file name, directory as well as file attributes; while the Is command can display only the file name and directory.
Download a remote file from the FTP server Upload a local file to the remote FTP server Rename a file on the remote server Log in with the specified user name and password Connect to a remote FTP server Terminate the current FTP connection without exiting FTP client view Terminate the current FTP connection and return to user view Display the online help about a specified command concerning FTP Enable the verbose function
get remotefile [ localfile ] put localfile [ remotefile ] rename remote-source remote-dest user username [ password ] open { ip-address | server-name } [ port ] disconnect close quit bye remotehelp [ protocol-command ] verbose Optional Enabled by default. Optional
Specifying the source interface and source IP address for an FTP client
You can specify the source interface and source IP address for a switch acting as an FTP client, so that it can connect to a remote FTP server. Follow these steps to specify the source interface and source IP address for an FTP client: To do Specify the source interface used for the current connection Specify the source IP address used for the current connection Enter system view Use the command ftp { cluster | remote-server } source-interface interface-type interface-number ftp { cluster | remote-server } source-ip ip-address system-view Optional Remarks
Optional
1-7
To do Specify an interface as the source interface the FTP client uses every time it connects to an FTP server Specify an IP address as the source IP address the FTP client uses every time it connects to an FTP server Display the source IP address used by an FTP client every time it connects to an FTP server
Remarks
The specified interface must be an existing one. Otherwise a prompt appears to show that the configuration fails. The value of the ip-address argument must be the IP address of the device where the configuration is performed. Otherwise a prompt appears to show that the configuration fails. The source interface/source IP address set for one connection is prior to the fixed source interface/source IP address set for each connection. That is, for a connection between an FTP client and an FTP server, if you specify the source interface/source IP address used for the connection this time, and the specified source interface/source IP address is different from the fixed one, the former will be used for the connection this time. Only one fixed source interface or source IP address can be set for the FTP client at one time. That is, only one of the commands ftp source-interface and ftp source-ip can be valid at one time. If you execute both of them, the new setting will overwrite the original one.
1-8
Network diagram
Figure 1-3 Network diagram for FTP configurations: a switch operating as an FTP server
Configuration procedure
1) Configure Switch A (the FTP server)
# Log in to the switch and enable the FTP server function on the switch. Configure the user name and password used to access FTP services, and specify the service type as FTP (You can log in to a switch through the Console port or by telnetting the switch. See the Login module for detailed information.) # Configure the FTP username as switch, the password as hello, and the service type as FTP.
<Sysname> <Sysname> system-view [Sysname] ftp server enable [Sysname] local-user switch [Sysname-luser-switch] password simple hello [Sysname-luser-switch] service-type ftp
2)
Run an FTP client application on the PC to connect to the FTP server. Upload the application named switch.bin to the root directory of the Flash memory of the FTP server, and download the configuration file named config.cfg from the FTP server. The following takes the command line window tool provided by Windows as an example: # Enter the command line window and switch to the directory where the file switch.bin is located. In this example it is in the root directory of C:\.
C:\>
# Access the Ethernet switch through FTP. Input the username switch and password hello to log in and enter FTP view.
C:\> ftp 1.1.1.1 Connected to 1.1.1.1. 220 FTP service ready. User (1.1.1.1:(none)): switch 331 Password required for switch. Password: 230 User logged in. ftp>
1-9
This example uses the command line window tool provided by Windows. When you log in to the FTP server through another FTP client, refer to the corresponding instructions for operation description.
If available space on the Flash memory of the switch is not enough to hold the file to be uploaded, you need to delete files not in use from the Flash memory to make room for the file, and then upload the file again. The files in use cannot be deleted. If you have to delete the files in use to make room for the file to be uploaded, you can only delete/download them through the Boot ROM menu. 3com switch 4200G is not shipped with FTP client application software. You need to purchase and install it by yourself.
3)
# After uploading the application, use the boot boot-loader command to specify the uploaded file (switch.bin) to be the startup file used when the switch starts the next time, and restart the switch. Thus the switch application is upgraded.
<Sysname> boot boot-loader switch.bin <Sysname> reboot
For information about the boot boot-loader command and how to specify the startup file for a switch, refer to the System Maintenance and Debugging part of this manual.
Configure the login banner of the switch as login banner appears and the shell banner as shell banner appears.
Network diagram
Figure 1-4 Network diagram for FTP banner display configuration
Configuration procedure
1) Configure the switch (FTP server)
# Configure the login banner of the switch as login banner appears and the shell banner as shell banner appears. For detailed configuration of other network requirements, see section Configuration Example: A Switch Operating as an FTP Server.
<Sysname> system-view [Sysname] header login %login banner appears% [Sysname] header shell %shell banner appears%
2)
# Access the Ethernet switch through FTP. Enter the username switch and the password hello to log in to the switch, and then enter FTP view. Login banner appears after FTP connection is established. Shell banner appears after the user passes the authentication.
C:\> ftp 1.1.1.1 Connected to 1.1.1.1. 220-login banner appears 220 FTP service ready. User (1.1.1.1:(none)): switch 331 Password required for switch. Password: 230-shell banner appears 230 User logged in. ftp>
Network diagram
Figure 1-5 Network diagram for FTP configurations: a switch operating as an FTP client
Configuration procedure
1) Configure the PC (FTP server)
Perform FTP serverrelated configurations on the PC, that is, create a user account on the FTP server with username switch and password hello. (For detailed configuration, refer to the configuration instruction relevant to the FTP server software.) 2) Configure the switch (FTP client)
# Log in to the switch. (You can log in to a switch through the Console port or by telnetting the switch. See the Login module for detailed information.)
<Sysname>
If available space on the Flash memory of the switch is not enough to hold the file to be uploaded, you need to delete files not in use from the Flash memory to make room for the file, and then upload the file again. The files in use cannot be deleted. If you have to delete the files in use to make room for the file to be uploaded, you can only delete/download them through the Boot ROM menu.
# Connect to the FTP server using the ftp command in user view. You need to provide the IP address of the FTP server, the user name and the password as well to enter FTP view.
<Sysname> ftp 2.2.2.2 Trying ... Press CTRL+K to abort Connected. 220 FTP service ready. User(none):admin 331 Password required for admin. Password: 230 User logged in. [ftp]
# Execute the put command to upload the configuration file named config.cfg to the FTP server.
[ftp] put config.cfg
# Execute the get command to download the file named switch.bin to the Flash memory of the switch.
1-12
# Execute the quit command to terminate the FTP connection and return to user view.
[ftp] quit <Sysname>
# After downloading the file, use the boot boot-loader command to specify the downloaded file (switch.bin) to be the application for next startup, and then restart the switch. Thus the switch application is upgraded.
<Sysname> boot boot-loader switch.bin <Sysname> reboot
For information about the boot boot-loader command and how to specify the startup file for a switch, refer to the System Maintenance and Debugging module of this manual.
SFTP Configuration
Complete the following tasks to configure SFTP: Task Enabling an SFTP server SFTP Configuration: A Switch Operating as an SFTP Server Configuring connection idle time Supported SFTP client software Basic configurations on an SFTP client SFTP Configuration: A Switch Operating as an SFTP Client Specifying the source interface or source IP address for an SFTP client Required Optional Remarks
Optional
1-13
Remarks
Disabled by default.
Currently a 3com switch 4200G operating as an SFTP server supports the connection of only one SFTP user. When multiple users attempt to log in to the SFTP server or multiple connections are enabled on a client, only the first user can log in to the SFTP user. The subsequent connection will fail. When you upload a large file through WINSCP, if a file with the same name exists on the server, you are recommended to set the packet timeout time to over 600 seconds, thus to prevent the client from failing to respond to device packets due to timeout. Similarly, when you delete a large file from the server, you are recommended to set the client packet timeout time to over 600 seconds.
Follow these steps to perform basic configurations on an SFTP client: To do Enter system view Use the command system-view sftp { host-ip | host-name } [ port-num ] [ identity-key { dsa | rsa } | prefer_kex { dh_group1 | dh_exchange_group } | prefer_ctos_cipher { 3des | des | aes128 } | prefer_stoc_cipher { 3des | des | aes128 } | prefer_ctos_hmac { sha1 | sha1_96 | md5 | md5_96 } | prefer_stoc_hmac { sha1 | sha1_96 | md5 | md5_96 } ] * cd pathname cdup pwd mkdir pathname rmdir pathname delete remotefile Delete a specified file remove remote-file dir [ -a | -l ] [ remote-path ] Optional Both commands have the same effect. Optional If no file name is provided, all the files in the current directory are displayed. Query a specified file on the SFTP server ls [ -a | -l ] [ remote-path ] The difference between these two commands is that the dir command can display the file name, directory as well as file attributes; while the Is command can display only the file name and directory. Optional Remarks
Required Support for the 3des keyword depends on the number of encryption bits of the software version. The 168-bit version supports this keyword, while the 56-bit version does not.
Change the working directory on the remote SFTP server Change the working directory to be the parent directory Display the working directory on the SFTP server Create a directory on the remote SFTP server Remove a directory on the remote SFTP server
Download a remote file from the SFTP server Upload a local file to the remote SFTP server Rename a file on the remote server Exit SFTP client view and return to system view
get remotefile [ localfile ] put localfile [ remotefile ] rename remote-source remote-dest bye exit quit The three commands have the same effect. Optional
1-15
Remarks
If you specify to authenticate a client through public key on the server, the client needs to read the local private key when logging in to the SFTP server. Since both RSA and DSA are available for public key authentication, you need to use the identity-key key word to specify the algorithms to get correct local private key; otherwise you will fail to log in. For details, see SSH Operation Manual.
Network diagram
Figure 1-6 Network diagram for SFTP configuration
1-16
Configuration procedure
1) Configure the SFTP server (switch B)
# Create a VLAN interface on the switch and assign to it an IP address, which is used as the destination address for the client to connect to the SFTP server.
[Sysname] interface vlan-interface 1 [Sysname-Vlan-interface1] ip address 192.168.0.1 255.255.255.0 [Sysname-Vlan-interface1] quit
# Configure the protocol through which the remote user logs in to the switch as SSH.
[Sysname-ui-vty0-4] protocol inbound ssh [Sysname-ui-vty0-4] quit
# Configure the authentication mode as password. Authentication timeout time, retry number, and update time of the server key adopt the default values.
[Sysname] ssh user client001 authentication-type password
2)
# Configure the IP address of the VLAN interface on switch A. It must be in the same segment with the IP address of the VLAN interface on switch B. In this example, configure it as 192.168.0.2.
<Sysname> system-view [Sysname] interface vlan-interface 1 [Sysname-Vlan-interface1] ip address 192.168.0.2 255.255.255.0 [Sysname-Vlan-interface1] quit
# Connect to the remote SFTP server. Enter the username client001 and the password abc, and then enter SFTP client view.
[Sysname] sftp 192.168.0.1 Input Username: client001 Trying 192.168.0.1 ... Press CTRL+K to abort
1-17
The Server is not authenticated. Do you continue to access it?(Y/N):y Do you want to save the server's public key?(Y/N):n Enter password:
sftp-client>
# Display the current directory of the server. Delete the file z and verify the result.
sftp-client> dir -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx drwxrwxrwx -rwxrwxrwx -rwxrwxrwx 1 noone 1 noone 1 noone 1 noone 1 noone 1 noone nogroup nogroup nogroup nogroup nogroup nogroup 1759 Aug 23 06:52 config.cfg 225 Aug 24 08:01 pubkey2 283 Aug 24 07:39 pubkey1 0 Sep 01 06:22 new 225 Sep 01 06:55 pub 0 Sep 01 08:00 z
Received status: End of file Received status: Success sftp-client> delete z The following files will be deleted: /z Are you sure to delete it?(Y/N):y This operation may take a long time.Please wait...
Received status: Success File successfully Removed sftp-client> dir -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx drwxrwxrwx -rwxrwxrwx 1 noone 1 noone 1 noone 1 noone 1 noone nogroup nogroup nogroup nogroup nogroup 1759 Aug 23 06:52 config.cfg 225 Aug 24 08:01 pubkey2 283 Aug 24 07:39 pubkey1 0 Sep 01 06:22 new 225 Sep 01 06:55 pub
# Add a directory new1, and then check whether the new directory is successfully created.
sftp-client> mkdir new1 Received status: Success New directory created sftp-client> dir -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx drwxrwxrwx -rwxrwxrwx drwxrwxrwx 1 noone 1 noone 1 noone 1 noone 1 noone 1 noone nogroup nogroup nogroup nogroup nogroup nogroup 1759 Aug 23 06:52 config.cfg 225 Aug 24 08:01 pubkey2 283 Aug 24 07:39 pubkey1 0 Sep 01 06:22 new 225 Sep 01 06:55 pub 0 Sep 02 06:30 new1
# Rename the directory new1 as new2, and then verify the result.
1-18
sftp-client> rename new1 new2 File successfully renamed sftp-client> dir -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx drwxrwxrwx -rwxrwxrwx drwxrwxrwx 1 noone 1 noone 1 noone 1 noone 1 noone 1 noone nogroup nogroup nogroup nogroup nogroup nogroup 1759 Aug 23 06:52 config.cfg 225 Aug 24 08:01 pubkey2 283 Aug 24 07:39 pubkey1 0 Sep 01 06:22 new 225 Sep 01 06:55 pub 0 Sep 02 06:33 new2
# Download the file pubkey2 from the server and rename it as public.
sftp-client> get pubkey2 public This operation may take a long time, please wait... . Remote file:/pubkey2 ---> Local file: public..
Received status: End of file Received status: Success Downloading file successfully ended
# Upload file pu to the server and rename it as puk, and then verify the result.
sftp-client> put pu puk This operation may take a long time, please wait... Local file: pu ---> Remote file: /puk
Received status: Success Uploading file successfully ended sftp-client> dir -rwxrwxrwx -rwxrwxrwx -rwxrwxrwx drwxrwxrwx drwxrwxrwx -rwxrwxrwx -rwxrwxrwx 1 noone 1 noone 1 noone 1 noone 1 noone 1 noone 1 noone nogroup nogroup nogroup nogroup nogroup nogroup nogroup 1759 Aug 23 06:52 config.cfg 225 Aug 24 08:01 pubkey2 283 Aug 24 07:39 pubkey1 0 Sep 01 06:22 new 0 Sep 02 06:33 new2 283 Sep 02 06:35 pub 283 Sep 02 06:36 puk
# Exit SFTP.
sftp-client> quit Bye [Sysname]
1-19
TFTP Configuration
When configuring TFTP, go to these sections for information you are interested in: Introduction to TFTP TFTP Configuration
Introduction to TFTP
Compared with FTP, Trivial File Transfer Protocol (TFTP) features simple interactive access interface and no authentication control. Therefore, TFTP is applicable in the networks where client-server interactions are relatively simple. TFTP is implemented based on UDP. It transfers data through UDP port 69. Basic TFTP operations are described in RFC 1986. TFTP transmission is initiated by clients, as described in the following: To download a file, a client sends Read Request packets to the TFTP server, then receives data from the TFTP server, and sends acknowledgement packets to the TFTP server. To upload a file, a client sends Write Request packets to the TFTP server, then sends data to the TFTP server, and receives acknowledgement packets from the TFTP server. A 3com switch 4200G can act as a TFTP client only. When you download a file that is larger than the free space of the switchs flash memory: If the TFTP server supports file size negotiation, file size negotiation will be initiated between the switch and the server and the file download operation will be aborted if the free space of the switchs flash memory is found to be insufficient. If the TFTP server does not support file size negotiation, the switch will receive data from the server until the flash memory is full. If there is more data to be downloaded, the switch will prompt that the space is insufficient and delete the data partially downloaded. File download fails. TFTP-based file transmission can be performed in the following modes: Binary mode for program file transfer. ASCII mode for text file transfer.
Before performing TFTP-related configurations, you need to configure IP addresses for the TFTP client and the TFTP server, and make sure a route exists between the two.
TFTP Configuration
Complete the following tasks to configure TFTP:
2-1
Task Basic configurations on a TFTP client TFTP Configuration: A Switch Operating as a TFTP Client TFTP server configuration Specifying the source interface or source IP address for an FTP client For details, see the corresponding manual
Remarks
Optional
Specify the source IP address used for the current connection Enter system view
2-2
To do Specify an interface as the source interface a TFTP client uses every time it connects to a TFTP server Specify an IP address as the source IP address a TFTP client uses every time it connects to a TFTP server Display the source IP address used by a TFTP client every time it connects to a TFTP server
Remarks
The specified interface must be an existing one; otherwise a prompt appears to show that the configuration fails. The value of the ip-address argument must be an IP address on the device where the configuration is performed, and otherwise a prompt appears to show that the configuration fails. The source interface/source IP address set for one connection is prior to the fixed source interface/source IP address set for each connection. That is, for a connection between a TFTP client and a TFTP server, if you specify the source interface/source IP address only used for the connection this time, and the specified source interface/source IP address is different from the fixed one, the former will be used for the connection this time. You may specify only one source interface or source IP address for the TFTP client at one time. That is, only one of the commands tftp source-interface and tftp source-ip can be effective at one time. If both commands are configured, the one configured later will overwrite the original one.
2-3
Network diagram
Figure 2-1 Network diagram for TFTP configurations
Configuration procedure
1) Configure the TFTP server (PC)
Start the TFTP server and configure the working directory on the PC. 2) Configure the TFTP client (switch).
# Log in to the switch. (You can log in to a switch through the Console port or by telnetting the switch. See the Login module for detailed information.)
<Sysname>
If available space on the Flash memory of the switch is not enough to hold the file to be uploaded, you need to delete files not in use from the Flash memory to make room for the file, and then upload the file again. The files in use cannot be deleted. If you have to delete the files in use to make room for the file to be uploaded, you can only delete/download them through the Boot ROM menu.
# Configure the IP address of a VLAN interface on the switch to be 1.1.1.1, and ensure that the port through which the switch connects with the PC belongs to this VLAN. (This example assumes that the port belongs to VLAN 1.)
[Sysname] interface Vlan-interface 1 [Sysname-Vlan-interface1] ip address 1.1.1.1 255.255.255.0 [Sysname-Vlan-interface1] quit
# Download the switch application named switch.bin from the TFTP server to the switch.
<Sysname> tftp 2.2.2.2 get switch.bin switch.bin
# Upload the switch configuration file named config.cfg to the TFTP server.
<Sysname> tftp 2.2.2.2 put config.cfg config.cfg
# After downloading the file, use the boot boot-loader command to specify the downloaded file (switch.bin) to be the startup file used when the switch starts the next time, and restart the switch. Thus the switch application is upgraded.
<Sysname> boot boot-loader switch.bin <Sysname> reboot
2-4
For information about the boot boot-loader command and how to specify the startup file for a switch, refer to the System Maintenance and Debugging module of this manual.
2-5
Table of Contents
1 Information Center1-1 Information Center Overview 1-1 Introduction to Information Center1-1 System Information Format 1-4 Information Center Configuration1-7 Information Center Configuration Task List1-7 Configuring Synchronous Information Output 1-7 Configuring to Display the Time Stamp with the UTC Time Zone 1-8 Setting to Output System Information to the Console 1-8 Setting to Output System Information to a Monitor Terminal 1-10 Setting to Output System Information to a Log Host1-11 Setting to Output System Information to the Trap Buffer 1-12 Setting to Output System Information to the Log Buffer1-13 Setting to Output System Information to the SNMP NMS1-13 Displaying and Maintaining Information Center 1-14 Information Center Configuration Examples 1-15 Log Output to a UNIX Log Host1-15 Log Output to a Linux Log Host1-16 Log Output to the Console 1-18 Configuration Example 1-18
Information Center
When configuring information center, go to these sections for information you are interested in: Information Center Overview Information Center Configuration Displaying and Maintaining Information Center Information Center Configuration Examples
1-1
Information filtering by severity works this way: information with the severity value greater than the configured threshold is not output during the filtering. If the threshold is set to 1, only information with the severity being emergencies will be output; If the threshold is set to 8, information of all severities will be output.
monitor
loghost
3 4 5 6 7 8 9
Configurations for the six output directions function independently and take effect only after the information center is enabled.
1-2
Description
Module name SYSMIB TAC TELNET TFTPC VLAN VTY XM default System MIB module HWTACACS module Telnet module TFTP client module
Description
Virtual local area network module Virtual type terminal module XModem module Default settings for all the modules
To sum up, the major task of the information center is to output the three types of information of the modules onto the ten channels in terms of the eight severity levels and according to the users settings, and then redirect the system information from the ten channels to the six output directions.
The space, the forward slash /, and the colon are all required in the above format. Before <timestamp> may have %, #, or * followed with a space, indicating log, alarm, or debugging information respectively.
(-1- indicates that the unit number of the device is 1.) If the output destination is loghost, the switch and the log host use the syslog protocol. The system information is in the following format according to RFC 3164 (The BSD Syslog Protocol):
<Int_16>timestamp sysname %%nnmodule/level/digest: source content
1-4
If the address of the log host is specified in the information center of the switch, when logs are generated, the switch sends the logs to the log host in the above format. For detailed information, refer to Setting to Output System Information to a Log Host. There is the syslog process on the Unix or Linux platform, you can start the process to receive the logs sent from the switch; in the Windows platform, you need to install the specific software, and it will operate as the syslog host. Some log host software will resolve the received information as well as its format, so that the log format displayed on the log host is different from the one described in this manual.
Int_16 (Priority)
The priority is calculated using the following formula: facility*8+severity-1, in which facility (the device name) defaults to local7 with the value being 23 (the value of local6 is 22, that of local5 is 21, and so on). severity (the information level) ranges from 1 to 8. Table 1-1 details the value and meaning associated with each severity. Note that the priority field appears only when the information has been sent to the log host.
Timestamp
Timestamp records the time when system information is generated to allow users to check and identify system events. Note that there is a space between the timestamp and sysname (host name) fields. The time stamp has the following two formats. 1) 2) Without the universal time coordinated (UTC) time zone, the time stamp is in the format of Mmm dd hh:mm:ss:ms yyyy. With the UTC time zone, the time stamp is in the format of Mmm dd hh:mm:ss:ms yyyy [GMT +|- hh:mm:ss]. Each field is described as follows: Mmm represents the month, and the available values are: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, and Dec. dd is the date, which shall follow a space if less than 10, for example, 7. hh:mm:ss:ms is the local time, where hh is in the 24-hour format, ranging from 00 to 23, both mm and ss range from 00 to 59, ms ranges from 000 to 999. (Note that: the time stamp of the system information sent from the information center to the log host is with a precision of seconds, while that of the system information sent from the system center to the Console, monitor terminal, logbuffer, trapbuffer and the SNMP is with a precision of milliseconds.) yyyy is the year. [GMT +|- hh:mm:ss] is the UTC time zone, which represents the time difference with the Greenwich standard time. Because switches in a network may distribute in different time zones, when the time displayed in the time stamps of output information is the local time on each switch, it is not so convenient for you to
1-5
locate and solve problems globally. In this case, you can configure the information center to add UTC time zone to the time stamp of the output information, so that you can know the standard time when the information center processing each piece of information. That is, you can know the Greenwich standard time of each switch in the network based on the UTC record in the time stamp. To add UTC time zone to the time stamp in the information center output information, you must: Set the local time zone Set the time stamp format in the output destination of the information center to date Configure to add UTC time zone to the output information After the above configuration, the UTC time zone will be displayed in the output information, like the following:
%Dec login 8 10:12:21:708 2006 [GMT+08:00:00] Sysname SHELL/5/LOGIN:- 1 - VTY(1.1.0.2) in unit1
Sysname
Sysname is the system name of the local switch and defaults to 3Com. You can use the sysname command to modify the system name. Refer to the System Maintenance and Debugging part of this manual for details) Note that there is a space between the sysname and module fields.
%%
This field is a preamble used to identify a vendor. It is displayed only when the output destination is log host.
nn
This field is a version identifier of syslog. It is displayed only when the output destination is log host.
Module
The module field represents the name of the module that generates system information. You can enter the info-center source ? command in system view to view the module list. Refer to Table 1-3 for module name and description. Between module and level is a /.
Level (Severity)
System information can be divided into eight levels based on its severity, from 1 to 8. Refer to Table 1-1 for definition and description of these severity levels. Note that there is a forward slash / between the level (severity) and digest fields.
Digest
The digest field is a string of up to 32 characters, outlining the system information. Note that there is a colon between the digest and content fields. For system information destined to the log host, If the character string ends with (l), it indicates the log information If the character string ends with (t), it indicates the trap information If the character string ends with (d), it indicates the debugging information
1-6
Source
This field indicates the source of the information, such as the source IP address of the log sender. This field is optional and is displayed only when the output destination is the log host.
Context
This field provides the content of the system information.
1-7
If the system information is output before you input any information following the current command line prompt, the system does not echo any command line prompt after the system information output. In the interaction mode, you are prompted for some information input. If the input is interrupted by system output, no system prompt (except the Y/N string) will be echoed after the output, but your input will be displayed in a new line.
Configuring to Display the Time Stamp with the UTC Time Zone
To add UTC time zone to the time stamp in the information center output information, you must: Set the local time zone Set the time stamp format in the output direction of the information center to date Configure to add the UTC time zone to the output information Follow these steps to configure to display time stamp with the UTC time zone: To do Set the time zone for the system Enter system view Set the time stamp format in the output direction of the information center to date Log host direction Use the command clock timezone zone-name { add | minus } time system-view info-center timestamp loghost date Required Non log host direction info-center timestamp { log | trap | debugging } date Use either command Required By default, UTC time zone is set for the system. Remarks
Set to display the UTC time zone in the output information of the information center
Required info-center timestamp utc By default, no UTC time zone is displayed in the output information
1-8
To do
Use the command Optional info-center console channel { channel-number | channel-name } info-center source { modu-name | default } channel { channel-number | channel-name } [ { log | trap | debug } { level severity | state state } ]*
Remarks
By default, the switch uses information channel 0 to output log/debugging/trap information to the console. Optional Refer to Table 1-4 for the default output rules of system information. Optional
By default, the time stamp format of the log and trap output information is date, and that of the debugging output information is boot.
To view the debugging information of some modules on the switch, you need to set the type of the output information to debug when configuring the system information output rules, and use the debugging command to enable debugging for the corresponding modules.
Table 1-4 Default output rules for different output directions LOG Output direction Modules allowed Enable d/disab led Enabled Enabled Enabled Disable d Enabled Disable d Severit y warning s warning s informati onal informati onal warning s debuggi ng TRAP Enabled/ disabled Enabled Enabled Enabled Enabled Disabled Enabled Severity debuggin g debuggin g debuggin g warnings debuggin g warnings DEBUG Enabled/ disabled Enabled Enabled Disabled Disabled Disabled Disabled Severity debuggin g debuggin g debuggin g debuggin g debuggin g debuggin g
Console Monitor terminal Log host Trap buffer Log buffer SNMP NMS
default (all modules) default (all modules) default (all modules) default (all modules) default (all modules) default (all modules)
Follow these steps to enable the system information display on the console: To do Enable the debugging/log/trap information terminal display function Enable debugging information terminal display function Enable log information terminal display function Enable trap information terminal display function Use the command terminal monitor Optional Enabled by default. Optional Disabled by default. Optional Enabled by default. Optional Enabled by default. Remarks
terminal debugging
terminal logging
terminal trapping
Make sure that the debugging/log/trap information terminal display function is enabled (use the terminal monitor command) before you enable the corresponding terminal display function by using the terminal debugging, terminal logging, or terminal trapping command.
1-10
To do
Remarks
By default, the time stamp format of the log and trap output information is date, and that of the debugging output information is boot.
When there are multiple Telnet users or dumb terminal users, they share some configuration parameters including module filter, language and severity level threshold. In this case, change to any such parameter made by one user will also be reflected on all other user terminals. To view debugging information of specific modules, you need to set the information type as debug when setting the system information output rules, and enable debugging for corresponding modules through the debugging command.
terminal debugging
terminal logging
terminal trapping
Make sure that the debugging/log/trap information terminal display function is enabled (use the terminal monitor command) before you enable the corresponding terminal display function by using the terminal debugging, terminal logging, or terminal trapping command.
Remarks
By default, the switch does not output information to the log host. After you configure the switch to output information to the log host, the switch uses information channel 2 by default. Optional
Configure the source interface through which log information is sent to the log host
By default, no source interface is configured, and the system automatically selects an interface as the source interface. Optional Refer to Table 1-4 for the default output rules of system information. Optional By default, the time stamp format of the information output to the log host is date.
info-center source { modu-name | default } channel { channel-number | channel-name } [ { log | trap | debug } { level severity | state state } ]* info-center timestamp loghost { date | no-year-date | none }
Set the format of the time stamp to be sent to the log host
Be sure to set the correct IP address when using the info-center loghost command. A loopback IP address will cause an error message prompting that this address is invalid.
1-12
To do
Use the command Optional info-center trapbuffer [channel { channel-number | channel-name } | size buffersize]* info-center source { modu-name | default } channel { channel-number | channel-name } [ { log | trap | debug } { level severity | state state } ]* info-center timestamp { log | trap | debugging } { boot | date | none }
Remarks
By default, the switch uses information channel 3 to output trap information to the trap buffer, which can holds up to 256 items by default. Optional Refer to Table 1-4 for the default output rules of system information. Optional By default, the time stamp format of the output trap information is date.
1-13
Remarks
Enabled by default. Optional By default, the switch outputs trap information to SNMP through channel 5. Optional Refer to Table 1-4 for the default output rules of system information. Optional By default, the time stamp format of the information output to the SNMP NMS is date.
info-center snmp channel { channel-number | channel-name } info-center source { modu-name | default } channel { channel-number | channel-name } [ { log | trap | debug } { level severity | state state } ]* info-center timestamp { log | trap | debugging } { boot | date | none }
To send information to a remote SNMP NMS properly, related configurations are required on both the switch and the SNMP NMS.
display logbuffer [ unit unit-id ] [ level severity | size buffersize ]* [ | { begin | exclude | include } regular-expression ] display logbuffer summary [ level severity ] display trapbuffer [ unit unit-id ] [ size buffersize ] reset logbuffer [ unit unit-id ]
1-14
Network diagram
Figure 1-1 Network diagram for log output to a Unix log host
Network
Switch Unix loghost 202.38.1.10
Configuration procedure
1) Configure the switch:
# Configure the host whose IP address is 202.38.1.10 as the log host. Permit ARP and IP modules to output information with severity level higher than informational to the log host.
[Switch] info-center loghost 202.38.1.10 facility local4 [Switch] info-center source arp channel loghost log level informational debug state off trap state off [Switch] info-center source ip channel loghost log level informational debug state off trap state off
2)
The operations here are performed on SunOS 4.0. The operations on other manufacturers' Unix operation systems are similar. Step 1: Execute the following commands as the super user (root user).
# mkdir /var/log/Switch # touch /var/log/Switch/information
Step 2: Edit the file /etc/syslog.conf as the super user (root user) to add the following selector/action pairs.
# Switch configuration messages local4.info /var/log/Switch/information
1-15
When you edit the file /etc/syslog.conf, note that: A note must start in a new line, starting with a # sign. In each pair, a tab should be used as a separator instead of a space. No space is allowed at the end of a file name. The device name (facility) and received log information severity level specified in the file /etc/syslog.conf must be the same as those corresponding parameters configured in the commands info-center loghost and info-center source. Otherwise, log information may not be output to the log host normally.
Step 3: After the log file information is created and the file /etc/syslog.conf is modified, execute the following command to send a HUP signal to the system daemon syslogd, so that it can reread its configuration file /etc/syslog.conf.
# ps -ae | grep syslogd 147 # kill -HUP 147
After all the above operations, the switch can make records in the corresponding log file.
Through combined configuration of the device name (facility), information severity level threshold (severity), module name (filter) and the file syslog.conf, you can sort information precisely for filtering.
Network diagram
Figure 1-2 Network diagram for log output to a Linux log host
Configuration procedure
1) Configure the switch:
1-16
# Configure the host whose IP address is 202.38.1.10 as the log host. Permit all modules to output log information with severity level higher than error to the log host.
[Switch] info-center loghost 202.38.1.10 facility local7 [Switch] info-center source default channel loghost log level errors debug state off trap state off
2)
Step 2: Edit the file /etc/syslog.conf as the super user (root user) to add the following selector/action pairs.
# Switch configuration messages local7.info /var/log/Switch/information
Note the following items when you edit file /etc/syslog.conf. A note must start in a new line, starting with a #" sign. In each pair, a tab should be used as a separator instead of a space. No space is permitted at the end of the file name. The device name (facility) and received log information severity specified in file /etc/syslog.conf must be the same with those corresponding parameters configured in commands info-center loghost and info-center source. Otherwise, log information may not be output to the log host normally.
Step 3: After the log file information is created and the file /etc/syslog.conf is modified, execute the following commands to view the process ID of the system daemon syslogd, stop the process, and then restart the daemon "syslogd" in the background with the -r option.
# ps -ae | grep syslogd 147 # kill -9 147 # syslogd -r &
In case of Linux log host, the daemon syslogd must be started with the -r option. After all the above operations, the switch can record information in the corresponding log file.
1-17
Through combined configuration of the device name (facility), information severity level threshold (severity), module name (filter) and the file syslog.conf, you can sort information precisely for filtering.
Network diagram
Figure 1-3 Network diagram for log output to the console
Configuration procedure
# Enable the information center.
<Switch> system-view [Switch] info-center enable
# Enable log information output to the console. Permit ARP and IP modules to output log information with severity level higher than informational to the console.
[Switch] info-center console channel console [Switch] info-center source arp channel console log level informational debug state off trap state off [Switch] info-center source ip channel console log level informational debug state off trap state off
Configuration Example
Network requirements
The switch is in the time zone of GMT+ 08:00:00. The time stamp format of output log information is date. UTC time zone will be added to the output information of the information center.
1-18
Network diagram
Figure 1-4 Network diagram
Configuration procedure
# Name the local time zone z8 and configure it to be eight hours ahead of UTC time.
<Switch> clock timezone z8 add 08:00:00
# Set the time stamp format of the log information to be output to the log host to date.
<Switch> system-view System View: return to User View with Ctrl+Z. [Switch] info-center timestamp loghost date
# Configure to add UTC time to the output information of the information center.
[Switch] info-center timestamp utc
1-19
Table of Contents
1 Boot ROM and Host Software Loading 1-1 Introduction to Loading Approaches 1-1 Local Boot ROM and Software Loading1-1 BOOT Menu 1-2 Loading by XModem through Console Port 1-3 Loading by TFTP through Ethernet Port 1-7 Loading by FTP through Ethernet Port1-9 Remote Boot ROM and Software Loading 1-11 Remote Loading Using FTP 1-11 Remote Loading Using TFTP1-15 2 Basic System Configuration and Debugging 2-1 Basic System Configuration2-1 Displaying the System Status 2-2 Debugging the System2-2 Enabling/Disabling System Debugging 2-2 Displaying Debugging Status 2-3 Displaying Operating Information about Modules in System 2-3 3 Network Connectivity Test 3-1 Network Connectivity Test 3-1 ping 3-1 tracert3-1 4 Device Management 4-1 Introduction to Device Management 4-1 Device Management Configuration4-1 Device Management Configuration Task list4-1 Rebooting the Ethernet Switch4-1 Scheduling a Reboot on the Switch 4-2 Configuring Real-time Monitoring of the Running Status of the System4-2 Specifying the APP to be Used at Reboot4-3 Upgrading the Boot ROM 4-3 Identifying and Diagnosing Pluggable Transceivers 4-3 Displaying the Device Management Configuration4-5 Remote Switch APP Upgrade Configuration Example 4-5
The Boot ROM software version should be compatible with the host software version when you load the Boot ROM and host software.
1-1
The loading process of the Boot ROM software is the same as that of the host software, except that during the former process, you should press 6 or <Ctrl+U> and <Enter> after entering the BOOT menu and the system gives different prompts. The following text mainly describes the Boot ROM loading process.
BOOT Menu
Starting......
***********************************************************
Copyright (c) 2004-2007 3Com Corporation and its licensors. Creation date : Nov 20 2007, 17:02:48
CPU Clock Speed : 200MHz BUS Clock Speed : 33MHz Memory Size Mac Address : 64MB : 00e0fc005100
To enter the BOOT menu, you should press <Ctrl+B> within five seconds (full startup mode) or one second (fast startup mode) after the information Press Ctrl-B to enter BOOT Menu... displays. Otherwise, the system starts to extract the program; and if you want to enter the BOOT Menu at this time, you will have to restart the switch.
Enter the correct Boot ROM password (no password is set by default). The system enters the BOOT Menu:
BOOT MENU
1-2
2. Select application file to boot 3. Display all files in flash 4. Delete file from flash 5. Modify bootrom password 6. Enter bootrom upgrade menu 7. Skip current configuration file 8. Set bootrom password recovery 9. Set switch startup mode 0. Reboot
Step 2: Press 3 in the above menu to download the Boot ROM using XModem. The system displays the following setting menu for download baudrate:
Please select your download baudrate: 1.* 9600 2. 19200 3. 38400 4. 57600 5. 115200 0. Return
1-3
Step 3: Choose an appropriate baudrate for downloading. For example, if you press 5, the baudrate 115200 bps is chosen and the system displays the following information:
Download baudrate is 115200 bps Please change the terminal's baudrate to 115200 bps and select XMODEM protocol Press enter key when ready
If you have chosen 19,200 bps as the download baudrate, you need not modify the HyperTerminals baudrate, and therefore you can skip Step 4 and 5 below and proceed to Step 6 directly. In this case, the system will not display the above information.
Following are configurations on PC. Take the HyperTerminal in Windows 2000 as an example. Step 4: Choose [File/Properties] in HyperTerminal, click <Configure> in the pop-up dialog box, and then select the baudrate of 115200 bps in the Console port configuration dialog box that appears, as shown in Figure 1-1, Figure 1-2. Figure 1-1 Properties dialog box
1-4
Step 5: Click the <Disconnect> button to disconnect the HyperTerminal from the switch and then click the <Connect> button to reconnect the HyperTerminal to the switch, as shown in Figure 1-3. Figure 1-3 Connect and disconnect buttons
The new baudrate takes effect after you disconnect and reconnect the HyperTerminal program.
Step 6: Press <Enter> to start downloading the program. The system displays the following information:
Now please start transfer file with XMODEM protocol. If you want to exit, Press <Ctrl+X>. Loading ...CCCCCCCCCC
Step 7: Choose [Transfer/Send File] in HyperTerminal, and click <Browse> in pop-up dialog box, as shown in Figure 1-4. Select the software file that you need to load to the switch, and set the protocol to XModem.
1-5
Step 8: Click <Send>. The system displays the page, as shown in Figure 1-5. Figure 1-5 Sending file page
Step 9: After the sending process completes, the system displays the following information:
Loading ...CCCCCCCCCC done!
Step 10: Reset HyperTerminals baudrate to 19,200 bps (refer to Step 4 and 5). Then, press any key as prompted. The system will display the following information when it completes the loading.
Bootrom updating.....................................done!
If the HyperTerminals baudrate is not reset to 19,200 bps, the system prompts "Your baudrate should be set to 19,200 bps again! Press enter key when ready". You need not reset the HyperTerminals baudrate and can skip the last step if you have chosen 19,200 bps. In this case, the system upgrades the Boot ROM automatically and prompts Bootrom updating now.....................................done!.
1-6
Step 2: Enter 3 in the above menu to load the host software by using XModem. The subsequent steps are the same as those for loading the Boot ROM, except that the system gives the prompt for host software loading instead of Boot ROM loading.
You can also use the xmodem get command to load host software through the Console port (of AUX type). The load procedures are as follows (assume that the PC is connected to the Console port of the switch, and logs onto the switch through the Console port): Step 1: Execute the xmodem get command in user view. In this case, the switch is ready to receive files. Step 2: Enable the HyperTerminal on the PC, and configure XModem as the transfer protocol, and configure communication parameters on the Hyper Terminal the same as that on the Console port. Step 3: Choose the file to be loaded to the switch, and then start to transmit the file.
Step 1: As shown in Figure 1-6, connect the switch through an Ethernet port to the TFTP server, and connect the switch through the Console port to the configuration PC.
1-7
You can use one PC as both the configuration device and the TFTP server.
Step 2: Run the TFTP server program on the TFTP server, and specify the path of the program to be downloaded.
TFTP server program is not provided with the 3Com Series Ethernet Switches.
Step 3: Run the HyperTerminal program on the configuration PC. Start the switch. Then enter the BOOT Menu. At the prompt "Enter your choice(0-9):" in the BOOT Menu, press <6> or <Ctrl+U>, and then press <Enter> to enter the Boot ROM update menu shown below:
Bootrom update menu: 1. Set TFTP protocol parameter 2. Set FTP protocol parameter 3. Set XMODEM protocol parameter 0. Return to boot menu
Step 4: Enter 1 in the above menu to download the Boot ROM using TFTP. Then set the following TFTP-related parameters as required:
Load File name Switch IP address Server IP address :Switch.btm :1.1.1.2 :1.1.1.1
Step 6: Enter Y to start file downloading or N to return to the Boot ROM update menu. If you enter Y, the system begins to download and update the Boot ROM. Upon completion, the system displays the following information:
Loading........................................done Bootrom updating..........done!
1-8
Step 2: Enter 1 in the above menu to download the host software using TFTP. The subsequent steps are the same as those for loading the Boot ROM, except that the system gives the prompt for host software loading instead of Boot ROM loading.
When loading Boot ROM and host software using TFTP through BOOT menu, you are recommended to use the PC directly connected to the device as TFTP server to promote upgrading reliability.
Step 1: As shown in Figure 1-7, connect the switch through an Ethernet port to the FTP server, and connect the switch through the Console port to the configuration PC.
You can use one computer as both configuration device and FTP server.
Step 2: Run the FTP server program on the FTP server, configure an FTP user name and password, and copy the program file to the specified FTP directory. Step 3: Run the HyperTerminal program on the configuration PC. Start the switch. Then enter the BOOT Menu.
1-9
At the prompt "Enter your choice(0-9):" in the BOOT Menu, press <6> or <Ctrl+U>, and then press <Enter> to enter the Boot ROM update menu shown below:
Bootrom update menu: 1. Set TFTP protocol parameter 2. Set FTP protocol parameter 3. Set XMODEM protocol parameter 0. Return to boot menu
Step 4: Enter 2 in the above menu to download the Boot ROM using FTP. Then set the following FTP-related parameters as required:
Load File name Switch IP address Server IP address FTP User Name FTP User Password :switch.btm :10.1.1.2 :10.1.1.1 :Switch :abc
Step 6: Enter Y to start file downloading or N to return to the Boot ROM update menu. If you enter Y, the system begins to download and update the program. Upon completion, the system displays the following information:
Loading........................................done Bootrom updating..........done!
Loading host software Follow these steps to load the host software: Step 1: Select <1> in BOOT Menu and press <Enter>. The system displays the following information:
1. Set TFTP protocol parameter 2. Set FTP protocol parameter 3. Set XMODEM protocol parameter 0. Return to boot menu
Enter 2 in the above menu to download the host software using FTP. The subsequent steps are the same as those for loading the Boot ROM, except for that the system gives the prompt for host software loading instead of Boot ROM loading.
When loading the Boot ROM and host software using FTP through BOOT menu, you are recommended to use the PC directly connected to the device as FTP server to promote upgrading reliability.
1-10
As shown in Figure 1-8, a PC is used as both the configuration device and the FTP server. You can telnet to the switch, and then execute the FTP commands to download the Boot ROM program switch.btm from the remote FTP server (whose IP address is 10.1.1.1) to the switch. Figure 1-8 Remote loading using FTP Client
When using different FTP server software on PC, different information will be output to the switch.
1-11
<Sysname> reboot
Before restarting the switch, make sure you have saved all other configurations that you want, so as to avoid losing configuration information.
2)
Loading the host software is the same as loading the Boot ROM program, except that the file to be downloaded is the host software file, and that you need to use the boot boot-loader command to select the host software used for next startup of the switch. After the above operations, the Boot ROM and host software loading is completed. Pay attention to the following: The loading of Boot ROM and host software takes effect only after you restart the switch with the reboot command. If the space of the Flash memory is not enough, you can delete the unused files in the Flash memory before software downloading. For information about deleting files, refer to File System Management part of this manual. Ensure the power supply during software loading.
Step 1: As shown in Figure 1-9, connect the switch through an Ethernet port to the PC (whose IP address is 10.1.1.1) Step 2: Configure the IP address of VLAN-interface 1 on the switch to 192.168.0.28, and subnet mask to 255.255.255.0.
1-12
You can configure the IP address for any VLAN on the switch for FTP transmission. However, before configuring the IP address for a VLAN interface, you have to make sure whether the IP addresses of this VLAN and PC are routable.
<Sysname> system-view System View: return to User View with Ctrl+Z. [Sysname] interface Vlan-interface 1 [Sysname-Vlan-interface1] ip address 192.168.0.28 255.255.255.0
Step 3: Enable FTP service on the switch, and configure the FTP user name to test and password to pass.
[Sysname-Vlan-interface1] quit [Sysname] ftp server enable [Sysname] local-user test New local user added. [Sysname-luser-test] password simple pass [Sysname-luser-test] service-type ftp
Step 4: Enable FTP client software on the PC. Refer to Figure 1-10 for the command line interface in Windows operating system. Figure 1-10 Command line interface
Step 5: Use the cd command on the interface to enter the path that the Boot ROM upgrade file is to be stored. Assume the name of the path is D:\Bootrom, as shown in Figure 1-110.
1-13
Step 6: Enter ftp 192.168.0.28 and enter the user name test, password pass, as shown in Figure 1-12, to log on to the FTP server. Figure 1-12 Log on to the FTP server
Step 7: Use the put command to upload the file switch.btm to the switch, as shown in Figure 1-13.
1-14
Step 8: Configure switch.btm to be the Boot ROM at next startup, and then restart the switch.
<Sysname> boot bootrom switch.btm This will update Bootrom on unit 1. Upgrading Bootrom, please wait... Upgrade Bootrom succeeded! <Sysname> reboot Continue? [Y/N] y
After the switch restarts, the file switch.btm is used as the Boot ROM. It indicates that the Boot ROM loading is finished. 2) Loading host software
Loading the host software is the same as loading the Boot ROM program, except that the file to be downloaded is the host software file, and that you need to use the boot boot-loader command to select the host software used for the next startup of the switch.
The steps listed above are performed in the Windows operating system, if you use other FTP client software, refer to the corresponding user guide before operation. Only the configuration steps concerning loading are listed here. For detailed description on the corresponding configuration commands, refer to FTP-SFTP-TFTP part of this manual.
1-15
clock summer-time zone_name { one-off | repeating } start-time start-date end-time end-date offset-time
Enter system view from user view Set the system name of the switch Return from current view to lower level view
2-1
Remarks
The composite key <Ctrl+Z> has the same effect with the return command.
ON
OFF
ON
OFF
ON
OFF
ON
1 3
2-2
Displaying debugging information on the terminal is the most commonly used way to output debugging information. You can also output debugging information to other directions. For details, refer to Information Center Operation.
You can use the following commands to enable the two switches. Follow these steps to enable debugging and terminal display for a specific module: To do Enable system debugging for specific module Enable terminal display for debugging Use the command debugging module-name [ debugging-option ] Required Disabled for all modules by default. Required Disabled by default. Remarks
terminal debugging
The output of debugging information affects the system operation. Disable all debugging after you finish the system debugging.
Display the current operation information about the modules in the system.
2-3
3
ping
You can use the ping command to check the network connectivity and the reachability of a host. To do Check the IP network connectivity and the reachability of a host Use the command ping [ -a ip-address ] [-c count ] [ -d ] [ -f ] [ -h ttl ] [ -i interface-type interface-number ] [ ip ] [ -n ] [ - p pattern ] [ -q ] [ -s packetsize ] [ -t timeout ] [ -tos tos ] [ -v ] host Remarks You can execute this command in any view.
This command can output the following results: Response status for each ping packet. If no response packet is received within the timeout time, the message "Request time out" is displayed. Otherwise, the number of data bytes, packet serial number, time to live (TTL) and response time of the response packet are displayed. Final statistics, including the numbers of sent packets and received response packets, the irresponsive packet percentage, and the minimum, average and maximum values of response time.
tracert
You can use the tracert command to trace the gateways that a packet passes from the source to the destination. This command is mainly used to check the network connectivity. It can also be used to help locate the network faults. The executing procedure of the tracert command is as follows: First, the source host sends a data packet with the TTL of 1, and the first hop device returns an ICMP error message indicating that it cannot forward this packet because of TTL timeout. Then, the source host resends the packet with the TTL of 2, and the second hop device also returns an ICMP TTL timeout message. This procedure goes on and on until the packet gets to the destination. During the procedure, the system records the source address of each ICMP TTL timeout message in order to offer the path that the packet passed through to the destination. To do View the gateways that a packet passes from the source host to the destination Use the command tracert [ -a source-ip ] [ -f first-ttl ] [ -m max-ttl ] [ -p port ] [ -q num-packet ] [ -w timeout ] string Remarks You can execute the tracert command in any view.
3-1
Device Management
When configuring device management, go to these sections for information you are interested in: Introduction to Device Management Device Management Configuration Displaying the Device Management Configuration Remote Switch APP Upgrade Configuration Example
4-1
Before rebooting, the system checks whether there is any configuration change. If yes, it prompts whether or not to proceed. This prevents the system from losing the configurations in case of shutting down the system without saving the configurations
Use the following command to reboot the Ethernet switch: To do Reboot the Ethernet switch Use the command reboot [ unit unit-id ] Remarks Available in user view
The switch timer can be set to precision of one minute, that is, the switch will reboot within one minute after the specified reboot date and time.
4-2
Enabling of this function consumes some amounts of CPU resources. Therefore, if your network has a high CPU usage requirement, you can disable this function to release your CPU resources.
Yes
Yes
Yes
Yes
4-3
Transceiver type XFP (10-Gigabit small Form-factor Pluggable) XENPAK (10 Gigabit EtherNet Transceiver Package)
Applied environment Generally used for 10G Ethernet interfaces Generally used for 10G Ethernet interfaces
Yes
Yes
You can use the Vendor Name field in the prompt information of the display transceiver interface command to identify an anti-spoofing pluggable transceiver customized by H3C. If the field is H3C, it is considered an H3C-customized pluggable transceiver. Electrical label information is also called permanent configuration data or archive information, which is written to the storage device of a card during device debugging or test. The information includes name of the card, device serial number, and vendor name or vendor name specified.
4-4
To do Display the currently measured value of the digital diagnosis parameters of the anti-spoofing optical transceiver(s) customized by H3C
Remarks
display diagnostic-information
4-5
The host software switch.app and the Boot ROM file boot.btm of the switch are stored in the directory switch on the PC. Use FTP to download the switch.app and boot.btm files from the FTP server to the switch.
Network diagram
Figure 4-1 Network diagram for FTP configuration
Configuration procedure
1) Configure the following FTP serverrelated parameters on the PC: an FTP user with the username as switch and password as hello, who is authorized with the read-write right on the directory Switch on the PC. The detailed configuration is omitted here. 2) On the switch, configure a level 3 telnet user with the username as user and password as hello. Authentication mode is by user name and password.
Refer to the Login Operation part of this manual for configuration commands and steps about telnet user.
3)
Execute the telnet command on the PC to log into the switch. The following prompt appears:
<Sysname>
If the Flash memory of the switch is not sufficient, delete the original applications before downloading the new ones.
4)
Initiate an FTP connection with the following command in user view. Enter the correct user name and password to log into the FTP server.
<Sysname> ftp 2.2.2.2 Trying ... Press CTRL+K to abort Connected. 220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user User(none):switch 331 Give me your password, please Password: 230 Logged in successfully
4-6
[ftp]
5) 6)
Enter the authorized path on the FTP server. Execute the get command to download the switch.app and boot.btm files on the FTP server to the Flash memory of the switch.
[ftp] cd switch
7)
Execute the quit command to terminate the FTP connection and return to user view.
8)
<Sysname> boot bootrom boot.btm This will update BootRom file on unit 1. Continue? [Y/N] y Upgrading BOOTROM, please wait... Upgrade BOOTROM succeeded!
9)
Specify the downloaded program as the host software to be adopted when the switch starts next time.
<Sysname> boot boot-loader switch.app The specified file will be booted next time on unit 1! <Sysname> display boot-loader Unit 1: The current boot app is: switch.app The main boot app is: The backup boot app is: switch.app
# Reboot the switch to upgrade the Boot ROM and host software of the switch.
<Sysname> reboot Start to check configuration with next startup configuration file, please wait...... This command will reboot the device. Current configuration may be lost in next startup if you continue. Continue? [Y/N] y
4-7
Table of Contents
1 remote-ping Configuration 1-1 remote-ping Overview 1-1 Introduction to remote-ping 1-1 Test Types Supported by remote-ping 1-2 remote-ping Test Parameters1-2 remote-ping Configuration 1-4 remote-ping Server Configuration 1-4 remote-ping Client Configuration1-4 Displaying remote-ping Configuration 1-15 remote-ping Configuration Examples1-15 ICMP Test1-15 DHCP Test 1-17 FTP Test1-18 HTTP Test 1-20 Jitter Test1-22 SNMP Test 1-24 TCP Test (Tcpprivate Test) on the Specified Ports1-26 UDP Test (Udpprivate Test) on the Specified Ports1-28 DNS Test 1-30
remote-ping Configuration
When configuring remote-ping, go to these sections for information you are interested in: remote-ping Overview remote-ping Configuration remote-ping Configuration Examples
remote-ping Overview
Introduction to remote-ping
remote-ping is a network diagnostic tool. It is used to test the performance of various protocols running in networks. remote-ping provides more functions than the ping command. The ping command can only use the ICMP protocol to test the round trip time (RTT) between this end and a specified destination end for the user to judge whether the destination end is reachable. Besides the above function of the ping command, remote-ping can also provide other functions, such as testing the status (open/close) of a DHCP/FTP/HTTP/SNMP server and the response time of various services. You need to configure remote-ping client and sometimes the corresponding remote-ping servers as well to perform various remote-ping tests. All remote-ping tests are initiated by a remote-ping client and you can view the test results on the remote-ping client only. When performing a remote-ping test, you need to configure a remote-ping test group on the remote-ping client. A remote-ping test group is a set of remote-ping test parameters. A test group contains several test parameters and is uniquely identified by an administrator name and a test tag. After creating a remote-ping test group and configuring the test parameters, you can then perform a remote-ping test by the test-enable command. Being different from the ping command, remote-ping does not display the RTT or timeout status of each packet on the Console terminal in real time. To view the statistic results of your remote-ping test operation, you need to execute the display remote-ping command. remote-ping also allows you to set parameters for remote-ping test groups, start remote-ping tests and view statistical test results through a network management device. Figure 1-1 remote-ping illustration
1-1
1-2
Test parameter
Description You can use remote-ping to test a variety of protocols, see Table 1-1 for details. To perform a type of test, you must first create a test group of this type. One test group can be of only one remote-ping test type. If you modify the test type of a test group using the test-type command, the parameter settings, test results, and history records of the original test type will be all cleared. For tests except jitter test, only one test packet is sent in a probe. In a jitter test, you can use the jitter-packetnum command to set the number of packets to be sent in a probe. For ICMP/UDP/jitter test, you can configure the size of test packets. For ICMP test, the ICMP packet size refers to the length of ECHO-REQUEST packets (excluding IP and ICMP headers) This parameter is used to specify the maximum number of history records that can be saved in a test group. When the number of saved history records exceeds the maximum number, remote-ping discards some earliest records. This parameter is used to set the interval at which the remote-ping client periodically performs the same test automatically. The probe timeout timer is started after the remote-ping client sends out a test packet. This parameter is in seconds. Type of service is the value of the ToS field in IP header in the test packets. This parameter is used to specify a DNS domain name in a remote-ping DNS test group. This parameter is used to set the DNS server IP address in a remote-ping DNS test group. This parameter is used to set the type of HTTP interaction operation between remote-ping client and HTTP server. This parameter is used to set the type of FTP interaction operation between remote-ping client and FTP server. The two parameters are used to set the username and password to be used for FTP operation. Name of a file to be transferred between remote-ping client and FTP server Jitter test is used to collect statistics about delay jitter in UDP packet transmission In a jitter probe, the remote-ping client sends a series of packets to the remote-ping server at regular intervals (you can set the interval). Once receiving such a packet, the remote-ping server marks it with a timestamp, and then sends it back to the remote-ping client. Upon receiving a packet returned, the remote-ping client computes the delay jitter time. The remote-ping client collects delay jitter statistics on all the packets returned in the test. So, the more packets a jitter probe sends, the more accurate the jitter statistics is, but the longer time the jitter test costs. Each jitter probe will send multiple UDP test packets at regular intervals (you can set the interval). The smaller the interval is, the faster the test is. But a too small interval may somewhat impact your network.
Packet size (datasize) Maximum number of history records that can be saved (history-records) Automatic test interval (frequency) Probe timeout time (timeout) Type of service (tos) dns dns-server HTTP operation type (http-operation) FTP operation type (ftp-operation) FTP login username and password (username and password) File name for FTP operation (filename)
1-3
Test parameter
Description A remote-ping test will generate a Trap message no matter whether the test successes or not. You can use the Trap switch to enable or disable the output of trap messages. You can set the number of consecutive failed remote-ping tests before Trap output. You can also set the number of consecutive failed remote-ping probes before Trap output.
Trap
remote-ping Configuration
The TCP/UDP/jitter tests need the cooperation of remote-ping client and remote-ping server. Other types of tests need to configure remote-ping client and corresponding different servers. You can enable both the remote-ping client and remote-ping server functions on an Switch 4200G, that is, the switch can serve as a remote-ping client and server simultaneously.
Note that: The remote-ping server function is needed only for jitter, TCP, and UDP tests. You can configure multiple TCP/UDP listening services on one remote-ping server, with each listening service corresponding to a specific destination IP address and port number.
1)
Follow these steps to configure ICMP test on remote-ping client: To do Enter system view Enable the remote-ping client function Create a remote-ping test group and enter its view Configure the destination IP address Use the command system-view remote-ping-agent enable remote-ping administrator-name operation-tag destination-ip ip-address Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required By default, no destination address is configured. Optional source-ip ip-address By default, no source IP address is configured. Optional By default, the test type is ICMP. Optional By default, each test makes one probe. Optional By default, the packet size is 56 bytes. Optional By default, the maximum number is 50. Optional Configure the automatic test interval frequency interval By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional timeout time By default, a probe times out in three seconds. Optional By default, the service type is zero. Required Required Available in any view. Remarks
Configure the test type Configure the number of probes per test Configure the packet size Configure the maximum number of history records that can be saved
test-type icmp
count times
datasize size
history-records number
Configure the probe timeout time Configure the type of service (ToS) Start the test Display test results
2)
Follow these steps to configure DHCP test on remote-ping client: To do Enter system view Use the command system-view Remarks
1-5
To do Enable the remote-ping client function Create a remote-ping test group and enter its view
Remarks
By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required
You can only configure a VLAN interface as the source interface. By default, no source interface is configured. Required By default, the test type is ICMP. Optional By default, each test makes one probe. Optional By default, the maximum number is 50. Optional
Configure the test type Configure the number of probes per test Configure the maximum number of history records that can be saved Configure the probe timeout time Start the test Display test results
test-type dhcp
count times
history-records number
By default, a probe times out in three seconds. Required Required You can execute the command in any view.
3)
Follow these steps to configure FTP test on remote-ping client: To do Enter system view Enable the remote-ping client function Create a remote-ping test group and enter its view Configure the destination IP address Use the command system-view remote-ping-agent enable remote-ping administrator-name operation-tag destination-ip ip-address Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required By default, no destination address is configured. Required source-ip ip-address By default, no source IP address is configured. Optional By default, no source port is configured. Remarks
source-port port-number
1-6
To do Configure the test type Configure the number of probes per test Configure the maximum number of history records that can be saved Configure the automatic test interval
Remarks
By default, the test type is ICMP. Optional By default, each test makes one probe. Optional By default, the maximum number is 50. Optional
count times
history-records number
frequency interval
By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional
timeout time
By default, a probe times out in three seconds. Optional By default, the service type is zero. Optional
tos value
Configure the type of FTP operation Configure an FTP login username Configure an FTP login password Configure a file name for the FTP operation Start the test Display test results
By default, the type of FTP operation is get, that is, the FTP operation will get a file from the FTP server. Required By default, neither username nor password is configured. Required
By default, no file name is configured for the FTP operation Required Required You can execute the command in any view.
4)
Follow these steps to configure HTTP test on remote-ping client: To do Enter system view Enable the remote-ping client function Create a remote-ping test group and enter its view Use the command system-view remote-ping-agent enable remote-ping administrator-name operation-tag Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Remarks
1-7
To do
Remarks
destination-ip ip-address
You can configure an IP address or a host name. By default, no destination address is configured. Required when you use the destination-ip command to configure the destination address as the host name. By default, no IP address of the DNS server is configured.
Configure dns-server
dns-server ip-address
Configure the source IP address Configure the source port Configure the test type Configure the number of probes per test Configure the maximum number of history records that can be saved Configure the automatic test interval
Optional source-ip ip-address By default, no source IP address is configured. Optional By default, no source port is configured. Required By default, the test type is ICMP. Optional By default, each test makes one probe. Optional By default, the maximum number is 50. Optional frequency interval By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional timeout time By default, a probe times out in three seconds. Optional By default, the service type is zero. Optional
source-port port-number
test-type http
count times
history-records number
tos value
By default, the type of HTTP operation is get, that is, the HTTP operation will get data from the HTTP server. Optional
Configure the HTTP operation string and HTTP version Start the test Display test results
By default, no HTTP operation string and HTTP version are configured. Required Required You can execute the command in any view.
5)
1-8
Follow these steps to configure jitter test on remote-ping client: To do Enter system view Enable the remote-ping client function Use the command system-view remote-ping-agent enable Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required Configure the destination IP address The destination address must be the IP address of a UDP listening service on the remote-ping server. By default, no destination address is configured. Required destination-port Port-number The destination port must be the port of a UDP listening service on the remote-ping server. By default, no destination port is configured. Configure the source IP address Optional source-ip ip-address By default, no source IP address is configured. Optional Configure the source port source-port port-number By default, no source port is configured. Required Configure the test type test-type jitter By default, the test type is ICMP. Optional count times By default, each test makes one probe. Optional history-records number By default, the maximum number is 50. Optional Configure the packet size datasize size By default, the packet size is 68 bytes. Optional Configure the automatic test interval frequency interval By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional timeout time By default, a probe times out in three seconds. Remarks
destination-ip ip-address
Configure the number of probes per test Configure the maximum number of history records that can be saved
1-9
Remarks
Configure the number of test packets that will be sent in each jitter probe Configure the interval to send test packets in the jitter test Start the test Display test results
jitter-packetnum number
By default, the interval is 20 milliseconds. Required Required You can execute the command in any view.
6)
Follow these steps to configure SNMP test on remote-ping client: To do Enter system view Enable the remote-ping client function Use the command system-view remote-ping-agent enable Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required destination-ip ip-address By default, no destination address is configured. Optional source-ip ip-address By default, no source IP address is configured. Optional Configure the source port source-port port-number By default, no source port is configured. Required Configure the test type test-type snmpquery By default, the test type is ICMP. Optional count times By default, each test makes one probe. Optional history-records number By default, the maximum number is 50. Remarks
Configure the number of probes per test Configure the maximum number of history records that can be saved
1-10
To do
Remarks
frequency interval
By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional
timeout time
Configure the type of service Start the test Display test results
By default, the service type is zero. Required Required You can execute the command in any view.
7)
Follow these steps to configure TCP test on remote-ping client: To do Enter system view Enable the remote-ping client function Create a remote-ping test group and enter its view Use the command system-view remote-ping-agent enable remote-ping administrator-name operation- tag Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required Configure the destination address destination-ip ip-address This IP address and the one configured on the remote-ping server for listening services must be the same. By default, no destination address is configured. Required in a Tcpprivate test A Tcppublic test is a TCP connection test on port 7. Use the remote-ping-server tcpconnect ip-address 7 command on the server to configure the listening service port; otherwise the test will fail. No port number needs to be configured on the client; any destination port number configured on the client will not take effect. By default, no destination port number is configured. Configure the source IP address Optional source-ip ip-address By default, the source IP address is not specified. Remarks
destination-port port-number
1-11
To do Configure the source port Configure the test type Configure the number of probes per test
Use the command source-port port-number test-type { tcpprivate | tcppublic } count times Optional
Remarks
By default, no source port is specified. Required By default, the test type is ICMP. Optional By default, one probe is made per time. Optional
frequency interval
By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional
Configure the probe timeout time Configure the maximum number of history records that can be saved Configure the type of service Start the test Display test results
timeout time
By default, a probe times out in three seconds. Optional By default, the maximum number is 50. Optional By default, the service type is zero. Required Required The display command can be executed in any view.
history-records number
8)
Follow these steps to configure UDP test on remote-ping client: To do Enter system view Enable the remote-ping client function Create a remote-ping test group and enter its view Use the command system-view remote-ping-agent enable remote-ping administrator-name operation- tag Required By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required Configure the destination address destination-ip ip-address This IP address and the one configured on the remote-ping server for listening service must be the same. By default, no destination address is configured. Remarks
1-12
To do
Remarks Required in a Udpprivate test A Udppublic test is a UDP connection test on port 7. Use the remote-ping-server udpecho ip-address 7 command on the server to configure the listening service port; otherwise the test will fail. No port number needs to be configured on the client; any destination port number configured on the client will not take effect. By default, no destination port number is configured. Optional By default, no source IP address is configured. Optional By default, no source port is specified. Required By default, the test type is ICMP. Optional By default, one probe is made per test. Optional By default, the maximum number is 50. Optional
destination-port port-number
Configure the source IP address Configure the source port Configure the test type Configure the number of probes per test Configure the maximum number of history records that can be saved Configure the data packet size
source-ip ip-address
history-records number
datasize size
frequency interval
By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional
Configure the probe timeout time Configure the service type Start the test Display test results
timeout time
By default, a probe times out in three seconds. Optional By default, the service type is zero. Required Required The display command can be executed in any view.
9)
Follow these steps to configure DNS test on remote-ping client: To do Enter system view Use the command system-view Remarks
1-13
Remarks
By default, the remote-ping client function is disabled. Required By default, no test group is configured. Optional
source-ip ip-address
test-type dns
Configure the number of probes per test Configure the maximum number of history records that can be saved
count times
history-records number
frequency interval
By default, the automatic test interval is zero seconds, indicating no automatic test will be made. Optional
timeout time
tos value
Configure the IP address of the DNS server Start the test Display test results
By default, no DNS server address is configured. Required Required The display command can be executed in any view.
Remarks
By default, the remote-ping client function is disabled. Required By default, no test group is configured. Required By default, Trap sending is disabled. Optional
Enable the remote-ping client to send Trap messages Configure the number of consecutive unsuccessful remote-ping tests before Trap output Configure the number of consecutive unsuccessful remote-ping probes before Trap output
test-failtimes times
By default, Trap messages are sent each time a test fails. Optional
probe-failtimes times
Network diagram
Figure 1-2 Network diagram for the ICMP test
1-15
Configuration procedure
Configure remote-ping Client (Switch A): # Enable the remote-ping client.
<Sysname> system-view [Sysname] remote-ping-agent enable
# Create a remote-ping test group, setting the administrator name to administrator and test tag to ICMP.
[Sysname] remote-ping administrator icmp
Min/Max/Average Round Trip Time: 3/6/3 Square-Sum of Round Trip Time: 145 Last succeeded test time: 2000-4-2 20:55:12.3 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 [Sysname-remote-ping-administrator-icmp] display remote-ping history administrator icmp remote-ping entry(admin administrator, tag icmp) history record: Index 1 2 3 4 Response 3 4 4 3 Status 1 1 1 1 LastRC 0 0 0 0 Time 2000-04-02 20:55:12.3 2000-04-02 20:55:12.3 2000-04-02 20:55:12.2 2000-04-02 20:55:12.2 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
1-16
2000-04-02 20:55:12.2
DHCP Test
Network requirements
Both the remote-ping client and the DHCP server are 4200G Ethernet switches. Perform a remote-ping DHCP test between the two switches to test the time required for the remote-ping client to obtain an IP address from the DHCP server.
Network diagram
Figure 1-3 Network diagram for the DHCP test
Configuration procedure
Configure DHCP Server(Switch B): Configure DHCP server on Switch B. For specific configuration of DHCP server, refer to the DHCP part of the manual. Configure remote-ping Client (Switch A): # Enable the remote-ping client.
<Sysname> system-view [Sysname] remote-ping-agent enable
# Create a remote-ping test group, setting the administrator name to administrator and test tag to DHCP.
[Sysname] Remote-ping administrator dhcp
# Configure the source interface, which must be a VLAN interface. Make sure the DHCP server resides on the network connected to this interface.
[Sysname-remote-ping-administrator-dhcp] source-interface Vlan-interface 1
1-17
remote-ping entry(admin administrator, tag dhcp) test result: Send operation times: 10 Receive response times: 10
Min/Max/Average Round Trip Time: 1018/1037/1023 Square-Sum of Round Trip Time: 10465630 Last complete test time: 2000-4-3 9:51:30.9 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 [Sysname-remote-ping-administrator-dhcp] display remote-ping history administrator dhcp remote-ping entry(admin administrator, tag dhcp) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 1018 1037 1024 1027 1018 1020 1018 1020 1020 1028 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-03 09:51:30.9 2000-04-03 09:51:22.9 2000-04-03 09:51:18.9 2000-04-03 09:51:06.8 2000-04-03 09:51:00.8 2000-04-03 09:50:52.8 2000-04-03 09:50:48.8 2000-04-03 09:50:36.8 2000-04-03 09:50:30.8 2000-04-03 09:50:22.8 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
You can perform a remote-ping DHCP test only when no DHCP client is enabled on any interface. Otherwise, the DHCP Server sends the response to an interface enabled with the DHCP Client rather than to the source interface, thus resulting in remote-ping DHCP test failure.
FTP Test
Network requirements
Both the remote-ping client and the FTP server are 4200G Ethernet switches. Perform a remote-ping FTP test between the two switches to test the connectivity to the specified FTP server and the time required to upload a file to the server after the connection is established. Both the username and password used to log in to the FTP server are admin. The file to be uploaded to the server is cmdtree.txt.
1-18
Network diagram
Figure 1-4 Network diagram for the FTP test
Configuration procedure
Configure FTP Server (Switch B): Configure FTP server on Switch B. For specific configuration of FTP server, refer to the FTP-SFTP-TFTP part of the manual. Configure remote-ping Client (Switch A): # Enable the remote-ping client.
<Sysname> system-view [Sysname] remote-ping-agent enable
# Create a remote-ping test group, setting the administrator name to administrator and test tag to FTP.
[Sysname] remote-ping administrator ftp
1-19
[Sysname-remote-ping-administrator-ftp] display remote-ping results administrator ftp remote-ping entry(admin administrator, tag ftp) test result: Destination ip address:10.2.2.2 Send operation times: 10 Receive response times: 10
Min/Max/Average Round Trip Time: 3245/15891/12157 Square-Sum of Round Trip Time: 1644458573 Last complete test time: 2000-4-3 4:0:34.6 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 [Sysname-remote-ping-administrator-ftp] display remote-ping history administrator ftp remote-ping entry(admin administrator, tag ftp) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 15822 15772 9945 15891 15772 15653 9792 9794 9891 3245 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-03 04:00:34.6 2000-04-03 04:00:18.8 2000-04-03 04:00:02.9 2000-04-03 03:59:52.9 2000-04-03 03:59:37.0 2000-04-03 03:59:21.2 2000-04-03 03:59:05.5 2000-04-03 03:58:55.6 2000-04-03 03:58:45.8 2000-04-03 03:58:35.9 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
If you are downloading a file from the server, you do not need to specify an FTP operation type. For details, see section Configuring FTP test on remote-ping client.
HTTP Test
Network requirements
An Switch 4200G serves as the remote-ping client, and a PC serves as the HTTP server. Perform a remote-ping HTTP test between the switch and the HTTP server to test the connectivity and the time required to download a file from the HTTP server after the connection to the server is established.
1-20
Network diagram
Figure 1-5 Network diagram for the HTTP test
Configuration procedure
Configure HTTP Server: Use Windows 2003 Server as the HTTP server. For HTTP server configuration, refer to the related instruction on Windows 2003 Server configuration. Configure remote-ping Client (Switch A): # Enable the remote-ping client.
<Sysname> system-view [Sysname] remote-ping-agent enable
# Create a remote-ping test group, setting the administrator name to administrator and test tag to HTTP.
[Sysname] Remote-ping administrator http
Min/Max/Average Round Trip Time: 47/87/74 Square-Sum of Round Trip Time: 57044 Last succeeded test time: 2000-4-2 20:41:50.4 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 Operation timeout number: 0 DS Maximal delay: 0
1-21
System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 Http result: DNS Resolve Time: 0 DNS Resolve Min Time: 0 DNS Resolve Max Time: 0 DNS Resolve Failed Times: 0 DNS Resolve Timeout Times: 0 TCP Connect Time: 73 TCP Connect Min Time: 5 TCP Connect Max Time: 20 TCP Connect Timeout Times: 0
HTTP Operation Time: 675 HTTP Test Total Time: 748 HTTP Transmission Successful Times: 10 HTTP Transmission Failed Times: 0 HTTP Transmission Timeout Times: 0 HTTP Operation Min Time: 27 HTTP Operation Max Time: 80
[Sysname-remote-ping-administrator-http] display remote-ping history administrator http remote-ping entry(admin administrator, tag http) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 13 9 3 3 3 2 3 3 2 2 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-02 15:15:52.5 2000-04-02 15:15:52.5 2000-04-02 15:15:52.5 2000-04-02 15:15:52.5 2000-04-02 15:15:52.5 2000-04-02 15:15:52.4 2000-04-02 15:15:52.4 2000-04-02 15:15:52.4 2000-04-02 15:15:52.4 2000-04-02 15:15:52.4
For an HTTP test, if configuring the destination address as the host name, you must configure the IP address of the DNS server to resolve the host name into an IP address, which is the destination IP address of this HTTP test.
Jitter Test
Network requirements
Both the remote-ping client and the remote-ping server are 4200G Ethernet switches. Perform a remote-ping jitter test between the two switches to test the delay jitter of the UDP packets exchanged between this end (remote-ping client) and the specified destination end (remote-ping server).
1-22
Network diagram
Figure 1-6 Network diagram for the Jitter test
Configuration procedure
Configure remote-ping Server (Switch B): # Enable the remote-ping server and configure the IP address and port to listen on.
<Sysname> system-view [Sysname] remote-ping-server enable [Sysname] remote-ping-server udpecho 10.2.2.2 9000
# Create a remote-ping test group, setting the administrator name to administrator and test tag to Jitter.
[Sysname] remote-ping administrator Jitter
Min/Max/Average Round Trip Time: 9/21/13 Square-Sum of Round Trip Time: 18623
1-23
Last complete test time: 2000-4-2 8:14:58.2 Extend result: SD Maximal delay: 10 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 Jitter result: RTT Number:100 Min Positive SD:1 Max Positive SD:6 Positive SD Number:38 Positive SD Sum:85 Positive SD average:2 Positive SD Square Sum:267 Min Negative SD:1 Max Negative SD:6 Negative SD Number:30 Negative SD Sum:64 Negative SD average:2 Negative SD Square Sum:200 SD lost packets number:0 Unknown result lost packet number:0 [Sysname-remote-ping-administrator-Jitter] Jitter remote-ping entry(admin administrator, tag Jitter) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 274 278 280 279 280 270 275 263 270 275 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-02 08:14:58.2 2000-04-02 08:14:57.9 2000-04-02 08:14:57.6 2000-04-02 08:14:57.3 2000-04-02 08:14:57.1 2000-04-02 08:14:56.8 2000-04-02 08:14:56.5 2000-04-02 08:14:56.2 2000-04-02 08:14:56.0 2000-04-02 08:14:55.7 display remote-ping history administrator Min Positive DS:1 Max Positive DS:8 Positive DS Number:25 Positive DS Sum:42 Positive DS average:1 Positive DS Square Sum:162 Min Negative DS:1 Max Negative DS:8 Negative DS Number:24 Negative DS Sum: 41 Negative DS average:1 Negative DS Square Sum:161 DS lost packet number:0 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 10
SNMP Test
Network requirements
Both the remote-ping client and the SNMP Agent are 4200G Ethernet switches. Perform remote-ping SNMP tests between the two switches to test the time required from Switch A sends an SNMP query message to Switch B (SNMP Agent) to it receives a response from Switch B.
1-24
Network diagram
Figure 1-7 Network diagram for the SNMP test
Configuration procedure
Configure SNMP Agent (Switch B): # Start SNMP agent and set SNMP version to V2C, read-only community name to public, and read-write community name to private.
<Sysname> system-view [Sysname] snmp-agent [Sysname] snmp-agent sys-info version v2c [Sysname] snmp-agent community read public [Sysname] snmp-agent community write private
The SNMP network management function must be enabled on SNMP agent before it can receive response packets. The SNMPv2c version is used as reference in this example. This configuration may differ if the system uses any other version of SNMP. For details, see SNMP RMON Operation Manual.
# Create a remote-ping test group, setting the administrator name to administrator and test tag to snmp.
[Sysname] Remote-ping administrator snmp
1-25
Min/Max/Average Round Trip Time: 9/11/10 Square-Sum of Round Trip Time: 983 Last complete test time: 2000-4-3 8:57:20.0 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 [Sysname-remote-ping-administrator-snmp] display remote-ping history administrator snmp remote-ping entry(admin administrator, tag snmp) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 10 10 10 10 9 11 10 10 10 10 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-03 08:57:20.0 2000-04-03 08:57:20.0 2000-04-03 08:57:20.0 2000-04-03 08:57:19.9 2000-04-03 08:57:19.9 2000-04-03 08:57:19.9 2000-04-03 08:57:19.9 2000-04-03 08:57:19.9 2000-04-03 08:57:19.8 2000-04-03 08:57:19.8 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
Network diagram
Figure 1-8 Network diagram for the Tcpprivate test
1-26
Configuration procedure
Configure remote-ping Server (Switch B): # Enable the remote-ping server and configure the IP address and port to listen on.
<Sysname> system-view [Sysname] remote-ping-server enable [Sysname] remote-ping-server tcpconnect 10.2.2.2 8000
# Create a remote-ping test group, setting the administrator name to administrator and test tag to tcpprivate.
[Sysname] remote-ping administrator tcpprivate
Min/Max/Average Round Trip Time: 4/7/5 Square-Sum of Round Trip Time: 282 Last complete test time: 2000-4-2 8:26:2.9 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
1-27
[Sysname-remote-ping-administrator-tcpprivate] display remote-ping history administrator tcpprivate remote-ping entry(admin administrator, tag tcpprivate) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 4 5 4 5 4 5 6 7 5 7 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-02 08:26:02.9 2000-04-02 08:26:02.8 2000-04-02 08:26:02.8 2000-04-02 08:26:02.7 2000-04-02 08:26:02.7 2000-04-02 08:26:02.6 2000-04-02 08:26:02.6 2000-04-02 08:26:02.5 2000-04-02 08:26:02.5 2000-04-02 08:26:02.4
Network diagram
Figure 1-9 Network diagram for the Udpprivate test
Configuration procedure
Configure remote-ping Server (Switch B): # Enable the remote-ping server and configure the IP address and port to listen on.
<Sysname> system-view [Sysname] remote-ping-server enable [Sysname] remote-ping-server udpecho 10.2.2.2 8000
# Create a remote-ping test group, setting the administrator name to administrator and test tag to udpprivate.
[Sysname] remote-ping administrator udpprivate
Min/Max/Average Round Trip Time: 10/12/10 Square-Sum of Round Trip Time: 1170 Last complete test time: 2000-4-2 8:29:45.5 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 [Sysname-remote-ping-administrator-udpprivate] display remote-ping history administrator udpprivate remote-ping entry(admin administrator, tag udpprivate) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 11 12 11 11 11 11 10 10 10 11 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2000-04-02 08:29:45.5 2000-04-02 08:29:45.4 2000-04-02 08:29:45.4 2000-04-02 08:29:45.4 2000-04-02 08:29:45.4 2000-04-02 08:29:45.4 2000-04-02 08:29:45.3 2000-04-02 08:29:45.3 2000-04-02 08:29:45.3 2000-04-02 08:29:45.3 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
1-29
DNS Test
Network requirements
An Switch 4200G serves as the remote-ping client, and a PC serves as the DNS server. Perform a remote-ping DNS test between the switch and the DNS server to test the time required from the client sends a DNS request to it receives a resolution result from the DNS server.
Network diagram
Figure 1-10 Network diagram for the DNS test
Configuration procedure
Configure DNS Server: Use Windows 2003 Server as the DNS server. For DNS server configuration, refer to the related instruction on Windows 2003 Server configuration. Configure remote-ping Client (Switch A) # Enable the remote-ping client.
<Sysname> system-view [Sysname] remote-ping-agent enable
# Create a remote-ping test group, setting the administrator name to administrator and test tag to dns.
[Sysname] remote-ping administrator dns
1-30
Min/Max/Average Round Trip Time: 6/10/8 Square-Sum of Round Trip Time: 756 Last complete test time: 2006-11-28 11:50:40.9 Extend result: SD Maximal delay: 0 Packet lost in test: 0% Disconnect operation number: 0 System busy operation number: 0 Operation sequence errors: 0 Other operation errors: 0 Dns result: DNS Resolve Current Time: 10 DNS Resolve Times: 10 DNS Resolve Timeout Times: 0 DNS Resolve Min Time: 6 DNS Resolve Max Time: 10 DNS Resolve Failed Times: 0 Operation timeout number: 0 Connection fail number: 0 Drop operation number: 0 DS Maximal delay: 0
[Sysname-remote-ping-administrator-dns] display remote-ping history administrator dns remote-ping entry(admin administrator, tag dns) history record: Index 1 2 3 4 5 6 7 8 9 10 Response 10 10 10 7 8 6 8 9 9 9 Status 1 1 1 1 1 1 1 1 1 1 LastRC 0 0 0 0 0 0 0 0 0 0 Time 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9 2006-11-28 11:50:40.9
1-31
Table of Contents
1 PoE Configuration 1-1 PoE Overview 1-1 Introduction to PoE 1-1 PoE Features Supported by Switch 4200G1-1 PoE Configuration 1-2 PoE Configuration Tasks1-2 Enabling the PoE Feature on a Port1-3 Setting the Maximum Output Power on a Port1-3 Setting PoE Management Mode and PoE Priority of a Port1-4 Setting the PoE Mode on a Port1-4 Configuring the PD Compatibility Detection Function 1-5 Configuring a PD Disconnection Detection Mode 1-5 Configuring PoE Over-Temperature Protection on the Switch 1-5 Upgrading the PSE Processing Software Online 1-6 Displaying PoE Configuration 1-7 PoE Configuration Example1-7 PoE Configuration Example 1-7 2 PoE Profile Configuration 2-1 Introduction to PoE Profile 2-1 PoE Profile Configuration2-1 Configuring PoE Profile 2-1 Displaying PoE Profile Configuration 2-2 PoE Profile Configuration Example2-2 PoE Profile Application Example2-2
PoE Configuration
When configuring PoE, go to these sections for information you are interested in: PoE Overview PoE Configuration Displaying PoE Configuration PoE Configuration Example
PoE Overview
Introduction to PoE
Power over Ethernet (PoE)-enabled devices use twisted pairs through electrical ports to supply power to the remote powered devices (PD) in the network and implement power supply and data transmission simultaneously.
Advantages of PoE
Reliability: The centralized power supply provides backup convenience, unified management, and safety. Easy connection: Network terminals only require an Ethernet cable, but no external power supply. Standard: PoE conforms to the 802.3af standard and uses a globally uniform power interfaces; Bright application prospect: PoE can be applied to IP phones, wireless access points (APs), chargers for portable devices, card readers, network cameras, and data collection system.
PoE components
PoE consists of three components: power sourcing equipment (PSE), PD, and power interface (PI). PSE: PSE is comprised of the power and the PSE functional module. It can implement PD detection, PD power information collection, PoE, power supply monitoring, and power-off for devices. PD: PDs receive power from the PSE. PDs include standard PDs and nonstandard PDs. Standard PDs conform to the 802.3af standard, including IP phones, Wireless APs, network cameras and so on. PI: PIs are RJ45 interfaces which connect PSE/PDs to network cables.
1-1
Table 1-1 Power supply parameters of PoE switches Input power supply DC input AC input Number of electrical ports supplying power 24 Maximum power provided by each electrical port Total Maximum PoE output power 370 W
Switch
100 m
15400 mW
A PoE-enabled Switch 4200G has the following features: As the PSE, it supports the IEEE802.3af standard. It can also supply power to some PDs that do not support the 802.3af standard. It can deliver data and current simultaneously through data wires (1,2,3,6) of category-3/5 twisted pairs. The PSE processing software on the switch can be upgraded online. The switch provides statistics about power supplying on each port and the whole equipment, which you can query through the display command. The switch provides two modes (auto and manual) to manage the power feeding to ports in the case of PSE power overload. The switch provides over-temperature protection mechanism. When the internal temperature of the switch exceeds the PoE protection temperature, the switch disables the PoE feature on all ports for self-protection; When the internal temperature of the switch drops below the PoE restoration temperature, the switch restores the PoE settings on all ports.
When you use the PoE-enabled Switch 4200G to supply power, the PDs need no external power supply. If a remote PD has an external power supply, the PoE-enabled Switch 4200G and the external power supply will backup each other for the PD. Only the Ethernet electrical ports of the PoE-enabled Switch 4200G support the PoE feature.
PoE Configuration
PoE Configuration Tasks
Table 1-2 PoE configuration tasks Task Enabling the PoE Feature on a Port Setting the Maximum Output Power on a Port Setting PoE Management Mode and PoE Priority of a Port Setting the PoE Mode on a Port Configuring the PD Compatibility Detection Function Remarks Required Optional Optional Optional Optional
1-2
Task Configuring a PD Disconnection Detection Mode Configuring PoE Over-Temperature Protection on the Switch Upgrading the PSE Processing Software Online Displaying PoE Configuration
By default, the PoE function on a port is enabled by the default configuration file (config.def) when the device is delivered. If you delete the default configuration file without specifying another one, the PoE function on a port will be disabled after you restart the device.
1-3
1-4
If you adjust the PD disconnection detection mode when the switch is running, the connected PDs will be powered off. Therefore, be cautious to do so.
1-5
Table 1-9 Follow these steps to configure PoE over-temperature protection on the switch: To do Enter system view Enable PoE over-temperature protection on the switch Use the command system-view poe temperature-protection enable Optional Enabled by default. Remarks
When the internal temperature of the switch decreases from X (X>61C) to Y (56CY<61C), the switch still keeps the PoE function disabled on all the ports. When the internal temperature of the switch increases from X (X<56C) to Y (56C<Y61C), the switch still keeps the PoE function enabled on all the ports.
In the case that the PSE processing software is damaged (that is, no PoE command can be executed successfully), use the full update mode to upgrade and thus restore the software. The refresh update mode is to upgrade the original processing software in the PSE through refreshing the software, while the full update mode is to delete the original processing software in PSE completely and then reload the software. Generally, the refresh update mode is used to upgrade the PSE processing software. When the online upgrading procedure is interrupted for some unexpected reason (for example, the device restarts due to some errors), if the upgrade in full mode fails after restart, you must upgrade in full mode after power-off and restart of the device, and then restart the device manually. In this way, the former PoE configuration is restored.
1-6
1-7
Networking diagram
Figure 1-1 Network diagram for PoE
Configuration procedure
# Upgrade the PSE processing software online.
<SwitchA> system-view [SwitchA] poe update refresh 0290_021.s19
# Enable the PoE feature on GigabitEthernet 1/0/1, and set the PoE maximum output power of GigabitEthernet 1/0/1 to 12,000 mW.
[SwitchA] interface GigabitEthernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] poe enable [SwitchA-GigabitEthernet1/0/1] poe max-power 12000 [SwitchA-GigabitEthernet1/0/1] quit
# Enable the PoE feature on GigabitEthernet 1/0/2, and set the PoE maximum output power of GigabitEthernet 1/0/2 to 2500 mW.
[SwitchA] interface GigabitEthernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] poe enable [SwitchA-GigabitEthernet1/0/2] poe max-power 2500 [SwitchA-GigabitEthernet1/0/2] quit
# Enable the PoE feature on GigabitEthernet 1/0/8, and set the PoE priority of GigabitEthernet 1/0/8 to critical.
[SwitchA] interface GigabitEthernet 1/0/8 [SwitchA-GigabitEthernet1/0/8] poe enable [SwitchA-GigabitEthernet1/0/8] poe priority critical [SwitchA-GigabitEthernet1/0/8] quit
# Set the PoE management mode on the switch to auto (it is the default mode, so this step can be omitted).
[SwitchA] poe power-management auto
# Enable the PD compatibility detect of the switch to allow the switch to supply power to part of the devices noncompliant with the 802.3af standard.
[SwitchA] poe legacy enable
1-8
Enable the PoE feature on a port Configure PoE mode for Ethernet ports Configure the PoE priority for Ethernet ports Configure the maximum power for Ethernet ports Quit system view
poe enable poe mode { signal | spare } poe priority { critical | high | low }
Operation
Command apply poe-profile profile-name interface interface-type interface-number [ to interface-type interface-number ] interface interface-type interface-number
Description
In system view
Enter Ethernet port view Apply the existing PoE profile to the port
Note the following during the configuration: 1) When the apply poe-profile command is used to apply a PoE profile to a port, some PoE features in the PoE profile can be applied successfully while some cannot. PoE profiles are applied to Switch 4200G according to the following rules: When the apply poe-profile command is used to apply a PoE profile to a port, the PoE profile is applied successfully only if one PoE feature in the PoE profile is applied properly. When the display current-configuration command is used for query, it is displayed that the PoE profile is applied properly to the port. If one or more features in the PoE profile are not applied properly on a port, the switch will prompt explicitly which PoE features in the PoE profile are not applied properly on which ports. The display current-configuration command can be used to query which PoE profile is applied to a port. However, the command cannot be used to query which PoE features in a PoE profiles are applied successfully.
GigabitEthernet 1/0/1 through GigabitEthernet 1/0/10 of Switch A are used by users of group A, who have the following requirements: The PoE function can be enabled on all ports in use. Signal mode is used to supply power. The PoE priority for GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5 is Critical, whereas the PoE priority for GigabitEthernet 1/0/6 through GigabitEthernet 1/0/10 is High. The maximum power for GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5 ports is 3,000 mW, whereas the maximum power for GigabitEthernet 1/0/6 through GigabitEthernet 1/0/10 is 15,400 mW. Based on the above requirements, two PoE profiles are made for users of group A. Apply PoE profile 1 for GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5; Apply PoE profile 2 for GigabitEthernet 1/0/6 through GigabitEthernet 1/0/10.
Network diagram
Figure 2-1 PoE profile application
Configuration procedure
# Create Profile1, and enter PoE profile view.
<SwitchA> system-view [SwitchA] poe-profile Profile1
# In Profile1, add the PoE policy configuration applicable to GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5 ports for users of group A.
[SwitchA-poe-profile-Profile1] poe enable [SwitchA-poe-profile-Profile1] poe mode signal [SwitchA-poe-profile-Profile1] poe priority critical [SwitchA-poe-profile-Profile1] poe max-power 3000
2-3
[SwitchA-poe-profile-Profile1] quit
# In Profile2, add the PoE policy configuration applicable to GigabitEthernet 1/0/6 through GigabitEthernet 1/0/10 ports for users of group A.
[SwitchA-poe-profile-Profile2] poe enable [SwitchA-poe-profile-Profile2] poe mode signal [SwitchA-poe-profile-Profile2] poe priority high [SwitchA-poe-profile-Profile2] poe max-power 15400 [SwitchA-poe-profile-Profile2] quit
# Apply the configured Profile1 to GigabitEthernet 1/0/1 through GigabitEthernet 1/0/5 ports.
[SwitchA] apply poe-profile Profile1 interface GigabitEthernet1/0/1 to GigabitEthernet1/0/5
# Apply the configured Profile2 to GigabitEthernet 1/0/6 through GigabitEthernet 1/0/10 ports.
[SwitchA] apply poe-profile Profile2 interface GigabitEthernet1/0/6 to
GigabitEthernet1/0/10
2-4
Table of Contents
1 Smart Link Configuration 1-1 Smart Link Overview 1-1 Basic Concepts in Smart Link 1-1 Operating Mechanism of Smart Link 1-3 Configuring Smart Link1-3 Configuration Task List1-3 Configuring a Smart Link Device1-4 Configuring Associated Devices1-5 Precautions1-5 Displaying and Maintaining Smart Link1-6 Smart Link Configuration Example 1-6 Implementing Link Redundancy Backup 1-6 2 Monitor Link Configuration 2-1 Introduction to Monitor Link2-1 How Monitor Link Works2-2 Configuring Monitor Link 2-3 Configuration Task List2-3 Creating a Monitor Link Group 2-3 Configuring the Uplink Port 2-3 Configuring a Downlink Port2-4 Displaying Monitor Link Configuration 2-5 Monitor Link Configuration Example 2-5 Implementing Collaboration Between Smart Link and Monitor Link 2-5
In Figure 1-1, GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 on Switch A are two member ports of a smart link group.
Master port
The master port can be either an Ethernet port or a manually-configured or static LACP aggregation group. For example, you can configure GigabitEthernet 1/0/1 of switch A in Figure 1-1 as the master port through the command line.
1-1
Slave port
The slave port can be either an Ethernet port or a manually-configured or static LACP aggregation group. For example, you can configure GigabitEthernet 1/0/2 of switch A in Figure 1-1 as the slave port through the command line.
Flush message
When a forwarding link fails, the device will switch the traffic to the blocked standby link. The former forwarding entries of each device in the network are no longer suitable for the new topology, so MAC address forwarding entries and ARP entries must be updated throughout the network. In this case, the smart link group sends flush messages to notify other devices to refresh MAC address forwarding entries and ARP entries.
Currently, the member ports of a smart link group cannot be dynamic link aggregation groups. If the master port or slave port of a smart link group is a link aggregation group, you cannot remove this link aggregation group directly or change the aggregation group into a dynamic aggregation group. Before removing this aggregation group, you must unbind the link aggregation group from the Smart Link.
1-2
As shown in Figure 1-2, GigabitEthernet 1/0/1 on Switch A is active and GigabitEthernet 1/0/2 on Switch A is blocked. When the link connected to GigabitEthernet 1/0/1 fails, GigabitEthernet 1/0/1 is blocked automatically, and the state of GigabitEthernet 1/0/2 turns to active state. When link switching occurs in the smart link group, MAC forwarding entries and ARP entries of each device in the network may be out of date. In order to guarantee correct packet transmission, you must enable the Smart Link device to send flush messages to notify the other devices in the network to refresh their own MAC forwarding entries and ARP entries. In this case, all the uplink devices must be capable of identifying flush messages from the smart link group and refreshing MAC forwarding entries and ARP entries. On a Smart Linkenabled device, if a port is blocked due to link failure, the port remains blocked after the link recovers from the failure, and does not preempt the traffic resource. Therefore, the traffic stays stable. The port does not come into the forwarding state until the next link switching.
Before configuring a member port of a smart link group, you must: Disable the port to avoid loops, thus preventing broadcast storm. Disable STP on the port. After completing the configuration, you need to enable the Ethernet ports disabled before configuring the smart link group.
1-3
Task Create a smart link group Configuring a Smart Link Device Add member ports to the smart link group Enable the function of sending flush messages in the specified control VLAN Enable the function of processing flush messages received from the specified control VLAN
Remarks
Required
Required
smart link group view Configure a port as a smart link group member
port interface-type interface-number { master | slave } quit interface interface-type interface-number Required Use either approach
Follow these steps to configure Smart Link (with link aggregation groups are the members of the smart link group): To do Enter system view Create a smart link group and enter smart link group view Configure a link aggregation group as a member of the smart link group Use the command
system-view smart-link group group-id
Remarks Required
Optional
1-4
To do Enable the function of sending flush messages in the specified control VLAN
Remarks
Precautions
When configuring Smart Link, pay attention to the following points: 1) A port or a link aggregation group cannot serve as a member port for two smart link groups. On the other hand, a port or a link aggregation group cannot serve as a member for a smart link group and a monitor link group at the same time. 2) 3) 4) 5) STP cannot be enabled on the member ports of a smart link group. An STP-enabled port or a link aggregation group with an STP-enabled port cannot serve as a member port for a smart link group. A smart link/monitor link group with members cannot be deleted. Smart Link/Monitor Link is mutually exclusive with remote port mirroring. When a Combo port operates as a member port of a smart link group, the optical port and the electrical port of the Combo port must not be both engaged with a cable at the same time.
1-5
6) 7)
When you copy a port, the smart link/monitor link group member information configured on the port will not be copied to other ports. If a single port is specified as a member of a smart link/monitor link group, you cannot execute the lacp enable command on this port or add this port into other dynamic link aggregation groups, because these operations will make this port become a link aggregation group member.
8) 9)
If no control VLAN is configured for flush message processing, the device will forward received flush messages without processing them. If the control VLAN for receiving flush messages configured on an associated device is different than the one for sending flush messages configured on the corresponding Smart Link device, the device will forward received flush messages without processing them.
10) In the static or manual link aggregation group which serves as a smart link group member, if a member port can process flush messages, this function cannot be synchronized to the other ports in the aggregation group automatically, that is, the other member ports in the aggregation group cannot process flush messages. The function of processing flush messages must be manually configured for each port in the aggregation group. 11) The VLAN configured as a control VLAN to send and receive flush messages must exist. You cannot directly remove the control VLAN. When a dynamic VLAN is configured as the control VLAN for the smart link group, this VLAN will become a static VLAN, and the prompt information is displayed.
Remarks
1-6
Network diagram
Figure 1-3 Network diagram for Smart Link configuration
Configuration procedure
1) Configure a smart link group on Switch A and configure member ports for it. Enable the function of sending flush messages in Control VLAN 1. # Enter system view.
<switchA> system-view
# Enter Ethernet port view. Disable STP on GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2.
[SwitchA] interface GigabitEthernet 1/0/1 [SwitchA-GigabitEthernet1/0/1] stp disable [SwitchA-GigabitEthernet1/0/1] quit [SwitchA] interface GigabitEthernet 1/0/2 [SwitchA-GigabitEthernet1/0/2] stp disable
# Create smart link group 1 and enter the corresponding smart link group view.
[SwitchA] smart-link group 1
# Configure GigabitEthernet 1/0/1 as the master port and GigabitEthernet 1/0/2 as the slave port for smart link group 1.
[SwitchA-smlk-group1] port GigabitEthernet 1/0/1 master [SwitchA-smlk-group1] port GigabitEthernet 1/0/2 slave
2)
Enable the function of processing flush messages received from VLAN 1 on Switch C.
1-7
# Enable the function of processing flush messages received from VLAN 1 on GigabitEthernet 1/0/2.
<SwitchC> smart-link flush enable control-vlan 1 port GigabitEthernet 1/0/2
3)
Enable the function of processing flush messages received from VLAN 1 on Switch D.
# Enable the function of processing flush messages received from VLAN 1 on GigabitEthernet 1/0/2.
[SwitchD] smart-link flush enable control-vlan 1 port GigabitEthernet 1/0/2
4)
Enable the function of processing flush messages received from VLAN 1 on Switch E.
# Enable the function of processing flush messages received from VLAN 1 on GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3.
[SwitchE] smart-link flush enable control-vlan 1 port GigabitEthernet 1/0/2 to
GigabitEthernet 1/0/3
1-8
As shown in Figure 2-1, the monitor link group configured on the device Switch A consists of an uplink port (GigabitEthernet 1/0/1) and two downlink ports (GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3). A member port can be an Ethernet port, static LACP aggregation group, manual link aggregation group, or smart link group. A smart link group can serve as the uplink port only.
2-1
As shown in Figure 2-2, the devices Switch C and Switch D are connected to the uplink device Switch E. Switch C is configured with a monitor link group, where GigabitEthernet 1/0/1 is the uplink port, while GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 are the downlink ports. Switch A is configured with a smart link group, where GigabitEthernet 1/0/1 is the master port and GigabitEthernet 1/0/2 is the slave port. If Switch C is not configured with monitor link group, when the link for the uplink port GigabitEthernet 1/0/1 on Switch C fails, the links in the smart link group are not switched because the link for the master port GigabitEthernet 1/0/1 of Switch A configured with smart link group operates normally. Actually, however, the traffic on Switch A cannot be up-linked to Switch E through the link of GigabitEthernet 1/0/1. If Switch C is configured with monitor link group and monitor link group detects that the link for the uplink port GigabitEthernet 1/0/1 fails, all the downlink ports in the group are shut down; therefore, GigabitEthernet 1/0/3 on Switch C is blocked. Now, smart link group configured on Switch A detects that a link fault occurs on the master port GigabitEthernet 1/0/1. Then, Smart Link immediately activates the slave port GigabitEthernet 1/0/2 so that traffic is switched to the backup link.
Currently, member ports of a monitor link group cannot be dynamic link aggregation groups. If the uplink or downlink port in the monitor link group is a link aggregation group, you cannot directly delete this aggregation group or change this aggregation group into a dynamic aggregation group. To delete this aggregation group, you must first unbind this aggregation group from the Monitor Link.
2-2
Before configuring a monitor link group, you must create a monitor link group and configure member ports for it. A monitor link group consists of an uplink port and one or multiple downlink ports. The uplink port can be a manually-configured or static LACP link aggregation group, an Ethernet port, or a smart link group. The downlink ports can be manually-configured link aggregation groups or static LACP link aggregation groups, or Ethernet ports.
Configure the specified link aggregation group as the uplink port of the monitor link group
Configure the specified smart link group as the uplink port of the monitor link group
2-3
Use the command port interface-type interface-number uplink quit Ethernet port view interface interface-type interface-number port monitor-link group group-id uplink
Remarks
Configure the specified Ethernet port as the uplink port of the monitor link group
Configure the specified link aggregation group as a downlink port of the monitor link group Configure a downlink port for the monitor link group
Required Monitor link group view port interface-type interface-number downlink quit Ethernet port view interface interface-type interface-number port monitor-link group group-id downlink Use either approach
Configure the specified Ethernet port as a downlink port of the monitor link group
2-4
A smart link/monitor link group with members cannot be deleted. A smart link group as a monitor link group member cannot be deleted. The smart link/monitor link function and the remote port mirroring function are incompatible with each other. If a single port is specified as a smart link/monitor link group member, do not use the lacp enable command on the port or add the port to another dynamic link aggregation group because doing so will cause the port to become an aggregation group member. Using the copy command on a port does not copy the smart link/monitor link group member information configured on the port to any other port.
2-5
Network diagram
Figure 2-3 Network diagram for Monitor Link configuration
Server
GE1/0/10
GE1/0/11
Switch E Switch C
GE1/0/1 GE1/0/1
Switch D
GE1/0/2 GE1/0/3
GE1/0/2 GE1/0/3
GE1/0/1 GE1/0/2
BLOCK GE1/0/2
GE1/0/1
Switch A
Switch B
PC 1
PC 2
PC 3
PC 4
Configuration procedure
1) Enable Smart Link on Switch A and Switch B to implement link redundancy backup. Perform the following configuration on Switch A. The configuration on Switch B is the same as on Switch A. # Enter system view.
<switchA> system-view
# Create smart link group 1 and enter smart link group view.
[SwitchA] smart-link group 1
# Configure GigabitEthernet 1/0/1 as the master port of the smart link group and GigabitEthernet 1/0/2 as the slave port.
[SwitchA-smlk-group1] port GigabitEthernet 1/0/1 master [SwitchA-smlk-group1] port GigabitEthernet 1/0/2 slave
2-6
2)
Enable Monitor Link on Switch C and Switch D and enable the function of processing flush messages received from VLAN 1. Perform the following configuration on Switch C. The operation procedure on Switch D is the same as that performed on Switch C.
# Create monitor link group 1 and enter monitor link group view
[SwitchC] monitor-link group 1
# Configure GigabitEthernet 1/0/1 as the uplink port of the monitor link group and GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 as the downlink ports.
[SwitchC-mtlk-group1] port GigabitEthernet 1/0/1 uplink [SwitchC-mtlk-group1] port GigabitEthernet 1/0/2 downlink [SwitchC-mtlk-group1] port GigabitEthernet 1/0/3 downlink
# Return to system view. Enable the function of processing flush messages received from VLAN 1 on GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3.
[SwitchC-mtlk-group1] quit [SwitchC] smart-link flush enable control-vlan 1 port GigabitEthernet 1/0/2 to
GigabitEthernet 1/0/3
3)
Enable the function of processing flush messages received from VLAN 1 on GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11 of Switch E.
# Enable the function of processing flush messages received from VLAN 1 on GigabitEthernet 1/0/10 and GigabitEthernet 1/0/11.
[SwitchE] smart-link flush enable control-vlan 1 port GigabitEthernet 1/0/10 to
GigabitEthernet 1/0/11
2-7
Table of Contents
1 IPv6 Configuration1-1 IPv6 Overview 1-1 IPv6 Features 1-1 Introduction to IPv6 Address 1-3 Introduction to IPv6 Neighbor Discovery Protocol1-6 Introduction to IPv6 DNS 1-8 Protocols and Standards 1-8 IPv6 Configuration Task List 1-9 Configuring an IPv6 Unicast Address1-9 Configuring IPv6 NDP 1-11 Configuring a Static IPv6 Route 1-12 Configuring IPv6 TCP Properties 1-13 Configuring the Maximum Number of IPv6 ICMP Error Packets Sent within a Specified Time1-13 Configuring the Hop Limit of ICMPv6 Reply Packets1-14 Configuring IPv6 DNS 1-14 Displaying and Maintaining IPv6 1-15 IPv6 Configuration Example 1-16 IPv6 Unicast Address Configuration1-16 2 IPv6 Application Configuration 2-1 Introduction to IPv6 Application 2-1 Configuring IPv6 Application2-1 IPv6 Ping 2-1 IPv6 Traceroute 2-2 IPv6 TFTP 2-2 IPv6 Telnet 2-3 IPv6 Application Configuration Example2-4 IPv6 Applications 2-4 Troubleshooting IPv6 Application 2-5 Unable to Ping a Remote Destination 2-5 Unable to Run Traceroute 2-6 Unable to Run TFTP2-6 Unable to Run Telnet2-6
IPv6 Configuration
When configuring IPv6, go to these sections for information you are interested in: IPv6 Overview IPv6 Configuration Task List IPv6 Configuration Example
The term router in this document refers to a router in a generic sense or an Ethernet switch running a routing protocol. 3com Switch 4200G supports IPv6 management features, but do not support IPv6 forwarding and related features.
IPv6 Overview
Internet Protocol Version 6 (IPv6), also called IP next generation (IPng), was designed by the Internet Engineering Task Force (IETF) as the successor to Internet Protocol Version 4 (IPv4). The significant difference between IPv6 and IPv4 is that IPv6 increases the IP address size from 32 bits to 128 bits.
IPv6 Features
Header format simplification
IPv6 cuts down some IPv4 header fields or moves them to extension headers to reduce the overhead of the basic IPv6 header. IPv6 uses a fixed-length header, thus making IPv6 packet handling simple and improving the forwarding efficiency. Although the IPv6 address size is four times that of IPv4 addresses, the size of the IPv6 header is only twice that of the IPv4 header (excluding the Options field). For the specific IPv6 header format, see Figure 1-1.
1-1
Figure 1-1 Comparison between IPv4 header format and IPv6 header format
Built-in security
IPv6 uses IPSec as its standard extension header to provide end-to-end security. This feature provides a standard for network security solutions and improves the interoperability between different IPv6 applications.
1-2
The double-colon :: can be used only once in an IPv6 address. Otherwise, the device is unable to determine how many zeros the double-colon represents when converting it to zeros to restore the IPv6 address to a 128-bit address.
An IPv6 address consists of two parts: address prefix and interface ID. The address prefix and the interface ID are respectively equivalent to the network ID and the host ID in an IPv4 address. An IPv6 address prefix is written in IPv6-address/prefix-length notation, where IPv6-address is an IPv6 address in any of the notations and prefix-length is a decimal number indicating how many bits from the left of an IPv6 address are the address prefix.
1-3
Multicast address: An identifier for a set of interfaces (typically belonging to different nodes), similar to an IPv4 multicast address. A packet sent to a multicast address is delivered to all interfaces identified by that address. Anycast address: An identifier for a set of interfaces (typically belonging to different nodes).A packet sent to an anycast address is delivered to one of the interfaces identified by that address (the nearest one, according to the routing protocols measure of distance).
There are no broadcast addresses in IPv6. Their function is superseded by multicast addresses.
The type of an IPv6 address is designated by the format prefix. Table 1-1 lists the mapping between major address types and format prefixes. Table 1-1 Mapping between address types and format prefixes Type Unassigned address Loopback address Unicast address Link-local address Site-local address Global unicast address Multicast address Anycast address Format prefix (binary) 00...0 (128 bits) 00...1 (128 bits) 1111111010 1111111011 other forms 11111111 ::/128 ::1/128 FE80::/10 FEC0::/10 FF00::/8 IPv6 prefix ID
Anycast addresses are taken from unicast address space and are not syntactically distinguishable from unicast addresses.
Unicast address
There are several forms of unicast address assignment in IPv6, including global unicast address, link-local address, and site-local address. The global unicast address, equivalent to an IPv4 public address, is used for aggregatable links and provided for network service providers. This type of address allows efficient routing aggregation to restrict the number of global routing entries. The link-local address is used in the neighbor discovery protocol and the stateless autoconfiguration process. Routers must not forward any packets with link-local source or destination addresses to other links. IPv6 unicast site-local addresses are similar to private IPv4 addresses. Routers must not forward any packets with site-local source or destination addresses outside of the site (equivalent to a private network). Loopback address: The unicast address 0:0:0:0:0:0:0:1 (represented in shorter format as ::1) is called the loopback address and may never be assigned to any physical interface. Like the loopback address in IPv4, it may be used by a node to send an IPv6 packet to itself.
1-4
Unassigned address: The unicast address :: is called the unassigned address and may not be assigned to any node. Before acquiring a valid IPv6 address, a node may fill this address in the source address field of an IPv6 packet, but may not use it as a destination IPv6 address.
Multicast address
Multicast addresses listed in Table 1-2 are reserved for special purpose. Table 1-2 Reserved IPv6 multicast addresses Address FF01::1 FF02::1 FF01::2 FF02::2 FF05::2 Application Node-local scope all-nodes multicast address Link-local scope all-nodes multicast address Node-local scope all-routers multicast address Link-local scope all-routers multicast address Site-local scope all-routers multicast address
Besides, there is another type of multicast address: solicited-node address. The solicited-node multicast address is used to acquire the link-layer addresses of neighbor nodes on the same link and is also used for duplicate address detection. Each IPv6 unicast or anycast address has one corresponding solicited-node address. The format of a solicited-node multicast address is as follows: FF02:0:0:0:0:1:FFXX:XXXX Where, FF02:0:0:0:0:1:FF is permanent and consists of 104 bits, and XX:XXXX is the last 24 bits of an IPv6 address.
1-5
Redirect message
3com Switch 4200G does not support the RS, RA, or Redirect message. Of the above mentioned IPv6 NDP functions, 3com Switch 4200G supports the following three functions: address resolution, neighbor unreachability detection, and duplicate address detection. The subsequent sections present a detailed description of these three functions and relevant configuration.
Address resolution
Similar to the ARP function in IPv4, a node acquires the link-layer address of neighbor nodes on the same link through NS and NA messages. Figure 1-3 shows how node A acquires the link-layer address of node B. Figure 1-3 Address resolution
The address resolution procedure is as follows: 2) Node A multicasts an NS message. The source address of the NS message is the IPv6 address of the interface of node A and the destination address is the solicited-node multicast address of node B. The NS message contains the link-layer address of node A. 3) After receiving the NS message, node B judges whether the destination address of the packet is the corresponding solicited-node multicast address of its own IPv6 address. If yes, node B learns the link-layer address of node A and returns an NA message containing the link-layer address of node B in the unicast mode. 4) Node A acquires the link-layer address of node B from the NA message. After that, node A and node B can communicate with each other.
1-7
The duplicate address detection procedure is as follows: 1) Node A sends an NS message whose source address is the unassigned address :: and the destination address is the corresponding solicited-node multicast address of the IPv6 address to be detected. The NS message also contains the IPv6 address. 2) 3) If node B uses this IPv6 address, node B returns an NA message. The NA message contains the IPv6 address of node B. Node A learns that the IPv6 address is being used by node B after receiving the NA message from node B. Otherwise, node B is not using the IPv6 address and node A can use it.
RFC 3513: Internet Protocol Version 6 (IPv6) Addressing Architecture RFC 3596: DNS Extensions to Support IP Version 6
1-9
Remarks Use either command By default, no site-local address or global unicast address is configured for an interface. Note that the prefix specified by the prefix-length argument in an EUI-64 address cannot exceed 64 bits in length. Optional
By default, after an IPv6 site-local address or global unicast address is configured for an interface, a link-local address will be generated automatically.
IPv6 unicast addresses can be configured for only one VLAN interface on a 3com switch 4200G. The total number of global unicast addresses and site-local addresses on the VLAN interface can be up to four. After an IPv6 site-local address or global unicast address is configured for an interface, a link-local address will be generated automatically. The automatically generated link-local address is the same as the one generated by using the ipv6 address auto link-local command. The manual assignment takes precedence over the automatic generation. That is, if you first adopt the automatic generation and then the manual assignment, the manually assigned link-local address will overwrite the automatically generated one. If you first adopt the manual assignment and then the automatic generation, the automatically generated link-local address will not take effect and the link-local address of an interface is still the manually assigned one. If the manually assigned link-local address is deleted, the automatically generated link-local address takes effect. You must have carried out the ipv6 address auto link-local command before you carry out the undo ipv6 address auto link-local command. However, if an IPv6 site-local address or global unicast address is already configured for an interface, the interface still has a link-local address because the system automatically generates one for the interface. If no IPv6 site-local address or global unicast address is configured, the interface has no link-local address.
1-10
Required
1-11
Follow these steps to configure the attempts to send an NS message for duplicate address detection: To do Enter system view Enter VLAN interface view Use the command system-view interface interface-type interface-number Optional Configure the attempts to send an NS message for duplicate address detection ipv6 nd dad attempts value 1 by default. When the value argument is set to 0, the duplicate address detection is disabled. Remarks
Remarks
To do
Use the command ipv6 route-static ipv6-address prefix-length [ interface-type interface-number] nexthop-address Required
Remarks
Configuring the Maximum Number of IPv6 ICMP Error Packets Sent within a Specified Time
If too many IPv6 ICMP error packets are sent within a short time in a network, network congestion may occur. To avoid network congestion, you can control the maximum number of IPv6 ICMP error packets sent within a specified time. Currently, the token bucket algorithm is adopted. You can set the capacity of a token bucket, namely, the number of tokens in the bucket. In addition, you can set the update period of the token bucket, namely, the interval for updating the number of tokens in the token bucket to the configured capacity. One token allows one IPv6 ICMP error packet to be sent. Each time an IPv6 ICMP error packet is sent, the number of tokens in a token bucket decreases by 1. If the number of the IPv6 ICMP error packets that are continuously sent out reaches the capacity of the token bucket, the subsequent IPv6 ICMP error packets cannot be sent out until new tokens are put into the token bucket based on the specified update frequency. Follow these steps to configure the maximum number of IPv6 ICMP error packets sent within a specified time:
1-13
To do Enter system view Configure the maximum number of IPv6 ICMP error packets sent within a specified time
Use the command system-view Optional ipv6 icmp-error { bucket bucket-size | ratelimit interval }*
Remarks
By default, the capacity of a token bucket is 10 and the update period to 100 milliseconds. That is, at most 10 IPv6 ICMP error packets can be sent within an update period.
1-14
To do Enter system view Enable the dynamic domain name resolution function
Remarks
If the IPv6 address of the DNS server is a link-local address, the interface-type and interface-number arguments are required. Required
By default, no domain name suffix is configured, that is, the domain name is resolved according to the input information.
The dns resolve and dns domain commands are the same as those of IPv4 DNS. For details about the commands, refer to DNS Operation in this manual.
Display the total number of neighbor entries satisfying the specified conditions Display information about the routing table Display information related to a specified socket
To do Display the statistics of IPv6 packets and IPv6 ICMP packets Display the statistics of IPv6 TCP packets Display the IPv6 TCP connection status Display the statistics of IPv6 UDP packets Clear IPv6 dynamic domain name cache information Clear IPv6 neighbor information Clear the statistics of IPv6 packets Clear the statistics of all IPv6 TCP packets Clear the statistics of all IPv6 UDP packets
Use the command display ipv6 statistics display tcp ipv6 statistics display tcp ipv6 status display udp ipv6 statistics reset dns ipv6 dynamic-host reset ipv6 neighbors [ all | dynamic | interface interface-type interface-number | static ] reset ipv6 statistics reset tcp ipv6 statistics reset udp ipv6 statistics
Remarks
The display dns domain and display dns server commands are the same as those of IPv4 DNS. For details about the commands, refer to DNS Operation in this manual.
Network diagram
Figure 1-5 Network diagram for IPv6 address configuration
1-16
Configuration procedure
1) Configure Switch A.
2)
Configure Switch B.
Verification
# Display the brief IPv6 information of an interface on Switch A.
[SwitchA-Vlan-interface2] display ipv6 interface vlan-interface 2 Vlan-interface2 current state : UP Line protocol current state : UP IPv6 is enabled, link-local address is FE80::20F:E2FF:FE49:8048 Global unicast address(es): 2001::20F:E2FF:FE49:8048, subnet is 2001::/64 3001::1, subnet is 3001::/64 Joined group address(es): FF02::1:FF00:1 FF02::1:FF49:8048 FF02::1 MTU is 1500 bytes ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND retransmit interval is 1000 milliseconds Hosts use stateless autoconfig for addresses
1-17
2001::20F:E2FF:FE00:1, subnet is 2001::/64 3001::2, subnet is 3001::/64 Joined group address(es): FF02::1:FF00:2 FF02::1:FF00:1 FF02::1 MTU is 1500 bytes ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND retransmit interval is 1000 milliseconds Hosts use stateless autoconfig for addresses
# On Switch A, ping the link-local address, EUI-64 address, and global unicast address of Switch B. If the configurations are correct, the above three types of IPv6 addresses can be pinged.
When you use the ping ipv6 command to verify the reachability of the destination, you must specify the i keyword if the destination address is a link-local address. For the operation of IPv6 ping, refer to section IPv6 Ping.
[SwitchA-Vlan-interface2] ping ipv6 FE80::20F:E2FF:FE00:1 -i Vlan-interface 2 PING FE80::20F:E2FF:FE00:1 : 56 data bytes, press CTRL_C to break
Reply from FE80::20F:E2FF:FE00:1 bytes=56 Sequence=1 hop limit=255 Reply from FE80::20F:E2FF:FE00:1 bytes=56 Sequence=2 hop limit=255 Reply from FE80::20F:E2FF:FE00:1 bytes=56 Sequence=3 hop limit=255 Reply from FE80::20F:E2FF:FE00:1 bytes=56 Sequence=4 hop limit=255 Reply from FE80::20F:E2FF:FE00:1 bytes=56 Sequence=5 hop limit=255 time = 60 ms time = 70 ms time = 60 ms time = 60 ms time = 80 ms
--- FE80::20F:E2FF:FE00:1 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 60/66/80 ms
[SwitchA-Vlan-interface2] ping ipv6 2001::20F:E2FF:FE00:1 PING 2001::20F:E2FF:FE00:1 : 56 data bytes, press CTRL_C to break
Reply from 2001::20F:E2FF:FE00:1 bytes=56 Sequence=1 hop limit=255 Reply from 2001::20F:E2FF:FE00:1 bytes=56 Sequence=2 hop limit=255 Reply from 2001::20F:E2FF:FE00:1 time = 70 ms time = 40 ms
1-18
bytes=56 Sequence=3 hop limit=255 Reply from 2001::20F:E2FF:FE00:1 bytes=56 Sequence=4 hop limit=255 Reply from 2001::20F:E2FF:FE00:1 bytes=56 Sequence=5 hop limit=255
time = 60 ms
time = 60 ms
time = 60 ms
--- 2001::20F:E2FF:FE00:1 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 40/58/70 ms
[SwitchA-Vlan-interface2] ping ipv6 3001::2 PING 3001::2 : 56 data bytes, press CTRL_C to break
Reply from 3001::2 bytes=56 Sequence=1 hop limit=255 Reply from 3001::2 bytes=56 Sequence=2 hop limit=255 Reply from 3001::2 bytes=56 Sequence=3 hop limit=255 Reply from 3001::2 bytes=56 Sequence=4 hop limit=255 Reply from 3001::2 bytes=56 Sequence=5 hop limit=255 time = 60 ms time = 70 ms time = 60 ms time = 60 ms time = 50 ms
--- 3001::2 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 50/60/70 ms
1-19
Ping IPv6
When you use the ping ipv6 command to verify the reachability of the destination, you must specify the i keyword if the destination address is a link-local address.
2-1
IPv6 Traceroute
The traceroute ipv6 command is used to record the route of IPv6 packets from source to destination, so as to check whether the link is available and determine the point of failure. Figure 2-1 Traceroute process
As Figure 2-1 shows, the traceroute process is as follows: The source sends an IP datagram with the Hop Limit of 1. If the first hop device receiving the datagram reads the Hop Limit of 1, it will discard the packet and return an ICMP timeout error message. Thus, the source can get the first devices address in the route. The source sends a datagram with the Hop Limit of 2 and the second hop device returns an ICMP timeout error message. The source gets the second devices address in the route. This process continues until the datagram reaches the destination host. As there is no application using the UDP port, the destination returns a port unreachable ICMP error message. The source receives the port unreachable ICMP error message and understands that the packet has reached the destination, and thus determines the route of the packet from source to destination. Follow these steps to traceroute IPv6: To do Traceroute IPv6 Use the command tracert ipv6 [ -f first-ttl | -m max-ttl | -p port | -q packet-num | -w timeout ]* remote-system Required Available in any view Remarks
IPv6 TFTP
IPv6 supports Trivial File Transfer Protocol (TFTP). As a client, the device can download files from or upload files to a TFTP server. For details about TFTP, see FTP-SFTP-TFTP Operation.
Configuration preparation
Enable TFTP on the TFTP server and specify the path to download or upload files. For specific operations, refer to TFTP server configuration specifications.
2-2
To do
Use the command tftp ipv6 remote-system [ -i interface-type interface-number ] { get | put } source-filename [ destination-filename ]
Remarks
When you use the tftp ipv6 command to connect to the TFTP server, you must specify the i keyword if the destination address is a link-local address.
IPv6 Telnet
Telnet protocol belongs to application layer protocols of the TCP/IP protocol suite, and is used to provide remote login and virtual terminals. The device can be used either as a Telnet client or a Telnet server. As the following figure shows, the Host is running Telnet client application of IPv6 to set up an IPv6 Telnet connection with Device A, which serves as the Telnet server. If Device A again connects to Device B through Telnet, the Device A is the Telnet client and Device B is the Telnet server. Figure 2-2 Provide Telnet services
Configuration prerequisites
Enable Telnet on the Telnet server and configure the authentication method. For details, refer to Login Operation in this manual. Follow these steps to set up IPv6 Telnet connections: To do Perform the telnet command on the Telnet client to log in to other devices Use the command telnet ipv6 remote-system [ -i interface-type interface-number ] [ port-number ] Remarks Required Available in user view
When you use the telnet ipv6 command to connect to the Telnet server, you must specify the i keyword if the destination address is a link-local address.
2-3
Network diagram
Figure 2-3 Network diagram for IPv6 applications
Telnet_Server
3001::2/64
TFTP_Server
3001::3/64 3001::4/64 3002::1/64
SWC
3003::1/64 3002::2/64
SWB
3003::2/64
SWA
Configuration procedure
You need configure IPv6 address at the switchs and servers interfaces and ensure that the route between the switch and the server is accessible before the following configuration.
Reply from 3003::1 bytes=56 Sequence=1 hop limit=64 Reply from 3003::1 time = 110 ms
2-4
bytes=56 Sequence=2 hop limit=64 Reply from 3003::1 bytes=56 Sequence=3 hop limit=64 Reply from 3003::1 bytes=56 Sequence=4 hop limit=64 Reply from 3003::1 bytes=56 Sequence=5 hop limit=64
time = 31 ms
time = 31 ms
time = 31 ms
time = 31 ms
--- 3003::1 ping statistics --5 packet(s) transmitted 5 packet(s) received 0.00% packet loss round-trip min/avg/max = 31/46/110 ms
# On SWA, configure static routes to SWC, the Telnet Server, and the TFTP Server.
<SWA> system-view [SWA] ipv6 route-static 3002:: 64 3003::1 [SWA] ipv6 route-static 3001:: 64 3003::1 [SWA] quit
3002::1 10 ms 10 ms 0 ms
Solution
Check that the IPv6 addresses are configured correctly.
2-5
Use the display ipv6 interface command to determine the interfaces of the source and the destination and the link-layer protocol between them are up. Use the display ipv6 route-table command to verify that the destination is reachable. Use the ping ipv6 -t timeout { destination-ipv6-address | hostname } [ -i interface-type interface-number ] command to increase the timeout time limit, so as to determine whether it is due to the timeout limit is too small.
Solution
Check that the destination host can be pinged. If the host can be pinged through, check whether the UDP port that was included in the tracert ipv6 command is used by an application on the host. If yes, you need to use the tracert ipv6 command with an unreachable UDP port.
Solution
Check that the route between the device and the TFTP server is up. Check that the file system of the device is usable. You can check it by running the dir command in user view. Check that the ACL configured for the TFTP server does not block the connection to the TFTP server.
Solution
Check that the Telnet server application is running on the server. Check the configuration allows the server reachable. Check that the route between the device and the TFTP server is up.
2-6
Table of Contents
1 UDP Helper Configuration 1-1 Introduction to UDP Helper 1-1 Configuring UDP Helper 1-2 Displaying and Maintaining UDP Helper1-2 UDP Helper Configuration Example 1-3 Cross-Network Computer Search Through UDP Helper1-3
Relay forwarding of BOOTP/DHCP broadcast packets is implemented by the DHCP relay function using UDP ports 67 and 68, so these two ports cannot be configured as UDP Helper relay ports.
By default, with UDP Helper enabled, the device forwards broadcast packets with the six UDP destination port numbers listed in Table 1-1. Table 1-1 List of default UDP ports Protocol DNS (Domain Name System) NetBIOS-DS (NetBIOS Datagram Service) NetBIOS-NS (NetBIOS Name Service) TACACS (Terminal Access Controller Access Control System) UDP port number 53 138 137 49
1-1
Enter VLAN interface view Specify the destination server to which the UDP packets are to be forwarded
You need to enable UDP Helper before specifying any UDP port to match UDP broadcasts; otherwise, the configuration fails. When the UDP helper function is disabled, all configured UDP ports are disabled, including the default ports. The dns, netbios-ds, netbios-ns, tacacs, tftp, and time keywords correspond to the six default ports. You can configure the default ports by specifying port numbers or the corresponding parameters. For example, udp-helper port 53 and udp-helper port dns specify the same port. You can specify up to 20 destination server addresses on a VLAN interface. If UDP Helper is enabled after a destination server is configured for a VLAN interface, the broadcasts from interfaces belonging to the VLAN and having a matching UDP port will be unicast to the destination server.
1-2
Network diagram
Figure 1-1 Network diagram for UDP Helper configuration
Configuration procedure
# Enable UDP Helper on Switch A.
<SwitchA> system-view [SwitchA] udp-helper enable
# Configure the switch to forward broadcasts containing the destination UDP port number 137. (By default, the device enabled with UDP Helper forwards the broadcasts containing the destination UDP port number 137.)
[SwitchA] udp-helper port 137
1-3
Table of Contents
1 Access Management Configuration 1-1 Access Management Overview 1-1 Configuring Access Management 1-2 Access Management Configuration Examples 1-2 Access Management Configuration Example 1-2 Combining Access Management with Port Isolation 1-3
Internet
Switch A
GE1/0/1
Switch B
PC1_1
PC1_2
PC1_n
PC2
PC3
Organization 1
The access management function aims to manage user access rights on access switches. It enables you to manage the external network access rights of the hosts connected to ports of an access switch. To implement the access management function, you need to configure an IP address pool on a port of an access switch, that is, bind a specified range of IP addresses to the port. A port with an access management IP address pool configured only allows the hosts with their IP addresses in the access management IP address pool to access external networks. A port without an access management IP address pool configured allows the hosts to access external networks only if their IP addresses are not in the access management IP address pools of other ports of the switch. Note that the IP addresses in the access management IP address pool configured on a port must be in the same network segment as the IP address of the VLAN (where the port belongs to) interface.
1-1
Enter Ethernet port view Configure the access management IP address pool of the port Display current configuration of access management
display am [ interface-list ]
Before configuring the access management IP address pool of a port, you need to configure the interface IP address of the VLAN to which the port belongs, and the IP addresses in the access management IP address pool of a port must be in the same network segment as the interface IP address of the VLAN which the port belongs to. If an access management address pool configured contains IP addresses that belong to the static ARP entries of other ports, the system prompts you to delete the corresponding static ARP entries to ensure the access management IP address pool can take effect. To allow only the hosts with their IP addresses in the access management address pool of a port to access external networks, do not configure static ARP entries for IP addresses not in the IP address pool.
1-2
Allow the PCs of Organization 1 to access the external network through GigabitEthernet 1/0/1 on Switch A. The port belongs to VLAN 1, and the IP address of VLAN-interface 1 is 202.10.20.200/24. Disable the PCs that are not of Organization 1 (PC 2 and PC 3) from accessing the external network through GigabitEthernet 1/0/1 of Switch A.
Network diagram
Figure 1-2 Network diagram for access management configuration Internet
Switch A
GE1/0/1 Vlan-int1 202.10.20.200/24
Switch B
Configuration procedure
Perform the following configuration on Switch A. # Enable access management.
<Sysname> system-view [Sysname] am enable
1-3
Allow the PCs of Organization 1 to access the external network through GigabitEthernet 1/0/1 of Switch A. Allow the PCs of Organization 2 to access the external network through GigabitEthernet 1/0/2 of Switch A. GigabitEthernet 1/0/1 and GigabitEthernet 1/0/2 belong to VLAN 1. The IP address of VLAN-interface 1 is 202.10.20.200/24. PCs of Organization 1 are isolated from those of Organization 2 on Layer 2.
Network diagram
Figure 1-3 Network diagram for combining access management and port isolation
Internet
Switch A
GE1/0/1
GE1/0/2
Vlan-int1 202.10.20.200/24
Switch B
Switch C
PC1_1
PC1_2
PC1_20
202.10.20.1/24202.10.20.20/24 Organization 1
Configuration procedure
Perform the following configuration on Switch A. For information about port isolation and the corresponding configuration, refer to the Port Isolation Operation. # Enable access management.
<Sysname> system-view [Sysname] am enable
1-5
Table of Contents
Appendix A Acronyms A-1
Appendix A Acronyms
A AAA ABR ACL ARP AS ASBR B BDR C CAR CLI CoS D DHCP DR D-V E EGP F FTP G GARP GE GVRP GMRP H HGMP I IAB ICMP IGMP IGP IP Internet Architecture Board Internet Control Message Protocol Internet Group Management Protocol Interior Gateway Protocol Internet Protocol Huawei Group Management Protocol Generic Attribute Registration Protocol Gigabit Ethernet GARP VLAN Registration Protocol GARP Multicast Registration Protocol File Transfer Protocol Exterior Gateway Protocol Dynamic Host Configuration Protocol Designated Router Distance Vector Routing Algorithm Committed Access Rate Command Line Interface Class of Service Backup Designated Router Authentication, Authorization and Accounting Area Border Router Access Control List Address Resolution Protocol Autonomous System Autonomous System Border Router
A-1
L LSA LSDB M MAC MIB N NBMA NIC NMS NVRAM O OSPF P PIM PIM-DM PIM-SM PoE Q QoS R RIP RMON RSTP S SNMP SP STP T TCP/IP TFTP ToS TTL U UDP V VLAN Virtual LAN
A-2
Non Broadcast MultiAccess Network Information Center Network Management System Nonvolatile RAM
Protocol Independent Multicast Protocol Independent Multicast-Dense Mode Protocol Independent Multicast-Sparse Mode Power over Ethernet
Quality of Service
Routing Information Protocol Remote Network Monitoring Rapid Spanning Tree Protocol
Transmission Control Protocol/ Internet Protocol Trivial File Transfer Protocol Type of Service Time To Live
Video On Demand
A-3