Attention light is lit on p610, what causes it?

[greenaixguy]

How do I diagnose what is causing this if the attention ('!') light is lit but the LCD does not report any error numbers?

OK I recognise the reboot entry but the others may as well be written in hebrew:

errlog.txt

---------------------------------------------------------------------------
LABEL: CASD_UP_IN
IDENTIFIER: BFF89323

Date/Time: Wed 22 May 10:12:58 2002
Sequence Number: 75
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: O
Type: INFO
Resource Name: ctcasd

Description
ctcasd Daemon Started

Probable Causes
ctcasd Daemon Started

Failure Causes
None

Recommended Actions
None required

Detail Data
DETECTING MODULE
rsct.core.sec,ctcas_main.c,1.9,269
ERROR ID
6XA7yz0O2quw.EDR.qkE.e0...................
REFERENCE CODE

---------------------------------------------------------------------------
LABEL: RMCD_INFO_0_ST
IDENTIFIER: A6DF45AA

Date/Time: Wed 22 May 10:12:57 2002
Sequence Number: 74
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: O
Type: INFO
Resource Name: RMCdaemon

Description
The daemon is started.

Probable Causes
The Resource Monitoring and Control daemon has been started.

User Causes
The startsrc -s ctrmc command has been executed or
the rmcctrl -s command has been executed.

Recommended Actions
Confirm that the daemon should be started.

Detail Data
DETECTING MODULE
RSCT,rmcd.c,1.32,196
ERROR ID
6eKora0N2quw.Hli1qkE.e0...................
REFERENCE CODE

---------------------------------------------------------------------------
LABEL: REBOOT_ID
IDENTIFIER: 2BFA76F6

Date/Time: Tue 21 May 17:24:33 2002
Sequence Number: 72
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: S
Type: TEMP
Resource Name: SYSPROC

Description
SYSTEM SHUTDOWN BY USER

Probable Causes
SYSTEM SHUTDOWN

Detail Data
USER ID
0
0=SOFT IPL 1=HALT 2=TIME REBOOT
1
TIME TO REBOOT (FOR TIMED REBOOT ONLY)
0
---------------------------------------------------------------------------
LABEL: ERRLOG_ON
IDENTIFIER: 9DBCFDEE

Date/Time: Wed 22 May 10:11:23 2002
Sequence Number: 71
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: O
Type: TEMP
Resource Name: errdemon

Description
ERROR LOGGING TURNED ON

Probable Causes
ERRDEMON STARTED AUTOMATICALLY

User Causes
/USR/LIB/ERRDEMON COMMAND

Recommended Actions
NONE

---------------------------------------------------------------------------
LABEL: ERRLOG_OFF
IDENTIFIER: 192AC071

Date/Time: Tue 21 May 17:23:28 2002
Sequence Number: 70
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: O
Type: TEMP
Resource Name: errdemon

Description
ERROR LOGGING TURNED OFF

Probable Causes
ERRSTOP COMMAND

User Causes
ERRSTOP COMMAND

Recommended Actions
RUN ERRDEAD COMMAND
TURN ERROR LOGGING ON

---------------------------------------------------------------------------
LABEL: CASD_UP_IN
IDENTIFIER: BFF89323

Date/Time: Tue 21 May 16:24:12 2002
Sequence Number: 69
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: O
Type: INFO
Resource Name: ctcasd

Description
ctcasd Daemon Started

Probable Causes
ctcasd Daemon Started

Failure Causes
None

Recommended Actions
None required

Detail Data
DETECTING MODULE
rsct.core.sec,ctcas_main.c,1.9,269
ERROR ID
6XA7yz0QOauw.XOs.qkE.e0...................
REFERENCE CODE

---------------------------------------------------------------------------
LABEL: RMCD_INFO_0_ST
IDENTIFIER: A6DF45AA

Date/Time: Tue 21 May 16:24:12 2002
Sequence Number: 68
Machine Id: 0050F52A4C00
Node Id: ext04dev02
Class: O
Type: INFO
Resource Name: RMCdaemon

Description
The daemon is started.

Probable Causes
The Resource Monitoring and Control daemon has been started.

User Causes
The startsrc -s ctrmc command has been executed or
the rmcctrl -s command has been executed.

Recommended Actions
Confirm that the daemon should be started.

Detail Data
DETECTING MODULE
RSCT,rmcd.c,1.32,196
ERROR ID
6eKora0QOauw.HiM.qkE.e0...................
REFERENCE CODE

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

 

[mkharris]

Have you tried running diag?? We had this problem a while back, and I'm pretty sure it was the sysplanar that was playing up. Best to place a call and get an FE in to look at - sounds like hardware ( as the software people always say )

Mark

 

[greenaixguy]

Mark,
I ran the diag Daignostics and Advanced Diagnostics tests and it didnt find any problems. Better get an engineer out then I suppose...
Cheers
Steve

 

[gheist]

Then you can run
errclear 0
to clear mess from errpt , it is very likely that error will go away (check it in a aweek or so)

 

[greenaixguy]

Apparently we dont have a current problem, its due to a previous power supply problem that is fixed, we just need to reset this in smitty somehow???

 

[mkharris]

I haven't done this myself, but it is done within diag ( which you can get to from smitty ). You can select 'Task Selection' and then 'log repair action' against the device which was repaired / replaced. I'd get a 2nd opinion on this, though, or let the engineer do it.

 

[gheist]

errclear 0 (zero)
is used to reset error log

 

[Yegolev]

diag -> repair action will leave the error log intact but diag-notify should leave you alone. errclear 0 will make it all go away. If you want to save it for some reason you can do

errpt -a>/somedir/errfile

then blast the error log with impunity (errclear 0).

 

[anshudad]

You have to shutdown the machine.When it comes up next time and the Rs/6000 logo is displayed press F1 or just 1 according to your console type. Then go to SMS menu.Then clear the errorlog from there. It will definitely fix the problem. This is nothing but clearing the NVRAM