01-04 Log Management

7/28/2019 01-04 Log Management

1/10

iManager N2000 DMS Datacomm Network Management System

Administrator Guide Contents

Issue 02 (2007-10-15) Huawei Technologies Proprietary i

Contents

4 Log Management........................................................................................................................4-1

4.1 Log Types......................................................................................................................................................4-2

4.1.1 Dynamic Debugging Information .................................................................... ....................................4-2

4.1.2 System Logs.........................................................................................................................................4-3

4.2 Managing Operation Logs of the DMS.........................................................................................................4-5

4.2.1 Setting the Automatic Dump Policy of User Logs...............................................................................4-5

4.2.2 Dumping User Logs Manually.............................................................................................................4-6


2/10

Figures

iManager N2000 DMS Datacomm Network

Management System

Administrator Guide

ii Huawei Technologies Proprietary Issue 02 (2007-10-15)

Figures

Figure 4-1 Dump Setting....................................................................................................................................4-6

Figure 4-2 Dumping a user log...........................................................................................................................4-7


3/10


Administrator Guide Tables

Issue 02 (2007-10-15) Huawei Technologies Proprietary iii

Tables

Table 4-1 Debugging information.......................................................................................................................4-3

Table 4-2 System log (1).....................................................................................................................................4-4

Table 4-3 System log (2).....................................................................................................................................4-4


4/10


Administrator Guide 4 Log Management

Issue 02 (2007-10-15) Huawei Technologies Proprietary 4-1

4 Log ManagementAbout This Chapter

The following table lists the contents of this chapter.

Section Describes

4.1 Log Types This section describes the log types, storage path, formatand contents.

4.2 Managing Operation Logsof the DMS

This section describes how to manage logs.


5/10

4 Log Management


Administrator Guide

4-2 Huawei Technologies Proprietary Issue 02 (2007-10-15)

4.1 Log Types

The DMS has three types of logs as follows:

z Dynamic debugging informationz System logsz Operation logsThe operation logs record user operations on the DMS, such as:

z Logging in to the systemz Adding a devicez Deleting device dataYou can perform the operations of querying and dumping logs on the client.

This guide does not detail the user operation logs. For details, see the iManager N2000 DMS

Datacomm Network Management System Operation Guide - Volume I.

4.1.1 Dynamic Debugging Information

Function

The log files of the dynamic debug information record the detailed process of an applicationcall functions. This can help the developer locate the code fault.

Pathz Path of saving the file

The log files of dynamic debug information are saved in $N2000ROOT/server/debug.

z Mode of naming the fileThe name format of the file is debugged program name + number + .dbg.

The "number" ranges from 1 to 5, that is, each program has up to five automaticdebugging files. The five files are used circularly, and the maximum size of each file is 1MB by default. When the fifth file reaches the maximum size, it overwrites the first fileautomatically.

Format

The debugging information is as follows:

2006/03/21-20:07:28 TRACE-INFO EmfGnlDev CEmfQvCtrTask : Find the device which

need to ping!2006/03/21-20:07:28 TRACE-INFO EmfGnlDev CEmfQvCtrTask : Enter the function:

SendDevIDMsg().

Description

Each dynamic debugging log consists of the header and message body.

The header consists of four parts, the time, alarm level ID, process ID, and module ID in aprocess.

The header and the other parts of the message are separated by colons (:). For details, seeTable 4-1.


6/10




Table 4-1Debugging informationParameter Description

Time Identifies the time when debugging information is recorded. The

format is YYYY/MM/DD-HH:MM:SS.

Alarm level ID Grouped into three categories:

TRACE-INFOinformation level debugging information

TRACE-WARN: warning level debugging information

TRACE-ERR: error level debugging information

Process ID Specifies the file name. You can view the file name of the systemprocess with the tool N2000 System Monitor.

Module ID in aprocess

Specifies the module ID in the process, such as GLOABL andCEmfTopoQueryTask.

Message body Specifies the customized debugging items.

4.1.2 System Logs

Function

The system logs record the information during a program runs, such as loading data duringstartup of a program.

Path

The system logs are saved in $N2000ROOT/server/conf/log and $N2000ROOT/server/log.

The logs in these directories record different information.

z $N2000ROOT/server/conf/logThe logs in this path record the message processing and thread status of a process. A logis created when the DMS is started.

The name rule for the log file is the process name_ProcID_YYYYMMDD_HHMMSS.log. For example, the platform log name of thesecurity process is CommonSecurityLog_p52_20060608_095044.log.

Each process can have up to 10 log files, and the maximum size of each file is 5 MB bydefault. When the tenth file reaches the maximum size, it overwrites the first fileautomatically.

z $N2000ROOT/server/logThe logs that are output by the DMS server applications are saved in this folder.

The name rule for the log file is the process name + sequence number. log. For example,the log file name of the fault process is the EmfFaultDm1.log and EmfFaultDm2.log.

The maximum number of these log files is five by default. The five files are usedcircularly, and the maximum size of each file is 1 MB by default. When the fifth filereaches the maximum size, it overwrites the first file automatically.


7/10

4 Log Management


Administrator Guide


Formatz $N2000ROOT/server/conf/log

The format for the logs in this path is as follows:

14:07:28.351811.T1:iMapSSDBFuncs::getLogConnection pointer=(008ED950) OK

z $N2000ROOT/server/log

The format for the logs in this path is as follows:

2006/03/01-07:23:47 LOG-INFO EmfFaultDm GLOABL : Insert first map success

Descriptionz $N2000ROOT/server/conf/log

Log information consists of the header and message body.

The header contains the time and thread ID. The header and message body are separatedby the colon (:). For details, see Table 4-2.

Table 4-2System log (1)Parameter Description

Time Format: HH:MM:SS:s

s range: from 0 to 999999

Thread ID Format: T + ID

ID range: form 1 to 65535

Message body Customized system items

z $N2000ROOT/server/logLog information consists of the header and message body.

The header contains the time, log ID, process ID, and module ID in a process. Theheader and the message body are separated by the colon (:). For details, see Table 4-3.

Table 4-3System log (2)Parameter Description

Time Used to identify the time when system information is recorded.

Format: YYYY/MM/DD-HH:MM:SS.

Log ID At present, only the "LOG-INFO" exists. LOG-INFO means logoutput.

Process ID You can view the file name of the system process with the tool N2000System Monitor.

Module ID in aprocess

Specifies the module ID in the process, such as GLOABL andCEmfTopoQueryTask.

Message body Specifies the customized system items.


8/10




4.2 Managing Operation Logs of the DMS

4.2.1 Setting the Automatic Dump Policy of User Logs

Description

This operation enables you to set the automatic dump policy for log data, so as to regularlydump log data to a file.

The automatic dump policy includes the following:

z Dumping when overflowed occurs: You can set the maximum number of logs dumped inthe log database. When the number is exceeded, the system dumps the overflowed logs.

z Dumping periodically: You can set the dump period of the log database. The systemdumps logs periodically.

The dump path is $N2000ROOT/server/dump by default.The dump files support cyclic overwriting. That is, when the amount of files exceeds 1000,the system overwrites the previously dumped files to release the disk space.

Precautionz When the log database is full, the system dumps the logs according to the overflow dump

policy.

z The logs are saved to a specified dump path and deleted from the database.z After the logs are dumped, you cannot query them in the Log Browser window.

Procedure

Step 1 In the NMS, choose System > Dump Settings.Step 2 Select the Log Dump tab in the Dump Settings dialog box that is displayed, as shown in

Figure 4-1.


9/10

4 Log Management


Administrator Guide


Figure 4-1Dump Setting

Step 3 Set the percentage ofMax Capacity(Item) and Dump Percent in the Dumping WhenOverflowed area frame.

Step 4 Choose the check box before Enable Dumping Periodically and set Dump Interval(Days)and End Time(Days Before).

Step 5 In the DumpingSetting area frame, set the log dump path.Step 6 ClickOK.

----End

4.2.2 Dumping User Logs Manually

Description

Automatically dump the user operation log.

The default dump path is $N2000ROOT/server/dump.

Precautionz The dumped log recordings are saved in the specified dump path and deleted from the

database.

z The dumped operation logs cannot be viewed in the Browse user log window.

Procedure

Step 1 In the NMS, choose System > Dump Manually > Dump User Log.Step 2 Set the end time of dumping logs in the Dump User Log dialog box as shown in Figure 4-2.


10/10




Figure 4-2Dumping a user log

ClickQuery and query how many records exist in this period of time. The amount is displayed inRecords(Pieces).

Step 3 ClickOK.----End

Documents

01-04 Log Management