Sequence of Startup Diagnostics

Default startup diagnostics are executed when the Sun Blade 8000 Series or individual system components are powered on, power cycled, or reset. When the system chassis is started, default startup diagnostics are executed in the following sequence:

  1. uBoot diagnostics test the hardware on the Chassis Monitoring Modules (CMMs).

    The OK LED on the CMM blinks slowly while uBoot executes. uBoot determines whether the CMM hardware can be safely started. If a diagnostic failure occurs, the CMM will not start. See About Diagnostic Failures.

    Note that if there are two CMMs present, uBoot diagnostics test the hardware on both of them.

  2. The CMM's OK LED changes to steady green to indicate that the CMM is now running.

  3. On each blade:

    1. uBoot diagnostics test the hardware on the blade's service processor (SP).

      The blade's OK LED blinks slowly while uBoot executes. uBoot determines whether the SP can be safely started. If a uBoot diagnostic failure occurs, neither the SP nor the blade host will start. See About Diagnostic Failures.

    2. The blade's OK LED changes to standby blink.

      Standby blink indicates that the SP is operational but the host has not yet booted.

    3. BIOS POST tests the hardware on the host.

      The blade's OK LED again blinks slowly as BIOS POST executes. BIOS POST determines whether the host's operating system can be started. If a fatal BIOS POST failure occurs, the host operating system will not boot. See About Diagnostic Failures.

    4. The host operating system begins to boot and the blade's OK LED changes to steady green.