Skip to main content

Intermittent problems

Use this information to solve intermittent problems.

Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.

The intermittent problems table is a two-column table that lists the symptoms and corrective actions for intermittent problems. Column 1 lists the symptom. Column 2 describes the corrective actions for each symptom.

  • Follow the suggested actions in the order in which they are listed in the Action column until the problem is solved.
  • See Parts listing, Types 7167 and 2590 to determine which components are customer replaceable units (CRU) and which components are field replaceable units (FRU) that must be replaced only by a trained service technician.
  • If an action step is preceded by (Trained service technician only), that step must be performed only by a trained service technician.
SymptomAction
Intermittent external device problems
  1. Make sure that the correct device drivers are installed. See the manufacturer's website for documentation.
  2. For a USB device:
    1. Make sure that the device is configured correctly (see Using the Setup utility).
    2. Connect the device to another port. If you are using a USB hub, remove the hub and connect the device directly to the compute node. Make sure that the device is configured correctly for the port (see Using the Setup utility).
    3. Run DSA Preboot USB diagnostics.
Intermittent KVM problems
Video problems:
  1. Make sure that all cables and the console breakout cable are properly connected and secure.
  2. Make sure that the monitor is working properly by testing it on another compute node.
  3. Test the console breakout cable on a working compute node to ensure that it is operating properly. Replace the console breakout cable if it is defective.

Keyboard problems:

Make sure that all cables and the console breakout cable are properly connected and secure.

Mouse problems:

Make sure that all cables and the console breakout cable are properly connected and secure.

Intermittent unexpected rebootsCheck for an event code that indicates a reboot. See the event log for the management node (if available) or see the CMM event log to determine what actions might be required to resolve this issue. See IMM event log. Some correctable errors require that the compute node reboot so that it can disable a device, such as a DIMM or a microprocessor, to allow the compute node to boot properly.