(B1xx) Service processor firmware reference codes

A B1xx reference code indicates that an event or exception occurred in service processor firmware. To resolve any B1xx reference code, determine if the SRC requires a service action or if it is for tracking purposes only.

Diagnostics analyze an event when it occurs to determine if the event requires service or if the event will only be recorded for tracking purposes and future reference. The determination is based on machine type, model, installed features, configuration, topology and activations at the time of the event. If you do not find the SRC in a serviceable event view then it is a tracking event only and does not require service. Tracking events appear as "informational" or "Misc." or "temp" in the i5/OS® Product Activity log and the Advanced System Manage Interface (ASMI). Serviceable event views are the AIX Diagnostics Results Log, the i5/OS Problem Log, the i5/OS Service Action Log (SAL), the HMC Service Focal Point, the Integrated Virtualization Manager Service Focal Point, the Linux Diagnostic Messages Log, the system control panel, or ASMI listed under serviceable events.

See (B1xx) Service processor firmware reference code descriptions for a description of the SRC.

Determine whether service action is needed or not, it is based upon where to work with the B1xx SRC:

  1. Is the system managed by an HMC?
  2. Is the system console available?
  3. The system console is not available.

Table 1. How to determine the nature of a (B1xx) reference code

Where you found the SRC How to determine the nature of the SRC
Hardware Management Console (HMC) Search for the SRC in the Service Focal Point on the HMC. See Using Service Focal Point for the HMC for help in using the Service Focal Point.
  • If you find the SRC in the Service Focal Point, it requires a service action. Refer to Repairing serviceable events for more information on using the Service Focal Point.
  • If you do not find the SRC in the Service Focal Point, it is for tracking purposes only and does not require service.
AIX Look in the diagnostics results log.
  • If you find the SRC in the Diagnostics Results Log, it requires a service action.
  • If you do not find the SRC in the Diagnostics Results Log, it is for tracking purposes only and does not require service.
Linux Look in the diagnostics message log.
  • If you find the SRC in the Diagnostics Message Log, it requires a service action.
  • If you do not find the SRC in the Diagnostics Message Log, it is for tracking purposes only and does not require service.
Note:
The Linux Service Aids must be installed to view the message log: If these Service Aids are not installed then the message log entries can not be viewed. http://techsupport.services.ibm.com/server/lopdiags
i5/OS Look in the Service Action Log.
  • If you find the SRC in the SAL, it requires a service action.
  • If you do not find the SRC in the SAL, it is for tracking purposes only and does not require service.
Integrated Virtualization Manager Look in the Service Focal Point. For details, see Using Service Focal Point for the Integrated Virtualization Manager.
  • If you find the SRC in the Service Focal Point, it requires a service action.
  • If you do not find the SRC in the Service Focal point, it is for tracking purposes only and does not require service.
Advanced System Management Interface (ASMI) To determine if the SRC requires repair action or not using ASMI, see the table in Displaying error and event logs.

If the SRC is in the Miscellaneous event logs row, then no repair action is needed. If the SRC is in the Error logs row, then service is needed. Select that log and Show Details to get the full detail format of the log. Then, use the Callout section of the Error and Event Logs and (B1xx) Service processor firmware reference code callouts.

Control Panel See (B1xx) Service processor firmware reference code callouts for instructions. Collect SRC and system information (if possible). See Using the control panel to collect reference codes and system information.

Send feedback |  Rate this page