CloudEngine 6800&5800 V100R001C00 Configuration Guide - Device Management 04.pdf

CloudEngine 6800&5800 Series SwitchesV100R001C00

Configuration Guide - DeviceManagement

Issue 04

Date 2013-07-10

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 a warranty of any kind, express or implied.

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://enterprise.huawei.com

Issue 04 (2013-07-10) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://enterprise.huawei.com

About This Document

Intended AudienceThis document provides the basic concepts, configuration procedures, and configurationexamples in different application scenarios of the device management feature supported by thedevice.

This document is intended for:

l Data configuration engineersl Commissioning engineersl Network monitoring engineersl 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 or medium level of riskwhich, if not avoided, could result in death or serious injury.

WARNINGIndicates a hazard with a low level of risk which, if notavoided, could result in minor or moderate injury.

CAUTIONIndicates a potentially hazardous situation that, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.

TIP Provides a tip that may help you solve a problem or save time.

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

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management About This Document


ii

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. You can select one or several items, or selectno item.

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

# A line starting with the # sign is comments.

Interface Numbering ConventionsInterface numbers used in this manual are examples. In device configuration, use the existinginterface numbers on devices.

Change HistoryChanges between document issues are cumulative. Therefore, the latest document versioncontains all updates made to previous versions.

Changes in Issue 04 (2013-07-10)

This version has the following updates:

The following information is modified:

l 8.2 iStack Features Supported by the Device

l 8.5.4 Configuring a Stack Port



iii

Changes in Issue 03 (2013-05-10)This version has the following updates:

The following information is added:

l 4.4.5 (Optional) Enabling the Output of the Statistics About Repeatedly GeneratedLogs

Changes in Issue 02 (2013-03-15)This version has the following updates:

The following information is added:

l 2.4 Enabling Master/Slave Switchoverl 6.4 (Optional) Disabling the USB-based Deployment Function

Changes in Issue 01 (2012-12-31)Initial commercial release.



iv

Contents

About This Document.....................................................................................................................ii

1 Displaying the Device Status......................................................................................................11.1 Displaying Information About the device......................................................................................................................31.2 Displaying Versions.......................................................................................................................................................31.3 Displaying Power Supply Information...........................................................................................................................31.4 Displaying the Power......................................................................................................................................................41.5 Displaying the Temperature...........................................................................................................................................41.6 Displaying the Fan Status...............................................................................................................................................41.7 Displaying CPU Usage...................................................................................................................................................51.8 Displaying Memory Usage.............................................................................................................................................51.9 Displaying Interface Status.............................................................................................................................................61.10 Displaying Electronic Labels........................................................................................................................................71.11 Displaying System MAC Address................................................................................................................................71.12 Displaying the Current Configuration..........................................................................................................................71.13 Displaying Diagnostic Information..............................................................................................................................81.14 Displaying Health Status..............................................................................................................................................81.15 Displaying Information About a Transceiver on the Interface.....................................................................................9

2 Hardware Management..............................................................................................................102.1 Hardware Management Overview................................................................................................................................112.2 Backing Up Electronic Labels......................................................................................................................................112.3 Resetting a Device........................................................................................................................................................112.4 Enabling Master/Slave Switchover..............................................................................................................................122.5 Configuring the CPU Usage Alarm Threshold.............................................................................................................132.6 Configuring the Memory Usage Alarm Threshold.......................................................................................................132.7 Configuring the Interval for Updating Power Consumption Data...............................................................................142.8 Configuring the System Resource Mode......................................................................................................................15

3 Energy-Saving Management.....................................................................................................173.1 Energy-saving Management Overview........................................................................................................................183.2 Energy-saving Management Features Supported by the Device..................................................................................183.3 Configuring ALS..........................................................................................................................................................193.3.1 Enabling ALS on an Interface...................................................................................................................................193.3.2 (Optional) Setting the Restart Mode of the Laser......................................................................................................20

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management Contents


v

3.3.3 (Optional) Setting the ALS Pulse Interval and Width of the Laser...........................................................................213.3.4 Checking the Configuration.......................................................................................................................................223.4 Configuring the EEE Function.....................................................................................................................................223.5 Configuring an Energy-Saving Mode...........................................................................................................................233.6 Configuration Examples...............................................................................................................................................243.6.1 Example for Configuring ALS..................................................................................................................................24

4 Information Center Configuration...........................................................................................274.1 Introduction to the Information Center.........................................................................................................................284.2 Information Center Features Supported by the Device................................................................................................284.3 Default Configuration...................................................................................................................................................284.4 Configuring Log Output...............................................................................................................................................304.4.1 Enabling the Information Center...............................................................................................................................324.4.2 (Optional) Naming an Information Channel.............................................................................................................324.4.3 (Optional) Configuring Log Filtering........................................................................................................................334.4.4 (Optional) Setting the Timestamp Format of Logs ..................................................................................................334.4.5 (Optional) Enabling the Output of the Statistics About Repeatedly Generated Logs...............................................344.4.6 Configuring the Device to Output Logs to the Log Buffer.......................................................................................354.4.7 Configuring the Device to Output Logs to a Log File...............................................................................................354.4.8 Configuring the Device to Output Logs to the Console............................................................................................364.4.9 Configuring the Device to Output Logs to a Terminal..............................................................................................374.4.10 Configuring the Device to Output Logs to a Log Host...........................................................................................384.4.11 Checking the Configuration.....................................................................................................................................394.5 Configuring Trap Output..............................................................................................................................................394.5.1 Enabling the Information Center...............................................................................................................................414.5.2 (Optional) Naming an Information Channel.............................................................................................................424.5.3 (Optional) Configuring Trap Filtering.......................................................................................................................434.5.4 (Optional) Setting the Timestamp Format of Traps..................................................................................................434.5.5 Configuring the Device to Output Traps to the Trap Buffer.....................................................................................444.5.6 Configuring the Device to Output Traps to a Log File..............................................................................................444.5.7 Configuring the Device to Output Traps to the Console...........................................................................................454.5.8 Configuring the Device to Output Traps to a Terminal.............................................................................................464.5.9 Configuring the Device to Output Traps to a Log Host............................................................................................474.5.10 Configuring the Device to Output Traps to an SNMP Agent..................................................................................484.5.11 Checking the Configuration.....................................................................................................................................494.6 Configuring Debugging Message Output.....................................................................................................................494.6.1 Enabling the Information Center...............................................................................................................................514.6.2 (Optional) Naming an Information Channel.............................................................................................................514.6.3 (Optional) Setting the Timestamp Format of Debugging Messages.........................................................................524.6.4 Configuring the Device to Output Debugging Messages to the Console..................................................................524.6.5 Configuring the Device to Output Debugging Messages to the Terminal................................................................534.6.6 Checking the Configuration.......................................................................................................................................544.7 Maintaining the Information Center.............................................................................................................................55



vi

4.7.1 Clearing Statistics......................................................................................................................................................554.7.2 Monitoring the Information Center...........................................................................................................................554.8 Configuration Examples...............................................................................................................................................554.8.1 Example for Outputting Logs to the Log File...........................................................................................................564.8.2 Example for Outputting Logs to a Log Host.............................................................................................................584.8.3 Example for Outputting Traps to the SNMP Agent..................................................................................................604.8.4 Example for Outputting Debugging Messages to the Console..................................................................................62

5 Fault Management Configuration............................................................................................645.1 Introduction to Fault Management...............................................................................................................................655.2 Default Configuration...................................................................................................................................................655.3 Configuring Alarm Management..................................................................................................................................655.3.1 Setting the Alarm Severity........................................................................................................................................655.3.2 Configuring the Alarm Reporting Delay Function....................................................................................................665.3.3 Checking the Configuration.......................................................................................................................................675.4 Maintenance..................................................................................................................................................................675.4.1 Clearing Alarms.........................................................................................................................................................685.4.2 Monitoring Alarms....................................................................................................................................................685.5 Configuration Examples...............................................................................................................................................695.5.1 Example for Configuring Alarm Management..........................................................................................................69

6 USB-based Deployment Configuration..................................................................................716.1 USB-based Deployment Overview..............................................................................................................................726.2 Making an Index File....................................................................................................................................................726.3 Configuring USB-based Deployment...........................................................................................................................766.4 (Optional) Disabling the USB-based Deployment Function........................................................................................786.5 Configuration Example.................................................................................................................................................786.5.1 Example for Configuring USB-based Deployment...................................................................................................78

7 Mirroring Configuration............................................................................................................817.1 Packet Mirroring Overview..........................................................................................................................................827.2 Packet Mirroring Features Supported by the Device....................................................................................................827.3 Configuring Local Port Mirroring................................................................................................................................857.3.1 Configuring a Local Observing Port.........................................................................................................................857.3.2 Configuring a Mirrored Port......................................................................................................................................867.3.3 Checking the Configuration.......................................................................................................................................867.4 Configuring Remote Port Mirroring.............................................................................................................................877.4.1 Configuring a Remote Observing Port......................................................................................................................877.4.2 Configuring a Mirrored Port......................................................................................................................................887.4.3 Checking the Configuration.......................................................................................................................................887.5 Configuring Local Traffic Mirroring............................................................................................................................897.5.1 Configuring a Local Observing Port.........................................................................................................................897.5.2 Configuring a Traffic Classifier................................................................................................................................897.5.3 Configuring a Traffic Behavior.................................................................................................................................89



vii

7.5.4 Configuring a Traffic Policy......................................................................................................................................907.5.5 Applying a Traffic Policy..........................................................................................................................................917.5.6 Checking the Configuration.......................................................................................................................................917.6 Configuring Remote Traffic Mirroring........................................................................................................................917.6.1 Configuring a Remote Observing Port......................................................................................................................917.6.2 Configuring a Traffic Classifier................................................................................................................................927.6.3 Configuring a Traffic Behavior.................................................................................................................................927.6.4 Configuring a Traffic Policy......................................................................................................................................937.6.5 Applying a Traffic Policy..........................................................................................................................................937.6.6 Checking the Configuration.......................................................................................................................................937.7 Configuration Examples...............................................................................................................................................947.7.1 Example for Configuring Local Port Mirroring........................................................................................................947.7.2 Example for Configuring Layer 2 Remote Port Mirroring........................................................................................957.7.3 Example for Configuring Layer 3 Remote Port Mirroring........................................................................................987.7.4 Example for Configuring Local Traffic Mirroring..................................................................................................100

8 iStack Configuration.................................................................................................................1038.1 iStack Overview.........................................................................................................................................................1048.2 iStack Features Supported by the Device...................................................................................................................1058.3 Configuration Notes...................................................................................................................................................1128.4 Default Configuration.................................................................................................................................................1148.5 Configuring a Stack....................................................................................................................................................1148.5.1 Configuring the Stack Domain ID...........................................................................................................................1158.5.2 (Optional) Configuring the Stack ID.......................................................................................................................1168.5.3 (Optional) Configuring the Stack Priority...............................................................................................................1168.5.4 Configuring a Stack Port.........................................................................................................................................1178.5.5 Restarting the Device...............................................................................................................................................1208.5.6 (Optional) Configuring the Delay in Stack MAC Address Switchover..................................................................1208.5.7 (Optional) Starting Fast Upgrade of Switches in a Stack........................................................................................1218.5.8 Checking the Configuration.....................................................................................................................................1218.6 (Optional) Configuring Dual-active Detection...........................................................................................................1228.6.1 Configuring the DAD Mode....................................................................................................................................1228.6.2 (Optional) Excluding Ports from Shutdown............................................................................................................1238.6.3 (Optional) Restoring Blocked Ports........................................................................................................................1248.6.4 Checking the Configuration.....................................................................................................................................1248.7 Configuration Examples.............................................................................................................................................1258.7.1 Example for Configuring a Stack with a Chain Topology......................................................................................1258.7.2 Example for Configuring a Stack with a Ring Topology........................................................................................1288.7.3 Example for Configuring DAD in Direct Mode......................................................................................................1328.7.4 Example for Configuring DAD in Relay Mode......................................................................................................134



viii

1 Displaying the Device Status

About This Chapter

This chapter describes the functions of display commands and how to use the display commandsto view the device running status.

1.1 Displaying Information About the deviceYou can use the display commands to view component information about the device.

1.2 Displaying VersionsYou can use the display commands to view version information about the device.

1.3 Displaying Power Supply InformationYou can use the display commands to view power supply information about the device.

1.4 Displaying the PowerYou can use the display commands to view the power of the device.

1.5 Displaying the TemperatureYou can use the display commands to view the temperature of the device.

1.6 Displaying the Fan StatusThis section describes how to check the fan status on a device.

1.7 Displaying CPU UsageYou can use the display commands to view CPU usage statistics and configurations.

1.8 Displaying Memory UsageYou can use the display commands to view memory usage statistics and threshold.

1.9 Displaying Interface StatusYou can use the display commands to view the configuration and status of a specified interface.

1.10 Displaying Electronic LabelsYou can use the display commands to view electronic labels.

1.11 Displaying System MAC AddressYou can run the display commands to view the system MAC address.

1.12 Displaying the Current ConfigurationYou can use the display commands to view the current configuration of the device.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 1 Displaying the Device Status


1

1.13 Displaying Diagnostic InformationYou can use the display commands to view diagnostic information for fault location.

1.14 Displaying Health StatusYou can use the display commands to view the health status of the device.

1.15 Displaying Information About a Transceiver on the InterfaceYou can use the display commands to view information about the optical module of an interface,including the specifications, manufacturer, and alarm information about the optical module.



2

1.1 Displaying Information About the deviceYou can use the display commands to view component information about the device.

ContextWhen a fault occurs on the device, you can view device information to check whether the deviceis working properly.

Procedurel Run

display device [ slot slot-id ]

The component information and device status are displayed.

----End

1.2 Displaying VersionsYou can use the display commands to view version information about the device.

ContextYou can view version information about the device to determine whether the device needs to beupgraded or whether the upgrade succeeds.

Procedurel Run:

display version [ slot slot-id ]

The version information of the device is displayed.

----End

1.3 Displaying Power Supply InformationYou can use the display commands to view power supply information about the device.

ContextWhen a power supply fault occurs on the device, you can run the following command to viewinformation about power status.

Procedurel Run:

display device power

The information about power status is displayed.

----End



3

1.4 Displaying the PowerYou can use the display commands to view the power of the device.

ContextTo learn about the power of the device, check the power information.

Procedurel Run:

display device power system

The information about the power of the device is displayed.

----End

1.5 Displaying the TemperatureYou can use the display commands to view the temperature of the device.

ContextA high or low temperature may damage the hardware. To learn about the temperature of thedevice, use the display commands to view the temperature.

Procedurel Run:

display device temperature { all | slot slot-id }

The temperature of the device is displayed.

----End

1.6 Displaying the Fan StatusThis section describes how to check the fan status on a device.

ContextDevices can run properly when fans are working properly. Ineffective heat dissipation causes adevice to overheat and may damage the device hardware.

Procedurel Run:

display device fan

The fan status is displayed.

----End



4

1.7 Displaying CPU UsageYou can use the display commands to view CPU usage statistics and configurations.

ContextCPU usage is an important index to evaluate device performance. A high CPU usage will causeservice faults, for example, BGP route flapping, frequent VRRP active/standby switchover, andeven failed device login. You can use the display commands to view CPU usage statistics andconfigurations to check whether devices are working properly.

CPU usage configurations include the CPU usage alarm threshold and recovery threshold.

l When CPU usage reaches the alarm threshold, the system generates a CPU usage alarm.l When CPU usage falls within the recovery threshold, the system generates a clear alarm.

Procedurel Run:

display cpu [ slot slot-id ]

The CPU usage statistics is displayed.l Run:

display cpu monitor { all | history [ slot slot-id ] | slot slot-id }

The CPU overloading status is displayed.l Run:

display cpu threshold [ slot slot-id ]

The CPU usage configurations are displayed.

----End

1.8 Displaying Memory UsageYou can use the display commands to view memory usage statistics and threshold.

ContextMemory usage is an important index to evaluate device performance. A high memory usage willcause service faults. You can use the display commands to view memory usage to check whetherdevices are working properly.

You can view the memory usage alarm threshold to learn about the conditions for triggeringalarms.l When memory usage reaches the alarm threshold, the system generates an alarm.l When memory usage falls within the alarm threshold, the system generates a clear alarm.

Procedurel Run:

display memory [ slot slot-id ]



5

The memory usage statistics is displayed.l Run:

display memory threshold [ slot slot-id ]

The memory usage threshold is displayed.

----End

1.9 Displaying Interface StatusYou can use the display commands to view the configuration and status of a specified interface.

ContextView the configuration of an interface.

l After performing operations in a interface view, you can view the configuration about thisinterface to check whether the configuration is correct.

View the status of an interface.

l You can view the status of an interface to monitor the interface or locate interface faults.

Procedurel View the configuration of a specified interface.

1. Run:system-viewThe system view is displayed.

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

3. Run:display thisThe configuration of the current interface is displayed.

l View the status of an interface using either of the following methods.

Method 1:

1. Run:display interface [ interface-type [ interface-number ] ]The status of the specified interface is displayed.

Method 2:



3. Run:



6

display this interface

The status of the specified interface is displayed.

----End

1.10 Displaying Electronic LabelsYou can use the display commands to view electronic labels.

ContextElectronic labels identify the hardware of devices.

Procedurel Run:

display device elabel [ slot slot-id [ card card-id ] ] [ brief ]

The electronic labels of the device is displayed.

----End

1.11 Displaying System MAC AddressYou can run the display commands to view the system MAC address.

ContextYou can run the following commands to view the current system MAC address.

Procedurel Run:

display system mac-address

The system MAC address is displayed.

----End

1.12 Displaying the Current ConfigurationYou can use the display commands to view the current configuration of the device.

ContextTo learn about services currently running on the device, run the following command to view thedevice configuration.

Procedurel Run:

display current-configuration



7

The information of the current configuration is displayed.

----End

1.13 Displaying Diagnostic InformationYou can use the display commands to view diagnostic information for fault location.

Context

When a fault occurs in the system or during routine maintenance, you can run the displaycommands to collect the running information about all modules.

CAUTIONViewing diagnostic information helps locate faults but may affect system performance. Forexample, CPU usage may become high. Therefore, do not view diagnostic information whenthe system is running properly.

Procedurel Run:

display diagnostic-information [ [ module-name ] &<1-8> [ slot slot-id ] | file-name ]

The diagnostic information is displayed.

----End

1.14 Displaying Health StatusYou can use the display commands to view the health status of the device.

Context

To learn about the device temperature, power supply, fan information, CPU usage, memoryusage, and storage medium, use the fallowing command to view the health status.

Procedurel Run:

display health

The health status of the device is displayed.

----End



8

1.15 Displaying Information About a Transceiver on theInterface

You can use the display commands to view information about the optical module of an interface,including the specifications, manufacturer, and alarm information about the optical module.

ContextWhen the optical module of an interface fails, run the following commands to view informationabout the optical module.

Procedurel Run:

display interface [ interface-type interface-number | slot slot-id ] transceiver [ verbose ]

Information about a transceiver on the interface is displayed.

----End



9

2 Hardware Management

About This Chapter

Scientific hardware management reduces the operations performed on hardware resources,including inserting, removing, installing and uninstalling the hardware, and improves hardwareresource reliability.

2.1 Hardware Management OverviewScientific hardware management allows you to use commands to operate and manage hardwareresources, for example, reset devices, configure master/slave switchover the hardware resources.

2.2 Backing Up Electronic LabelsYou can back up electronic labels to improve network maintenance efficiency.

2.3 Resetting a DeviceWhen a device fails to be upgraded or cannot work properly, you may need to reset the device.

2.4 Enabling Master/Slave SwitchoverTo implement backup between master and standby switches in a stack with multiple switches,enable the master/slave switchover function to allow the original standby switch to become thenew master switch.

2.5 Configuring the CPU Usage Alarm ThresholdYou can configure the CPU usage alarm threshold to monitor CPU usage.

2.6 Configuring the Memory Usage Alarm ThresholdYou can configure the memory usage alarm threshold to monitor memory usage.

2.7 Configuring the Interval for Updating Power Consumption DataYou can configure the interval for updating power consumption data to view power consumptionof the device during a period.

2.8 Configuring the System Resource ModeYou can configure the system resource mode to adjust the allocation of hardware resources.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 2 Hardware Management


10

2.1 Hardware Management OverviewScientific hardware management allows you to use commands to operate and manage hardwareresources, for example, reset devices, configure master/slave switchover the hardware resources.

Scientific hardware management reduces the operations performed on hardware resources,including inserting, removing, installing and uninstalling the hardware, and improves hardwareresource reliability.

2.2 Backing Up Electronic LabelsYou can back up electronic labels to improve network maintenance efficiency.

ContextElectronic labels can help locate network faults and replace hardware in batches. Therefore,backing up electronic labels is a must.l When a network fault occurs, you can rapidly learn about hardware information using

electronic labels, which improves hardware maintenance efficiency. In addition, you canefficiently analyze and trace the defects in the hardware by analyzing and collectingelectronic labels statistics on the faulty hardware.

l Before replacing hardware in batches, you can use the electronic labels recorded in thearchive systems of customers' devices to obtain accurate hardware deployment information.Then you can evaluate the impact of hardware replacement and define policies to efficientlyreplace hardware in batches.

Electronic labels can be backed up to the FTP server, TFTP server, or local flash memory. Beforebacking up electronic labels to the FTP or TFTP server, ensure that there are reachable routesbetween the device and FTP server (or TFTP server).

Procedurel Run:

backup device elabel [ slot slot-id [ card card-id ] ] filename

Electronic labels are backed up to the flash memory.l Run:

backup device elabel [ slot slot-id [ card card-id ] ] ftp ftp-server-address filename username

Electronic labels are backed up to the FTP server.l Run:

backup device elabel [ slot slot-id [ card card-id ] ] tftp tftp-server-address filename

Electronic labels are backed up to the TFTP server.

----End

2.3 Resetting a DeviceWhen a device fails to be upgraded or cannot work properly, you may need to reset the device.



11

Context

NOTE

Resetting a device will interrupt services on the device. When a device is not working properly, to preventservices from being affected, rectify the fault rather than reset the device.

Procedure

Step 1 (Optional) Run:display device [ slot slot-id ]

The device status is displayed.

Step 2 Run:reset slot slot-id

The device is reset.

----End

2.4 Enabling Master/Slave SwitchoverTo implement backup between master and standby switches in a stack with multiple switches,enable the master/slave switchover function to allow the original standby switch to become thenew master switch.

ContextIn a stack containing multiple switches, you can manually perform a switchover between themaster and standby switches during software upgrade or system maintenance. After the master/slave switchover is complete, the original master switch restarts and joins the stack, and theoriginal standby switch becomes the new master switch.

Before a master/slave switchover, check whether the stack is ready for a switchover. The master/slave switchover can be performed only when the stack meets switchover requirements.

Procedure

Step 1 (Optional) Run:display switchover state

Information about master and slave switchover is displayed, which helps check whether the stackmeets switchover requirements.

You can perform a master/slave switchover only when the Switchover State field displays Ready.

Step 2 Run:system-view

The system view is displayed.

Step 3 Run:slave switchover enable

Master/slave device switchover is enabled.



12

By default, master/slave switchover is enabled.

Step 4 Run:slave switchover

A master/slave switchover is performed.

----End

2.5 Configuring the CPU Usage Alarm ThresholdYou can configure the CPU usage alarm threshold to monitor CPU usage.

ContextWhen the system has a large number of routes, many CPU resources will be used. This degradessystem performance and results in the delay in processing data or causes a high packet loss rate.During data processing, if the device can generate an alarm when high CPU usage occurs, youcan effectively monitor CPU usage and optimize system performance to ensure system stability.

l CPU usage alarm thresholdWhen CPU usage reaches this threshold, the system generates an alarm.

l CPU usage alarm recovery thresholdWhen CPU usage falls within this threshold, the system generates a clear alarm.

ProcedureStep 1 (Optional) Run:

display cpu threshold [ slot slot-id ]

The CPU usage configuration is displayed.



Step 3 Run:set cpu threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ]

The CPU usage alarm threshold and CPU usage alarm recovery threshold are set.

By default, the CPU usage alarm threshold is 95% and the CPU usage alarm recovery thresholdis 75%.

Step 4 Run:commit

The configuration is committed.

----End

2.6 Configuring the Memory Usage Alarm ThresholdYou can configure the memory usage alarm threshold to monitor memory usage.



13

Context

Memory usage is an important indicator to evaluate device performance. A high memory usagewill cause service faults. During data processing, if the device can generate an alarm when highmemory usage occurs, you can effectively monitor memory usage and optimize systemperformance to ensure system stability.

l Memory usage alarm thresholdWhen memory usage reaches this threshold, the system generates an alarm.

l Memory usage alarm recovery thresholdWhen memory usage falls within this threshold, the system generates a clear alarm.

Procedure

Step 1 (Optional) Run:display memory threshold [ slot slot-id ]

The memory usage configuration is displayed.



Step 3 Run:set memory threshold threshold-value [ restore restore-threshold-value ] [ slot slot-id ]

The memory usage alarm threshold and memory usage alarm recovery threshold are set.

By default, the memory usage alarm threshold is 95% and the memory usage alarm recoverythreshold is 75%.

Step 4 Run:commit


----End

2.7 Configuring the Interval for Updating PowerConsumption Data

You can configure the interval for updating power consumption data to view power consumptionof the device during a period.

Context

The average power consumption of a device is the average power consumption within a periodof time. To obtain real-time power consumption, set a short interval.

You can use the display device power system command to view power consumption data,including the accumulative power consumption and average power consumption.



14

Procedure

Step 1 (Optional) Run:display device power system

The interval for updating power consumption data is displayed.



Step 3 Run:set device power manage cycle cycle-id

The interval for updating power consumption data is set.

By default, power consumption data is updated at an internal of 1 hour.

Step 4 Run:commit


----End

2.8 Configuring the System Resource ModeYou can configure the system resource mode to adjust the allocation of hardware resources.

Context

Services share chip resources. You can properly allocate chip resources to meet different servicerequirements.

NOTE

Only the CE5850 supports the configuration of the system resource mode.

Procedure



Step 2 (Optional) Run:display system resource

The system resource mode is displayed.

Step 3 Run:system resource { large-mac-table | standard | user-defined }

The system resource mode is set.

By default, the standard system resource mode is used.



15

Step 4 Run:commit


----End



16

3 Energy-Saving Management

About This Chapter

You can configure the energy-saving management function to reduce device power consumptionand save energy.

3.1 Energy-saving Management OverviewAs network scale enlarges, device power consumption increases enterprise operating expense.Energy saving becomes the major concern in network construction. Devices use multiple energy-saving technologies to reduce power consumption.

3.2 Energy-saving Management Features Supported by the DeviceThe device supports energy-saving features such as intelligent fan speed adjustment, EnergyEfficient Ethernet (EEE), and automatic laser shutdown (ALS).

3.3 Configuring ALSThe ALS function on an optical module controls laser sending and saves energy.

3.4 Configuring the EEE FunctionYou can configure the EEE function on the electrical interface to reduce power consumption.

3.5 Configuring an Energy-Saving ModeYou can configure an energy-saving mode for the device to reduce power consumption.

3.6 Configuration ExamplesThis section provides energy-saving management configuration examples including networkingrequirements and configuration roadmap.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 3 Energy-Saving Management


17

3.1 Energy-saving Management OverviewAs network scale enlarges, device power consumption increases enterprise operating expense.Energy saving becomes the major concern in network construction. Devices use multiple energy-saving technologies to reduce power consumption.

3.2 Energy-saving Management Features Supported by theDevice

The device supports energy-saving features such as intelligent fan speed adjustment, EnergyEfficient Ethernet (EEE), and automatic laser shutdown (ALS).

Intelligent Fan Speed AdjustmentThe device adopts the intelligent fan speed adjustment technology to monitor the temperatureof key components. If a sensitive component overheats, the fan speed increases; when thetemperature falls back to its normal range, the fan speed decreases. In this way, the fan moduleenables the device to run in normal temperature and reduces power consumption and noise.

ALSThe automatic laser shutdown (ALS) mechanism controls the pulse of the laser of an opticalmodule by detecting the Loss of Signal (LOS) on an optical interface. The ALS mechanismprotects operators against laser injury and saves energy.

When ALS is disabled, if the optical fiber link fails, data communication is interrupted. However,the optical interface and the laser of an optical module are enabled. If the laser of an opticalmodule still sends pulses after data communication is interrupted, energy is wasted and eyes ofoperators may be hurt.

When ALS is enabled, if the optical fiber link fails, the software automatically disables the laserof an optical module from sending pulses on the optical interface after detecting the LOS on theoptical interface. When the faulty optical fiber link is recovered, the software detects that theLOS of the optical interface is cleared and enables the laser to send pulses.

EEEEnergy Efficient Ethernet (EEE) dynamically adjusts the electrical interface power accordingto network traffic volume.

When the EEE function is not configured on the electrical interface, the system provides powerfor each interface. Even though an interface is idle, it consumes the same power as workinginterfaces. After the EEE function is configured, the system reduces the power on an interfacewhen the interface is idle and restores the power when the interface starts to transmit data. Thisreduces power consumption in the system.

Port DormancyIn port dormancy mode, the physical layer (PHY) chip on the electrical interface enters the lowenergy consumption mode to reduce power consumption. When interfaces are not connected,



18

major data transmission channels of the chip enter the dormancy state to save energy. Wheninterfaces are connected and traffic on the cable is detected, the PHY chip restores to normalworking state.

Shutting Down Idle Circuits and Components

The device shuts down circuits and components based on their usage to save energy. Forexample, when the optical module is unavailable on the interface, the system closes circuits thatare not used. When the optical module is installed, circuits automatically open.

Powering off Redundant Power Modules

The device powers off redundant power modules based on rated power consumption or real-time power consumption. This does not affect system power supply and saves energy. When therated power or real-time power increases, the device automatically powers on redundant powermodules. This ensures stable power supply.

Energy-saving Mode

Besides intelligent fan speed adjustment and ALS, the device saves energy through the energy-saving mode.

The device supports the following energy-saving modes:

l User-defined mode: Users set the energy-saving mode as service requires.

l Standard mode: Default energy saving technologies are used, for example, intelligent fanspeed adjustment, ALS, port dormancy, EEE, and shutting down idle circuits andcomponents.

l Basic mode: The basic energy-saving mode uses technologies supported by the standardmode and allows the device to power off redundant power modules based on rated powerconsumption.

l Deep mode: The deep energy-saving mode uses technologies supported by the standardmode and allows the device to power off redundant power modules based on rated powerconsumption.

NOTE

The device supports only the standard mode.

3.3 Configuring ALSThe ALS function on an optical module controls laser sending and saves energy.

Pre-configuration Tasks

Before configuring ALS, complete the following task:

l Ensuring that the link layer protocol status on the interfaces is Up

3.3.1 Enabling ALS on an Interface



19

ContextThe constraints on ALS are as follows:l Only optical interfaces support ALS. Electrical interfaces do not support ALS.l When optical interfaces transmit services unidirectionally, they do not support ALS.

Procedure



Step 2 Run:interface interface-type interface-number

The interface view is displayed.

Step 3 Run:als enable

ALS is enabled on an interface.

By default, ALS is disabled on an interface.

Step 4 Run:commit


----End

3.3.2 (Optional) Setting the Restart Mode of the Laser

ContextThe laser of an optical module works in automatic restart mode or manual restart mode.l Automatic restart mode: The laser automatically sends a pulse at an interval to detect

whether a link is restored. After the LOS is cleared, the laser sends pulses and datacommunication is recovered.

l Manual restart mode: If the optical fiber link recovers, you must start the laser manually.Then the laser sends a pulse to detect whether the link is recovered.

Procedurel Configure automatic restart mode

1. Run:system-view

The system view is displayed.2. Run:

interface interface-type interface—number




20

3. Run:als restart mode automatic

The laser of the optical module is configured to work in automatic restart mode.By default, a laser works in automatic restart mode.

4. Run:commit

The configuration is committed.l Configure manual restart mode

1. Run:system-view


interface interface-type interface—number

The interface view is displayed.3. Run:

als restart mode manual

The laser of the optical module is configured to work in manual restart mode.4. Run:

commit

The configuration is committed.5. (Optional) Run:

als restart

The laser of the optical module is started manually.

NOTE

In manual restart mode, after the optical fiber link recovers, you must start the laser manually. Thelaser then sends a pulse to detect whether the link is recovered.

----End

3.3.3 (Optional) Setting the ALS Pulse Interval and Width of theLaser

Context

The ALS pulse interval refers to the duration in which a laser sends pulses; the ALS pulse widthrefers to the period between rising edges of pulses.

A smaller pulse width and a greater pulse interval save more energy but the fiber link recoverycannot be detected immediately. You can set a proper laser pulse interval and width to ensureenergy conservation, emission deduction, and timely detection of optical fiber link recovery.

Procedure




21




Step 3 Run:als restart pulse interval pulse-interval

The ALS pulse interval of the laser 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 is set.

By default, the ALS pulse width is 2s.

Step 5 Run:commit


----End

3.3.4 Checking the Configuration

Procedurel Run the display als { all | slot slot-id } command to check ALS configurations on the

device.l Run the display als interface interface-type interface-number command to check ALS

configuration on a specified interface.

----End

3.4 Configuring the EEE FunctionYou can configure the EEE function on the electrical interface to reduce power consumption.

ContextAfter the EEE function is configured, the system reduces the power on an interface when theinterface is idle and restores the power when the interface starts to transmit data. This reducespower consumption in the system.

NOTE

l Only the electrical interface supports the EEE function. The optical interface does not support the EEEfunction.

l This function takes effect only after it is configured on both ends of a link.

l The interface must work in auto-negotiation mode.



22

Procedure



Step 2 Run:interface interface-type interface—number


Step 3 Run:undo negotiation disable

The interface is configured to work in auto-negotiation mode.

Step 4 Run:eee enable

The EEE function is enabled on the interface.

By default, EEE is disabled on an interface.

Step 5 Run:commit


----End

Checking the Configuration

l Run the display this command in a specified interface view to check whether the EEEfunction is enabled on the interface.

3.5 Configuring an Energy-Saving ModeYou can configure an energy-saving mode for the device to reduce power consumption.

Context

The device supports the following energy-saving modes:l User-defined mode: Users set the energy-saving mode as service requires.l Standard mode: Default energy saving technologies are used, for example, intelligent fan

speed adjustment, ALS, port dormancy, EEE, and shutting down idle circuits andcomponents.

l Basic mode: The basic energy-saving mode uses technologies supported by the standardmode and allows the device to power off redundant power modules based on rated powerconsumption.

l Deep mode: The deep energy-saving mode uses technologies supported by the standardmode and allows the device to power off redundant power modules based on rated powerconsumption.



23

NOTE

The device supports only the standard mode.

Procedure



Step 2 Run:set device power manage mode mode

An energy-saving mode is configured for the device.

By default, the standard energy-saving mode is used.

Step 3 Run:commit


----End

Checking the Configuration

l Run the display device power system command to check the energy-saving mode of thedevice.

3.6 Configuration ExamplesThis section provides energy-saving management configuration examples including networkingrequirements and configuration roadmap.

3.6.1 Example for Configuring ALS

Networking Requirements

As shown in Figure 3-1, 10GE1/0/1 on SwitchA connects to 10GE1/0/1 on SwitchB throughthe optical fiber.

When a link fails, the laser on the optical module is required to automatically stop sending pulsesand recover pulse sending after the link is recovered.

Figure 3-1 Networking diagram for configuring ALS

SwitchA SwitchB

10GE1/0/1 10GE1/0/1



24

Configuration RoadmapThe configuration roadmap is as follows:

1. Enable ALS on the interface so that the laser automatically stops sending pulses when alink fails.

2. Set the restart mode of the laser to automatic restart mode so that the laser sends pulsesagain after the link is recovered.

Procedure

Step 1 Configure ALS on the interface and the restart mode of the laser.

# Enable ALS on 10GE1/0/1 of SwitchA and set the restart mode of the laser to automatic restart.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] interface 10ge 1/0/1[~SwitchA-10GE1/0/1] als enable[~SwitchA-10GE1/0/1] als restart mode automatic[~SwitchA-10GE1/0/1] commit

# Enable ALS on 10GE1/0/1 of SwitchB and set the restart mode of the laser to automatic restart.

<HUAWEI> system-view[~HUAWEI] sysname SwitchB[~HUAWEI] commit[~SwitchB] interface 10ge 1/0/1[~SwitchB-10GE1/0/1] als enable[~SwitchB-10GE1/0/1] als restart mode automatic[~SwitchB-10GE1/0/1] commit

Step 2 Verify the configuration.

# Check ALS configurations on interfaces of SwitchA and SwitchB.

<SwitchA> display als interface 10ge 1/0/1--------------------------------------------------------------------------------Interface ALS Status Laser Status Restart Mode Interval(s) Width(s) --------------------------------------------------------------------------------10GE1/0/1 Enable on Auto 100 2 --------------------------------------------------------------------------------<SwitchB> display als interface 10ge 1/0/1--------------------------------------------------------------------------------Interface ALS Status Laser Status Restart Mode Interval(s) Width(s) --------------------------------------------------------------------------------10GE1/0/1 Enable on Auto 100 2 --------------------------------------------------------------------------------

----End

Configuration filel Configuration file of SwitchA

#sysname SwitchA#interface 10GE1/0/1



25

als enable# return

l Configuration file of SwitchB

#sysname SwitchB#interface 10GE1/0/1 als enable# return



26

4 Information Center Configuration

About This Chapter

The information center works as the information hub. It records system running information inreal time, which helps the network administrator and developers to monitor network operationand analyze network faults.

4.1 Introduction to the Information CenterThe information center records information generated by each module during device running,including logs, traps, and debugging messages.

4.2 Information Center Features Supported by the DeviceThe information center outputs logs, traps, and debugging messages to different destinationsbased on output rules.

4.3 Default ConfigurationThis section describes default parameter settings of the information center.

4.4 Configuring Log OutputLogs of a specific module can be output to the log buffer, log file, console, terminal, or log host.

4.5 Configuring Trap OutputTraps of a specific module can be output to the trap buffer, log file, console, terminal, log host,or SNMP agent.

4.6 Configuring Debugging Message OutputDebugging messages of a specific module can be output to the console and terminal.

4.7 Maintaining the Information CenterThis section describes how to maintain the information center.

4.8 Configuration ExamplesThis section provides several configuration examples of the information center, coveringnetworking requirements, configuration notes, and configuration roadmap.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 4 Information Center Configuration


27

4.1 Introduction to the Information CenterThe information center records information generated by each module during device running,including logs, traps, and debugging messages.

During routine maintenance or emergency troubleshooting, users or administrators want to learninformation generated during device running. You can configure the information center toclassify and filter information based on information types and severities so that information canbe flexibly output to different destinations such as the console, user terminal, and log host. Bydoing this, users or network administrators can collect device information from differentdestinations so that they can easily monitor the device running status and locate faults.

4.2 Information Center Features Supported by the DeviceThe information center outputs logs, traps, and debugging messages to different destinationsbased on output rules.

Table 4-1 lists applicable scenarios of logs, traps, and debugging messages.

Table 4-1 Information center applicable scenarios

Information Type

Applicable Scenario Output Direction

Log To monitor the device runningstatus, you can configure the deviceto output logs to differentdestinations. You can learn devicerunning status in real time bycollecting logs generated by thedevice.

Logs can be output to the console,remote terminal, log host, log buffer,and log file.

Trap When an exception or a fault occurson the device, you can configure thedevice to output traps to differentdestinations. You can learn devicerunning status and locate the fault inreal time by collecting trapsgenerated by the device.

Traps can be output to the console,remote terminal, log host, trap buffer,SNMP agent, and log file.

Debuggingmessage

To learn internal tracinginformation or debug the device,you can configure the device tooutput debugging messages todifferent destinations.

Debugging messages can be output tothe console and remote terminal.

4.3 Default ConfigurationThis section describes default parameter settings of the information center.



28

Table 4-2 Default parameter settings of the information center

Parameter Default Setting

Information center Enabled

Maximum number of logs in the log buffer 512

Maximum number of traps in the trap buffer 256

Log file size 8 MB

Maximum number of log files that can besaved

200

Log host IP address None

Timestamp format date

Default Output Rules of Information ChannelsDefault output rules define information modules to which different types of information can beoutput, lowest information severity, and information channels. See Table 4-3.

Table 4-3 Default output rules

OutputChannel

ModuleEnabled toOutputInformation

Log Trap DebuggingMessage

Status LowestOutputSeverity



0(console)

default(allmodules)

Enabled warning Enabled debugging

Enabled debugging

1(remoteterminal)

default(allmodules)

Enabled warning Enabled debugging

Enabled debugging

2 (loghost)

default(allmodules)

Enabled informational

Enabled debugging

Disabled debugging

3 (trapbuffer)

default(allmodules)

Disabled informational

Enabled debugging

Disabled debugging



29

OutputChannel

ModuleEnabled toOutputInformation

Log Trap DebuggingMessage




4 (logbuffer)

default(allmodules)

Enabled warning Disabled debugging

Disabled debugging

5(SNMPagent)

default(allmodules)

Disabled debugging

Enabled debugging

Disabled debugging

6(channel6)

default(allmodules)

Enabled debugging

Enabled debugging

Disabled debugging

7(channel7)

default(allmodules)

Enabled debugging

Enabled debugging

Disabled debugging

8(channel8)

default(allmodules)

Enabled debugging

Enabled debugging

Disabled debugging

9(channel9)

default(allmodules)

Enabled debugging

Enabled debugging

Disabled debugging

4.4 Configuring Log OutputLogs of a specific module can be output to the log buffer, log file, console, terminal, or log host.


Before enabling log output, complete the following task:

Starting the Switch

Configuration Process

Table 4-4 lists the configuration process for enabling log output.



30

Table 4-4 Configuration process for enabling log output

No. ConfigurationTask

Description Remarks

1 4.4.1 Enabling theInformationCenter

You can configure the informationcenter only after the information centeris enabled.By default, the information center isenabled.

Steps 2 to 4 areoptional and can beperformed in anysequence.

2 4.4.2 (Optional)Naming anInformationChannel

You can rename channels, whichfacilitates memorization and usage.

3 4.4.3 (Optional)Configuring LogFiltering

If some logs are unnecessary,configure the Switch not to outputthese logs.

4 4.4.4 (Optional)Setting theTimestampFormat of Logs

To adjust the time format and timeprecision for information output,configure the timestamp.

5 4.4.6 Configuringthe Device toOutput Logs to theLog Buffer

To view logs in the log buffer,configure the Switch to output logs tothe log buffer.

Steps 5 to 9 can beconfigured in anysequence. You canconfigure the deviceto output logs to oneor more destinationsaccording to yourneeds.

6 4.4.7 Configuringthe Device toOutput Logs to aLog File

After logs are output to a log file, youcan download the log file anytime tomonitor device running based on thelogs.

7 4.4.8 Configuringthe Device toOutput Logs to theConsole

After logs are output to the console,you can view logs on the console (hostfrom which you can log in to theSwitch through the console interface)to monitor device running.

8 4.4.9 Configuringthe Device toOutput Logs to aTerminal

After logs are output to a user terminal,you can view logs on the user terminal(host from which you log in to theSwitch through STelnet) to monitordevice running.

9 4.4.10 Configuringthe Device toOutput Logs to aLog Host

After configuring the Switch to outputlogs to a log host, you can view logssaved on the log host to monitor devicerunning.



31

4.4.1 Enabling the Information Center

ProcedureStep 1 Run:

system-view


Step 2 Run:info-center enable

The information center is enabled.

By default, the information center is enabled.

Step 3 Run:commit


----End

4.4.2 (Optional) Naming an Information Channel

ContextYou can rename channels, which facilitates memorization and usage.

NOTE

Channel names must be unique. It is recommended that channel names represent channel functions.

The following lists default channel names.

Table 4-5 Default channel names

Channel Number Default Channel Name

0 console

1 monitor

2 loghost

3 trapbuffer

4 logbuffer

5 snmpagent

6 channel6

7 channel7

8 channel8

9 channel9



32

Procedure



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

A name is configured for the information channel with the specified number.

Step 3 Run:commit


----End

4.4.3 (Optional) Configuring Log Filtering

ContextIf some logs are unnecessary, configure the device not to output these logs. When the filteringfunction is enabled, the information center does not send the specified logs that satisfy thefiltering condition to any channel. As a result, all output directions cannot receive the specifiedlogs.

Procedure



Step 2 Run:info-center filter-id { id | bymodule-alias modname alias }

The filtering function is configured for specified logs.

Step 3 Run:commit


----End

4.4.4 (Optional) Setting the Timestamp Format of Logs

ContextTo adjust the time format and time precision for information output, configure the timestamp.

Procedure




33


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

The timestamp format of logs is configured.

By default, the timestamp format of logs is date.

Step 3 Run:commit


----End

4.4.5 (Optional) Enabling the Output of the Statistics AboutRepeatedly Generated Logs

Context

On the system, service modules generate logs and control the volume of generated logs. Theinformation center processes the received logs.

In some scenarios, service modules, such as ARP and VRRP, generate a large number of repeatedlogs within a short period. In this situation, you can enable the output of the statistics aboutrepeatedly generated logs to protect the information center against the impact of the large logvolume.

NOTE

Logs that are generated consecutively and with identical log IDs and parameters can be regarded asrepeatedly generated logs.

Procedure



Step 2 Run:info-center statistic-suppress enable

The output of the statistics about repeatedly generated logs is enabled.

By default, the output of the statistics about repeatedly generated logs is enabled.

Step 3 Run:commit


----End



34

4.4.6 Configuring the Device to Output Logs to the Log Buffer

ContextTo view logs in the log buffer, configure the device to output logs to the log buffer.

Procedure



Step 2 Run:info-center logbuffer

The device is enabled to output information to the log buffer.

By default, the device is enabled to output logs to the log buffer.

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

The channel used by the device to output logs to the log buffer is specified.

By default, the device uses channel 4 to output logs to the log buffer.

Step 4 Run:info-center source { module-name | default } channel { channel-number | channel-name } log { state { off | on } | level severity } *

A rule for outputting logs to a channel is set.

By default, channel 4 is enabled to output logs and the lowest log severity is warning.

Step 5 (Optional) Run:info-center logbuffer size logbuffer-size [ channel { channel-number | channel-name } ]

The maximum number of logs in the log buffer is set.

By default, a log buffer can store a maximum of 512 logs.

Step 6 Run:commit


----End

4.4.7 Configuring the Device to Output Logs to a Log File

ContextAfter logs are output to a log file, you can view the log file anytime to monitor device runningbased on the logs.



35

Procedure



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

A channel through which logs are output to a log file is specified.

By default, the device uses channel 9 to output logs to a log file.



By default, channel 9 is enabled to output logs and the lowest log severity is debugging.

Step 4 (Optional) Run:info-center logfile size size

The log file size is set.

By default, the log file size is 8 MB.

NOTE

l If the size of a log file generated on the device exceeds the configured log file size, the systemdecompresses the log file into a zip file.

l You can run the save logfile command to manually save logs in the log file buffer to a log file.

Step 5 (Optional) Run:info-center max-logfile-number filenumbers

The maximum number of log files that can be saved is set.

By default, a maximum of 200 log files can be saved.

If the number of log files generated on the Switch exceeds the limit, the system deletes the oldestlog file.

Step 6 Run:commit


----End

4.4.8 Configuring the Device to Output Logs to the Console

Context

After logs are output to the console, you can view logs on the console (host from which you canlog in to the device through the console interface) to monitor device running.



36

Procedure



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

A channel through which logs are output to the console is specified.

By default, the device uses channel 0 to output logs to the console.




Step 4 Run:commit


Step 5 Run:quit

Return to the user view.

Step 6 Run:terminal monitor

Display of logs, traps, and debugging message output is enabled on the user terminal.

By default, terminal display is enabled.

Step 7 Run:terminal logging

Log display is enabled on the user terminal.

By default, log display is disabled on the user terminal.

----End

4.4.9 Configuring the Device to Output Logs to a Terminal

ContextAfter logs are output to a user terminal, you can view logs on the user terminal (host from whichyou log in to the device through Telnet) to monitor device running.

Procedure




37


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

A channel through which logs are output to a user terminal is specified.

By default, the Switch uses channel 1 to output logs to a user terminal.




Step 4 Run:commit


Step 5 Run:quit





Step 7 Run:terminal logging

Log display is enabled on the user terminal.

By default, log display is disabled on the user terminal.

----End

4.4.10 Configuring the Device to Output Logs to a Log Host

ContextAfter configuring the device to output logs to a log host, you can view logs saved on the log hostto monitor device running.

Pre-configuration TasksThere is a reachable route between the device and the log host.

Procedure




38


Step 2 Run:info-center loghost ip-address [ channel { channel-number | channel-name } | vpn-instance vpn-insname | facility local-number | port port-number | level info-level | { local-time | utc } ] *

The device is configured to output logs to a log host.

By default, the device does not output logs to a log host.

The device supports a maximum of eight log hosts to implement backup among log hosts.



By default, channel 2 is enabled to output logs and the lowest log severity is informational.

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

The source interface used by the device to send logs to a log host is specified.

By default, the source interface is the interface that sends logs.

After the source interface is specified, the log host determines the device that sends messages.The log host then can easily retrieve received messages.

Step 5 Run:commit


----End


Procedurel Run the display info-center channel [ channel-number | channel-name ] command to view

the channel configuration.l Run the display logbuffer command to check logs recorded in the log buffer.l Run the display logfile file-name [ offset ] command to check the log file.

----End

4.5 Configuring Trap OutputTraps of a specific module can be output to the trap buffer, log file, console, terminal, log host,or SNMP agent.

Pre-configuration TasksBefore enabling trap output, complete the following task:



39

Starting the Switch

Configuration ProcessTable 4-6 lists the configuration process for enabling trap output.

Table 4-6 Configuration process for enabling trap output

No. Name Description Remarks

1 4.5.1 Enabling theInformation Center

You can configure theinformation center onlyafter the informationcenter is enabled.By default, theinformation center isenabled.

Steps 2 to 4 are optionaland can be performed inany sequence.

2 4.5.2 (Optional) Namingan Information Channel

You can rename channels,which facilitatesmemorization and usage.

3 4.5.3 (Optional)Configuring TrapFiltering

If some traps areunnecessary, configure theSwitch not to output thesetraps.

4 4.5.4 (Optional) Settingthe Timestamp Formatof Traps

To adjust the time formatand time precision forinformation output,configure the timestamp.

5 4.5.5 Configuring theDevice to Output Trapsto the Trap Buffer

To view traps in the trapbuffer, configure theSwitch to output traps tothe trap buffer.

Steps 5 to 10 can beconfigured in anysequence. You canconfigure the device tooutput traps to one or moredestinations according toyour needs.

6 4.5.6 Configuring theDevice to Output Trapsto a Log File

After traps are output to alog file, you can downloadthe log file anytime toview traps generated bythe Switch to monitordevice running.

7 4.5.7 Configuring theDevice to Output Trapsto the Console

After traps are output tothe console, you can viewtraps on the console (hostfrom which you can log into the Switch through theconsole interface) tomonitor device running.



40

No. Name Description Remarks

8 4.5.8 Configuring theDevice to Output Trapsto a Terminal

After traps are output to auser terminal, you canview traps on the userterminal (host from whichyou log in to the Switchthrough STelnet) tomonitor device running.

9 4.5.9 Configuring theDevice to Output Trapsto a Log Host

After configuring theSwitch to output traps to alog host, you can viewtraps saved on the log hostto monitor device running.

10 4.5.10 Configuring theDevice to Output Trapsto an SNMP Agent

When an exception or afault occurs on theSwitch, the networkadministrator wants tolearn device running. Youcan configure the Switchto output traps to an NMSserver so that the networkadministrator can monitorthe Switch in real time andlocate faults immediately.Before configuring theSwitch to output traps toan NMS server, configurethe Switch to output trapsto an SNMP agent. Thenthe SNMP agent sendstraps to the NMS server.


Procedure






Step 3 Run:commit



41


----End



NOTE





0 console

1 monitor

2 loghost

3 trapbuffer

4 logbuffer

5 snmpagent

6 channel6

7 channel7

8 channel8

9 channel9

Procedure





Step 3 Run:commit


----End



42

4.5.3 (Optional) Configuring Trap Filtering

Context

If some traps are unnecessary, configure the device not to output these traps. When the filteringfunction is enabled, the information center does not send the specified traps that satisfy thefiltering condition to any channel. As a result, all output directions cannot receive the specifiedtraps.

Procedure



Step 2 Run:info-center filter-id { id | bymodule-alias modname alias }

The filtering function is configured for specified traps.

Step 3 Run:commit


----End

4.5.4 (Optional) Setting the Timestamp Format of Traps

Context

To adjust the time format and time precision for information output, configure the timestamp.

Procedure



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

The timestamp format of traps is set.

By default, the timestamp format of traps is date.

Step 3 Run:commit


----End



43

4.5.5 Configuring the Device to Output Traps to the Trap Buffer

ContextTo view traps in the trap buffer, configure the device to output traps to the trap buffer.

Procedure



Step 2 Run:info-center trapbuffer

The device is enabled to output traps to the trap buffer.

By default, the device is enabled to output traps to the trap buffer.

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

The channel used by the device to output traps to the trap buffer is specified.

By default, the device uses channel 3 to output traps to the trap buffer.

Step 4 Run:info-center source { module-name | default } channel { channel-number | channel-name } trap { state { off | on } | level severity } *

A rule for outputting traps to a channel is set.

By default, channel 3 is enabled to output traps and the lowest severity is debugging.

Step 5 (Optional) Run:info-center trapbuffer size trapbuffer-size [ channel { channel-number | channel-name } ]

The maximum number of traps in the trap buffer is set.

By default, the trap buffer can store a maximum of 256 traps.

Step 6 Run:commit


----End

4.5.6 Configuring the Device to Output Traps to a Log File

ContextAfter traps are output to a log file, you can view the log file anytime to monitor device runningbased on the traps.



44

Procedure



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

A channel through which traps are output to a log file is specified.

By default, the device uses channel 9 to output traps to a log file.




Step 4 (Optional) Run:info-center logfile size size

The log file size is set.

By default, the log file size is 8 MB.

NOTE

l If the size of a log file generated on the device exceeds the configured log file size, the systemdecompresses the log file into a zip file.

l You can run the save logfile command to manually save traps in the log file buffer to a log file.

Step 5 (Optional) Run:info-center max-logfile-number filenumbers

The maximum number of log files that can be saved is set.

By default, a maximum of 200 log files can be saved.

If the number of log files generated on the Switch exceeds the limit, the system deletes the oldestlog file.

Step 6 Run:commit


----End

4.5.7 Configuring the Device to Output Traps to the Console

Context

After traps are output to the console, you can view traps on the console (host from which youcan log in to the device through the console interface) to monitor device running.



45

Procedure




A channel through which traps are output to the console is specified.

By default, the device uses channel 0 to output traps to the console.




Step 4 Run:commit


Step 5 Run:quit





Step 7 Run:terminal alarm

Traps display is enabled on the user terminal.

By default, traps display is disabled on the user terminal.

----End

4.5.8 Configuring the Device to Output Traps to a Terminal

ContextAfter traps are output to a user terminal, you can view traps on the user terminal (host fromwhich you log in to the device through Telnet) to monitor device running.

Procedure




46



A channel through which traps are output to a user terminal is specified.

By default, the device uses channel 1 to output traps to a user terminal.




Step 4 Run:commit


Step 5 Run:quit





Step 7 Run:terminal alarm

Traps display is enabled on the user terminal.

By default, traps display is disabled on the user terminal.

----End

4.5.9 Configuring the Device to Output Traps to a Log Host

ContextAfter configuring the device to output traps to a log host, you can view traps saved on the loghost to monitor device running.

Pre-configuration TasksThere is a reachable route between the device and the log host.

Procedure




47


Step 2 Run:info-center loghost ip-address [ channel { channel-number | channel-name } | vpn-instance vpn-insname | facility local-number | port port-number | level info-level | { local-time | utc } ] *

The device is configured to output traps to a log host.

By default, the device does not output traps to a log host.

The device supports a maximum of eight log hosts to implement backup among log hosts.




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

The source interface used by the device to send logs to a log host is specified.

By default, the source interface is the interface that sends logs.

After the source interface is specified, the log host determines the device that sends messages.The log host then can easily retrieve received messages.

Step 5 Run:commit


----End

4.5.10 Configuring the Device to Output Traps to an SNMP Agent

ContextWhen an exception or a fault occurs on the device, the network administrator needs to learn thedevice running status. You can configure the device to output traps to an NMS server so that thenetwork administrator can monitor the device in real time and locate faults immediately. Beforeconfiguring the device to output traps to an NMS server, configure the device to output traps toan SNMP agent. Then the SNMP agent sends traps to the NMS server.

Procedure



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

The channel used by the device to output traps to an SNMP agent is specified.



48

By default, the device uses channel 5 to output traps to an SNMP agent.




Step 4 Run:snmp-agent

The SNMP agent function is enabled.

By default, the SNMP agent function is disabled.

The SNMP agent can work properly and receive traps only when the SNMP agent function isenabled.

NOTE

For details on how to configure the SNMP agent, see SNMP Configuration in the CloudEngine 6800&5800Series Switches Configuration Guide - Network Management.

Step 5 Run:commit


----End



the channel configuration.

l Run the display logfile file-name [ offset ] command to check the log file.

l Run the display trapbuffer [ size value ] command to check traps recorded in the trapbuffer.

----End

4.6 Configuring Debugging Message OutputDebugging messages of a specific module can be output to the console and terminal.


Before enabling debugging message output, complete the following task:

Starting the Switch



49

CAUTIONDebugging occupies CPU resources on the device, affecting system running. After debugging,run the undo debugging all command to disable it immediately.

Configuration Process

Table 4-8 lists the configuration process for enabling debugging message output.

Table 4-8 Configuration process for enabling debugging message output

No. Configuration Task Description Remarks

1 4.6.1 Enabling theInformation Center

You can configure theinformation center onlyafter the informationcenter is enabled.By default, theinformation center isenabled.

Steps 2 and 3 are optionaland can be performed inany sequence.

2 4.6.2 (Optional) Namingan Information Channel

You can rename channels,which facilitatesmemorization and usage.

3 4.6.3 (Optional) Settingthe Timestamp Formatof Debugging Messages

To adjust the time formatand time precision forinformation output,configure the timestamp.

4 4.6.4 Configuring theDevice to OutputDebugging Messages tothe Console

After debuggingmessages are output to theconsole, you can viewdebugging messages onthe console (host fromwhich you can log in to thethrough the consoleinterface) to monitordevice running.

Steps 4 to 5 can beperformed in anysequence. You canconfigure the device tooutput debuggingmessages to one or moredestinations according toyour needs.

5 4.6.5 Configuring theDevice to OutputDebugging Messages tothe Terminal

After debuggingmessages are output to auser terminal, you canview debugging messageson the user terminal (hostfrom which you log in tothe Switch throughSTelnet) to monitordevice running.



50



system-view





Step 3 Run:commit


----End



NOTE





0 console

1 monitor

2 loghost

3 trapbuffer

4 logbuffer

5 snmpagent

6 channel6

7 channel7

8 channel8

9 channel9



51

Procedure





Step 3 Run:commit


----End

4.6.3 (Optional) Setting the Timestamp Format of DebuggingMessages

ContextTo adjust the time format and time precision for information output, configure the timestamp.

Procedure



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

The timestamp format of debugging messages is set.

By default, the timestamp format of debugging messages is date.

Step 3 Run:commit


----End

4.6.4 Configuring the Device to Output Debugging Messages to theConsole

ContextAfter debugging messages are output to the console, you can view debugging messages on theconsole (host from which you can log in to the device through the console interface) to monitordevice running.



52

Procedure




A channel used by the device to output debugging messages to the console is specified.

By default, the device uses channel 0 to output debugging messages to the console.

Step 3 Run:info-center source { module-name | default } channel { channel-number | channel-name } debug { state { off | on } | level severity } *

A rule for outputting debugging messages to a channel is set.

By default, channel 0 is enabled to output debugging messages and the lowest severity isdebugging.

Step 4 Run:commit


Step 5 Run:quit





Step 7 Run:terminal debugging

Debugging message display is enabled on the user terminal.

By default, debugging message display is disabled on the user terminal.

----End

4.6.5 Configuring the Device to Output Debugging Messages to theTerminal

Context

After debugging messages are output to a user terminal, you can view debugging messages onthe user terminal (host from which you log in to the device through STelnet) to monitor devicerunning.



53

Procedure




A channel used by the device to output debugging messages to a user terminal is specified.

By default, the device uses channel 1 to output debugging messages to a user terminal.

Step 3 Run:info-center source { module-name | default } channel { channel-number | channel-name } debug { state { off | on } | level severity } *

A rule for outputting debugging messages to a channel is set.

By default, channel 1 is enabled to output debugging messages and the lowest severity isdebugging.

Step 4 Run:commit


Step 5 Run:quit





Step 7 Run:terminal debugging

Debugging message display is enabled on the user terminal.

By default, debugging message display is disabled on the user terminal.

----End



the channel configuration.

----End



54

4.7 Maintaining the Information CenterThis section describes how to maintain the information center.

4.7.1 Clearing Statistics

Context

CAUTIONStatistics of the information center cannot be restored after you clear them. Exercise cautionwhen running the commands.

Procedurel To clear the statistics of the information center, run the reset info-center statistics

command in the user view.l To clear the statistics in the log buffer, run the reset logbuffer command in the user view.l To clear the statistics in the trap buffer, run the reset trapbuffer command in the user view.

----End

4.7.2 Monitoring the Information Center

Procedurel Run the display info-center command to view output configuration of the information

center.l Run the display info-center statistics command to view statistics of the information center.l Run the display logbuffer command to view logs recorded in the log buffer.l Run the display logfile file-name [ offset ] command to view the log file.l Run the display trapbuffer [ size value ] command to view traps recorded in the trap buffer.

----End

4.8 Configuration ExamplesThis section provides several configuration examples of the information center, coveringnetworking requirements, configuration notes, and configuration roadmap.



55

4.8.1 Example for Outputting Logs to the Log File

Networking RequirementsAs shown in Figure 4-1, SwitchA connects to the FTP server through the network. There is areachable route between SwitchA and the FTP server. The network administrator wants to usethe FTP server to view logs generated by SwitchA and learn operations on SwitchA.

NOTEFTP cannot secure secure file transfer. SFTP is recommended on networks that require high security.

Figure 4-1 Networking diagram for outputting logs to the log file

FTP ServerSwitchA

Network

10.1.1.1/1610.2.1.1/16


1. Enable the information center.2. Configure a channel and a rule for outputting logs to a log file so that logs are saved in the

log file.3. Configure SwitchA to transfer the log file to the FTP server so that the network

administrator can use the FTP server to view logs generated by SwitchA.

Procedure

Step 1 Enable the information center.<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] info-center enable[~SwitchA] commit

Step 2 Configure a channel and a rule for outputting logs to a log file.

# Configure a channel for outputting logs to a log file.

[~SwitchA] info-center logfile channel channel6[~SwitchA] commit

NOTE

By default, channel 9 is used to send logs to a log file. If the default setting is used, skip this step.

# Configure a rule for outputting logs to a log file.

[~SwitchA] info-center source default channel channel6 log level warning[~SwitchA] commit



56

Step 3 Configure SwitchA to transfer the log file to the FTP server.

# Log in to the FTP server with user name user1 and password pwd123.

<SwitchA> ftp 10.1.1.1Trying 10.1.1.1 ... Press CTRL + K to abort Connected to 10.1.1.1. 220 VRPV8 FTP service ready.User(10.1.1.1:(none)):user1 331 Password required for user1. Enter password: 230 User logged in.

# Configure SwitchA to transfer the log file to the FTP server.

[ftp] put flash:/logfile/log.log200 Port command okay.150 Opening ASCII mode data connection for /log.log.226 Transfer complete.\ 100% [***********]FTP: 7521956 byte(s) send in 3.1784917300 second(s) 2311.409Kbyte(s)/sec.[ftp] quit


# View information recorded by the channel.

<SwitchA> display info-centerInformation Center:enabledLog host:Console: 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 18, channel number : 4, channel name : logbufferdropped messages 0, overwritten messages 0Trap buffer: enabled,max buffer size 1024, current buffer size 256,current messages 36, channel number:3, channel name:trapbufferdropped messages 0, overwritten messages 0Logfile: channel number : 6, channel name : channel6, language : EnglishInformation timestamp setting: log - date, trap - date, debug - date millisecond

# View the received log file on the FTP server. The configuration details are not mentioned here.

----End

Configuration Filesl Configuration file of SwitchA

#sysname SwitchA#info-center source default channel 6 log level warninginfo-center logfile channel 6#return



57

4.8.2 Example for Outputting Logs to a Log Host

Networking RequirementsAs shown in Figure 4-2, SwitchA connects to four log hosts. Log hosts are required to havereliability and receive logs of different types and severities so that the network administrator canmonitor logs generated by different modules on SwitchA.

Figure 4-2 Networking diagram for outputting logs to a log host

VLANIF100172.16.0.1/24

10GE1/0/1SwitchA

Server1

Server 2Server 4

Server 310.1.1.2/24 10.1.1.1/24

10.2.1.1/2410.2.1.2/24


1. Enable the information center.2. Configure SwitchA to send logs of notification generated by the ARP module to Server1,

and specify Server3 as the backup of Server1. Configure SwitchA to send logs of warninggenerated by the AAA module to Server2, and specify Server4 as the backup of Server2.

3. Configure the log host on the server so that the network administrator can receive logsgenerated by SwitchA on the log host.

Procedure


Step 2 Configure a channel and a rule for outputting logs to a log host.

# Name a channel.

[~SwitchA] info-center channel 6 name loghost1[~SwitchA] info-center channel 7 name loghost2[~SwitchA] commit

# Configure a channel for outputting logs to a log host.

[~SwitchA] info-center loghost 10.1.1.1 channel loghost1[~SwitchA] info-center loghost 10.1.1.2 channel loghost1



58

[~SwitchA] info-center loghost 10.2.1.1 channel loghost2[~SwitchA] info-center loghost 10.2.1.2 channel loghost2[~SwitchA] commit

# Configure a rule for outputting logs to a log host.

[~SwitchA] info-center source arp channel loghost1 log level notification[~SwitchA] info-center source aaa channel loghost2 log level warning[~SwitchA] commit

Step 3 Specify the source interface for sending logs.

# Specify the source interface for sending logs.

[~SwitchA] info-center loghost source vlanif 100[~SwitchA] commit

Step 4 Configure the log host on the server.

The Switch can generate many logs, which may exceed the limited storage space of theSwitch. To address this problem, configure a log host to store all the logs.

The log host can run the Unix or Linux operating system or run third-party log software. Fordetails about the configuration procedure, see the relevant documentation.


# View the configured lost host.

<SwitchA> display info-centerInformation Center:enabledLog host: 10.1.1.1, channel number 6, channel name loghost1,language English , host facility local7 10.1.1.2, channel number 6, channel name loghost1,language English , host facility local7 10.2.1.1, channel number 7, channel name loghost2,language English , host facility local7 10.2.1.2, channel number 7, channel name loghost2,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 26, channel number : 4, channel name : logbufferdropped messages 0, overwritten messages 0Trap buffer: enabled,max buffer size 1024, current buffer size 256,current messages 11, channel number:3, channel name:trapbufferdropped messages 0, overwritten messages 0logfile: channel number : 9, channel name : channel9, language : EnglishInformation timestamp setting: log - date, trap - date, debug - date millisecond

----End


#sysname SwitchA#info-center channel 6 name loghost1



59

info-center channel 7 name loghost2info-center source arp channel 6 log level notificationinfo-center source aaa channel 7 log level warninginfo-center loghost source Vlanif100info-center loghost 10.1.1.1 channel 6info-center loghost 10.1.1.2 channel 6info-center loghost 10.2.1.1 channel 7info-center loghost 10.2.1.2 channel 7#return

4.8.3 Example for Outputting Traps to the SNMP Agent


As shown in Figure 4-3, SwitchA connects to the NMS station. There is a reachable routebetween SwitchA and the NMS station. The network administrator wants to view traps generatedby SwitchA on the NMS station to monitor device running and locate faults.

Figure 4-3 Networking diagram for outputting traps to the SNMP agent

NM Station SwitchA10.1.1.2/2410.1.1.1/24

Configuration Roadmap

The configuration roadmap is as follows:

1. Enable the information center.2. Configure a channel and a rule for outputting traps to the SNMP agent so that the SNMP

agent can receive traps generated by SwitchA.3. Configure SwitchA to output traps to the NMS station so that the NMS station can receive

traps generated by SwitchA.

Procedure


Step 2 Configure a channel and a rule for outputting traps to the SNMP agent.

# Configure a channel for outputting traps to the SNMP agent.

[~SwitchA] info-center snmp channel channel7[~SwitchA] commit

# Configure a rule for outputting traps to the SNMP agent.



60

[~SwitchA] info-center source arp channel channel7 trap level informational state on [~SwitchA] commit

NOTE

By default, the device uses the SNMP agent to output traps of all modules.

Step 3 Configure the SNMP agent to output traps to the NMS station.

# Enable the SNMP agent and set the SNMP version to SNMPv2c.

[~SwitchA] snmp-agent sys-info version v2c[~SwitchA] commit

# Configure the trap function.

[~SwitchA] snmp-agent trap enable[~SwitchA] snmp-agent community write adminnms123[~SwitchA] snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname public[~SwitchA] commit[~SwitchA] quit


# View the output configuration of the information center.

<SwitchA> display info-centerInformation Center:enabledLog host:Console: channel number : 0, channel name : consoleMonitor: channel number : 1, channel name : monitorSNMP Agent: channel number : 7, channel name : channel7Log buffer: enabled,max buffer size 1024, current buffer size 512,current messages 26, channel number : 4, channel name : logbufferdropped messages 0, overwritten messages 0Trap buffer: enabled,max buffer size 1024, current buffer size 256,current messages 22, channel number:3, channel name:trapbufferdropped messages 0, overwritten messages 0logfile: channel number : 9, channel name : channel9, language : EnglishInformation timestamp setting: log - date, trap - date, debug - date millisecond

# View the channel used by the SNMP agent to output traps.

<SwitchA> display info-center channel 7channel number:7, channel name:channel7MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVELffffffff default Y debugging Y debugging N debugging00000859 ARP Y debugging Y informational N debugging

# View traps output to the NMS station by the SNMP agent.

<SwitchA> display snmp-agent target-hostTarget-host NO. 1 --------------------------------------------------------------------------- Host-name : - IP-address : 10.1.1.1 Source interface : - VPN instance : - Security name : %$%$>Oh`"sfiHSgR>SLWkM`3%tkb%$%$



61

Port : 162 Type : trap Version : v1 Level : No authentication and privacy NMS type : NMS With ext-vb : No Notification filter profile name : - ---------------------------------------------------------------------------

----End


#sysname SwitchA#snmp-agentsnmp-agent local-engineid 800007DB030A0B0C000003#snmp-agent sys-info version v2csnmp-agent community write cipher %@%@0L%%$pI<#6z,oF3zc&U0,ULCJWa^>)*=-)r[4#-p^+25h[RMjYqfYysx,A5sw$F_SuNXk_VS%@%@snmp-agent target-host trap address udp-domain 10.1.1.1 params securityname cipher %$%$>Oh`"sfiHSgR>SLWkM`3%tkb%$%$#snmp-agent trap enable#info-center source arp channel 7 trap level informationalinfo-center snmp channel 7#return

4.8.4 Example for Outputting Debugging Messages to the Console


As shown in Figure 4-4, the PC connects to SwitchA through a console interface. It is requiredthat debugging messages of the ARP module be displayed on the PC.

Figure 4-4 Networking diagram for outputting debugging messages to the console

SwitchA

Console

PC

Configuration Roadmap

The configuration roadmap is as follows:

1. Enable the information center.

2. Configure a channel and a rule for outputting debugging messages to the console so thatthe console can receive debugging messages generated by SwitchA.



62

3. Enable terminal display so that users can use the terminal to view debugging messagesgenerated by SwitchA.

Procedure


Step 2 Configure a channel and a rule for outputting debugging messages to the console.

# Configure a channel for outputting debugging messages to the console.

[~SwitchA] info-center console channel console[~SwitchA] commit

# Configure a rule for outputting debugging messages to the console.

[~SwitchA] info-center source arp channel console debug level debugging state on[~SwitchA] commit[~SwitchA] quit

Step 3 Enable terminal display.<SwitchA> terminal monitorInfo: Current terminal monitor is on.<SwitchA> terminal debuggingInfo: Current terminal debugging is on.

Step 4 Debug the ARP module.<SwitchA> debugging arp packet


# View the channel used by the Console to output debugging messages.

<SwitchA> display info-center channel 0channel number:0, channel name:consoleMODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVELffffffff default Y warning Y debugging Y debugging00000859 ARP Y warning Y debugging Y debugging

----End


#sysname SwitchA#info-center source arp channel 0#return



63

5 Fault Management Configuration

About This Chapter

The fault management configuration allows users to collect fault information and locate faultsquickly and efficiently at the NMS side.

5.1 Introduction to Fault ManagementBy using fault management, users can efficiently manage and report alarms in a centralizedmanner.

5.2 Default ConfigurationThis section describes default parameter settings of the device.

5.3 Configuring Alarm ManagementAlarm management includes setting alarm severities, and enabling alarm reporting delay.

5.4 MaintenanceThis section describes how to monitor and clear alarms.

5.5 Configuration ExamplesThis section describes fault management configurations based on the configuration flowchart,including networking requirements, configuration roadmap, and configuration procedure.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 5 Fault Management Configuration


64

5.1 Introduction to Fault ManagementBy using fault management, users can efficiently manage and report alarms in a centralizedmanner.

With the rapid growth in network scales and complexity, more and more network configurationsand applied features are required. When a module on a device is faulty, a great number of alarmsmay be generated on one or more devices. The alarms, however, may be lost when being sentto the NMS due to limited capability of handling alarms on the devices or the NMS. As a result,certain needed alarms cannot be displayed, which inconveniences network management. Tocollect valid fault information on the NMS, configure the alarm severity, alarm reporting delayfunction to efficiently manage and report alarms in a centralized manner.

5.2 Default ConfigurationThis section describes default parameter settings of the device.

Table 5-1 Default configuration of fault management


Alarm reporting delay function Enabled

5.3 Configuring Alarm ManagementAlarm management includes setting alarm severities, and enabling alarm reporting delay.


Before configuring alarm management, complete the following task:

Powering on the device and ensuring a successful self-check

5.3.1 Setting the Alarm Severity

Context

The system defines default alarm severity for each alarm. Users can change the alarm severity.When receiving alarms reported by a device, the NMS can configure filtering rules to displayonly alarms of a specified severity.

Alarm severities are defined as follows:l Critical: indicates that a fault affecting services has occurred and it must be rectified

immediately. For example, a critical alarm is generated to notify users that a managed objectfails to work and the fault must be rectified.

l Major: indicates that services are being affected and related measures need to be takenurgently. For example, a major alarm is generated to notify users that performance of a



65

managed object seriously degrades and all the capabilities of the managed object must berestored.

l Minor: indicates that a fault occurs but does not affect services. To avoid more seriousfaults that affect services, related measures must be taken.

l Warning: indicates that a potential or impending service-affecting fault is detected beforeany significant effect has been felt. Take corrective actions to diagnose and rectify the fault.

Procedure



Step 2 Run:alarm

The alarm view is displayed.

Step 3 (Optional) Run:display alarm information [ name alarm-name ]

The alarm severity is displayed.

Step 4 Run:alarm alarm-name severity severity

The alarm severity is changed.

The system has defined default alarm severity for each alarm.

Step 5 Run:commit


----End

5.3.2 Configuring the Alarm Reporting Delay Function

ContextWhen an alarm is reported repeatedly, users cannot locate faults in an efficient manner. Afterthe alarm reporting delay function is enabled and the delay is configured, a large number ofinvalid alarms are prevented from being reported.

After the alarm reporting delay function is enabled,

l If no clear alarm is generated during the period, the alarm is reported to the NMS when theperiod expires.

l If a clear alarm is generated during this period, the alarm and its clear alarm are both deletedfrom the alarm queue and will not be reported to the NMS.

Procedure

Step 1 Run:



66

system-view


Step 2 Run:alarm

The alarm view is displayed.

Step 3 Run:delay-suppression enable

The alarm reporting delay function is enabled.

By default, the alarm reporting delay function is enabled.

Step 4 (Optional) Run:suppression alarm alarm-name { cause-period cause-seconds | clear-period clear-seconds }

The delay in reporting alarms is configured.

The system defines a default delay in reporting alarms.

NOTE

l To set the delay in reporting an active alarm, select the cause-period parameter. To set the delay in reportinga clear alarm, select the clear-period parameter.

l To view the default delay in reporting alarms, run the undo suppression alarm alarm-name { cause-period | clear-period } and display alarm information [ name alarm-name ] commands in sequence.

Step 5 Run:commit


----End


Contextl Run the display alarm information [ name alarm-name ] command to view the specified

alarm configuration.l Run the display this command in the alarm view to view the alarm configuration.

5.4 MaintenanceThis section describes how to monitor and clear alarms.



67

5.4.1 Clearing Alarms

Context

CAUTIONThe cleared alarm statistics cannot be restored. Confirm the action before you run the command.

Procedurel Clears hardware alarms.

– Run:clear device alarm hardware { all | index index | slot slot-id } { no-trap | send-trap }Hardware alarms are cleared.

l Clearing active alarms or alarm statistics.


2. Run:alarmThe alarm view is displayed.

3. Clearing alarms– Run:

clear alarm active { all | sequence-number sequence-number }Active alarms are cleared.

– Run:reset statistics [ name alarm-name ]The alarm statistics are cleared.

----End

5.4.2 Monitoring Alarms

Procedurel Run:

display alarm active [ verbose ]

Active alarms are displayed.l Run:

display alarm information [ name alarm-name ]

The alarm configuration is displayed.l Run:

display alarm statistics [ name alarm-name ]



68

The alarm statistics are displayed.l Run:

display device alarm hardware [ slot slot-id ]

The hardware alarms on the device are displayed.l Run:

display alarm history [ verbose ]

The historical alarms are displayed.

----End

5.5 Configuration ExamplesThis section describes fault management configurations based on the configuration flowchart,including networking requirements, configuration roadmap, and configuration procedure.

5.5.1 Example for Configuring Alarm Management

Networking RequirementsAs shown in Figure 5-1, the route between the device and the NMS is reachable. Users want toview alarms generated by the device on the NMS in real time. Users must monitor the LinkDownalarm to ensure the normal interconnection of the device.

Figure 5-1 Networking for configuring alarm management

NM Station Switch11.1.1.2/2410.1.1.1/24

Network


1. Configure the alarm severity to critical, allowing users to monitor LinkDown alarms onthe NMS in real time based on the alarm filtering rules.s

2. Configure the alarm reporting delay function to prevent repetitive or flapping alarms frombeing reported to the NMS.

Procedure

Step 1 Configure an SNMPv3 user and an NMS host.<HUAWEI> system-view[~HUAWEI] snmp-agent[~HUAWEI] snmp-agent sys-info version v3[~HUAWEI] snmp-agent group v3 group1 privacy[~HUAWEI] snmp-agent usm-user v3 user1 group1 authentication-mode md5 pwd123456 privacy-mode des56 pri123456[~HUAWEI] snmp-agent target-host host-name nms trap address udp-domain 10.1.1.1



69

params securityname user1 v3 privacy[~HUAWEI] snmp-agent trap enable[~HUAWEI] commit

Step 2 Set the severity for the linkDown alarm to critical.[~HUAWEI] alarm[~HUAWEI-alarm] alarm linkDown severity critical[~HUAWEI-alarm] commit

Step 3 Enable the alarm reporting delay function.[~HUAWEI-alarm] delay-suppression enable[~HUAWEI-alarm] suppression alarm linkDown cause-period 5[~HUAWEI-alarm] suppression alarm linkDown clear-period 15[~HUAWEI-alarm] commit

NOTE

By default, the alarm reporting delay function is enabled.


# Run the display alarm information command to view the alarm configuration.

<HUAWEI> display alarm information name linkDown--------------------------------------------------------------------------------Feature : IFNET AlarmName : linkDown AlarmId : 0x8520003 Severity : Critical Cause Suppress Time : 5 Clear Suppress Time : 15 --------------------------------------------------------------------------------

----End

Configuration Filesl Configuration file of the Switch

#snmp-agentsnmp-agent local-engineid 800007DB0300259E957C20snmp-agent sys-info version v3snmp-agent group v3 group1 privacysnmp-agent target-host host-name nms trap address udp-domain 10.1.1.1 params securityname user1 v3 privacysnmp-agent usm-user v3 user1 group1 authentication-mode md5 %$%$Gmt[/c{_mJqJJa00s%J#,5,#%$%$ privacy-mode des56 %$%$@s`f)1@[WD3t^_M+)B+S,90'%$%$#snmp-agent trap enable#alarm suppression alarm linkDown cause-period 5 suppression alarm linkDown clear-period 15 alarm linkDown severity Critical#return



70

6 USB-based Deployment Configuration

About This Chapter

USB-based deployment simplifies the deployment process, reduces the deployment costs, andrelieves users from software commissioning.

6.1 USB-based Deployment OverviewIn site deployment, USB-based deployment allows you to save the upgrade files in a USB flashdrive, connect the USB flash drive to a device, and download the files from the USB flash driveto complete the automatic upgrade and configuration.

6.2 Making an Index FileBefore USB-based deployment, you must make an index file.

6.3 Configuring USB-based DeploymentTo use USB-based deployment, you must create a USB-based deployment index file, copy theindex file to the root directory of a USB flash drive, copy deployment files to the directoryspecified by the index file, and insert the USB flash drive into a device to start the USB-baseddeployment process.

6.4 (Optional) Disabling the USB-based Deployment Function

6.5 Configuration ExampleThis topic provides a USB-based deployment example. The configuration example includes thenetworking requirements, configuration roadmap and configuration procedure.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 6 USB-based Deployment Configuration


71

6.1 USB-based Deployment OverviewIn site deployment, USB-based deployment allows you to save the upgrade files in a USB flashdrive, connect the USB flash drive to a device, and download the files from the USB flash driveto complete the automatic upgrade and configuration.

As the network expands, more and more network devices are used and software commissioningcosts increase. USB-based deployment simplifies device deployment and reduces deploymentcosts. This function enables devices to be upgraded or configured automatically.

6.2 Making an Index FileBefore USB-based deployment, you must make an index file.

Procedure of Making an Index File

To edit the index file on the PC, perform the following operations:

1. Create a text file.

2. Edit the file based on the index file format.

3. Rename the file as smart_config.ini.

4. Copy the smart_config.ini file to the root directory of the USB flash drive.

Index File Format

The index file format is as follows:

BEGIN DC[GLOBAL CONFIG]SN=EMS_ONLINE_STATE=UPGRADEMODE=[DEVICEn DESCRIPTION]OPTION=ESN=MAC=DIRECTORY=SYSTEM-SOFTWARE=SYSTEM-CONFIG=SYSTEM-PAT=END DC

Table 6-1 Fields in the index file

Field Description

BEGIN DC Start tag of the index file. This field cannot be modified.

GLOBAL CONFIG Start tag of the global configuration. This field cannot bemodified.



72

Field Description

SN Data change time in the formatYearMonthDay.HourMinuteSecond.For example, the value 20110628.080910 indicates2011-06-28 08:09:10.NOTE

The SN field is a USB-based deployment flag. A device has adefault USB-based deployment flag. If the smart_config.ini fileexists in the USB flash drive, the device checks whether the defaultUSB-based deployment flag and the SN value in thesmart_config.ini file are the same. If they are different, the USB-based deployment process is triggered. If the deploymentsucceeds, the value of the default USB-based deployment flag onthe device is changed to the SN value in the smart_config.ini file.

EMS_ONLINE_STATE Whether the NMS is online, indicating whether a deviceregisters with the NMS after being deployed:l YES: The device registers with the NMS.l NO: The device does not register with the NMS.The default value is NO.NOTE

This field is optional. If this field does not exist or is empty, thedefault value is used.

UPGRADEMODE Upgrade mode:l AUTO: automatic model MANU: manual model DFT: production mode, which is used in production,

commissioning, and testing environment. In this mode,only the system software version is upgraded.

The default value is AUTO.NOTE


DEVICEn DESCRIPTION Start tag of the file description. n indicates the devicenumber and starts from 0.

OPTION Whether file information is valid:l OK: validl NOK: invalidThe default value is OK.NOTE




73

Field Description

ESN Serial number of a device. If the value of this field isDEFAULT, the index file is applicable to all devices.Otherwise, the index file is applicable to a specific device.The default value is DEFAULT.NOTE


MAC Device MAC address, in XXXX-XXXX-XXXX format. Xis a hexadecimal number. If the value of this field isDEFAULT, the index file is applicable to all devices.Otherwise, the index file is applicable to a specific device.The default value is DEFAULT.NOTE


DIRECTORY Path for storing deployment files.l If the value is DEFAULT, the deployment files are

stored in the root directory of the USB flash drive.l If the value is /abc, the deployment files are stored in

the abc directory.The default value is DEFAULT.NOTE


SYSTEM-SOFTWARE System software file with file name extension .cc.NOTE

This field is optional.

SYSTEM-CONFIG Configuration file with file name extension .cfg or .zip.NOTE


If this field has a value, the MAC field cannot be empty or default.

SYSTEM-PAT Patch file with file name extension .pat.NOTE


END DC End tag of the index file.

Examples

Example 1

You need to create an index file for upgrading one device, and the requirements are as follows:

l Data is changed at 08:09:10 on June 28, 2011.



74

l The device does not register with the NMS.l The device MAC address is 0018-0303-1234.l The system software system-software.cc, the configuration file system-config.zip, and

the patch file system-pat.pat are stored in the root directory of the USB flash drive.

The index file that meets the preceding requirements is as follows:

BEGIN DC[GLOBAL CONFIG]SN=20110628.080910EMS_ONLINE_STATE=NOUPGRADEMODE=AUTO[DEVICE0 DESCRIPTION]OPTION=OKESN=DEFAULTMAC=0018-0303-1234DIRECTORY=DEFAULTSYSTEM-SOFTWARE=system-software.ccSYSTEM-CONFIG=system-config.zipSYSTEM-PAT=system-pat.patEND DC

Example 2You need to create an index file for upgrading multiple devices to the same software version,and the requirements are as follows:l Data is changed at 08:09:10 on June 28, 2011.l The device does not register with the NMS.l The system software system-software.cc is stored in the root directory of the USB flash

drive.


BEGIN DC[GLOBAL CONFIG]SN=20110628.080910EMS_ONLINE_STATE=NOUPGRADEMODE=AUTO[DEVICE0 DESCRIPTION]OPTION=OKESN=DEFAULTMAC=DEFAULTDIRECTORY=DEFAULTSYSTEM-SOFTWARE=system-software.ccEND DC

Example 3You need to create an index file for two devices with different description information, and therequirements are as follows:l Data is changed at 08:09:10 on June 28, 2011.l The device does not register with the NMS.l The MAC address of the first device is 0018-0303-1234.l The MAC address of the second device is 0018-0303-5678.l The system software system-software.cc and the configuration file system-config.zip are

stored in the root directory of the USB flash drive. The first device does not need to loadthe configuration file while the second device must load the configuration file.



75


BEGIN DC[GLOBAL CONFIG]SN=20110628.080910EMS_ONLINE_STATE=NOUPGRADEMODE=AUTO[DEVICE0 DESCRIPTION]OPTION=OKESN=DEFAULTMAC=0018-0303-1234DIRECTORY=DEFAULTSYSTEM-SOFTWARE=system-software.cc[DEVICE1 DESCRIPTION]OPTION=OKESN=DEFAULTMAC=0018-0303-5678DIRECTORY=DEFAULTSYSTEM-SOFTWARE=system-software.ccSYSTEM-CONFIG=system-config.zipEND DC

6.3 Configuring USB-based DeploymentTo use USB-based deployment, you must create a USB-based deployment index file, copy theindex file to the root directory of a USB flash drive, copy deployment files to the directoryspecified by the index file, and insert the USB flash drive into a device to start the USB-baseddeployment process.

Background InformationWhen using USB-based deployment, pay attention to the following points:l The file system format of a USB flash drive must be FAT32 and its interface must be

standard USB2.0.l Use a USB flash drive that is certificated by Huawei to ensure the compatibility between

the USB flash drive and devices.l To write data to a USB flash drive, disable the write-protection function.l Before USB-based deployment, ensure that the device can start properly and has sufficient

space for saving deployment files.l Only one USB flash drive can be inserted into a device each time.l USB-based deployment files include the index file, system software, configuration file, and

patch file. The index file is mandatory. At least one type of other files must exist.l Do not power off the device during file copy; otherwise, the upgrade fails or even the device

cannot start.l Do not remove the USB flash drive before the upgrade is complete; otherwise, the data in

the USB flash drive may be damaged.l USB-based deployment cannot be used to deploy multiple stack devices simultaneously.

Pre-configuration Tasksl The device has been powered on and the self-check is successful.



76

Procedure1. Create an index file.

For details, see 6.2 Making an Index File.

2. Save the index file in the root directory of a USB flash drive, and copy deployment files tothe specified directory.

The DIRECTORY field in the index file specifies the path for storing deployment files.

l If the value is DEFAULT, the deployment files are stored in the root directory of theUSB flash drive.

l If the value is /abc, the deployment files are stored in the abc directory.

3. Insert the USB flash drive into a device to start the deployment process.

Based on the description information in the smart_config.ini file, the system first copiesdeployment files from the USB flash drive to the default storage media (If the system failedto copy files, the deployment indicator is steady red and the deployment failed), set thesystem software and configuration file as files to be loaded during next system startup, andautomatically restarts.

Checking the Configurationl Observe the ACT indicator to determine the USB-based deployment status:

– Steady green: USB-based deployment is successful.

– Blinking green: USB-based deployment is in progress.

– Steady red: USB-based deployment failed.

NOTE

Verify that USB-based deployment is successful and remove the USB flash drive. The USB-baseddeployment process is complete.

l View the USB-based deployment reports to learn about the deployment result.

After the deployment is complete, the system generates the usbload_verify.txt orusbload_error.txt files, containing the success information and error informationrespectively. The report files are stored in the root directory of the USB flash drive.

The content and format of the usbload_verify.txt and usbload_error.txt files are asfollows:===================================================Time : 2011-10-29 10:30:50MAC Address : 0e-0f-22-01-02-03System Name : CE6850Description : USB-based deployed succeeded.===================================================

Table 6-2 USB-based deployment report description

Item Description

Time Date and time when the information isgenerated.

MAC Address MAC address of a device.

System Name Device model.



77

Item Description

Description USB-based deployment reportinformation.

6.4 (Optional) Disabling the USB-based DeploymentFunction

ContextBy default, the USB-based deployment function is enabled on a device, and the device can beupgraded once a qualified USB flash drive is connected to the device. To enhance device securityand avoid service interruption caused by unnecessary version upgrades, disable the USB-baseddeployment. After the USB-based deployment function is disabled, the device cannot beupgraded using any qualified USB flash drive.

Procedure


The system view is displayed:

Step 2 Run:set device usb-deployment disable

The USB-based deployment function is disabled.

By default, the USB-based deployment function is enabled.

Step 3 Run:commit


----End

6.5 Configuration ExampleThis topic provides a USB-based deployment example. The configuration example includes thenetworking requirements, configuration roadmap and configuration procedure.

6.5.1 Example for Configuring USB-based Deployment

Networking RequirementsA user must upgrade two devices without the software commissioning engineers being onsite.The requirements are as follows:l The device can start properly and has sufficient space for saving deployment files.



78

l The devices must be upgraded at 2011-06-28 08:09:10.l The device does not register with the NMS.l The MAC address of the first device is 0018-0303-1234. The name of the system software

is V100R001C00.cc. No configuration file needs to be loaded.l The MAC address of the second device is 0018-0303-5678. The name of the system

software is V100R001C00.cc. The configuration file config.zip must be loaded.


1. Create the index file smart_config.ini.2. Save the smart_config.ini file in the root directory of a USB flash drive, and copy

deployment files to the directory specified by the index file.3. Insert the USB flash drive into a device to start the deployment process.

Procedure

Step 1 Create the index file smart_config.ini.# Create an index file and name it smart_config.ini. The content and format of the index fileare as follows:BEGIN DC[GLOBAL CONFIG]SN=20110628.080910EMS_ONLINE_STATE=NOUPGRADEMODE=AUTO[DEVICE0 DESCRIPTION]OPTION=OKMAC=0018-0303-1234DIRECTORY=DEFAULTSYSTEM-SOFTWARE=V100R001C00.cc[DEVICE1 DESCRIPTION]OPTION=OKMAC=0018-0303-5678DIRECTORY=DEFAULTSYSTEM-SOFTWARE=V100R001C00.ccSYSTEM-CONFIG=config.zipEND DC

Step 2 Save the smart_config.ini file in the root directory of a USB flash drive, and copy theV100R001C00.cc and config.zip files to the directory specified by the index file.

Step 3 Insert the USB flash drive into the two devices in sequence.

Step 4 Observe the deployment indicator to monitor the USB-based deployment process:l If any deployment file is not found, the deployment indicator is off.l If deployment files are found but not valid, the deployment failed and the deployment

indicator is steady red.l If deployment files are found and valid, the USB-based deployment starts and the deployment

indicator blinks green.Based on the description information in the smart_config.ini file, the system first copiesdeployment files from the USB flash drive to the default storage media (If the system failedto copy files, the deployment indicator is steady red and the deployment failed), set the systemsoftware and configuration file as files to be loaded during next system startup, andautomatically restarts.



79

Step 5 Verify the configuration.l After the device restarts, the system checks the deployment status. If the deployment indicator

is steady green, USB-based deployment succeeds.If the deployment indicator is steady red,USB-based deployment fails.

NOTE

Verify that USB-based deployment is successful and remove the USB flash drive. The USB-baseddeployment process is complete.

l After the deployment is complete, the system generates the usbload_verify.txt orusbload_error.txt files, containing the success information and error informationrespectively. The report files are stored in the root directory of the USB flash drive.

----End



80

7 Mirroring Configuration

About This Chapter

Packet mirroring copies packets to a specified destination so that you can ayalyze packets tomonitor the network and rectify faults.

NOTE

The terms mirrored port, port mirroring, traffic mirroring, and mirroing in this manual are mentioned onlyto describe the product's function of communication error or failure detection, and do not involve collectionor processing of any personal information or communication data of users.

7.1 Packet Mirroring OverviewPacket mirroring copies the packets on a mirrored port (source port) to an observing port(destination port).

7.2 Packet Mirroring Features Supported by the DeviceThe device supports port mirroring and traffic mirroring.

7.3 Configuring Local Port MirroringAfter local port mirroring is configured, packets passing through mirrored ports are copied to alocal monitoring device for analysis and monitoring.

7.4 Configuring Remote Port MirroringAfter remote port mirroring is configured, packets passing through mirrored ports are copied toa remote monitoring device for analysis and monitoring.

7.5 Configuring Local Traffic MirroringAfter local traffic mirroring is configured, specified packets passing through mirrored ports arecopied to a local monitoring device for analysis and monitoring.

7.6 Configuring Remote Traffic MirroringAfter remote traffic mirroring is configured, specified packets passing through mirrored portsare copied to a remote monitoring device for analysis and monitoring.

7.7 Configuration ExamplesThis section provides several configuration examples of packet mirroring, including networkrequirements, configuration roadmap, and configuration procedures.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 7 Mirroring Configuration


81

7.1 Packet Mirroring OverviewPacket mirroring copies the packets on a mirrored port (source port) to an observing port(destination port).

During network maintenance, maintenance personnel need to capture and analyze packets (forexample, when there are suspicious attack packets). However, these operations always affectpacket forwarding.

Packet mirroring copies packets on a mirrored port to an observing port so that you can analyzepackets copied to the destination port by a monitoring device to monitor the network and rectifyfaults.

Conceptsl Mirrored port

All the packets or packets matching the traffic classification rule passing through a mirroredport are copied to an observing port.

l Observing portAn observing port is connected to a monitoring device and is used to export the packetscopied from a mirrored port.

7.2 Packet Mirroring Features Supported by the DeviceThe device supports port mirroring and traffic mirroring.

Mirroring Specificationsl A maximum of eight observing ports can be configured on the switch, and only one can be

used at one time. An observing port can mirror both incoming and outgoing traffic.l The switch can mirror packets on multiple ports to one observing port.l A port cannot be configured as both a mirrored port and an observing port. An Ethernet or

Eth-Trunk port can be configured as a mirrored port. An Eth-Trunk member port cannotbe configured as an observing port.

l In a stack, physical member interfaces do not support inter-chassis mirroring; the mirroredport and physical member interface that functions as the observing port must be on the samedevice.

l If the mirrored port is an access port, the outgoing packets mirrored to an observing portcarry VLAN tags, different from original packets.

l The following configurations for outgoing traffic do not take effect for mirrored traffic:– Configure an ACL in which the rule is deny.– Configure traffic policing.– Configure WRED profiles.– Configure the traffic shaping rate.– Configure the queue scheduling mode.Outgoing packets discarded on the mirrored port are still mirrored to the observing port.



82

Port MirroringA packet passing through a mirrored port is copied and then sent to a specified observing portfor analysis and monitoring, as shown in Figure 7-1.

Figure 7-1 Networking diagram of port mirroring

Observing port

Monitoring device

Mirrored port

Mirrored port

Packet flowCopied packet flow

Port

Port mirroring can be performed as follows:l Inbound: mirroring the packets that are received by the mirrored portl Outbound: mirroring the packets that are sent by the mirrored portl Bidirectional: mirroring the packets that are received and sent by the mirrored port

Port mirroring is classified into local port mirroring and remote port mirroring:l In local port mirroring, a monitoring device is directly connected to an observing port, as

shown in Figure 7-2.

Figure 7-2 Networking diagram of local port mirroring

Mirrored portObserving portPacket flowCopied packet flow

Monitoring device

Host Switch

l In remote port mirroring, the monitoring device and the observing port are connectedthrough a Layer 2 or Layer 3 network.– Remote switched port analyzer (RSPAN): The device encapsulates packets passing

through mirrored ports into VLAN packets, and the observing port broadcasts theVLAN packets in the RSPAN VLAN to forward packets to the monitoring device, asshown in Figure 7-3.



83

Figure 7-3 Networking diagram of Layer 2 RSPAN

SwitchA

Monitoring device

SwitchB SwitchC

Host


– Encapsulated Remote SPAN (ERSPAN): The device encapsulates mirrored packetspassing through mirrored ports into Generic Routing Encapsulation (GRE) packets andforwards the GRE packets to the monitoring device through a Layer 3 IP network, asshown in Figure 7-4.

NOTE

In ERSPAN mode, the device cannot decapsulate ERSPAN packets.

Figure 7-4 Networking diagram of Layer 3 ERSPAN

SwitchA

Monitoring device

SwitchC

Host

IP network


Traffic MirroringTraffic mirroring is used to copy specified packets passing through a mirrored port to theobserving port for analysis and monitoring. In traffic mirroring, traffic policies containing thetraffic behavior are applied to mirrored ports. If packets passing through a mirrored port matchthe traffic classification rule, the packets are copied to the observing port, as shown in Figure7-5.



84

Figure 7-5 Schematic diagram of traffic mirroring

Port

Traffic classifier

Mirrored port

Mirrored port

Observing port

Monitoring device

Packet flowCopied packet flow

Similar to port mirroring, traffic mirroring is also classified into local traffic mirroring andremote traffic mirroring.

7.3 Configuring Local Port MirroringAfter local port mirroring is configured, packets passing through mirrored ports are copied to alocal monitoring device for analysis and monitoring.

Pre-configuration TasksBefore configuring local port mirroring, complete the following task:

Ensuring that the link layer protocol status of ports is Up

7.3.1 Configuring a Local Observing Port

ContextIn local mirroring, the monitoring device is directly connected to the observing port.

Procedure



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

A local observing port is configured.

By default, no local observing port is configured.



85

Step 3 Run:commit


----End

7.3.2 Configuring a Mirrored Port

ContextA mirrored port can be an Ethernet port or an Eth-Trunk port.

NOTE

l If an Eth-Trunk is configured as a mirrored port, its member ports cannot be configured as mirrored ports.

l If a member port of an Eth-Trunk is configured as a mirrored port, the Eth-Trunk cannot be configured asa mirrored port.

Procedure





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

A mirrored port is configured.

In the preceding command, observe-port-index specifies an observing port index. The value ofthis parameter must be the same as the value set in 7.3.1 Configuring a Local ObservingPort.

NOTE

To improve system performance, cancel the port mirroring configuration when you do not need to monitorpackets.

Step 4 Run:commit


----End


Procedurel Run the display observe-port command to check the observing port.



86

l Run the display port-mirroring command to check the port mirroring configuration.

----End

7.4 Configuring Remote Port MirroringAfter remote port mirroring is configured, packets passing through mirrored ports are copied toa remote monitoring device for analysis and monitoring.

Pre-configuration TasksBefore configuring remote port mirroring, complete the following tasks:l Ensuring that the observing port can communicate with the monitoring device on a Layer

2 or Layer 3 network

7.4.1 Configuring a Remote Observing Port

ContextIn remote mirroring, the monitoring device and the observing port are connected over a Layer2 or Layer 3 network. Remote mirroring is classified into the following types:l Layer 2 remote mirroring: The device encapsulates mirrored packets into VLAN packets

so that the mirrored packets can be transmitted to the remote monitoring device over aLayer 2 network.

l Layer 3 remote mirroring: The device encapsulates mirrored packets into GRE packets sothat the mirrored packets can be transmitted to the remote monitoring device over a Layer3 network.

Procedure



Step 2 Configure a remote observing port.

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

A remote observing port is configured for Layer 2 remote mirroring.

l Run:observe-port [ observe-port-index ] interface interface-type interface-number destination-ip dest-ip-address source-ip source-ip-address [ dscp dscp-value | vlan vlan-id ] *


By default, no remote observing port is configured.

Step 3 Run:commit



87


----End

7.4.2 Configuring a Mirrored Port

ContextA mirrored port can be an Ethernet port or an Eth-Trunk port.

NOTE

l If an Eth-Trunk is configured as a mirrored port, its member ports cannot be configured as mirrored ports.l If a member port of an Eth-Trunk is configured as a mirrored port, the Eth-Trunk cannot be configured as

a mirrored port.

Procedure





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

A mirrored port is configured.

In the preceding command, observe-port-index specifies an observing port index. The value ofthis parameter must be the same as the value set in 7.4.1 Configuring a Remote ObservingPort.

NOTE

The mirrored port cannot be added to the RSPAN VLAN.To improve system performance, cancel the port mirroring configuration when you do not need to monitorpackets.

Step 4 Run:commit


----End


Procedurel Run the display observe-port command to check the observing port.l Run the display port-mirroring command to check the port mirroring configuration.

----End



88

7.5 Configuring Local Traffic MirroringAfter local traffic mirroring is configured, specified packets passing through mirrored ports arecopied to a local monitoring device for analysis and monitoring.

Pre-configuration TasksBefore configuring local traffic mirroring, complete the following task:

Ensuring that the link layer protocol status of ports is Up

7.5.1 Configuring a Local Observing Port

ContextIn local mirroring, the monitoring device is directly connected to the observing port.

Procedure



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

A local observing port is configured.

By default, no local observing port is configured.

Step 3 Run:commit


----End

7.5.2 Configuring a Traffic Classifier

ContextConfigure complex traffic classification by selecting proper traffic classification rules. Fordetails, see Configuring a Traffic Classifier in the CloudEngine 6800&5800 Series SwitchesConfiguration Guide - QoS.

7.5.3 Configuring a Traffic Behavior

ContextBy configuring the traffic behavior, the device mirrors all the packets matching trafficclassification rules to the observing interface.



89

Procedure



Step 2 Run:traffic behavior behavior-name

A traffic behavior is configured and its view is displayed.

Step 3 Run:mirroring observe-port observe-port-index

Traffic matching the rules is mirrored to the specified observing port.

In the preceding command, observe-port-index specifies an observing port index. The value ofthis parameter must be the same as the value set in 7.5.1 Configuring a Local ObservingPort.

Step 4 Run:commit


----End

7.5.4 Configuring a Traffic Policy

Procedure



Step 2 Run:traffic policy policy-name

A traffic policy is created and its view is displayed.

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

The traffic policy is associated with the traffic classifier and the traffic behavior containing trafficmirroring.

In the preceding command, classifier-name specifies a traffic classifier. The value of thisparameter must be the same as the value set in 7.5.2 Configuring a Traffic Classifier. Thebehavior-name parameter specifies a traffic behavior. The value of this parameter must be thesame as the value set in 7.5.3 Configuring a Traffic Behavior.

Step 4 Run:commit


----End



90

7.5.5 Applying a Traffic Policy

Context

You can apply a traffic policy bound to traffic behaviors and traffic classifiers to the system,interface, or VLAN. For details, see Applying the Traffic Policy in the CloudEngine 6800&5800Series Switches Configuration Guide - QoS.


Procedurel Run the display observe-port command to check the observing port.l Run the display traffic behavior [ behavior-name ] command to check the traffic behavior

configuration.l Run the display traffic classifier [ classifier-name ] command to check the traffic classifier

configuration.l Run the display traffic policy [ policy-name [ classifier classifier-name ] ] command to

check the traffic policy configuration.l Run the display traffic-policy applied-record [ policy-name ] command to check the

application record of a specified mirroring policy.

----End

7.6 Configuring Remote Traffic MirroringAfter remote traffic mirroring is configured, specified packets passing through mirrored portsare copied to a remote monitoring device for analysis and monitoring.


Before configuring remote traffic mirroring, complete the following tasks:l Ensuring that the observing port can communicate with the monitoring device on a Layer

2 or Layer 3 network

7.6.1 Configuring a Remote Observing Port

Context

In remote mirroring, the monitoring device and the observing port are connected over a Layer2 or Layer 3 network. Remote mirroring is classified into the following types:l Layer 2 remote mirroring: The device encapsulates mirrored packets into VLAN packets

so that the mirrored packets can be transmitted to the remote monitoring device over aLayer 2 network.

l Layer 3 remote mirroring: The device encapsulates mirrored packets into GRE packets sothat the mirrored packets can be transmitted to the remote monitoring device over a Layer3 network.



91

Procedure




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


l Run:observe-port [ observe-port-index ] interface interface-type interface-number destination-ip dest-ip-address source-ip source-ip-address [ dscp dscp-value | vlan vlan-id ] *


By default, no remote observing port is configured.

Step 3 Run:commit


----End

7.6.2 Configuring a Traffic Classifier

ContextConfigure complex traffic classification by selecting proper traffic classification rules. Fordetails, see Configuring a Traffic Classifier in the CloudEngine 6800&5800 Series SwitchesConfiguration Guide - QoS.

7.6.3 Configuring a Traffic Behavior

ContextBy configuring the traffic behavior, the device mirrors all the packets matching trafficclassification rules to the observing interface.

Procedure



Step 2 Run:traffic behavior behavior-name

A traffic behavior is configured and its view is displayed.



92

Step 3 Run:mirroring observe-port observe-port-index

Traffic matching the rules is mirrored to the specified observing port.

In the preceding command, observe-port-index specifies an observing port index. The value ofthis parameter must be the same as the value set in 7.6.1 Configuring a Remote ObservingPort.

Step 4 Run:commit


----End

7.6.4 Configuring a Traffic Policy

Procedure



Step 2 Run:traffic policy policy-name

A traffic policy is created and its view is displayed.

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

The traffic policy is associated with the traffic classifier and the traffic behavior containing trafficmirroring.

In the preceding command, classifier-name specifies a traffic classifier. The value of thisparameter must be the same as the value set in 7.6.2 Configuring a Traffic Classifier. Thebehavior-name parameter specifies a traffic behavior. The value of this parameter must be thesame as the value set in 7.6.3 Configuring a Traffic Behavior.

Step 4 Run:commit


----End

7.6.5 Applying a Traffic Policy

ContextYou can apply a traffic policy bound to traffic behaviors and traffic classifiers to the system,interface, or VLAN. For details, see Applying the Traffic Policy in the CloudEngine 6800&5800Series Switches Configuration Guide - QoS.




93

Procedurel Run the display observe-port command to check the observing port.l Run the display traffic behavior [ behavior-name ] command to check the traffic behavior

configuration.l Run the display traffic classifier [ classifier-name ] command to check the traffic classifier

configuration.l Run the display traffic policy [ policy-name [ classifier classifier-name ] ] command to

check the traffic policy configuration.l Run the display traffic-policy applied-record [ policy-name ] command to check the

application record of a specified mirroring policy.

----End

7.7 Configuration ExamplesThis section provides several configuration examples of packet mirroring, including networkrequirements, configuration roadmap, and configuration procedures.

7.7.1 Example for Configuring Local Port Mirroring

Networking RequirementsAs shown in Figure 7-6, HostA is connected to 10GE1/0/1 on SwitchA, and Server is directlyconnected to 10GE1/0/2 on SwitchA.

Users want to use the monitoring device (Server) to monitor packets sent from HostA.

Figure 7-6 Networking diagram of local port mirroring

10GE1/0/2

SwitchAHostA

10GE1/0/1

Server


1. Configure 10GE1/0/2 on SwitchA as the local observing port so that Server can receivemirrored packets.

2. Configure 10GE1/0/1 on SwitchA as the mirrored port to monitor packets passing throughthe mirrored port.

Procedure

Step 1 Configure an observing port.

# Configure 10GE1/0/2 on SwitchA as the local observing port.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA



94

[~HUAWEI] commit[~SwitchA] observe-port 1 interface 10ge 1/0/2[~SwitchA] commit

Step 2 Configure a mirrored port.

# Configure 10GE1/0/1 on SwitchA as the mirrored port to monitor packets sent from HostA.

[~SwitchA] interface 10ge 1/0/1[~SwitchA-10GE1/0/1] port-mirroring observe-port 1 inbound[~SwitchA-10GE1/0/1] commit[~SwitchA-10GE1/0/1] quit

Step 3 Verify the configurations.

# Check the observing port configuration.

<SwitchA> display observe-port ---------------------------------------------------------------------- Index : 1 Interface: 10GE1/0/2 ----------------------------------------------------------------------

# Check the mirrored port configuration.

<SwitchA> display port-mirroring Port-mirror: ---------------------------------------------------------------------- Mirror-port Direction Observe-port ---------------------------------------------------------------------- 1 10GE1/0/1 Inbound 10GE1/0/2 ----------------------------------------------------------------------

----End


#sysname SwitchA#observe-port 1 interface 10GE1/0/2#interface 10GE1/0/1 port-mirroring observe-port 1 inbound#return

7.7.2 Example for Configuring Layer 2 Remote Port Mirroring

Networking RequirementsAs shown in Figure 7-7, HostA is connected to 10GE1/0/2 on SwitchA, and Server is connectedto 10GE1/0/1 on SwitchC. SwitchA and SwitchC are connected over a Layer 2 network.

Users want to use the monitoring device (Server) to remotely monitor packets sent from HostA.



95

Figure 7-7 Networking diagram of Layer 2 remote port mirroring

10GE1/0/110GE1/0/1

10GE1/0/210GE1/0/2

VLAN2 VLAN2

SwitchA

SwitchB

SwitchC

10GE1/0/2 10GE1/0/1

HostA Server


1. Configure ports so that devices can communicate on Layer 2.2. Configure 10GE1/0/1 on SwitchA as the remote observing port so that mirrored packets

can be forwarded to Server over the Layer 2 network.3. Configure 10GE1/0/2 on SwitchA as the mirrored port to monitor packets passing through

the mirrored port.

ProcedureStep 1 Configure ports so that devices can communicate on Layer 2.

# Configure SwitchA.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] vlan batch 2 to 3[~SwitchA] interface 10ge 1/0/1[~SwitchA-10GE1/0/1] port link-type trunk[~SwitchA-10GE1/0/1] port trunk allow-pass vlan 2[~SwitchA-10GE1/0/1] quit[~SwitchA] interface 10ge 1/0/2[~SwitchA-10GE1/0/2] port default vlan 3[~SwitchA-10GE1/0/2] quit[~SwitchA] commit

# Configure SwitchB.

<HUAWEI> system-view[~HUAWEI] sysname SwitchB[~HUAWEI] commit[~SwitchB] vlan 2[~SwitchB-vlan2] quit[~SwitchB] interface 10ge 1/0/1[~SwitchB-10GE1/0/1] port link-type trunk[~SwitchB-10GE1/0/1] port trunk allow-pass vlan 2[~SwitchB-10GE1/0/1] quit[~SwitchB] interface 10ge 1/0/2[~SwitchB-10GE1/0/2] port link-type trunk[~SwitchB-10GE1/0/2] port trunk allow-pass vlan 2[~SwitchB-10GE1/0/2] quit[~SwitchB] commit

# Configure SwitchC.



96

<HUAWEI> system-view[~HUAWEI] sysname SwitchC[~HUAWEI] commit[~SwitchC] vlan 2[~SwitchC-vlan2] quit[~SwitchC] interface 10ge 1/0/1[~SwitchC-10GE1/0/1] port default vlan 2[~SwitchC-10GE1/0/1] quit[~SwitchC] interface 10ge 1/0/2[~SwitchC-10GE1/0/2] port link-type trunk[~SwitchC-10GE1/0/2] port trunk allow-pass vlan 2[~SwitchC-10GE1/0/2] quit[~SwitchC] commit


# Configure 10GE1/0/1 on SwitchA as the remote observing port.

[~SwitchA] observe-port 1 interface 10ge 1/0/1 vlan 2[~SwitchA] commit


# Configure 10GE1/0/2 on SwitchA as the mirrored port.

[~SwitchA] interface 10ge 1/0/2[~SwitchA-10GE1/0/2] port-mirroring observe-port 1 inbound[~SwitchA-10GE1/0/2] quit[~SwitchA] commit



<SwitchA> display observe-port ---------------------------------------------------------------------- Index : 1 Interface: 10GE1/0/1 Vlan : 2 ----------------------------------------------------------------------



----End


#sysname SwitchA#vlan batch 2 to 3#observe-port 1 interface 10GE1/0/1 vlan 2#interface 10GE1/0/1 port link-type trunk port trunk allow-pass vlan 2#interface 10GE1/0/2



97

port default vlan 3 port-mirroring observe-port 1 inbound#return

l Configuration file of SwitchB#sysname SwitchB#vlan batch 2#interface 10GE1/0/1 port link-type trunk port trunk allow-pass vlan 2#interface 10GE1/0/2 port link-type trunk port trunk allow-pass vlan 2#return

l Configuration file of SwitchC#sysname SwitchC#vlan batch 2#interface 10GE1/0/1 port default vlan 2#interface 10GE1/0/2 port link-type trunk port trunk allow-pass vlan 2#return

7.7.3 Example for Configuring Layer 3 Remote Port Mirroring

Networking RequirementsAs shown in Figure 7-8, HostA is connected to 10GE1/0/2 on SwitchA, and Server is connectedto 10GE1/0/2 on SwitchB. HostA can Server are connected over a Layer 2 network, and routesbetween them are reachable.

Users want to use the monitoring device (Server) to remotely monitor packets sent from HostA.



98

Figure 7-8 Networking diagram of Layer 3 remote port mirroring

SwitchA

Server10.2.1.1/24

Network

SwitchB

HostA10.1.1.1/24

10GE1/0/2

10GE1/0/1

10GE1/0/2


1. Configure 10GE1/0/1 on SwitchA as the remote observing port so that mirrored packetscan be forwarded to Server over the Layer 3 network.

2. Configure 10GE1/0/2 on SwitchA as the mirrored port to monitor packets sent from HostA.

Procedure


# Configure 10GE1/0/1 on SwitchA as the Layer 3 remote observing port and set the destinationIP address to the Server IP address.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] observe-port interface 10ge 1/0/1 destination-ip 10.2.1.1 source-ip 10.1.1.1[~SwitchA] commit


# Configure 10GE1/0/2 on SwitchA as the mirrored port.

[~SwitchA] interface 10ge 1/0/2[~SwitchA-10GE1/0/2] port-mirroring observe-port 1 inbound[~SwitchA-10GE1/0/2] quit[~SwitchA] commit



<SwitchA> display observe-port ---------------------------------------------------------------------- Index : 1 Interface: 10GE1/0/1



99

Vlan : 0 Dscp : 0 Src-Ip : 10.1.1.1 Dst-Ip : 10.2.1.1 Src-Mac : 00-25-9e-37-ee-a5 Dst-Mac : ff-ff-ff-ff-ff-ff ----------------------------------------------------------------------



----End


#sysname SwitchA#observe-port 1 interface 10GE1/0/1 destination-ip 10.2.1.1 source-ip 10.1.1.1#interface 10GE1/0/2 port-mirroring observe-port 1 inbound#return

7.7.4 Example for Configuring Local Traffic Mirroring

Networking RequirementsAs shown in Figure 7-9, HostA is connected to 10GE1/0/1 on SwitchA, and Server is directlyconnected to 10GE1/0/2 on SwitchA.

Users want to use the monitoring device (Server) to monitor packets with the 802.1p priority of6 sent from HostA.

Figure 7-9 Networking diagram of local traffic mirroring

10GE1/0/2

SwitchAHostA

10GE1/0/1

Server


1. Configure 10GE1/0/2 on SwitchA as the local observing port so that Server can receivemirrored packets.

2. Configure a traffic classifier to match packets with the 802.1p priority of 6, and configurea traffic behavior to mirror packets to the observing port.



100

3. Configure a traffic policy, bind the traffic classifier and traffic behavior to the traffic policy,and apply the traffic policy to the inbound direction of 10GE1/0/1.

Procedure

Step 1 Configure an observing port.

# Configure 10GE1/0/2 on SwitchA as the observing port.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] observe-port 1 interface 10ge 1/0/2[~SwitchA] commit

Step 2 Configure a traffic classifier.

# Create a traffic classifier named c1 on SwitchA and set the traffic classification rule that onlypackets with the 802.1p priority of 6 can be matched.

[~SwitchA] traffic classifier c1[~SwitchA-classifier-c1] if-match 8021p 6[~SwitchA-classifier-c1] commit[~SwitchA-classifier-c1] quit

Step 3 Configure a traffic behavior.

# Create a traffic behavior named b1 on SwitchA and configure it.

[~SwitchA] traffic behavior b1[~SwitchA-behavior-b1] mirroring observe-port 1[~SwitchA-behavior-b1] commit[~SwitchA-behavior-b1] quit

Step 4 Configure a traffic policy and apply the traffic policy to the interface.

# Create a traffic policy named p1 on SwitchA, bind the traffic classifier and traffic behavior tothe traffic policy, and apply the traffic policy to the inbound direction of 10GE1/0/1 to monitorpackets with the 802.1p priority of 6 sent from HostA.

[~SwitchA] traffic policy p1[~SwitchA-trafficpolicy-p1] classifier c1 behavior b1[~SwitchA-trafficpolicy-p1] commit[~SwitchA-trafficpolicy-p1] quit[~SwitchA] interface 10ge 1/0/1[~SwitchA-10GE1/0/1] traffic-policy p1 inbound[~SwitchA-10GE1/0/1] commit[~SwitchA-10GE1/0/1] quit[~SwitchA] quit


# View the traffic classifier configuration.

<SwitchA> display traffic classifier c1 Traffic Classifier Information: Classifier: c1 Operator: OR Rule(s): if-match 8021p 6

# View the traffic policy configuration.

<SwitchA> display traffic policy p1 Traffic Policy Information: Policy: p1 Classifier: c1



101

Operator: OR Behavior: b1 Mirroring observe-port 1

----End


#sysname SwitchA#observe-port 1 interface 10GE1/0/2#traffic classifier c1 type or if-match 8021p 6#traffic behavior b1 mirroring observe-port 1#traffic policy p1 classifier c1 behavior b1#interface 10GE1/0/1 traffic-policy p1 inbound#return



102

8 iStack Configuration

About This Chapter

Multiple switches set up a stack to improve data forwarding capabilities and network reliability.

8.1 iStack OverviewIntelligent Stack (iStack) allows multiple stacking-capable switches to function as a singlelogical switch.

8.2 iStack Features Supported by the DeviceiStack features supported by the device include stack establishment, management, andmaintenance, dual-active detection, and fast stack upgrade.

8.3 Configuration NotesThis section describes precautions for configuring a stack.

8.4 Default ConfigurationThis section describes the default configurations of a stack and common stack parameters.

8.5 Configuring a StackYou can configure stack ports and parameters on member switches to set up a stack.

8.6 (Optional) Configuring Dual-active DetectionYou can configure dual-active detection to detect and deal with a dual-active scenario when astack splits.

8.7 Configuration ExamplesThis section describes stack configuration examples, including networking requirements,configuration roadmap, and configuration procedure.

CloudEngine 6800&5800 Series SwitchesConfiguration Guide - Device Management 8 iStack Configuration


103

8.1 iStack OverviewIntelligent Stack (iStack) allows multiple stacking-capable switches to function as a singlelogical switch.

Before a stack is set up, each switch is an independent entity and has its own IP address andMAC address. You need to manage the switches separately. After a stack is set up, the switchesin the stack form a logical entity. You can use a single IP address to manage and maintain allthe switches in the stack as shown in Figure 8-1. A stack can transmit a large amount of data,improve network reliability, and simplify network management.

Figure 8-1 iStack networking diagram

iStack

iStack Link

ConceptsFigure 8-2 shows the basic concepts involved in a stack.

Figure 8-2 Basic concepts involved in a stack

Domain 10

Master

Standby

Slave

Member ID = 1Priority = 10



Stack portPhysical member port

l Switch rolesEach switch in a stack is a member switch. Member switches are classified into thefollowing roles:– Master switch

The master switch manages the entire stack. A stack has only one master switch.– Standby switch

The standby switch is the backup to the master switch. A stack has only one standbyswitch.

– Slave switch



104

In a stack, all member switches except the master switch and standby switch are slaveswitches.

l Stack domainSwitches that connect to each other using stack links to form a stack belong to a stackdomain. To meet various networking requirements, you can configure multiple stacks ona network and use stack domain IDs to identify these stacks.

l Stack IDA stack ID, also called a member ID, is used to identify and manage member switches ina stack. All member switches in a stack have a unique stack ID.

l Stack priorityThe stack priority is an attribute of member switches, which helps determine the role ofmember switches in role election. A larger priority value indicates a higher priority. Themember switch with a higher stack priority has a higher probability of becoming the masterswitch.

l Physical member portSwitches connect to each other to form a stack using physical member ports.

l Stack portA stack port is a logical port that is bound to physical member ports to implement thestacking function. Each member switch has two stack ports, which are named Stack-Portn/1 and Stack-Portn/2. n specifies the stack ID of the member switch.

8.2 iStack Features Supported by the DeviceiStack features supported by the device include stack establishment, management, andmaintenance, dual-active detection, and fast stack upgrade.

NOTE

Currently, four switches can form a stack. CE6800 or CE5800 series switches can only form a stack with switchesof the same series. CE6800 and CE5800 series switches cannot form a stack.

Setting Up a StackTo use multiple switches to form a stack, connect physical member ports bound to the local stackport to those bound to the neighbor stack port, as shown in Figure 8-3. A stack port can be boundto multiple physical member ports to improve stack link bandwidth and reliability.

Figure 8-3 Stack networking diagram

iStack

iStack Link

Stack port Stack port

The stack contains multiple member switches, each of which has a role. During the setup of astack, member switches exchange packets to elect the master switch that manages the stack.

The rules for electing the master switch are as follows:



105

1. The switch that has started is preferred over the switch that is starting.2. The switch with higher stack priority is preferred.3. The switch with a later software version is preferred.4. The switch with a smaller MAC address is preferred.

The election results are compared one by one. In the case of the same election result, the nextrule is used until the master switch is elected.

The master switch collects member information, calculates the stack topology, and synchronizesthe stack topology to all the other member switches.l If member switches have the same stack ID, the master switch assigns a unique stack ID

to each of the member switches.l When the master and slave switches use different software versions, slave switches

synchronize the software version with the master switch, restart, and then join the stack.

The master switch elects a standby switch from slave switches as the standby switch. When themaster switch fails, the standby switch takes over all services from the master switch.

The rules for electing the standby switch are as follows:

1. The switch with higher stack priority is preferred.2. The switch with a smaller MAC address is preferred.


Connection TopologyA stack has two connection topologies: chain topology and ring topology, as shown in Figure8-4.

A ring topology is more reliable than a chain topology. When a link fault occurs in the chaintopology, the stack splits. When a link fault occurs in the ring topology, a chain topology isformed, which prevents stack services from being affected.

Figure 8-4 Stack connection topology

Chain topology Ring topology

Master SlaveStandby

Standby Slave

iStack

iStack

Slave

Master Slave

Managing and Maintaining a StackAfter a stack is set up, all member switches function as one logical switch on the network, andthe master switch manages the resources of all remember switches. You can log in to the stack



106

through the management network interface or serial interface of any member switch to manageand maintain the stack.

NOTE

When multiple management network ports are used in a stack, only one management network port can be usedfor login.

After a switch joins a stack, the interface number is in the format stack ID/subcard ID/interfacesequence number.

Interface Configuration CombinationPhysical member port configuration is saved in both the flash memory and configuration file ofa device. If the physical member port configuration in the flash memory is different from thatin the configuration file, for example, a new configuration file is specified, the physical memberport configuration in the flash memory combines with that in the configuration file. Rules forcombining the port configuration are as follows:l Only the configurations of physical member ports are combined.

As shown in Figure 8-5, SwitchA and SwitchB form a stack. SwitchA functions as themaster switch and specifies a new configuration file. After the stack is set up, the portconfigurations in the flash memory and configuration file of SwitchA are combined.

l If the port configurations in the flash memory and configuration file are different, the portconfiguration in the configuration file takes effect.In Figure 8-5, 10GE1/0/5 has the service configuration in the configuration file of SwitchA,so the stack configuration of 10GE1/0/5 is deleted.

l The port configuration of the slave switch combines with that of the master switch, and theport configuration of the master switch takes effect.In Figure 8-5, the configuration of 10GE2/0/2 on SwitchA conflicts with the portconfiguration of SwitchB. SwitchA functions as the master switch, so the port configurationof SwitchA takes effect after the port configurations of SwitchA and SwitchB are combined.

l After a stack is set up, the slave switch synchronizes the configuration file of the masterswitch to keep the same configuration as the master switch.In Figure 8-5, after a stack is set up, the configuration file of SwitchB is consistent withthat of SwitchA.



107

Figure 8-5 Interface configuration combination

#interface 10GE2/0/1port mode stackstack-port 2/1

#interface 10GE2/0/2port mode stack stack-port 2/1

#



#



#

A stack is formed


#interface 10GE2/0/2port mode stack

#interface 10GE1/0/5 eth-trunk 10

#

SwitchA Flash

SwitchA Configuration File


#interface 10GE2/0/2port mode stack stack-port 2/1

#

SwitchB Flash

SwitchB Configuration File





#interface 10GE1/0/5 eth-trunk 10

#

SwitchA Flash



#

SwitchB Flash

SwitchA and SwitchB Configuration File

Adding a Member Switch to a StackYou can add a member switch to a stably running stack. Here, the member switch is added tothe stack when it is powered off. If the member switch with power on is added to the stack, astack merge occurs. In this situation, see Stack Merge. After the member switch is added, thenew member switch is elected as a slave switch, the original master and standby switches remainunchanged, and the stack updates the topology.



108

Removing a Member Switch from a StackYou can remove a member switch from a stack. The stack may be affected depending on therole of the member switch that leaves the stack.l If the master switch leaves the stack, the standby switch becomes the new master switch,

updates the stack topology, and specifies a new standby switch.l If the standby switch leaves the stack, the master switch updates the stack topology and

specifies a new standby switch.l If a slave switch leaves the stack, the master switch updates the stack topology.l If both the master and standby switches leave the stack, all slave switches restart and form

another stack.

Stack Active/Standby SwitchoverIf the master switch is faulty or leaves the stack, the standby switch becomes the new masterswitch, which then specifies a new standby switch and synchronizes data to the new standbyswitch.l When a stack is formed for the first time, the MAC address of the master switch is used as

the stack MAC address. If the master switch is faulty or leaves the stack, the MAC addressof the new master switch is used as the stack MAC address when the delay in stack MACaddress switchover is not configured.

l When the master switch is faulty or leaves the stack, the new master switch uses its ownMAC address as the stack MAC address, if the old master switch does not rejoin thestack within the configured delay in stack MAC address switchover. If the old master switchrejoins the stack within the delay in stack MAC address switchover, the old master switchbecomes a slave switch, and the stack MAC address remains unchanged. In this case, thestack MAC address is the MAC address of a slave switch.

l When a slave switch (the owner of the stack MAC address) leaves a stack and does notrejoin the stack within the delay in stack MAC address switchover, the master switch usesits own MAC address as the stack MAC address.

Stack MergeTwo stacks can be merged into one stack. Then the superior switch between the master switchesof the two stacks is selected as the master switch of the new stack. The original stack containingthe new master remains the original device roles, and services in this stack are not affected.Switches in the other stack restart, join the new stack as slave switches, and synchronizeconfigurations with the new master switch. Services of this stack are interrupted.

Stack SplitAs shown in Figure 8-6, a stack splits into multiple stacks when some member switches areremoved from the running stack with power on or when the stack cable fail. A stack may splitinto multiple stacks with the same configurations, which causes conflicts of IP addresses andMAC addresses.



109

Figure 8-6 Stack split

Master Master

iStack 1 iStack 2

+=

Master StandbyiStack Link

iStack

Dual-active DetectionDual-active detection (DAD) is a method to detect a dual-active scenario and take recoveryaction, ensuring network stability.

DAD has two modes:l Direct mode

As shown in Figure 8-7, DAD is performed between member switches in a stack using adedicated direct link.

Figure 8-7 DAD in direct mode

SwitchA SwitchB

iStack

DAD LinkiStack LinkDAD packets

l Relay modeAs shown in Figure 8-8, DAD is configured on the inter-chassis Eth-Trunk in a stack, andDAD in relay mode is configured on the proxy device.

NOTE

To enable DAD packets to be forwarded between Eth-Trunk member links, the proxy device must supportDAD in relay mode. All CloudEngine series switches support DAD in relay mode.



110

Figure 8-8 DAD in relay mode

SwitchA SwitchB

iStack

Relay

SwitchC

Eth-Trunk

DAD LinkiStack LinkDAD packets

The proxy device can be a stack. That is, two stacks can function as a proxy for each other,as shown in Figure 8-9.

Figure 8-9 DAD relay between two stacks

Eth-Trunk10

SwitchA SwitchB

SwitchC SwitchD

Eth-Trunk20

DAD LinkiStack LinkDAD Packets

Domain 10

Domain 20

NOTE

To avoid interference to DAD in the two stacks, the two stacks must be configured with different domainIDs and use different Eth-Trunk links as DAD links.

After a DAD link is configured, the master switch sends DAD packets over the DAD link. Aftera stack splits into multiple stacks, the stacks compare information in received DAD packet withlocal information. If the switch in a stack is elected as the master switch, the switch remainsActive and continues forwarding service packets. If the switch in a stack is elected as the standby



111

switch, the switch shuts down all its service ports except those excluded from shutdown, entersthe Recovery state, and stops forwarding service packets.

The rules for electing the master switch are as follows:

1. The switch with higher stack priority is preferred.

2. The switch with a smaller MAC address is preferred.


After the stack link recovers, the switch in Recovery state restarts and restores all the blockedservice ports.

Fast Stack Upgrade

Fast stack upgrade is a mechanism that minimizes service forwarding interruption during thesoftware upgrade of member switches in a stack. This mechanism reduces the impact of memberdevice upgrade on services.

During fast stack upgrade, the standby switch restarts using the new version, and the masterswitch forwards data traffic. If the upgrade fails, the standby switch restarts and rolls back tothe previous version. After the standby switch is upgraded, it becomes the master switch andforwards data traffic. The previous master switch restarts using the new version. After theupgrade, the switch becomes the standby switch.

NOTE

Only the stack containing two member switches supports fast upgrade.

Figure 8-10 Fast upgrade of a stack

iStack Link

SwitchA(Master)

SwitchB(Standby)

iStack

8.3 Configuration NotesThis section describes precautions for configuring a stack.

Table 8-1 lists the notes to take when you configure a stack.



112

Table 8-1 Stack configuration notes

Item CE6850-48S4Q-EI CE6850-48T4Q-EI CE5850-48T4S2Q-EI

Number of memberswitches in a stack

4 4

Type of physicalmember ports

48x10GE opticalinterfaces and4x40GE opticalinterfaces

4x40GE opticalinterfaces

4x10GE opticalinterfaces and2x40GE opticalinterfaces

Type of cables usedto connect physicalmember ports

Interfacetype

High-speed cable forconnection

Fiber for connection

10GE opticalinterface

SFP+ - SFP+ Optical module: SFP+ optical moduleFiber: LC/PC fiber

40GE opticalinterface

QSFP+ - QSFP+ Optical module:QSFP+ opticalmoduleFiber: MPO-MPOfiber

Maximum number ofphysical memberports in a stack port

1 to 16 (10GE and40GE opticalinterfaces cannotbelong to the samestack port.)

1 to 4 1 to 4 (10GE and40GE opticalinterfaces cannotbelong to the samestack port.)

NOTE

l A stack can contain only devices of the same series. For example, CE6800 and CE5800 switches cannotform a stack.

l When configuring 10GE optical interfaces as physical member ports, follow these rules: The numberof physical member ports in a stack port must be a multiple of 4. The physical member ports must haveconsecutive IDs, and the last ID must be a multiple of 4. For example, interfaces with IDs 1 to 4, 5 to8, or 1 to 8 can be added to the same stack port but interfaces with IDs 2 to 5 or 3 to 6 cannot. 10GEoptical interfaces can be used as physical member ports only when they have 10GE optical modulesinstalled. They cannot be used to set up a stack when having GE optical modules or GE copper modulesinstalled.

l 40GE optical interfaces cannot be configured as physical member ports after they are split into 10GEoptical interfaces.

l Use Huawei-certified optical or copper modules. Non-Huawei-certified optical or copper modulescannot ensure transmission reliability and may affect service stability. Huawei is not responsible forany problem caused by non-Huawei-certified optical or copper modules and will not fix such problems.



113

8.4 Default ConfigurationThis section describes the default configurations of a stack and common stack parameters.

Table 8-2 Default stack configuration


The status of the CSS function Enabled

Stack ID 1

Stack priority 100

8.5 Configuring a StackYou can configure stack ports and parameters on member switches to set up a stack.

Pre-configuration TasksBefore configuring a stack, complete the following task:l Confirming that the switches support the stacking function and starting the devices



114

Configuration Procedure

Figure 8-11 Flowchart for configuring a stack

Configure the stack ID and priority

Configure a stack domain

Power off and connect the device using

cables

Mandatory step

Optional step

Configure a stack interface

Power on and start the device

8.5.1 Configuring the Stack Domain ID

ContextSwitches that connect to each other using stack links to form a stack belong to a stack domain.To meet various networking requirements, you can configure multiple stacks on a network anduse stack domain IDs to identify these stacks.

NOTEOnly the devices with the same stack domain ID can form a stack.


system-view


Step 2 Run:stack

The stack management view is displayed.

Step 3 Run:stack [ member { member-id | all } ] domain domain-id



115

The stack domain ID is configured for the member switch.

By default, no stack domain ID is configured for a device.

Step 4 Run:commit


----End

8.5.2 (Optional) Configuring the Stack ID

Context

The stack ID can be used to identify and manage member switches in a stack. Each memberswitch in a stack has a unique stack ID. If member switches have the same stack ID, the masterswitch assigns a unique stack ID to each of the member switches.

Procedure



Step 2 Run:stack


Step 3 Run:stack [ member member-id ] renumber new-member-id

A stack ID is set for the member switch.

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

Step 4 Run:commit


----End

8.5.3 (Optional) Configuring the Stack Priority

Context

The stack priority helps determine the role of member switches in master switch election. Alarger priority value indicates a higher priority. The member switch with a higher stack priorityhas a higher probability of becoming the master switch.



116

Procedure



Step 2 Run:stack


Step 3 Run:stack [ member { member-id | all } ] priority priority-value

The stack priority is configured.

By default, the stack priority is 100.

Step 4 Run:commit


----End

8.5.4 Configuring a Stack Port

ContextNOTE

If you connect devices using stack cables before configuring stack ports, the devices may restart because of thestack merge, causing configuration loss. You are advised to perform the stack configuration and run the savecommand to save the configuration before connecting devices using stack cables and restarting the devices.

During the setup of a stack, physical ports must be configured as physical member ports, whichare then added to a stack port. Multiple physical member ports can be added to a stack port toimprove stack link bandwidth and reliability.

When adding a physical port to a stack port, pay attention to the following points:l Ports with common service configuration cannot be added to a stack port.l Multiple physical member ports can be added to a stack port to implement stack link backup

and load balancing. This can improve link bandwidth and reliability.l 10GE optical ports or 40GE optical ports can be added to a stack port, but GE or 10GE

electrical ports cannot.l 10GE and 40GE ports cannot be added to the same stack port.l When configuring 10GE optical ports as physical member ports, follow these rules: The

number of physical member ports in a stack port must be a multiple of 4. The physicalmember ports must have consecutive IDs, and the last ID must be a multiple of 4. Forexample, ports with IDs 1 to 4, 5 to 8, or 1 to 8 can be added to the same stack port butports with IDs 2 to 5 or 3 to 6 cannot.

l When a physical port in Up state is configured as a physical member port, a CRC alarmmay be generated on the interface, but physicals are not affected. If the physical port isconfigured to transit to the error-down state when the number of received CRC error packets



117

exceeds the threshold, run the shutdown command to shut down the interface and then runthe undo shutdown command to return the interface to the Up state.

l After configuring a stack port, save the configuration to the configuration file for the nextstartup. Otherwise, the configuration is lost during the next startup.

Procedure

Step 1 Create a stack port.1. Run:

system-view


interface stack-port member-id/port-id

A stack port is created.

By default, no stack port is created.3. Run:

commit


Step 2 Configure physical ports as physical member ports.l In the stack management view


2. Run:stackThe stack management view is displayed.

3. Run:port mode stack interface interface-type interface-number1 [ to interface-number2 ]Physical ports are configured as physical member ports.

4. Run:commitThe configuration is committed.

l In the interface view



3. Run:port mode stackPhysical ports are configured as physical member ports.



118

4. Run:commit


Step 3 Add physical member ports to a stack port.l In the stack port view

1. Run:system-view



The stack port view is displayed.3. Run:

port member-group interface interface-type interface-number1 [ to interface-number2 ]

Member ports are added to the stack port.4. Run:

commit

The configuration is committed.l In the interface view

1. Run:system-view


interface interface-type interface-number


stack-port member-id/port-id

Physical member ports are added to the stack port.4. Run:

commit


Step 4 (Optional) Set the load balancing mode for the stack port.1. Run:

system-view



The stack port view is displayed.3. Run:

load-balance { dst-ip | dst-mac | src-dst-ip | src-dst-mac | src-ip | src-mac }

The load balancing mode is configured for the stack port.



119

By default, the load balancing mode of a stack port is src-dst-ip.

----End

8.5.5 Restarting the Device

ContextAfter stack attributes, such as the stack domain ID, stack ID, and stack priority, are configuredon a device, the configuration takes effect after the device is restarted. After performing the stackconfiguration, you can power off the device, connect the device using stack cables, and thenpower on and start the device.

NOTE

Before rebooting device, please use save command to save configuration.

8.5.6 (Optional) Configuring the Delay in Stack MAC AddressSwitchover

ContextIn a stack, if the owner of the stack MAC address leaves the stack and does not rejoin thestack within the delay in stack MAC address switchover, the master switch uses its own MACaddress as the new stack MAC address. If the member switch rejoins the stack within the delay,its own MAC address is still the stack MAC address.

If all switches have the delay in stack MAC address switchover configured before they form astack, the delay configured on the master switch is used after a stack is formed, and the delayconfigured on the other member switches remains the same as that of the master switch.

Procedure



Step 2 Run:stack


Step 3 Run:stack mac-address switch-delay { delay-time | immediately }

The delay in stack MAC address switchover is configured.

By default, the delay in stack MAC address switchover is 10 minutes.

Step 4 Run:commit


----End



120

8.5.7 (Optional) Starting Fast Upgrade of Switches in a Stack

Context

You can use commands to fast upgrade switches in a stack, which reduces the impact of deviceupgrade on services.

NOTE

Only the stack containing two member switches supports fast upgrade.

A device connected to the stack must be connected to the two member switches using an Eth-Trunk in thestack. Otherwise, data traffic may be interrupted.

During fast stack upgrade, the standby switch restarts using the new version, and the masterswitch forwards data traffic. After the standby switch is upgraded, it becomes the master switchand forwards data traffic. The previous master switch restarts using the new version. After theupgrade, the switch becomes the standby switch.

Procedure

Step 1 Run:startup system-software system-file all

The software package for the next startup is specified.



Step 3 Run:stack


Step 4 Run:stack upgrade fast

Fast upgrade is configured for switches in a stack.

----End


Procedurel Run the display stack [ member member-id ] command to check information about

member switches.

l Run the display stack configuration [ member member-id ] command to check the stackconfiguration.

l Run the display stack topology command to check stack topology information.

----End



121

8.6 (Optional) Configuring Dual-active DetectionYou can configure dual-active detection to detect and deal with a dual-active scenario when astack splits.

Pre-configuration TasksBefore configuring dual-active (DAD), complete the following task:l Setting up a stack.

8.6.1 Configuring the DAD Mode

ContextTwo DAD modes are available:l DAD in direct mode: DAD is performed between member switches in a stack using a

dedicated direct link.l DAD in relay mode: DAD is performed between member switches in a stack using the

relay function.

NOTE

l In a stack, you can only configure DAD in direct mode or DAD in relay mode but cannot configure bothDAD in direct mode and DAD in relay mode.

l To ensure DAD reliability, configure four direct links or four relay channels to detect the Eth-Trunk interface.In a dual-active scenario, if one direct link or one relay channel is in Up state, DAD can properly work.

Procedurel Configure DAD in direct mode.

1. Run:system-view


interface interface-type interface-number


dual-active detect mode direct

DAD in direct mode is enabled on the interface.

By default, DAD in direct mode is disabled on an interface.

NOTE

After DAD in direct mode is configured on an interface, other services are not suggested beingconfigured on the interface.

4. Run:commit



122

The configuration is committed.l Configure DAD in relay mode.

– On a member switch

1. Run:system-view


interface eth-trunk trunk-id

The Eth-Trunk interface view is displayed.3. Run:

dual-active detect mode relay

DAD in relay mode is enabled on the Eth-Trunk interface.

By default, DAD in relay mode is disabled on an interface.4. Run:

commit


– On a specified proxy device

1. Run:system-view


interface eth-trunk trunk-id

The Eth-Trunk interface view is displayed.3. Run:

dual-active proxy

The relay function is enabled on the Eth-Trunk interface.

By default, the relay function is disabled on an interface.4. Run:

commit


----End

8.6.2 (Optional) Excluding Ports from Shutdown

ContextWhen DAD detects a failure, all service ports of the member switch that fails master switchelection must be shut down to minimize the impact of the same MAC addresses and IP addresseson the network. Some ports that only transparently transmit packets do not affect networkstability in a dual-active scenario. You can exclude these ports from shutdown. In dual-activescenario, all service ports except those excluded from shutdown are in shutdown state.



123

Procedure



Step 2 Run:dual-active exclude interface interface-type interface-number1 [ to interface-number2 ]

The specified ports are excluded from error-down.

By default, only physical member ports are excluded from error-down.

Step 3 Run:commit


----End

8.6.3 (Optional) Restoring Blocked Ports

ContextIf the master switch fails or is removed from the network before a CSS split fault is rectified,restore the standby switch on which ports are in shutdown state so that the standby switch cantake over the master role. This minimizes the impact of the master switch fault on services.

Procedure



Step 2 Run:dual-active restore

Ports in shutdown state are restored.

Step 3 Run:commit


----End


Procedure

Step 1 Run the display dual-active [ proxy ] command to check the detailed DAD configuration.

----End



124

8.7 Configuration ExamplesThis section describes stack configuration examples, including networking requirements,configuration roadmap, and configuration procedure.

8.7.1 Example for Configuring a Stack with a Chain Topology


As the network size rapidly increases, more access interfaces must be provided on accessswitches, and the network must be easy to manage and maintain. A single access switch cannotmeet these requirements. A stack can be set up to meet these requirements.

As shown in Figure 8-12, SwitchA, SwitchB, and SwitchC need to set up a stack with a chaintopology. 10GE1/0/1 and 10GE1/0/2 of SwitchA need to be added to stack port 1/1. 10GE1/0/1and 10GE1/0/2 of SwitchB need to be added to stack port 1/1; 10GE1/0/3 and 10GE1/0/4 needto be added to stack port 1/2. 10GE1/0/1 and 10GE1/0/2 of SwitchC need to be added to stackport 1/1.

Figure 8-12 Stack with a chain topology

iStack Domain 10

SwitchA

SwitchB

10GE1/0/110GE1/0/2

iStack Link

Common Link

Eth-Trunk

Network

SwitchC10GE1/0/110GE1/0/2

10GE1/0/110GE1/0/2

10GE1/0/310GE1/0/4



125


1. Configure a domain ID for SwitchA, SwitchB, and SwitchC to enable the three switchesto form a stack and differentiate the stack from other stacks on the network.

2. Configure stack ports on SwitchA, SwitchB, and SwitchC so that physical member portscan forward data packets between the three member switches. A stack port can be boundto multiple physical member ports to improve stack link bandwidth and reliability.

3. Use optical fibers to connect stack ports of the three switches and restart the three switchesto make the configuration take effect.

Procedure

Step 1 Configure stack parameters on SwitchA, SwitchB, and SwitchC.

# On SwitchA, set the domain ID to 10, the stack ID to 1, and the stack priority to 150.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] stack[~SwitchA-stack] stack domain 10[~SwitchA-stack] stack renumber 1[~SwitchA-stack] stack priority 150[~SwitchA-stack] quit[~SwitchA] commit

# On SwitchB, set the domain ID to 10 and the stack ID to 2.

<HUAWEI> system-view[~HUAWEI] sysname SwitchB[~HUAWEI] commit[~SwitchB] stack[~SwitchB-stack] stack domain 10[~SwitchB-stack] stack renumber 2[~SwitchB-stack] quit[~SwitchB] commit

# On SwitchC, set the domain ID to 10 and the stack ID to 3.

<HUAWEI> system-view[~HUAWEI] sysname SwitchC[~HUAWEI] commit[~SwitchC] stack[~SwitchC-stack] stack domain 10[~SwitchC-stack] stack renumber 3[~SwitchC-stack] quit[~SwitchC] commit

Step 2 Configure stack ports.

# On SwitchA, configure 10GE 1/0/1 and 10GE 1/0/2 as physical member ports and add themto stack port 1/1.

[~SwitchA-stack] port mode stack interface 10ge 1/0/1 to 1/0/4[~SwitchA-stack] quit[~SwitchA] interface stack-port 1/1[~SwitchA-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2[~SwitchA-Stack-Port1/1] quit[~SwitchA] commit

# On SwitchB, configure 10GE1/0/1 through 10GE1/0/4 as physical member ports. Add10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to 1/2.



126

[~SwitchB-stack] port mode stack interface 10ge 1/0/1 to 1/0/4[~SwitchB-stack] quit[~SwitchB] interface stack-port 1/1[~SwitchB-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2[~SwitchB-Stack-Port1/1] quit[~SwitchB] interface stack-port 1/2[~SwitchB-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4[~SwitchB-Stack-Port1/2] quit[~SwitchB] commit

# On SwitchC configure 10GE 1/0/1 and 10GE 1/0/2 as physical member ports and add themto stack port 1/1.

[~SwitchC-stack] port mode stack interface 10ge 1/0/1 to 1/0/4[~SwitchC-stack] quit[~SwitchC] interface stack-port 1/1[~SwitchC-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2[~SwitchC-Stack-Port1/1] quit[~SwitchC] commit

Step 3 Save the configurations of SwitchA, SwitchB and SwitchC, power off the three switches, connectthe stack link, and power on the three switches.


# Check stack information.

<SwitchA> display stack------------------------------------------------------------ MemberID Role Mac Priority Device Type ------------------------------------------------------------ 1 Master 0004-9f31-d520 150 CE6850-48T4Q-EI 2 Standby 0004-9f62-1f40 100 CE6850-48T4Q-EI 3 Slave 0004-9f69-a391 100 CE6850-48T4Q-EI ------------------------------------------------------------

NOTE

To cancel the stack configuration, perform the following operations:

1. Delete physical member interfaces from a stack interface.

l Run the undo port member-group interface interface-type interface-number1 [ to interface-number2 ] command in the stack port view .

l Run the undo port member-group interface interface-type interface-number1 [ to interface-number2 ] command in the interface view.

2. Restore physical member interfaces as service interfaces.

l Run the undo port mode stack interface interface-type interface-number1 [ to interface-number2 ]command in the stack management view.

l Run the undo port mode stack command in the interface view.

3. Run the undo interface stack-port member-id/port-id command in the system view to delete the stackinterface.

4. Remove stack cables between switches. To restore the stack ID of a switch to 1, run the stack [ membermember-id ] renumber 1 command in the stack management view and restart the switch.

----End

Configuration Filesl Configuration file of the stack

#sysname SwitchA#interface 10GE1/0/1 port mode stack



127

stack-port 1/1#interface 10GE1/0/2 port mode stack stack-port 1/1#interface 10GE2/0/1 port mode stack stack-port 2/1#interface 10GE2/0/2 port mode stack stack-port 2/1#interface 10GE2/0/3 port mode stack stack-port 2/2#interface 10GE2/0/4 port mode stack stack-port 2/2#interface 10GE3/0/1 port mode stack stack-port 3/1#interface 10GE3/0/2 port mode stack stack-port 3/1#return

8.7.2 Example for Configuring a Stack with a Ring Topology

Networking RequirementsAs the network size rapidly increases, more access interfaces must be provided on accessswitches, and the network must be easy to manage and maintain. A single access switch cannotmeet these requirements. A stack can be set up to meet these requirements.

As shown in Figure 8-13, SwitchA, SwitchB, and SwitchC need to set up a stack with a ringtopology. On the switches, 10GE1/0/1 and 10GE1/0/2 need to be added to stack port 1/1, and10GE1/0/3 and 10GE1/0/4 need to be added to stack port 1/2.



128

Figure 8-13 Stack with a ring topology

iStack Link

Common Link

Eth-Trunk

SwitchA SwitchB

iStack Domain 10

SwitchC

Network

10GE1/0/110GE1/0/2

10GE1/0/110GE1/0/2

10GE1/0

/3

10GE1/0

/410

GE1/0/3

10GE1/0

/4

10GE1/0/1

10GE1/0/210GE1/0/3

10GE1/0/4


1. Configure a domain ID for SwitchA, SwitchB, and SwitchC to enable the three switchesto form a stack and differentiate the stack from other stacks on the network.

2. Configure stack ports on SwitchA, SwitchB, and SwitchC so that physical member portscan forward data packets between the three member switches. A stack port can be boundto multiple physical member ports to improve stack link bandwidth and reliability.

3. Use optical fibers to connect stack ports of the three switches and restart the three switchesto make the configuration take effect.

Procedure

Step 1 Configure stack parameters on SwitchA, SwitchB, and SwitchC.

# On SwitchA, set the domain ID to 10, the stack ID to 1, and the stack priority to 150.

<HUAWEI> system-view[~HUAWEI] sysname SwitchA[~HUAWEI] commit[~SwitchA] stack



129

[~SwitchA-stack] stack domain 10[~SwitchA-stack] stack renumber 1[~SwitchA-stack] stack priority 150[~SwitchA-stack] quit[~SwitchA] commit

# On SwitchB, set the domain ID to 10 and the stack ID to 2.

<HUAWEI> system-view[~HUAWEI] sysname SwitchB[~HUAWEI] commit[~SwitchB] stack[~SwitchB-stack] stack domain 10[~SwitchB-stack] stack renumber 2[~SwitchB-stack] quit[~SwitchB] commit

# On SwitchC, set the domain ID to 10 and the stack ID to 3.

<HUAWEI> system-view[~HUAWEI] sysname SwitchC[~HUAWEI] commit[~SwitchC] stack[~SwitchC-stack] stack domain 10[~SwitchC-stack] stack renumber 3[~SwitchC-stack] quit[~SwitchC] commit

Step 2 Configure stack ports.

# On SwitchA, configure 10GE1/0/1 through 10GE1/0/4 as physical member ports. Add10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to 1/2.

[~SwitchA] stack[~SwitchA-stack] port mode stack port 10ge 1/0/1 to 1/0/4[~SwitchA-stack] commit[~SwitchA-stack] quit[~SwitchA] interface stack-port 1/1[~SwitchA-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2[~SwitchA-Stack-Port1/1] quit[~SwitchA] interface stack-port 1/2[~SwitchA-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4[~SwitchA-Stack-Port1/2] quit[~SwitchA-Stack] commit

# On SwitchB, configure 10GE1/0/1 through 10GE1/0/4 as physical member ports. Add10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to 1/2.

[~SwitchB] stack[~SwitchB-stack] port mode stack port 10ge 1/0/1 to 1/0/4[~SwitchB-stack] commit[~SwitchB-stack] quit[~SwitchB] interface stack-port 1/1[~SwitchB-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2[~SwitchB-Stack-Port1/1] quit[~SwitchB] interface stack-port 1/2[~SwitchB-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4[~SwitchB-Stack-Port1/2] quit[~SwitchB-Stack] commit

# On SwitchC, configure 10GE1/0/1 through 10GE1/0/4 as physical member ports. Add10GE1/0/1 and 10GE1/0/2 to stack port 1/1, and add 10GE1/0/3 and 10GE1/0/4 to 1/2.

[~SwitchC] stack[~SwitchC-stack] port mode stack port 10ge 1/0/1 to 1/0/4[~SwitchC-stack] commit[~SwitchC-stack] quit[~SwitchC] interface stack-port 1/1[~SwitchC-Stack-Port1/1] port member-group interface 10ge 1/0/1 to 1/0/2



130

[~SwitchC-Stack-Port1/1] quit[~SwitchC] interface stack-port 1/2[~SwitchC-Stack-Port1/2] port member-group interface 10ge 1/0/3 to 1/0/4[~SwitchC-Stack-Port1/2] quit[~SwitchC-Stack] commit

Step 3 Save the configurations of SwitchA, SwitchB and SwitchC, power off the three switches, connectthe stack link, and power on the three switches.


# Check stack information.

<SwitchA> display stack------------------------------------------------------------ MemberID Role Mac Priority Device Type ------------------------------------------------------------ 1 Master 0004-9f31-d520 150 CE6850-48T4Q-EI 2 Standby 0004-9f62-1f40 100 CE6850-48T4Q-EI 3 Slave 0004-9f69-a391 100 CE6850-48T4Q-EI ------------------------------------------------------------

----End


#sysname SwitchA#interface 10GE1/0/1 port mode stack stack-port 1/1#interface 10GE1/0/2 port mode stack stack-port 1/1#interface 10GE1/0/3 port mode stack stack-port 1/2#interface 10GE1/0/4 port mode stack stack-port 1/2#interface 10GE2/0/1 port mode stack stack-port 2/1#interface 10GE2/0/2 port mode stack stack-port 2/1#interface 10GE2/0/3 port mode stack stack-port 2/2#interface 10GE2/0/4 port mode stack stack-port 2/2#interface 10GE3/0/1 port mode stack stack-port 3/1#interface 10GE3/0/2 port mode stack



131

stack-port 3/1#interface 10GE3/0/3 port mode stack stack-port 3/2#interface 10GE3/0/4 port mode stack stack-port 3/2#return

8.7.3 Example for Configuring DAD in Direct Mode


As shown in Figure 8-14, SwitchA and SwitchB form a stack. SwitchA is the master switch inthe stack. The stack IDs of SwitchA and SwitchB are 1 and 2 respectively. DAD in direct modeneeds to be configured on interfaces 10GE1/0/5 and 10GE2/0/5.

When the stack splits because of a stack link fault and there are two stacks with the sameconfiguration on the network, you can use DAD to reduce the impact of a stack split on thenetwork.

Figure 8-14 Networking diagram of DAD in direct mode

Network

iStack

SwitchA SwitchB10GE1/0/5 10GE2/0/5

SwitchC

DAD Link

iStack Link

Common Link

Eth-Trunk



132


1. Configure DAD in direct mode on specified interfaces.

Procedure

Step 1 Configure DAD on interfaces.

# Configure DAD in direct mode on 10GE1/0/5.

<HUAWEI> system-view[~HUAWEI] interface 10ge 1/0/5[~HUAWEI-10GE1/0/5] dual-active detect mode directWarning: The interface will block common data packets, except BPDU packets. Continue? [Y/N]: y[~HUAWEI-10GE1/0/5] commit

# Configure DAD in direct mode on 10GE2/0/5.

<HUAWEI> system-view[~HUAWEI] interface 10ge 2/0/5[~HUAWEI-10GE2/0/5] dual-active detect mode directWarning: The interface will block common data packets, except BPDU packets. Continue? [Y/N]: y[~HUAWEI-10GE2/0/5] commit


# Check detailed DAD configuration.

<HUAWEI> display dual-activeDual-active status: Normal Dual-active detect mode: Direct Dual-active direct detect interfaces configured: 10GE1/0/5 up 10GE2/0/5 up Dual-active relay detect interfaces configured: - Excluded ports(configurable): - Excluded ports(can not be configured): 10GE1/0/1 10GE1/0/2 10GE1/0/3 10GE1/0/4 10GE2/0/1 10GE2/0/2 10GE2/0/3 10GE2/0/4

----End


#interface 10GE1/0/1 port mode stack stack-port 1/1#interface 10GE1/0/2 port mode stack stack-port 1/1#



133

interface 10GE1/0/3 port mode stack stack-port 1/1#interface 10GE1/0/4 port mode stack stack-port 1/1#interface 10GE1/0/5 dual-active detect mode direct#interface 10GE2/0/1 port mode stack stack-port 2/1#interface 10GE2/0/2 port mode stack stack-port 2/1#interface 10GE2/0/3 port mode stack stack-port 2/1#interface 10GE2/0/4 port mode stack stack-port 2/1#interface 10GE2/0/5 dual-active detect mode direct#return

8.7.4 Example for Configuring DAD in Relay Mode

Networking RequirementsAs shown in Figure 8-15, SwitchA and SwitchB form a stack. SwitchA and SwitchB connectto SwitchC using Eth-Trunk10.

When the stack splits because of a stack link fault and there are two stacks with the sameconfiguration on the network, you can use DAD to reduce the impact of a stack split on thenetwork.



134

Figure 8-15 Networking diagram of DAD in relay mode

Network

SwitchA SwitchB

SwitchC

Eth-Trunk10

iStack10GE1/0/5 10GE2/0/5

10GE1/0/1 10GE1/0/2

DAD Link

iStack Link

Common Link

Eth-Trunk


1. Configure DAD in relay mode on a specified Eth-Trunk interface.2. Configure the relay function on the proxy device to allow the proxy device to forward DAD

protocol packets.

Procedure

Step 1 Configure DAD in relay mode on a specified Eth-Trunk interface.

# Configure DAD in relay mode on Eth-Trunk10.

<HUAWEI> system-view[~HUAWEI] interface eth-trunk 10[~HUAWEI-Eth-Trunk10] trunkport 10ge 1/0/5[~HUAWEI-Eth-Trunk10] trunkport 10ge 2/0/5[~HUAWEI-Eth-Trunk10] dual-active detect mode relay[~HUAWEI-Eth-Trunk10] commit

Step 2 Configure the relay function on the proxy device.

# Configure the relay function on SwitchC.



135

<HUAWEI> system-view[~HUAWEI] sysname SwitchC[~HUAWEI] commit[~SwitchC] interface eth-trunk 10[~SwitchC-Eth-Trunk10] trunkport 10ge 1/0/1[~SwitchC-Eth-Trunk10] trunkport 10ge 1/0/2[~SwitchC-Eth-Trunk10] dual-active proxy[~SwitchC-Eth-Trunk10] commit


# Check detailed DAD configuration.

<HUAWEI> display dual-activeDual-active status: NormalDual-active detect mode: RelayDual-active direct detect interfaces configured: -Dual-active relay detect interfaces configured: Eth-Trunk10 10GE1/0/5 up 10GE2/0/5 upExcluded ports(configurable): -Excluded ports(can not be configured): 10GE1/0/1 10GE1/0/2 10GE1/0/3 10GE1/0/4 10GE2/0/1 10GE2/0/2 10GE2/0/3 10GE2/0/4

# Check information about SwitchC.

<SwitchC> display dual-active proxyDual-active proxy interfaces configured: Eth-Trunk10 10GE1/0/1 up 10GE1/0/2 up

----End


#interface 10GE1/0/1 port mode stack stack-port 1/1#interface 10GE1/0/2 port mode stack stack-port 1/1#interface 10GE1/0/3 port mode stack stack-port 1/1#interface 10GE1/0/4 port mode stack stack-port 1/1#interface 10GE1/0/5 eth-trunk 10#interface 10GE2/0/1



136

port mode stack stack-port 2/1#interface 10GE2/0/2 port mode stack stack-port 2/1#interface 10GE2/0/3 port mode stack stack-port 2/1#interface 10GE2/0/4 port mode stack stack-port 2/1#interface 10GE2/0/5 eth-trunk 10#interface Eth-Trunk10 dual-active detect mode relay#return

l Configuration file of SwitchC#sysname SwitchC#interface 10GE1/0/1 eth-trunk 10#interface 10GE1/0/2 eth-trunk 10#interface Eth-Trunk10 dual-active proxy#return



137

Documents

CloudEngine 6800&5800 V100R001C00 Configuration Guide - Device Management 04.pdf