User guide

126 Event Logs
Controller Port Event
Messages
Type [ID] Cause Action
A host has accessed a
Logical Drive <yy> for
the first time, or for the
first time following a
reset or LIP. It accessed
it through Host Loop
<xx> (ID <zz>) with the
SCSI command <check
condition, busy, or task
set full>.
Information
[0xB2E (2862)]
First access by a
particular host after a
LIP or reset.
A host has accessed a
Logical Drive <yy> for
the first time, or for the
first time following a
reset. ID <zz> accessed
it thru Host Channel
<nn> with the SCSI
command 0x<zz>.
No action necessary.
Host Loop <num> has
reported an error status
of 0x<xx> to a partic
-
ular command.
Error
[0xB37 (2871)]
This may indicate a
loop reset or LIP during
a command, or a loop
failure. Repeat Count =
<count>.
Contact technical
support.
Host Loop <num> has
reported an invalid
status of 0x<xx> to a
particular command.
Error
[0xB38 (2872)]
This indicates a
firmware error in the
host fibre channel chip.
Contact technical
support.
A SAS command was
aborted on the drive w/
WWN <xx xx xx xx xx
xx xx xx> (Slot <num>,
Enclosure <num>)
for the SCSI Op Code
0x<xx>.
Error
[0xB39 (2873)]
Aborted command. Possible reasons are:
faulty disk drive, faulty
drive slot, faultyenclo-
sure, cable issue, faulty
drive firmware, fault in
SAS expander, exces-
sive noise, or possible
drive interference.
The controller has
generated a LIP on Host
Loop <xx>, due to a
loop error.
Error
[0xB3D (2877)]
Controller initiated a
LIP.
No action necessary.
The host system
w/WWN:<xx xx xx xx
xx xx> and Loop ID of
<xx> has logged into
the controller through
Host Loop <xx>. These
events will only be
listed for HBAs with
SAN LUN Mappings.
Information
[0xB3F (2879)]
Host system logs into
the controller.
No action necessary.