- Table of Contents
-
- 20-Network Management and Monitoring Configuration Guide
- 00-Preface
- 01-Ping and tracert configuration
- 02-System debugging configuration
- 03-NQA configuration
- 04-iNQA configuration
- 05-iFIT configuration
- 06-NTP configuration
- 07-SNMP configuration
- 08-RMON configuration
- 09-Sampler configuration
- 10-Mirroring configuration
- 11-NetStream configuration
- 12-IPv6 NetStream configuration
- 13-sFlow configuration
- 14-Cloud connection configuration
- 15-Packet capture configuration
- 16-IP traffic statistics collection configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
02-System debugging configuration | 56.96 KB |
Enabling debugging for a module
Displaying the enabled debugging features
Enabling the debugging-auto-off feature
Displaying the enabling status of the debugging-auto-off feature
Configuring system debugging
About system debugging
The device supports debugging for the majority of protocols and features, and provides debugging information to help users diagnose errors.
The following switches control the display of debugging information:
· Module debugging switch—Controls whether to generate the module-specific debugging information.
· Screen output switch—Controls whether to display the debugging information on a certain screen. Use terminal monitor and terminal logging level commands to turn on the screen output switch. For more information about these two commands, see information center commands in System Management Command Reference.
As shown in Figure 1, the device can provide debugging for the three modules 1, 2, and 3. The debugging information can be output on a terminal only when both the module debugging switch and the screen output switch are turned on.
Debugging information is typically displayed on a console. You can also send debugging information to other destinations. For more information, see information center configuration in System Management Configuration Guide.
Figure 1 Relationship between the module and screen output switch
Debugging a feature module
Restrictions and guidelines
CAUTION: Output of excessive debugging messages increases the CPU usage and downgrades the system performance. To guarantee system performance, enable debugging only for modules that are in an exceptional condition. |
When debugging is complete, use the undo debugging all command to disable all the debugging functions.
Enabling debugging for a module
Enable debugging for a module in user view:
debugging module-name [ option ]
By default, debugging is disabled for all modules.
Displaying the enabled debugging features
Execute the following command in any view to display the enabled debugging features for a module or for all modules:
display debugging [ module-name ]
Enabling the debugging-auto-off feature
Execute the following command in user view to enable the debugging-auto-off feature to automatically disable all types of debugging when the CPU usage reaches or exceeds the lowest CPU usage alarm threshold:
debugging-auto-off enable cpu-usage-alarm
By default, the debugging-auto-off feature is not enabled.
Displaying the enabling status of the debugging-auto-off feature
Execute the following command in any view to display the enabling status of the debugging-auto-off feature:
display debugging-auto-off