nx.os.and.cisco.nexus.switching.2nd.edition.1587143046

disruptive and should be used with caution within a production environment.
GOLD verifies functionality using a variety of techniques; the full suite of diagnostic
utilities is broken down into the following categories:
• Bootup diagnostics
• Runtime diagnostics
• On-demand diagnostics
Within each of these categories, specific tests are also classified as disruptive or
nondisruptive.
Bootup Diagnostics
Prior to a module coming online within NX-OS, several checks are run on the hardware
depending on the type. By default, a complete set of tests are run prior to placing the module
in service. It is not recommended to alter this behavior, but if necessary to decrease boot
time, these tests can be bypassed, as shown in Example 6-6.
Example 6-6. Bypassing Bootup Diagnostics
Click here to view code image
Congo# show diagnostic bootup level
Current bootup diagnostic level: complete
Congo# conf t
Enter configuration commands, one per line. End with
CNTL/Z.
Congo(config)# diagnostic bootup level bypass
Congo(config)# sho diagnostic bootup level
Congo(config)#
Runtime Diagnostics
Current bootup diagnostic level: bypass
Although bootup diagnostics prevent a module from coming online without exhaustively
testing the hardware functionality, it is not uncommon for modules or entire systems to run
for months or years without rebooting. It is therefore necessary to run periodic checks on the
hardware during the normal operation of the device. These checks are referred to as runtime
diagnostics and can be viewed from the command-line interface (CLI).
Example 6-7 shows the runtime diagnostics performed on a supervisor module.