No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


How to Collect Debugging Information?

Publication Date:  2012-07-28 Views:  262 Downloads:  0
Issue Description
This topic describes how to collect debugging information in the NMS, which will be used for fault location if a fault recurs.
Alarm Information
Handling Process
1.         Telnet to the NMS server through port 9810 to start debugging, as shown in the following figure.:

2.         Enter setdbgpara (or setdbg for short) and specify the following information as prompted: 

1.         Process ID.

2.         Sub-module name. Press Enter to skip this step.

3.         Debugging level, used to define the output information.

0 indicates no debugging information. 

1 indicates assertions and 2 indicates both assertions and errors.

3 indicates assertions, errors, and alarms.

indicates all debugging information.

To obtain the most detailed information, set the level to 4.

4.         Information output destination, where 0 means no output, 2 means output to a file, and 4 means output to the current debugging window. To save the output information, set the destination option to 2. As shown in the following figure, the process ID is 74, which indicates an XDSL process.

3.         Perform the following operations in the NMS.

4.         In the server\conf\log directory, open the corresponding log file, as determined by the process ID, to view detailed debugging information.

For example, base_p74_20080704_150206.log is the debugging information of process 74, where 20080704 and 150206 indicate that the debugging information was created at 15:02:06 on July 4th, 2008. 

5.         Copy the log file to another directory and save it.

6.         Disable the debugging by specifying the debugging level to 0 and the output destination to 1.
Root Cause
You can see from the System Monitor that the test process (Service: Exam Process, Process Name: EmfExamDm) operates normally on the client.
Collect debugging information in time if an issue recurs. This helps avoid loss of the information needed for fault location due to information refreshing. 

After collecting debugging information, disable the debugging function. 

In the server\conf\log directory, collect only the debugging files whose name is in the format of base_p(process ID)_(date)_time.log. Do not pack the entire directory.