Attention Indicator

However, if the S/P error log entry, and the corresponding Attention Indicator, was activated during install/setup by some known user action, it may be appropriate to clear the attention indicator. Simple user actions which can turn on the LED include - rebooting the HMC, attempting to boot a system (or LPAR) without specifying a valid boot device etc.
The system attention indicator LED can also be turned on by any detected hardware error conditions.

The LED can be turned off temporarily (using AIX diag command, HMC menu, or S/P menu).
However, if the LED was turned on by some system event, it will be re-activated the next time that the system is re-booted. This will continue to happen until the Service Processor error log is cleared.

Clearing Service Processor Error Log

Using an ASCII terminal attached to S1 port

1. Verify that the operator panel shows "OK"
2. Connect an ASCII terminal to S1 port
3. Press Enter
   You should then see the Service Processor Main Menu (and the operator panel should show E075)
4. Follow the procedure "Clearing the Attention Indicator" described below

Using HMC

1. On HMC, verify that the CEC (or "managed syste") shows "No Power"
2. On HMC - right click the CEC and select "Open Terminal Window".
   If you receive a message HSCL0FA2 "All available virtual terminal sessions have been opened and are in use", simply right-click the CEC and select "Close Terminal Connection", then repeat step 1
3. You should see the Service Processor Menu.
   If not, press enter.
4. Follow the procedure "Clearing the Attention Indicator" described below

   Clearing the Attention Indicator

   (An example of the Service Processor Main Menu is shown at the end of this page)
   At the Service Processor Main Menu:
   1. Select 3. System Information Menu
      will give the System Information Menu
   2. Select 3. Read Service Processor Error Logs
      If you receive message "No errors have been reported", press enter to return to the menu, and go to step 4
      If you receive a list of errors "Error Log", this Service processor error log can be cleared providing that:
      • the error details are accurately written down or
      • all errors have been reviewed and the appropriate repair actions have been completed
        ( For further details, see the "Error Log" section below.)
   3. Press C to clear the error log. ( this will automatically return to the previous menu)
   4. Select 10. LED Control Menu
   5. Select 2. Clear System Attention Indicator
   6. Select 98 to return to previous menu, then 98 to return to S/P Main Menu
   7. Restart the system

   Error Log

   You might see something like this:

   1. 04/04/2003 14:34:29 System Power Control Network Cooling Warning
   10117621   U0.1-F4
   2. 04/04/2003 21:45:50 System Power Control Network Power Warning
   10211520   U0.2-V2
   3. 04/20/2003 21:42:15 Boot failure detected
   20EE000B
   4. 04/25/2003 13:13:04 HMC Surveillance Error - Connection to HMC lost
   B1764699
   

   
   Errors requiring attention and action:
   Some of the errors (e.g 1 and 2 ) could indicate an error condition which requires attention.
   Do not clear the error log until CE (and/or the System Administrator) has performed the appropriate action.
   Appropriate action might include
   • Viewing Service Events on HMC - and performing appropriate action.
   • Verifying hardware (e.g. diagnostics) - and performing appropriate action.
   • Recording the actions in the SFP log.
   • Reviewing error logs in AIX
   • Running system verification using "diag" command (e.g. diag -d sysplanar0)
   • Running the "Log Repair Action" Service Aid using AIX "diag" command
   • Clearing warnings issued by cron (e.g. for power/cooling errors)
     See /var/spool/cron/crontabs/root
     
   • etc.
   Always verify that there is no CE action required before clearing the error log.
   In the above example there was, in fact, no error condition .. items (1) and (2) were caused by shutting down the system and disconnecting the power.

   Errors requiring attention:
   Some of the errors could indicate a condition which may require attention, but perhaps requires no hardware service action, for example:

   • Boot failure detected 20EE000B
     This simply indicates a boot failure, perhaps caused by not specifying the correct boot-disk
   • HMC Surveillance Error
     This could indicate a potential problem (e.g. with HMC) or could be caused simply be rebooting the HMC.

   In the above example there was, in fact, no error condition . item (3) was caused by selecting the wrong disk in the SMS menu, and (4) was caused by a manual re-boot of the HMC.

   The initial Service Processor menu:

   Service Processor Firmware

   Version RR030324

   Copyright 2001, IBM Corporation

   655CFFA - p630

   --------------------------------------------

   MAIN MENU

   1. Service Processor Setup Menu

   2. System Power Control Menu

   3. System Information Menu

   4. Language Selection Menu

   5. Call-In/Call-Out Setup Menu

   6. Set System Name

   99 Exit from Menus

   The above is just shown as an example. Clearly the initial details will depend upon the actual system (in this case a p630).