Contents

Configuring GOLD·· 1

About GOLD·· 1

Types of GOLD diagnostics· 1

GOLD diagnostic tests· 1

Restrictions: Hardware compatibility with GOLD·· 1

GOLD tasks at a glance· 2

Configuring monitoring diagnostics· 2

Configuring script-bound diagnostics· 3

Simulating diagnostic tests· 3

Configuring the log buffer size· 4

Display and maintenance commands for GOLD·· 4

 

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:

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

Restrictions: Hardware compatibility with GOLD

Hardware platform	Module type	GOLD compatibility
M9006 M9010 M9014	Blade IV firewall module	No
	Blade V firewall module	No
	NAT module	No
	Application delivery engine (ADE) module	No
	Anomaly flow cleaner (AFC) module	No
M9010-GM	Encryption module	No
M9016-V	Blade V firewall module	No
M9008-S M9012-S	Blade IV firewall module	No
	Application delivery engine (ADE) module	No
	Intrusion prevention service (IPS) module	No
	Video network gateway module	No
	Anomaly flow cleaner (AFC) module	No
M9008-S-6GW	IPv6 module	No
M9008-S-V	Blade IV firewall module	No
M9000-AI-E8	Blade V firewall module	Yes
	Application delivery engine (ADE) module	Yes
M9000-AI-E16	Blade V firewall module	Yes

‌

GOLD tasks at a glance

To configure GOLD, perform the following tasks:

1.     Configuring diagnostics

Choose the following tasks as needed:

¡     Configuring monitoring diagnostics

¡     Configuring script-bound diagnostics

2.     (Optional.) Simulating diagnostic tests

3.     (Optional.) Configuring the log buffer size

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 script-bound diagnostics

About this task

The device is configured with tests that are bound with scripts before the device is shipped. The system supports TCL and shell scripts, such as scripts for verifying chip and port basic information after the device is powered on. After you use this command to start a test, the system automatically runs the scripts and displays the results at the CLI.

Procedure

To start script-bound diagnostics, execute the following command in user view:

diagnostic start test test-name [ parameters ]

Simulating diagnostic tests

About this task

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/standby switchover.

Restrictions and guidelines

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

Procedure

To simulate a test, execute the following command in user view:

In standalone mode:

diagnostic simulation slot slot-number-list [ cpu cpu-number ] test test-name { failure | random-failure | success }

In IRF mode:

diagnostic simulation chassis chassis-number slot slot-number-list [ cpu cpu-number ] test test-name { failure | random-failure | success }

By default, the system runs a test instead of simulating it.

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.

 

Task	Command
Display test content.	In standalone mode: display diagnostic content [ slot slot-number [ cpu cpu-number ] ] [ verbose ] In IRF mode: display diagnostic content [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] ] ] [ verbose ]
Display GOLD logs.	display diagnostic event-log [ error | info ]
Display test results.	In standalone mode: display diagnostic result [ slot slot-number [ cpu cpu-number ] [ test test-name ] ] [ verbose ] In IRF mode: display diagnostic result [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ test test-name ] ] ] [ verbose ]
Display statistics for packet-related tests.	In standalone mode: display diagnostic result [ slot slot-number [ cpu cpu-number ] [ test test-name ] ] statistics In IRF mode: display diagnostic result [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ test test-name ] ] ] statistics
Display configurations for simulated tests.	In standalone mode: display diagnostic simulation [ slot slot-number [ cpu cpu-number ] ] In IRF mode: display diagnostic simulation [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] ] ]
Clear GOLD logs.	reset diagnostic event-log
Clear test results.	In standalone mode: reset diagnostic result [ slot slot-number [ cpu cpu-number ] [ test test-name ] ] In IRF mode: reset diagnostic result [ chassis chassis-number [ slot slot-number [ cpu cpu-number ] [ test test-name ] ] ]

‌