configuration guide - device management(v200r002c00_02)

Huawei AR2200 Series Enterprise RoutersV200R002C00

Configuration Guide - DeviceManagement

Issue 02Date 2012-03-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. 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.comEmail: [email protected]

Issue 02 (2012-03-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

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 theAR2200.This document describes how to configure the device management feature.This document is intended for:l Data configuration engineersl Commissioning engineersl Network monitoring engineersl System maintenance engineers

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

Symbol Description

DANGERIndicates a hazard with a high level 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 AR2200 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 DescriptionBoldface 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 by

vertical bars. One item is selected.[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.{ x | y | ... }* Optional items are grouped in braces and separated by

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

& 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 02 (2012-03-30)Based on issue 01 (2011-12-30), the document is updated as follows:The following information is modified:l 5.3.2 Configuring the DHCP Serverl 2.7.1 Example for Outputting Logs to the Log Filel 2.7.2 Example for Outputting Logs to Log Hosts



iii

Changes in Issue 01 (2011-12-30)Initial commercial release.



iv

Contents

About This Document.....................................................................................................................ii1 Displaying the Device Status......................................................................................................1

1.1 Display Commands.............................................................................................................................................21.2 Displaying the AR2200 Status...........................................................................................................................2

1.2.1 Displaying AR2200 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.........................................................................................................................6

2 Information Center Configuration.............................................................................................72.1 Introduction to the Information Center...............................................................................................................82.2 Information Center Supported by the AR2200...................................................................................................82.3 Enabling Log Output........................................................................................................................................13

2.3.1 Establishing the Configuration Task.......................................................................................................132.3.2 Enabling the Information Center.............................................................................................................142.3.3 (Optional) Naming an Information Channel...........................................................................................152.3.4 (Optional) Configuring the Function of Filtering Logs by IDs...............................................................152.3.5 (Optional) Configuring the Function of Generating a Data Dictionary..................................................152.3.6 Outputting Logs to the Log Buffer..........................................................................................................162.3.7 Outputting Logs to a Log File.................................................................................................................172.3.8 Outputting Logs to the Console...............................................................................................................172.3.9 Outputting Logs to the Terminal.............................................................................................................182.3.10 Outputting Logs to the Log Host...........................................................................................................192.3.11 Checking the Configuration...................................................................................................................20

2.4 Enabling Alarm Output....................................................................................................................................222.4.1 Establishing the Configuration Task.......................................................................................................22

Huawei AR2200 Series Enterprise RoutersConfiguration Guide - Device Management Contents


v

2.4.2 Enabling the Information Center.............................................................................................................232.4.3 (Optional) Naming an Information Channel...........................................................................................232.4.4 Outputting Alarms to the Alarm Buffer..................................................................................................232.4.5 Outputting Alarms to the Log File..........................................................................................................242.4.6 Outputting Alarms to the Console...........................................................................................................252.4.7 Outputting Alarms to the Terminal.........................................................................................................262.4.8 Outputting Alarms to the SNMP Agent..................................................................................................272.4.9 Checking the Configuration.....................................................................................................................28

2.5 Enabling the Output of Debugging Information...............................................................................................292.5.1 Establishing the Configuration Task.......................................................................................................302.5.2 Enabling the Information Center.............................................................................................................302.5.3 (Optional) Naming an Information Channel...........................................................................................312.5.4 Outputting Debugging Information to the Log File................................................................................312.5.5 Outputting Debugging Information to the Console.................................................................................322.5.6 Outputting Debugging Information to the Terminal...............................................................................332.5.7 Outputting Debugging Information to the Log Host...............................................................................342.5.8 Checking the Configuration.....................................................................................................................34

2.6 Maintaining Information Center.......................................................................................................................352.7 Information Center Configuration Examples...................................................................................................36

2.7.1 Example for Outputting Logs to the Log File.........................................................................................362.7.2 Example for Outputting Logs to Log Hosts............................................................................................382.7.3 Example for Configuring Binary Logs to be Sent to the Log Host.........................................................422.7.4 Example for Outputting Alarms to the SNMP Agent..............................................................................442.7.5 Example for Outputting the Debugging Information to the Console......................................................46

3 Mirroring Configuration............................................................................................................483.1 Introduction to Mirroring..................................................................................................................................493.2 Mirroring Features Supported by the AR2200.................................................................................................493.3 Configuring Local Port Mirroring....................................................................................................................52

3.3.1 Establishing the Configuration Task.......................................................................................................523.3.2 Configuring a Local Observing Interface................................................................................................533.3.3 Configuring a Local Mirrored Interface..................................................................................................533.3.4 Checking the Configuration.....................................................................................................................54

3.4 Configuring Local Flow Mirroring...................................................................................................................553.4.1 Establishing the Configuration Task.......................................................................................................553.4.2 Configuring a Local Observing Interface................................................................................................553.4.3 Configuring Complex Traffic Classification...........................................................................................563.4.4 Creating a Local Traffic Behavior...........................................................................................................563.4.5 Configuring a Traffic Policy....................................................................................................................563.4.6 Checking the Configuration.....................................................................................................................57

3.5 Configuring Remote Port Mirroring.................................................................................................................583.5.1 Establishing the Configuration Task.......................................................................................................583.5.2 Configuring the Observing Server...........................................................................................................59



vi

3.5.3 Configuring a Mirrored Interface............................................................................................................593.5.4 Checking the Configuration.....................................................................................................................60

3.6 Configuring Remote Flow Mirroring...............................................................................................................613.6.1 Establishing the Configuration Task.......................................................................................................613.6.2 Configuring the Observing Server...........................................................................................................623.6.3 Configuring Complex Traffic Classification...........................................................................................623.6.4 Configuring the Traffic Behavior............................................................................................................633.6.5 Configuring a Traffic Policy....................................................................................................................633.6.6 Checking the Configuration.....................................................................................................................64

3.7 Configuring Packet Capture Using Mirroring..................................................................................................643.8 Configuration Examples...................................................................................................................................67

3.8.1 Example for Configuring Local Port Mirroring......................................................................................673.8.2 Example for Configuring Local Flow Mirroring.....................................................................................713.8.3 Example for Configuring Remote Port Mirroring...................................................................................733.8.4 Example for Configuring Remote Flow Mirroring.................................................................................77

4 Hardware Management..............................................................................................................824.1 Introduction to Hardware Management............................................................................................................834.2 Hardware Management Supported by the AR2200..........................................................................................834.3 Powering On and Off the Board.......................................................................................................................83

4.3.1 Establishing the Configuration Task.......................................................................................................834.3.2 Powering Off a Board..............................................................................................................................844.3.3 Powering On a Board..............................................................................................................................844.3.4 Checking the Configuration.....................................................................................................................84

4.4 Backing Up Electronic Labels..........................................................................................................................854.4.1 Establishing the Configuration Task.......................................................................................................854.4.2 Backing Up Electronic Labels.................................................................................................................854.4.3 Checking the Configuration.....................................................................................................................86

4.5 Setting Fan Speed.............................................................................................................................................864.5.1 Establishing the Configuration Task.......................................................................................................864.5.2 Setting Fan Speed....................................................................................................................................874.5.3 Checking the Configuration.....................................................................................................................87

4.6 Resetting the LPU.............................................................................................................................................884.6.1 Establishing the Configuration Task.......................................................................................................884.6.2 Resetting the LPU....................................................................................................................................884.6.3 Checking the Configuration.....................................................................................................................89

5 Auto-Config..................................................................................................................................905.1 Auto-Config Overview.....................................................................................................................................915.2 Auto-Config Features Supported by the AR2200............................................................................................915.3 Deploying Unconfigured Routers ....................................................................................................................96

5.3.1 Establishing the Configuration Task.......................................................................................................965.3.2 Configuring the DHCP Server.................................................................................................................985.3.3 Configuring the FTP/TFTP Server........................................................................................................100



vii

5.3.4 Checking the Configuration...................................................................................................................1015.4 Configuration Examples.................................................................................................................................102

5.4.1 Example for Configuring the Auto-Config Function............................................................................1026 Fault Management.....................................................................................................................107

6.1 Introduction to Fault Management.................................................................................................................1086.2 Fault Management Features Supported by the AR2200.................................................................................1086.3 Configuring Alarm Management....................................................................................................................108

6.3.1 Establishing the Configuration Task.....................................................................................................1086.3.2 Setting the Alarm Severity Level..........................................................................................................1096.3.3 Configuring Delaying Alarm Reporting................................................................................................1096.3.4 Configuring Correlated Alarm Suppression..........................................................................................1106.3.5 Checking the Configuration...................................................................................................................111

6.4 Configuring Event Management....................................................................................................................1126.4.1 Establishing the Configuration Task.....................................................................................................1126.4.2 Configuring Delayed Event Reporting..................................................................................................1136.4.3 Checking the Configuration...................................................................................................................113

6.5 Maintenance....................................................................................................................................................1146.5.1 Clearing Alarm Messages......................................................................................................................1156.5.2 Clearing Event Messages.......................................................................................................................115

6.6 Configuration Examples.................................................................................................................................1166.6.1 Example for Configuring Alarm Management......................................................................................116



viii

1 Displaying the Device StatusAbout 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 AR2200 StatusThis section describes how to use the display commands to show the AR2200 version, CPUusage, and memory usage.

Huawei AR2200 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 AR2200 in order to maintain and troubleshooting networks.Table 1-1 lists the display commands in common use. For details, see the Huawei AR2200Series Enterprise Routers - Command Reference.

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

Table 1-1 Common display commandsCommand Descriptiondisplay current-configuration Displays the parameters that take effect currently on the

AR2200.display device Displays information about the AR2200.display version Displays the version and boards information of the

AR2200.display this Displays valid configurations in the current view.display diagnostic-information Collects information about the AR2200 when a fault

cannot 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 AR2200 StatusThis section describes how to use the display commands to show the AR2200 version, CPUusage, and memory usage.

1.2.1 Displaying AR2200 InformationUse the display device command to view information about AR2200 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 AR2200.

Procedurel Run:

display version [ slot slot-id ]

Version information is displayed.This command can be used in any view.

----End

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

ProcedureStep 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.This command can be used in any view.

----End

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

Procedurel Run:

display fan

Fan status is displayed.This command can be used in any view.

l Run:display temperature slot fan

Fan module temperature is displayed.----End

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


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.



4

This command can be used in any view. If slot slot-id is specified, the memory usage of the LPU in this slot is displayed. If slot slot-id is not specified, the memory usage of the active main control board is

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


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.



5

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

display elabel backplane

Electronic labels of the backplane are displayed.----End

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



6

2 Information Center ConfigurationAbout 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 AR2200The 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 AR2200 Series Enterprise RoutersConfiguration Guide - Device Management 2 Information Center Configuration


7

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 AR2200The information center outputs logs, alarms, and debugging messages at eight severity levelsthrough 10 information channels.

Information ClassificationThe information center receives and processes information of the following types:l Logsl Debugging informationl Alarms

Severity Levels of InformationInformation 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 informationThreshold Severity Level Description0 Emergencies A fatal fault, such as a program exception or incorrect

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



8

Threshold Severity Level Description4 Warning An abnormal situation, such as the user disabling the

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



9

Figure 2-1 Functions of the information channelInformation

channelConsole

Remote terminal

Loghost

Trap bufferLog buffer

SNMP agent

Logs

Traps

Debugs

Outputdirection

Direction of logsDirection of alarmsDirection of debugging

information Logfile

Console

SNMP agent

Monitor

Loghost

LogbufferTrapbuffer

01

234

5channel6

channel7channel8channel9

6

78

9

Information Channels and Output DirectionsThe 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 directionsChannelNumber

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.



10

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 to

output to different directions.7 Unspecified Unspecified Reserved, this channel can be configured to

output to different directions.8 Unspecified Unspecified Reserved, this channel can be configured to

output to different directions.9 Channel9 Log file Outputs information to log files that can

receive logs, traps, and debugginginformation. Information is saved to the SDcard or the USB 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 logsTIMESTAMP HOSTNAME %%ddAAA/B/CCC(l)[DDD]: YYYY

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



11

Table 2-3 Description of each field in a log messageField Indication DescriptionTIMESTAMP Time to send out the

informationAvailable 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 a

Huawei device.dd Version number Identifies the version of the log format.AAA Module name Indicates the name of the module that outputs

information to the information center.B Log level Indicates the severity level of a log.CCC Brief description Describes the information type.(t) Information type Indicates the user log identifier.[e] Information counter Indicates the log sequence number.DDD Log ID A maximum of 1024 logs can be stored in the log

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

Figure 2-3 shows the format of the output alarms.

Figure 2-3 Format of the output alarmsTimeStamp HostName ModuleName/Severity/Brief:Description



12

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

Table 2-4 Description of each field of in an alarm messageField Indication DescriptionTimeStamp Time to send out the

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



13

Applicable EnvironmentThe 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 TasksBefore configuring the log output, complete the following tasks:l Connecting the router to the PC properlyl Ensuring that the route between the router and the log host is reachablel Configuring an VPN instance

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

No. Data1 l Channel number

l Channel name2 Module name3 Address of the log host4 Severity level of the log5 (Optional) Size of the log buffer6 (Optional) VPN instance name

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

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


system-view

The system view is displayed.Step 2 Run:

info-center enable

The information center is enabled.



14

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.


system-view


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


info-center filter-id { id | bymodule-alias modname alias } * &

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.



15

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.


system-view


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.



16

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 system selects a storage medium in descending order of priority: sd0, sd1, usb0, and usb1. The defaultlog storage medium is sd0. If sd0 is unavailable, the default log storage medium is sd1. If none of sd0, sd1,usb0, and usb1 is unavailable, the log files cannot be saved. The log storage path is in the format of storagemedium name:/logfile, for example, usb0:/logfile.

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



17

ProcedureStep 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



Logs are added to 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 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.


1. Run:system-view



Logs are added to the information channel.Logs can be output only after the information center is enabled.



18

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

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

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

quit


1. Run:system-view

The system view is displayed.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.


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 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 ] } | { vpn-instance vpn-instance-name | 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



19

2.3.11 Checking the ConfigurationChecking the Configuration of Information Center

PrerequisitesThe 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 | bymodule-alias modname alias } 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. 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



20

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

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. 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. display info-center filter-id 3221442627ID : 3221442627 Module : HA Alias : DISCARDINBATCH Content : The message was discarded because module batch doesn't begin. (SourceModuleId=[ULONG], SourceModuleSubId=[ULONG], DestinationModuleId=[ULONG], DestinationModuleSubId=[ULONG]) Filtered Number : 0

Run the display info-center filter-id command to check whether IDs of all logs are added intothe filtering list. display info-center filter-idID : 3221442627 Module : HA Alias : DISCARDINBATCH Content : The message was discarded because module batch doesn't begin.



21

(SourceModuleId=[ULONG], SourceModuleSubId=[ULONG], DestinationModuleId=[ULONG], DestinationModuleSubId=[ULONG]) Filtered Number : 0 ID : 3491254537 Module : BGP Alias : ADD_DELETED_ROUTE Content : Add the route [STRING] that have other flags besides deleted flag [USHORT] Filtered Number : 0

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.


l Channel name2 Module name3 Severity level of alarms4 (Optional) Size of an alarm buffer5 IP address of Network Management System



22


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


system-view


info-center enable

The information center is enabled.By default, the information center is enabled.----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:



23

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 } * ]

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.


ProcedureStep 1 Send logs to the channel.

1. Run:system-view





24


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.

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



1. Run:system-view



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.



25

For the debugging information, the state is off.Step 2 Configure the channel through which alarms are output to the console.

1. Run:info-center console channel { channel-number | channel-name }

The channel through which alarms are output to the Console is configured.By default, alarms are output to the Console through Channel 0.

2. Run:quit


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.



1. Run:system-view






26

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

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

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


1. Run: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.



1. Run:system-view




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



27

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

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

PrerequisitesThe configurations of the alarm output 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

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

the alarm buffer.----End

ExampleRun the display channel command to show channels. 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



28

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

Run the display info-center command to show the data recorded by info-center. 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

Sent messages = 25, Received messages = 25

Run the display trapbuffer command. If alarms in the alarm buffer are displayed, it means thatthe configuration is successful. 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.



29

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.

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.


l Channel name2 Module name3 Severity level of debugging information4 IP address of a log host


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



30


system-view


info-center enable

The information center is enabled.By default, the information center is enabled.----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.


system-view



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.


ProcedureStep 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 } * ]



31

Debugging information is 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 debugging information is output to the log file.1. Run:


The channel through which debugging information is 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

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.


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

Huawei AR2200 S

configuration guide - device management(v200r002c00_02)

Documents

huawei trademarks

huawei proprietary

huawei industrial basebantian

device management feature

additional information

command line

italic command arguments

low level of risk