Machine Administration Guide 2.6 |
Contents
Index
![]() ![]() |
This Chapter contains information common to all models.
If the status of the monitored hardware changes, a message is displayed on the console and the GUI menu screen.*1 The information is also output to syslog. If the REMCS function is enabled, the information is reported to the REMCS Center.
Messages are in the format described below. The format is explained using the message requesting tape cleaning as an example.
*1 When System Management Console(SMC) is connected, the message is output to System Management Console.
In this case, the notification level is four. For information on the notification level, refer to the " System Console Software User's Guide".
Main unit identifier |
: |
The host name is displayed as the main unit identifier. |
Identifier |
: |
The machine administration identifier (FJSVmadm) is displayed. |
Notification level |
: |
The notification levels are shown in the following table. |
Notification level |
Definition |
---|---|
A |
Alarm A serious system failure has occurred. Take corrective action immediately. |
W |
Warning A system failure has occurred. Corrective action is required, but not urgent. |
I |
Information An event that does not fall under any of the categories of Alarm, Warning, or Panic has occurred. Take corrective action as required. |
P |
Panic A panic has occurred. Take corrective action immediately. |
Unit |
: |
The name of the part causing the message is displayed. |
Detector identifier |
: |
The detector of the failure is displayed. |
Identifier |
Definition |
---|---|
FJSVmadm |
Error detected by machine administration |
Kern |
Error detected by a kernel |
SCF_driver |
Error detected by the SCF driver |
FJSVcpupd |
Error detected by CPU patrol diagnosis. |
IO-related |
Error detected by a driver |
Firmware-related |
Error detected by firmware |
Message body |
: |
The message is displayed. |
Symbol |
Definition |
---|---|
MMM |
Month |
DD |
Day (1 - 31) |
hh |
Hour (00 - 23) |
mm |
Minute (00 - 59) |
ss |
Second (00 - 59) |
TZ |
Time zone |
Check the displayed message with the table "Explanation of messages and appropriate action."
"XXXX" in a message indicates the name of the unit where the status change occurred.
Check the unit name with the table "Part names and corresponding main units."
Once a message is output, repeated output of the same message is suppressed by default.
Messages are output to the System Management Console.
The part name designation used in messages is displayed separately by main unit.
Main unit |
Main unit model name |
---|---|
A |
PRIMEPOWER1 |
B |
PRIMEPOWER200/400/600, GP7000F model 200/200R/400/400R/400A/600/600R |
C |
PRIMEPOWER250/450 |
D |
PRIMEPOWER650/850 |
E |
PRIMEPOWER800/1000/2000, GP7000F model 1000/2000 |
F |
PRIMEPOWER900/1500/2500/HPC2500 |
Symbol |
Definition |
---|---|
n |
Unspecified alphanumeric character |
mm |
Hexadecimal number from 0 to F |
<component> |
Name of faulty component |
(*1) |
Applicable to main unit A only. |
(*2) |
Power supply in a PCI/Disk BOX. |
(*3) |
Applicable only when the CPU is SPARC64 V. |
(*4) |
Applicable to main unit D only. |
Error type |
Main unit A/B |
Main unit C |
Main unit E |
Main unit D/F |
---|---|---|---|---|
UPS |
UPS#n |
UPS#n |
None |
UPS#n(*4) |
Fan |
FAN#n |
FAN#n |
None |
Cabinet#n-FAN#n (*4) |
Power supply |
FEP#n |
DDC-A#n |
None |
Cabinet#n-FEP#n (*4) |
Error in system initialization |
0x-SLOTn |
None |
None |
CnS0n-SLOTn |
DTAG |
SB#n-DTAG#n |
DTAG#z |
None |
None |
Battery |
UPS-B#n |
UPS-B#n |
None |
UPS-B#n |
Memory |
SB#y-SLOTn |
SLOT#n |
Cabinet#n-SB#n- |
Cabinet#n-SB#n-SLOT#n |
CPU |
SB#n-CPU#n |
CPU#n |
None |
Cabinet#n-SB#n-CPU#n |
CPU cache |
SB#n-CPU#n |
CPU#n |
Cabinet#n-SB#n- |
Cabinet#n-SB#n-CPU#n |
Sbus |
SBus card, I/O board (*1) |
None |
None |
None |
PCI, Failure occurrence during I/O processing at the PCI |
AFAR mm |
<component> |
Cabinet#n-SB#n- |
Cabinet#n-SB#n-<component> Rack#n-PCIBOX#n-<component> |
Bus |
AFAR mm |
AFAR mm |
AFAR mm |
AFAR mm |
Disk |
SB#n-PCI#n-ID#n |
PCI#n-ID#nSCSI#n-ID#n |
PCI#n-ID#n |
Cabinet#n-SB#n-PCI#n-ID#n |
Tape unit |
SB#n-PCI#n-ID#n |
PCI#n-ID#n |
Cabinet#n-SB#n- |
Cabinet#n-SB#n-PCI#n-ID#n Rack#n-PCIBOX#n-PCI#n-ID#n Rack#n-PCI_DISKBOX#n-SCSI#n-ID#n |
PCI card |
SB#n-PCI#n |
PCI#n |
Cabinet#n-SB#n- |
Cabinet#n-SB#n-PCI#n Rack#n-PCIBOX#n-PCI#n |
TTY driver |
SB#n-ESCC(TTY) |
TTY-A |
Cabinet#n-SB#n- |
Cabinet#n-SB#n-ESCC (TTY) |
OS panic |
Part name by analogy with the panic that occurred (*1) |
None |
None |
Part name by analogy with the panic that occurred |
System-board-related |
None |
SB |
None |
Cabinet#n-SB#n(*4) |
RCI connection unit |
None |
rci-address |
None |
None |
Panel |
None |
PANEL |
None |
Cabinet#n-PANEL#n(*4) |
PCIBOX |
None |
None |
None |
Rack#n-PCIBOX#n |
Others |
None |
Part name detected/analyzed by the CPU (*3) |
None |
None |
Check the unit name with the table "Part names and corresponding main units."
Main unit |
Main unit model name |
---|---|
A |
PRIMEPOWER1 |
B |
PRIMEPOWER200/400/600, GP7000F model 200/200R/400/400R/400A/600/600R |
C |
PRIMEPOWER250/450 |
D |
PRIMEPOWER650/850 |
E |
PRIMEPOWER800/1000/2000, GP7000F model 1000/2000 |
F |
PRIMEPOWER900/1500/2500/HPC2500 |
Y : The unit displays this message.
N : The unit does not display this message.
The following shows the detector identifiers and the corresponding table title.
Detector identifier |
Table title |
---|---|
FJSVmadm |
|
Kern |
|
SCF_driver |
|
FJSVcpupd |
|
IO-related |
|
Firmware-related |
Explanation of messages and appropriate action (firmware-related) |
No |
Message (FJSVmadm) |
Explanation/Appropriate action |
Main unit |
|||||
---|---|---|---|---|---|---|---|---|
|
A |
B |
C |
D |
E |
F |
||
1 |
FJSVmadm:A:XXXX:FJSVmadm: |
The CPU has gone offline due to frequent CPU correctable errors. |
N |
N |
Y |
Y |
N |
Y |
2 |
FJSVmadm:I:XXXX: FJSVmadm: |
The CPU offline processing in response to frequent CPU correctable errors failed. <Caution> This message is not reported to the REMCS Center. |
N |
N |
Y |
Y |
N |
Y |
3 |
FJSVmadm:A:XXXX:FJSVmadm: |
An error occurred in XXXX. |
Y |
Y |
N |
Y |
N |
N |
4 |
FJSVmadm:A:XXXX:FJSVmadm: |
An error occurred in XXXX. |
Y |
Y |
Y |
Y |
N |
N |
5 |
FJSVmadm:A:XXXX:FJSVmadm: |
An error occurred in XXXX. |
Y |
Y |
Y |
Y |
N |
N |
6 |
FJSVmadm:A::FJSVmadm: |
An error occurred in XXXX. The unit that was defective when system initialization was attempted by the fjprtdiag or prtdiag command has been reported. |
Y |
Y |
N |
Y |
Y |
N |
7 |
FJSVmadm:A:XXXX:FJSVmadm: |
A DTAG 1-bit error was found in the SCF error log. |
Y |
Y |
N |
N |
N |
N |
8 |
FJSVmadm:W:XXXX:FJSVmadm: |
The battery of XXXX is nearing the end of its life. |
Y |
Y |
Y |
N |
N |
Y |
9 |
FJSVmadm:W:XXXX:FJSVmadm: |
The life of the battery for XXXX has been expired. |
Y |
Y |
Y |
N |
N |
Y |
10 |
FJSVmadm:W:XXXX:FJSVmadm: |
The expiration date of the life of the battery for XXXX has passed. |
Y |
Y |
Y |
N |
N |
Y |
11 |
FJSVmadm:W:XXXX:FJSVmadm: |
The power-on time of XXXX has reached 90% of its life. |
Y |
Y |
Y |
N |
N |
Y |
12 |
FJSVmadm:W:XXXX:FJSVmadm: |
The power-on time of XXXX has reached 100% of its life. |
Y |
Y |
Y |
N |
N |
Y |
13 |
FJSVmadm:A:XXXX:FJSVmadm: |
A memory 1-bit error message was found in the SCF error log. |
N |
N |
N |
Y |
N |
Y |
14 |
FJSVmadm:A::FJSVmadm: |
SCF error log, halt log, and watchdog log were detected. Contact a certified service engineer. |
N |
Y |
N |
N |
N |
N |
15 |
FJSVmadm:W:XXXX:FJSVmadm: |
Sense code (0x5d) indicating a predicted drive failure caused by a disk was returned. |
Y |
Y |
Y |
Y |
Y |
Y |
16 |
FJSVmadm:W:XXXX:FJSVmadm: |
Sense code (0x5d) indicating a predicted drive failure caused by a disk was returned. |
Y |
Y |
Y |
Y |
Y |
Y |
17 |
FJSVmadm:W:XXXX:FJSVmadm: |
XXXX requires head cleaning. |
Y |
Y |
Y |
Y |
Y |
Y |
18 |
FJSVmadm:W:XXXX:FJSVmadm: |
XXXX requires head cleaning. |
Y |
Y |
Y |
Y |
Y |
Y |
19 |
FJSVmadm:A::FJSVmadm: |
A thermal error message was found in the message log. |
Y |
Y |
N |
N |
N |
N |
20 |
FJSVmadm:A:XXXX:FJSVmadm: |
A YYYY unit failure was detected. |
N |
N |
N |
Y |
N |
N |
21 |
FJSVmadm:W:XXXX:FJSVmadm: |
A YYYY unit failure was detected. |
N |
N |
N |
Y |
N |
N |
22 |
FJSVmadm:W::FJSVmadm: |
The NFS mount failed for System Management Console (hostname= XXXXX). |
N |
N |
N |
N |
N |
Y |
No |
Message (Kern) |
Explanation/Appropriate action |
Main unit |
|||||||
---|---|---|---|---|---|---|---|---|---|---|
|
A |
B |
C |
D |
E |
F |
||||
1 |
FJSVmadm:A:XXXX:kern: |
An error occurred in XXXX. |
Y |
Y |
N |
N |
N |
N |
||
2 |
FJSVmadm:A:XXXX:kern: |
A hardware failure message associated with XXXX was found in the message log. |
Y |
Y |
N |
N |
N |
N |
||
3 |
FJSVmadm:A:XXXX:kern: |
A memory 1-bit error message was found in the message log. |
Y |
Y |
N |
Y |
Y |
Y |
||
4 |
FJSVmadm:A:XXXX:kern: |
A memory 1-bit error message was found in the message log. |
Y |
Y |
N |
Y |
Y |
Y |
||
5 |
FJSVmadm:A:XXXX:kern: |
A secondary cache 1-bit error message was found in the message log. |
Y |
Y |
N |
N |
Y |
N |
||
6 |
FJSVmadm:A:XXXX:kern: |
A secondary cache 1-bit error message was found in the message log. |
Y |
Y |
N |
N |
Y |
N |
||
7 |
FJSVmadm:A:XXXX:kern: |
Degradation of cache/TLB has occurred. |
Y |
Y |
Y |
Y |
Y |
Y |
||
8 |
FJSVmadm:A:XXXX:kern:CPU offline |
A CPU offline message caused by frequent secondary cache 1-bit errors on the CPU was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
9 |
FJSVmadm:A:XXXX:kern: |
A CPU offline message caused by frequent secondary cache 1-bit errors on the CPU was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
10 |
FJSVmadm:A:XXXX:kern: |
A CPU urgent error message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
11 |
FJSVmadm:A:XXXX:kern: |
An Sbus error message was found in the message log. |
N |
N |
N |
N |
Y |
N |
||
12 |
FJSVmadm:A:XXXX:kern: |
A PCI data parity error message was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
||
13 |
FJSVmadm:A:XXXX:kern: |
An PCI bus error message was found in the message log. |
N |
N |
Y |
Y |
Y |
Y |
||
14 |
FJSVmadm:A:XXXX:kern: |
An PCI bus error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
15 |
FJSVmadm:A:XXXX:kern: |
An PCI bus error message was found in the message log. |
N |
N |
Y |
Y |
Y |
Y |
||
16 |
FJSVmadm:A:XXXX:kern: |
An PCI bus error message was found in the message log. |
N |
N |
Y |
Y |
Y |
Y |
||
17 |
FJSVmadm:A:XXXX:kern: |
An PCI bus error message was found in the message log. |
N |
N |
Y |
Y |
Y |
Y |
||
18 |
FJSVmadm:A:XXXX:kern: |
An PCI bus error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
19 |
FJSVmadm:A:XXXX:kern: |
A message stating that a PCI bus is detached was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
||
20 |
FJSVmadm:A:XXXX:kern: |
A PCI error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
21 |
FJSVmadm:A:XXXX:kern: |
A PCI slot power-on error message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
22 |
FJSVmadm:A:XXXX:kern: |
A PCI slot power-off error message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
23 |
FJSVmadm:A:XXXX:kern: |
An UPA bus error message was found in the message log. |
Y |
Y |
N |
Y |
Y |
Y |
||
24 |
FJSVmadm:A:XXXX:kern: |
An UPA bus error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
25 |
FJSVmadm:A:XXXX:kern: |
An UPA bus error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
26 |
FJSVmadm:A:XXXX:kern: |
A UPA bus error message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
27 |
FJSVmadm:A:XXXX:kern:UPA |
A UPA bus timeout message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
28 |
FJSVmadm:A:XXXX:kern:Bus error |
A bus error message was found in the message log. |
Y |
Y |
N |
Y |
Y |
Y |
||
29 |
FJSVmadm:P:XXXX:kern:Panic |
A panic message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
N |
||
30 |
FJSVmadm:I:XXXX:kern:Panic |
A panic message was found in the message log. |
N |
N |
Y |
N |
N |
N |
||
31 |
FJSVmadm:A:XXXX:kern:Occurred |
A BAD TRAP message was found in the message log. |
N |
N |
N |
N |
N |
N |
||
32 |
FJSVmadm:A:XXXX:kern:Detected abnormal temperature |
A thermal error message was found in the message log. |
N |
N |
N |
N |
N |
N |
||
33 |
FJSVmadm:A:XXXX:kern:"Message" |
A hardware failure message associated with XXXX was found in the message log. |
Y |
Y |
N |
N |
N |
N |
||
34 |
FJSVmadm:A:XXXX:kern:TLB |
A TLB multiple hit error message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
35 |
FJSVmadm:A:XXXX:kern:TLB |
A TLB parity error message was found in the message log. |
N |
N |
Y |
Y |
N |
Y |
||
36 |
FJSVmadm:A:XXXX:kern: |
A correctable error of XXXX was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
37 |
FJSVmadm:A:XXXX:kern: |
A message about a correctable memory error was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
38 |
FJSVmadm:A:XXXX:kern: |
A CPU uncorrectable error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
39 |
FJSVmadm:A:XXXX:kern: |
A CPU uncorrectable error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
40 |
FJSVmadm:A:XXXX:kern: |
A message about an uncorrectable memory error was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
41 |
FJSVmadm:A:XXXX:kern: |
A CPU FPU error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
||
42 |
FJSVmadm:A:X:kern:FMA message is detected (SUNW-MSG-ID: YYYY) |
An FMA message was detected in the message log.Contact a certified service engineer. |
N |
N |
N |
N |
N |
N |
No |
Message (SCF_driver) |
Explanation/Appropriate action |
Main unit |
|||||
---|---|---|---|---|---|---|---|---|
|
A |
B |
C |
D |
E |
F |
||
1 |
FJSVmadm:A:SB:scf_driver: |
Ebus timeout has occurred. |
N |
N |
Y |
N |
N |
N |
2 |
FJSVmadm:A:SCF:scf_driver: |
An IOCHRDY timeout (Ebus2 T.O) message was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
3 |
FJSVmadm:A:SCF:scf_driver: |
A host bus error message of Ebus2 DMA was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
4 |
FJSVmadm:A:SB:scf_driver: |
The SCF command has returned abnormally. |
N |
N |
Y |
N |
N |
N |
5 |
FJSVmadm:A:SB:scf_driver: |
All the SCF devices have stopped. |
N |
N |
Y |
N |
N |
N |
6 |
FJSVmadm:A:SCF:scf_driver: |
A sumcheck error message was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
7 |
FJSVmadm:A:SB:scf_driver: |
A sumcheck error was detected in the received data of the SCF command. |
N |
N |
Y |
N |
N |
N |
8 |
FJSVmadm:A:SB:scf_driver: |
A parity error occurred during the register read operation. |
N |
N |
Y |
N |
N |
N |
9 |
FJSVmadm:A:RCI_address: |
An RCI device was notified of sense information that is not supported or defined by the SCF driver. Contact a certified service engineer. |
N |
N |
Y |
N |
N |
N |
10 |
FJSVmadm:A:SCF:scf_driver: |
A command timeout message was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
11 |
FJSVmadm:A:SCF:scf_driver: |
An offline message was found in the message log. |
N |
N |
N |
Y |
Y |
Y |
No |
Message (FJSVcpupd) |
Explanation/Appropriate action |
Main unit |
|||||
---|---|---|---|---|---|---|---|---|
|
A |
B |
C |
D |
E |
F |
||
1 |
FJSVmadm:A:XXXX:FJSVcpupd |
A CPU error was detected by CPU patrol diagnosis. |
N |
Y |
N |
Y |
Y |
Y |
No |
Message (IO-related) |
Explanation/Appropriate action |
Main unit |
|||||
---|---|---|---|---|---|---|---|---|
|
A |
B |
C |
D |
E |
F |
||
1 |
FJSVmadm:A:XXXX:sd: |
A message stating that the read (or write) command ended abnormally and a retry failed was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
2 |
FJSVmadm:A:XXXX:sd: |
A message stating that the read (or write) command ended abnormally and a retry failed was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
3 |
FJSVmadm:A:XXXX:sd: |
A SCSI transfer error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
4 |
FJSVmadm:A:XXXX:sd: |
A SCSI transfer error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
5 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
6 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
7 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
8 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
9 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
10 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
11 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
12 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
13 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
14 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
15 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
16 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
17 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
18 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
19 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
20 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
21 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
22 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
23 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
24 |
FJSVmadm:A:XXXX:sd: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
25 |
FJSVmadm:A:XXXX:sd: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
26 |
FJSVmadm:A:XXXX:sd: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
27 |
FJSVmadm:A:XXXX:sd: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
28 |
FJSVmadm:A:XXXX:sd: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
29 |
FJSVmadm:A:XXXX:sd: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
30 |
FJSVmadm:A:XXXX:sd: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
31 |
FJSVmadm:A:XXXX:sd: |
Access to an I/O device failed. |
Y |
Y |
Y |
Y |
Y |
Y |
32 |
FJSVmadm:A:XXXX:sd: |
Access to an I/O device failed. |
Y |
Y |
Y |
Y |
Y |
Y |
33 |
FJSVmadm:A:XXXX:sd: |
A nonresponse message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
34 |
FJSVmadm:A:XXXX:sd: |
A nonresponse message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
35 |
FJSVmadm:A:XXXX:sd: |
A transfer error message was found in the message log. |
N |
N |
N |
Y |
N |
Y |
36 |
FJSVmadm:A:XXXX:sd: |
A transfer error message was found in the message log. |
N |
N |
N |
Y |
N |
Y |
37 |
FJSVmadm:A:XXXX:ssd: |
A message stating that the read (or write) command ended abnormally and a retry failed was found in the message log. |
N |
N |
N |
N |
N |
N |
38 |
FJSVmadm:A:XXXX:ssd: |
A message stating that the read (or write) command ended abnormally and a retry failed was found in the message log. |
N |
N |
N |
N |
N |
N |
39 |
FJSVmadm:A:XXXX:ssd: |
A SCSI transfer error message was found in the message log. |
N |
N |
N |
N |
N |
N |
40 |
FJSVmadm:A:XXXX:ssd: |
A SCSI transfer error message was found in the message log. |
N |
N |
N |
N |
N |
N |
41 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
42 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
43 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
44 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
45 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
46 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
47 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
48 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
49 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
50 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
51 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
52 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
53 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
54 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
55 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
56 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
57 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
58 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
59 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
60 |
FJSVmadm:A:XXXX:ssd: |
A device error message was found in the message log. |
N |
N |
N |
N |
N |
N |
61 |
FJSVmadm:A:XXXX:ssd: |
A nonresponse message was found in the message log. |
N |
N |
N |
N |
N |
N |
62 |
FJSVmadm:A:XXXX:ssd: |
A nonresponse message was found in the message log. |
N |
N |
N |
N |
N |
N |
63 |
FJSVmadm:A:XXXX:ssd: |
A transfer error message was found in the message log. |
N |
N |
N |
N |
N |
N |
64 |
FJSVmadm:A:XXXX:ssd: |
A transfer error message was found in the message log. |
N |
N |
N |
N |
N |
N |
65 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
66 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
67 |
FJSVmadm:A:XXXX:hddv: |
A read/write command error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
68 |
FJSVmadm:A:XXXX:hddv: |
A read/write command error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
69 |
FJSVmadm:A:XXXX:hddv: |
A SCSI transfer error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
70 |
FJSVmadm:A:XXXX:hddv: |
A SCSI transfer error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
71 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
72 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
73 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
74 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
75 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
76 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
77 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
78 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
79 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
80 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
81 |
JFSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
82 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
83 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
84 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
85 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
86 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
87 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
88 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
89 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
90 |
FJSVmadm:A:XXXX:hddv: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
91 |
FJSVmadm:A:XXXX:hddv: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
92 |
FJSVmadm:A:XXXX:hddv: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
93 |
FJSVmadm:A:XXXX:hddv: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
94 |
FJSVmadm:A:XXXX:hddv: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
95 |
FJSVmadm:A:XXXX:hddv: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
96 |
FJSVmadm:A:XXXX:hddv: |
An I/O device failure was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
97 |
FJSVmadm:A:XXXX:hddv: |
Access to the disk array unit failed. |
Y |
Y |
Y |
Y |
Y |
Y |
98 |
FJSVmadm:A:XXXX:hddv: |
Access to the disk array unit failed. |
Y |
Y |
Y |
Y |
Y |
Y |
99 |
FJSVmadm:A:XXXX:hddv: |
A nonresponse message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
100 |
FJSVmadm:A:XXXX:hddv: |
A nonresponse message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
101 |
FJSVmadm:A:XXXX:st: |
A SCSI transfer error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
102 |
FJSVmadm:A:XXXX:st: |
A SCSI transfer error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
103 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
104 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
105 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
106 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. Check the statuses of the SCSI cable, SCSI unit, and SCSI adapter. |
Y |
Y |
Y |
Y |
Y |
Y |
107 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
108 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
109 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
110 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
111 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
112 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
113 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
114 |
FJSVmadm:A:XXXX:st: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
115 |
FJSVmadm:A:XXXX:glm: |
An XXXX offline message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
116 |
FJSVmadm:A:XXXX:isp: |
An XXXX adapter offline message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
117 |
FJSVmadm:A:XXXX:isp: |
A hardware failure message associated with XXXX was found in the message log. |
N |
N |
N |
Y |
N |
Y |
118 |
FJSVmadm:A:XXXX:fcpfcd: |
A cipher processor card error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
119 |
FJSVmadm:A:XXXX:fcpfcd: |
A cipher processor card error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
120 |
FJSVmadm:A:XXXX:MPHD: |
A disk path error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
121 |
FJSVmadm:A:XXXX:MPHD: |
A disk path error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
122 |
FJSVmadm:A:XXXX:MPHD: |
A redundant path was used but access to the disk array unit failed. |
Y |
Y |
Y |
Y |
Y |
Y |
123 |
FJSVmadm:A:XXXX:MPHD: |
A SCSI transfer error was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
124 |
FJSVmadm:A:XXXX:MPHD: |
A SCSI transfer error was detected. |
Y |
Y |
Y |
Y |
Y |
Y |
125 |
FJSVmadm:A:XXXX:fjpfca: |
An adapter hard error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
126 |
FJSVmadm:A:XXXX:fjpfca: |
A PCI error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
127 |
FJSVmadm:A:XXXX:fjpfca: |
An adapter error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
128 |
FJSVmadm:A:XXXX:fjpfca: |
A device error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
129 |
FJSVmadm:A:XXXX:sf: |
A transfer error message was found in the message log. |
N |
N |
N |
Y |
N |
Y |
130 |
FJSVmadm:A:XXXX:soc: |
An XXXX offline message was found in the message log. |
N |
N |
N |
N |
N |
N |
131 |
FJSVmadm:A:XXXX:hme: |
An offline message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
132 |
FJSVmadm:A:XXXX:se: |
An offline message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
133 |
FJSVmadm:A:XXXX:wpcd: |
An adapter hard error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
134 |
FJSVmadm:A:XXXX:sfdsk: |
A SynfinityDISK error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
135 |
FJSVmadm:A:XXXX:sfdsk: |
A SynfinityDISK error message was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
136 |
FJSVmadm:A:XXXX:nf: |
An adapter hard error message was found in the message log. |
N |
N |
N |
N |
N |
N |
137 |
FJSVmadm:A:TimerUnit: |
The timer unit connected to host_name failed. A timer unit error message was found in the message log. |
Y |
Y |
Y |
Y |
N |
N |
138 |
FJSVmadm:X:XXXX:XXXX |
A message associated with additional monitoring was found in the message log. |
Y |
Y |
Y |
Y |
Y |
Y |
No |
Message (firmware-related) |
Explanation/Appropriate action |
Main unit |
|||||
---|---|---|---|---|---|---|---|---|
|
A |
B |
C |
D |
E |
F |
||
1 |
FJSVmadm:X:XXXX:Firm: |
A system board error was found. |
N |
N |
Y |
N |
N |
N |
2 |
FJSVmadm:X:XXXX:SCF: |
A fan error was found. |
N |
N |
Y |
N |
N |
N |
3 |
FJSVmadm:X:XXXX:SCF: |
A power error was found. |
N |
N |
Y |
N |
N |
N |
4 |
FJSVmadm:X:XXXX:Firm: |
A CPU error was found. |
N |
N |
Y |
N |
N |
N |
5 |
FJSVmadm:X:XXXX:Firm: |
A secondary cache 1-bit error was found. |
N |
N |
Y |
N |
N |
N |
6 |
FJSVmadm:X:XXXX:SCF: |
An RCI node error was found. |
N |
N |
Y |
N |
N |
N |
7 |
FJSVmadm:X:XXXX:SCF: |
A panel error was found. |
N |
N |
Y |
N |
N |
N |
8 |
FJSVmadm:X:XXXX:Firm: |
A PCI card error was found. |
N |
N |
Y |
N |
N |
N |
9 |
FJSVmadm:X:XXXX:SCF: |
A UPS error was found. |
N |
N |
Y |
N |
N |
N |
10 |
FJSVmadm:X:XXXX:Firm: |
A memory error was found. |
N |
N |
Y |
N |
N |
N |
11 |
FJSVmadm:X:XXXX:Firm: |
A memory bit error was found. |
N |
N |
Y |
N |
N |
N |
12 |
FJSVmadm:I:XXXX:Firm: |
A message was reported. |
N |
N |
Y |
N |
N |
N |
13 |
FJSVmadm:X:XXXX:SCF: |
An environment error was found. |
N |
N |
Y |
N |
N |
N |
14 |
FJSVmadm:X:XXXX:Firm: |
A DTAG1 bit error was found. |
N |
N |
Y |
N |
N |
N |
15 |
FJSVmadm:X:XXXX:Firm: |
A hardware configuration error occurred. |
N |
N |
Y |
N |
N |
N |
16 |
FJSVmadm:X:XXXX:Firm: |
Cache/TLB has been degraded. |
N |
N |
Y |
N |
N |
N |
17 |
FJSVmadm:X:XXXX:Firm: |
A hardware error occurred. |
N |
N |
Y |
N |
N |
N |
18 |
FJSVmadm:X:XXXX:Firm: |
Status reset failed due to recurring part failures. |
N |
N |
Y |
N |
N |
N |
19 |
FJSVmadm:X:TEST:Firm: |
A test error log is reported. |
N |
N |
Y |
N |
N |
N |
20 |
FJSVmadm:A:XXXX:SCF: |
Setting data held in SCF has been lost. |
N |
N |
N |
Y |
N |
N |
21 |
FJSVmadm:A:XXXX:POST: |
A single-bit E-cache error was detected. |
N |
N |
N |
Y |
N |
N |
22 |
FJSVmadm:A:XXXX:POST: |
A single-bit U2U error was detected. |
N |
N |
N |
Y |
N |
N |
23 |
FJSVmadm:A:XXXX:POST: |
The TOD battery power is low. |
N |
N |
N |
Y |
N |
N |
24 |
FJSVmadm:A:XXXX:POST: |
A single-bit E-cache error was detected. |
N |
N |
N |
Y |
N |
N |
25 |
FJSVmadm:A:XXXX:POST: |
A single-bit memory error was detected. |
N |
N |
N |
Y |
N |
N |
26 |
FJSVmadm:A:XXXX:POST: |
A single-bit UPA error was detected. |
N |
N |
N |
Y |
N |
N |
27 |
FJSVmadm:A:XXXX:OBP: |
An abnormal CPU reset trap occurred. |
N |
N |
N |
Y |
N |
N |
28 |
FJSVmadm:A:XXXX:OBP: |
An abnormal CPU reset trap occurred. |
N |
N |
N |
Y |
N |
N |
29 |
FJSVmadm:A:XXXX:OBP: |
Though the OS encountered a panic, the panic was not handled. |
N |
N |
N |
Y |
N |
N |
* One of Firm:SCF/POST/OBP is displayed.
Contents
Index
![]() ![]() |