ERR_TOC_TASK and another Error???

[Mousa55]

Hi
I have now new attention lamp glows in my unix server (rp8420)
And I am tray to clear this attention by read the logs file from SEL
but this attempt did not help me, how to clear this attention

Alert level 2: Informational
Keyword: IO_BP_LPM_OFF
The IO backplane is reporting the LPM status as off.
Reporting Entity: Management Processor located in cabinet 0
0x4b000eca00e00a70 0x0100000047984236

Log Entry 42320: 01/24/2008 07:45:58
Alert level 2: Informational
Keyword: CABPWR_OFF
Cabinet Power Turned Off By Command
Reporting Entity: Power Monitor located in cabinet 0
0x4b000af800e00a71 0x0100000047984236

Log Entry 42321: 01/24/2008 07:45:58
Alert level 2: Informational
Keyword: IO_BP_LPM_OFF
The IO backplane is reporting the LPM status as off.
Reporting Entity: Management Processor located in cabinet 0
0x4b000eca00e00a72 0x0100000047984236

Log Entry 42322: 01/24/2008 08:22:45
Alert level 2: Informational
Keyword: POWER_SWITCH_OFF
Cabinet Power Switch turned off
Reporting Entity: Power Monitor located in cabinet 0
0x4b000b1b00e00a73 0x0100000047984ad5

Log Entry 42323: 01/24/2008 08:22:53
Alert level 2: Informational
Keyword: CABPWR_OFF
Cabinet Power Turned Off By Command
Reporting Entity: Power Monitor located in cabinet 0
0x4b000af800e00a74 0x0100000047984add

Log Entry 42324: 01/24/2008 08:23:30
Alert level 2: Informational
Keyword: MAIN_BP_LPM_GOOD
The main backplane is reporting the LPM status as good.
Reporting Entity: Management Processor located in cabinet 0
0x4b000ec600e00a75 0x0100000047984b02

Log Entry 42325: 01/24/2008 08:23:31
Alert level 2: Informational
Keyword: IO_BP_LPM_GOOD
The IO backplane is reporting the LPM status as good.
Reporting Entity: Management Processor located in cabinet 0
0x4b000ec900e00a76 0x0100000047984b03

Log Entry 42326: 01/24/2008 08:23:32
Alert level 2: Informational
Keyword: CELL_ON
The specified cell has been powered ON.
Reporting Entity: Management Processor located in cabinet 0
Physical Location: Cell board cabinet 0 slot 0
0x44800ee700e00a77 0x00ffffffff00ff68
0x4b000ee700e00a78 0x0100000047984b04

Log Entry 42327: 01/24/2008 08:23:32
Alert level 2: Informational
Keyword: CELL_POWER_GOOD
Power is good on cell board
Reporting Entity: Processor Dependent Hardware Controller located in cabinet 0, slot 0
0x4b000b5800e00a79 0x0100000047984b04

Log Entry 42328: 01/24/2008 08:23:32
Alert level 2: Informational
Keyword: IO_BP_LPM_GOOD
The IO backplane is reporting the LPM status as good.
Reporting Entity: Management Processor located in cabinet 0
0x4b000ec900e00a7a 0x0100000047984b04

Log Entry 42329: 01/24/2008 08:23:33
Alert level 2: Informational
Keyword: CELL_ON
The specified cell has been powered ON.
Reporting Entity: Management Processor located in cabinet 0
Physical Location: Cell board cabinet 0 slot 1
0x44800ee700e00a7b 0x00ffffffff01ff68
0x4b000ee700e00a7c 0x0100000047984b05

Log Entry 42330: 01/24/2008 08:23:33
Alert level 2: Informational
Keyword: CELL_POWER_GOOD
Power is good on cell board
Reporting Entity: Processor Dependent Hardware Controller located in cabinet 0, slot 1
0x4b000b5801e00a7d 0x0100000047984b05

Log Entry 42331: 01/24/2008 08:23:33
Alert level 2: Informational
Keyword: CELL_POWER_GOOD
Power is good on cell board
Reporting Entity: Processor Dependent Hardware Controller located in cabinet 0, slot 2
0x4b000b5802e00a7e 0x0100000047984b05

Log Entry 42332: 01/24/2008 08:23:33
Alert level 2: Informational
Keyword: CELL_ON
The specified cell has been powered ON.
Reporting Entity: Management Processor located in cabinet 0
Physical Location: Cell board cabinet 0 slot 2
0x44800ee700e00a7f 0x00ffffffff02ff68
0x4b000ee700e00a80 0x0100000047984b05

Log Entry 42333: 01/24/2008 08:23:34
Alert level 2: Informational
Keyword: CELL_ON
The specified cell has been powered ON.
Reporting Entity: Management Processor located in cabinet 0
Physical Location: Cell board cabinet 0 slot 3
0x44800ee700e00a81 0x00ffffffff03ff68
0x4b000ee700e00a82 0x0100000047984b06

Log Entry 42334: 01/24/2008 08:23:34
Alert level 2: Informational
Keyword: CELL_POWER_GOOD
Power is good on cell board
Reporting Entity: Processor Dependent Hardware Controller located in cabinet 0, slot 3
0x4b000b5803e00a83 0x0100000047984b06

Log Entry 42335: 01/24/2008 08:25:15
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING
There is at least one PDH event pending in the partition
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 0
Implementation Dependent: 0x0000000001000000
0x56800ef520e00a84 0x0000000001000000
0x4b000ef520e00a85 0x0100000047984b6b

Log Entry 42336: 01/24/2008 08:25:15
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING_ON_CELL
There is at least one pending PDH event on this cell
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 0
Physical Location: Cell board cabinet 0 cell 2
0x44800ef620e00a86 0x00ffff02ffffff94
0x4b000ef620e00a87 0x0100000047984b6b

Log Entry 42337: 01/24/2008 08:25:36
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING
There is at least one PDH event pending in the partition
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 0
Implementation Dependent: 0x0000000001000000
0x56800ef500e00a88 0x0000000001000000
0x4b000ef500e00a89 0x0100000047984b80

Log Entry 42338: 01/24/2008 08:25:36
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING_ON_CELL
There is at least one pending PDH event on this cell
Reporting Entity: System Firmware located in cabinet 0, slot 0, cpu 0
Physical Location: Cell board cabinet 0 cell 0
0x44800ef600e00a8a 0x00ffff00ffffff94
0x4b000ef600e00a8b 0x0100000047984b80

Log Entry 42339: 01/24/2008 08:25:37
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING
There is at least one PDH event pending in the partition
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 0
Implementation Dependent: 0x0000000001000000
0x56800ef510e00a8c 0x0000000001000000
0x4b000ef510e00a8d 0x0100000047984b81

Log Entry 42340: 01/24/2008 08:25:37
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING_ON_CELL
There is at least one pending PDH event on this cell
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 0
Physical Location: Cell board cabinet 0 cell 1
0x44800ef610e00a8e 0x00ffff01ffffff94
0x4b000ef610e00a8f 0x0100000047984b81

Log Entry 42341: 01/24/2008 08:27:57
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING
There is at least one PDH event pending in the partition
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 0
Implementation Dependent: 0x0000000001000000
0x56800ef510e00a90 0x0000000001000000
0x4b000ef510e00a91 0x0100000047984c0d

Log Entry 42342: 01/24/2008 08:27:57
Alert level 2: Informational
Keyword: BOOT_PDH_EVENTS_PENDING_ON_CELL
There is at least one pending PDH event on this cell
Reporting Entity: System Firmware located in cabinet 0, slot 1, cpu 0
Physical Location: Cell board cabinet 0 cell 1
0x44800ef610e00a92 0x00ffff01ffffff94
0x4b000ef610e00a93 0x0100000047984c0d

Log Entry 42343: 01/25/2008 00:00:05
Alert level 2: Informational
Keyword: MP_TIMESTAMP
MP timestamp event.
Reporting Entity: Management Processor located in cabinet 0
0x4b001a6600e00a94 0x0100000047992685

Log Entry 42344: 01/25/2008 00:44:30
Alert level 2: Informational
Keyword: MP_TIMESTAMP
MP timestamp event.
Reporting Entity: Management Processor located in cabinet 8
0x4b001a6608e00a95 0x01000000479930ee

Log Entry 42345: 01/25/2008 17:38:58
Alert level 2: Informational
Keyword: ERR_CPU_CHECK_SUMMARY
CPU API CpuProcessMachineCheck return value report
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 1
System Firmware Return Code: 0x2000000000000000
0x57800f7321e00a96 0x2000000000000000
0x4b000f7321e00a97 0x01000000479a1eb2

Log Entry 42346: 01/25/2008 17:38:58
Alert level 2: Informational
Keyword: ERR_CPU_CHECK_SUMMARY
CPU API CpuProcessMachineCheck return value report
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 4
System Firmware Return Code: 0x2000000000000000
0x57800f7324e00a98 0x2000000000000000
0x4b000f7324e00a99 0x01000000479a1eb2

Log Entry 42347: 01/25/2008 17:38:58
Alert level 2: Informational
Keyword: ERR_TOC_TASK
This chassis code identifies the type of TOC encountered
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 4
System Firmware Return Code: 0x0000000000000003
0x578003dd24e00a9a 0x0000000000000003
0x4b0003dd24e00a9b 0x01000000479a1eb2

Log Entry 42348: 01/25/2008 17:38:58
Alert level 2: Informational
Keyword: ERR_TOC_TASK
This chassis code identifies the type of TOC encountered
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 1
System Firmware Return Code: 0x0000000000000003
0x578003dd21e00a9c 0x0000000000000003
0x4b0003dd21e00a9d 0x01000000479a1eb2

Log Entry 42349: 01/25/2008 17:38:58
Alert level 2: Informational
Keyword: ERR_CPU_CHECK_SUMMARY
CPU API CpuProcessMachineCheck return value report
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 5
System Firmware Return Code: 0x2000000000000000
0x57800f7325e00a9e 0x2000000000000000
0x4b000f7325e00a9f 0x01000000479a1eb2

Log Entry 42350: 01/25/2008 17:38:59
Alert level 2: Informational
Keyword: ERR_TOC_TASK
This chassis code identifies the type of TOC encountered
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 5
System Firmware Return Code: 0x0000000000000003
0x578003dd25e00aa0 0x0000000000000003
0x4b0003dd25e00aa1 0x01000000479a1eb3

Log Entry 42351: 01/25/2008 17:40:56
Alert level 2: Informational
Keyword: BOOT_USER_INTERRUPTED
The user interrupted the boot by pressing a key during AutoBoot.
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 0
0x4b000a3020e00aa2 0x01000000479a1f28

Log Entry 42352: 01/25/2008 17:42:45
Alert level 2: Informational
Keyword: ERR_CPU_CHECK_SUMMARY
CPU API CpuProcessMachineCheck return value report
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 0
System Firmware Return Code: 0x2000000000000000
0x57800f7320e00aa3 0x2000000000000000
0x4b000f7320e00aa4 0x01000000479a1f95

Log Entry 42353: 01/25/2008 17:42:45
Alert level 2: Informational
Keyword: ERR_TOC_TASK
This chassis code identifies the type of TOC encountered
Reporting Entity: System Firmware located in cabinet 0, slot 2, cpu 0
System Firmware Return Code: 0x0000000000000000
0x578003dd20e00aa5 0x0000000000000000
0x4b0003dd20e00aa6 0x01000000479a1f95

Log Entry 42354: 01/26/2008 00:00:02
Alert level 2: Informational
Keyword: MP_TIMESTAMP
MP timestamp event.
Reporting Entity: Management Processor located in cabinet 0
0x4b001a6600e00aa7 0x01000000479a7802

Log Entry 42355: 01/26/2008 00:43:56
Alert level 2: Informational
Keyword: MP_TIMESTAMP
MP timestamp event.
Reporting Entity: Management Processor located in cabinet 8
0x4b001a6608e00aa8 0x01000000479a824c


Thanks & kind Regards

[Michael Steele_2]

Please verify that you're just trying to clear the ATTN light.

As for all of these ALERT LEVEL 2 errors, they can be ignored. Anything below 10 or 12 is non-urgent and informational.

As for just zeroing out these log messages, most admin's don't do this. Sometimes keeping the log history is an import clue to future problems. However, if you really want to zero out the log files, then you can reset all of the GSP parameters to there default level using this command:

GSP


stty +resetGSP < /dev/GSPdiag1

Run the following command on the command line to "reboot" the GSP (without rebooting the server):
When you run this command you will get a prompt on the console: "Press 'p' now
to clear all GSP passwords and users...". If you press "p" and then confirm it
(you only have a few seconds to respond), the GSP user/password info is wiped.
Generic login and password is either: Admin Admin or (blank
blank - in other words)