configuration guide - device management(v200r001c01_03).pdf

Huawei AR1200-S Series Enterprise RoutersV200R001C01

Configuration Guide - DeviceManagement

Issue 03

Date 2011-11-27

HUAWEI TECHNOLOGIES CO., LTD.

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

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

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

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

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

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

i

http://www.huawei.com

mailto:[email protected]

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

This document describes how to configure the device management feature.

This document is intended for:

l Data configuration engineers

l Commissioning engineers

l Network monitoring engineers

l System maintenance engineers

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

Symbol Description

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

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

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

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

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

Huawei AR1200-S Series Enterprise RoutersConfiguration 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. Several items or no item can be selected.

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

# A line starting with the # sign is comments.

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

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

Changes in Issue 03 (2011-11-27)

Based on issue 02 (2011-10-15), the document is updated as follows:

The following information is added:

l 4.6.2 Example for Configuring Local Flow Mirroring

The following information is modified:

l 5.3.1 Establishing the Configuration Task



iii

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

The following information is added:

l 6.4.1 Example for Configuring the Auto-Config Functionl 1.2.12 Checking Interface Card Work Mode

Changes in Issue 01 (2011-08-15)Initial commercial release.



iv

Contents

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

1 Displaying the Device Status......................................................................................................11.1 Display Commands.............................................................................................................................................21.2 Displaying the AR1200-S Status........................................................................................................................2

1.2.1 Displaying AR1200-S Information...........................................................................................................21.2.2 Displaying Versions..................................................................................................................................31.2.3 Displaying Power Information..................................................................................................................31.2.4 Displaying Temperature............................................................................................................................31.2.5 Viewing Fan Status....................................................................................................................................41.2.6 Displaying CPU Usage..............................................................................................................................41.2.7 Displaying Memory Usage........................................................................................................................41.2.8 Displaying Interface Status........................................................................................................................51.2.9 Displaying Electronic Labels.....................................................................................................................51.2.10 Displaying Diagnostic Information.........................................................................................................61.2.11 Displaying Health Status.........................................................................................................................61.2.12 Checking Interface Card Work Mode......................................................................................................6

2 Information Center Configuration.............................................................................................82.1 Introduction to the Information Center...............................................................................................................92.2 Information Center Supported by the AR1200-S...............................................................................................92.3 Enabling Log Output........................................................................................................................................14

2.3.1 Establishing the Configuration Task.......................................................................................................142.3.2 Enabling the Information Center.............................................................................................................152.3.3 (Optional) Naming an Information Channel...........................................................................................162.3.4 (Optional) Configuring the Function of Filtering Logs by IDs...............................................................162.3.5 (Optional) Configuring the Function of Generating a Data Dictionary..................................................162.3.6 Outputting Logs to the Log Buffer..........................................................................................................172.3.7 Outputting Logs to a Log File.................................................................................................................182.3.8 Outputting Logs to the Console...............................................................................................................182.3.9 Outputting Logs to the Terminal.............................................................................................................192.3.10 Outputting Logs to the Log Host...........................................................................................................202.3.11 Checking the Configuration...................................................................................................................20

2.4 Enabling Alarm Output....................................................................................................................................23

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management Contents


v

2.4.1 Establishing the Configuration Task.......................................................................................................232.4.2 Enabling the Information Center.............................................................................................................232.4.3 (Optional) Naming an Information Channel...........................................................................................242.4.4 Outputting Alarms to the Alarm Buffer..................................................................................................242.4.5 Outputting Alarms to the Log File..........................................................................................................252.4.6 Outputting Alarms to the Console...........................................................................................................262.4.7 Outputting Alarms to the Terminal.........................................................................................................272.4.8 Outputting Alarms to the SNMP Agent..................................................................................................282.4.9 Checking the Configuration.....................................................................................................................29

2.5 Enabling the Output of Debugging Information...............................................................................................302.5.1 Establishing the Configuration Task.......................................................................................................312.5.2 Enabling the Information Center.............................................................................................................312.5.3 (Optional) Naming an Information Channel...........................................................................................322.5.4 Outputting Debugging Information to the Log File................................................................................322.5.5 Outputting Debugging Information to the Console.................................................................................332.5.6 Outputting Debugging Information to the Terminal...............................................................................342.5.7 Outputting Debugging Information to the Log Host...............................................................................352.5.8 Checking the Configuration.....................................................................................................................35

2.6 Maintaining Information Center.......................................................................................................................362.7 Information Center Configuration Examples...................................................................................................37

2.7.1 Example for Outputting Logs to the Log File.........................................................................................372.7.2 Example for Outputting Logs to Log Hosts............................................................................................392.7.3 Example for Configuring Binary Logs to be Sent to the Log Host.........................................................432.7.4 Example for Outputting Alarms to the SNMP Agent..............................................................................452.7.5 Example for Outputting the Debugging Information to the Console......................................................47

3 PoE Configuration.......................................................................................................................493.1 Introduction to PoE...........................................................................................................................................503.2 PoE Features Supported by the AR1200-S.......................................................................................................503.3 Configuring PoE Functions..............................................................................................................................50

3.3.1 Establishing the Configuration Task.......................................................................................................513.3.2 Configuring the PoE Function Globally..................................................................................................513.3.3 Configuring the PoE Function on an Interface........................................................................................533.3.4 Checking the Configuration.....................................................................................................................55

3.4 Configuration Examples...................................................................................................................................563.4.1 Example for Configuring PoE.................................................................................................................56

4 Mirroring Configuration............................................................................................................594.1 Introduction to Mirroring..................................................................................................................................604.2 Mirroring Features Supported by the AR1200-S.............................................................................................604.3 Configuring Local Port Mirroring....................................................................................................................62

4.3.1 Establishing the Configuration Task.......................................................................................................624.3.2 Configuring a Local Observing Interface................................................................................................634.3.3 Configuring a Local Mirrored Interface..................................................................................................63



vi

4.3.4 Checking the Configuration.....................................................................................................................644.4 Configuring Local Flow Mirroring...................................................................................................................65

4.4.1 Establishing the Configuration Task.......................................................................................................654.4.2 Configuring a Local Observing Interface................................................................................................654.4.3 Configuring Complex Traffic Classification...........................................................................................664.4.4 Creating a Local Traffic Behavior...........................................................................................................664.4.5 Configuring a Traffic Policy....................................................................................................................674.4.6 Checking the Configuration.....................................................................................................................68

4.5 Configuring Packet Capture Using Mirroring..................................................................................................684.6 Configuration Examples...................................................................................................................................71

4.6.1 Example for Configuring Local Port Mirroring......................................................................................714.6.2 Example for Configuring Local Flow Mirroring.....................................................................................75

5 Hardware Management..............................................................................................................785.1 Introduction to Hardware Management............................................................................................................795.2 Hardware Management Supported by the AR1200-S......................................................................................795.3 Powering On and Off the Board.......................................................................................................................79

5.3.1 Establishing the Configuration Task.......................................................................................................795.3.2 Powering Off a Board..............................................................................................................................805.3.3 Powering On a Board..............................................................................................................................805.3.4 Checking the Configuration.....................................................................................................................80

5.4 Backing Up Electronic Labels..........................................................................................................................815.4.1 Establishing the Configuration Task.......................................................................................................815.4.2 Backing Up Electronic Labels.................................................................................................................81

5.5 Setting Fan Speed.............................................................................................................................................825.5.1 Establishing the Configuration Task.......................................................................................................825.5.2 Setting Fan Speed....................................................................................................................................835.5.3 Checking the Configuration.....................................................................................................................83

5.6 Resetting the LPU.............................................................................................................................................835.6.1 Establishing the Configuration Task.......................................................................................................835.6.2 Resetting the LPU....................................................................................................................................845.6.3 Checking the Configuration.....................................................................................................................84

6 Auto-Config..................................................................................................................................866.1 Auto-Config Overview.....................................................................................................................................876.2 Auto-Config Features Supported by the AR1200-S.........................................................................................876.3 Deploying Unconfigured Routers ....................................................................................................................92

6.3.1 Establishing the Configuration Task.......................................................................................................926.3.2 Configuring the DHCP Server.................................................................................................................946.3.3 Configuring the FTP/TFTP Server..........................................................................................................966.3.4 Checking the Configuration.....................................................................................................................97

6.4 Configuration Examples...................................................................................................................................986.4.1 Example for Configuring the Auto-Config Function..............................................................................98



vii

1 Displaying the Device Status

About This Chapter

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

1.1 Display CommandsThis section describes the functions of display commands and lists the display commands incommon use.

1.2 Displaying the AR1200-S StatusThis section describes how to use the display commands to show the AR1200-S version, CPUusage, and memory usage.

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management 1 Displaying the Device Status


1

1.1 Display CommandsThis section describes the functions of display commands and lists the display commands incommon use.

The display commands can be used to collect current information about the version, device, anddiagnosis of the AR1200-S in order to maintain and troubleshooting networks.

Table 1-1 lists the display commands in common use. For details, see the Huawei AR1200-SSeries Enterprise Routers - Command Reference.

CAUTIONThe display diagnostic-information command cannot be simultaneously run on multipleterminals connected to the AR1200-S. If this occurs, the AR1200-S CPU usage rises and thenetwork performs less efficiently.

Table 1-1 Common display commands

Command Description

display current-configuration Displays the parameters that take effect currently on theAR1200-S.

display device Displays information about the AR1200-S.

display version Displays the version and boards information of theAR1200-S.

display this Displays valid configurations in the current view.

display diagnostic-information Collects information about the AR1200-S when a faultcannot be located or fixed. Send information to Huaweitechnical personnel for fault analysis.NOTE

This command is not recommended for routine troubleshooting.

display this interface Displays the current status of the interface.

1.2 Displaying the AR1200-S StatusThis section describes how to use the display commands to show the AR1200-S version, CPUusage, and memory usage.

1.2.1 Displaying AR1200-S InformationUse the display device command to view information about AR1200-S components, includingthe slot number, component type, online status, power status, register status, alarm status, andmaster/backup status.



2

Procedurel Run:

display device [ slot slot-id ]

Component information is displayed.

This command can be used in any view.

----End

1.2.2 Displaying VersionsUse the display version command to view the information about the software version, hardwaretype, main control board and LPU of the AR1200-S.

Procedurel Run:

display version [ slot slot-id ]

Version information is displayed.


----End

1.2.3 Displaying Power InformationUse the display power command to view information about the power status and power of theAR1200-S.

Procedure

Step 1 Run:display power

The power status is displayed.

Step 2 Run:display power system

Power information is displayed.

Displayed information includes the power status, power used by the system (watts), and powerused by boards (watts). These commands can be used in any view.

----End

1.2.4 Displaying TemperatureUse the display temperature command to view board temperature, including the currenttemperature, temperature upper threshold, and temperature lower threshold.

Procedurel Run:

display temperature { all | slot slot-id }



3

Board temperature is displayed.


----End

1.2.5 Viewing Fan StatusUse the following display command to view the fan status, including the running status,registration status, fan speed, and working mode.

Procedurel Run:

display fan

Fan status is displayed.


----End

1.2.6 Displaying CPU UsageView the CPU usage statistics and threshold configurations.

Procedure

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

CPU usage statistics are displayed.

Step 2 Run:display cpu-usage configuration [ slot slot-id ]

CPU usage configurations are displayed.

l If slot slot-id is specified, the CPU usage of the LPU in this slot is displayed.l If slot slot-id is not specified, the CPU usage of the active main control board is displayed.

----End

1.2.7 Displaying Memory UsageUse the display memory-usage command to view memory usage statistics and threshold.

Procedurel Run:

display memory-usage [ slot slot-id ]

Memory usage statistics are displayed.


– If slot slot-id is specified, the memory usage of the LPU in this slot is displayed.



4

– If slot slot-id is not specified, the memory usage of the active main control board isdisplayed.

----End

1.2.8 Displaying Interface StatusUse the display interface command to view the running status, basic configurations, and packetforwarding statistics on an interface.

ContextThere are two ways to display interface status:

1. Run the display interface command in any view.2. Run the display this interface command in an interface view.

Procedurel Run the following command in any view:

display interface interface-type interface-number

The status of the specified interface is displayed.l View interface status in a specified interface view:

1. Run the system-view command to enter the system view.2. Run the interface interface-type interface-number command to enter the interface

view.3. Run the display this interface command to display interface status.

Using the display this interface command in the interface view is equivalent to usingthe display interface interface-type interface-numbercommand in any view.

4. Run the display this command to display interface configurations.

----End

1.2.9 Displaying Electronic LabelsUse the display elabel command to view information about electronic labels, including the boardtype, BOM code, description, manufacture date, vendor name, issuing number, CommonLanguage Equipment Identification (CLEI) code, and sales BOM code.

Procedure

Step 1 Run:display elabel [ slot-id ] [ brief ]

Electronic labels are displayed.

This command can be used in any view. The slot-id parameter can be specified to view labelinformation about the board in a specified slot.

If the brief parameter is specified, the electronic label of an optical module is not displayed.

----End



5

1.2.10 Displaying Diagnostic InformationUse the display diagnostic-information command to collect running information of allmodules, including clocks, versions, current configuration file, saved configuration files,physical and protocol information about an interface, statistics on the transmitted and receivedpackets, memory usage, and system logs. Use this command for locating faults instead of runningmultiple display commands.

Procedurel Run:

display diagnostic-information

Diagnostic information is displayed.

CAUTIONWhen this command is being executed, system performance will be degraded, for example,the CPU usage increases. Therefore, do not use this command when the system is operatingnormally.

----End

1.2.11 Displaying Health StatusUse the display health command to view health status information, including CPU usage,memory usage, power supply status, fan status, and temperature.

Procedurel Run:

display health

Health status is displayed.

----End

1.2.12 Checking Interface Card Work ModeThe interface card work mode can be displayed using the display workmode command.

ContextOnly the work mode of the interface cards with configurable work modes can be displayed.

The work mode of these interface cards can be changed: 2E1/T1-M, 1E1/T1-M, 2E1/T1-F, 1E1/T1-F, 4G.SHDSL, and 1CPOS-155M.

Procedure

Step 1 Run:display workmode



6

The interface card work mode is displayed.

----End



7

2 Information Center Configuration

About This Chapter

This chapter describes how to configure the information center to control the output of logs,alarms, and debugging messages.

2.1 Introduction to the Information CenterThe information center works as the information hub of a router. It classifies and filters the outputof a system. The information center uses a debugging program to help network administratorand developers monitor network operation and analyze network faults.

2.2 Information Center Supported by the AR1200-SThe information center outputs logs, alarms, and debugging messages at eight severity levelsthrough 10 information channels.

2.3 Enabling Log OutputThis section describes how to output logs of a specific module to a log file, console, terminal,or log host.

2.4 Enabling Alarm OutputThis section describes how to configure a specific module to output alarm information to logfiles, consoles, terminals, or SNMP agents.

2.5 Enabling the Output of Debugging InformationThis section describes how to configure a specific module to output debugging information tolog files, consoles, terminals, or SNMP agents.

2.6 Maintaining Information CenterThis section describes how to run the following commands to delete messages in the buffer ofthe information center. Note that deleted messages cannot be restored.

2.7 Information Center Configuration ExamplesThis section provides information center configuration examples.

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management 2 Information Center Configuration


8

2.1 Introduction to the Information CenterThe information center works as the information hub of a router. It classifies and filters the outputof a system. The information center uses a debugging program to help network administratorand developers monitor network operation and analyze network faults.

2.2 Information Center Supported by the AR1200-SThe information center outputs logs, alarms, and debugging messages at eight severity levelsthrough 10 information channels.

Information Classification

The information center receives and processes information of the following types:

l Logsl Debugging informationl Alarms

Severity Levels of Information

Information has eight severity levels as shown in Table 2-1. The lower the severity level, themore severe the information.

Table 2-1 Description of the severity levels of information

Threshold Severity Level Description

0 Emergencies A fatal fault, such as a program exception or incorrectmemory usage, occurs on the device. The system mustrestart.

1 Alert An important fault, such as the device memoryreaching the highest limit, occurs on the device. Thefault needs to be fixed immediately.

2 Critical A crucial fault, such as the memory or temperaturereaching the lowest limit, or the BFD device beingunreachable, occurs on the device. An internal faultcan also be generated by the device itself. The faultneeds to be analyzed and fixed.

3 Error A fault, such as a user running incorrect commands,entering a wrong password, or receiving wrongprotocol packets from other devices, occurs on thedevice. These faults can be caused by improperoperation or a wrong process.They do not affect services but should be givenattention.



9

Threshold Severity Level Description

4 Warning An abnormal situation, such as the user disabling therouting process, the BFD detecting packet loss, or thewrong protocol packet being received occurs on thedevice.The fault may affect services and should be givenattention.

5 Notification Indicates the key operations used to ensure that thedevice runs normally, such as the execution of theshutdown command, the performance of neighbordiscovery, or the status change of the state machine.

6 Informational Indicates the common operations used to ensure thatthe device runs normally, such as the execution of thedisplay command.

7 Debugging Indicates that the common device information doesnot require attention.

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

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

Working Process of the Information CenterThe working process of the information center is as follows:

l The information center receives logs, alarms, and debugging information from all modules.l The information center outputs information with different severity levels to different

information channels according to the configuration.l Information is transmitted in different directions based on the relationship between the

information channel and the output direction.

Generally, the information center distributes three types of information classified into eightlevels to 10 information channels. Information is then output to different directions.

As shown in Figure 2-1, logs, alarms, and debugging information have default output channels.They can be customized to be output from other channels. For example, logs can be configuredto be output to the log cache through Channel 6 rather than the default Channel 4.



10

Figure 2-1 Functions of the information channel

Informationchannel

Console

Remote terminal

Loghost

Trap buffer

Log buffer

SNMP agent

Logs

Traps

Debugs

Outputdirection

Direction of logsDirection of alarmsDirection of debugging

informationLogfile

Console

SNMP agent

Monitor

Loghost

Logbuffer

Trapbuffer

0

1

23

4

5

channel6

channel7

channel8

channel9

6

7

8

9

Information Channels and Output Directions

The system supports 10 channels. The first six channels (Channel 0 to Channel 5) have defaultchannel names and are associated with six default output directions. For devices equipped withstorage media, log information is output to log files through Channel 9 by default. That is, seventotal default output directions are supported.

For details of the association relationship between default channels and output directions, seeTable 2-2.

Table 2-2 Association relationship between default channels and output directions

ChannelNumber

DefaultChannel Name

OutputDirection

Description

0 Console Console Outputs logs, alarms, and debugginginformation to the local console.

1 Monitor Monitor Outputs logs, alarms, and debugginginformation to the VTY terminals forremote maintenance.

2 Loghost Log host Outputs logs, alarms, and debugginginformation to the log host. Information issaved to the log host in the file format foreasy reference.



11

ChannelNumber

DefaultChannel Name

OutputDirection

Description

3 Trapbuffer Trap buffer Outputs alarms to the alarm buffer. Therouter assigns a specific area to be the alarmbuffer for recording alarms.

4 Logbuffer Log buffer Outputs logs to the log buffer. The routerassigns a specified area to be the log bufferfor recording logs.

5 Snmpagent SNMP agent Outputs alarms to the SNMP agent.

6 Unspecified Unspecified Reserved, this channel can be configured tooutput to different directions.



9 Channel9 Log file Outputs information to log files that canreceive logs, traps, and debugginginformation. Information is saved to theUSB disk in the file format.

In the case of multiple log hosts, logs can be output through one channel or several channels.For example, some logs can be output to a log host through Channel 2 (loghost) and some logscan be output to another log host through Channel 6. For easy management, the name of Channel6 can be changed.

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

Figure 2-2 shows the format of logs.

Figure 2-2 Format of the output logs

TIMESTAMP HOSTNAME %%ddAAA/B/CCC(l)[DDD]: YYYY

Table 2-3 describes each field in a log message.



12

Table 2-3 Description of each field in a log message

Field Indication Description

TIMESTAMP Time to send out theinformation

Available formats for the timestamp are as follows:l boot: The timestamp in this format indicates a

relative time.l date: The timestamp in this format indicates the

system time. Timestamps in logs, alarms anddebugging information are in this format bydefault.

l short-date: Unlike the date format, timestampsin the short-date format do not indicate the year.

l format-date: The timestamp in this format isanother format of the system time.

l none: indicates that the information does notcontain any timestamp.

There is a space between the timestamp and thehost name.

HOSTNAME Host name By default, the name is Huawei.

%% Huawei logo Indicates that log information is output by aHuawei device.

dd Version number Identifies the version of the log format.

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

B Log level Indicates the severity level of a log.

CCC Brief description Describes the information type.

(l) Information type Indicates the user log identifier.

DDD Log ID A maximum of 1024 logs can be stored in the logbuffer. In the log file buffer, the value of thisparameter depends on the log buffer size.

YYYY Descriptor Indicates detailed information output from eachmodule to the information center.Before outputting logs, each module fills in thisfield to describe log content.

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

Figure 2-3 Format of the output alarms

TimeStamp HostName ModuleName/Severity/Brief:Description



13

Table 2-4 describes each field in an alarm message.

Table 2-4 Description of each field of in an alarm message

Field Indication Description

TimeStamp Time to send out theinformation

Available formats for the timestamp are as follows:l boot: The timestamp in this format indicates a

relative time.l date: The timestamp in this format indicates the

system time. Timestamps in logs, alarms anddebugging information are in this format bydefault.

l short-date: Unlike the date format, timestampsin the short-date format do not indicate the year.

l format-date: The timestamp in this format isanother format of the system time.

l none: indicates that the information does notcontain a timestamp.

There is a space between the timestamp and thehost name.

HostName Host name By default, the name is Huawei.There is a spacebetween the sysname and module name.

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

Severity Severity level Severity of traps.

Brief Brief information Provides brief information of the alarms.

Description Description Provides detailed description of the alarms.

2.3 Enabling Log OutputThis section describes how to output logs of a specific module to a log file, console, terminal,or log host.

2.3.1 Establishing the Configuration TaskBefore configuring the log output, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This can help you completethe configuration task quickly and accurately.



14

Applicable Environment

The system logs the operation information about devices in real time. It then outputs logs to thelog buffer, log file, console, terminal, and log host for storage and future reference. In thismanner, when faults occur on devices, users can locate the faults based on the logs.

Pre-configuration Tasks

Before configuring the log output, complete the following tasks:

l Connecting the router to the PC properly

l Ensuring that the route between the router and the log host is reachable

Data Preparation

To configure the log output, you need the following data.

No. Data

1 l Channel numberl Channel name

2 Module name

3 Address of the log host

4 Severity level of the log

5 (Optional) Size of the log buffer

2.3.2 Enabling the Information CenterIf the information center function is disabled, you can enable it. By default, this function isenabled.

Context

The information center classifies and outputs information. When it is heavily loaded withinformation processing, system performance degrades.

Procedure

Step 1 Run:system-view

The system view is displayed.

Step 2 Run:info-center enable

The information center is enabled.



15

By default, the information center is enabled.

----End

2.3.3 (Optional) Naming an Information ChannelNaming an information channel helps clarify what is output by each channel.

ProcedureStep 1 Run:

system-view


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

A channel is named.

----End

2.3.4 (Optional) Configuring the Function of Filtering Logs by IDsThe binary log function can filter specific logs.

ContextBinary logs provide the function of filtering specified logs by their IDs. To filter certain logs,the user can obtain IDs of these logs through log resolution tools and add these IDs to the logfiltering list.

After that, the information center does not send these logs in each output direction.


system-view


Step 2 Run:info-center filter-id { id } * &<1-50>

One or more IDs are added and a space is used to separate these IDs.

NOTECurrently, only 50 IDs can be shielded. The aggregation of these shielded IDs is called a log ID filteringlist. The log ID filtering list is arranged by ID values.

----End

2.3.5 (Optional) Configuring the Function of Generating a DataDictionary

To resolve log files on the log server, transform binary logs into text logs through the datadictionary.



16

ContextA data dictionary is used to transform binary logs into text logs. A data dictionary is theaggregation of log IDs and fixed information required in the log, such as the level, mnemonicsymbol, and format string. The generated data dictionary is downloaded by the externalresolution tool.

Procedure



Step 2 Run:info-center create-logbook { file-name | ftp ftp-address user-name user-name password password [ file-name file-name | port-id port-number ] * }

The data dictionary is generated.

----End

2.3.6 Outputting Logs to the Log BufferThe log buffer stores the latest logs generated by the system. You can set the log buffer size orchannels in this task.

Procedurel Configure the channel through which logs are output.

1. Run the following command on the router enabled with the information center:system-view

The system view is displayed.2. Run:

info-center source { module-name | default } channel { channel-number | channel-name } [ log { state { off | on } | level severity } * ]

Logs are sent to the information channel.

Logs can be output only after the information center is enabled.l Configure the channel through which logs are output.

1. Run the following command on the router enabled with the information center:system-view


info-center logbuffer [ channel { channel-number | channel-name } ]

The channel through which logs are output to the log buffer is configured.3. (Optional) Run:

info-center logbuffer [ channel { channel-number | channel-name } | size buffersize ] *

The size of the log buffer is configured.



17

After the information center is enabled, logs are output to the log buffer throughChannel 4 by default and the log buffer can cache a maximum of 512 logs.

----End

2.3.7 Outputting Logs to a Log FileWhen a fault occurs on the device, you locate the fault based on information saved in the logfile.

ContextNOTE

The default log storage medium is usb0. If usb0 is unavailable, the default log storage medium is usb1. Ifboth usb0 and usb1 are unavailable, the log files cannot be saved. The log storage path is in the format ofstorage medium name:/logfile, for example, usb0:/logfile.

Procedure

Step 1 Send logs to a channel.1. Run:

system-view


info-center source { module-name | default }channel { channel-number | channel-name } [ log { state { off | on } | level severity } * ]

Logs are sent the information channel.

Logs can be output only after the information center is enabled.

Step 2 Configure the channel through which logs are output to the log file.1. Run:

info-center logfile channel { channel-number | channel-name }

The channel through which logs are output to the log file is configured.

Step 3 (Optional) Configure the size of the log file output by the information center.1. Run:

info-center logfile size size

The size of the configuration file is set.

By default, the size of log files is 8 MB.

----End

2.3.8 Outputting Logs to the ConsoleBy outputting logs to the console, you can view the operating status of the device on the console.

Procedure

Step 1 Configure the logs to be output through the channel.



18

1. Do as follows on the router configured with the information center, run:system-view



Logs are added to the information channel.


Step 2 Configure the channel through which logs are output to the console.1. Run:

info-center console channel { channel-number | channel-name }

The channel through which logs are output to the Console is configured.2. Run:

quit

Return to the user view.

Step 3 Enable terminal display.1. Do as follows on the router configured with the information center, run:

terminal monitor

Terminal display is enabled.2. Run:

terminal logging

Displaying logs on the terminal is enabled.

----End

2.3.9 Outputting Logs to the TerminalBy outputting logs to the terminal, you can view the operating status of the device on the terminal.

Procedure

Step 1 Configure the logs to be output through the channel.1. Run:

system-view





Step 2 Configure the information channel through which logs are output to the terminal.1. Run:

info-center monitor channel { channel-number | channel-name }



19

The information channel through which logs are output to the terminal is configured.2. Run:

quit


Step 3 Enable terminal display.1. Run:

system-view


terminal monitor


terminal logging

The log display is enabled on the terminal.

----End

2.3.10 Outputting Logs to the Log HostBy outputting logs to the log host, you can view the operating status of the device on the loghost.

Procedure

Step 1 Configure the logs to be output through the channel.1. Do as follows on the router configured with the information center, run:

system-view




Step 2 Configure the channel through which logs are output to the log host.l (On an IPv4 network) Run:

info-center loghost ip-address [ channel { channel-number | channel-name } | facility local-number |{ language language-name | binary [ port ] } | public-net ] *

The channel through which logs are output to the log host is configured.By default, logs are not output to the log host after the information center is enabled.The system supports the configuration of a maximum of eight log hosts to realize backupamong log hosts.

----End

2.3.11 Checking the ConfigurationChecking the Configuration of Information Center



20

PrerequisiteThe configurations of the information center function are complete.

Procedurel Run the display channel [ channel-number | channel-name ] command to check the

configuration of a channel.l Run the display info-center [ statistics ] command to check the information recorded by

an information center.l Run the display logbuffer command to view the information recorded by a log buffer.l Run the display info-center filter-id { id } command to check whether the ID of a single

log is added into the filtering list.l Run the display info-center filter-id command to check whether IDs of all logs are added

into the filtering list.

----End

ExampleRun the display channel [ channel-number | channel-name ] command to check the contents ofinformation channels.

<Huawei> display channelchannel number: 0, channel name: console MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y warning Y debugging Y debugging channel number: 1, channel name: monitor MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y warning Y debugging Y debugging channel number: 2, channel name: loghost MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y informational Y debugging N debugging channel number: 3, channel name: trapbuffer MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default N informational Y debugging N debugging channel number: 4, channel name: logbuffer MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y warning N debugging N debugging channel number: 5, channel name: snmpagent MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default N debugging Y debugging N debugging channel number: 6, channel name: channel6 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging channel number: 7, channel name: channel7 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging channel number: 8, channel name: channel8 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging channel number: 9, channel name: channel9 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging



21

Run the display info-center command to check the contents of information center.

Information 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: 6, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 0, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 0Logfile: channel number: 9, channel name: channel9, language: EnglishInformation timestamp setting: log - date, trap - date, debug - date

Sent messages = 25, Received messages = 25

Run the display logbuffer command to view the logs in the log buffer.

<Huawei> display logbufferLogging buffer configuration and contents: enabled Allowed max buffer size: 1024 Actual buffer size: 512 Channel number: 4, Channel name: logcy Dropped messages: 0 Overwritten messages: 0 Current messages: 1 Aug 21 2007 18:33:31+00:00 AR200-V2R2C00-161 %%01DEFD/4/CPCAR_DROP_MPU(l)[0]:Some packets are dropped by cpcar on the MPU. (Packet-type=arp-request, Drop-Count=474)

Run the display info-center filter-id [ id ] command to check whether the log with the ID being1098649600 is added into the filtering list.

<Huawei> display info-center filter-id 1098649600ID : 1098649600Content : LSPM return error to TE when processing tunnel commit event! (TunnelName=[STRING], ErrorCode=[ULONG])Filtered Number : 0

Run the display info-center filter-id command to check whether IDs of all logs are added intothe filtering list.

<Huawei> display info-center filter-idID: 3221442627 Content: The message was discarded because module batch doesn't begin. (SourceModuleId=[ULONG], SourceModuleSubId=[ULONG], DestinationModuleId=[ULONG], DestinationModuleSubId=[ULONG]) Filtered Number: 0 ID: 3491254537 Content: Add the route [STRING] that have other flags besides deleted flag [USHORT] Filtered Number: 0



22

2.4 Enabling Alarm OutputThis section describes how to configure a specific module to output alarm information to logfiles, consoles, terminals, or SNMP agents.

2.4.1 Establishing the Configuration TaskBefore configuring the alarm output, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This can help you completethe configuration task quickly and accurately.

Applicable EnvironmentThe device can generate alarms in specific situations to draw attention of the administrators.Alarms can be output to the alarm buffer, log file, Console, terminal, and Network ManagementSystem (NMS), through which the administrator can easily locate and rectify the fault.

Pre-configuration TasksBefore enabling alarm output, complete the following tasks:

l Connecting the router and the NM station correctlyl Configuring routes between the router and the NM station

Data PreparationTo configure alarm output, you need the following data.

No. Data


2 Module name

3 Severity level of alarms

4 (Optional) Size of an alarm buffer

5 IP address of Network Management System


ContextClassifying and outputting a large amount of information degrades system performance.



23


system-view





----End

2.4.3 (Optional) Naming an Information ChannelNaming information channels helps clarify what is output by each channel.

ContextDo as follows on the router configured with the information center.


system-view



The information channel specified by the channel-number is named as channel-name.

----End

2.4.4 Outputting Alarms to the Alarm BufferBy default, alarms are output to the alarm buffer through a default channel. You can configurealarms to be output through a specific channel.

ContextDo as follows on the router configured with the information center:

ProcedureStep 1 Configure the alarms to be output through the channel.

1. Run:system-view


info-center source { module-name | default } channel { channel-number | channel-name } [ trap { state { off | on } | level severity } * ]



24

Alarms are added to the information channel.

For the specific modules, the default configurations are as follows:

For the log information, the state is on and the allowed information level is warning.

For the alarm information, the state is on and the allowed information level isdebugging.

For the debugging information, the state is off.

Step 2 Configure the channel through which alarms are output to the alarm buffer.1. Run:

info-center trapbuffer [ channel { channel-number | channel-name } ]

The alarm buffer is set to receive information.2. Run:

(optional)info-center trapbuffer [ channel { channel-number | channel-name } | size buffersize ] *

The channel through which alarms are output to the alarm buffer is configured.

After the information center is enabled, alarms default to be output through Channel 3 tothe alarm buffer and the alarm buffer can contain 256 pieces of information.

----End

2.4.5 Outputting Alarms to the Log FileWhen a fault occurs on the device, you can analyze the output alarms to provide references forfault location.


Procedure

Step 1 Send logs to the channel.1. Run:

system-view










25

Step 2 Configure the channel through which alarms are output to the log file.1. Run:


The channel through which alarms are output to the log file is configured.

By default, alarms are output through Channel 9 to the log file after the information centeris enabled.



The size of the log buffer is set.

By default, the size of log files is 8 MB.

----End

2.4.6 Outputting Alarms to the ConsoleBy outputting alarms to the console, you can view the operating status of the device on theconsole.


Procedure

Step 1 Configure the alarms to be output through the channel.1. Run:

system-view








Step 2 Configure the channel through which alarms are output to the console.1. Run:


The channel through which alarms are output to the Console is configured.

By default, alarms are output to the Console through Channel 0.



26

2. Run:quit


Step 3 Enable terminal display.1. Run the following command on the router configured with the information center:

terminal monitor


terminal trapping

Displaying alarms on the terminal is enabled.

----End

2.4.7 Outputting Alarms to the TerminalBy outputting alarms to the terminal, you can view the operating status of the device on theterminal.


Procedure

Step 1 Configure the alarms to be output through the channel.1. Run:

system-view








Step 2 Configure the channel through which alarms are output to the VTY terminal.1. Run:


The channel through which alarms are output to the VTY terminal is configured.

By default, alarms are output to the VTY terminal through Channel 1.2. Run:

quit



27



terminal monitor


terminal trapping

Displaying alarms on the terminal is enabled.

----End

2.4.8 Outputting Alarms to the SNMP AgentBy outputting alarms to the SNMP agent, you can view the operating status of the device on theNMS.


ProcedureStep 1 Configure the alarms to be output through the channel.

1. Run:system-view








Step 2 Configure the channel through which alarms are output to the SNMP agent.1. Run:

info-center snmp channel { channel-number | channel-name }

The channel through which alarms are output to the SNMP agent is configured.

By default, alarms are output to the SNMP agent through Channel 5.2. Run:

snmp-agent

SNMP agent is enabled.

----End



28

2.4.9 Checking the ConfigurationAfter configuring the alarm output, you can use related commands to confirm the configuration.

PrerequisiteThe configurations of the alarm output function are complete.


configuration of a channel.l Run the display info-center [ statistics ] command to check the information recorded by

the information center.l Run the display trapbuffer [ size value ] command to check the information recorded by

the alarm buffer.

----End

ExampleRun the display info-center command to show channels.

<Huawei> display channelchannel number: 0, channel name: console MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y warning Y debugging Y debugging channel number: 1, channel name: monitor MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y warning Y debugging Y debugging channel number: 2, channel name: loghost MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y informational Y debugging N debugging channel number: 3, channel name: trapbuffer MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default N informational Y debugging N debugging channel number: 4, channel name: logbuffer MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y warning N debugging N debugging channel number: 5, channel name: snmpagent MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default N debugging Y debugging N debugging channel number: 6, channel name: channel6 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging channel number: 7, channel name: channel7 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging channel number: 8, channel name: channel8 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging channel number: 9, channel name: channel9 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging



29

Run the display info-center command to show the data recorded by info-center.

<Huawei> 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: 6, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 0, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 0Logfile: channel number: 9, channel name: channel9, language: EnglishInformation timestamp setting: log - date, trap - date, debug - date


Run the display trapbuffer command. If alarms in the alarm buffer are displayed, it means thatthe configuration is successful.

<Huawei> display trapbufferTrapping buffer configuration and contents: enabled Allowed max buffer size: 1024 Actual buffer size: 256 Channel number: 3, Channel name: trapbuffer Dropped messages: 0 Overwritten messages: 713 Current messages: 1 #Aug 23 2007 18:47:19+00:00 AR200-V2R2C00-161 SECE/4/ARP_SIP_SPEEDLIMIT_ALARM:OID=1.3.6.1.4.1.2011.5.25.165.2.2.2.11 The arp packet speed with source ip 10.137.216.1 exceed the speed-limit value configed 5.

2.5 Enabling the Output of Debugging InformationThis section describes how to configure a specific module to output debugging information tolog files, consoles, terminals, or SNMP agents.

Context

CAUTIONDebugging degrades system performance. Therefore, after debugging, run the undo debuggingall command to disable debugging immediately. When the CPU usage is close to 100%,debugging ARP may cause boards to reset. So, confirm the action before you use the command.



30

2.5.1 Establishing the Configuration TaskBefore configuring the debugging message output, familiarize yourself with the applicableenvironment, complete the pre-configuration tasks, and obtain the required data. This can helpyou complete the configuration task quickly and accurately.

Applicable EnvironmentWhen faults occur on a device, you can enable the information center to output debugginginformation for easy faults location and analysis.

Pre-configuration TasksBefore enabling the output of debugging information, complete the following tasks:

l Connecting the router and the PC correctlyl Configuring routes between the router and the log host

Data PreparationTo enable the output of debugging information, you need the following data.

No. Data


2 Module name

3 Severity level of debugging information

4 IP address of a log host


ContextClassifying and outputting a large amount of information degrades system performance.

Procedure







31


----End

2.5.3 (Optional) Naming an Information ChannelNaming information channels helps clarify what is output by each channel.

ContextDo as follows on the router configured with the information center.

Procedure




The name of the specified channel is set.

----End

2.5.4 Outputting Debugging Information to the Log FileWhen a fault occurs on the device, you can analyze the output debugging messages to providereferences for fault location.


Procedure

Step 1 Configure debugging information to be output through the channel.1. Run:

system-view


info-center source { module-name | default } channel { channel-number | channel-name } [ debug { state { off | on } | level severity } * ]

Debugging information is added to the information channel.







32

Step 2 Configure the channel through which debugging information is output to the log file.1. Run:


The channel through which debugging information is output to the log file is configured.



By default, the debugging information is not saved in the log file. If you want the debugginginformation to be saved in the log file, run the info-center source default channel 9debug state on level severity command to add records to the information channel.

----End

2.5.5 Outputting Debugging Information to the ConsoleWhen logging in to the device through a console, output debugging messages to the console fora query in real time.


Procedure


system-view








Step 2 Configure the channel through which debugging information is output to the console.1. Run:


The channel through which debugging information is output to the console is configured.2. Run:

quit




33


terminal monitor


terminal debugging

Displaying debugging information on the terminal is enabled.

----End

2.5.6 Outputting Debugging Information to the TerminalWhen logging in to the device through a terminal, output debugging messages to the terminalfor query in real time.


Procedure


system-view








Step 2 Configure the channel through which debugging information is output to the terminal.1. Run:


The channel through which debugging information is output to the terminal is configured.2. Run:

quit



terminal monitor



34


terminal debugging

Displaying debugging information on the terminal is enabled.

----End

2.5.7 Outputting Debugging Information to the Log HostBy outputting debugging messages to the log host, you can view debugging messages moreconveniently.

Procedure


system-view




Step 2 Configure the channel through which debugging information is output to the log host.

l (On an IPv4 network) Run:info-center loghost ip-address [ channel { channel-number | channel-name } | facility local-number |{ language language-name | binary [ port ] } | public-net ] *

The channel through which debugging information is output to the log host is configured.By default, debugging information is not output to the log host after the information centeris enabled.The system supports the configuration of a maximum of eight log hosts to realize backupamong log hosts.

----End

2.5.8 Checking the ConfigurationAfter configuring the debugging message output, you can view the configuration of theinformation center.

PrerequisiteThe configurations of the debugging information function are complete.


configuration of a channel.



35

l Run the display info-center [ statistics ] command to check the information recorded byan information center.

----End

ExampleRun the display channel command. For example:

<Huawei> display channel 0channel number: 0, channel name: consoleMODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVELffff0000 default Y warning Y debugging Y debugging416e0000 ARP Y warning Y debugging Y debugging

Run the display info-center command. For example:

<Huawei> 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: 6, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 0, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 0Logfile: channel number: 9, channel name: channel9, language: EnglishInformation timestamp setting: log - date, trap - date, debug - date


2.6 Maintaining Information CenterThis section describes how to run the following commands to delete messages in the buffer ofthe information center. Note that deleted messages cannot be restored.

Context

CAUTIONStatistics about the information center cannot be restored after being cleared. So, confirm theaction before you use the command.



36

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

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

view.

----End

2.7 Information Center Configuration ExamplesThis section provides information center configuration examples.

2.7.1 Example for Outputting Logs to the Log FileThis section describes how to output logs of a specific module or specific severity level to thelog file. This enables maintenance engineers to monitor the operating status of the device andlocate a fault by checking the output logs.

Networking RequirementsAs shown in Figure 2-4, Router A is required to transport logs to a File Transfer Protocol (FTP)server. Maintenance engineers can easily obtain the operating status of Router A and locate anyfaults occurring on it.

NOTE

The default log storage medium is usb0. If usb0 is unavailable, the default log storage medium is USB 1.If both usb0 and usb1 are unavailable, the log files cannot be saved. The log storage path is in the formatof storage medium name:/logfile, for example, usb0:/logfile.

Figure 2-4 Networking diagram of log output to the log file

FTP ServerRouterA

IP network

10.1.1.1/16

10.2.1.1/16GE1/0/0

Configuration RoadmapThe configuration roadmap is as follows:

1. Enable the information center.2. Configure the contents of the logs to be output.3. Configure the channel through which logs are output.4. Configure logs to be output to the FTP server.



37

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

l IP address of each interfacel Information channel numberl Module enabled to output logsl Severity levels of logsl Language in which logs are outputl IP address of the FTP serverl User name and password of the FTP server

Procedure

Step 1 Configure the routing protocol to make the router and the FTP server reachable. (The detailedprocedure is not mentioned here.)

Step 2 Configure the user name and password that are used on the FTP server. (The configuration detailsare not provided here.)

Step 3 Enable the information center:<Huawei> system-view[Huawei] sysname RouterA[RouterA] info-center enable

Step 4 Configure the logs to be output through the channel.

# Configure the module enabled to output the logs and the severity levels of the logs that areallowed to be output.

[RouterA] info-center source ip channel channel9 log level warnings

Step 5 Configure the channel through which logs are output.

# Configure the channel through which logs are output to the log file.

[RouterA] info-center logfile channel channel9[RouterA] quit

Step 6 Configure logs to be output to the FTP server.

# Log in to the FTP server.

<RouterA> ftp 10.1.1.1

# Configure logs to be output to the FTP server.

[RouterA-ftp] put log.log[RouterA-ftp] quit<RouterA>

Step 7 Verify the configuration.

# View the logs that are output through the channel.

<RouterA> display info-centerInformation Center: enabled Log host: Console: channel number: 0, channel name: console Monitor:



38

channel number: 1, channel name: monitor SNMP Agent: channel number: 5, channel name: snmpagent Log buffer: enabled max buffer size: 1024, current buffer size: 512 current messages: 204, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0 Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 256, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 29 Logfile: channel number: 9, channel name: channel9, language: English Information timestamp setting: log - date, trap - date, debug - date Sent messages = 1514, Received messages = 1514

# View the received logs on the FTP server. (The display is omitted here.)

----End

Configuration Files# sysname RouterA# info-center source IP channel 9 log level warning#interface GigabitEthernet1/0/0 ip address 10.2.1.1 255.255.0.0#ip route-static 10.1.0.0 255.255.0.0 10.2.1.2#return

2.7.2 Example for Outputting Logs to Log HostsThis section describes how to output logs of different modules or severity levels to different loghosts, and how to configure backup log hosts.

Networking RequirementsAs shown in Figure 2-5, logs of multiple types and severity levels must be output to differentlog hosts through information channels.

Router sends the logs (with a severity level as notification) generated on the ForwardingInformation Base (FIB) module and the IP module to the log host Server 1. Server 3 functionsas a backup router of Server 1.

Router sends the logs (with a severity level as warning) generated on the Point-to-Point Protocol(PPP) module and the AAA module to the log host Server 1. Server 4 functions as a backuprouter of Server 2.

Both the Router s and the log hosts need to be configured.



39

Figure 2-5 Networking diagram of outputting logs to the log host

172.16.0.1/24GE1/0/0

Router

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. Name the tunnel.3. Specify the module enabled to output logs.4. Configure the channel for outputting logs.5. Configure the source interface that sends logs.6. Configure the log host.


l IP address of the log hostl Information channel numberl Name of the channel through which logs are outputl Module enabled to output logsl Information severity levell Language in which the log is output

Procedure

Step 1 Configure routing protocols to make the router and log server routable. (The detailed procedureis not mentioned here.)

Step 2 Configure the channel for outputting logs.

# Enable the information center.

<Huawei> system-view[Huawei] info-center enable

Step 3 Name the channel.

# Name the channel through which logs are output.



40

[Huawei] info-center channel 6 name loghost1

Step 4 Configure the channel through which logs are output.

# Configure the module enabled to output logs and the severity levels of logs allowed to beoutput.[Huawei] info-center source fib channel loghost log level notifications[Huawei] info-center source ip channel loghost log level notifications[Huawei] info-center source ppp channel loghost1 log level warnings[Huawei] info-center source aaa channel loghost1 log level warnings

Step 5 Configure the source interface that sends logs.

# Configure the source interface that sends logs.[Huawei] info-center loghost source gigabitethernet 1/0/0

Step 6 Configure the logs to be output to a specified log host.

# Specify Server 1 as the log server and Server 3 as the backup log server to receive the logsfrom the FIB module and the IP module. The logs are output in English, by Local2.[Huawei] info-center loghost 10.1.1.1 channel loghost facility local2 language english[Huawei] info-center loghost 10.1.1.2 channel loghost facility local2 language english

# Specify Server 2 as the log server and Server 4 as the backup log server to receive the logsfrom the PPP module and the AAA module. The logs are output by Local4.[Huawei] info-center loghost 10.2.1.1 channel loghost1 facility local4 language english[Huawei] info-center loghost 10.2.1.2 channel loghost1 facility local4 language english

Step 7 Configure the log server.

A log server is used to collect logs of the device when the storage memory of the router is notlarge enough to record them.

Log servers can be installed with a Unix or Linux operating system or with the log software ofa third party.

If installed with a Unix or Linux operating system, logs enabled with Syslog can be collectedby the host.

If the host has a Linux operating system, choose from the following options:

l To create log files:Run the touch loghost.info command in the directory /var/log to create a file loghost.infoto record logs of the router.

l To edit configuration files:Edit etc/syslog.conf to loghost.info /var/log/router.log, which specifies the log host name.The logs with the severity level listed are then output to /var/log/loghost.log.

l To configure the file etc/sysconfig/syslog:Modify syslogd_options="-m o" to syslogd_option="-1 -m o", enabling the system to recordthe logs of remote devices.

l To enable Syslog:Run the service syslog restart command.

If the host has a third party's log software installed, this software can be configured to implementhost's log collection function. For example, the HUAWEI iManager 2000 supports various log



41

management settings and can therefore receive, filter, save, and forward the Syslog messagessent by the device.

For the procedure for configuring log services on the HUAWEI iManager N200, refer to theHUAWEI iManager N2000 DM - Compound Package User Manual Volume I.


# Display the configuration of the log host.

<Huawei> display info-centerInformation Center: enabledLog host: the interface name of the source address:GigabitEthernet1/0/0 10.1.1.1, channel number: 2, channel name: loghost language: english, host facility: local2 10.1.1.2, channel number: 2, channel name: loghost language: english, host facility: local2 10.2.1.1, channel number: 6, channel name: loghost1 language: english, host facility: local4 10.2.1.2, channel number: 6, channel name: loghost1 language: english, host facility: local4 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: 218, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0 Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 256, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 150Logfile: channel number: 9, channel name: channel9, language: English Information timestamp setting: log - date, trap - date, debug - boot


----End

Configuration Files# info-center channel 6 name loghost1 info-center source FIB channel 2 log level notification info-center source IP channel 2 log level notification info-center source PPP channel 6 log level warning info-center source AAA channel 6 log level warning info-center loghost source GigabitEthernet1/0/0 info-center loghost 10.1.1.1 facility local2 info-center loghost 10.1.1.2 facility local2 info-center loghost 10.2.1.1 channel 6 facility local4 info-center loghost 10.2.1.2 channel 6 facility local4#interface GigabitEthernet1/0/0 ip address 172.16.0.1 255.255.255.0# ip route-static 10.1.1.0 255.255.255.0 172.16.0.2 ip route-static 10.2.1.0 255.255.255.0 172.16.0.2



42

#return

2.7.3 Example for Configuring Binary Logs to be Sent to the LogHost

This section describes how to output logs to the log host in binary mode. Outputting logs inbinary mode can effectively lighten the network load.

Networking RequirementsAs shown in Figure 2-6, binary logs generated on Router A are sent to the log host in real time.Users or maintenance personnel can analyze the log through log analysis tools and locate thefault.

Figure 2-6 Example for Configuring Binary Logs to be sent to the Log Host

RouterA Loghost

GE1/0/010.1.1.1/24

10.1.1.6/24


1. Enable the information center on the router.2. Add the ID of the log to be filtered.3. Generate a data dictionary and send it to the log server.4. Configure binary logs to be sent to the log host.

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

l ID of the log to be filteredl File name of the generated data dictionaryl IP address of the FTP serverl User name and password used for logging into the FTP serverl IP address of the log host

Procedure

Step 1 Configure routes between Router A and Loghost. (The detailed procedure is not mentioned here.)

Step 2 Enable the information center.

# Enable the information center.

<Huawei> system-view



43

[Huawei] info-center enable

Step 3 Add the ID of a log to be filtered.

# Configure the module and channel used to output alarm messages.

[Huawei] info-center filter-id 1077514264

Step 4 Generate a data dictionary and send it to the log server.

# Configure alarm messages to be output to the SNMP agent.

[Huawei] info-center create-logbook ftp 10.1.1.6 user-name ftp password ftp file-name dicx.xml

After the data dictionary is sent successfully, a prompt is displayed indicating Info: Succeededin creating a data dictionary.. For further confirmation, you can check whether the datadictionary is successfully sent to the log server.

Step 5 Configure binary logs to be sent to the log host.[Huawei] info-center loghost 10.1.1.6 binary


# Check the added ID of the log to be filtered.

[Huawei] display info-center filter-id 1077514264ID: 1077514264Content: task: [string] ip: [string] user: [string] command: [string]Filtered Number: 3

# Check the channel used by the SNMP agent to output alarms.

[Huawei] display info-center[Huawei] display info-centerInformation Center: enabled Log host: 10.1.1.6, channel number: 2, channel name: loghost language: english, host facility: local7 binary loghost, port number: 514 Console: channel number: 0, channel name: console Monitor: channel number: 1, channel name: monitor SNMP Agent: channel number: 5, channel name: snmpagent Log buffer: enabled max buffer size: 1024, current buffer size: 512 current messages: 499, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0 Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 9, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 0 Logfile: channel number: 9, channel name: channel9, language: English Information timestamp setting: log - date, trap - date, debug - date Sent messages = 15274, Received messages = 15274

----End

Configuration Files#



44

interface GigabitEthernet1/0/0 ip address 10.1.1.1 255.255.255.0#info-center filter-id 1077514264info-center loghost 10.1.1.6 binary#return

2.7.4 Example for Outputting Alarms to the SNMP AgentAfter alarms are output to the SNMP agent, the NM Station can receive the alarms sent fromthe device.

Networking RequirementsAs shown in Figure 2-7, alarms are required to be output first to the SNMP agent and then tothe NM Station through SNMP Agent.

Figure 2-7 Networking diagram of outputting alarms to the SNMP Agent

NM Station Agent10.1.1.2/2410.1.1.1/24

GE1/0/0


1. Enable the information center on the router.2. Specify the module enabled to output logs and configure the channel through which the

alarm is output.3. Enable the outputting alarm to the SNMP agent.4. Enable transmitting alarms to the NM Station through SNMP.


l Information channel numberl Module enabled to output alarmsl Severities of alarms

Procedure

Step 1 Enable the information center.<Huawei> system-view[Huawei] info-center enable

Step 2 Specify the module enabled to output alarms and configure the channel used to output alarms.

# Specify the module enabled to output alarms and configure the channel used to output alarms.



45

[Huawei] info-center source ip channel channel7 trap level informational state on

NOTE

By default, alarms are output through the SNMP agent and information about all modules is displayed.

Step 3 Enable outputting alarms to the SNMP agent.

# Enable outputting alarms to the SNMP agent.

[Huawei] info-center snmp channel channel7

Step 4 Enable transmitting alarms to the NM Station through SNMP agent.

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

[Huawei] snmp-agent sys-info version v2c

# Configure the alarm function.

[Huawei] snmp-agent trap enableAll switches of SNMP trap/notification will be open. Continue? [Y/N]:y [Huawei] snmp-agent target-host trap-hostname nms address 10.1.1.1 trap-paramsname trapnms[Huawei] snmp-agent target-host trap-paramsname trapnms v2c securityname public


# View the channel used to output alarms to the SNMP agent.

[Huawei] display info-centerInformation Center: enabled Log host: 10.1.1.6, channel number: 2, channel name: loghost language: english, host facility: local7 binary loghost, port number: 514 Console: channel number: 0, channel name: console Monitor: channel number: 1, channel name: monitor SNMP Agent: channel number: 7, channel name: channel7 Log buffer: enabled max buffer size: 1024, current buffer size: 512 current messages: 503, channel number: 4, channel name: logbuffer dropped messages: 0, overwritten messages: 0 Trap buffer: enabled max buffer size: 1024, current buffer size: 256 current messages: 9, channel number: 3, channel name: trapbuffer dropped messages: 0, overwritten messages: 0 Logfile: channel number: 9, channel name: channel9, language: English Information timestamp setting: log - date, trap - date, debug - date Sent messages = 15299, Received messages = 15299

# View the alarms output through the channel selected by SNMP agent.

[Huawei] display channel 7channel number: 7, channel name: channel7 MODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVEL ffff0000 default Y debugging Y debugging N debugging c16a0000 IP Y debugging Y informational N debugging

# View the alarms output to the NM Station through SNMP agent.



46

[Huawei] display snmp-agent target-host Traphost list: Target host name: nms Traphost address: 10.1.1.1 Traphost portnumber: 162 Target host parameter: trapnms Total number is 1 Parameter list trap target host: Parameter name of the target host: trapnms Message mode of the target host: SNMPV2C Trap version of the target host: v2c Security name of the target host: public Total number is 1

----End

Configuration Files# info-center source IP channel 7 trap level informational info-center snmp channel 7#interface GigabitEthernet1/0/0 ip address 10.1.1.2 255.255.255.0# snmp-agent snmp-agent local-engineid 000007DB7F00000100003598 snmp-agent sys-info version v2c snmp-agent target-host trap-hostname nms address 10.1.1.1 udp-port 162 trap-paramsname trapnms snmp-agent target-host trap-paramsname trapnms v2C securityname public snmp-agent trap enable#return

2.7.5 Example for Outputting the Debugging Information to theConsole

After debugging messages are configured to be output to the console, log in to the device throughthe console. When a fault occurs, run the debugging command to view debugging messages.

Networking RequirementsAs shown in Figure 2-8, it is required to output the debugging information of the AddressResolution Protocol (ARP) module to the console.

Figure 2-8 Networking diagram of outputting information to the console

Router

Console

PC




47

1. Enable the information center.

2. Set the logs to be output to the console and the information module.

3. Configure the channel through which the debugging information is output.

4. Enable the terminal monitor function and display the debugging information.

Data Preparation

To complete the configuration, you need the following data:

l Information channel number

l Module enabled to output the logs

l Information severity level

Procedure

Step 1 Enable the information center.<Huawei> system-viewInfo: Current terminal monitor is on.[Huawei] info-center enableInfo: Current terminal debugging is on.

Step 2 Allow the debugging on the ARP module to be output to the Console with the severity level ofthe information as debugging.[Huawei] info-center source arp channel console debug level debugging[Huawei] info-center console channel console[Huawei] quit

Step 3 Enable the terminal monitor function to display the debugging information.<Huawei> terminal monitor<Huawei> terminal debugging

Step 4 Enable ARP module debugging.<Huawei> debugging arp packet


# View the configuration of the channel.

<Huawei> display channel 0channel number: 0, channel name: consoleMODU_ID NAME ENABLE LOG_LEVEL ENABLE TRAP_LEVEL ENABLE DEBUG_LEVELffff0000 default Y warning Y debugging Y debuggingc16e0000 ARP Y warning Y debugging Y debugging

----End

Configuration Files# info-center source ARP channel 0#return



48

3 PoE Configuration

About This Chapter

This chapter describes the basic concepts and configuration methods of PoE.

3.1 Introduction to PoEThis section describes the basic concepts of PoE.

3.2 PoE Features Supported by the AR1200-SThis section describes the PoE features supported by the AR1200-S.

3.3 Configuring PoE FunctionsThis section describes how to configure PoE functions.

3.4 Configuration ExamplesThis section provides an example for configuring PoE on the AR1200-S.

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management 3 PoE Configuration


49

3.1 Introduction to PoEThis section describes the basic concepts of PoE.

Power over Ethernet (PoE) refers to power supply over a 10Base-T, 100Base-TX, or 1000Base-T twisted pair cable. PoE can be used to effectively provide power for terminals such as IPphones, Access Points (APs), portable device chargers, point-of-sale (POS) machines, cameras,and data collection. Terminals are powered when they access the network. Therefore, the indoorcabling of power supply does not need to be considered. Currently, PoE supports the unifiedstandard IEEE 802.3af and 802.3at, which enables devices developed by different vendors to becompatible with each other.

3.2 PoE Features Supported by the AR1200-SThis section describes the PoE features supported by the AR1200-S.

NOTE

l Currently, only AR1220W-S supports the PoE features.

l Currently, only Ethernet 0/0/4 to Ethernet 0/0/7 on the SRU of the AR1200-S support PoE.

PoE Functions Provided by the AR1200-Sl The PoE power supply is independent of the system power supply.

l The AR1200-S complies with the legacy power supply standard, and can also providepower for PDs that do not comply with the legacy standard.

l The AR1200-S can provide power and transmit data at the same time through signal lines1, 3, 2, and 6 of the category-3 or category-5 twisted pair. If the PD can obtain power onlythrough idle lines 4, 5, 7, and 8 of the twisted pair, the AR1200-S can provide power througha converter.

l The AR1200-S provides power for devices through Ethernet electrical interfaces on themain control board at a distance of up to 100 m.

l The maximum PoE power of an electrical interface is 30 W.

NOTE

l When the AR1200-S provides power for a PD, the PD can work without other external power supplies.

l If a PD has an external power supply, the AR1200-S and the external power supply of the PD work inredundancy mode.

PoE Power Supplies Supported by the AR1200-S

The AR1200-S does not support built-in power modules. It provides only one external PoEpower module and its default power is 100 W.

3.3 Configuring PoE FunctionsThis section describes how to configure PoE functions.



50

3.3.1 Establishing the Configuration TaskBefore configuring PoE, familiarize yourself with the applicable environment, complete the pre-configuration tasks, and obtain the required data. This will help you complete the configurationtask quickly and accurately.

Applicable EnvironmentThe AR1200-S can detect whether a device connected to it needs power supply and providepower for it.

According to the actual requirements on the network, you can perform the following operationsby using commands:

l Set the maximum output power, power supply management mode, and reserved power ofa board.

l Configure a board to allow high inrush current during power-on.l Set the backup mode of the PoE power supplies. Currently, the AR1200-S supports one

backup mode: 1+0, meaning that PoE power supplies are not backed up.l Set the alarm threshold of the power consumption percentage.l Enable the PoE function on an interface.l Set the maximum output power and power supply priority of an interface.l Power on and power off a PD on an interface.l Set the power-off time range of a PoE interface.l Configure a PSE to check the compatibility of PDs.

Pre-configuration TasksBefore configuring the PoE function, complete the following task:

Installing the PoE power supply and PoE board on the AR1200-S

3.3.2 Configuring the PoE Function GloballyIn the system view, you can set the maximum output power of a board, set the PoE power supplymanagement mode, configure a board to allow high inrush current during power-on, set thepercentage of the reserved PoE power against the total PoE power, set the backup mode of thePoE power supplies, and set the alarm threshold of the power consumption percentage.

Procedurel Optional: Set the maximum output power of a board.

NOTE

The maximum output power of a board that you can set depends on the number of PoE power suppliesand the capability of the PoE power supplies.

1. Run:system-view


poe max-power slot_max_power slot slot-id



51

The maximum output power of a board is set.

The value of slot_max_power ranges from 0 to the maximum output power of the PoEpower supplies in the system. The unit is mW.

By default, the maximum output power of a PoE board depends on the power of thePoE power supply provided by the system.

l Optional: Set the PoE power supply management mode.1. Run:

system-view


poe power-management { auto | manual } slot slot-id

The PoE power supply management mode of the board in the specified slot is set.

By default, the AR1200-S uses the automatic power management mode.l Optional: Configure a board to allow high inrush current during power-on.

If a PD does not comply with IEEE 802.3at or 802.3af, high inrush current is generatedwhen the PD is powered on. In this case, the PSE cuts off the power of the PD to protectitself. If the PSE is required to provide power for the PD, the PSE must allow high inrushcurrent.

1. Run:system-view


poe high-inrush enable slot slot-id

The PoE board is configured to allow high inrush current during power-on.

By default, a board does not allow high inrush power during power-on.l Optional: Set the percentage of the reserved PoE power to the total PoE power.

The AR1200-S can dynamically allocate power to each interface according to the powerconsumption of each interface. The power consumption of a PD keeps changing when thePD is running. The AR1200-S periodically calculates the total power consumption of allthe PDs connected to boards. If the total power consumption exceeds the upper thresholdof the board, the AR1200-S cuts off the power of the PDs on the interfaces of low priorityto ensure that other PDs can run normally.

Sometimes, the power consumption increases sharply and the available power of a boardor the entire equipment cannot support the burst increase of power. At this time, the softwaresystem has not found that the total power consumption exceeded the upper threshold;therefore, the AR1200-S does not power off interfaces of low priority in time. As a result,the PoE power supply is shut down for overload protection, and all PDs are powered off.

This problem can be solved by setting proper reserved power. When the power consumptionincreases sharply, the reserved power can support the system running. Then the systemsoftware has time to power off interfaces of low priority to ensure stable running of otherPDs.

1. Run:system-view



52


poe power-reserved power-reserved

The percentage of the reserved PoE power to the total PoE power is set.

By default, 20% of the total PoE power is reserved.l Optional: Set the backup mode of the PoE power supplies.

1. Run:system-view


poe-power backup-mode using-power-num

The backup mode of the PoE power supplies used by the board in a slot is set.

NOTEBy default, the backup mode of the AR1200-S PoE power supplies is 1+0.

l Optional: Set the alarm threshold of power consumption percentage.1. Run:

system-view


poe-power utilization-threshold thresholdvalue

The alarm threshold of power consumption percentage is set.

The value range of thresholdvalue in the poe-power utilization-threshold dependson the reserved power. If the reserved power is set to 25% of the total PoE power byusing the poe power-reserved command, the value of thresholdvalue ranges from75% to 99%. By default, the alarm threshold is 90%. Therefore, an alarm is generatedwhen the power consumed accounts for 90% of the total power.

----End

3.3.3 Configuring the PoE Function on an InterfaceIn the interface view, you can enable the PoE function on an interface, set the maximum outputpower of an interface, set the power supply priority of an interface, manually power on or poweroff the PD connected to an interface, enable an interface to check PD compatibility, and set thepower-off time range of a PoE interface.

Procedurel Enable the PoE function on an interface.

1. Run:system-view


interface interface-type interface-number



53

The interface view is displayed.3. Run:

poe enable

The PoE function is enabled. By default, the PoE function is enabled on all interfaces.

NOTE

Currently, only Ethernet 0/0/4 to Ethernet 0/0/7 on the SRU of the AR1200-S support PoE.

l Optional: Set the maximum output power of an interface.1. Run:

system-view




poe power port_max_power

The maximum output power of the interface is set.

The unit of port_max_power is mW.

NOTE

l By default, the maximum output power of an interface is 37 W.

l The maximum output power of a board is not equal to the maximum output power of aninterface multiplied by the number of interfaces on the board because not all interfaces onthe board can provide maximum output power at the same time.

l Optional: Set the power supply priority of an interface.1. Run:

system-view




poe priority { critical | high | low }

The power supply priority of the interface is set.

By default, the power supply priority of an interface is low.

The priorities in descending order are critical, high, and low.l Optional: Manually power on or off the PD connected to an interface.

1. Run:system-view


poe { power-on | power-off } interface interface-type interface-number



54

The PD connected to an interface is powered on or powered off manually.

NOTE

When the manual power management mode is adopted, you must manually power on or poweroff PDs on interfaces.

l Optional: Set the power-off time range of a PoE interface.1. Run:

system-view


time-range time-name { start-time to end-time days | from time1 date1 [ to time2 date2 ] }

The power-off time range of a PoE interface is set.

NOTE

To configure multiple time ranges with the same name on the AR1200-S, run the precedingcommand with the same value of time-name repeatedly.

3. Run:interface interface-type interface-number


poe power-off time-range time-name

The power-off time range takes effect on the interface.l Optional: Enable an interface to check PD compatibility.

NOTEBefore enabling an interface to check compatibility of PDs, you must enable PoE on the PSE. Afterthis function is enabled, the interface can detect the PDs that do not comply with IEEE 802.3af or802.3at.

1. Run:system-view




poe legacy enable

The interface is enabled to check PD compatibility.

By default, an interface does not check PD compatibility.

----End

3.3.4 Checking the ConfigurationAfter the PoE configurations are complete, you can view the PoE power status, deviceinformation, and PoE configuration on an interface.



55

PrerequisiteThe PoE power supply and PoE board are installed, and the PoE function is configured.

Procedure

Step 1 Run the display poe-power command to view the status of the PoE power supply.

Step 2 Run the display poe device command to view information about the devices that support thePoE function.

Step 3 Run the display poe information [ slot slot-id ] command to view the PoE information.

Step 4 Run the display poe power interface interface-type interface-number command to view theoutput power of an interface.

Step 5 Run the display poe power slot slot-id command to view the output power of the interfaces onthe board in the specified slot.

Step 6 Run the display poe power-state interface interface-type interface-number command to viewthe status of PoE power supply on an interface.

Step 7 Run the display poe power-state slot slot-id command to view the status of the PoE powersupply on the board in the specified slot.

----End

3.4 Configuration ExamplesThis section provides an example for configuring PoE on the AR1200-S.

3.4.1 Example for Configuring PoEThis section provides an example of PoE power supply.

Networking RequirementsAs shown in Figure 3-1, the requirements as follows:

l IP phones are connected to Ethernet 0/0/4 and Ethernet 0/0/5.l Other PDs are connected to Ethernet 0/0/6 and Ethernet 0/0/7.l The PD connected to Ethernet 0/0/6 has a high priority in power supply.l The maximum output power of the PoE board in slot 0 is 100 W.l The PD connected to Ethernet 0/0/7 requires the input power of no more than 20 mW.



56

Figure 3-1 Networking diagram of the PoE application

IP Phone PD

PDIP Phone

Ethernet0/0/4

Ethernet0/0/5 Ethernet0/0/7

Ethernet0/0/6


1. In the system view, set the maximum output power of the PoE board in slot 0.2. In the interface view, set the power supply priority of Ethernet 0/0/6.3. In the interface view, set the maximum output power of Ethernet 0/0/7.

Data PreparationTo complete the configuration, you need the following data:l Power supply priority of Ethernet 0/0/6l Maximum output power of the PoE board in slot 0l Maximum output power of Ethernet 0/0/7

Procedure

Step 1 In the system view, set the maximum output power of the PoE board in slot 0.

# Set the maximum output power of the PoE board in slot 0 to 100 W.

NOTE

On the AR1200-S, the unit of the output power is mW.<Huawei> system-view[Huawei] poe max-power 100000 slot 0

Step 2 Set the maximum output power of Ethernet 0/0/7.<Huawei> system-view[Huawei] interface ethernet 0/0/7[Huawei-Ethernet0/0/7] poe power 20[Huawei-Ethernet0/0/7] quit[Huawei]

Step 3 Set the power supply priority of Ethernet 0/0/6 to critical.



57

[Huawei] interface ethernet 0/0/6[Huawei-Ethernet0/0/6] poe priority critical


# Display the PoE power supply status of the LPU in slot 0.

<Huawei> display poe power-state slot 0PortName PowerOn/Off Enabled Priority Status --------------------------------------------------------------------------------Ethernet0/0/4 On Enable Low Delivering-power Ethernet0/0/5 On Enable Low Delivering-power Ethernet0/0/6 On Enable Critical Delivering-power Ethernet0/0/7 On Enable Low Delivering-power

----End

Configuration Files# poe max-power 100000 slot 0 #interface Ethernet0/0/6 poe priority critical #interface Ethernet0/0/7poe power 20#return



58

4 Mirroring Configuration

About This Chapter

This document describes the mirroring configuration procedures and provides configurationexamples.

4.1 Introduction to MirroringThis section describes the principle and concepts of mirroring.

4.2 Mirroring Features Supported by the AR1200-SThe AR1200-S supports local mirroring.

4.3 Configuring Local Port MirroringTo monitor and analyze all the packets passing through the mirrored interface that is located onthe same AR1200-S as the observing interface, configure local port mirroring on the AR1200-S.

4.4 Configuring Local Flow MirroringTo monitor and analyze the packets with same characteristics passing through the mirroredinterface that is located on the same AR1200-S as the observing interface, configure local portmirroring on the AR1200-S.

4.5 Configuring Packet Capture Using MirroringThis section describes how to configure packet capture using mirroring so that packets enteringthe device interface can be displayed on the terminal or saved to the device.

4.6 Configuration ExamplesThis section describes the networking requirements, configuration roadmap, and datapreparation for mirroring and provides the configuration examples.

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management 4 Mirroring Configuration


59

4.1 Introduction to MirroringThis section describes the principle and concepts of mirroring.

DefinitionMirroring is a function that copies the packets on the mirrored interface (source interface) to theobserving interface (destination interface). When the observing interface is connected to amonitoring device, you can use the monitoring device to analyze the packets copied to theobserving interface for network monitoring and fault troubleshooting.

TermsMirroring is classified into port mirroring and flow mirroring. Port mirroring and flow mirroringinvolve the following interfaces:

l Observing interfaceAn observing interface is connected to a monitoring device and is used to export the trafficcopied from the mirrored interface.

l Mirrored interfaceA mirrored interface is the interface to be observed. In port mirroring, all the packets passingthrough the mirrored interface are copied to the observing interface. In flow mirroring, allthe packets matching the traffic classifier rules are copied to the observing interface.

4.2 Mirroring Features Supported by the AR1200-SThe AR1200-S supports local mirroring.

Local mirroring includes local port mirroring and local flow mirroring.

Local Port MirroringAs shown in Figure 4-1, when the mirrored interface connected to monitored devices and theobserving interface are located on the same device, local port mirroring can be configured onthe Router to monitor and analyze the packets on the monitored devices. The Router copies thepackets passing through a mirrored interface and sends the packets to a specified observinginterface for analysis and monitoring. In port mirroring, all the packets passing through amirrored interface are copied to an observing interface.



60

Figure 4-1 Networking diagram of local port mirroring

Monitoringdevice

Observinginterface

Router

InterfacePacket flows

Mirroredinterface

Copied packet flows

Mirroredinterface

Local Flow Mirroring

As shown in Figure 4-2, the Router copies specified data passing through a flow mirroredinterface to a specified observing interface for analysis and monitoring. A flow mirroredinterface refers to the interface to which a traffic policy containing the flow mirroring action isapplied. If the packets passing through the flow mirrored interface match a traffic classifier inthe traffic policy on this interface, the packets are copied and sent to an observing interface.

Figure 4-2 Networking diagram of local flow mirroring

Observinginterface

Monitoring device

Interface

Traffic classification match

Copied packet flowsMirrored flowsPacket flows

Flow mirroredinterface

Flow mirroredinterface

Router



61

Local Mirroring Specifications

On the AR1200-S configured with local mirroring, only one observing interface can beconfigured. The observing interface can only be configured on LAN-side Ethernet interfaces.The packets on multiple interfaces can be mirrored to one observing interface.

In local port mirroring, the AR1200-S supports inter-board mirroring. That is, the observinginterface and mirrored interface can be on different LPUs of a router.

In local flow mirroring, when a WAN-side interface is used as a mirrored interface, the AR1200-S supports inter-board mirroring. When a LAN-side interface is used as a mirrored interface,the AR1200-S does not support inter-board mirroring.

NOTE

Observing and mirrored interfaces are configured on the same device.

The packets on the mirrored interface are copied to the observing interface; therefore, the observinginterface is considered as the outbound interface of the packets. In this case, the discarded packets on themirrored interface are not counted.

When you configure the observing interface and mirrored interface, pay attention to the interfacebandwidth. For example, if a GE interface is used as the mirrored interface and an Ethernet interface isused as the observing interface, the observing interface has no sufficient capability to receive packets andmirroring packets may be lost.

Remote Mirroring Specifications

Only one observing server can be configured, and there must be a reachable route from themirrored interfaces to the observing server. The packets on multiple mirrored interfaces can bemirrored to one observing server.

4.3 Configuring Local Port MirroringTo monitor and analyze all the packets passing through the mirrored interface that is located onthe same AR1200-S as the observing interface, configure local port mirroring on the AR1200-S.

4.3.1 Establishing the Configuration TaskBefore configuring local port mirroring, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This will help you completethe configuration task quickly and accurately.


An intranet has high requirements for information security and privacy protection. You canconfigure mirroring on an interface to monitor incoming and outgoing data packets. Themanagement server that has the monitoring software installed can capture these packets foranalysis and fault location.

To monitor and analyze all the packets passing through the mirrored interface that is located onthe same AR1200-S as the observing interface, configure local port mirroring on the AR1200-S.



62

Pre-configuration TasksEnsuring that the link layer protocol status of interfaces is Up

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

No. Data

1 Type and number of the observing interface.

2 Type and number of the mirrored interface.

3 Direction to which packets are mirrored.

4.3.2 Configuring a Local Observing InterfaceThe local observing interface is used to export the packets copied from the mirrored interface.

ContextAfter an interface is configured as the observing interface, other configurations are notrecommended on the interface. Otherwise, the following situations may occur:l If other service traffic exists on the observing interface in addition to mirrored packets, the

packet source cannot be differentiated.l If congestion occurs on the observing interface, mirrored packets may be discarded because

the priority of mirrored is low.

Procedure



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

A local observing interface is configured.

observe-port-index specifies the observing interface index.

NOTE

On the AR1200-S, only one observing interface can be configured.Other configurations are not recommended on the observing interface; otherwise, non-mirrored packetsmay be forwarded through the observing interface.

----End

4.3.3 Configuring a Local Mirrored InterfaceAll the packets passing through the local mirrored interface are copied to the observing interface.



63

Context

If you want to configure an Eth-Trunk as a mirrored interface, run the interface eth-trunk trunk-id command to create an Eth-Trunk first. Pay attention to the following points when you use anEth-Trunk as a mirrored interface:

l If an Eth-Trunk is configured as a mirrored interface, its member interfaces cannot beconfigured as mirrored interfaces. To configure a member interface as a mirrored interface,delete it from the Eth-Trunk first.

l If a member interface of an Eth-Trunk is configured as a mirrored interface, the Eth-Trunkcannot be configured as a mirrored interface. To configure the Eth-Trunk as a mirroredinterface, delete the member interface from it first.

Procedure



Step 2 Run:interface interface-type interface-number

The interface view is displayed.

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

A local mirrored interface is configured.

observe-port-index specifies the observing interface index. The value of this parameter must bethe same as the value set in 4.3.2 Configuring a Local Observing Interface.

NOTE

To ensure that mirroring packets sent from the observing interface carry the same as that of the originalpackets, the downstream mirrored interface and observing interface on the SRU of the AR1220 must beconfigured with the same VLAN tag.

If the downstream mirroring interface is configured with an ACL, the ACL does not take effect for mirroringpackets. After the mirrored interface is specified, all packets on the interface are mirrored regardless ofwhether a traffic policy is configured.

----End

4.3.4 Checking the ConfigurationAfter port mirroring is configured, check the usage of the observing interface and mirroredinterface.

PrerequisiteThe configurations of port mirroring are complete.

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



64

l Run the display port-mirroring command to check the mirrored interface in portmirroring.

----End

4.4 Configuring Local Flow MirroringTo monitor and analyze the packets with same characteristics passing through the mirroredinterface that is located on the same AR1200-S as the observing interface, configure local portmirroring on the AR1200-S.

4.4.1 Establishing the Configuration TaskBefore configuring local flow mirroring, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This will help you completethe configuration task quickly and accurately.


An intranet has high requirements for information security and privacy protection. You canconfigure mirroring on an interface to monitor incoming and outgoing data packets. Themanagement server that has the monitoring software installed can capture these packets foranalysis and fault location.

To monitor and analyze the packets with some characteristics passing through the mirroredinterface that is located on the same AR1200-S as the observing interface, configure local portmirroring on the AR1200-S.


None.

Data Preparation

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

No. Data

1 Type and number of the observing interface

2 Type and number of the traffic mirrored interface

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

4.4.2 Configuring a Local Observing InterfaceThe local observing interface is used to export the packets copied from the mirrored interface.



65

ContextAfter an interface is configured as the observing interface, other configurations are notrecommended on the interface. Otherwise, the following situations may occur:l If other service traffic exists on the observing interface in addition to mirrored packets, the

packet source cannot be differentiated.l If congestion occurs on the observing interface, mirrored packets may be discarded because

the priority of mirrored is low.

Procedure



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

A local observing interface is configured.

observe-port-index specifies the observing interface index.

NOTE

On the AR1200-S, only one observing interface can be configured.

Other configurations are not recommended on the observing interface; otherwise, non-mirrored packetsmay be forwarded through the observing interface.

----End

4.4.3 Configuring Complex Traffic ClassificationSelect proper traffic classification rules and configure complex traffic classification as required.

For the configuration procedure, see Configuring Traffic Classification in the Huawei AR1200-S Series Enterprise Routers Configuration Guide - QoS.

4.4.4 Creating a Local Traffic BehaviorConfigure the local flow mirroring action to copy the packets matching traffic classificationrules to the observing interface.

Procedure



Step 2 Run:traffic behavior behavior-name

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

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



66

The flows matching rules are mirrored to the specified observing interface.

observe-port-index specifies the observing interface index. The value of this parameter must bethe same as the value set in 4.4.2 Configuring a Local Observing Interface.

----End

4.4.5 Configuring a Traffic PolicyAfter the traffic classifier and the flow mirroring action are configured, bind the traffic classifierand the traffic behavior to a traffic policy and apply the traffic policy to an interface.

Procedure

Step 1 Create a traffic policy.

1. Run:system-view


2. Run:traffic policy policy-name

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

3. Run:classifier classifier-name behavior behavior-name

A traffic classifier is bound to a traffic behavior in the traffic policy.

classifier-name specifies the name of a traffic classifier and must be the same as the nameof a traffic classifier in 4.4.3 Configuring Complex Traffic Classification; behavior-name specifies the name of a traffic behavior and must be the same as the name of a trafficbehavior in 4.4.4 Creating a Local Traffic Behavior.

4. Run:quit

Quit the traffic policy view.

Step 2 Apply the traffic policy to an interface.

1. Run:interface interface-type interface-number

The mirrored interface view is displayed.

2. Run:traffic-policy policy-name inbound

The traffic policy is applied to the flow mirrored interface.

NOTE

In flow mirroring, when a WAN-side interface is used as a mirrored interface, the AR1200-S supportsinter-board mirroring. When a LAN-side interface is used as a mirrored interface, the AR1200-S does notsupport inter-board mirroring.

----End



67

4.4.6 Checking the ConfigurationAfter local flow mirroring is configured, check the observing interface and the configuration ofthe traffic classifier, traffic behavior, and traffic policy.

PrerequisiteThe configurations of local flow mirroring are complete.

Procedurel Run the display observe-port command to check the observing interface in local port

mirroring.

l Run the display port-mirroring command to check the mirrored interface in local portmirroring.

l Run the display traffic behavior user-defined [ behavior-name ] command to check theconfiguration of the traffic behavior.

l Run the display traffic classifier user-defined [ classifier-name ] command to check theconfiguration of the traffic classifier.

l Run the display traffic policy user-defined [ policy-name [ classifier classifier-name ] ]command to check the configuration of the traffic policy.

l Run the display traffic-policy policy-name applied-record command to check theapplication of the traffic policy.

----End

4.5 Configuring Packet Capture Using MirroringThis section describes how to configure packet capture using mirroring so that packets enteringthe device interface can be displayed on the terminal or saved to the device.


Local port mirroring or local flow mirroring requires that an observing port needs to be directlyconnected to a monitoring device. If the observing port is not directly connected to a mirroringdevice, capture packets using mirroring to locate faults so that packets entering the deviceinterface can be displayed on the terminal or saved to the device.

If mirrored packets are saved to the device, log in to the device through FTP and download themirrored packets for analysis.

NOTE

l Currently, only incoming traffic can be captured using mirroring.

l Before using the capture-packet interface command again, wait until the last command execution iscomplete.

l Packet capturing rate must be lower than 256 pps. If the traffic is heavy, some packets matching rulesmay not be captured.

l Currently, the AR1200-S supports the following mirrored interfaces: Ethernet interface,GigabitEthernet interface, ATM interface, Serial interface, and Eth-trunk.



68

Pre-configuration TasksEnsuring that the interface link layer protocol status is Up and the storage memory is sufficientfor mirrored packets

Procedure



Step 2 (Optional) Configure a numbered ACL. For details, see ACL Configuration in ConfigurationGuide-Security.

NOTE

To capture mirrored packets matching an ACL, configure the ACL.

Step 3 Run:capture-packet interface interface-type interface-number [ acl acl-number ] destination { file file-name | terminal } * [ car cir cir-value | time-out time out value | packet-num packet number | packet-len { packet length | total-packet ] *

Rules are defined to capture mirrored packets on the device and display the packet informationon the terminal.

----End

ExampleAfter the configuration is complete, mirrored packets are displayed on the terminal or saved tothe device. If mirrored packets are saved to the device, download the mirrored packets foranalysis. The following shows information about mirrored packets displayed on the terminal:

Info: Captured packets will be showed on terminal. [Huawei] Packet: 1 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0a 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 2 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 3 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 4 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01



69

08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0a 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 5 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 6 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 7 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0a 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 8 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 9 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 10 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0a 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 11 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- Packet: 12 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0a 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 -------------------------------------------------------



70

Packet: 13 ------------------------------------------------------- ff ff ff ff ff ff 00 e0 fc 01 00 08 08 06 00 01 08 00 06 04 00 01 00 e0 fc 01 00 08 02 01 01 03 00 00 00 00 00 00 0b 01 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------------------------------- ------------------capture report----------------------- file: NULL interface: GigabitEthernet1/0/0 acl: 2000 car: 64pps timeout: 60s packets: 100 (expected) 13 (actual) length: 128 (expected) -------------------------------------------------------

4.6 Configuration ExamplesThis section describes the networking requirements, configuration roadmap, and datapreparation for mirroring and provides the configuration examples.

4.6.1 Example for Configuring Local Port MirroringThe local port mirroring function allows you to monitor the packets on a local device.

Networking Requirements

As shown in Figure 4-3, the R&D department and marketing department are connected toEthernet0/0/0 and Ethernet0/0/1 on the Router. The server (that is, the monitoring device) thathas the monitoring software installed is connected to Ethernet0/0/2 on the Router to analyze thecaptured packets. To ensure information security, configure local port mirroring on the Routerto monitor all the packets sent by the R&D department and marketing department.

Figure 4-3 Networking diagram of local port mirroring

Eth0/0/0

Eth0/0/1

Eth0/0/2

LSWA

LSWB

Router Server

R&D department

Marketing department



71


1. Configure Ethernet0/0/2 as a local observing interface.2. Configure Ethernet0/0/0 and Ethernet0/0/1 as mirrored interfaces.

Data PreparationTo complete the configuration, you need the following data:l Type and number of the observing interfacel Type and number of the mirrored interfacel Index number of the observing interface, that is, 1

ProcedureStep 1 Configure an observing interface.

# Configure Ethernet0/0/2 on the Router as an observing interface.<Huawei> system-view[Huawei] observe-port 1 interface Ethernet 0/0/2

Step 2 Configure mirrored interfaces.

# Configure Ethernet0/0/0 on the Router as the local mirrored interface to monitor the packetssent by the R&D department.[Huawei] interface Ethernet 0/0/0[Huawei-Ethernet0/0/0] port-mirroring to observe-port 1 inbound[Huawei-Ethernet0/0/0] quit

# Configure Ethernet0/0/1 on the Router as the local mirrored interface to monitor the packetssent by the marketing department.[Huawei] interface Ethernet 0/0/1[Huawei-Ethernet0/0/1] port-mirroring to observe-port 1 inbound[Huawei-Ethernet0/0/1] quit[Huawei] quit


# Check the configuration of the observing interface.<Huawei> display observe-port --------------------------------------------------------------------------- Index : 1 Interface: Ethernet0/0/2 Used : 2 ---------------------------------------------------------------------------

# Check the configuration of mirrored interfaces.<Huawei> display port-mirroring ---------------------------------------------------------------------- Mirror-port Direction Observe-port ---------------------------------------------------------------------- 1 Ethernet0/0/0 Inbound Ethernet0/0/2 2 Ethernet0/0/1 Inbound Ethernet0/0/2 ----------------------------------------------------------------------

# View the packet statistics on Ethernet0/0/0, Ethernet0/0/1, and Ethernet0/0/2. The number ofpackets on Ethernet0/0/2 equals the sum of the numbers of packets on Ethernet0/0/0 and



72

Ethernet0/0/1. Alternatively, view all the packets received by Ethernet0/0/0 and Ethernet0/0/1by using the server. Packets on Ethernet0/0/0 and Ethernet0/0/1 are mirrored by the Router.

<Huawei> display interface Ethernet 0/0/0Ethernet0/0/0 current state : UPDescription:HUAWEI, AR Series, Ethernet0/0/0 InterfaceSwitch Port,The Maximum Frame Length is 1628IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 10e0-1220-8001Last physical up time : 2010-10-07 22:24:31 UTC-05:00Last physical down time : 2010-10-05 22:22:22 UTC-05:00Current system time: 2010-10-22 15:48:52-05:13Port Mode: COMMON FIBERSpeed : 100, Loopback: NONEDuplex: FULL, Negotiation: ENABLEMdi : NORMALLast 300 seconds input rate 728 bits/sec, 0 packets/secLast 300 seconds output rate 32 bits/sec, 0 packets/secInput peak rate 13608 bits/sec,Record time: 2008-03-07 22:24:32Output peak rate 528 bits/sec,Record time: 2008-03-07 22:24:34

Input: 62754 packets, 8937914 bytes Unicast: 0, Multicast: 62754 Broadcast: 0, Jumbo: 0 Discard: 0, Total Error: 0

CRC: 0, Giants: 0 Jabbers: 0, Throttles: 0 Runts: 0, DropEvents: 0 Alignments: 0, Symbols: 0 Ignoreds: 0, Frames: 0Output: 6816 packets, 477120 bytes Unicast: 0, Multicast: 6816 Broadcast: 0, Jumbo: 0 Discard: 0, Total Error: 0

Collisions: 0, ExcessiveCollisions: 0 Late Collisions: 0, Deferreds: 0 Buffers Purged: 0 Input bandwidth utilization threshold : 100.00% Output bandwidth utilization threshold: 100.00% Input bandwidth utilization : 0.01% Output bandwidth utilization : 0.00%<Huawei> display interface Ethernet 0/0/1Ethernet0/0/1 current state : UPDescription:HUAWEI, AR Series, Ethernet0/0/1 InterfaceSwitch Port,The Maximum Frame Length is 1628IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 10e0-1220-8001Last physical up time : 2010-10-07 22:24:31 UTC-05:00Last physical down time : 2010-10-05 22:22:22 UTC-05:00Current system time: 2010-10-22 15:48:52-05:13Port Mode: COMMON FIBERSpeed : 100, Loopback: NONEDuplex: FULL, Negotiation: ENABLEMdi : NORMALLast 300 seconds input rate 728 bits/sec, 0 packets/secLast 300 seconds output rate 32 bits/sec, 0 packets/secInput peak rate 13608 bits/sec,Record time: 2008-03-07 22:24:32Output peak rate 528 bits/sec,Record time: 2008-03-07 22:24:34


CRC: 0, Giants: 0 Jabbers: 0, Throttles: 0 Runts: 0, DropEvents: 0 Alignments: 0, Symbols: 0 Ignoreds: 0, Frames: 0



73

Output: 6817 packets, 477190 bytes Unicast: 0, Multicast: 6817 Broadcast: 0, Jumbo: 0 Discard: 0, Total Error: 0

Collisions: 0, ExcessiveCollisions: 0 Late Collisions: 0, Deferreds: 0 Buffers Purged: 0 Input bandwidth utilization threshold : 100.00% Output bandwidth utilization threshold: 100.00% Input bandwidth utilization : 0.01% Output bandwidth utilization : 0.00%<Huawei> display interface Ethernet 0/0/2Ethernet0/0/2 current state : UPDescription:HUAWEI, AR Series, Ethernet0/0/2 InterfaceSwitch Port,The Maximum Frame Length is 1628IP Sending Frames' Format is PKTFMT_ETHNT_2, Hardware address is 10e0-1220-8001Last physical up time : 2010-10-07 22:24:31 UTC-05:00Last physical down time : 2010-10-05 22:22:22 UTC-05:00Current system time: 2010-10-22 15:48:52-05:13Port Mode: COMMON FIBERSpeed : 100, Loopback: NONEDuplex: FULL, Negotiation: ENABLEMdi : NORMALLast 300 seconds input rate 728 bits/sec, 0 packets/secLast 300 seconds output rate 32 bits/sec, 0 packets/secInput peak rate 13608 bits/sec,Record time: 2008-03-07 22:24:32Output peak rate 528 bits/sec,Record time: 2008-03-07 22:24:34


CRC: 0, Giants: 0 Jabbers: 0, Throttles: 0 Runts: 0, DropEvents: 0 Alignments: 0, Symbols: 0 Ignoreds: 0, Frames: 0Output: 0 packets, 0 bytes Unicast: 0, Multicast: 0 Broadcast: 0, Jumbo: 0 Discard: 0, Total Error: 0

Collisions: 0, ExcessiveCollisions: 0 Late Collisions: 0, Deferreds: 0 Buffers Purged: 0 Input bandwidth utilization threshold : 100.00% Output bandwidth utilization threshold: 100.00% Input bandwidth utilization : 0.01% Output bandwidth utilization : 0.00%

----End

Configuration Filesl Configuration file of the Router

# observe-port 1 interface Ethernet0/0/2#interface Ethernet0/0/0 port-mirroring to observe-port 1 inbound#interface Ethernet0/0/1 port-mirroring to observe-port 1 inbound #return



74

4.6.2 Example for Configuring Local Flow MirroringWith the local flow mirroring function, the AR1200-S can monitor the packets with the samecharacteristics.

Networking Requirements

As shown in Figure 4-4, an enterprise's R&D department connects to the Router throughEthernet0/0/0. A server with the monitoring software installed is connected to Ethernet0/0/1 onthe Router to analyze the captured packets. The enterprise needs to monitor all the IPv4 packetssent from host 192.168.1.10/24 in the R&D department.

Figure 4-4 Local flow mirroring network

Eth0/0/0 Eth0/0/1

Router Server

HostA192.168.1.10/24

R&D department

Configuration Roadmap

The configuration roadmap is as follows:

1. Configure Ethernet0/0/1 as the observing interface.

2. Create a traffic classifier to match the IPv4 packets with the source IP address192.168.1.10/24.

3. Create a traffic behavior and bind it to the local flow mirroring action.

4. Create a traffic policy and bind it to the traffic classifier and traffic behavior.

5. Apply the traffic policy to Ethernet0/0/0.

Data Preparation

To complete the configuration, you need the following data:

l Type and number of the observing interface

l Type and number of the mirrored interface

l Observing interface index, 1

l Traffic classifier, c1

l Traffic behavior, b1

l Traffic policy, p1



75

Procedure

Step 1 Configure the local observing interface.

# Configure Ethernet0/0/1 on the Router as the observing interface.

<Huawei> system-view[Huawei] observe-port 1 interface Ethernet 0/0/1

Step 2 Configure the traffic classifier c1.

# Create IPv4 ACL 2000 on the Router to match the IPv4 packets with destination address192.168.1.10.

<Huawei> system-view[Huawei] acl number 2000[Huawei-acl-basic-2000] rule permit source 192.168.1.10 0[Huawei-acl-basic-2000] quit

# Create a traffic classifier named c1 and bind it to ACL 2000.

[Huawei] traffic classifier c1 [Huawei-classifier-c1] if-match acl 2000[Huawei-classifier-c1] quit

Step 3 Create a traffic behavior named b1 and configure the local flow mirroring action in the trafficbehavior.[Huawei] traffic behavior b1[Huawei-behavior-b1] mirroring to observe-port 1 [Huawei-behavior-b1] quit

Step 4 Configure a traffic policy.

# Create a traffic policy named p1 on the Router, bind the traffic behavior and traffic classifierto the traffic policy, and apply the traffic policy to the inbound direction of Ethernet0/0/0.

[Huawei] traffic policy p1[Huawei-trafficpolicy-p1] classifier c1 behavior b1 [Huawei-trafficpolicy-p1] quit[Huawei] interface Ethernet0/0/0 [Huawei-Ethernet0/0/0] traffic-policy p1 inbound[Huawei-Ethernet0/0/0] quit


# View the traffic classifier configuration.

<Huawei> display traffic classifier user-defined c1 User Defined Classifier Information: Classifier: c1 Operator: OR Rule(s) : if-match acl 2000

# View the traffic policy configuration.

<Huawei> display traffic policy user-defined p1 User Defined Traffic Policy Information: Policy: p1 Classifier: c1 Operator: OR Behavior: b1 Mirroring to cpu

----End



76

Configuration Filesl Configuration file of the Router

# observe-port 1 interface Ethernet 0/0/1 # acl number 2000 rule 5 permit source 192.168.1.10 0 # traffic classifier c1 operator or if-match acl 2000 # traffic behavior b1 mirroring to observe-port 1 # traffic policy p1 classifier c1 behavior b1 # interface Ethernet0/0/0 traffic-policy p1 inbound # return



77

5 Hardware Management

About This Chapter

This chapter describes hardware management on the AR1200-S, including power on and poweroff of boards, electronic label backup, and board reset.

5.1 Introduction to Hardware ManagementHardware management indicates the operations performed on hardware resources after thehardware is installed. Hardware configurations include reset, backup, power on, and power off.

5.2 Hardware Management Supported by the AR1200-SThis section describes the hardware management operations supported by the AR1200-S.

5.3 Powering On and Off the BoardThis section describes how to power on and off the board.

5.4 Backing Up Electronic LabelsThis section describes how to back up electronic labels.

5.5 Setting Fan SpeedThis section describes how to set fan speed.

5.6 Resetting the LPUThis section describes how to reset the LPU.

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management 5 Hardware Management


78

5.1 Introduction to Hardware ManagementHardware management indicates the operations performed on hardware resources after thehardware is installed. Hardware configurations include reset, backup, power on, and power off.

Hardware configurations reduce the frequency at which hardware resources are plugged in andpulled out or installed and uninstalled, which improves the reliability of hardware resources.

5.2 Hardware Management Supported by the AR1200-SThis section describes the hardware management operations supported by the AR1200-S.

The AR1200-S supports the following hardware operations:

l Powering on and powering off the board

l Backing up the electronic label

l Setting the rotating speed of a fan

l Resetting the LPU

5.3 Powering On and Off the BoardThis section describes how to power on and off the board.

5.3.1 Establishing the Configuration TaskBefore powering on or powering off a board, familiarize yourself with the applicableenvironment, complete the pre-configuration tasks, and obtain the required data. This will helpyou complete the configuration task quickly and accurately.

Application Environment

Powering on and off boards remotely reduces energy consumption and facilitates boardoperations.

NOTEThe AR200-S boards are hot swappable. Therefore, you do not need to remotely power off boards beforehot swapping them.


Powering on the router

Data Preparation

To configure the commands for powering on or powering off the board, you need the followingdata.



79

No. Data

1 Slot number of the board to be powered off

2 Slot number of the board to be powered on

5.3.2 Powering Off a BoardYou can run a command to remotely power off a board.

Procedurel Run the following command in any view:

power off slot slot-id

The board is powered off.

----End

5.3.3 Powering On a BoardYou can run a command to remotely power on a board.

Procedure

Step 1 Run the following command in any view:power on slot slot-id

The board is powered on.

----End

5.3.4 Checking the ConfigurationAfter a board is powered on or powered off, run the following commands to check theconfigurations.

ContextConfiguring power-on and power-off of the board is complete.

Procedure

Step 1 Run the display device [ slot slot-id ] command in any view to check the board status.

----End

Result

After boards are powered off, the power status is displayed as PowerOff. After boards arepowered on, the power status is displayed as PowerOn.



80

5.4 Backing Up Electronic LabelsThis section describes how to back up electronic labels.

5.4.1 Establishing the Configuration TaskBefore backing up electronic labels, familiarize yourself with the applicable environment,complete the pre-configuration tasks, and obtain the required data. This will help you completethe configuration task quickly and accurately.

Applicable EnvironmentElectronic labels play an important role in handling network faults and replacing hardware inbatches. Therefore, backing up electronic labels is a must.

l When a fault occurs on the network, you can obtain information on related hardwareconveniently and accurately and improve the efficiency of maintenance tasks by usingelectronic labels. For example, you can run queries on the maintenance cases of theknowledge base, the preparation of spare boards, and the tests of related indexes. Inaddition, you can efficiently analyze and trace defects in the hardware by analyzing andcollecting statistics on the electronic labels of the faulty hardware.

l When you need to replace hardware in batches, you can accurately view the distribution ofhardware in the entire network through the electronic labels recorded in the archive systemsof clients' devices. In this manner, you can pre-estimate the impact of hardware replacementand formulate corresponding policies to make batch hardware replacement more efficient.

Pre-configuration TasksBefore backing up electronic labels, ensure that the AR1200-S and the FTP server are routable.

Data PreparationTo back up electronic labels, you need the following data.

No. Data

1 Name of the electronic label to be backed up

2 (Optional) Slot number of the electronic label

3 (Optional, applicable to backing up the electronic label to the FTP server) Addressof the FTP server, and user name and password

4 (Optional, applicable to backing up the electronic label to the TFTP server) Addressof the TFTP server

5.4.2 Backing Up Electronic LabelsThe AR1200-S can back up electronic labels to the FTP server, TFTP server, flash memory, orUSB disk.



81

Procedurel Back up electronic labels to the flash memory, or USB disk

1. Run:backup elabel filename [ slot-id ]

Electronic labels are backed up to the flash memory, or USB disk.

This command can be run in any view.

l Back up electronic labels to an FTP server.1. Run:

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

Electronic labels are backed up to an FTP server.

l Back up electronic labels to a TFTP server.1. Run:

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

Electronic labels are backed up to a TFTP server.

----End

5.5 Setting Fan SpeedThis section describes how to set fan speed.

5.5.1 Establishing the Configuration TaskBefore adjusting fan speed, familiarize yourself with the applicable environment, complete thepre-configuration tasks, and obtain the required data. This will help you complete theconfiguration task quickly and accurately.


When fan speed does not adapt to the current application environment of the device, you canadjust the fan speed.



Data Preparation

To set fan speed, you need the following data.

No. Data

1 Slot number of the fan module and expected fan speed



82

5.5.2 Setting Fan SpeedYou can adjust the fan speed.

ContextCheck the upper and lower thresholds of board temperature and current temperature of boardsusing the display temperature { all | slot slot-id } command. If the temperature of a boardexceeds the upper threshold, adjust the fan speed on the AR1200-S.

Procedure



Step 2 Run:set fan-speed fan slot-id percent percent

Fan speed is set.

By default, fans run in automatic mode. In this mode, the system changes the fan speed whendetecting that the board temperature increases or decreases. The automatic mode reduces noisesand saves energy without affecting normal system running.

You can manually change the fan speed. By default, only users of level 2 and level 3 can runthe set fan-speed command to set the fan speed.

----End

5.5.3 Checking the ConfigurationAfter fan speed is set, you can check the configurations.

ContextAdjusting fan speed is complete.

Procedurel Run the display fan command to check the status, running mode, and speed of the fan.

----End

5.6 Resetting the LPUThis section describes how to reset the LPU.

5.6.1 Establishing the Configuration TaskBefore resetting an LPU, familiarize yourself with the applicable environment, complete thepre-configuration tasks, and obtain the required data. This will help you complete theconfiguration task quickly and accurately.



83


When the LPU fails to be upgraded or fails to work normally, you need to reset the LPU.



Data Preparation

To reset the LPU, you need the following data.

No. Data

1 Slot number of the LPU to be reset

5.6.2 Resetting the LPUWhen an LPU fails to be upgraded or fails to work normally, you need to reset the LPU.

Context

CAUTIONWhen the LPU works abnormally, try to find and remove the fault rather than resetting the LPUdirectly to avoid service interruption.

Procedure

Step 1 Run:reset slot slot-id

The LPU in the specified slot is reset.

----End

5.6.3 Checking the ConfigurationAfter an LPU is reset, you can check the LPU status and resetting cause.

ContextResetting the LPU is complete.

Procedurel Run the display device command to check the LPU status.



84

l Run the display reset-reason [ slot slot-id ] command to check the reason for resetting theLPU.

----End



85

6 Auto-Config

About This Chapter

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

6.1 Auto-Config OverviewThis section describes the functions and advantages of Auto-Config.

6.2 Auto-Config Features Supported by the AR1200-SThis section describes the intermediate file, Option parameters, and process of Auto-Configsupported by the AR1200-S.

6.3 Deploying Unconfigured RoutersThis section describes how to deploy unconfigured Routers.

6.4 Configuration ExamplesThis section provides examples for configuring Auto-Config, including networkingrequirements, configuration notes, and configuration roadmap.

Huawei AR1200-S Series Enterprise RoutersConfiguration Guide - Device Management 6 Auto-Config


86

6.1 Auto-Config OverviewThis section describes the functions and advantages of Auto-Config.

Auto-Config Functions

When a new or unconfigured router is powered on, a version file, patch file, and configurationfile must be loaded to the router. If routers are located dispersedly, the maintenance personnelhave to manually configure each router, which requires a heavy workload. The Auto-Configfunction implements remote device configuration and reduces maintenance costs. The routersrunning Auto-Config automatically downloads version file, patch file, and configuration file.

Auto-Config Advantages

Maintenance personnel do not need to manually configure each device. Auto-Config simplifiesnetwork configurations and implements unified management and remote debugging on routers.

6.2 Auto-Config Features Supported by the AR1200-SThis section describes the intermediate file, Option parameters, and process of Auto-Configsupported by the AR1200-S.

NOTE

Auto-Config deployment and USB deployment are mutually exclusive.

Intermediate File

The intermediate file arnet.ini is used in the Auto-Config process. The intermediate file recordsthe mappings between the router's MAC address (or ESN) and system software name, versionnumber, patch file name, and configuration file name. If the version file, patch file, andconfiguration file are stored on the FTP or TFTP server, its system software name extensionmust be .cc, the patch file name extension must be .pat, and the configuration file name extensionmust be .zip or .cfg. After the router obtains the IP address of the FTP or TFTP server, itdownloads the file arnet.ini from the FTP or TFTP server to search for the names of the requiredsystem software, version number, patch file, and configuration file, and then downloads filesfrom the FTP or TFTP server.

NOTE

Auto-Config uses Option 67 to obtain the configuration file first. If Option 67 is not configured, Auto-Config obtains the intermediate file.

Each row in the intermediate file describes a device. The intermediate file contains information about amaximum of 1000 devices.

For example, if the MAC address of an AR1200-S is 0018-82C5-AA89, the ESN is9300070123456789, the system software name is auto_V200R001C00.cc, the version isV200R001C00, the patch file is auto_V200R001C00.pat, and the configuration file isauto_V200R001C00.cfg, the contents of the intermediate file arnet.ini are as follows:

MAC=0018-82C5-AA89;ESN=9300070123456789;vrpfile=auto_V200R001C00.cc;vrpver=V200R001C00;patchfile=auto_V200R001C00.pat;cfgfile=auto_V200R001C00.cfg;



87

NOTE

l When configuring the intermediate file, enter the MAC address and ESN, or either of them. Theconfiguration file is mandatory, and the version file and patch file are optional. The three files can beconfigured in any sequence.

l A MAC address (or an ESN), a system software name, patch file name, and configuration file nameare separated by semicolons. A MAC address is in xxxx-xxxx-xxxx-xxxx or xx-xx-xx-xx format. Thefile name is case insensitive and contains only letters, digits, and underscores.

l The system software name and version information must be available in the intermediate file, andversion information in the system software name must be the same as that in the intermediate file.Version information must be contained in the system software.

Auto-Config ProcessFigure 6-1 shows the Auto-Config process.



88

Figure 6-1 Auto-Config process

DHCP Request packets are sent

periodically

Are DHCP Reply

Packetsreceived?

Auto-Config starts

No

Is the configuration file

obtained?

Set it as the configuration file for

next startup

End

Yes

No

Does the device need to be

upgraded?

Start a timer to set the delay in restarting the

device

Can a patch file be

downloaded to the device?

Obtain a version file Obtain a patch file

Is the version file obtained?

Is the patch file obtained?

Are DHCP Reply

packets valid?

Parse Option parameters

Obtain a configuration file

Yes

No

No

Yes

Yes

Are there the version file

name and version

information?

Is there patch file information?

No

No No

No No

Yes Yes

Yes

Is there ACS Option information?

Is there Option

information about the configuration

file?

Obtain and parse the intermediate file

No

No

Yes

End

Yes Configure the ACS

Yes YesThe timer expires, and the device is restarted

Set it as the version file for next startup

Set it as the patch file for next startup



89

The Auto-Config process involves three phases:l Parsing Options

1. Obtain the IP address and configuration of the FTP or TFTP server.A router automatically enables the DHCP client function on the uplink Ethernetinterface in Up state, and broadcasts DHCP Request packets (assuming that an IPaddress pool, Option parameters, and gateway information have been configured onthe DHCP server). Then the DHCP server sends the related configurations to therouter, including the IP address assigned to the router, IP address of the FTP or TFTPserver, FTP user name and password, and default gateway address.If no DHCP Reply packet is received or the received DHCP Reply packet is invalid,a DHCP Request packet is sent every 5 minutes. After 24 hours, a DHCP Requestpacket is sent every hour.

2. Parse Option parameters.

a. If the received DHCP Reply packet contains Option 43, ACS information needsto be configured. After the basic ACS configuration is complete, the Auto-Configprocess ends, and Auto-Config is suspended to wait for ACS deployment.

b. If the received DHCP Reply packet does not contain Option 67, the intermediatefile needs to be obtained. Then the router downloads the intermediate filearnet.ini from the FTP or TFTP server and obtains information about the filesto be downloaded from the intermediate file. Subsequently, the process ofobtaining files is started.

c. If the received DHCP Reply packet contains Option 67, the process of obtainingfiles is started.

l Obtaining files

1. (Optional) Download a system software.If the space is insufficient, delete version files from the file system according to thesetting of Option 146.After a system software is downloaded successfully, it is automatically set as thesystem software for the next startup.If the system software fails to be obtained, it is downloaded once every 30 minutes.If it cannot be obtained after 3 days, it is downloaded once every 2 hours. If it cannotbe obtained after 30 days, the process of downloading the system software stops andwaits to be handled manually.

2. (Optional) Download a patch file.After the patch file is downloaded successfully, it is automatically set as the patch filefor the next startup.If the patch file fails to be obtained, it is downloaded once every 30 minutes. If itcannot be obtained after 3 days, it is downloaded once every 2 hours. If it cannot beobtained after 30 days, the process of downloading the patch file stops and waits tobe handled manually.

3. Download a configuration file.After the configuration file is downloaded successfully, it is automatically set as theconfiguration file for the next startup.If the configuration file fails to be obtained, it is downloaded once every 30 minutes.If it cannot be obtained after 3 days, it is downloaded once every 2 hours. If it cannot



90

be obtained after 30 days, the process of downloading the configuration file stops andwaits to be handled manually.

l Restarting the routerAfter the configuration file is downloaded successfully, the router is restarted according tothe setting of Option 146. If no Option 146 is configured, the router is restarted immediatelyafter the configuration file is downloaded.

Option Parameters

Table 6-1 Option parameters

Option Description

Option 6 IP address of a DNS server.

Option 15 DNS domain name.

Option 43 l sub-option 1: ACS URL in the following format:URL=URL_INFO;For example:URL=http://192.168.1.40:80/acs;

l sub-option 2: ACS user name and password, in the following format:username=USERNAME;password=PASSWORD;

Option 66 TFTP server name.

Option 67 Configuration file information.

Option 141 FTP user name.

Option 142 FTP password.

Option 143 IP address of an FTP server.

Option 145 Non-configuration file information, such as system software information,version information and patch file information, in the following format:vrpfile=VRPFILENAME;vrpver=VRPVERSION;patchfile=PATCHFILENAME;For example:vrpfile=auto_V200R001C00.cc;vrpver=V200R001C00;patchfile=auto_V200R001C00.pat;NOTE

Version information must be contained in the system software.



91

Option Description

Option 146 Operation information in the following format:opervalue=OPERATEVALUE;delaytime=DELAYTIME;l opervalue=0: indicates that no file will be deleted from the file system

when the space is insufficient. opervalue=1: indicates that versionfiles will be deleted from the file system when the space is insufficient.By default, no file will be deleted from the file system when the spaceis insufficient.

l delaytime: specifies the delay in restarting a device after aconfiguration file is downloaded to the device, in seconds. By default,the delay is 0 seconds.

NOTEThe maximum delay in restarting a device is 1 day. If the configured delay is longerthan 1 day, the actual delay is 1 day.

Option 147 Authentication information. Option 147 is optional. If Option 147 isrequired, it must be configured as AutoConfig.

Option 150 IP address of a TFTP server.

NOTE

You can use the following methods to configure an FTP or TFTP server:

l To configure a TFTP server, configure Options 6, 15, and 66 and obtain a TFTP server address froma DNS server.

l To configure a TFTP server, configure Option 150 and obtain the TFTP server address.

l To configure an FTP server, configure Options 141, 142, and 143 and obtain the TFTP user name,FTP password, and FTP server address.

6.3 Deploying Unconfigured RoutersThis section describes how to deploy unconfigured Routers.

6.3.1 Establishing the Configuration TaskBefore deploying routers, familiarize yourself with the applicable environment, complete thepre-configuration tasks, and obtain the data required for the configuration. This will help youcomplete the configuration task quickly and accurately.

Applicable EnvironmentAs shown in Figure 6-2, the physical link between the router and DHCP relay agent functionsproperly, and there are reachable routes between the DHCP relay agent and servers. Theintermediate file, version file, and configuration file are stored on the FTP/TFTP server. Afterthe DHCP server and FTP/TFTP server are configured, routers can be configured by using Auto-Config.



92

NOTE

Only Layer 3 Ethernet interfaces on the main control board support Auto-Config.

If the received DHCP Reply packet contains Option 43, the auto-configuration server (ACS) is used fordeployment.

Figure 6-2 Auto-Config application

CPE

GE0/0/1LAN

DHCP ServerDHCP Relay

FTP/TFTP Server

DNS Server

IP network

ACS Server


Before deploying routers, complete the following task:

l Ensuring that physical links between routers and the DHCP server and FTP/TFTP serverwork properly

Data Preparation

To deploy routers, you need the following data.

No.

Data

1 Information about the interface that connects an AR1200-S to the DHCP server

2 Address pool of the DHCP server

3 IP address range and mask of the DHCP server

4 Egress gateway of routers

5 Option parameters of the DHCP server



93

No.

Data

6 Authentication information, authorization mode, and working directory of the FTP/TFTP server (optional)

7 IP address of the FTP/TFTP server

8 MAC addresses or ESNs of routers, version files (optional), patch files (optional), andconfiguration files

6.3.2 Configuring the DHCP ServerRouters obtain IP addresses and option parameters after the DHCP server is configured.

ContextAfter a new AR1200-S or an unconfigured AR1200-S is powered on, the Auto-Config processstarts automatically.

To stop the Auto-Config process, use either of the following methods:l Run the undo autoconfig enable command in the system view. You can run the display

autoconfig-status command to check whether the Auto-Config process stops.l Run the save command in the system view to save the temporary configuration file, restart

the AR1200-S, and then perform configurations.

When you connect to the console port of an AR1200-S that does not have a startup configurationfile, the system displays "Warning: Auto-Config is working. Do you want to stop Auto-Config?[y/n]:"l To continue Auto-Config, enter n and press Enter.l To stop Auto-Config, choose y and press Enter.

CAUTIONIf you choose n but still perform configurations through the console port, the DHCP,routing, DNS, and VTY configurations will be lost.

Before powering on the Auto-Config-enabled routers, configure the DHCP server and file server;otherwise, the routers cannot obtain configuration files.

NOTE

l The DHCP server must be configured with option parameters by referring to 6.2 Auto-Config FeaturesSupported by the AR1200-S.

l Here, an AR is used to describe how to configure the DHCP server based on a global address pool.When the AR functions as a DHCP server, configure the DHCP server by referring to Configuring aDHCP Server Based on a Global Addrss Poolor Configuring a DHCP Server Based on an InterfaceAddress Pool.

l If routers and the DHCP server are on different network segments, configure a DHCP relay agent byreferring to Configuring a DHCP Relay Agent.



94

Procedure



Step 2 Run:dhcp enable

DHCP is enabled.



Step 4 Run:ip address ip address { mask | mask-length }

The IP address is configured for the interface.

Step 5 Run:dhcp select global

The interface is configured to use a global address pool. Users going online through this interfacecan obtain IP addresses from the global address pool.

Step 6 Run:quit

Return to the system view.

Step 7 Run:ip pool ip-pool-name

The global address pool view is displayed.

By default, no global address pool exists on an AR1200-S.

Step 8 Run:network ip-address [ mask { mask | mask-length } ]

The range of IP addresses that can be dynamically allocated is configured.

Step 9 Run:gateway-list ip-address &<1-8>

The IP address of the egress gateway is configured for the DHCP client.

Step 10 Run:option code { ascii ascii-string | hex hex-string | ip-address ip-address &<1-8> }

Option parameters of the DHCP server are configured.

If Option 67 is not configured, the process of obtaining the intermediate file is started.



95

NOTE

Pay attention to the following points when configuring option parameters:

l When the configuration file is obtained using TFTP, the DHCP server must support Option 150 orsupport Option 6, Option 15, and Option 66.

l When the configuration file is obtained using FTP, the DHCP server must support Option 141, Option142, and Option 143.

l When option parameters of TFTP and FTP are both set on the DHCP server, the FTP mode is preferred.

----End

6.3.3 Configuring the FTP/TFTP ServerRouters obtain configuration files after the FTP/TFTP server is configured.

ContextNOTE

l On an FTP server, the IP address must be the same as that contained in Option 143 configured on theDHCP server. On a TFTP server, the IP address must be the same as that contained in Option 150 orOption 6, 15, and 66 configured on the DHCP server.

Procedure



Step 2 Run:ftp server enable

The FTP server is enabled.

NOTE

After the DHCP client obtains configuration files from the FTP server, run the undo ftp server commandto disable the FTP server immediately to ensure FTP server security.

Step 3 (Optional) Configure the authentication information, authorization mode, and working directoryfor FTP users.

1. For TACACS authentication users:l Run:

set default ftp-directory directoryThe default FTP working directory is configured.

2. For AAA authentication users:l Run:

aaaThe AAA view is displayed.

l Run:local-user user-name password { simple | cipher } passwordThe local user name and password are configured.

l Run:



96

local-user user-name service-type ftp

The service type is set to FTP.

l Run:local-user user-name ftp-directory directory

The directory is configured for FTP users.



Step 5 Run:ip address ip address { mask | mask-length }

The IP address of the FTP server is configured.

NOTE

The IP address of the FTP server must be the same as that contained in Option 143 configured on the DHCPserver.

Step 6 (Optional) Create and configure an intermediate file.

NOTE

The configuration file is obtained using Option 67 in the Auto-Config process. If Option 67 is notconfigured, the process of obtaining the intermediate file is started.

The intermediate file is configured based on the MAC addresses or ESNs of routers, versionfiles, patch files, and configuration files. For details about the format of the intermediate file,see 6.2 Auto-Config Features Supported by the AR1200-S.

1. Create a .txt file and name it arnet.ini.2. Configure the intermediate file. For example, if the MAC address of an AR3200 is

0018-82C5-AA89 and the ESN is 9300070123456789, the version file name isauto_V200R001C01.cc, the version number is V200R001C01, the patch file name isauto_V200R001C01.pat, the configuration file name is auto_V200R001C01.cfg,and thecontents of the intermediate file arnet.ini are as follows:

MAC=0018-82C5-AA89;ESN=9300070123456789;vrpfile=auto_V200R001C01.cc;vrpver=V200R001C01;patchfile=auto_V200R001C01.pat;cfgfile=auto_V200R001C01.cfg;

Step 7 Save the intermediate file, version file, patch file, and configuration file to the working directoryon the FTP server.

----End

6.3.4 Checking the ConfigurationYou can view the configuration in different phases of the Auto-Config process to check whetherAuto-Config runs properly.

Prerequisite

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



97

Procedure

Step 1 Five minutes after routers are powered on, check address allocation on the DHCP server to checkwhether the routers are connected to the DHCP server.

NOTE

If the routers are connected to the DHCP server, log in to the routers using Telnet but do not configure therouters.

Step 2 Five minutes after the routers obtain IP addresses, check the log about file downloading fromthe FTP/TFTP server, or log in to the routers to check whether correct version files, patch files,and configuration files have been downloaded and check the running status of Auto-Config byusing the display autoconfig-status command.

NOTE

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

Step 3 After correct files are downloaded to the routers, the routers are restarted according to the settingof Option 146. You can run the display autoconfig activating-config { delay | remanent-time } command to check whether the configuration takes effect.

----End

6.4 Configuration ExamplesThis section provides examples for configuring Auto-Config, including networkingrequirements, configuration notes, and configuration roadmap.

6.4.1 Example for Configuring the Auto-Config FunctionThis section describes how to configure Auto-Config so that users can automatically load theconfiguration file, version file, and patch file.

Networking RequirementsWhen a new router or a non-configured router accesses the network, the configuration file,version file, and patch file are required to be configured. To reduce the maintenance cost, therouter uses the Auto-Config function to automatically load the configuration file, version file,and patch file. The router then can be managed remotely.

As shown in Figure 6-3, the AR1200-S connects to the DHCP server through GE0/0/1 andsupports the Auto-Config function. The AR1200-S can automatically load the configuration file,version file, and patch file stored on the FTP server after the FTP server and DHCP server areconfigured.



98

Figure 6-3 Networking diagram for configuring the Auto-Config function

DHCP Server FTP Server

Eth1/0/0192.168.1.6/24

Eth1/0/0192.168.2.6/24

HostB

HostA

HostC

RouterGE0/0/1 Eth1/0/0


1. Configure the DHCP server so that a router can obtain IP addresses and option parameters.2. Configure an intermediate file.3. Configure the IP address of the FTP server.4. Save the intermediate file, version file, patch file, and configuration file to the working

directory on the FTP server.

NOTEThis example describes how to configure the Auto-Config function on an AR1200-S. Option 67 is specifiedto carry the configuration file when the DHCP server is configured.


l GE0/0/1 used to connect the AR1200-S to the DHCP serverl DHCP server information:

– Downlink interface Eth1/0/0 connected to the router– IP address: 192.168.2.6/24– Address pool: 192.168.2.0/24– Option 67 (configuration file): auto_V200R002C00B002.cfg– Option 141 (FTP user name): user– Option 142 (FTP password): huawei– Option 143 (FTP server address): 192.168.1.6– Option 145 (non-configuration file):

vrpfile=auto_V200R002C00B001.cc;vrpver=V200R002C00B001;patchfile=auto_V200R002C00B002.pat;

l Egress gateway's IP address 192.168.2.6 and MAC address 0018-82C5-AA89l FTP server's IP address: 192.168.1.6/24



99

Procedure

Step 1 Configure the DHCP server.<DHCP Server> system-view[DHCP Server] dhcp enable[DHCP Server] interface ethernet 1/0/0[DHCP Server-Ethernet1/0/0] ip address 192.168.2.6 255.255.255.0[DHCP Server-Ethernet1/0/0] dhcp select global[DHCP Server-Ethernet1/0/0] quit[DHCP Server] ip pool auto-config[DHCP Server] network 192.168.2.0 mask 255.255.255.0[DHCP Server] gateway-list 192.168.2.6[DHCP Server] option 67 ascii auto_V200R002C00B002.cfg[DHCP Server] option 141 ascii user[DHCP Server] option 142 ascii huawei[DHCP Server] option 143 ip-address 192.168.1.6[DHCP Server] option 145 ascii vrpfile=auto_V200R002C00B001.cc;vrpver=V200R002C00B001;patchfile=auto_V200R002C00B002.pat;

Step 2 Configure the FTP server.

Set the IP address of the FTP server to 192.168.1.6, configure the authorization mode andworking directory for FTP users, and save the version file, patch file, and configuration file tothe working directory on the FTP server.


Five minutes after the router is powered on, run the display ip pool name auto-config commandon the DHCP server to check address allocation of the auto-config address pool.

<DHCP Server> display ip pool name auto-config Pool-name : auto-config Pool-No : 0 Lease : 1 Days 0 Hours 0 Minutes Domain-name : - Option-code : 67 Option-subcode : -- Option-type : ascii Option-value : auto_V200R002C00B002.cfg Option-code : 141 Option-subcode : -- Option-type : ascii Option-value : user Option-code : 142 Option-subcode : -- Option-type : ascii Option-value : huawei Option-code : 143 Option-subcode : -- Option-type : ascii Option-value : 192.168.1.6 Option-code : 145 Option-subcode : -- Option-type : ascii Option-value : vrpfile=auto_V200R002C00B001.cc;vrpver=V200R002C00B001;patchfile=auto_V200R002C00B002.pat; DNS-server0 : - NBNS-server0 : - Netbios-type : - Position : Local Status : Unlocked Gateway-0 : 192.168.2.6 Mask : 255.255.255.0 VPN instance : -- ----------------------------------------------------------------------------- Start End Total Used Idle(Expired) Conflict Disable -----------------------------------------------------------------------------



100

192.168.2.1 192.168.2.254 253 1 252 0 0 0 -----------------------------------------------------------------------------

Five minutes after the router obtains the IP address, run the display autoconfig-status commandto check whether correct version files, patch files, and configuration files have been downloadedand check the running status of Auto-Config.

<AR1200-S> display autoconfig-statusRunning: Yes

Can deploy configurations with a USB disk: No

Stop : No Reason : --

Suspend: Yes Reason : The unknown reason cause getting fil

The status of DHCP phase: Operation result: Successful Failed reason : --

The status of setting ACS phase: URL : -- User name : -- Password : -- Operation result: -- Failed reason : --

The status of getting middle file phase: File name : -- Operation result: --Failed reason : --

The status of getting system software phase:File name : auto_V200R002C00B001.ccOperation result: SuspendFailed reason : The unknown reason cause getting file from file server failed

The status of getting patch file phase:File name : auto_V200R002C00B002.patOperation result: --Failed reason : --

The status of getting configuration file phase:File name : auto_V200R002C00B002.cfgOperation result: --Failed reason : --

The status of activating configuration phase:Remained time : --Operation result: --Failed reason : --

----End

Configuration FilesConfiguration file of the DHCP server

# dhcp enable # ip pool auto-config gateway-list 192.168.2.6 network 192.168.2.0 mask 255.255.255.0



101

option 67 ascii auto_V200R002C00B002.cfg option 141 ascii user option 142 ascii huawei option 143 ip-address 192.168.1.6 option 145 ascii vrpfile=auto_V200R002C00B001.cc;vrpver=V200R002C00B001;patchfile=auto_V200R002C00B002.pat; # interface Ethernet1/0/0 ip address 192.168.2.6 255.255.255.0 dhcp select global

Configuration file of the FTP server

# ftp server enable # aaa local-user user1 password simple huawei local-user user1 ftp-directory flash:/ local-user user1 service-type ftp # interface Ethernet1/0/0 ip address 192.168.1.6 255.255.255.0 #



102

configuration guide - device management(v200r001c01_03).pdf

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

device management feature

additional information

command line

italic command arguments

low level of risk