Configuration Guide - Device Management(V100R005C01_03)

Quidway S5300 Series Ethernet SwitchesV100R005C01

Configuration Guide - DeviceManagement

Issue 03

Date 2011-01-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 03 (2011-01-30) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

About This Document

Intended AudienceThis document describes procedures and provides examples for configuring the DeviceManagement features of the S5300.

This document guides you through the configuration and applicable environment of the DeviceManagement features of the S5300.

This document is intended for:

l Data configuration engineers

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

WARNINGIndicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.

TIP Indicates a tip that may help you solve a problem or savetime.

NOTE Provides additional information to emphasize or supplementimportant points of the main text.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management About This Document


iii

Command ConventionsThe command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

&<1-n> The parameter before the & sign can be repeated 1 to n times.

# A line starting with the # sign is comments.

Change HistoryUpdates between document issues are cumulative. Therefore, the latest document issue containsall updates made in previous issues.

Changes in Issue 03 (2011-01-30)Based on issue 02 (2010-12-01), the document is updated as follows:

The following content is modified:

Minor mistakes are rectified.

Changes in Issue 02 (2010-12-01)Based on issue 01 (2010-08-15), the document is updated as follows:

The following content is modified:

l 8.2 PoE Features Supported by the S5300

Changes in Issue 01 (2010-08-15)This is the first release.

About This DocumentQuidway S5300 Series Ethernet Switches

Configuration Guide - Device Management

iv Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2011-01-30)

Contents

About This Document...................................................................................................................iii

1 Auto-Config.................................................................................................................................1-11.1 Overview.........................................................................................................................................................1-21.2 Auto-Config Features Supported by the S5300..............................................................................................1-31.3 Deploying Unconfigured Switches (Same Network Segment).......................................................................1-6

1.3.1 Establishing the Configuration Task......................................................................................................1-61.3.2 Configuring the DHCP Server...............................................................................................................1-71.3.3 Configuring the FTP/TFTP Server.........................................................................................................1-81.3.4 Checking the Configuration...................................................................................................................1-8

1.4 Deploying Unconfigured Switches (Different Network Segments)................................................................1-91.4.1 Establishing the Configuration Task......................................................................................................1-91.4.2 Configuring the DHCP Server.............................................................................................................1-101.4.3 Configuring DHCP Relay....................................................................................................................1-111.4.4 Configuring the FTP/TFTP Server.......................................................................................................1-111.4.5 Checking the Configuration.................................................................................................................1-12

2 NAP Configuration....................................................................................................................2-12.1 NAP Overview................................................................................................................................................2-22.2 Configuring NAP-based Remote Deployment................................................................................................2-2

2.2.1 Establishing the Configuration Task......................................................................................................2-32.2.2 Configuring and Starting the NAP Master Interface..............................................................................2-32.2.3 Remote Login.........................................................................................................................................2-52.2.4 Disabling NAP on the Slave Device......................................................................................................2-62.2.5 Checking the Configuration...................................................................................................................2-6

2.3 Configuration Examples..................................................................................................................................2-82.3.1 Example for Configuring NAP-based Remote Deployment in Automatic Mode..................................2-82.3.2 Example for Configuring NAP-based Remote Deployment in Static Mode.........................................2-9

3 Stacking........................................................................................................................................3-13.1 Stacking Overview..........................................................................................................................................3-23.2 Principle of Stacking.......................................................................................................................................3-23.3 Features of Stacking Supported by the S5300................................................................................................3-83.4 Typical Topology of a Stack...........................................................................................................................3-93.5 Configuring the Stacking Function on the S5300.........................................................................................3-10

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management Contents


v

3.5.1 Establishing the Configuration Task....................................................................................................3-103.5.2 (Optional) Configuring the Reserved VLAN of the Stack...................................................................3-113.5.3 (Optional) Enabling the Stacking Function..........................................................................................3-113.5.4 (Optional) Configuring a Stack ID for the S5300................................................................................3-123.5.5 (Optional) Configuring a Stack Priority for a Device..........................................................................3-123.5.6 (Optional) Configuring the MAC Address Switchover Time..............................................................3-133.5.7 Checking the Configuration.................................................................................................................3-13

3.6 Configuration Examples................................................................................................................................3-143.6.1 Example for Configuring a Stack in a Ring Topology.........................................................................3-14

4 Using display commands to check the status of the device...............................................4-14.1 Introduction.....................................................................................................................................................4-24.2 Checking the Status of the S5300................................................................................................................... 4-2

4.2.1 Checking Information About the S5300................................................................................................ 4-24.2.2 Checking the Version of the S5300........................................................................................................4-24.2.3 Checking the Electronic Labels..............................................................................................................4-34.2.4 Checking Temperature...........................................................................................................................4-34.2.5 Checking the External Fan Status.......................................................................................................... 4-44.2.6 Checking the Power Supply Status........................................................................................................ 4-44.2.7 Checking the CPU Usage.......................................................................................................................4-44.2.8 Checking the Memory Usage.................................................................................................................4-44.2.9 Checking Alarms....................................................................................................................................4-54.2.10 Checking the Status of an Interface......................................................................................................4-5

5 Hardware Management.............................................................................................................5-15.1 Hardware Management Overview...................................................................................................................5-25.2 Hardware Management Features Supported by the S5300.............................................................................5-25.3 Backing Up the Electronic Label....................................................................................................................5-2

5.3.1 Establishing the Configuration Task......................................................................................................5-25.3.2 Backing Up the Electronic Label...........................................................................................................5-3

5.4 Configuring Electrical Port Sleep................................................................................................................... 5-35.4.1 Establishing the Configuration Task......................................................................................................5-35.4.2 Enabling Electrical Port Sleep................................................................................................................5-45.4.3 Checking the Configuration...................................................................................................................5-4

6 Monitoring the Device Through the Information Center..................................................6-16.1 Information Center Overview......................................................................................................................... 6-2

6.1.1 Introduction to the Information Center.................................................................................................. 6-26.1.2 Information Center Supported by the S5300..........................................................................................6-2

6.2 Configuring the Information Center................................................................................................................6-86.2.1 Establishing the Configuration Task......................................................................................................6-86.2.2 Enabling the Information Center............................................................................................................6-86.2.3 (Optional) Naming the Information Channel.........................................................................................6-96.2.4 Defining the Information Channel......................................................................................................... 6-9

ContentsQuidway S5300 Series Ethernet Switches


vi Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2011-01-30)

6.2.5 (Optional) Configuring the Timestamp for the Output Information....................................................6-106.2.6 Checking the Configuration.................................................................................................................6-10

6.3 Sending Information of the Information Center............................................................................................6-106.3.1 Sending Information to the Console.....................................................................................................6-116.3.2 Sending Information to the Telnet Terminal........................................................................................6-116.3.3 Sending Information to the SNMP Agent............................................................................................6-126.3.4 Sending Information to the Log Buffer................................................................................................6-126.3.5 Sending Information to the Trap Buffer...............................................................................................6-136.3.6 Sending Information to the Log Host...................................................................................................6-136.3.7 Checking the Configuration.................................................................................................................6-14

6.4 Maintaining the Information Center..............................................................................................................6-146.5 Configuration Examples................................................................................................................................6-14

6.5.1 Example for Configuring the Information Center................................................................................6-15

7 Mirroring......................................................................................................................................7-17.1 Introduction.....................................................................................................................................................7-3

7.1.1 Mirroring Functions...............................................................................................................................7-37.1.2 Logical Relationships Between Configuration Tasks............................................................................7-6

7.2 Configuring Local Port Mirroring...................................................................................................................7-67.2.1 Establishing the Configuration Task......................................................................................................7-67.2.2 Configuring Local Port Mirroring..........................................................................................................7-77.2.3 Checking the Configuration...................................................................................................................7-7

7.3 Configuring Remote Port Mirroring...............................................................................................................7-87.3.1 Establishing the Configuration Task......................................................................................................7-87.3.2 Configuring Remote Port Mirroring......................................................................................................7-97.3.3 Checking the Configuration.................................................................................................................7-11

7.4 Canceling Port Mirroring..............................................................................................................................7-117.4.1 Establishing the Configuration Task....................................................................................................7-127.4.2 Canceling Port Mirroring.....................................................................................................................7-127.4.3 Checking the Configuration.................................................................................................................7-12

7.5 Configuring Local VLAN Mirroring............................................................................................................7-137.5.1 Establishing the Configuration Task....................................................................................................7-137.5.2 Configuring Local VLAN Mirroring...................................................................................................7-137.5.3 Checking the Configuration.................................................................................................................7-14

7.6 Configuring Remote VLAN Mirroring.........................................................................................................7-147.6.1 Establishing the Configuration Task....................................................................................................7-157.6.2 Configuring Remote VLAN Mirroring................................................................................................7-157.6.3 Checking the Configuration.................................................................................................................7-16

7.7 Canceling VLAN Mirroring..........................................................................................................................7-177.7.1 Establishing the Configuration Task....................................................................................................7-177.7.2 Canceling VLAN Mirroring.................................................................................................................7-177.7.3 Checking the Configuration.................................................................................................................7-18

7.8 Configuring MAC Address-based Local Mirroring......................................................................................7-18



vii

7.8.1 Establishing the Configuration Task....................................................................................................7-187.8.2 Configuring Local SPAN Based on MAC Addresses..........................................................................7-187.8.3 Checking the Configuration.................................................................................................................7-19

7.9 Configuring RSPAN Based on MAC Addresses..........................................................................................7-197.9.1 Establishing the Configuration Task....................................................................................................7-207.9.2 Configuring Remote MAC Address Mirroring....................................................................................7-207.9.3 Checking the Configuration.................................................................................................................7-21

7.10 Canceling Mirroring Based on MAC Addresses.........................................................................................7-227.10.1 Establishing the Configuration Task..................................................................................................7-227.10.2 Canceling Mirroring Based on MAC Addresses................................................................................7-227.10.3 Checking the Configuration...............................................................................................................7-23

7.11 Configuring Local Flow Mirroring.............................................................................................................7-237.11.1 Establishing the Configuration Task..................................................................................................7-237.11.2 Configuring Traffic Classification Rules...........................................................................................7-247.11.3 Configuring Flow Mirroring..............................................................................................................7-247.11.4 Creating and Applying a Traffic Policy.............................................................................................7-247.11.5 Checking the Configuration...............................................................................................................7-25

7.12 Configuring Remote Flow Mirroring..........................................................................................................7-267.12.1 Establishing the Configuration Task..................................................................................................7-267.12.2 Setting Traffic Classification Rules...................................................................................................7-267.12.3 Configuring Remote Flow Mirroring.................................................................................................7-277.12.4 Creating and Applying a Traffic Policy.............................................................................................7-287.12.5 Checking the Configuration...............................................................................................................7-28

7.13 Canceling Flow Mirroring...........................................................................................................................7-287.13.1 Establishing the Configuration Task..................................................................................................7-297.13.2 Canceling Flow Mirroring..................................................................................................................7-297.13.3 Checking the Configuration...............................................................................................................7-30

7.14 Changing or Deleting an Observing Port....................................................................................................7-307.14.1 Establishing the Configuration Task..................................................................................................7-307.14.2 (Optional) Deleting an Observing Port..............................................................................................7-317.14.3 (Optional) Changing an Observing Port.............................................................................................7-327.14.4 Checking the Configuration...............................................................................................................7-32

7.15 Configuring CPU Mirroring........................................................................................................................7-327.15.1 Establishing the Configuration Task..................................................................................................7-327.15.2 (Optional) Configuring an ACL Rule................................................................................................7-337.15.3 Configuring an Observing Port..........................................................................................................7-337.15.4 Configuring CPU Mirroring...............................................................................................................7-347.15.5 Checking the Configuration...............................................................................................................7-34

7.16 Cancelling CPU Mirroring..........................................................................................................................7-347.16.1 Establishing the Configuration Task..................................................................................................7-357.16.2 Cancelling CPU Mirroring.................................................................................................................7-357.16.3 Checking the Configuration...............................................................................................................7-35

ContentsQuidway S5300 Series Ethernet Switches


viii Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2011-01-30)

7.17 Configuration Examples..............................................................................................................................7-367.17.1 Example for Configuring Local Port Mirroring.................................................................................7-367.17.2 Example for Configuring Local VLAN Mirroring............................................................................7-387.17.3 Example for Configuring MAC Address-based Local Mirroring......................................................7-397.17.4 Example for Configuring Local Flow Mirroring...............................................................................7-417.17.5 Example for Configuring Remote Port Mirroring..............................................................................7-447.17.6 Example for Changing an Observing Port.........................................................................................7-47

8 PoE Configuration......................................................................................................................8-18.1 PoE Overview................................................................................................................................................. 8-28.2 PoE Features Supported by the S5300............................................................................................................8-28.3 Configuring PoE Functions.............................................................................................................................8-3

8.3.1 Establishing the Configuration Task......................................................................................................8-38.3.2 Configuring the PoE Function Globally.................................................................................................8-38.3.3 Configuring the PoE Function on an Interface.......................................................................................8-58.3.4 Checking the Configuration...................................................................................................................8-7

8.4 Configuration Examples..................................................................................................................................8-88.4.1 Example for Configuring PoE on the Switch.........................................................................................8-8

9 ALS Configuration.....................................................................................................................9-19.1 ALS Overview.................................................................................................................................................9-29.2 ALS Features Supported by the S5300...........................................................................................................9-29.3 Configuring ALS.............................................................................................................................................9-3

9.3.1 Establishing the Configuration Task......................................................................................................9-49.3.2 Enabling ALS on an Interface................................................................................................................9-49.3.3 (Optional) Setting the Restart Mode of the Laser..................................................................................9-59.3.4 (Optional) Starting the Laser Manually................................................................................................. 9-69.3.5 (Optional) Setting the ALS Pulse Interval and Width of the Laser........................................................9-79.3.6 Checking the Configuration...................................................................................................................9-7

9.4 Configuration Examples..................................................................................................................................9-89.4.1 Example for Configuring ALS...............................................................................................................9-8

10 Restarting and Resetting.......................................................................................................10-110.1 Introduction.................................................................................................................................................10-2

10.1.1 Process of Starting the S5300.............................................................................................................10-210.1.2 Process of Starting the BootROM......................................................................................................10-2

10.2 Restarting the S5300 Immediately..............................................................................................................10-310.2.1 Restarting the S5300 Immediately Through Command Lines...........................................................10-410.2.2 Restarting the S5300 Through the Power Button on the S5300........................................................10-4

10.3 Restarting the S5300 at a Fixed Time.........................................................................................................10-5



ix

Figures

Figure 1-1 Basic process of Auto-Config.............................................................................................................1-4Figure 1-2 Auto-Config networking where the DHCP server, FTP/TFTP server, and unconfigured switch are onthe same network segment.................................................................................................................................... 1-6Figure 1-3 Auto-Config networking where the DHCP server, FTP/TFTP server, and unconfigured switches areon different network segments..............................................................................................................................1-9Figure 2-1 Networking diagram of configuring NAP-based remote deployment................................................2-8Figure 2-2 Networking diagram of configuring NAP-based remote deployment..............................................2-10Figure 3-1 Networking diagram of a stack system...............................................................................................3-6Figure 3-2 Networking diagram of a stack system...............................................................................................3-7Figure 3-3 Ring Topology....................................................................................................................................3-9Figure 3-4 link Topology..................................................................................................................................... 3-9Figure 3-5 Networking of a stack in a ring topology.........................................................................................3-14Figure 6-1 Functions of the information channel.................................................................................................6-4Figure 6-2 Format of the output logs....................................................................................................................6-5Figure 6-3 Format of the output alarms................................................................................................................6-7Figure 6-4 Networking of sending logs to the log host......................................................................................6-15Figure 7-1 Schematic diagram of interface mirroring..........................................................................................7-4Figure 7-2 Schematic diagram of flow mirroring.................................................................................................7-4Figure 7-3 Networking diagram of RSPAN.........................................................................................................7-5Figure 7-4 Networking diagram of local port mirroring....................................................................................7-36Figure 7-5 Networking diagram of local VLAN mapping.................................................................................7-38Figure 7-6 Networking diagram of local MAC address mirroring.....................................................................7-40Figure 7-7 Networking diagram of local flow mirroring...................................................................................7-42Figure 7-8 Networking diagram of remote port mirroring.................................................................................7-45Figure 7-9 Networking for changing the observing port....................................................................................7-48Figure 8-1 Networking diagram of PoE configurations.......................................................................................8-8Figure 9-1 Connecting switches through fibers................................................................................................... 9-2Figure 9-2 Connecting the switch and ONT through the fiber.............................................................................9-2Figure 9-3 ALS application..................................................................................................................................9-8Figure 10-1 Process of starting the S5300..........................................................................................................10-2

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management Figures


xi

Tables

Table 6-1 Description of the severity levels of information.................................................................................6-2Table 6-2 Association relationship between the information channels and output directions.............................6-4Table 6-3 Description of each field in the format of logs.....................................................................................6-6Table 6-4 Description of each field of the format of alarms................................................................................6-7

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management Tables


xiii

1 Auto-Config

About This Chapter

This chapter describes the concept, working mechanism, and deployment of Auto-Config.

1.1 OverviewThis section describes the functions, application scenarios, and terms of Auto-Config.

1.2 Auto-Config Features Supported by the S5300This section describes how Auto-Config runs on the S5300.

1.3 Deploying Unconfigured Switches (Same Network Segment)This section describes how to deploy S5300es without configuration file.

1.4 Deploying Unconfigured Switches (Different Network Segments)This section describes how to deploy unconfigured S5300es.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 1 Auto-Config


1-1

1.1 OverviewThis section describes the functions, application scenarios, and terms of Auto-Config.

When a new switch or a switch without any configuration file is powered on, Auto-Config runsautomatically to obtain a configuration file. With the Auto-Config function, the networkadministrator can manage new switches or switches without any configuration file remotely.

NOTEThe Auto-Config function is applicable to new switches or switches without any configuration file(hereinafter referred to as unconfigured switches).

The Auto-Config function has the following advantages:l The maintenance personnel do not need to manually configure each switch. With this

function, a few maintenance personnel can maintenance widely deployed devices.l Auto-Config simplifies the network configurations and implements unified management

and remote debugging on switches.l With Auto-Config, switches can automatically download corresponding configuration

files, which greatly reduces the workload of network administrators.

Intermediate FileThe intermediate file lswnet.cfg is used in the Auto-Config process. The intermediate file recordsthe mapping between MAC addresses of switches and names of configuration files. After anunconfigured switch obtains the IP address of the FTP/TFTP server, it downloads thelswnet.cfg file from the FTP/TFTP server to search for the name of the required configurationfile, and then downloads the configuration file from the FTP/TFTP server.

For example, if the MAC address of an S5300 is 0018-82C5-AA89 and the S5300 needs todownload the configuration file S5300.cfg, the contents of the intermediate file are as follows:

0018-82C5-AA89 S5300.cfg

NOTE

If the configuration file is located on the FTP or TFTP server, its extension must be .cfg.

A MAC address and a configuration file name are separated by a space character. The format of a MACaddress is xxxx-xxxx-xxxx-xxxx. The name of a configuration file contains up to 48 characters, includingthe extension .cfg. The name is case insensitive and cannot contain special characters. It is recommendedthat the name consists of English letters, numbers, and underscore (_).

If multiple unconfigured switch need to be configured, each row in the intermediate file records the MACaddress of a switch and the name of the configuration file that the switch requires.

Default Configuration FileThe default configuration file is a file named lswdef.cfg in the download directory of the FTP/TFTP server. The default configuration file can be used by multiple devices and is usuallyadopted when downloading a specified configuration file fails.

Option 150The Option 150 field is configured on the DHCP server to specify the IP address of the TFTPserver.

1 Auto-ConfigQuidway S5300 Series Ethernet Switches


1-2 Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

Issue 03 (2011-01-30)

Option 14xThe Option 14x field is configured on the DHCP server to specify the IP address, user name,and password of the FTP server.l Option 141: specifies the user name of the FTP user.l Option 142: specifies the password of the FTP user.l Option 143: specifies the IP address of the FTP server.

1.2 Auto-Config Features Supported by the S5300This section describes how Auto-Config runs on the S5300.

Figure 1-1 shows the basic process of Auto-Config.



1-3

Figure 1-1 Basic process of Auto-Config

Delete the timer for obtaining a

configuration file

Power on a switch

Switch is without any configuration file?

Load the existing configuration file

Start

Auto-Config is enabled?

Create a timer for obtaining a configuration file

Load default configurations and initiate Auto-Config

Start the switch according to default configurations

Timer expires?

File with the extension .cfg or .zip

exists in the flash memory?

Switch is added to an HGMP

culster?

Obtain a configuration file when the timer expires

Configuration file is obtained?

Create a configuration validation timer and delete the timer for obtaining a configuration file

Configuration file takes effect when the configuration validation

timer expires

Delete the configuration validation timer

End

Yes

No

Yes

No

Yes

No

No

No

No

Yes

Yes

Yes

Configuration file is obtained within

24 consecutive timeout periods?

Yes

No




Issue 03 (2011-01-30)

The Auto-Config process can be divided into three phases:

l StartupAfter being powered on, an unconfigured switch checks whether there is a configurationfile (*.cfg or *.zip) in the flash memory, and then takes actions according to the checkingresult:

– If the switch detects a configuration file, it loads the configuration file to complete thestartup.

– If the switch does not detect any configuration file, it checks whether Auto-Config isenabled. If Auto-Config is enabled, the switch starts a 5-minute timer for obtaining aconfiguration file and then load the default configuration to complete the startup. IfAuto-Config is disabled, the switch loads the default configuration to complete thestartup.

l Obtaining a configuration file when the timer expiresWhen the timer set for obtaining a configuration file expires, the switch checks whether aconfiguration file is saved in the flash memory. If the flash memory does not contain anyconfiguration file, the switch checks whether it is added to a Huawei Group ManagementProtocol (HGMP) cluster. If the switch is not in any HGMP cluster, the switch begins toobtain a configuration file as follows:

1. Obtaining the IP address and information about the FTP/TFTP serverA switch that does not load any configuration file automatically enables the DHCPclient function on the VLANIF1 interface in Up state. VLANIF1 then broadcastsDHCP Request packets (presuming that the DHCP server has been configured withthe address pool, Option 150 or Option 14x, and gateway information). Then, theDHCP server sends the related configurations to the switch, including the IP addressallocated to the switch, IP address of the FTP/TFTP server, FTP user name andpassword, and default gateway.If the switch fails to obtain the IP address of the FTP/TFTP server, the switch starts acounter. If the switch fails to obtain the IP address 24 times consecutively (that is, in2 hours), it disables the timer for obtaining a configuration file. Then, the switchfunctions as a hub.

2. Downloading a configuration fileAfter the switch that does not load any configuration file obtains the IP address of theFTP/TFTP server, it accesses the FTP/TFTP server to obtain a configuration filethrough Layer 2 or Layer 3 forwarding.

(1) The switch downloads the intermediate file lswnet.cfg from the FTP/TFTPserver.

(2) The switch searches for the name of the required configuration file, and thendownloads the configuration file from the FTP/TFTP server.

(3) If downloading the configuration file fails, the switch attempts to download thedefault configuration file lswdef.cfg. If downloading the default configurationfile lswdef.cfg fails, the switch waits until the timer expires and then repeats theprocess to obtain a configuration file.

l Loading a configuration fileAfter downloading a configuration file, the switch starts a 2-hour configuration validationtimer and deletes the timer for obtaining a configuration file. When the 2-hour timer expires,the switch deletes the existing default configurations, loads the downloaded configurationfile, and makes the configuration file take effect without being restarted. The switch



1-5

automatically saves the configuration file to the flash memory, and then deletes theconfiguration validation timer.

1.3 Deploying Unconfigured Switches (Same NetworkSegment)

This section describes how to deploy S5300es without configuration file.

1.3.1 Establishing the Configuration Task

1.3.2 Configuring the DHCP Server

1.3.3 Configuring the FTP/TFTP Server

1.3.4 Checking the Configuration


Applicable Environment

As shown in Figure 1-2, unconfigured switches are reachable from a DHCP server. A PC isconnected to the DHCP server and functions as an FTP or a TFTP server to store configurationfiles. After the DHCP server and FTP/TFTP server are configured, every switch obtains aconfiguration file through Auto-Config.

The DHCP server, FTP/TFTP server, and switches are deployed on the same network segment.

Figure 1-2 Auto-Config networking where the DHCP server, FTP/TFTP server, andunconfigured switch are on the same network segment

SwitchA

SwitchC

SwitchB

DHCP Server FTP/TFTP Server

Operator

Pre-configuration Tasks

Before deploying unconfigured switches, complete the following tasks:l Ensuring that there are routes from the DHCP server and FTP/TFTP server to the switchesl Ensuring that there is no *.cfg or *.zip file except the *web.zip and web.zip files in the

flash memory of each switch




Issue 03 (2011-01-30)

l Ensuring that the switches are not added to any HGMP cluster

Data Preparation

To deploy unconfigured switches, you need the following data.

No.

Data

1 Interconnection information about the upstream interfaces on each S5300 and thedownstream interfaces on the DHCP server

2 MAC address of each unconfigured switch

3 IP address, mask, address pool, and Option 150 or Option 14x of the DHCP server

4 IP address, default configuration file, and required configuration files on the FTP/TFTPserver


ContextThe configuration procedure varies according to the device type of the DHCP server. Therefore,the configuration procedure is not described and only the configuration contents are provided.

NOTEThe DHCP server must support either Option 150 or Option 14x.

Procedurel Enable DHCP server.

l Configure an address pool, including the address range and Option 150 (or Option 14x).

It is required that the address pool be on the same network segment with unconfiguredswitches and the FTP/TFTP server.

NOTEPay attention to the following points when configuring Option 150 or Option 14x:

l When new switches obtain configuration file through TFTP, the DHCP server must supportOption 150.

l When new switches obtain configuration files through FTP, the DHCP server must supportOption 141, Option 142, and Option 143.

l If both Option 150 and Option 14x are configured on the DHCP server, Option 150 takesprecedence over Option 14x.

l If you use ordinary characters to configure Option 150 or Option 143 on the DHCP server, theAuto-Config module cannot recognize the IP address, which results in an Auto-Config failure.

l Add the downstream interface on the DHCP server to the management VLAN in accessmode and assign an IP address on the same network segment as the IP address of the DHCPserver to the management VLAN.



1-7

After Auto-Config is enabled, packets from an unconfigured switch do not carry tags.Therefore, ensure that untagged packets can be transmitted between unconfigured switchesand the DHCP server.

----End


ContextThe configuration procedure varies according to the device type of the FTP/TFTP server.Therefore, the configuration procedure is not described and only the configuration contents areprovided.

Procedurel Set the IP address of the FTP/TFTP server.

For an FTP server, the IP address must be the same as the value of Option 143 configuredon the DHCP server; for a TFTP server, the IP address must be the same as the value ofOption 150 configured on the DHCP server.

l Create and configure an intermediate file.

The intermediate file is configured according to the MAC addresses of unconfiguredswitches and the names of required configuration files. For the format of the intermediatefile, see 1.1 Overview.

l Save the intermediate file, default configuration file, and required configuration files to theworking directory on the FTP/TFTP server.

----End


Prerequisite

The configurations of the DHCP server and FTP/TFTP server are complete.

ContextYou can check different items in different phases in the Auto-Config process to confirm thatAuto-Config runs properly.

Procedure

Step 1 Five minutes after unconfigured switches are powered on, check address allocation on the DHCPserver to confirm that the switches are connected to the DHCP server.

NOTE

If the switches are connected to the DHCP server, you can log in to the switches through Telnet but do notconfigure the switches.

Step 2 Five minutes after the switches obtain IP addresses, check the file downloading log on the FTP/TFTP server or log in to the switches to confirm that correct configuration files have beendownloaded.




Issue 03 (2011-01-30)

NOTEDo not save a configuration file to a switch to be configured immediately after the configuration file isdownloaded; otherwise, only a temporary configuration file is saved because the configurations have nottaken effect.

Step 3 Wait 2 hours for the downloaded configuration file to take effect, and then run the displaycurrent-configuration command to check whether the configurations take effect.

NOTE

If you access the switch when it is busy delivering configurations in the Auto-Config process, the switchmay not respond in real time.After the configurations take effect, modify the configuration of the downstream interface on the DHCPserver as required.

----End

1.4 Deploying Unconfigured Switches (Different NetworkSegments)

This section describes how to deploy unconfigured S5300es.

1.4.1 Establishing the Configuration Task1.4.2 Configuring the DHCP Server1.4.3 Configuring DHCP Relay1.4.4 Configuring the FTP/TFTP Server1.4.5 Checking the Configuration


Applicable EnvironmentAs shown in Figure 1-3, unconfigured switches are reachable from a DHCP relay and a DHCPserver. A PC is connected to the DHCP server and functions as an FTP or a TFTP server to storeconfiguration files. After the DHCP server and FTP/TFTP server are configured, every switchobtains a configuration file through Auto-Config.

The DHCP server, FTP/TFTP server, and switches are deployed on different network segments.

Figure 1-3 Auto-Config networking where the DHCP server, FTP/TFTP server, andunconfigured switches are on different network segments

SwitchA

SwitchC

SwitchBDHCP Server FTP/TFTP Server

Operator

DHCP Relay

Network



1-9

Pre-configuration TasksBefore deploying unconfigured switches, complete the following tasks:l Ensuring that there are routes from the DHCP server, DHCP relay, and FTP/TFTP server

to the switchesl Ensuring that there is no *.cfg or *.zip file except the *web.zip and web.zip files in the

flash memory of each switchl Ensuring that the switches are not added to any HGMP cluster

Data PreparationTo deploy unconfigured switches, you need the following data.

No.

Data

1 Interconnection information about the upstream interfaces on each S5300 and thedownstream interfaces on the DHCP relay

2 Interconnection information about the DHCP relay and DHCP server

3 MAC address of each unconfigured switch

4 IP address, mask, address pool, and Option 150 or Option 14x of the DHCP server

5 IP address, mask, and relay address of the DHCP relay

6 IP address, default configuration file, and required configuration files on the FTP/TFTPserver


ContextThe configuration procedure varies according to the device type of the DHCP server. Therefore,the configuration procedure is not described and only the configuration contents are provided.

NOTEThe DHCP server must support either Option 150 or Option 14x.

Procedurel Enable DHCP server.l Configure an address pool, including the address range, gateway, and Option 150 (or Option

14x).




Issue 03 (2011-01-30)

NOTEPay attention to the following points when configuring Option 150 or Option 14x:

l When new switches obtain configuration file through TFTP, the DHCP server must supportOption 150.

l When new switches obtain configuration files through FTP, the DHCP server must supportOption 141, Option 142, and Option 143.

l If both Option 150 and Option 14x are configured on the DHCP server, Option 150 takesprecedence over Option 14x.

l If you use ordinary characters to configure Option 150 or Option 143 on the DHCP server, theAuto-Config module cannot recognize the IP address, which results in an Auto-Config failure.

----End

1.4.3 Configuring DHCP Relay

ContextThe configuration procedure varies according to the device type of the DHCP relay. Therefore,the configuration procedure is not described and only the configuration contents are provided.

Procedurel Enable DHCP relay.l Configure the upstream and downstream interfaces.

You need to configure the IP address and mask for the upstream interface and configurethe IP address, mask, and DHCP relay address for the downstream interface.

NOTEYou can temporarily set the IP address of the downstream interface on the same network segmentwith the IP addresses of unconfigured switches, and then add the downstream interface to themanagement VLAN in access mode.

----End


ContextThe configuration procedure varies with the device type of the FTP/TFTP server. Therefore, theconfiguration procedure is not described and only the configuration contents are provided.

Procedurel Set the IP address of the FTP/TFTP server.

For an FTP server, the IP address must be the same as the value of Option 143 configuredon the DHCP server; for a TFTP server, the IP address must be the same as the value ofOption 150 configured on the DHCP server.

l Create and configure an intermediate file.

The intermediate file is configured according to the MAC addresses of unconfiguredswitches and the names of required configuration files. For the format of the intermediatefile, see 1.1 Overview.



1-11

l Save the intermediate file, default configuration file, and required configuration files to theworking directory on the FTP/TFTP server.

----End


PrerequisiteThe configurations of the DHCP server, DHCP relay, and FTP/TFTP server are complete.

ContextYou can check different items in different phases in the Auto-Config process to confirm thatAuto-Config runs properly.

Procedure

Step 1 Five minutes after unconfigured switches are powered on, check address allocation on the DHCPserver to confirm that the switches are connected to the DHCP server.

NOTE

If the switches are connected to the DHCP server, you can log in to the switches through Telnet but do notconfigure the switches.

Step 2 Five minutes after the switches obtain IP addresses, check the file downloading log on the FTP/TFTP server or log in to the switches to confirm that correct configuration files have beendownloaded.

NOTEDo not save a configuration file to a switch to be configured immediately after the configuration file isdownloaded; otherwise, only a temporary configuration file is saved because the configurations have nottaken effect.

Step 3 Wait 2 hours for the downloaded configuration file to take effect, and then run the displaycurrent-configuration command to check whether the configurations take effect.

NOTE

If you access the switch when it is busy delivering configurations in the Auto-Config process, the switchmay not respond in real time.

After the configurations take effect, modify the configuration of the downstream interface on the DHCPrelay as required.

----End




Issue 03 (2011-01-30)

2 NAP Configuration

About This Chapter

This chapter describes how to configure the Neighbor Access Protocol (NAP) on the S5300.

2.1 NAP OverviewNAP is a Huawei proprietary protocol that implements remote configuration and deployment ofunconfigured devices. You can log in to an unconfigured device from a directly connected deviceand configure the unconfigured device remotely through NAP.

2.2 Configuring NAP-based Remote DeploymentUsing NAP, you can remotely log in to devices with empty configurations to implement remotedeployment.

2.3 Configuration ExamplesThis section provides upgrade and maintenance examples together with the configurationflowchart. The configuration examples explain networking requirements, configuration notes,and configuration roadmap.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 2 NAP Configuration


2-1

2.1 NAP OverviewNAP is a Huawei proprietary protocol that implements remote configuration and deployment ofunconfigured devices. You can log in to an unconfigured device from a directly connected deviceand configure the unconfigured device remotely through NAP.

Usually, a device is installed with only necessary software before delivery and no configurationis made. Therefore, engineers must configure and commission new devices on site but cannotlog in to the devices remotely. This makes the deployment inconvenient and increases the costsof project operation and delivery.

The Huawei Group Management Protocol (HGMP) implements remote configuration on Layer2 networks and is applicable to Ethernet networks. NAP implements remote configuration onLayer 3 networks. It establishes a temporary neighbor relationship between a configured deviceand an unconfigured device that are directly connected through physical links. Then you can login to the unconfigured device from the configured device and configure the unconfigured deviceremotely. NAP greatly reduces the costs of network operation, maintenance, and delivery.

2.2 Configuring NAP-based Remote DeploymentUsing NAP, you can remotely log in to devices with empty configurations to implement remotedeployment.

Context

CAUTIONAfter the device with an empty configuration is powered on and started, you must make surethat its interfaces connected to the devices on the current network are Up and support NAP;otherwise, the function of NAP-based remote deployment cannot take effect.

2.2.1 Establishing the Configuration TaskBefore configuring NAP-based remote deployment, familiarize yourself with the applicableenvironment, complete the pre-configuration tasks, and obtain the required data. This can helpyou complete the configuration task quickly and accurately.

2.2.2 Configuring and Starting the NAP Master InterfaceYou can assign an IP address to the NAP master interface or use the IP address that isautomatically allocated by the system to start the NAP master interface.

2.2.3 Remote LoginAfter the neighbor relationship is set up, you can log in to the NAP slave device from the NAPmaster device.

2.2.4 Disabling NAP on the Slave DeviceIf the NAP function is no longer required, you need to disable NAP on the slave interface of theslave device.


2 NAP ConfigurationQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

After configuring NAP-based remote deployment, you can view the NAP status globally or ona specified interface.

2.2.1 Establishing the Configuration TaskBefore configuring NAP-based remote deployment, familiarize yourself with the applicableenvironment, complete the pre-configuration tasks, and obtain the required data. This can helpyou complete the configuration task quickly and accurately.


To deploy devices having empty configurations, you can use NAP to perform remote login tothe devices from a device in the current network. In this manner, you can implement remotedeployment of devices.


Before configuring NAP-based remote deployment, complete the following tasks:

l Connecting the device having an empty configuration to a device in the current networkvia a single hop by using network cables

l Ensuring that the interfaces connecting the device with an empty configuration and thedevice in the current network are both in the Up state, and support NAP.

Data PreparationNOTE

l If the IP addresses used for establishing NAP connections are to be manually configured, you need toprepare the following data before configuring NAP.

l Conversely, if the IP addresses for establishing NAP connections are to be automatically configured,you can skip this.

To configure NAP-based remote deployment, you need the following data.

No. Data

1 Two primary IP addresses. The two IP addresses are primary IP addresses for themaster interface and the slave interface respectively, and should be on the samenetwork segment.

2 Two secondary IP addresses. The two IP addresses are secondary IP addresses forthe master interface and the slave interface respectively, and should be on the samenetwork segment.

2.2.2 Configuring and Starting the NAP Master InterfaceYou can assign an IP address to the NAP master interface or use the IP address that isautomatically allocated by the system to start the NAP master interface.



2-3

Context

CAUTIONIf commands affecting the IP address configuration or IP packet forwarding (such asconfigurations and commands related to the VPN, Eth-Trunk, or Layer 2 interface) exist ondevice of the master interface, NAP enabled on the master interface becomes unavailable. Youare recommended to delete these commands and re-enable NAP.

Do as follows on the switch to configure and start the NAP master interface.

In NAP, IP addresses can be allocated either automatically or manually.

Procedurel Automatic allocation of IP addresses

1. Run:system-view

The system view is displayed.2. Run:

interface interface-type interface-number

The interface view is displayed.3. Run:

nap port master

The NAP Master interface is configured and started.l Manual IP address allocation

Two methods are available for manually allocating IP addresses. You can choose themethod according to actual needs.You can specify the NAP IP address pool. Then, IP addresses are automatically allocatedto the IP address pool. To use this method, do as follows.1. Run:

system-view


nap ip-pool ip-address mask-length

An IP address pool is configured for NAP.

The default IP address pool for establishing NAP connections is 10.167.253.0/24. Youcan run the nap ip-pool ip-address mask-length command to change the IP addresspool.

NOTE

After NAP is started on the master device, the IP address pool cannot be changed.

3. Run:interface interface-type interface-number




Issue 03 (2011-01-30)


nap port master

The NAP Master interface is configured and started.You can also specify the NAP IP addresses. To use this method, do as follows.1. Run:

system-view




nap local-ip mast-inter-mast-ip sub-ip mast-inter-sub-ip peer-ip sub-inter-mast-ip sub-ip sub-inter-sub-ip mask-length

IP addresses are configured for establishing NAP connections.

The default IP address pool for establishing NAP connections is 10.167.253.0/24.

When configuring IP addresses, ensure that the primary IP addresses of both the masterand the slave interfaces are on the same network segment, and that the secondary IPaddresses of both the master and the slave interfaces are on the same network segment.

4. Run:nap port master

The NAP master interface is configured and started.

----End

2.2.3 Remote LoginAfter the neighbor relationship is set up, you can log in to the NAP slave device from the NAPmaster device.

ContextUsing the display nap interface command, you can view the NAP status of an interface toensure that the interface is assigned a correct IP address.

Do as follows on the switch where the NAP master interface is configured.

Procedure

Step 1 Run:system-view

The system view is displayed.

Step 2 Run:interface interface-type interface-number

The interface view is displayed.



2-5

Step 3 Run:nap login neighbor

The login to the slave device from the master device is performed.

l If the slave device has an empty configuration, you can log in to the slave device from themaster device without a user name and a password.

l If, however, the slave device is configured with user name(s) and password(s), you mustenter the correct user name and password to perform a NAP-based remote login to the slavedevice.

NOTETo ensure security for NAP, the slave device having an empty configuration checks the source address ofthe Telnet login. If the Telnet source address is the NAP address of the master device that is telnetting tothe slave device, the slave device allows the master device to directly log in without being authenticated.This is because by default, the user level of the remote login based on the NAP address is the same as thelogin through the console interface, which enjoys the highest user level. If the Telnet source address is notthe NAP address of the master device, the remote login fails.

----End

2.2.4 Disabling NAP on the Slave DeviceIf the NAP function is no longer required, you need to disable NAP on the slave interface of theslave device.

ContextThe master device has logged in to the slave device through Telnet. The NAP function is nolonger required, and to ensure security of the network, NAP should be globally disabled on theslave interface of the slave device.

Do as follows on the switch that is configured as the NAP slave device.

Procedure



Step 2 Run:undo nap slave enable

NAP is disabled on the slave device.

----End

2.2.5 Checking the ConfigurationAfter configuring NAP-based remote deployment, you can view the NAP status globally or ona specified interface.

PrerequisiteNAP-based remote deployment has been completed.




Issue 03 (2011-01-30)

ProcedureStep 1 Using the display nap status command, you can view the current NAP status.

Step 2 Using the display nap interface [ interface-type interface-number ] command, you can viewthe NAP status of the specified interface.

----End

ExampleRun the display nap status command to view the current NAP status.

<Quidway> display nap status Slave port status : Enable Nap ip-pool/Mask : 12.12.12.0/24

Run the display nap interface interface-type interface-number command to view the NAP statusof the specified interface.

<Quidway> display nap interface gigabitethernet0/0/1l If the interface is not assigned an IP address, the following information is displayed.

------------------------------------------------------ NAP master port list: Port count : 2------------------------------------------------------ Port property : Master Current status : DETECTING Local port : GigabitEthernet0/0/1 Peer port : GigabitEthernet0/0/1 Local primary ip : NULL Peer primary ip : NULL Local secondary ip : NULL Peer secondary ip : NULL Hello time : 3s Linked time : 00:00:00------------------------------------------------------ Port property : Master Current status : DETECTING Local port : GigabitEthernet0/0/2 Peer port : GigabitEthernet0/0/2 Local primary ip : NULL Peer primary ip : NULL Local secondary ip : NULL Peer secondary ip : NULL Hello time : 3s Linked time : 00:00:00------------------------------------------------------

l If the interface is assigned an IP address, the following information is displayed.------------------------------------------------------ NAP master port list : Port count : 2------------------------------------------------------ Port property : Master Current status : IP-ASSIGNED Local port : GigabitEthernet0/0/1 Peer port : GigabitEthernet0/0/1 Local primary ip : 12.12.12.5 Peer primary ip : 12.12.12.6 Local secondary ip : 12.12.12.9 Peer secondary ip : 12.12.12.10 Hello time : 3s Linked time : 00:09:12------------------------------------------------------ Port property : Master



2-7

Current status : IP-ASSIGNED Local port : GigabitEthernet0/0/2 Peer port : GigabitEthernet0/0/2 Local primary ip : 10.10.10.5 Peer primary ip : 10.10.10.6 Local secondary ip : 10.10.10.9 Peer secondary ip : 10.10.10.10 Hello time : 3s Linked time : 00:03:41------------------------------------------------------

2.3 Configuration ExamplesThis section provides upgrade and maintenance examples together with the configurationflowchart. The configuration examples explain networking requirements, configuration notes,and configuration roadmap.

2.3.1 Example for Configuring NAP-based Remote Deployment in Automatic ModeIn this example, the temporary neighbor relationship is set up between a switch and anotherswitch that has the empty configuration to implement remote deployment in automatic mode.

2.3.2 Example for Configuring NAP-based Remote Deployment in Static ModeIn this example, the temporary neighbor relationship is set up between the switch and the devicewith the empty configuration and IP addresses are assigned to the switch and the device toimplement remote deployment in manual mode.

2.3.1 Example for Configuring NAP-based Remote Deployment inAutomatic Mode

In this example, the temporary neighbor relationship is set up between a switch and anotherswitch that has the empty configuration to implement remote deployment in automatic mode.

Networking RequirementsAs shown in Figure 2-1, the user needs to perform a remote login to Switch B from Switch A.Switch B is the master device, and temporary neighbor relationship is to be set up betweenSwitch B and Switch C having an empty configuration. Switch B and Switch C need to be directlyconnected via a single hop. Both the interfaces connecting Switch B and Switch C should be inthe Up state, and should support NAP.

Figure 2-1 Networking diagram of configuring NAP-based remote deployment

Network

SwitchAPC SwitchB SwitchC

Configuration RoadmapThe configuration roadmap is as follows:




Issue 03 (2011-01-30)

1. Configure a primary IP address and a secondary IP address on Switch B.2. Configure the NAP master interface on Switch B.3. Telnet to Switch C from Switch B by means of NAP.

Data PreparationNone

ProcedureStep 1 Configuring the NAP master interface

# Do as follows on Switch B.

<Quidway> system-view[Quidway] sysname SwitchB[SwitchB] interface gigabitethernet0/0/1[SwitchB-GigabitEthernet0/0/1] nap port master

Step 2 Logging in to the slave device from the master device.


[SwitchB-GigabitEthernet0/0/1] nap login neighborTrying 10.167.253.10 ...Press CTRL+K to abortConnected to 10.167.253.10 ...

Info: The max number of VTY users is 10, and the number of current VTY users on line is 1.

Step 3 Shutting down NAP on the slave device.

# Do as follows on Switch C.

<Quidway> system-view[Quidway] sysname SwitchC[SwitchC] undo nap slave enable

----End

Configuration FilesNone

2.3.2 Example for Configuring NAP-based Remote Deployment inStatic Mode

In this example, the temporary neighbor relationship is set up between the switch and the devicewith the empty configuration and IP addresses are assigned to the switch and the device toimplement remote deployment in manual mode.

Networking RequirementsAs shown in Figure 2-2, the user needs to perform a remote login to Switch B from Switch A.Switch B is the master device, and temporary neighbor relationship is to be set up betweenSwitch B and Switch C having an empty configuration. Switch B and Switch C need to be directlyconnected via a single hop. Both the interfaces connecting Switch B and Switch C should be inthe Up state, and should support NAP.



2-9

Figure 2-2 Networking diagram of configuring NAP-based remote deployment

Network

SwitchAPC SwitchB SwitchC


1. Configure a primary IP address and a secondary IP address on Switch B.2. Configure the NAP master interface on Switch B.3. Telnet to Switch C from Switch B by means of NAP.

Data PreparationTo complete the configuration, you need the following data:

l Two primary IP addresses. The two IP addresses are primary IP addresses for the masterinterface and the slave interface respectively, and should be on the same network segment.

l Two secondary IP addresses. The two IP addresses are secondary IP addresses for themaster interface and the slave interface respectively, and should be on the same networksegment.

Procedure

Step 1 Configuring IP addresses for establishing NAP connections.


<Quidway> system-view[Quidway] sysname SwitchB[SwitchB] nap ip-pool 12.12.12.0 24

Step 2 Configuring the NAP master interface.


[SwitchB] interface gigabitethernet0/0/1[Switch-GigabitEthernet0/0/1] nap port master

Step 3 Configuring primary IP addresses and secondary IP addresses for the master and slave interfaces.


[SwitchB-GigabitEthernet0/0/1] nap local-ip 12.12.12.5 sub-ip 12.12.12.9 peer-ip 12.12.12.6 sub-ip 12.12.12.10 30Are you sure to continue?[Y/N] y

# After the preceding configurations, on Switch B, run the display nap status command to findthat the NAP protocol is enabled, and run the display nap interface command to find that theprimary IP addresses and secondary IP addresses are successfully assigned to the master andslave interfaces.




Issue 03 (2011-01-30)

[SwitchB-GigabitEthernet0/0/1] display nap status Slave port status : Enable Nap ip-pool/Mask : 12.12.12.0/24[SwitchB-GigabitEthernet0/0/1] display nap interface------------------------------------------------------ NAP master port list Port count : 1------------------------------------------------------ Port property : Master Current status : IP-ASSIGNED local port : GigabitEthernet0/0/1 peer port : GigabitEthernet0/0/1 local pri ip : 12.12.12.5 peer pri ip : 12.12.12.6 local sec ip : 12.12.12.9 peer sec ip : 12.12.12.10 hello time : 3s linked time : 00:01:00------------------------------------------------------

Step 4 Logging in to the slave device from the master device.


[SwitchB-GigabitEthernet0/0/1] nap login neighborTrying 12.12.12.10 ...Press CTRL+K to abortConnected to 12.12.12.10 ...

Info: The max number of VTY users is 10, and the number of current VTY users on line is 1.

Step 5 Shutting down NAP on the slave device.

# Do as follows on Switch C.

<Quidway> system-view[Quidway] sysname SwitchC[SwitchC] undo nap slave enable

----End

Configuration FilesNone



2-11

3 Stacking

About This Chapter

This chapter describes the basic concepts and configuration methods of the stacking function.

3.1 Stacking OverviewThis section describes the basic concepts of the stacking function.

3.2 Principle of StackingThis section describes how a stack system is set up.

3.3 Features of Stacking Supported by the S5300

3.4 Typical Topology of a StackThis section describes two typical topologies of a stack.

3.5 Configuring the Stacking Function on the S5300This section describes how to configure the stacking function on the S5300.

3.6 Configuration ExamplesThis section provides an example for configuring a stack in a ring topology.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 3 Stacking


3-1

3.1 Stacking OverviewThis section describes the basic concepts of the stacking function.

The stacking function indicates that multiple devices that support the stacking function areconnected together to logically function as one device. Up to nine stack devices are connectedthrough stack cables in a ring or link topology. All stack devices logically function as one deviceto forward packets. Roles of devices in a stack are as follows:

l Master switchA stack has only one master switch. The master switch manages the entire stack system byassigning stack IDs to member switches, collecting information about the stack topology,and notifying all the member switches of the information.

l Standby switchA stack has only one standby switch. The standby switch backs up the master switch. Whenthe master switch is faulty, the standby switch functions as a master switch.

l Slave switchThe slave switch sends packets to inform the master switch of the topology change afterdetecting that a neighbor is lost. Apart from the master switch and standby switch, all theother switches in a stack are slave switches.

The master switch, standby switch, and all the slave switches are all member switches.

Interfaces connecting member switches are stack interfaces, and other interfaces are commonuser interfaces. Member switches are connected through independent stack modules and stackcables.

3.2 Principle of StackingThis section describes how a stack system is set up.

Prerequisites for Setting Up a Stack System

To successfully create a stack system, complete the following tasks:

l Configure the same software version for all the member switches. When the master switchdetects that a new member switch runs a different version, the master switch synchronizessystem version of the member switch.

NOTE

l When the products of the same series are stacked, the switch that is closest to the physical interfaceof the new member switch added to the stack system synchronizes the system version of the newmember switch.

l If no switch in the stack system is of the same series as the new member switch or the system versionof the new member switch cannot be synchronized to the master switch version, the new membercannot join the stack system.

l Use the devices of the same type as the member switches of a stack system, for example,use EI devices or SI devices in a stack system. The EI devices and SI devices cannot beused in the same stack system.

l Connect all devices by using leased stack cables and stack modules.

3 StackingQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

l Ensure that all the stack devices can be started normally.l Ensure that the stacking function is enabled on all the stack devices.

Creation of a Stack SystemIf all the member switches in a stack meet the preceding prerequisites, the stack system isautomatically created when a member switch in the stack is powered on.

The master switch is elected as follows:

l The device that is started first becomes the master switch.l If all the devices are started at the same time, the one of the highest priority becomes the

master switch.l If all the devices are started at the same time and are of the same priority, the one with the

smallest MAC address becomes the master switch.

The standby switch is elected as follows:

l If all the switches excluding the master switch start at the same time, the master switchpreferentially selects the switch connected to stack interface 2 on the master switch as thestandby switch.

l If all the other switches excluding the master switch start at the same time and no switchis connected to stack interface 2 on the master switch, the master switch selects the switchconnected to stack interface 1 on the master switch as the standby switch.

Before the stacking system is created, each switch is an independent entity. That is, each switchhas its own IP address and functions individually. As a result, a user needs to manage each switchindividually. After the stacking system is created, all the member switches are presented as oneunified logical entity. In this manner, a user manages and maintains all the member switches ina stack through one IP address. The stacking protocol elects the master switch, standby switch,and slave switch in a stack. Then, data can be backed up and the active/standby switchover canbe implemented.

The switches are connected through stack cables in a ring or link topology. A master switch iselected among all the member switches through the stacking protocol. The master switchmanages the stacking system by assigning stack IDs to member switches, collecting informationabout the topology of the stack, and informing all the stack members of the topology information.A standby switch is specified by the master switch. The standby switch becomes the masterswitch to manage the stack system if the original master switch is faulty.

After the master, standby, and slave switches are specified, the master switch collects the packetsthat are sent from all the slave switches to report the topology information, and then generatesstack entries accordingly and deliver the entries to all the member switches in the stack.

Adding a Member Switch to a Stack SystemAdding a member switch to a stack system refers to the action of adding a new switch to a stablestack. A member switch can be added to a stack system in two modes: with power on and withpower off. In this manual, member switches are added to a stack system with power off. Addinga member switch to a stack system with power on refers to the action of combining two stacks.(An independent switch can be regarded as a stack system after being enabled with stacking.)The details are described in the scenario of combining two stacks. The member switch to beadded is powered off at first and then restarts after being connected to the stack interface of thestack. The adding of a member switch does not affects the status of the original master switchin the stack.



3-3

The original service configurations on a switch are cleared after the switch is added to a stack.Then, the switch uses global configurations of the master switch. If the configuration file alreadyexists on the master device and an interface already exists in the configuration file, the interfacecan be configured through the configuration file. If an interface does not exist in the configurationfile, the configuration of the interface is null. If the configuration file does not exist on the masterdevice, the default configuration of the interface is used. If the stack ID of the added switchconflicts with the stack ID of another member switch in the stack, the master switch reassignsa stack ID to the added switch. Adding a member switch does not affect the original services inthe stack system.

A stack consists of up to nine switches. The number of the member switches cannot exceed thelimit after new member switches are added to the stack.

Quitting a Stack SystemQuitting a stack system refers to the action of leaving a stack. Different roles inflict differentimpacts on a stack by quitting the stack system. The following describes different situations:

l When the master switch quits a stack system, the neighbor switch detects the change, andthen informs the neighbors of the change and updates the information about the localneighbors. The standby switch becomes the master switch, and then recalculates the stacktopology and informs all the other member switches of the change. In addition, the newmaster switch specifies a member switch as the standby switch, and then runs normally.

l When the standby switch quits a stack system, the master switch re-specifies a memberswitch as the standby switch, and then recalculates the stack topology and informs all theother member switches of the change.

l When a slave switch quits a stack system, the master switch only recalculates the stacktopology and informs all the other switches of the change. The quitting slave switch restartsimmediately.

l When the master and standby switches quit a stack system at the same time, all the othermember switches in the stack system restart and recreate a stack system.

Restarting a Member SwitchIf a stack system runs stably, restarting a member switch indicates that a member switch quitsa stack system first and then rejoins the stack system.

l If the master switch restarts, the standby switch becomes the master switch, and thenspecifies another member switch as the standby switch and synchronizes data to the newstandby switch.

l If the standby switch restarts, the master switch specifies another member switch as thestandby switch and synchronizes data to the new standby switch.

l When the master and standby switches restart at the same time, all the other memberswitches in the stack system restart and recreate a stack system.

When a member switch restarts, the master switch recalculates the stack topology and deliversthe stack routing table. Then, the member switch rejoins the stack as a standby or slave switch.

Replacing a Member SwitchIf a stack system runs stably, replacing a member switch indicates that a member switch quitsthe stack system first and then a new member switch joins the stack system. For more details,see the description of adding a member switch to a stack system and quitting a stack system.




Issue 03 (2011-01-30)

Replacing a member switch requires that the stack cables connecting the replaced switches toother switches be removed.

l If the master switch is replaced, the standby switch becomes the master switch, and thenspecifies another member switch as the standby switch and synchronizes data to the newstandby switch.

l If the standby switch is replaced, the master switch specifies another member switch as thestandby switch and synchronizes data to the new standby switch.

Switchover Between the Master and Standby SwitchesAfter a stack system is created, the standby switch automatically becomes the master switch ifthe master switch is faulty or exits from the stack system. The new master switch specifies thenew slave switch and data is synchronized on the master and slave switches.

l After a stack system is created for the first time, the MAC address of the stack system isthe MAC address of the master switch. When the master switch is faulty or quits the stacksystem, the MAC address of the stack system is immediately switched to be that of thenewly-elected master switch if the function of the delay in switching the MAC address ofthe stack system is disabled. By default, the MAC address switchover is enabled and thedelay for switchover is 10 minutes.

l When a stack system is created, the MAC address of the stack system is switched to be thatof the newly-elected master switch, if the master switch is faulty or quits the stack system,the stack system is configured with the MAC address switchover time, and the quittingswitch does not rejoin the stack within the switchover timeout interval. If the quitting switchrejoins the stack before the switchover timer expires, the switch becomes a slave and theMAC address of the stack system remains unchanged. In this case, the MAC address of thestack system is the MAC address of a slave switch.

l When a slave switch quits a stack system, the MAC address of the stack system is switchedto be that of the master switch, if the MAC address of the stack system is the same as thatof the quitting slave switch and the quitting salve switch does not rejoin the stack after theswitchover timer times out.

Combining Two Stack SystemsIf two stack systems are combined, a new master switch is elected. The running time of the twostack systems is compared and is accurate to minutes. The stack system that has a long runningtime is of a higher priority. If the running time is the same, the election mode in the setup of thestack system is used for electing the master switch. In one stack system, the roles, configurations,and services of the switches keep unchanged. In the other stack system, all the switches restartand join the combined stack system as slave switches. The master switch reassigns stack IDs tothese slave switches and synchronizes its configurations to these slave switches. In addition,services in this stack system are interrupted.

Dividing a Stack SystemDividing a stack system refers to the action of removing certain member switches with poweron. As shown in Figure 3-1, Switch A, Switch B, Switch C, and Switch D form Stack-A.



3-5

Figure 3-1 Networking diagram of a stack system

SwitchA

SwitchC SwitchD

SwitchB

Ethernet

stack link

common link

Stack-A

Switch A is disconnected from Switch B; Switch C is disconnected from Switch D; Switch B isdirectly connected to the Ethernet. As shown in Figure 3-2, Switch A and Switch B form Stack-B; Switch C and Switch D form Stack-C. In this case, Stack-A is divided into Stack-B and Stack-C, and the process of diving a stack system is complete.




Issue 03 (2011-01-30)

Figure 3-2 Networking diagram of a stack system

SwitchA

SwitchC SwitchD

SwitchB

Ethernet

stack link

common link

Stack-B Stack-C

The action of diving a stack system varies with different roles of the removed switches.l After a stack system is divided, the original master and standby switches still belong to the

same stack system. In this case, the master switch recalculates the stack topology andupdates the topology information accordingly. After detecting that the stack protocolpackets time out, the removed slave switches are reset by themselves and reelect the masterswitch. The newly-elected master switch obtains the configurations of the stack systemfrom the flash memory and then restores the configurations of other switches.

l After a stack system is divided, the original master and standby switches belong to differentstack systems. In this case, the original master switch specifies another switch as the standbyswitch in its own stack system. The process of the stack system becoming stable is the sameas that when the standby switch quits the stack system. In the stack system where the originalstandby switch currently belongs, the active/standby switchover is implemented, and theprocess of the stack system becoming stable is the same as that when the master switchquits the stack system.

IP Address and MAC Address Collision After a Stack System Is Divided

The IP address and MAC address of a stack system is configured globally. That is, all the switchesin a stack system share the same IP address and MAC address. When a stack system is divided,configuration collision may occur at Layer 3. For example, a Layer 3 VLANIF interface isconfigured with an IP address 192.168.1.1. After the stack system is divided, two stack systemswith the IP address 192.168.1.1 exist on the network. In this case, IP address and MAC addresscollision occurs. Therefore, collision detection must be implemented at Layer 2 and Layer 3after a stack system is divided.

The dividing of a stack system mentioned here refers to the case that the original master andstandby switches belong to different stack systems after the original stack system is divided. In



3-7

this case, the active/standby switchover is implemented on the stack system where the standbyswitch belongs. After the active/standby switchover, the new master switch specifies the MACaddress of its own as the MAC address of the stack system. In addition, the new master switchsends gratuitous ARP packets to instruct other switches to update their MAC address andimplements IP collision detection. It is required that the two newly-created stack systems be ableto receive gratuitous ARP packets. After the original stack system is divided, the original masterswitch detects IP address collision if receiving gratuitous packets whose source IP address is thesame as the IP address of the master switch. At the same time, the original master switch keepssending gratuitous ARP packets until no ARP packet with the conflicted IP address is received.

3.3 Features of Stacking Supported by the S5300

The features of stacking supported by the S5300 are as follows:l The S5300EI Switch supports the following routing features of stacking:

IPv4 static route, route-policy, OSPF, IPv6 static route, and RIPl The S5300SI Switch supports the following routing features of stacking:

IPv4 static route, IPv6 static route, and RIPl The Switch supports the following Ethernet features of stacking:

Trunk, LACP, Blackhole MAC, Static MAC, Sticky MAC, MAC learning, commonVLAN, MUX VLAN, VLAN stacking, voice VLAN, LLDP-MED for voice VLAN, STP,RSTP, MSTP, VLAN aggregation, port group, port security, and ARP

l The Switch supports the following security features of stacking:802.1x, MAC authentication, AAA, DHCP snooping, attack defense, storm control,broadcast storm suppression, IPSG, MFF, MAC, and ACL

l The Switch supports the following IP service features of stacking:DHCP client, DHCP server, DHCP relay, DNS, and ND

l The Switch supports the following multicast features of stacking:Multicast policy, controllable multicast, IGMP snooping, MLD snooping, and multicastload balancing

l The Switch supports the following network management features of stacking:NTP, RMON, SNMP, HGMP, ping, and tracert

l The S5300EI Switch supports the following reliability features of stacking:VRRP for IPv4, VRRP for IPv6, Smart Link, and Monitor Link

l The S5300SI Switch supports the following reliability features of stacking:Smart Link and Monitor Link

l The Switch supports the following QoS features of stacking:Traffic policy, priority mapping, traffic policing, traffic shaping, congestion avoidance,congestion management, flow mirroring, and port mirroring

l PoE, LLDP-MED for PoE, RSPAN, and information centerl SSH, FTP (server or client), SFTP (server or client) TFTP client, and Telnet

After a stack system is created, the entire stack system logically functions as one switch. Thefeatures supported by stacking are configured the same whether in a stack system or in a non-stack system. For more details, see the related configuration guide.




Issue 03 (2011-01-30)

3.4 Typical Topology of a StackThis section describes two typical topologies of a stack.

Ring TopologyThe typical topology of a stack is a ring topology. As shown in Figure 3-3, stack interfaces onthe Switches are connected through leased stack cables.

NOTE

Do not directly connect stack ports on the same switch to form a loop.

Figure 3-3 Ring Topology

stack link

common link

SwitchA

SwitchC SwitchD

SwitchB

Link TopologyAs shown in Figure 3-4, stack interfaces on the Switches are connected through leased stackcables.

NOTE

Do not directly connect stack ports on the same switch to form a loop.

Figure 3-4 link Topology

SwitchA SwitchB SwitchCPC1 PC2

stack link

common link



3-9

Compared with the link topology, the ring topology enjoys higher reliability. When a stack linkin a ring topology breaks, the ring topology becomes a link topology. The entire stack system,however, runs normally. You are recommended to adopt a ring topology when deployingservices.

3.5 Configuring the Stacking Function on the S5300This section describes how to configure the stacking function on the S5300.


3.5.2 (Optional) Configuring the Reserved VLAN of the StackThis section describes how to configure the reserved VLAN for the stack.

3.5.3 (Optional) Enabling the Stacking Function

3.5.4 (Optional) Configuring a Stack ID for the S5300

3.5.5 (Optional) Configuring a Stack Priority for a Device

3.5.6 (Optional) Configuring the MAC Address Switchover Time



Applicable EnvironmentTo improve the interface density and forwarding capacity of a network, you can configure thestacking function on the S5300. In this manner, you can expand the network capacity andfacilitate users' management.

Pre-configuration TasksBefore creating a stack system, complete the following tasks:l Configuring the same software version for all the member switchesl Using the devices of the same type as the member switches of a stack system, for example,

using EI devices or SI devices in a stack system. The EI devices and SI devices cannot beused in the same stack system.

l Installing stack cards on all devices and connecting the devices through stack cables.l Ensuring that all the stack devices can be started normally

Data PreparationTo configure the stacking function, you need the following data.

No. Data

1 Stack ID of an S5300

2 Stack priority of an S5300




Issue 03 (2011-01-30)

No. Data

3 MAC address switchover time

3.5.2 (Optional) Configuring the Reserved VLAN of the StackThis section describes how to configure the reserved VLAN for the stack.

ContextWhen the default reserved VLAN of the stack is used for other services, you need to configurea new reserved VLAN before enabling the stacking function.

The reserved VLAN of the stack is configured on the master switch.

Procedure



Step 2 Run:stack reserved-vlan vlan-id

The reserved VLAN is configured.

By default, a stack system uses VLAN 4093 as the reserved VLAN.

NOTE

The reserved VLAN cannot be used for other services.

----End

3.5.3 (Optional) Enabling the Stacking Function

ContextBefore connecting stack devices through leased stack cables, do as follows on the stacking-capable devices.

Procedure



Step 2 Run:stack enable

The stacking function is enabled on the S5300.

By default, the stacking function is enabled.



3-11

NOTE

If you run the undo stack enable command to disable the stacking function on the S5300, the configurationtakes effect only after the S5300 is restarted. If you run the stack enable command to enable the stackingfunction on the S5300, the configuration takes effect only after the S5300 is restarted.

----End

3.5.4 (Optional) Configuring a Stack ID for the S5300

ContextStack IDs can be configured before or after the stack system is created. By default, stack IDs ofmember switches in a stack are all 0s. If stack IDs are not configured for member switches beforethe stack system is created, the stack system assigns stack IDs to member switches after beingcreated. After the stack system is created successfully, all the configuration of the stack systemcan be performed on the master switch only.

Procedure



Step 2 Run:stack slot slot-id renumber new-slot-id

A stack ID is configured for a device.

By default, the stack ID of a device is 0.

NOTE

After the stack ID is configured, the configuration takes effect only after the device is restarted. The stackslot-id command is valid only on the device where the stacking function is enabled.

----End

3.5.5 (Optional) Configuring a Stack Priority for a Device

ContextThe stack priority of a device can be configured before or after the stack system is created. Ifthe stack system is created, you can configure stack priorities on the master switch only; if thestack system is not created, you can configure a stack priority on each device.

Procedure



Step 2 Run:stack slot slot-id priority priority




Issue 03 (2011-01-30)

A stack priority is configured for a specified stack device.

By default, the priority value of a device is 100. A great value indicates a high priority.

NOTEBefore the stack system is created, the default stack ID is 0. You can run the display stack and displaystack peers commands to view the stack ID of a device.

----End

3.5.6 (Optional) Configuring the MAC Address Switchover Time

ContextThe MAC address switchover time can be configured before or after the stack system is created.If the MAC address switchover time is configured for all the stack switches before the stacksystem is created, the MAC address switchover time of the stack system is specified by the MACaddress switchover time of the master switch after the stack system is created, and the MACaddress switchover time of other member switches keeps the same as that of the master switch.After the stack system is restarted, the MAC address of the stack is changed into the MACaddress of the new master switch. In this case, the MAC address of the stack system keepsunchanged if the master switch is unchanged. If the stack system is created before the MACaddress switchover time of the system is configured, you can configure the MAC addressswitchover time of the system on the master switch only. In this case, the MAC addressswitchover time of other member switches keeps the same as that of the master switch. TheMAC address of the stack system keeps unchanged after the stack system is restarted. Do asfollows on the devices where the MAC address switchover time is to be configured.

ProcedureStep 1 Run:

system-view


Step 2 Run:stack timer mac-address switch-delay delay-time

The MAC address switchover time of the stack system is configured.

----End


PrerequisiteRun the following commands to check the previous configuration.

Procedurel Run the display stack command to check information about the member switches in a

stack.l Run the display stack configuration command to check the default stack ID and stack

priority when the stack member starts this time and next time.

----End



3-13

ExampleYou can use the display stack command to check stack IDs and priorities of member switchesin a stack.<Quidway> display stackStack topology type : LinkStack systern MAC: 0018-82b1-6eb4MAC switch delay time: 2 minStack reserve vlanid : 4093slot# role Mac address Priority Device type------ ---- -------------- ------ ------- 0 Master 0018-82b1-6eb4 200 S5300 1 Standby 0018-82b1-6eba 150 S5300

You can use the display stack configuration command to check the default stack ID and stackpriority when the stack member starts this time and next time.<Quidway> display stack configurationCurrent slot-id Next slot-id Current Priority Next Priority---------------- ------------- ---------------------- ------------- 0 8 200 200 1 3 150 150

3.6 Configuration ExamplesThis section provides an example for configuring a stack in a ring topology.

3.6.1 Example for Configuring a Stack in a Ring Topology

3.6.1 Example for Configuring a Stack in a Ring Topology

Networking RequirementsAs shown in Figure 3-5, Switch A, Switch B, Switch C, and Switch D form a stack in a ringtopology. The stack system is automatically created. Switch A functions as the master switch,whereas Switch B functions as a standby switch. After the active/standby switchover, the MACaddress of the stack system is immediately switched. To avoid updating MAC addresses of thestack system frequently and wasting system resources, set the MAC address switchover time ofthe stack system to 1 minute after the active/standby switchover.

Figure 3-5 Networking of a stack in a ring topology

SwitchA

SwitchC SwitchD

SwitchB

stack link

common link




Issue 03 (2011-01-30)


l Configure the MAC address switchover time of the stack system on the master switch.

Data PreparationTo complete the configuration, you need the following data:l MAC address switchover time of the stack system

Configuration Procedure1. # Configure the MAC address switchover time of the stack system on Switch A.

<SwitchA> system-view[SwitchA] stack timer mac-address switch-delay 1# Run the display stack command on Switch A to check basic information about a stack.<SwitchA> display stackStack topology type: RingStack system MAC: 0018-82b1-6eb8MAC switch delay time: 1 minStack reserve vlanid : 4093slot# role Mac address Priority Device type------ ---- -------------- ------ ------- 0 Slave 0018-82d2-2e85 100 S5352C-EI 1 Slave 0018-82c6-1f44 100 S5328C-EI-24S 3 Standby 0018-82c6-1f4c 100 S5328C-EI-24S 4 Master 0018-82b1-6eb8 100 S5328C-EI

Configuration FilesNone.



3-15

4 Using display commands to check the statusof the device

About This Chapter

This chapter describes the maintenance, usage of the display commands and the regularexpression.

4.1 IntroductionThis section describes function of display commands.

4.2 Checking the Status of the S5300This section describes how to check the status of the S5300 by using the display commands.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 4 Using display commands to check the status of the device


4-1

4.1 IntroductionThis section describes function of display commands.

You can use display commands to view the status of a device and check whether the device runsnormally.

4.2 Checking the Status of the S5300This section describes how to check the status of the S5300 by using the display commands.

4.2.1 Checking Information About the S5300

4.2.2 Checking the Version of the S5300

4.2.3 Checking the Electronic Labels

4.2.4 Checking Temperature

4.2.5 Checking the External Fan StatusWhen the device temperature is high, you can check whether the external fan is functioningnormally.

4.2.6 Checking the Power Supply StatusBefore replacing a power supply, you need to check the status of the power supply.

4.2.7 Checking the CPU UsageYou can check the CPU utilization statistics and CPU settings.

4.2.8 Checking the Memory Usage

4.2.9 Checking Alarms

4.2.10 Checking the Status of an Interface

4.2.1 Checking Information About the S5300

Context

You can run the following command in any view to check the type and status of a componenton the S5300.

Procedure

Step 1 Run:display device [ slot slot-id ]

Information about a component on the S5300 is displayed.

----End

4.2.2 Checking the Version of the S5300

4 Using display commands to check the status of the deviceQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

ContextYou can run the display version command in any view to check the version of the S5300.

The displayed information includes the type of a card, startup duration, version of the hardware,and version of the software.


display version [ slot slot-id ]

The version of the specified a card is displayed.

----End

4.2.3 Checking the Electronic Labels

ContextYou can run the display elabel command in any view to check the electronic labels.

You can run the display elabel command to check information about the hardware code. Thehardware code provides necessary basis for such services as network installation, networkupgrade, network expansion, device management and maintenance, and device replacement inbatches.

The displayed information includes: type of the card, bar code, Bill of Material (BOM) code,English description, production date, supplier name, issuing number, Common LanguageEquipment Identification (CLEI) code, and sales BOM code.


display elabel [ slot slot-id [ subcard-id ] ]

The electronic labels are displayed.

----End

4.2.4 Checking Temperature

ContextYou can run the following command in any view to check the working temperature of theS5300.


display environment [ slot slot-id ]

The temperature of a temperature-sending SIC is displayed.

----End



4-3

4.2.5 Checking the External Fan StatusWhen the device temperature is high, you can check whether the external fan is functioningnormally.

Procedure

Step 1 Run:display fan [ slot slot-id | verbose ]

The external fan status is displayed.

----End

4.2.6 Checking the Power Supply StatusBefore replacing a power supply, you need to check the status of the power supply.

Procedure

Step 1 Run the following command in any view:display power

The status of each power supply is displayed.

----End

4.2.7 Checking the CPU UsageYou can check the CPU utilization statistics and CPU settings.

Procedure

Step 1 Run:display cpu-usage [ configuration | slave | slot slot-id ]

The CPU utilization statistics and CPU settings are displayed.

----End

4.2.8 Checking the Memory Usage

ContextYou can run the following command in any view to check the memory usage of the S5300.

Procedure

Step 1 Run:display memory-usage [ slave | slot slot-id ]

The memory usage is displayed.

----End

4 Using display commands to check the status of the deviceQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

4.2.9 Checking Alarms

ContextYou can run the following command in any view to check alarms on the S5300.

Procedure

Step 1 Run:display alarm urgent [ slot slot-id | time interval ]

The alarms generated during device operation are displayed.

----End

4.2.10 Checking the Status of an Interface

Checking the Status of a Specified Interface1. Run:

display interface interface-type interface-numberThe status of a specified interface is displayed.

Information about the status of an interface contains the running status, basic configuration ofthe interface, and statistics of the transmission of packets.

Checking the Status of an Interface in the Current Interface View1. Run:

system-viewThe system view is displayed.

2. Run:interface interface-type interface-numberThe interface view is displayed.

3. Run:display this interfaceThe status of the interface in the current interface view is displayed.



4-5

5 Hardware Management

About This Chapter

This chapter describes the hardware management configurations on the S5300.

5.1 Hardware Management OverviewThis section explains the definition of hardware management.

5.2 Hardware Management Features Supported by the S5300This section describes the hardware management features supported by the S5300.

5.3 Backing Up the Electronic LabelThis section describes how to back up the electronic label of the S5300.

5.4 Configuring Electrical Port SleepThis section describes how to configure electrical port sleep to save energy.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 5 Hardware Management


5-1

5.1 Hardware Management OverviewThis section explains the definition of hardware management.

Hardware management refers to operating the installed hardware of the S5300 by usingcommands.

5.2 Hardware Management Features Supported by the S5300This section describes the hardware management features supported by the S5300.

The S5300 supports the following hardware management features:

l Electronic label backupl Electrical port sleep

5.3 Backing Up the Electronic LabelThis section describes how to back up the electronic label of the S5300.

5.3.1 Establishing the Configuration TaskBefore backing up the electronic label, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This helps you complete theconfiguration task quickly and accurately.

5.3.2 Backing Up the Electronic LabelYou can back up the electronic label of the S5300 to an FTP server or the CF card of theS5300.

5.3.1 Establishing the Configuration TaskBefore backing up the electronic label, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This helps you complete theconfiguration task quickly and accurately.

Applicable EnvironmentElectronic labels of network devices play an important role in troubleshooting. When faultsoccur on a network, you can obtain hardware information quickly from electronic labels.Therefore, you need to back up electronic labels.

Pre-configuration TasksBefore backing up the electronic label of the S5300, complete the following task:l Connecting the S5300 to an FTP server and ensuring that there is a reachable route between

them

Data PreparationTo back up the electronic label of the S5300, you need the following data.

5 Hardware ManagementQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

No. Data

1 Name of the electronic label backup file

2 Stack ID of the S5300 whose electronic label needs to be backed up

3 FTP server address, FTP user name, and password (only applicable to saving theelectronic label to an FTP server)

5.3.2 Backing Up the Electronic LabelYou can back up the electronic label of the S5300 to an FTP server or the CF card of theS5300.

Procedurel Back up the electronic label to the CF card.

1. Run the following command in the user view:backup elabel [ slot slot-id ]

The electronic label is backed up to the CF card.l Back up the electronic label to an FTP server.

1. Run the following command in the user view:backup elabel [ ftp ip-address filename username password ] [ slot slot-id [ subcard-id ] ]

The electronic label is backed up to an FTP server.

----End

5.4 Configuring Electrical Port SleepThis section describes how to configure electrical port sleep to save energy.

5.4.1 Establishing the Configuration TaskBefore configuring electrical port sleep, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This helps you complete theconfiguration task quickly and accurately.

5.4.2 Enabling Electrical Port SleepTo save energy on a device, you can enable electrical port sleep on the device.

5.4.3 Checking the ConfigurationAfter enabling electrical port sleep, you can run the following command to check theconfiguration.

5.4.1 Establishing the Configuration TaskBefore configuring electrical port sleep, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This helps you complete theconfiguration task quickly and accurately.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 5 Hardware Management


5-3


When a device is working normally, you can enable electrical port sleep to save energy.


None.

Data Preparation

To configure electrical port sleep, you need the following data.

No. Data

1 Number of the electrical port where the sleep function is to be enabled

5.4.2 Enabling Electrical Port SleepTo save energy on a device, you can enable electrical port sleep on the device.

Procedure



Step 2 Run:interface [ interface-type interface-number ]


Step 3 Run:port-auto-sleep enable

Electrical port sleep is enabled.

By default, the sleep function is disabled on an Ethernet port.

----End

5.4.3 Checking the ConfigurationAfter enabling electrical port sleep, you can run the following command to check theconfiguration.

Procedurel Run the display this command in the interface view to check whether port sleep is enabled.

----End

5 Hardware ManagementQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

6 Monitoring the Device Through theInformation Center

About This Chapter

This chapter describes the basics of the information center, introduces the procedure formanaging the information center and monitoring the device, and provides configurationexamples.

6.1 Information Center OverviewThe information center controls the output of logs, alarms, and debugging messages.

6.2 Configuring the Information CenterThis section describes how to manage and configure the information center.

6.3 Sending Information of the Information CenterThis section describes how to send information to the specified direction.

6.4 Maintaining the Information CenterThis section describes how to clear the statistics.

6.5 Configuration ExamplesThis section provides examples for configuring the information center.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 6 Monitoring the Device Through the Information Center


6-1

6.1 Information Center OverviewThe information center controls the output of logs, alarms, and debugging messages.

6.1.1 Introduction to the Information CenterThe information center works as the information hub of a switch. It classifies and filters theoutput of a system. The information center uses a debugging program to help networkadministrator and developers monitor network operation and analyze network faults.

6.1.2 Information Center Supported by the S5300In the S5300, the information center outputs logs, alarms, and debugging messages with eightseverity levels to different directions through 10 information channels.

6.1.1 Introduction to the Information CenterThe information center works as the information hub of a switch. It classifies and filters theoutput of a system. The information center uses a debugging program to help networkadministrator and developers monitor network operation and analyze network faults.

6.1.2 Information Center Supported by the S5300In the S5300, the information center outputs logs, alarms, and debugging messages with eightseverity levels to different directions through 10 information channels.

Information Classification

The information receives and processes the following types of information:

l Logs

l Debugging information

l Alarm information

Severity Levels of Information

Information is classified into eight severity levels as shown in Table 6-1. The severer theinformation level is, the lower the severity level value is.

Table 6-1 Description of the severity levels of information

Threshold Severity Level Description

0 Emergency A fatal fault, such as a programme exception orincorrect use of the memory, occurs on the device. Thesystem must restart.

1 Alert An important fault, such as the device memoryreaching the highest limit, occurs to device. The faultthen needs to be removed immediately.

6 Monitoring the Device Through the Information CenterQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

Threshold Severity Level Description

2 Critical A crucial fault occurs, such as the memory ortemperature reaches the lowest limit, the BFD deviceis unreachable, or an internal fault that is generated bythe device itself. The fault then needs to be analyzedand removed.

3 Error A fault caused by an improper operation or a wrongprocess occurs, such as entering the wrong userpassword or receiving wrong protocol packets fromother devices.The faults do not affect service but should be paidattention to.

4 Warning An abnormal situation of the running device occurs,such as the user disables the routing process, BFDdetects packet loss, or the wrong protocol packet isreceived.The fault should be paid attention to because it mayaffect services.

5 Notice Indicates the key operations used to ensure that thedevice runs normally, such as the shutdowncommand, neighbor discovery, or the state machine.

6 Informational Indicates the common operations to ensure that thedevice runs normally, such as the display command.

7 Debugging Indicates the common information of the device thatneed not be paid attention to.

When information filtering based on severity levels is enabled, only the information whoseseverity level threshold is less than or equal to the configured value is output.

For example, if the severity level value is configured to 6, only the information with the severitylevel value from 0 to 6 is output.

Working Process of an Information Center

The working process of the information center is as follows:

l The information center receives logs, traps, and debugging information from all modules.

l The information center outputs information with different severity levels to differentinformation channels according to the configurations of users.

l The information is transmitted to different directions based on the association relationshipbetween the information channel and the output direction.

Generally, the information center distributes the three types of information that can be classifiedinto eight levels to ten information channels. The information is then output to differentdirections.



6-3

As shown in Figure 6-1, logs, alarms, and debugging information have default output channels.You can, however, customize them to be output from other channels. For example, you canconfigure logs to be output to the log cache through Channel 6 rather than Channel 3.

Figure 6-1 Functions of the information channel

Infomation type Infomation channel

Console

Remoteterminal

Loghost

Trap buffer

Log buffer

SNMP agent

Logs

Traps

Debugs

Output direction

Direction of logsDirection of alarmsDirection of debugging

information

Console

SNMP agent

Monitor

Loghost

Logbuffer

Trapbuffer

0

1

2

3

4

5

channel6

channel7

channel8

channel9

6

78

9

Information Channels and Output Directions

The system supports ten channels. The first six channels (Channel 0 to Channel 5) have theirdefault channel names, and are associated with six output directions.

For details of association relationship between default channels and output directions, see Table6-2.

Table 6-2 Association relationship between the information channels and output directions

ChannelNumber

DefaultChannel Name

OutputDirection

Description

0 Console Console Outputs the information to the localConsole that can receive logs, alarms, anddebugging information.

1 Monitor Monitor Outputs the information to the VTYterminals that can receive logs, alarms, anddebugging information and then performremote maintenance.




Issue 03 (2011-01-30)

ChannelNumber

DefaultChannel Name

OutputDirection

Description

2 Loghost Log host Outputs the information to the log host thatcan receive logs, alarms, and debugginginformation. The information is saved to alog host in the file format for easy reference.

3 Trapbuffer Trap buffer Outputs information to the trap buffer thatcan receive traps. An area is specified insidea device as the trap buffer to record traps.

4 Logbuffer Log buffer Outputs the information to the log bufferarea that can receive logs. The switchassigns a specified area in itself to be the logbuffer area that can record the information.

5 Snmpagent SNMP agent Outputs the information to the SNMP agentthat can receive alarms.

6 Unspecified Unspecified Reserved.




When multiple log hosts are configured, you can configure logs to be output to different loghosts through one channel or several channels. For example, configure parts of logs to be outputto a log host either through Channel 2 (loghost) or through Channel 6. You can also change thename of Channel 6 for managing channel conveniently.

Format of LogsSyslog is a sub-function of the information center. It outputs information to a log host throughport 514.

Figure 6-2 shows the format of logs.

Figure 6-2 Format of the output logs

<Int_16>TIMESTAMP HOSTNAME %%ddAAA/B/CCC(l):slot=XXX; YYYY

Table 6-3 describes each field in the log format.



6-5

Table 6-3 Description of each field in the format of logs

Field Indication Description

<Int_16> Leading character Before logs are output to log hosts, leadingcharacters are added.Logs saved in the local device do not containleading characters.

TIMESTAMP Time to send out theinformation

Timestamp has five formats.l boot: indicates the relative time.l date: indicates the time of the system. Logs,

alarms and debugging information adopt thisformat by default.

l short-date: The only difference between dateformat and short-date is that short-date does notinclude the year.

l format-date: It is another time format of thesystem time.

l none: indicates that the information does notcontain timestamp.

There is a space between the timestamp and thehost name.

HOSTNAME Host name By default, the name is Quidway.

%% Log information Indicates that this piece of log is output by thedevice produced by Huawei.

dd Version number Identifies the version of the log format.

AAA Module name Indicates the name of the module that outputsinformation to an information center.

B Log level Indicates the severity levels of logs.

CCC Brief description Describes the information type.

(l) Information type L: indicates the user log identifier.

slot=XXX Location information Slot indicates the number of the slot that sends thelocation information.

YYYY Descriptor Indicates the detailed information output from eachmodule to the information center.Each module fills in this field before outputtinglogs to describe the detailed contents of logs.

Format of AlarmsFigure 6-3 shows the format of the output alarms.




Issue 03 (2011-01-30)

Figure 6-3 Format of the output alarms

TimeStamp HostName ModuleName/Severity/BriefDescription

Table 6-4 describes each field of the alarm format.

Table 6-4 Description of each field of the format of alarms

Field Indication Description

TimeStamp Time to send out theinformation

Five timestamp formats are available:l boot: indicates relative time. By default,

debugging information adopts this timestampformat.

l date: indicates the timestamp in the format ofsystem time. By default, logs and traps adoptthis timestamp format.

l short-date: indicates system time. The short-date format does not contain year information.

l format-date: indicates another format of systemtime.

l none: indicates that no timestamp is containedin traps.

The timestamp and the host name are separated bya blank space.

HostName Host name By default, the name is Quidway.There is a space between the sysname and modulename.

ModuleName Module name Indicates the name of the module that generates analarm.

Severity Severity level Indicates the severity levels of alarms:l Criticall Majorl Minorl Warningl Indeterminatel Cleared

Brief Brief information Provides brief information of the alarms.

Description Description Provides a detailed description of the alarms.



6-7

6.2 Configuring the Information CenterThis section describes how to manage and configure the information center.


6.2.2 Enabling the Information Center

6.2.3 (Optional) Naming the Information Channel

6.2.4 Defining the Information Channel

6.2.5 (Optional) Configuring the Timestamp for the Output Information




To collect debugging information, logs, and traps during the operation of the S5300, and to sendthem to the terminal for display, or to the buffer or the host for storage, you need to configurethe information center.


None.

Data Preparation

To manage the information center, you need the following data.

No. Data

1 (Optional) Numbers and names of the information channels

2 (Optional) Format of the timestamp

3 (Optional) Severity level

4 (Optional) Language used in the logs and the address of the log host

5 (Optional) Size of the log buffer and the trap buffer

6.2.2 Enabling the Information Center

Context

Do as follows on the S5300.




Issue 03 (2011-01-30)

Procedure



Step 2 Run:info-center enable

The information center view is displayed.

NOTE

The system sends the system information to the log host and the console only after the information centeris enabled.

----End

6.2.3 (Optional) Naming the Information Channel

Procedure



Step 2 Run:info-center channel channel-number name channel-name

Channels are specified to send debugging information, logs, and traps.

----End

6.2.4 Defining the Information Channel

Procedure



Step 2 Run:info-center source { module-name| default } channel { channel-number | channel-name } [ { debug | log | trap } { state { off | on } | level severity } * ] *

A module (or modules) is specified to send debugging information, logs, or traps to theinformation channels.

NOTE

Run the undo info-center source { module-name | default } channel { channel-number | channel-name } command to disable the unnecessary modules and select one or more modules to send informationto the information channels.

----End



6-9

6.2.5 (Optional) Configuring the Timestamp for the OutputInformation

Procedure



Step 2 Run:info-center timestamp debugging { boot | none | { short-date | format-date | date } [ precision-time { tenth-second | second } ] }

The format of the timestamp is set for the debugging information.

Step 3 Run:info-center timestamp { trap | log } { boot | none | { short-date | format-date | date } [ precision-time { tenth-second | millisecond } ] }

The format of the timestamp is set for the output logs or traps information.

----End

6.2.6 Checking the ConfigurationRun the following commands to check the previous configuration.

Action Command

Check the configuration of thechannel.

display channel [ channel-number | channel-name ]

Check the information recorded bythe information center.

display info-center [ statistics ]

Check the information in the logbuffer of the memory.

display logbuffer [ level severity | module module-name | size value | slot slot-id ]*

Check the summary of theinformation in the log buffer.

display logbuffer summary [ level severity | slot slot-id ]

Check the information in the trapbuffer of the memory.

display trapbuffer [ size value ]

6.3 Sending Information of the Information CenterThis section describes how to send information to the specified direction.

6.3.1 Sending Information to the Console

6.3.2 Sending Information to the Telnet Terminal

6.3.3 Sending Information to the SNMP Agent




Issue 03 (2011-01-30)

6.3.4 Sending Information to the Log Buffer

6.3.5 Sending Information to the Trap Buffer

6.3.6 Sending Information to the Log Host


6.3.1 Sending Information to the Console

Procedure



Step 2 Run:info-center console channel { channel-number | channel-name }

Information is sent to the console.

Step 3 Run:quit

Return to the user view.

Step 4 Run:terminal monitor

The terminal is enabled to display information.

By default, the terminal is enabled to display information.

Step 5 Run:terminal debuggingorterminal loggingorterminal trapping

The terminal is enabled to display debugging information, logs, and traps.

NOTE

Step 4 and Step 5 are not listed in sequence.

----End

6.3.2 Sending Information to the Telnet Terminal

Procedure





6-11

Step 2 Run:info-center monitor channel { channel-number | channel-name }

Information is sent to the Telnet terminal.

Step 3 Run:quit

Return to the user view.

Step 4 Run:terminal monitor

The terminal is enabled to display information.

Step 5 Run:terminal debuggingorterminal loggingorterminal trapping

The terminal is enabled to display debugging information, logs, and traps.

NOTE

Step 4 and Step 5 are not listed in sequence.

----End

6.3.3 Sending Information to the SNMP Agent

Procedure



Step 2 Run:info-center snmp channel { channel-number | channel-name }

Information is sent to the SNMP agent.

Step 3 Run:snmp-agent

The SNMP agent is enabled.

For details on configuring the SNMP agent, refer to chapter "SNMP Configuration" in theConfiguration Guide - Network Management.

----End

6.3.4 Sending Information to the Log Buffer




Issue 03 (2011-01-30)

Procedure



Step 2 Run:info-center logbuffer [ channel { channel-number | channel-name } | size buffersize ] *

Information is sent to the log buffer.

----End

6.3.5 Sending Information to the Trap Buffer

ContextDo as follows on the S5300.

Procedure



Step 2 Run:info-center trapbuffer [ channel { channel-number | channel-name } | size buffersize ] *

Information is sent to the trap buffer.

----End

6.3.6 Sending Information to the Log Host

Procedure



Step 2 Run:info-center loghost ip-address [ channel { channel-number | channel-name } | facility local-number | { language language-name | binary [ port ] } | { vpn-instance vpn-instance-name | public-net } ] *

Information is sent to the IPv4 log host.

Step 3 Run:info-center loghost ipv6 ipv6-address [ channel { channel-number | channel-name } | facility local-number | { language language-name | binary [ port ] } ] *



6-13

Information is sent to the IPv6 log host.

Step 4 Run:info-center loghost source interface-type interface-number

The source interface for sending logs is specified.

----End


Action Command

Check statistics in theinformation center.

display info-center [ statistics ]

Run the preceding command. If the information center can send the statistics to the destinationterminal, it means that the configuration succeeds.

6.4 Maintaining the Information CenterThis section describes how to clear the statistics.

CAUTIONStatistics cannot be restored after being cleared. So, confirm the action before you run thecommand.

Action Command

Clear the statistics in theinformation center.

reset info-center statistics

Clear the information in the logbuffer.

reset logbuffer

Clear the information in the trapbuffer.

reset trapbuffer

6.5 Configuration ExamplesThis section provides examples for configuring the information center.

6.5.1 Example for Configuring the Information Center




Issue 03 (2011-01-30)

6.5.1 Example for Configuring the Information Center

Networking Requirements

Figure 6-4 Networking of sending logs to the log host

Network

Log HostSwitch

1.0.0.1/8VLANIF102.0.0.1/8


1. Enable the information center.2. Configure the information channel to ensure that the S5300 can correctly send logs to the

log host. Disable the sending of the traps and debugging information to the log host.3. Configure the log host.


l The IP address of the log host is specified as 1.0.0.1/8.

Configuration ProcedureNOTE

In the example, only the commands related to monitoring are listed. For details on configuring the log host,see the help files on the log host.

1. Enable the information center.# Enable the information center. By default, the information center on the S5300 is enabled.<Quidway> system-view[Quidway] info-center enableInfo:Information center is enabled

2. Configure the information channel.# Send logs of severity levels 0 to 7 from all modules on the S5300 through the channel tothe log host. Disable the sending of the debugging information and traps through the channelto the log host.[Quidway] info-center source default channel loghost log level debugging state on trap state off debug state off

# Verify the configuration.[Quidway] display channel loghostchannel number:2, channel name:loghostMODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVELffff0000 default Y debugging N debugging N debugging



6-15

3. Configure the log host.# Set the IP address of the log host to 1.0.0.1.[Quidway] info-center loghost 1.0.0.1

# Set VLANIF 10 as the interface for sending information to the log host on the S5300.[Quidway] vlan 10[Quidway-vlan10] quit[Quidway] interface GigabitEthernet0/0/1[Quidway-GigabitEthernet0/0/1] port link-type hybrid[Quidway-GigabitEthernet0/0/1] port hybrid untagged vlan 10[Quidway-GigabitEthernet0/0/1] quit[Quidway] interface vlanif 10[Quidway-vlanif10] ip address 2.0.0.1 255.0.0.0[Quidway-vlanif10] quit[Quidway] info-center loghost source vlanif 10

# Verify the configuration.[Quidway] display info-centerInformation Center:enabledLog host: the interface name of the source address:vlanif 10 1.0.0.1, channel number 2, channel name loghost, language English , host facility local7Console: channel number : 0, channel name : consoleMonitor: channel number : 1, channel name : monitorSNMP Agent: channel number : 5, channel name : snmpagentLog buffer: enabled,max buffer size 1024, current buffer size 512,current messages 440, channel number : 4, channel name : logbufferdropped messages 0, overwritten messages 0Trap buffer: enabled,max buffer size 1024, current buffer size 256,current messages 1, channel number:3, channel name:trapbufferdropped messages 0, overwritten messages 0Information timestamp setting: log - date, trap - date, debug - boot

Sent messages = 499, Received messages = 499

IO Reg messages = 0 IO Sent messages = 0

4. Enable the terminal display of the console.# Enable the terminal display of the console. Enable the corresponding terminal display tocheck the information type as required.[Quidway] info-center console channel 0[Quidway] quit<Quidway> terminal monitorInfo:Current terminal monitor is on<Quidway> terminal loggingInfo:Current terminal logging is on

Configuration Files# info-center source default channel loghost log level debugging state on trap state off debug state off info-center loghost source vlanif 10 info-center loghost 1.0.0.1 info-center console channel 0## vlan batch 10#




Issue 03 (2011-01-30)

interface vlanif10 ip address 2.0.0.1 255.0.0.0#interface GigabitEthernet0/0/1 port link-type hybridport hybrid untagged vlan 10#return



6-17

7 Mirroring

About This Chapter

The mirroring function is used to monitor packets that meet certain requirements.

7.1 IntroductionThis section describes the basics of mirroring.

7.2 Configuring Local Port MirroringThis section describes how to configure local interface mirroring.

7.3 Configuring Remote Port MirroringThis section describes how to configure remote port mirroring.

7.4 Canceling Port MirroringThis section describes how to cancel interface mirroring.

7.5 Configuring Local VLAN MirroringThis section describes how to configure local VLAN mirroring.

7.6 Configuring Remote VLAN MirroringThis section describes how to configure remote VLAN mirroring.

7.7 Canceling VLAN MirroringThis section describes how to cancel local VLAN mirroring and remote VLAN mirroring.

7.8 Configuring MAC Address-based Local MirroringThis section describes how to configure local MAC address mirroring.

7.9 Configuring RSPAN Based on MAC AddressesThis section describes how to configure RSPAN based on MAC addresses.

7.10 Canceling Mirroring Based on MAC AddressesThis section describes how to cancel mirroring based on MAC addresses.

7.11 Configuring Local Flow MirroringThis section describes how to configure local flow mirroring.

7.12 Configuring Remote Flow MirroringThis section describes how to configure remote flow mirroring.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 7 Mirroring


7-1

7.13 Canceling Flow MirroringThis section describes how to cancel flow mirroring.

7.14 Changing or Deleting an Observing PortThis section describes how to change or delete an observing port.

7.15 Configuring CPU MirroringThis section describes how to configure CPU mirroring.

7.16 Cancelling CPU MirroringThis section describes how to cancel CPU mirroring.

7.17 Configuration ExamplesThis section provides several configuration examples for mirroring.

7 MirroringQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

7.1 IntroductionThis section describes the basics of mirroring.

7.1.1 Mirroring Functions

7.1.2 Logical Relationships Between Configuration Tasks

7.1.1 Mirroring Functions

Mirroring is to copy packets to an observing port to monitor packets without affecting packetforwarding. You can use the mirroring function for network check and troubleshooting.

Mirroring functions are classified into interface mirroring, flowing mirroring, VLAN mirroring,MAC address mirroring, and CPU mirroring.

The S5300SI does not support remote mirroring based on flows, VLANs, or MAC addresses.

Conceptsl Observing port

An observing port on the S5300 is connected to a monitoring host. It is used to export thetraffic copied from a mirrored port or a flow mirroring port.

l Mirrored portA mirrored port is the interface to be observed. Incoming traffic or outgoing traffic passingthrough a mirrored port is copied to an observing port.

l Flow mirroring portA flow mirroring port is a port to which traffic policies are applied. On such a port, theincoming traffic that matches the traffic classifier in the traffic policy is copied to anobserving port.

l Mirrored flowA mirrored flow is a packet flow that runs to a flow mirroring port and is observed. Whena flow becomes a mirrored flow, it is copied to an observing port.

l Mirrored VLANA mirrored VLAN is a VLAN to be observed. Incoming traffic or outgoing traffic passingthrough a mirrored VLAN is copied to an observing port.

l Mirrored MAC addressA mirrored MAC address is the source or destination MAC address of the packets to bemirrored. The S5300 copies the traffic matching this MAC address to an observing port.

l RSPAN VLANA Remote Switched Port Analyzer (RSPAN) VLAN is a VLAN used for remote mirroring.When the mirrored port and the observing port are located on different switches, packetsfrom the mirrored port must be broadcast to the observing port through the RSPAN VLAN.

l Local mirroringThe observing port and mirrored port are on the same switch.

l Remote mirroring



7-3

The observing port and mirrored port are on different switches.NOTE

The S5300 does not support the function of mirroring a flow to multiple observing ports.

Port MirroringIn the process of port mirroring, the S5300 copies the packets passing through a mirrored portand then sends the copy to a specified observing port. Figure 7-1 shows the diagram of interfacemirroring.

Figure 7-1 Schematic diagram of interface mirroring

Observe port

Sniffer host

PortData flow

Mirrorport

Copy of data flow

Mirrorport

Switch

Flow MirroringIn the process of flow mirroring, the S5300 copies the mirroring flow passing one or moreinterfaces and sends the copy to an observing port. Figure 7-2 shows the diagram of flowmirroring.

Figure 7-2 Schematic diagram of flow mirroring

Observe port

Sniffer host

Port

Data flow

Mirrorport

Copy of data flow

Mirrorport

Switch

Match traffic classification




Issue 03 (2011-01-30)

Flow mirroring is a type of action in traffic behaviors. When a traffic policy configured withflow mirroring is applied to an interface, the S5300 copies the inbound data flow on this interfacethat matches the traffic classifier and sends the copy to the observing port.

VLAN MirroringIn the process of VLAN mirroring, the S5300 mirrors the packets passing through all activeinterfaces in a specified VLAN to a specified observing port. Compared with interface mirroring,VLAN mirroring mirrors packets in a wider range. You can monitor packets in one or moreVLANs.

MAC Address MirroringMAC address mirroring allows you to monitor the packets received by or sent from a specifieddevice on a network. The S5300 mirrors the packets matching a specified source or destinationMAC address in a VLAN to a specified observing port.

CPU MirroringCPU mirroring is used to mirror all the packets received by the CPU. CPU mirroring isimplemented as follows:

l If an ACL rule is specified, the packets that match the ACL rule are mirrored to a specifiedobserving port.

l If no ACL rule is specified, all the packets received by the CPU are mirrored to a specifiedobserving port.

CPU mirroring facilitates debugging and fault location.

RSPANA switch can copy incoming or outgoing packets on a mirrored port to an observing port. Whenthe observing port and the mirrored port are on different switches, packets can be copied to theobserving port through the RSPAN function, which is also called remote mirroring.

Figure 7-3 Networking diagram of RSPAN

Sniffer host

Mirror port

Source Switch

Intermediate Switch

Destination Switch

Observeport

Observe port

PortData flowCopy of data flow



7-5

In Figure 7-3:

l The source switch is the Switch where the mirrored port is located.

l The destination switch is the Switch where the observing port is located.

l The intermediate switch is a device between the source switch and destination switch.

NOTE

The source switch and destination switch can also be directly connected to implement the RSPANfunction.

The RSPAN function broadcasts mirrored packets from the source switch to the destinationswitch in the RSPAN VLAN. Interfaces between the source switch, intermediate switch, anddestination switch must be added to the RSPAN VLAN.

Mirrored packets are forwarded to the intermediate switch through the observing port on thesource switch. Then the intermediate switch broadcasts mirrored packets to the observing porton the destination switch in the RSPAN VLAN.

The observing port on the destination switch receives mirrored packets.

Through the RSPAN function, packets on a specified interface or VLAN, with a specified sourceor destination MAC address, or matching a classifier can be copied to an observing port on aremote device.

7.1.2 Logical Relationships Between Configuration TasksBefore performing 7.14 Changing or Deleting an Observing Port, complete7.4 CancelingPort Mirroring, 7.13 Canceling Flow Mirroring, 7.7 Canceling VLAN Mirroring and 7.10Canceling Mirroring Based on MAC Addresses.

7.2 Configuring Local Port MirroringThis section describes how to configure local interface mirroring.


7.2.2 Configuring Local Port Mirroring




When all incoming or outgoing packets passing through a specified interface of the S5300 needto be monitored, you can configure local interface mirroring if the mirrored port is located onthe same S5300 as the observing port.


None.




Issue 03 (2011-01-30)

Data Preparation

To configure local interface mirroring, you need the following data.

No. Data

1 Type and number of the observing port

2 Type and number of the mirrored port

7.2.2 Configuring Local Port Mirroring

Context

A mirrored port can be a physical interface or an Eth-Trunk interface.

To configure an Eth-Trunk as a mirrored interface, you must run the interface eth-trunk trunk-id command to create the Eth-Trunk first.l If an Eth-Trunk is configured as a mirrored interface, its member interfaces cannot be

configured as mirrored interfaces.l If a member interface of an Eth-Trunk is configured as a mirrored interface, the Eth-Trunk

cannot be configured as a mirrored interface.

Procedure



Step 2 Run:observe-port index interface interface-type interface-number

An observing port is configured.


The view of the mirrored port is displayed.

Step 4 Run:port-mirroring to observe-port index { both | inbound | outbound }

Interface mirroring is configured on the mirrored port.

To monitor packets on multiple interface, repeat Step 3 and Step 4.

----End




7-7

Action Command

Check information aboutinterface mirroring.

display port-mirroring

Check information about theobserving port.

display observe-port

If the following results are obtained, it indicates that the configuration succeeds:

l The observing port is configured properly.l The mirrored port and the mirroring direction are configured properly.

7.3 Configuring Remote Port MirroringThis section describes how to configure remote port mirroring.


7.3.2 Configuring Remote Port Mirroring



Applicable EnvironmentWhen incoming or outgoing packets passing through one or more ports of the S5300 need to bemonitored, you can configure remote port mirroring if the monitored ports are not located onthe same S5300 as the observing port.

Pre-configuration TasksNone.

Data PreparationTo configure remote port mirroring, you need the following data.

No. Data


2 Number of the mirrored port

3 ID of the RSPAN VLAN




Issue 03 (2011-01-30)

7.3.2 Configuring Remote Port Mirroring

ContextA mirrored port can be a physical interface or an Eth-Trunk interface.

To configure an Eth-Trunk as a mirrored interface, you must run the interface eth-trunk trunk-id command to create the Eth-Trunk first.l If an Eth-Trunk is configured as a mirrored interface, its member interfaces cannot be

configured as mirrored interfaces.l If a member interface of an Eth-Trunk is configured as a mirrored interface, the Eth-Trunk

cannot be configured as a mirrored interface.

Procedurel Specify a mirrored port and an RSPAN VLAN on the source switch.

NOTE

The mirrored port cannot be added to the RSPAN VLAN.

1. Run:system-view


vlan vlan-id

An RSPAN VLAN is created and the RSPAN VLAN view is displayed.3. Run:

mac-address learning disable

The MAC address learning is disabled.

NOTEIf MAC address learning is disabled in the VLAN, other services cannot be configured in the VLAN.

4. Run:quit

Return to the system view.5. Run:

observe-port index interface interface-type interface-number [ vlan vlan-id ]

An observing port is configured, and the RSPAN VLAN is specified.6. Run:


The view of the mirrored port is displayed.7. Run:

port-mirroring to observe-port index { both | inbound | outbound }

Remote port mirroring is configured.

To observe incoming and outgoing packets on multiple interfaces, repeat Step 6 andStep 7.



7-9

l Configure the RSPAN VLAN and add the interfaces connected to the source switch anddestination switch to the RSPAN VLAN.

NOTE


Do as follows on the intermediate switch. The configurations on the interfaces connectedto the source switch and destination switch are similar. If no intermediate switch exists,skip this step.

1. Run:system-view


vlan vlan-id

The RSPAN VLAN is created and the RSPAN VLAN view is displayed.3. Run:

quit



The view of the interface connected to the source switch or destination switch isdisplayed.

5. Run:port link-type trunk

The interface is configured as a trunk interface.6. Run:

port trunk allow-pass vlan vlan-id

The interface is added to the RSPAN VLAN.7. Run:

quit

Return to the system view.l Configure the remote observing port on the destination switch.

1. Run:system-view


vlan vlan-id

The RSPAN VLAN is created and the RSPAN VLAN view is displayed.3. Run:

quit






Issue 03 (2011-01-30)

The view of the interface connected to the intermediate switch is displayed.

NOTEIf no intermediate switch exists, you enter the view of the interface connected to the sourceswitch.

5. Run:port link-type trunk

The interface is configured as a trunk interface.6. Run:

port trunk allow-pass vlan vlan-id

The interface is added to the RSPAN VLAN.7. Run:


The observing port view is displayed.8. Run:

port hybrid untagged vlan vlan-id

The observing port is configured as a hybrid interface and it allows packets of theRSPAN VLAN to pass.

9. Run:quit

Return to the system view.

----End


Action Command



Check information about portmirroring.



l The RSPAN VLAN is configured properly.l The number of the observing port is configured properly.l The type of the observing port is configured properly.l The number of the mirrored port and the mirroring direction are configured properly.

7.4 Canceling Port MirroringThis section describes how to cancel interface mirroring.



7-11


7.4.2 Canceling Port Mirroring



Applicable EnvironmentWhen interface mirroring is enabled on an interface of the S5300, and the incoming or outgoingpackets passing through this interface do not need to be monitored, you can cancel interfacemirroring on that interface. You must cancel interface mirroring on the bound observing portbefore deleting this observing port.


Data PreparationTo cancel interface mirroring, you need the following data.

No. Data

1 Type and number of an observing port

2 Type and number of the mirrored port to be deleted

7.4.2 Canceling Port Mirroring

Procedure





Step 3 Run:undo port-mirroring { both | inbound | outbound }

Interface mirroring is canceled.

----End





Issue 03 (2011-01-30)

Action Command





Run the display port-mirroring command. If interface mirroring is cancelled properly, itindicates that the configuration succeeds.

7.5 Configuring Local VLAN MirroringThis section describes how to configure local VLAN mirroring.


7.5.2 Configuring Local VLAN Mirroring



Applicable EnvironmentWhen incoming packets passing through all active interfaces of the S5300 in a specified VLANor some VLANs need to be monitored, you can configure local VLAN mirroring if all interfacesreceiving these monitored incoming packets are located on the same S5300 as the observingport.

Pre-configuration TasksBefore configuring local VLAN mirroring, complete the following tasks:l Creating a VLAN as the monitored VLANl Adding physical interfaces to the monitored VLAN

Data PreparationTo configure local VLAN mirroring, you need the following data.

No. Data


2 ID of a mirrored VLAN

7.5.2 Configuring Local VLAN Mirroring



7-13

Procedure





Step 3 Run:vlan vlan-id

The view of the mirrored VLAN is displayed.

Step 4 Run:mirroring to observe-port index inbound

VLAN mirroring is configured.

To observe incoming packets from multiple VLANs, repeat Step 3 and Step 4.

----End


Action Command






l The type of the observing port is configured properly.

l The number of the observing port is configured properly.

7.6 Configuring Remote VLAN MirroringThis section describes how to configure remote VLAN mirroring.


7.6.2 Configuring Remote VLAN Mirroring





Issue 03 (2011-01-30)



When incoming packets passing through any active interfaces of the S5300 in a specified VLANor some VLANs need to be monitored, you can configure remote VLAN mirroring if the interfaceadded to the monitored VLAN is not located on the same S5300 as the observing port.

NOTE

S5300SI does not support remote VLAN mirroring.


Before configuring remote VLAN mirroring, complete the following tasks:l Creating a VLAN as the monitored VLANl Adding physical interfaces to the monitored VLAN

Data Preparation

To configure remote VLAN mirroring, you need the following data.

No. Data


2 ID of the mirrored VLAN


7.6.2 Configuring Remote VLAN Mirroring

Procedurel Configure remote VLAN mirroring on the source switch.

NOTE


1. Run:system-view


vlan vlan-id






7-15


4. Run:quit


5. Run:observe-port index interface interface-type interface-number [ vlan vlan-id ]

An observing port is configured and the RSPAN VLAN is specified.

6. Run:vlan vlan-id

The RSPAN VLAN view is displayed.

7. Run:mirroring to observe-port index inbound

Remote VLAN mirroring is configured.

To observe incoming and outgoing packets of multiple VLANs, repeat Step 6 andStep 7.

l Configure the RSPAN VLAN on the intermediate switch and add interfaces to the RSPANVLAN.

The configuration is the same as that for remote port mirroring. For details, see 7.3.2Configuring Remote Port Mirroring.

l Configure the remote observing port on the destination switch.


----End


Action Command











Issue 03 (2011-01-30)

7.7 Canceling VLAN MirroringThis section describes how to cancel local VLAN mirroring and remote VLAN mirroring.


7.7.2 Canceling VLAN Mirroring



Applicable EnvironmentWhen VLAN mirroring is enabled in a specified VLAN and all incoming packets in this VLANdo not need to be monitored on the S5300, or before deleting or changing the bound observingport, you need to cancel VLAN mirroring.


Data PreparationTo cancel VLAN mirroring, you need the following data.

No. Data

1 ID of the mirrored VLAN to be deleted

7.7.2 Canceling VLAN Mirroring

Procedure




The view of the monitored VLAN is displayed.

Step 3 Run:undo mirroring inbound

VLAN mirroring is canceled.

----End



7-17


Action Command





If VLAN mirroring is cancelled, it indicates that the operation succeeds.

7.8 Configuring MAC Address-based Local MirroringThis section describes how to configure local MAC address mirroring.


7.8.2 Configuring Local SPAN Based on MAC Addresses



Applicable EnvironmentWhen incoming packets with the specified source or destination MAC address in a VLAN needto be monitored on the S5300, you can configure local MAC address mirroring if the monitoringinterface receiving these incoming packets is located on the same S5300 as the observing port.


Data PreparationTo configure local MAC address mirroring, you need the following data.

No. Data


2 MAC address of the packets to be mirrored

3 ID of the VLAN that the observed MAC address belongs to

7.8.2 Configuring Local SPAN Based on MAC Addresses




Issue 03 (2011-01-30)

Procedure






The VLAN view is displayed.

Step 4 Run:mac-mirroring mac-address to observe-port index inbound

Local SPAN based on MAC addresses is configured.

You can repeatedly perform Step 3 and Step 4 to monitor the incoming packets with multipleMAC addresses in multiple VLANs.

----End


Action Command






l The type of the observing port is configured properly.l The number of the observing port is configured properly.

7.9 Configuring RSPAN Based on MAC AddressesThis section describes how to configure RSPAN based on MAC addresses.


7.9.2 Configuring Remote MAC Address MirroringThis section describes how to configure remote MAC address mirroring.




7-19



When incoming packets with the specified source or destination MAC address in a VLAN needto be monitored on the S5300, you can configure RSPAN based on MAC addresses if themonitoring interface receiving these incoming packets is not located on the same S5300 as theobserving port.


None.

Data Preparation

To configure RSPAN based on MAC addresses, you need the following data.

No. Data


2 MAC address of the packet to be mirrored

3 ID of the VLAN that the packet with the MAC address to be mirrored belongs to

4 ID of an RSPAN VLAN

7.9.2 Configuring Remote MAC Address MirroringThis section describes how to configure remote MAC address mirroring.

Procedurel Configure remote MAC address mirroring on the source switch.

NOTE


The S5300SI series do not support remote MAC address mirroring.

1. Run:system-view


vlan vlan-id







Issue 03 (2011-01-30)


4. Run:quit


observe-port index interface interface-type interface-number [ vlan vlan-id ]

An observing port is configured, and the RSPAN VLAN is specified.6. Run:

vlan vlan-id

The view of the VLAN that the observed MAC address belongs to is displayed.7. Run:

mac-mirroring mac-address to observe-port index inbound

Remote MAC address mirroring is configured and the RSPAN VLAN is specified.

To observe incoming packets from or destined for multiple MAC addresses, repeatStep 6 and Step 7.



l Configure the remote observing interface on the destination switch.


----End


Action Command



Check information about MACaddress mirroring.



l The type of the observing port is configured properly.l The RSPAN VLAN is configured properly.l The number of the observing port is configured properly.



7-21

7.10 Canceling Mirroring Based on MAC AddressesThis section describes how to cancel mirroring based on MAC addresses.


7.10.2 Canceling Mirroring Based on MAC Addresses



Applicable EnvironmentWhen mirroring based on MAC addresses is enabled and incoming packets with specified MACaddresses in this VLAN do not need to be monitored on the S5300, or before deleting or changingthe bound observing port, you need to cancel mirroring based on MAC addresses.


Data PreparationTo cancel mirroring based on MAC addresses, you need the following data.

No. Data

1 MAC address of the mirrored packet to be deleted

7.10.2 Canceling Mirroring Based on MAC Addresses

Procedure




The view of the VLAN that monitored MAC address belongs to is displayed.

Step 3 Run:undo mac-mirroring mac-address inbound

Mirroring based on MAC addresses is canceled.

----End




Issue 03 (2011-01-30)


Action Command



Check the configuration of themirrored port.


If MAC address mirroring on the VLANIF interface is cancelled, it indicates that the operationsucceeds.

7.11 Configuring Local Flow MirroringThis section describes how to configure local flow mirroring.


7.11.2 Configuring Traffic Classification Rules

7.11.3 Configuring Flow Mirroring

7.11.4 Creating and Applying a Traffic Policy



Applicable EnvironmentWhen incoming flows passing through the S5300 with the same attribute need to be monitored,you can configure local flow mirroring if the monitored interface receiving these incoming flowsis located on the same S5300 as the observing port.


Data PreparationTo configure local flow mirroring, you need the following data.

No. Data


2 Type and number of the flow mirroring interface

3 Names of the traffic classifier, traffic behavior, and traffic policy



7-23

7.11.2 Configuring Traffic Classification RulesNOTE

There is no specified order among the matching rules in a traffic classifier. You can combine these rules.

For details on configuring traffic classification rules, see Configuring Complex TrafficClassification in the Quidway S5300 Series Ethernet Switches Configuration Guide - QoS.

7.11.3 Configuring Flow Mirroring

Procedure





Step 3 Run:traffic behavior behavior-name

A traffic behavior is created and the traffic behavior view is displayed.

Step 4 Run:mirroring to observe-port index

Flow mirroring is configured.

----End

Follow-up ProcedureAfter configuring flow mirroring in a traffic behavior, you need to bind the behavior to a trafficclassifier in a traffic policy and then apply the policy to the interface. For detailed configurationprocedures, see 7.11.4 Creating and Applying a Traffic Policy.


ContextDo as follows on the S5300 that needs to be configured with flow mirroring.

Procedure



Step 2 Run:




Issue 03 (2011-01-30)

traffic policy policy-name

A traffic policy is created and the policy view is displayed.

Step 3 Run:classifier classifier-name behavior behavior-name

A traffic behavior is configured for a specified class in the traffic policy.

class-name in this step must be the same as the name of the traffic class created in 7.11.2Configuring Traffic Classification Rules.

In this step, behavior-name must be the same as that specified in Step 3 when you configure thetraffic behavior.

Step 4 Run:quit




Step 6 Run:traffic-policy policy-name inbound

The traffic policy that contains flow mirroring is applied to the interface.

You can repeatedly perform Step 5 and Step 6 to monitor the incoming flows, with the sameattributes, passing through multiple interfaces.

----End


Action Command





Check the flow mirroringconfiguration in the traffic policyon an interface.

display traffic policy interface [ interface-typeinterface-number ] [ inbound ]


l The observing port is configured properly.l A proper traffic policy is applied to the interface where incoming flows need to be

monitored.



7-25

l The traffic policy contains a proper traffic classifier and a traffic behavior and the trafficbehavior contains a flow mirroring action.

7.12 Configuring Remote Flow MirroringThis section describes how to configure remote flow mirroring.


7.12.2 Setting Traffic Classification Rules

7.12.3 Configuring Remote Flow Mirroring




Applicable EnvironmentWhen incoming flows passing through the S5300 with the same attribute need to be monitored,you can configure remote flow mirroring if the monitored interface receiving these incomingflows is not located on the same S5300 as the observing port.

NOTE

S5300SI does not support remote flow mirroring.


Data PreparationTo configure remote flow mirroring, you need the following data.

No. Data


2 Type and number of the flow mirroring interface

3 Names of the traffic classifier, traffic behavior, and traffic policy


7.12.2 Setting Traffic Classification Rules

ContextFor how to configure traffic classification rules, see 7.11.2 Configuring Traffic ClassificationRules.




Issue 03 (2011-01-30)

7.12.3 Configuring Remote Flow Mirroring

Procedurel Configure remote flow mirroring on the source switch.

NOTE


The S5300SI series do not support remote flow mirroring.

1. Run:system-view


2. Run:vlan vlan-id

An RSPAN VLAN is created and the RSPAN VLAN view is displayed.

3. Run:mac-address learning disable



4. Run:quit


5. Run:observe-port index interface interface-type interface-number [ vlan vlan-id ]

An observing port is configured, and the RSPAN VLAN is specified.

6. Run:traffic behavior behavior-name

A traffic behavior is created and the traffic behavior view is displayed.

7. Run:mirroring to observe-port index

Remote flow mirroring is configured.

After configuring flow mirroring in a traffic behavior, you need to bind the behaviorto a traffic classifier in a traffic policy and then apply the policy to the interface. Fordetails, see 7.11.4 Creating and Applying a Traffic Policy.



l Configure the remote observing Interface on the destination switch.



7-27


----End


Context

For how to configure traffic classification rules on the source S5300, see 7.11.4 Creating andApplying a Traffic Policy.


Action Command





Check the configuration of flowmirroring in the traffic policy onan interface.





l The RSPAN VLAN is configured properly.

l A proper traffic policy is applied to the interface where incoming flows need to bemonitored.

l The applied traffic policy contains a proper traffic classifier and a traffic behavior, and thetraffic behavior contains the flow mirroring action.

7.13 Canceling Flow MirroringThis section describes how to cancel flow mirroring.


7.13.2 Canceling Flow Mirroring





Issue 03 (2011-01-30)



When flow mirroring is enabled and the flow, with the same attributes, passing through theS5300 does not need to be monitored, you can cancel flow mirroring.


None.

Data Preparation

To cancel flow mirroring, you need the following data.

No. Data

1 Type and number of the interface where flow mirroring needs to be cancelled

2 Name of the traffic policy

7.13.2 Canceling Flow Mirroring

Context

Do as follows on the S5300 that is configured with flow mirroring.

Procedure



Step 2 Run:traffic behavior behavior-name

The traffic behavior view is displayed.

Step 3 Run:undo mirroring

The flow mirroring action is cancelled.

Step 4 Run:quit

Exit from the traffic behavior view.




7-29


Step 6 Run:undo traffic-policy inbound

The traffic policy and flow mirroring action on the interface are canceled.

To cancel a traffic policy, you must cancel the traffic policy on all the interfaces where the trafficpolicy is applied, and then run the undo traffic policy policy-name command to cancel the trafficpolicy in the system view.

----End


Action Command





Check the flow mirroringconfiguration in the traffic policyon an interface.


If the following result is obtained, it indicates that the configuration succeeds:

The traffic policy applied on an interface is cancelled.

7.14 Changing or Deleting an Observing PortThis section describes how to change or delete an observing port.


7.14.2 (Optional) Deleting an Observing Port

7.14.3 (Optional) Changing an Observing Port




When you do not need to monitor the flow passing through the S5300, you can delete the currentobserving port; when you need to specify another interface on the S5300 as an observing port,you can change the current observing port.




Issue 03 (2011-01-30)


Before changing or deleting an observing port, complete the following tasks:l 7.4 Canceling Port Mirroringl 7.7 Canceling VLAN Mirroringl 7.10 Canceling Mirroring Based on MAC Addressesl 7.13 Canceling Flow Mirroring

Data Preparation

To change or delete an observing port, you need the following data.

No. Data

1 Type and number of the new observing port

7.14.2 (Optional) Deleting an Observing Port

PrerequisiteBefore deleting an observing port, make sure that the observing port is not used in any mirroringconfiguration.

Procedure





Step 3 Run:undo port-mirroring { both | inbound | outbound }

Interface mirroring is canceled.

Step 4 Run:quit


Step 5 Run:undo observe-port index

The observing port is deleted.

----End



7-31

7.14.3 (Optional) Changing an Observing Port

Procedure




Another interface is specified as an observing port.

----End


Action Command





If the observing port is deleted or a new observing port is specified, it indicates that theconfiguration succeeds.

7.15 Configuring CPU MirroringThis section describes how to configure CPU mirroring.


7.15.2 (Optional) Configuring an ACL Rule

7.15.3 Configuring an Observing Port

7.15.4 Configuring CPU Mirroring



Applicable EnvironmentWhen debugging the S5300, you can configure CPU mirroring, if you need to monitor thepackets received by the CPU.




Issue 03 (2011-01-30)


Data PreparationTo configure CPU mirroring, you need the following data.

No. Data

1 (Optional) ACL number and ACL rule

2 Index, type, and ID of the observing port

7.15.2 (Optional) Configuring an ACL Rule

ContextDo as follows on the S5300 that needs to be configured with CPU mirroring.

Procedure



Step 2 Run:acl [ number ] acl-number

An Access Control List (ACL) is created and the ACL view is displayed.

For details on the acl command, refer to the Quidway S5300 Series Ethernet Switches -Command Reference.

Step 3 Run:rule

A basic or an advanced ACL rule is created.

For details on the rule command, see the Quidway S5300 Series Ethernet Switches - CommandReference.

----End

7.15.3 Configuring an Observing Port

Procedure




7-33



A global observing port is configured.

----End

7.15.4 Configuring CPU Mirroring

Procedure



Step 2 Run:port-mirroring cpu [ acl acl-number ] to observe-port index inbound

CPU mirroring is configured.

By default, CPU mirroring is disabled.

----End


Action Command



Check information about CPUmirroring.

display cpu port-mirroring

If the number of the ACL that matches packets received by the CPU and the observing port aredisplayed, it indicates that the configuration succeeds.

7.16 Cancelling CPU MirroringThis section describes how to cancel CPU mirroring.


7.16.2 Cancelling CPU Mirroring





Issue 03 (2011-01-30)


Applicable EnvironmentIf packets received by the CPU of the S5300 do not need to be monitored, you can cancel CPUmonitoring.


Data PreparationTo cancel CPU mirroring, you need the following data.

No. Data

1 Number of the observing port

7.16.2 Cancelling CPU Mirroring

Procedure



Step 2 Run:undo port-mirroring cpu

CPU mirroring is cancelled.

Step 3 Optional: Run:undo observe-port index

The index of the observing port is deleted.

----End


Action Command



Check information about CPUmirroring.

display cpu port-mirroring



7-35

7.17 Configuration ExamplesThis section provides several configuration examples for mirroring.

7.17.1 Example for Configuring Local Port Mirroring

7.17.2 Example for Configuring Local VLAN Mirroring

7.17.3 Example for Configuring MAC Address-based Local Mirroring

7.17.4 Example for Configuring Local Flow Mirroring

7.17.5 Example for Configuring Remote Port Mirroring

7.17.6 Example for Changing an Observing Port

7.17.1 Example for Configuring Local Port Mirroring


As shown in Figure 7-4, a Layer 2 (L2) switch is connected to GigabitEthernet 0/0/1 on theSwitch, and the incoming traffic on GigabitEthernet 0/0/1 needs to be monitored. In this case,you can configure local port mirroring with GigabitEthernet 0/0/1 as a mirrored port andGigabitEthernet 0/0/24 as an observing port.

Figure 7-4 Networking diagram of local port mirroring

Router

SwitchGE0/0/3

GE0/0/1 GE0/0/24

L2 Switch Mirroring host

Configuration Roadmap

The configuration roadmap is as follows:

1. Configure GigabitEthernet 0/0/24 as an observing port.

2. Configure GigabitEthernet 0/0/1 as a mirrored port.




Issue 03 (2011-01-30)

Data PreparationNone.

Configuration Procedure1. Create a VLAN on the Switch and add interfaces to the VLAN in trunk mode.

# Add GigabitEthernet 0/0/1 and GigabitEthernet 0/0/3 to a same VLAN in trunk mode.The following takes the configuration of GigabitEthernet 0/0/1 as an example. Theconfiguration of GigabitEthernet 0/0/3 is the same as the configuration of GigabitEthernet0/0/1 and is not mentioned here.<Switch> system-view[Switch] vlan 1[Switch-vlan1] quit[Switch] interface GigabitEthernet 0/0/1[Switch-GigabitEthernet0/0/1] port trunk allow-pass vlan 1[Switch-GigabitEthernet0/0/1] quit

2. Configure an observing port.# Set GigabitEthernet 0/0/24 as the observing port.<Switch> system-view[Switch] observing-port 1 interface GigabitEthernet 0/0/24

3. Configure a mirrored port.# Set GigabitEthernet 0/0/1 as the mirrored port.[Switch] interface GigabitEthernet 0/0/1[Switch-GigabitEthernet0/0/1] port-mirroring to observe-port 1 inbound[Switch-GigabitEthernet0/0/1] quit

4. Verify the configuration.# Run the display port-mirroring command. You can check the configurations on theobserving port and mirrored port.[Switch] display port-mirroring Observe index 1 is set to interface GigabitEthernet0/0/24 Observe Type: Local Interface GigabitEthernet0/0/1 Mirrored to: Observe index 1 Direction: inbound Observe index 2 is not set to any interface Observe index 3 is not set to any interface Observe index 4 is not set to any interface

Configuration FilesConfiguration file of the Switch

#vlan batch 1# sysname Switch# observing-port 1 interface GigabitEthernet0/0/24#interface GigabitEthernet0/0/1 port trunk allow-pass vlan 1 port-mirroring to observe-port 1 inbound#interface GigabitEthernet0/0/3 port trunk allow-pass vlan 1#return



7-37

7.17.2 Example for Configuring Local VLAN Mirroring

Networking RequirementsAs shown in Figure 7-5, GigabitEthernet0/0/1 is connected to PC1; GigabitEthernet0/0/2 isconnected to PC2. PC1 and PC2 belong to VLAN 10. Now, incoming traffic of all activeinterfaces in VLAN 10 needs to be monitored. In this case, you can configure local VLANmirroring.

GigabitEthernet0/0/3 serves as an observing port.

Figure 7-5 Networking diagram of local VLAN mapping

PC1 PC2

GE0/0/2

GE0/0/3GE0/0/1 PC3


1. Configure GigabitEthernet0/0/3 as an observing port.2. Configure VLAN 10 as a mirrored VLAN.


Configuration Procedure1. Add GigabitEthernet0/0/1 and GigabitEthernet0/0/2 to VLAN 10 as access interfaces.

# Add GigabitEthernet0/0/1 to VLAN 10 as an access interface.<Switch> system-view[Switch] interface gigabitethernet 0/0/1[Switch-GigabitEthernet0/0/1] port link-type access[Switch-GigabitEthernet0/0/1] port default vlan 10[Switch-GigabitEthernet0/0/1] quitAdd GigabitEthernet0/0/2 to VLAN 10 as an access interface in the same way.

2. Configure an observing port.# Set GigabitEthernet0/0/3 as an observing port.




Issue 03 (2011-01-30)

[Switch] observing-port 1 interface GigabitEthernet 0/0/3

3. Configure a mirrored VLAN.

# Set VLAN 10 as a mirrored VLAN.[Switch] VLAN 10[Switch-VLAN10] mirroring to observe-port 1 inbound[Switch-VLAN10] quit

4. Verify the configuration.

# Run the display port-mirroring command. You can view the configuration of theobserving port.[Switch] display port-mirroring Observe index 1 is set to interface GigabitEthernet0/0/3 Observe Type: Local Observe index 2 is not set to any interface Observe index 3 is not set to any interface Observe index 4 is not set to any interface

Configuration Files

Configuration file of the Switch

#sysname Switch# vlan batch 1 10# observe-port 1 interface GigabitEthernet0/0/3#vlan 10 mirroring to observe-port 1 inbound#interface GigabitEthernet0/0/1 port link-type access port default vlan 10#interface GigabitEthernet0/0/2 port link-type access port default vlan 10# #return

7.17.3 Example for Configuring MAC Address-based LocalMirroring


As shown in Figure 7-6, GigabitEthernet 0/0/1 is connected to PC1; GigabitEthernet 0/0/2 isconnected to PC2; GigabitEthernet 0/0/4 is connected to a router. GigabitEthernet 0/0/1,GigabitEthernet 0/0/2, and GigabitEthernet 0/0/4 belong to VLAN 10. Now, incoming trafficwith the source or destination MAC as the MAC address of GigabitEthernet 1/0/1 on the routerin VLAN 10 needs to be monitored. In this case, you can configure local MAC address mirroringon the Switch.

GigabitEthernet 0/0/3 serves as an observing port. The MAC address of GigabitEthernet 1/0/1is 0001-0001-0001.



7-39

Figure 7-6 Networking diagram of local MAC address mirroring

PC1 PC2

GE0/0/2

GE0/0/3GE0/0/1

PC3

GE0/0/4

GE1/0/1


1. Set GigabitEthernet 0/0/3 as an observing port.2. Configure local MAC address mirroring in the view of VLAN 10.


Configuration Procedure1. Configure VLAN 10 and then add GigabitEthernet 0/0/1, GigabitEthernet 0/0/2, and

GigabitEthernet 0/0/4 to VLAN 10. The configuration procedure is not mentioned here.2. # Set GigabitEthernet 0/0/3 as an observing port.

<Switch> system-view[Switch] observing-port 1 interface GigabitEthernet 0/0/3

3. Configure a mirroring VLAN.# Configure local MAC address mirroring in the view of VLAN 10.[Switch] VLAN 10[Switch-VLAN10] mac-mirroring 0001-0001-0001 to observe-port 1 inbound[Switch-VLAN10] quit

4. Verify the configuration.# Run the display port-mirroring command. You can view the configuration of theobserving port.[Switch] display port-mirroring Observe index 1 is set to interface GigabitEthernet0/0/3 Observe Type: Local Observe index 2 is not set to any interface Observe index 3 is not set to any interface Observe index 4 is not set to any interface





Issue 03 (2011-01-30)

#sysname Switch# vlan batch 1 10# observing-port 1 interface GigabitEthernet0/0/3# cluster enable ntdp enable ntdp hop 16 ndp enable#vlan 10 mac-mirroring 0001-0001-0001 to observe-port 1 inbound#interface GigabitEthernet0/0/1 port default vlan 10 bpdu enable ntdp enable ndp enable#interface GigabitEthernet0/0/2 port default vlan 10 bpdu enable ntdp enable ndp enable #interface GigabitEthernet0/0/3 port default vlan 1 bpdu enable ntdp enable ndp enable#interface GigabitEthernet0/0/4 port default vlan 10 bpdu enable ntdp enable ndp enable# #return

7.17.4 Example for Configuring Local Flow Mirroring

Networking RequirementsAs is shown in Figure 7-7, the Switch is connected to two L2 switches through GigabitEthernet0/0/1 and GigabitEthernet 0/0/5. Packets with the same attributes received by GigabitEthernet0/0/1 and GigabitEthernet 0/0/5 and transmitted from GigabitEthernet 0/0/3 need to bemonitored. In this example, packets with the 802.1p priority as 6 need to be monitored.

GigabitEthernet 0/0/24 is set as an observing port.



7-41

Figure 7-7 Networking diagram of local flow mirroring

Router

Switch GE0/0/3

GE 0/0/1 GE0/0/24

L2 Switch Mirroring host

GE0/0/5

L2 Switch


1. Set GigabitEthernet 0/0/24 as an observing port.2. Create a traffic classifier and set the traffic classification rule that only the packets with the

802.1p priority as 6 can be matched.3. Create a traffic behavior and configure flow mirroring in the traffic behavior.4. Create a traffic policy and bind the traffic classifier to the traffic behavior.5. Apply the traffic policy to GigabitEthernet 0/0/1 and GigabitEthernet 0/0/5.6. Create a VLAN on the Switch. Add GigabitEthernet 0/0/3, GigabitEthernet 0/0/1, and

GigabitEthernet 0/0/5 to the same VLAN in trunk mode.


l Name of the traffic classifier: c1l Name of the traffic behavior: b1l Name of the traffic policy: p1l ID of the VLAN created on the Switch: 1

Configuration Procedure1. Create a VLAN on the Switch and add interfaces to the VLAN in trunk mode.

# Add GigabitEthernet 0/0/1, GigabitEthernet 0/0/3, and GigabitEthernet 0/0/5 to the sameVLAN in trunk mode. The following takes the configuration of GigabitEthernet 0/0/1 asan example. The configurations of GigabitEthernet 0/0/3 and GigabitEthernet 0/0/5 are thesame as the configuration of GigabitEthernet 0/0/1 and are not mentioned here.




Issue 03 (2011-01-30)

<Switch> system-view[Switch] vlan 10[Switch-vlan10] quit[Switch] interface GigabitEthernet 0/0/1[Switch-GigabitEthernet0/0/1] port link-type trunk[Switch-GigabitEthernet0/0/1] port trunk allow-pass vlan 10[Switch-GigabitEthernet0/0/1] quit

2. Configure an observing port.# Set GigabitEthernet 0/0/24 as the observing port.[Switch] observe-port 1 interface GigabitEthernet 0/0/24

3. # Create a traffic classifier.# Create traffic classifier c1 and set the traffic classification rule that only the packets withthe 802.1p priority as 6 can be matched.[Switch] traffic classifier c1[Switch-classifier-c1] if-match 8021p 6[Switch-classifier-c1] quit

4. # Create a traffic behavior.# Create traffic behavior b1 and configure flow mirroring in the traffic behavior.[Switch] traffic behavior b1[Switch-behavior-b1] mirroring to observe-port 1[Switch-behavior-b1] quit

5. Create a traffic policy.# Create a traffic policy and bind traffic classifier c1 to traffic behavior b1.[Switch] traffic policy p1[Switch-trafficpolicy-p1] classifier c1 behavior b1[Switch-trafficpolicy-p1] quit

6. Apply the traffic policy and enable the interface to trust the 802.1p priority of packets.# Apply traffic policy p1 to GigabitEthernet 0/0/1 and GigabitEthernet 0/0/5, and enableGigabitEthernet 0/0/1 and GigabitEthernet 0/0/5 to trust the 802.1p priority of packets.[Switch] interface GigabitEthernet 0/0/1[Switch-GigabitEthernet0/0/1] traffic-policy p1 inbound[Switch-GigabitEthernet0/0/1] trust 8021p[Switch-GigabitEthernet0/0/1] quit[Switch]interface GigabitEthernet 0/0/5[Switch-GigabitEthernet0/0/5] traffic-policy p1 inbound[Switch-GigabitEthernet0/0/5] trust 8021p[Switch-GigabitEthernet0/0/5] quit

7. Verify the configuration.# Run the display port-mirroring command. You can check the observing port.[Switch] display port-mirroring Observe index 1 is set to interface GigabitEthernet0/0/24 Observe Type: Local Observe index 2 is not set to any interface Observe index 3 is not set to any interface Observe index 4 is not set to any interface # Run the display traffic policy interface command. You can check the traffic policyapplied to GigabitEthernet 0/0/1 and GigabitEthernet 0/0/5.[Switch] display traffic policy interface Interface: GigabitEthernet0/0/1 Direction: Inbound Policy: p1 Classifier: c1 Rule(s) : if-match 8021p 6 Behavior: b1 mirroring to observe-port 1 Interface: GigabitEthernet0/0/5



7-43

Direction: Inbound Policy: p1 Classifier: c1 Rule(s) : if-match 8021p 6 Behavior: b1 mirroring to observe-port 1


#sysname Switch#vlan batch 10# observe-port 1 interface GigabitEthernet0/0/24#traffic classifier c1 if-match 8021p 6#traffic behavior b1 mirroring to observe-port 1#traffic policy p1 classifier c1 behavior b1#interface GigabitEthernet0/0/1port link-type trunkport trunk allow-pass vlan 10 traffic-policy p1 inbound trust 8021p#interface GigabitEthernet0/0/3port link-type trunk port trunk allow-pass vlan 10#interface GigabitEthernet0/0/5port link-type trunk port trunk allow-pass vlan 10 traffic-policy p1 inbound trust 8021p#interface GigabitEthernet0/0/24#return

7.17.5 Example for Configuring Remote Port Mirroring

Networking RequirementsAs shown in Figure 7-8, Switch A is connected to PC1; Switch C is connected to PC2. Now,incoming traffic of GigabitEthernet 0/0/2 on Switch A needs to be monitored on PC2. In thiscase, you can configure remote port mirroring on Switch A.




Issue 03 (2011-01-30)

Figure 7-8 Networking diagram of remote port mirroring

SwitchA SwitchB SwitchC

PC2

GE0/0/2

GE 0/0/1GE0/0/2

GE 0/0/1GE0/0/2

GE0/0/1

PC1



l Configure GE 0/0/1 of Switch A as an observing interface and specify the RSPAN VLAN.l Configure Ethernet 0/0/2 of Switch A as a mirrored interface.l Configure Ethernet 0/0/1 of Switch C as an observing interface.

Data Preparation

To complete the configuration, you need the following data:l Index of the observing interface on Switch A: 1l ID of the RSPAN VLAN on Switch A, Switch B, and Switch C: 2l Index of the observing interface on Switch C: 1

Configuration Procedure1. Configure Switch A.

# Configure the RSPAN VLAN.<SwitchA> system-view[SwitchA] vlan 2[SwitchA-vlan2] quit

# Configure GE 0/0/1 of Switch A as an observing interface and specify the RSPAN VLAN.[SwitchA] observe-port 1 interface GigabitEthernet 0/0/1 vlan 2

# Add GE 0/0/1 to the RSPAN VLAN as a trunk interface.[SwitchA] interface gigabitethernet 0/0/1[SwitchA-GigabitEthernet0/0/1] port link-type trunk[SwitchA-GigabitEthernet0/0/1] port trunk allow-pass vlan 2[SwitchA-GigabitEthernet0/0/1] quit

# Configure remote port mirroring for incoming traffic on GE 0/0/2 and specify the RSPANVLAN.[SwitchA] interface GigabitEthernet 0/0/2[SwitchA-GigabitEthernet0/0/2] port-mirroring to observe-port 1 inbound[SwitchA-GigabitEthernet0/0/2] quit



7-45

2. Configure Switch B.# Create an RSPAN VLAN and disable MAC address learning in this VLAN..<SwitchB> system-view[SwitchB] vlan 2[SwitchB-vlan2] mac-address learning disable[SwitchB-vlan2] quit# Add GE 0/0/1 and GE 0/0/2 to the RSPAN VLAN as trunk interfaces.[SwitchB] interface GigabitEthernet 0/0/1[SwitchB-GigabitEthernet0/0/1] port link-type trunk[SwitchB-GigabitEthernet0/0/1] port trunk allow-pass vlan 2[SwitchB-GigabitEthernet0/0/1] quit[SwitchB] interface GigabitEthernet 0/0/2[SwitchB-GigabitEthernet0/0/2] port link-type trunk[SwitchB-GigabitEthernet0/0/2] port trunk allow-pass vlan 2[SwitchB-GigabitEthernet0/0/2] quit

3. Configure Switch C.# Create the RSPAN VLAN.<SwitchC> system-view[SwitchC] vlan 2[SwitchC-vlan2] quit# Add GE 0/0/2 to the RSPAN VLAN as a trunk interface.[SwitchC] interface GigabitEthernet 0/0/2[SwitchC-GigabitEthernet0/0/2] port link-type trunk[SwitchC-GigabitEthernet0/0/2] port trunk allow-pass vlan 2[SwitchC-GigabitEthernet0/0/2] quit# Configure GE 0/0/1 as a hybrid interface and configure it to allow packets of the RSPANVLAN to pass.[SwitchC] interface GigabitEthernet 0/0/1[SwitchC-GigabitEthernet0/0/1] port hybrid untagged vlan 2[SwitchC-GigabitEthernet0/0/1] quit

Configuration FilesConfiguration file of Switch A

#sysname SwitchA#vlan 2# observe-port 1 interface GigabitEthernet0/0/1 vlan 2#interface GigabitEthernet0/0/1 port link-type trunk port trunk allow-pass vlan 2#interface GigabitEthernet0/0/2 port-mirroring to observe-port 1 inbound# #return

Configuration file of Switch B

sysname SwitchB#vlan 2 mac-address learning disable




Issue 03 (2011-01-30)

#interface GigabitEthernet0/0/1 port link-type trunk port trunk allow-pass vlan 2#interface GigabitEthernet0/0/2 port link-type trunk port trunk allow-pass vlan 2# #return

Configuration file of Switch C

#sysname SwitchC#vlan 2#interface GigabitEthernet 0/0/1 port hybrid untagged vlan 2#interface GigabitEthernet 0/0/2 port link-type trunk port trunk allow-pass vlan 2# #return

7.17.6 Example for Changing an Observing Port

Networking RequirementsAs shown in Figure 7-9,GigabitEthernet 0/0/1 on the Switch is connected to an L2 switch;GigabitEthernet 0/0/24 is connected to host 1; GigabitEthernet 0/0/5 is connected to host 2. Tomonitor incoming traffic on GigabitEthernet 0/0/1, port mirroring is configured on the Switch.Configure GigabitEthernet 0/0/1 as a mirrored port, and GigabitEthernet 0/0/24 connected tohost 1 as an observing port. Enable host 1 to receive incoming traffic from GigabitEthernet 0/0/1.

At present, host 2 needs to receive incoming traffic from GigabitEthernet 0/0/1. Thus, theobserving port needs to switch from GigabitEthernet 0/0/24 to GigabitEthernet 0/0/5.



7-47

Figure 7-9 Networking for changing the observing port

Router

SwitchGE0/0/3

GE0/0/1

L2 Switch

Mirroringhost1

Mirroring host2

GE0/0/5

GE0/0/24


1. Delete the mirrored port GigabitEthernet 0/0/1.2. Set GigabitEthernet 0/0/5 instead of GigabitEthernet 0/0/24 as the observing port.3. Reset GigabitEthernet 0/0/1 as the mirrored port.


l Type and number of the new observing port, that is, GigabitEthernet 0/0/5

Configuration Procedure1. Check the configurations on the current observing port and mirrored port.

# Run the display port-mirroring command to check the configurations on the currentobserving port and mirrored port.<Switch> display port-mirroring Port-mirror: ---------------------------------------------------------- Mirror-port Direction Observe-port ---------------------------------------------------------- GigabitEthernet0/0/1 Inbound GigabitEthernet0/0/24

2. Delete the mirrored port.# Delete the mirrored port GigabitEthernet 0/0/1.<Switch> system-view[Switch] interface GigabitEthernet 0/0/1[Switch-GigabitEthernet0/0/1] undo port-mirroring inbound




Issue 03 (2011-01-30)

3. Delete the observing port.# Delete the observing port GigabitEthernet 0/0/24.<Switch> system-view[Switch] undo observe-port 1

4. Change the observing port.# Change the observing port to GigabitEthernet 0/0/5.[Switch] observe-port 1 interface GigabitEthernet 0/0/5

5. Configure a mirrored port.# Reset GigabitEthernet 0/0/1 as the mirrored port.[Switch] interface GigabitEthernet 0/0/1[Switch-GigabitEthernet0/0/1] port-mirroring to observe-port 1 inbound[Switch-GigabitEthernet0/0/1] quit

6. Verify the configuration.# Run the display port-mirroring command. You can check the configurations on thecurrent observing port and mirrored port.[Switch] display port-mirroring Port-mirror: ---------------------------------------------------------- Mirror-port Direction Observe-port ---------------------------------------------------------- GigabitEthernet0/0/1 Inbound GigabitEthernet0/0/5


# sysname Switch# observe-port 1 interface GigabitEthernet0/0/5#interface GigabitEthernet0/0/1 port-mirroring to observe-port 1 inbound#return



7-49

8 PoE Configuration

About This Chapter

This chapter describes the basic concepts and configuration methods of PoE.

8.1 PoE OverviewThis section describes the basic concepts of PoE.

8.2 PoE Features Supported by the S5300This section describes the PoE features supported by the S5300.

8.3 Configuring PoE FunctionsThis section describes how to configure PoE functions.

8.4 Configuration ExamplesThis section provides an example for configuring PoE on the S5300.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 8 PoE Configuration


8-1

8.1 PoE OverviewThis section describes the basic concepts of PoE.

Power over Ethernet (PoE) refers to power supply over a 10Base-T, 100Base-TX, or 1000Base-T twisted pair cable. PoE can be used to effectively provide power for terminals such as IPphones, Access Points (APs), chargers of portable devices, point-of-sale (POS) machines,cameras, and data collection. Terminals are powered when they access the network. Therefore,the indoor cabling of power supply need not be considered. Currently, PoE supports the unifiedstandard IEEE 802.3af and 802.3at, which enables devices developed by different vendors to becompatible with each other.

8.2 PoE Features Supported by the S5300This section describes the PoE features supported by the S5300.

The downstream electrical interfaces of the S5300 support PoE. Each downstream interfaceprovides a maximum of 30 W power and a maximum power supply distance of 100 m. TheS5300 can transmit current and data on the same pair of signal cables.

PoE power supplies are classified into the following types: 500 W constant current power supplyand 250 W constant current power supply. A 500 W power supply provides 369.6 W power forthe PoE function, and a 250 W power supply provides 123.2 W for the PoE function.

The following S5300 models support PoE:l S5348TP-PWR-SI, S5352C-PWR-SI, and S5352C-PWR-EI

Each switch has two power supply slots. Each slot supports a 500 W or 250 W powersupply. When two PoE power supplies are used, determine their working mode accordingto the following table.

Power Supply Combination Available PoE Power

250 W constant current – 123.2W


250 W constant current 250 W constant current 246.4W



l S5324TP-PWR-SI, S5328C-PWR-EI, and S5328C-PWR-SI

Each switch has two power supply slots. Each slot supports a 500 W or 250 W powersupply. When two PoE power supplies are used, determine their working mode accordingto the following table.




8 PoE ConfigurationQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)





8.3 Configuring PoE FunctionsThis section describes how to configure PoE functions.


8.3.2 Configuring the PoE Function Globally

8.3.3 Configuring the PoE Function on an InterfaceIn an interface view, you can enable the PoE function, set the maximum output power, set thepower supply priority, and specify the power-off time segment.



Applicable EnvironmentThe S5300 can detect whether a device connected to it needs the remote power supply andprovide power for the device that requires the remote power supply.

According to the actual requirements on the network, you can:

l Set the maximum power and reserved power of the PoE power supply on the S5300 throughcommands.

l Control the remote power supply features of PoE interfaces separately, for example, enableor disable the remote power supply function, and set the maximum output power, the powersupply mode, and the power supply priority through commands.

Pre-configuration TasksBefore configuring the PoE functions, complete the following task:

Installing the PoE power supply on the S5300.

8.3.2 Configuring the PoE Function Globally

Procedurel Optional: Set the maximum output power of the device.

1. Run:system-view




8-3

2. Run:poe max-power maximum-power [ slot slot-id ]

The maximum output power of a board is set.

The value of maximum-power ranges from 15400 to 739200, in mW.l Optional: Configure the PoE power supply management mode.

1. Run:system-view


poe power-management { auto | manual } [ slot slot-id ]

The power supply management mode is configured.l Optional: Manually power on or power off the PD connected to an interface.

NOTE

When the manual power management mode is adopted, you must manually power on or power offPDs on interfaces.

1. Run:system-view


poe power-on interface interface-type interface-number or poe power-off interface interface-type interface-number

The PD connected to an interface is powered on or powered off manually.l Optional: Configure a board to allow high inrush current during power-on.

If a PD does not comply with IEEE 802.3at or 802.3af, high inrush current is generatedwhen the PD is powered on. In this case, the PSE cuts off the power of the PD to protectitself. If the PSE is required to provide power for the PD, the PSE must allow high inrushcurrent.

1. Run:system-view


poe high-inrush enable

A PoE board is configured to allow high inrush current during power-on.

By default, a board does not allow high inrush power during power-on.l Optional: Set the percentage of the reserved PoE power against the total PoE power.

The S5300 can dynamically allocate power to each interface according to the powerconsumption of each interface. The power consumption of a PD keeps changing when thePD is running. The S5300 periodically calculates the total power consumption of all thePDs connected to the device. If the total power consumption exceeds the upper thresholdof the board, the S5300 cuts off the power of the PDs on the interfaces of low priority toensure that other PDs can run normally.

Sometimes, the power consumption increases sharply and the available power of the devicecannot support the burst increase of power. At this time, the software system has not found




Issue 03 (2011-01-30)

that the total power consumption exceeded the upper threshold; therefore, the S5300 doesnot power off interfaces of low priority in time. As a result, the PoE power supply is shutdown for overload protection, and thus all PDs are powered off.

This problem can be solved by setting proper reserved power. When the power consumptionincreases sharply, the reserved power can support the system running. Then the systemsoftware has time to power off interfaces of low priority to ensure stable running of otherPDs.

1. Run:system-view


poe power-reserved reserved-power-percent [ slot slot-id ]

The percentage of the reserved PoE power against the total PoE power is set.

By default, 20% of the total PoE power is reserved.l Optional: Set the alarm threshold of power consumption percentage.

1. Run:system-view


poe power-threshold thresholdvalue [ slot slot-id ]

The alarm threshold of power consumption percentage is set.

By default, the alarm threshold is 90%. That is, an alarm is generated when theconsumed power accounts for 90% of the total power.

----End

8.3.3 Configuring the PoE Function on an InterfaceIn an interface view, you can enable the PoE function, set the maximum output power, set thepower supply priority, and specify the power-off time segment.

Procedure

Step 1 Enable the PoE function on an interface.1. Run:

system-view




poe enable

The PoE function is enabled.



8-5

By defult, the PoE function is enabled on all interfaces.

Step 2 Optional: Set the maximum output power of an interface.1. Run:

system-view




poe power maximum-power

The maximum output power of the interface is set.

By default, the maximum output power of an interface is 30000 mW.

Step 3 Optional: Set the power supply priority of an interface.

1. Run:system-view




poe priority { critical | high | low }

The power supply priority of the interface is set.

By default, the power supply priority of an interface is low.

The priorities in descending order are critical, high, and low.

Step 4 Optional: (Optional) Set the power-off time range of a PoE interface.1. Run:

system-view


time-range time-name { start-time to end-time days | from time1 date1 [ to time2 date2 ] }

The power-off time range of a PoE interface is set.3. Run:



poe power-off time-range time-range-name

The power-off time range takes effect on the interface.

Step 5 Optional: Enable an interface to check compatibility of PDs.




Issue 03 (2011-01-30)

NOTEBefore enabling an interface to check compatibility of PDs, you must enable PoE on the PSE. After thisfunction is enabled, the interface can detect the PDs that do not comply with IEEE 802.3af.

1. Run:system-view




poe legacy enable

The interface is enabled to check compatibility of PDs.

By default, an interface does not check compatibility of PDs.

Step 6 Optional: Power on an interface forcibly.

If the PSE cannot identify the PD connected to an interface, you can forcibly power on theinterface. Before powering on the interface, ensure that the system power is sufficient.

1. Run:system-view




poe force-power

The interface is forcibly powered on.

By default, an interface cannot provide power for unidentified PDs.

----End


Prerequisite

The PoE power supply and PoE board are installed, and the PoE function is configured.

Procedure

Step 1 Run the display poe-power command to view the status of the PoE power supply.

Step 2 Run the display poe device command to view information about the devices that support thePoE function.

Step 3 Run the display poe information command to view the PoE information.



8-7

Step 4 Run the display poe power interface interface-type interface-number command to view theoutput power of an interface.

Step 5 Run the display poe power-state interface interface-type interface-number command to viewthe status of PoE power supply on an interface.

----End

8.4 Configuration ExamplesThis section provides an example for configuring PoE on the S5300.

8.4.1 Example for Configuring PoE on the Switch

8.4.1 Example for Configuring PoE on the Switch


As shown in Figure 8-1, Switch supports PoE. Switch A, Switch B, and the AP can be poweredthrough PoE.

NOTESwitch A, Switch B, and the AP are devices of other vendors and need to be powered through PoE.

l Switch A is connected to GE 0/0/1 on Switch; the maximum power consumption of SwitchA is 12000 mw; Switch A is connected to the data server and needs to be powered first.

l Switch B is connected to GE 0/0/2 on Switch; the maximum power consumption of SwitchB is 12000 mw; Switch B is connected to common users who access the Internet.

l The AP is connected to GE 0/0/3 on Switch; the maximum power consumption of the APis 2500 mw; the AP is connected to users who access the Internet wirelessly.

Switch provides power for Switch A, Switch B, and the AP in automatic mode, and is enabledwith compatibility detection for PDs.

Figure 8-1 Networking diagram of PoE configurations

Switch

SwitchB

SwitchA AP

GE0/0/1

GE0/0/2

GE0/0/3




Issue 03 (2011-01-30)


1. Enable PoE on GE 0/0/1 of Switch, and configure the maximum power and the powersupply priority of GE 0/0/1.

2. Enable PoE on GE 0/0/2 of Switch, and set the maximum power consumption of GE 0/0/2.3. Enable PoE on GE 0/0/3 of Switch, and set the maximum power consumption of GE 0/0/3.4. Configure the maximum power consumption of the interface connecting the AP on

Switch.5. Configure the power supply management of Switch to be in automatic mode.

Data PreparationTo complete the configuration, you need the following data:l Number of an interface on which PoE is to be enabledl Maximum power consumption of an interface

Configuration Procedure1. # Enable PoE on GE 0/0/1 of Switch, and configure the maximum power and the power

supply priority GE 0/0/1.<Switch> system-view[Switch] interface gigabitethernet 0/0/1[Switch-GigabitEthernet0/0/1] poe enable[Switch-GigabitEthernet0/0/1] poe power 12000[Switch-GigabitEthernet0/0/1] poe priority critical[Switch-GigabitEthernet0/0/1] quit

2. # Enable PoE on GE 0/0/2 of Switch, and set the maximum power consumption of GE 0/0/2to 20000 mW.[Switch] interface gigabitethernet 0/0/2[Switch-GigabitEthernet0/0/2] poe enable[Switch-GigabitEthernet0/0/2] poe power 20000[Switch-GigabitEthernet0/0/2] quit

3. # Enable PoE on GE 0/0/3 of Switch, and set the maximum power consumption of GE 0/0/3to 2500 mW.[Switch] interface gigabitethernet 0/0/3[Switch-GigabitEthernet0/0/3] poe enable[Switch-GigabitEthernet0/0/3] poe power 2500[Switch-GigabitEthernet0/0/3] quit

4. # Configure the power supply management of Switch to be in automatic mode.[Switch] poe power-management auto

Configuration FilesConfiguration file of Switch

# sysname Switch#interface GigabitEthernet0/0/1 poe power 12000 poe priority critical#interface GigabitEthernet0/0/2 poe power 20000



8-9

#interface GigabitEthernet0/0/3 poe power 2500#interface GigabitEthernet0/0/4#

return




Issue 03 (2011-01-30)

9 ALS Configuration

About This Chapter

This chapter describes the Automatic Laser Shutdown (ALS) configuration on the S5300.

9.1 ALS OverviewThe ALS mechanism controls the pulse of the laser of an optical module by detecting the Lossof Signal (LOS) on an optical interface.

9.2 ALS Features Supported by the S5300This section describes the ALS features supported by the S5300.

9.3 Configuring ALSConfiguring ALS of the laser of an optical module in the interface view provides securityprotection and saves energy.

9.4 Configuration ExamplesThis section provides a configuration example of ALS.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 9 ALS Configuration


9-1

9.1 ALS OverviewThe ALS mechanism controls the pulse of the laser of an optical module by detecting the Lossof Signal (LOS) on an optical interface.

When ALS is disabled, if the fiber link is faulty, the optical interface is not disabled and the laserof an optical module is enabled though data communication is interrupted. If the laser of anoptical module still sends pulses after data communication is interrupted, energy is wasted andeyes of operators may be hurt.

When ALS is enabled, if the fiber link is faulty, the software automatically disables the laser ofan optical module from sending pulses on the optical interface after detecting the LOS on theoptical interface. When the faulty fiber link is recovered, the software detects that the LOS ofthe optical interface is cleared. Then the software enables the laser to send pulses. The ALSmechanism protects operators against laser injury and saves energy.

9.2 ALS Features Supported by the S5300This section describes the ALS features supported by the S5300.

Applicable Environment of ALSl The switches are connected through fibers.

When switches are connected through fibers, the ALS function can be enabled on interfacesof switches to protect users against laser radiation to eyes, as shown in Figure 9-1.

Figure 9-1 Connecting switches through fibers

SwitchA SwitchB

TX RX

RX TX

l The switch and the optical network terminal (ONT) are connected through fibers.

In the application of fiber to the home (FTTH), if ONT users perform improper operationson the fiber because of lack of knowledge about radiation or children touch the fiber, theradiation of the laser harms eyes. To solve this problem, you can enable the ALS functionon the switch to protect safety of users. Figure 9-2 shows the connection.

Figure 9-2 Connecting the switch and ONT through the fiber

TX

TXRX

RX

Switch ONT

9 ALS ConfigurationQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

Influence of the ALS Function on Link Data Communication RecoveryWhen ALS is disabled, the optical module laser of the switch is still working. After the fiberlink is recovered, the LOS is cleared and the interface becomes Up rapidly. When ALS is enabled,the switch controls the laser by detecting the LOS on the interface. This delays the recovery ofdata communication on the link.

l ALS is enabled on both ends of the fiber link.As shown in Figure 9-1, two switches are connected through the fiber. The interfaces ofthe two switches are enabled with ALS and work in automatic restart mode. After the fiberlink is recovered, the process for interfaces of Switch A and Switch B changing from Downto Up is as follows:

1. Switch A sends pulses periodically.2. Switch B receives pulses of Switch A after the fiber link is recovered.3. The LOS on the interface of Switch B is cleared, and the interface becomes Up and

sends signals.4. Switch A receives signals of Switch B.5. The LOS on the interface of Switch A is cleared, the interface becomes Up, and data

communication is recovered.l ALS is enabled on one end of the fiber link.

As shown in Figure 9-1, two switches are connected through the fiber. ALS is disabled onthe interface of Switch A and enabled on the interface of Switch B, and the interface workin automatic restart mode. After the fiber link is recovered, the process for interfaces ofSwitch A and Switch B changing from Down to Up is as follows:

1. The optical module laser of Switch A is still working.2. Switch B receives optical signals of Switch A immediately after the fiber link is

recovered.3. The LOS on the interface of Switch B is cleared, and the interface becomes Up and

sends signals.4. Switch A receives signals of Switch B.5. The LOS on the interface of Switch A is cleared, the interface becomes Up, and data

communication is recovered.

After ALS is enabled on an interface, the communication recovery speed on the interface isreduced. Packets are discarded if traffic is transmitted on the interface.

9.3 Configuring ALSConfiguring ALS of the laser of an optical module in the interface view provides securityprotection and saves energy.

9.3.1 Establishing the Configuration TaskBefore configuring ALS, familiarize yourself with the applicable environment, complete thepre-configuration tasks, and obtain the required data. This helps you complete the configurationtask quickly and accurately.

9.3.2 Enabling ALS on an InterfaceThe ALS configuration takes effect only after ALS is enabled on an interface.

9.3.3 (Optional) Setting the Restart Mode of the Laser



9-3

The laser can work in automatic restart mode or manual restart mode. By default, the laser worksin automatic restart mode.

9.3.4 (Optional) Starting the Laser ManuallyWhen the laser works in automatic restart mode, you need to manually open the laser so that thelaser sends one pulse.

9.3.5 (Optional) Setting the ALS Pulse Interval and Width of the LaserYou can set the proper laser pulse interval and width to ensure energy conservation and emissiondeduction and timely detection of fiber link recovery.

9.3.6 Checking the ConfigurationAfter ALS is configured, you can the ALS configuration on a specified interface or in a specifiedslot, including the ALS status, laser status, ALS restart mode, and ALS pulse interval and width.

9.3.1 Establishing the Configuration TaskBefore configuring ALS, familiarize yourself with the applicable environment, complete thepre-configuration tasks, and obtain the required data. This helps you complete the configurationtask quickly and accurately.


The S5300 controls the laser of an optical module by detecting the LOS on the optical interface;thus, the S5300 provides security protection and saves energy.

According to the actual networking requirements, after ALS is enabled, you can:

l Set the restart mode of the laser of an optical module through a command.

l Set the ALS pulse interval and width of the laser of an optical module through commands.

l View the ALS configuration on interfaces of different optical modules through commands.


Before configuring ALS, complete the following task:

Ensure that the S5300 has an optical module.

Data Preparation

To configure ALS, you need the following data.

No. Data

1 ALS pulse interval of the laserALS pulse width of the laser

9.3.2 Enabling ALS on an InterfaceThe ALS configuration takes effect only after ALS is enabled on an interface.




Issue 03 (2011-01-30)

ContextThe constraints on ALS are as follows:

l Only optical interfaces support ALS. Electrical interfaces do not support ALS.– When optical interfaces transmit services undirectionally, they do not support ALS.– The hardware must provide support for the software to detect the LOS on an optical

interface and control the laser on an interface.l The link aggregation group does not support ALS.

Procedure





Step 3 Run:als enable

ALS is enabled on the interface.

By default, ALS is disabled on an interface.

----End

9.3.3 (Optional) Setting the Restart Mode of the LaserThe laser can work in automatic restart mode or manual restart mode. By default, the laser worksin automatic restart mode.

PrerequisiteALS is enabled on the interface.

ContextIf the laser of an optical module works in automatic restart mode, the laser starts automaticallyat ALS pulse intervals. If the laser of an optical module is set to work in manual restart mode,you must start the laser manually. Then the laser sends a pulse.

If the fiber link recovery is detected in time, you can use the manual restart mode so that thelaser can send pulses immediately. Therefore, data communication can be recovered rapidly.

By default, the laser works in automatic restart mode after ALS is enabled on all the interfaces.

Procedure




9-5




Step 3 Run:als restart mode manual

The restart mode of the laser is set to manual.

The ALS pulse width of the interface in manual restart mode is the same as that in automaticrestart mode.

----End

9.3.4 (Optional) Starting the Laser ManuallyWhen the laser works in automatic restart mode, you need to manually open the laser so that thelaser sends one pulse.

Prerequisite

The interface is enabled with ALS and works in manual restart mode.

Context

When an interface detects the LOS, the laser of the optical module stops sending pulses. If theals restart command is not used, the laser will not be restarted. If the interface still detects theLOS after the laser is started manually, the laser is stopped again. If the interface detects thatthe LOS is cleared, the laser of an optical module sends pulses and data communication isrecovered.

Procedure





Step 3 Run:als restart

The laser of an optical module is started manually. Then the laser sends a pulse.

----End




Issue 03 (2011-01-30)

9.3.5 (Optional) Setting the ALS Pulse Interval and Width of theLaser

You can set the proper laser pulse interval and width to ensure energy conservation and emissiondeduction and timely detection of fiber link recovery.

Prerequisite

The interface is enabled with ALS and works in automatic restart mode.

Context

The ALS pulse width refers to the duration in which a laser sends pulses; the ALS pulse intervalrefers to the period between rising edges of pulses. A smaller pulse width and a greater pulseinterval saves more energy but reduces the speed of fiber link recovery.

Procedure





Step 3 Run:als restart pulse-interval pulse-interval

The ALS pulse interval of the laser on the interface is set.

By default, the ALS pulse interval is 100s.

Step 4 Run:als restart pulse-width pulse-width

The ALS pulse width of the laser on the interface is set.

By default, the ALS pulse width is 2s.

----End

9.3.6 Checking the ConfigurationAfter ALS is configured, you can the ALS configuration on a specified interface or in a specifiedslot, including the ALS status, laser status, ALS restart mode, and ALS pulse interval and width.

Prerequisite

The ALS configurations are complete on the S5300.



9-7

Procedurel Run the display als configuration slot slot-id command to view the ALS configurations

of member switches.

l Run the display als configuration interface interface-type interface-number command tocheck the ALS configuration on the specified interface.

----End

9.4 Configuration ExamplesThis section provides a configuration example of ALS.

9.4.1 Example for Configuring ALSThrough the ALS function, a laser can automatically stop sending pulses when a link is faultyand recover pulse transmission after the link is recovered.

9.4.1 Example for Configuring ALSThrough the ALS function, a laser can automatically stop sending pulses when a link is faultyand recover pulse transmission after the link is recovered.


As shown in Figure 9-3, the LPUs that support ALS are installed in slot 1 of Switch A andSwitch B, GE 0/0/1 of Switch A and Switch B are connected through a fiber.

When data transmission is interrupted by faults occurred on the fiber link, if the laser of theoptical module sends pulses continuously, the energy is wasted and potential risks are caused.After ALS is enabled on both interfaces of the fiber link, the laser stops sending pulses if a faultoccurs on the fiber link. If the faulty link is recovered, the laser starts to send pulses.

Figure 9-3 ALS application

GE0/0/1 GE0/0/1

SwitchA SwitchB



1. Enable ALS on GE 0/0/1 on Switch A and Switch B.

2. Configure the lasers of GE 0/0/1 on Switch A and Switch B to work in automatic restartmode.

3. Set the ALS pulse intervals and widths of the lasers of GE 0/0/1 on Switch A and SwitchB.




Issue 03 (2011-01-30)

Data Preparation

To complete the configuration, you need the following data:

l ALS pulse interval and width of the laser of the optical module on GE 0/0/1 of Switch A

l ALS pulse interval and width of the laser of the optical module on GE 0/0/1 of Switch B

Procedure

Step 1 Enable ALS on GE 0/0/1 of Switch A, configure the laser of the interface to work in automaticrestart mode, and set the ALS pulse interval and width to 200s and 3s.

# Enable ALS.

<SwitchA> system-view[SwitchA] interface gigabitethernet 0/0/1[SwitchA-GigabitEthernet0/0/1] als enable

# Set the ALS pulse interval and width of the laser.

[SwitchA-GigabitEthernet0/0/1] undo als restart mode manual[SwitchA-GigabitEthernet0/0/1] als restart pulse-interval 200[SwitchA-GigabitEthernet0/0/1] als restart pulse-width 3

Step 2 Enable ALS on GE 0/0/1 of Switch B, configure the laser of the interface to work in automaticrestart mode, and set the ALS pulse interval and width to 200s and 3s.

# Enable ALS.

<SwitchB> system-view[SwitchB] interface gigabitethernet 0/0/1[SwitchB-GigabitEthernet0/0/1] als enable

# Set the ALS pulse interval and width of the laser.

[SwitchA-GigabitEthernet0/0/1] undo als restart mode manual[SwitchB-GigabitEthernet0/0/1] als restart pulse-interval 200[SwitchB-GigabitEthernet0/0/1] als restart pulse-width 3

Step 3 Verify the configuration.

# Run the display als configuration interface interface-type interface-number command onSwitch A and Switch B, and you can view the ALS configuration.

<SwitchA> display als configuration interface gigabitethernet0/0/1

-------------------------------------------------------------------------------Interface ALS Laser Restart Interval(s) Width(s) Status Status Mode-------------------------------------------------------------------------------GigabitEthernet0/0/1 Enable Off Auto 200 3-------------------------------------------------------------------------------<SwitchB> display als configuration interface gigabitethernet0/0/1

-------------------------------------------------------------------------------Interface ALS Laser Restart Interval(s) Width(s) Status Status Mode-------------------------------------------------------------------------------GigabitEthernet0/0/1 Enable Off Auto 200 3-------------------------------------------------------------------------------

----End



9-9

Configuration Filesl Configuration file of Switch A

# sysname SwitchA#interface GigabitEthernet0/0/1 als enable als restart pulse-interval 200 als restart pulse-width 3#return

l Configuration file of Switch B# sysname SwitchB#interface GigabitEthernet0/0/1 als enable als restart pulse-interval 200 als restart pulse-width 3#return




Issue 03 (2011-01-30)

10 Restarting and Resetting

About This Chapter

This chapter introduces the basics of the BootROM software and the Versatile Routing Platform(VRP) system software, and describes how to restart the S5300.

10.1 IntroductionThis section introduces the required knowledge in restarting and resetting the S5300.

10.2 Restarting the S5300 ImmediatelyThis section describes how to restart the S5300 immediately.

10.3 Restarting the S5300 at a Fixed TimeThis section describes how to restart the S5300 at a fixed time.

Quidway S5300 Series Ethernet SwitchesConfiguration Guide - Device Management 10 Restarting and Resetting


10-1

10.1 IntroductionThis section introduces the required knowledge in restarting and resetting the S5300.

10.1.1 Process of Starting the S5300

10.1.2 Process of Starting the BootROM

10.1.1 Process of Starting the S5300

The software of the S5300 consists of the BootROM and the VRP. After the S5300 is poweredon, the BootROM and the VRP start the system in turn as shown in Figure 10-1.

Figure 10-1 Process of starting the S5300

Start

BootROM starts

Yes

No

VRP starts

End

Quit the BootROM menu

Enter thecommand line

interface

Enter the BootROMmenu

Upgrade the VRP

Press Ctrl+B

The advanced BootROM starts the VRP.

10.1.2 Process of Starting the BootROMNOTETo check the BootROM startup process, you need to connect the Console port of the switch to a terminalby using a serial port cable.

The BootROM compares the current configuration with the configuration file. If they are thesame, the BootROM asks you whether to reboot the system. The message is as follows:

10 Restarting and ResettingQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

Info: The system is now comparing the configuration, please wait.System will reboot! Continue?[Y/N]:y

BIOS LOADING ...Copyright (c) 2008-2010 HUAWEI TECH CO., LTD.CX22EFFE (Ver124, Jun 9 2010, 17:41:46)

Press Ctrl+B to enter BOOTROM menu ... 0

Press Ctrl+B within two seconds. The system prompts you to enter the password of the advancedBootROM menu as follows:

The default password is huawei.password: BOOTROM MENU

1. Boot with default mode 2. Enter serial submenu 3. Enter startup submenu 4. Enter ethernet submenu 5. Enter filesystem submenu 6. Modify BOOTROM password 7. RebootEnter your choice(1-7):

In the advanced BootROM menu, you can choose to upgrade the VRP or specify the VRP versionto be loaded when the S5300 is started.

The BootROM initializes the serial interface and the console interface, decompresses the logicalfiles on the logical chip and the VRP, and then starts the VRP. The terminal displays informationas follows:

Decompressing Image file ... done

PPI DEV SysInit......OKHard system init.................OKBegin to start the system, please waiting ......

VOS VFS init.....................OKVOS monitor init.................OKCFM init advance.................OKPAT init ........................OKVOS VFS init hind ...............OK

VRP_Root begin...VRP_InitializeTask begin...Init the Device Link.............OKCFG_PlaneInit begin..............OKCFM_Init begin...................OKCLI_CmdInit begin................OKVRP_RegestAllLINKCmd begin.......OKcreate task begin................task init begin...

Recover configuration...OK!done

Press ENTER to get started.

When the terminal displays the preceding information, it indicates that the starting of the VRPis complete. Press Enter to enter a Command Line Interface (CLI).

10.2 Restarting the S5300 ImmediatelyThis section describes how to restart the S5300 immediately.



10-3

10.2.1 Restarting the S5300 Immediately Through Command Lines

10.2.2 Restarting the S5300 Through the Power Button on the S5300

10.2.1 Restarting the S5300 Immediately Through Command Lines

Context

CAUTIONThe reboot command can paralyze the network for a while. Therefore, run the reboot commandwith caution.

Before restarting the S5300, check whether to save the configuration file and whether the filecontents are correct. For details on saving the configuration file, refer to the Configuration Guide- Basic Configuration.

Procedure

Step 1 Run:reboot

The S5300 is restarted immediately.

----End

10.2.2 Restarting the S5300 Through the Power Button on the S5300

Context

CAUTIONThe action can paralyze the network for a while. Therefore, perform this action with caution.

Before restarting the S5300, check whether to save the configuration file and whether the filecontents are correct. For details on saving the configuration file, see the Quidway S5300Series Ethernet Switches Configuration Guide - Basic Configuration.

Procedure

Step 1 Press the power button on the S5300 to power off the running S5300.

Step 2 Press the power button on the S5300 again to restart the S5300.

----End

10 Restarting and ResettingQuidway S5300 Series Ethernet Switches



Issue 03 (2011-01-30)

10.3 Restarting the S5300 at a Fixed TimeThis section describes how to restart the S5300 at a fixed time.

Procedure

Step 1 Run:schedule reboot { at time | delay interval [ force ] }

The function of restarting the S5300 at a fixed time is enabled.

The S5300 does not support the function of restarting the S5300 at a fixed time by default.

----End



10-5

Documents

Configuration Guide - Device Management(V100R005C01_03)