Contents

Configuring GOLD·· 1

Configuring monitoring diagnostics· 1

Configuring on-demand diagnostics· 2

Simulating test results· 3

Configuring the log buffer size· 3

Displaying and maintaining GOLD· 4

GOLD configuration example (in standalone mode) 4

GOLD configuration example (in IRF mode) 6

 

Configuring GOLD

Generic Online Diagnostics (GOLD) performs the following tasks:

·     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.

GOLD diagnostics are divided into the following categories:

·     Boot-up diagnostics—Test device cards during boot-up or when the cards are inserted or removed. The device does not support boot-up diagnostics.

·     Monitoring diagnostics—Run diagnostic tests periodically when the system is in operation and record test results. Monitoring diagnostics execute only non-disruptive tests.

·     On-demand diagnostics—Enable you to manually start or stop diagnostic tests during system operation.

Each kind of diagnostics runs its diagnostic tests. 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.

To configure monitoring diagnostics (in standalone mode):

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
1.     Enable monitoring diagnostics.	diagnostic monitor enable slot slot-number-list [ test test-name ]	The default enabling status varies by monitoring diagnostic test. To view the status of diagnostic tests, use the display diagnostic content command.
2.     Set the execution interval.	diagnostic monitor interval slot slot-number-list [ test test-name ] time time	The default execution interval varies by monitoring diagnostic test. To view the execution interval of diagnostic tests, use the display diagnostic content command.

 

To configure monitoring diagnostics (in IRF mode):

 

Step	Command	Remarks
1.     Enter system view.	system-view	N/A
2.     Enable monitoring diagnostics.	diagnostic monitor enable chassis chassis-number slot slot-number-list [ test test-name ]	The default enabling status varies by monitoring diagnostic test. To view the status of diagnostic tests, use the display diagnostic content command.
3.     Set the execution interval.	diagnostic monitor interval chassis chassis-number slot slot-number-list [ test test-name ] time time	The default execution interval varies by monitoring diagnostic test. To view the execution interval of diagnostic tests, use the display diagnostic content command.

 

Configuring on-demand diagnostics

The diagnostic ondemand commands are effective only during the current system operation. These commands are restored to the default after you restart the device.

You can stop an on-demand diagnostic test by using any of the following commands:

·     Use the diagnostic ondemand stop command to immediately stop the test.

·     Use the diagnostic ondemand repeating command to configure the number of executions for the test.

·     Use the diagnostic ondemand failure command to configure the maximum number of failed tests before the system stops the test.

To configure on-demand diagnostics (in standalone mode):

 

Task	Command	Remarks
Configure the number of executions.	diagnostic ondemand repeating repeating-number	The default value for the repeating-number argument is 1. This command only applies to diagnostic tests to be enabled.
Configure the number of failed tests.	diagnostic ondemand failure failure-number	By default, the maximum number of failed tests is not specified. Configure a number no larger than the configured repeating-number argument. This command only applies to diagnostic tests to be enabled.
Enable on-demand diagnostics.	diagnostic ondemand start slot slot-number-list test { non-disruptive | test-name } [ para parameters ]	The system runs the tests according to the default configuration if you do not perform the first two configurations.
(Optional.) Stop on-demand diagnostics.	diagnostic ondemand stop slot slot-number-list test { non-disruptive | test-name }	You can manually stop all on-demand diagnostic tests.

 

To configure on-demand diagnostics (in IRF mode):

 

Task	Command	Remarks
Configure the number of executions.	diagnostic ondemand repeating repeating-number	The default value for the repeating-number argument is 1. This command only applies to diagnostic tests to be enabled.
Configure the number of failed tests.	diagnostic ondemand failure failure-number	By default, the maximum number of failed tests is not specified. Configure a number no larger than the configured repeating-number argument. This command only applies to diagnostic tests to be enabled.
Enable on-demand diagnostics.	diagnostic ondemand start chassis chassis-number slot slot-number-list test { non-disruptive | test-name } [ para parameters ]	By default, all on-demand diagnostic tests must be manually enabled.
(Optional.) Stop on-demand diagnostics.	diagnostic ondemand stop chassis chassis-number slot slot-number-list test { non-disruptive | test-name }	N/A

 

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.

Only monitoring diagnostics and on-demand diagnostics support test simulation.

To simulate a test:

 

Task	Command	Remarks
Simulate a test (in standalone mode).	diagnostic simulation slot slot-number-list test test-name { failure | random-failure | success }	By default, the system runs a test instead of simulating it.
Simulate a test (in IRF mode).	diagnostic simulation chassis chassis-number slot slot-number-list test test-name { failure | random-failure | success }	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

Execute display commands in any view and reset commands in user view.

 

Task	Command
Display test content (in standalone mode).	display diagnostic content [ slot slot-number ] [ verbose ]
Display test content (in IRF mode).	display diagnostic content [ chassis chassis-number [ slot slot-number ] ] [ verbose ]
Display GOLD logs.	display diagnostic event-log [ error | info ]
Display configurations of on-demand diagnostics.	display diagnostic ondemand configuration
Display test results (in standalone mode).	display diagnostic result [ slot slot-number [ test test-name ] ] [ verbose ]
Display test results (in IRF mode).	display diagnostic result [ chassis chassis-number [ slot slot-number [ test test-name ] ] ] [ verbose ]
Display statistics for packet-related tests (in standalone mode).	display diagnostic result [ slot slot-number [ test test-name ] ] statistics
Display statistics for packet-related tests (in IRF mode).	display diagnostic result [ chassis chassis-number [ slot slot-number [ test test-name ] ] ] statistics
Display configurations for simulated tests (in standalone mode).	display diagnostic simulation [ slot slot-number ]
Display configurations for simulated tests (in IRF mode).	display diagnostic simulation [ chassis chassis-number [ slot slot-number ] ]
Clear GOLD logs.	reset diagnostic event-log
Clear test results (in standalone mode).	reset diagnostic result [ slot slot-number [ test test-name ] ]
Clear test results (in IRF mode).	reset diagnostic result [ chassis chassis-number [ slot slot-number [ test test-name ] ] ]

 

GOLD configuration example (in standalone mode)

Network requirements

Enable monitoring diagnostic test HGMonitor on MPU 6, and set its execution interval to 1 minute.

Configuration procedure

# View the default status and execution interval of the test on MPU 6.

<Sysname> display diagnostic content slot 6 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 6 :

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.

exec             : -NA-

# Enable test HGMonitor on MPU 6.

<Sysname> system-view

[Sysname] diagnostic monitor enable slot 6 test HGMonitor

# Set the execution interval to 1 minute.

[Sysname] diagnostic monitor interval slot 6 test HGMonitor time 0:1:0

Verifying the configuration

# View the test configuration.

[Sysname] display diagnostic content slot 6 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 6 :

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.

exec             : -NA-

# View the test result.

[Sysname] display diagnostic result slot 6 verbose

Slot 6 :

  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

GOLD configuration example (in IRF mode)

Network requirements

Enable monitoring diagnostic test HGMonitor on MPU 6 of IRF member device 1, and configure its execution interval as 1 minute.

Configuration procedure

# View the default status and execution interval of the test on MPU 6 of IRF member device 1.

<Sysname> display diagnostic content chassis 1 slot 6 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

 

Chassis 1 Slot 6 :

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.

exec             : -NA-

# Enable test HGMonitor on MPU 6 of IRF member device 1.

<Sysname> system-view

[Sysname] diagnostic monitor enable chassis 1 slot 6 test HGMonitor

# Set the execution interval to 1 minute.

[Sysname] diagnostic monitor interval chassis 1 slot 6 test HGMonitor time 0:1:0

Verifying the configuration

# View the test configuration.

[Sysname] display diagnostic content chassis 1 slot 6 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

 

Chassis 1 Slot 6 :

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.

exec             : -NA-

# View the test result.

[Sysname] display diagnostic result chassis 1 slot 6 verbose

Chassis 1 Slot 6 :

  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