Professional Documents
Culture Documents
Contents
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
Issue 02 (2007-10-15)
Figures
Figures
Figure 4-1 Dump Setting ....................................................................................................................................4-6 Figure 4-2 Dumping a user log...........................................................................................................................4-7
ii
Issue 02 (2007-10-15)
Tables
Tables
Table 4-1 Debugging information.......................................................................................................................4-3 Table 4-2 System log (1).....................................................................................................................................4-4 Table 4-3 System log (2).....................................................................................................................................4-4
Issue 02 (2007-10-15)
iii
4 Log Management
4
About This Chapter
The following table lists the contents of this chapter. Section 4.1 Log Types 4.2 Managing Operation Logs of the DMS Describes
Log Management
This section describes the log types, storage path, format and contents. This section describes how to manage logs.
Issue 02 (2007-10-15)
4-1
4 Log Management
The operation logs record user operations on the DMS, such as:
z z z
You 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.
Path
z
Path of saving the file The log files of dynamic debug information are saved in $N2000ROOT/server/debug. Mode of naming the file The 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 automatic debugging files. The five files are used circularly, and the maximum size of each file is 1 MB by default. When the fifth file reaches the maximum size, it overwrites the first file automatically.
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 a process. The header and the other parts of the message are separated by colons (:). For details, see Table 4-1.
4-2
Issue 02 (2007-10-15)
4 Log Management
Table 4-1 Debugging information Parameter Time Alarm level ID Description Identifies the time when debugging information is recorded. The format is YYYY/MM/DD-HH:MM:SS. Grouped into three categories: TRACE-INFOinformation level debugging information TRACE-WARN: warning level debugging information TRACE-ERR: error level debugging information Process ID Module ID in a process Message body Specifies the file name. You can view the file name of the system process with the tool N2000 System Monitor. Specifies the module ID in the process, such as GLOABL and CEmfTopoQueryTask. Specifies the customized debugging items.
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/log The logs in this path record the message processing and thread status of a process. A log is 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 the security 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 by default. When the tenth file reaches the maximum size, it overwrites the first file automatically.
$N2000ROOT/server/log The 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 used circularly, and the maximum size of each file is 1 MB by default. When the fifth file reaches the maximum size, it overwrites the first file automatically.
Issue 02 (2007-10-15)
4-3
4 Log Management
Format
z
Description
z
$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 separated by the colon (:). For details, see Table 4-2.
Table 4-2 System log (1) Parameter Time Thread ID Message body Description Format: HH:MM:SS:s s range: from 0 to 999999 Format: T + ID ID range: form 1 to 65535 Customized system items
$N2000ROOT/server/log Log information consists of the header and message body. The header contains the time, log ID, process ID, and module ID in a process. The header and the message body are separated by the colon (:). For details, see Table 4-3.
Table 4-3 System log (2) Parameter Time Log ID Process ID Module ID in a process Message body Description Used to identify the time when system information is recorded. Format: YYYY/MM/DD-HH:MM:SS. At present, only the "LOG-INFO" exists. LOG-INFO means log output. You can view the file name of the system process with the tool N2000 System Monitor. Specifies the module ID in the process, such as GLOABL and CEmfTopoQueryTask. Specifies the customized system items.
4-4
Issue 02 (2007-10-15)
4 Log Management
Dumping when overflowed occurs: You can set the maximum number of logs dumped in the log database. When the number is exceeded, the system dumps the overflowed logs. Dumping periodically: You can set the dump period of the log database. The system dumps 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.
Precaution
z z z
When the log database is full, the system dumps the logs according to the overflow dump policy. The logs are saved to a specified dump path and deleted from the database. 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.
Issue 02 (2007-10-15)
4-5
4 Log Management
Step 3 Set the percentage of Max Capacity(Item) and Dump Percent in the Dumping When Overflowed 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 Dumping Setting area frame, set the log dump path. Step 6 Click OK. ----End
Precaution
z z
The dumped log recordings are saved in the specified dump path and deleted from the database. 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.
4-6
Issue 02 (2007-10-15)
4 Log Management
Click Query and query how many records exist in this period of time. The amount is displayed in Records(Pieces).
Issue 02 (2007-10-15)
4-7