- Table of Contents
-
- 12-Network Management and Monitoring Configuration Guide
- 00-Preface
- 01-System maintenance and debugging configuration
- 02-NQA configuration
- 03-NTP configuration
- 04-SNMP configuration
- 05-RMON configuration
- 06-NETCONF configuration
- 07-EAA configuration
- 08-Process monitoring and maintenance configuration
- 09-Sampler configuration
- 10-Mirroring configuration
- 11-NetStream configuration
- 12-IPv6 NetStream configuration
- 13-sFlow configuration
- 14-Information center configuration
- 15-GOLD configuration
- 16-Packet capture configuration
- 17-VCF fabric configuration
- 18-CWMP configuration
- 19-SmartMC configuration
- Related Documents
-
Title | Size | Download |
---|---|---|
15-GOLD configuration | 63.73 KB |
Configuring GOLD
Generic Online Diagnostics (GOLD) performs the following operations:
· Runs diagnostic tests on a device to inspect device ports, RAM, chip, connectivity, forwarding paths, and control paths for hardware faults.
· Reports the problems to the system.
The device supports only monitoring diagnostics. Monitoring diagnostics run diagnostic tests periodically when the system is in operation and record test results. Monitoring diagnostics execute only non-disruptive tests.
Diagnostic tests are used for diagnostics. The parameters of a diagnostic test include test name, type, description, attribute (disruptive or non-disruptive), default status, and execution interval.
Support for the diagnostic tests and default values for a test's parameters depend on the device model. You can modify part of the parameters by using the commands provided by this document.
The diagnostic tests are released with the system software image of the device. All enabled diagnostic tests run in the background. You can use the display commands to view test results and logs to verify hardware faults.
Configuring monitoring diagnostics
The system automatically executes monitoring diagnostic tests that are enabled by default after the device starts. Use the diagnostic monitor enable command to enable monitoring diagnostic tests that are disabled by default.
Use the diagnostic monitor interval command to configure an execution interval for each test. The interval you set must be no smaller than the minimum interval for each test. You can view the minimum interval for a test by using the display diagnostic content command.
(In standalone mode.) To configure monitoring diagnostics:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Enable monitoring diagnostics. |
diagnostic monitor enable slot slot-number-list [ test test-name ] |
By default, the settings for this command vary by test. Use the display diagnostic content command to view the status of a monitoring diagnostic test. |
3. Set the execution interval. |
diagnostic monitor interval slot slot-number-list [ test test-name ] time interval |
By default, the settings for this command vary by test. Use the display diagnostic content command to view the execution interval for a test. |
(In IRF mode.) To configure monitoring diagnostics:
Step |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
1. Enable monitoring diagnostics. |
diagnostic monitor enable chassis chassis-number slot slot-number-list [ test test-name ] |
By default, the settings for this command vary by test. Use the display diagnostic content command to view the status of a monitoring diagnostic test. |
2. Set the execution interval. |
diagnostic monitor interval chassis chassis-number slot slot-number-list [ test test-name ] time interval |
By default, the settings for this command vary by test. Use the display diagnostic content command to view the execution interval for a test. |
Simulating test results
Test simulation verifies GOLD frame functionality. When you use the diagnostic simulation commands to simulate a diagnostic test, only part of the test code is executed to generate a test result. Test simulation does not trigger hardware correcting actions such as device restart and active and standby switchover.
To simulate a test:
Task |
Command |
Remarks |
Simulate a test. |
·
In standalone mode: ·
In IRF mode: |
By default, the system runs a test instead of simulating it. |
Configuring the log buffer size
GOLD saves test results in the form of logs. You can use the display diagnostic event-log command to view the logs.
To configure the GOLD log buffer size:
Task |
Command |
Remarks |
1. Enter system view. |
system-view |
N/A |
2. Configure the maximum number of GOLD logs that can be saved. |
diagnostic event-log size number |
By default, GOLD saves 512 log entries at most. When the number of logs exceeds the configured log buffer size, the system deletes the oldest entries. |
Displaying and maintaining GOLD
(In standalone mode.) Execute display commands in any view and reset commands in user view.
Task |
Command |
Display test content. |
display diagnostic content [ slot slot-number ] [ verbose ] |
Display GOLD logs. |
display diagnostic event-log [ error | info ] |
Display test results. |
display diagnostic result [ slot slot-number [ test test-name ] ] [ verbose ] |
Display configurations for simulated tests. |
display diagnostic simulation [ slot slot-number ] |
Clear GOLD logs. |
reset diagnostic event-log |
Clear test results. |
reset diagnostic result [ slot slot-number [ test test-name ] ] |
(In IRF mode.) Execute display commands in any view and reset commands in user view.
Task |
Command |
Display test content. |
display diagnostic content [ chassis chassis-number [ slot slot-number ] ] [ verbose ] |
Display GOLD logs. |
display diagnostic event-log [ error | info ] |
Display test results. |
display diagnostic result [ chassis chassis-number [ slot slot-number [ test test-name ] ] ] [ verbose ] |
Display configurations for simulated tests. |
display diagnostic simulation [ chassis chassis-number [ slot slot-number ] ] |
Clear GOLD logs. |
reset diagnostic event-log |
Clear test results. |
reset diagnostic result [ chassis chassis-number [ slot slot-number [ test test-name ] ] ] |
GOLD configuration example
Network requirements
Enable monitoring diagnostic test HGMonitor on slot 1, and set its execution interval to 1 minute.
Configuration procedure
# View the default status and execution interval of the test on slot 1.
<Sysname> display diagnostic content slot 1 verbose
Diagnostic test suite attributes:
#B/*: Bootup test/NA
#O/*: Ondemand test/NA
#M/*: Monitoring test/NA
#D/*: Disruptive test/Non-disruptive test
#P/*: Per port test/NA
#A/I/*: Monitoring test is active/Monitoring test is inactive/NA
Slot 1:
Test name : HGMonitor
Test attributes : **M*PI
Test interval : 00:00:10
Min interval : 00:00:10
Correct-action : -NA-
Description : A Real-time test, disabled by default that checks link status between ports.
# Enable test HGMonitor on slot 1.
<Sysname> system-view
[Sysname] diagnostic monitor enable slot 1 test HGMonitor
# Set the execution interval to 1 minute.
[Sysname] diagnostic monitor interval slot 1 test HGMonitor time 0:1:0
Verifying the configuration
# View the test configuration.
[Sysname] display diagnostic content slot 1 verbose
Diagnostic test suite attributes:
#B/*: Bootup test/NA
#O/*: Ondemand test/NA
#M/*: Monitoring test/NA
#D/*: Disruptive test/Non-disruptive test
#P/*: Per port test/NA
#A/I/*: Monitoring test is active/Monitoring test is inactive/NA
Slot 1:
Test name : HGMonitor
Test attributes : **M*PA
Test interval : 00:01:00
Min interval : 00:00:10
Correct-action : -NA-
Description : A Real-time test, disabled by default that checks link status between ports.
# View the test result.
[Sysname] display diagnostic result slot 1 verbose
Slot 1:
Test name : HGMonitor
Total run count : 1247
Total failure count : 0
Consecutive failure count: 0
Last execution time : Tue Dec 25 18:09:21 2012
First failure time : -NA-
Last failure time : -NA-
Last pass time : Tue Dec 25 18:09:21 2012
Last execution result : Success
Last failure reason : -NA-
Next execution time : Tue Dec 25 18:10:21 2012
Port link status : Normal