Contents

Configuring GOLD·· 1

About GOLD·· 1

Types of GOLD diagnostics· 1

GOLD diagnostic tests· 1

GOLD tasks at a glance· 1

Configuring boot-up diagnostics· 1

Configuring monitoring diagnostics· 2

Configuring the log buffer size· 3

Display and maintenance commands for GOLD·· 3

Configuring GOLD

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

Types of GOLD diagnostics

GOLD diagnostics are divided into the following types:

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

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

GOLD diagnostic tests

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.

GOLD tasks at a glance

To configure GOLD, perform the following tasks:

1.     Configuring diagnostics

Choose the following tasks as needed:

¡     Configuring boot-up diagnostics

¡     Configuring monitoring diagnostics

2.     (Optional.) Configuring the log buffer size

Configuring boot-up diagnostics

·     Enable the device to run all boot-up diagnostic tests.

a.     system-view

b.     diagnostic bootup level complete

·     Disable boot-up diagnostics.

a.     system-view

b.     diagnostic bootup level bypass

By default, the system does not run boot-up diagnostic tests during startup.

Configuring monitoring diagnostics

About this task

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.

Procedure

1.     Enter system view.

system-view

2.     Enable monitoring diagnostics.

In standalone mode:

diagnostic monitor enable slot slot-number-list [ cpu cpu-number ] [ test test-name ]

In IRF mode:

diagnostic monitor enable chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ test test-name ]

By default, monitoring diagnostics are enabled.

3.     Set an execution interval for monitoring diagnostic tests.

In standalone mode:

diagnostic monitor interval slot slot-number-list [ cpu cpu-number ] [ test test-name ] time interval

In IRF mode:

diagnostic monitor interval chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ test test-name ] time interval

By default, the execution interval varies by monitoring diagnostic test. To display the execution interval of a monitoring diagnostic test, execute the display diagnostic content command.

The configured interval cannot be smaller than the minimum execution interval of the tests. Use the display diagnostic content verbose command to view the minimum execution interval of the tests.

4.     Set the recovery action for monitoring diagnostic tests.

In standalone mode:

diagnostic monitor action slot slot-number-list [ cpu cpu-number ] [ test test-name ] mode { none | self-reboot | service-restart | switchover | system-reboot }

In IRF mode:

diagnostic monitor action chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ test test-name ] mode { none | self-reboot | service-restart | switchover | system-reboot }

By default, the settings for this command vary by test. Use the display diagnostic content verbose command to view the recovery action for a test. If a test does not support any recovery action, its recovery action is displayed as -NA-.

Configuring the log buffer size

About this task

GOLD saves test results in the form of logs. You can use the display diagnostic event-log command to view the logs.

Procedure

1.     Enter system view.

system-view

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.

Display and maintenance commands for GOLD

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

‌