Issue Description
Q:
How to turn on the debug switch in the DC Server process?
How to turn on the debug switch in the DC Server process?
Alarm Information
Null
Handling Process
A:
There are two methods to turn on the debug switch in the DC Server process:
I. Find the DC_DEBUGINFO_SWITCH parameter in the $n2000\server\conf\dc.cfg file (under the n2000 installation directory):
#For debugging the data center
DC_DEBUGINFO_SWITCH = 1
1: indicates starting the system monitor; 0: indicates closing the system monitoring function
Modify the parameter to 1 to turn on the debug switch. After several operations resulting in the DCServer faults, two log files containing the DC field will be generated under $n2000/server/log.
DC_UA5000G_Alarm_Info.log0 and DC_172.20.17.70-161_Info.log0 (172.20.17.70 refers to the IP address of the operated device in the DCServer),
After collecting the debug information, you are recommended to turn off the switch timely to avoid generating further log files.
2. Operate as per the following steps:
telnet 10.71.61.45 9810
Firstly, telnet to the port 9810 of the NM server. 10.71.61.45 corresponds to the IP address of the NM server
iMAP>setdbg
ProcessID : 148 (The internal process number corresponding to the DCServer)
Scope(format is "module_submodule". default, all module) ://enter
Debug level as following:
0, None;
1, Error.
2, Error and Warning.
3, Error Warning and Info.
Please select level : 3
Debug output orient as following:
0, Standard output.
1, file.
2, share memory.
3, EmfExamDm.
Please select orient : 1
Setting succeeded!
After several operations resulting in the DC Server fault, stop the debug switch.
iMAP>setdbg
Process ID : 148
Scope(format is "module_submodule". default, all module) :
Debug level as following:
0, Null;
1, Error.
2, Error and Warning.
3, Error Warning and Info.
Please select level : 0
Debug output orient as following:
0, Standard output.
1, file.
2, share memory.
3, EmfExamDm.
Please select orient : 0
Setting succeeded!
Obtain the debug information about the DCServer process generated under $n2000/server/debug.
3. The information generated from the first method is less and easier for analysis, so the Method 1is normally used to identify general problems. The second method can generate more information, so it is more complicated for analysis, and often used to identify difficult problems.
There are two methods to turn on the debug switch in the DC Server process:
I. Find the DC_DEBUGINFO_SWITCH parameter in the $n2000\server\conf\dc.cfg file (under the n2000 installation directory):
#For debugging the data center
DC_DEBUGINFO_SWITCH = 1
1: indicates starting the system monitor; 0: indicates closing the system monitoring function
Modify the parameter to 1 to turn on the debug switch. After several operations resulting in the DCServer faults, two log files containing the DC field will be generated under $n2000/server/log.
DC_UA5000G_Alarm_Info.log0 and DC_172.20.17.70-161_Info.log0 (172.20.17.70 refers to the IP address of the operated device in the DCServer),
After collecting the debug information, you are recommended to turn off the switch timely to avoid generating further log files.
2. Operate as per the following steps:
telnet 10.71.61.45 9810
Firstly, telnet to the port 9810 of the NM server. 10.71.61.45 corresponds to the IP address of the NM server
iMAP>setdbg
ProcessID : 148 (The internal process number corresponding to the DCServer)
Scope(format is "module_submodule". default, all module) ://enter
Debug level as following:
0, None;
1, Error.
2, Error and Warning.
3, Error Warning and Info.
Please select level : 3
Debug output orient as following:
0, Standard output.
1, file.
2, share memory.
3, EmfExamDm.
Please select orient : 1
Setting succeeded!
After several operations resulting in the DC Server fault, stop the debug switch.
iMAP>setdbg
Process ID : 148
Scope(format is "module_submodule". default, all module) :
Debug level as following:
0, Null;
1, Error.
2, Error and Warning.
3, Error Warning and Info.
Please select level : 0
Debug output orient as following:
0, Standard output.
1, file.
2, share memory.
3, EmfExamDm.
Please select orient : 0
Setting succeeded!
Obtain the debug information about the DCServer process generated under $n2000/server/debug.
3. The information generated from the first method is less and easier for analysis, so the Method 1is normally used to identify general problems. The second method can generate more information, so it is more complicated for analysis, and often used to identify difficult problems.
Root Cause
In the event of some unpredictable errors during the device operation in the DC Server, such as upgrade failure or patching failure, you can turn on the debug switch in the DC Server process to collect the debug information to identify the cause of the fault.
Suggestions
Null
More related:Introduction to MSTP_Prelude_Overview and History
No comments:
Post a Comment