Bytes 8 Through 11 Failure Reasons And Actions - IBM TotalStorage SAN32M1 Installation And Service Manual

• Reroute Fibre Channel traffic by moving device connections to a
less-congested region of the fabric.
Did the corrective action solve the problem and relieve the reported
low BB_Credit condition?
NO YES
↓
The ISL appears operational. Exit MAP.
Contact the next level of support. Exit MAP.
25
A 150 event code indicates a zone merge process failed during ISL
initialization. Either an incompatible zone set was detected or a
problem occurred during delivery of a zone merge frame. This event
code always precedes a 070 event code, and represents the reply of
an adjacent fabric element in response to a zone merge frame.
Obtain supplementary event data for each 150 event code.
a. At the Hardware View, click Logs and select Event Log. The
Event Log displays.
b. Examine the first 12 bytes (0 through 11) of event data.
c. Bytes 0 through 3 specify the E_Port number (00 through 23)
reporting the problem. Bytes 8 through 11 specify the failure
reason as specified in

Bytes 8 through 11 failure reasons and actions

Table 13
Bytes 8 - 11 Failure Reason
01 Invalid data length.
08 Invalid zone set format.
09 Invalid data.
0A Cannot merge.
F0 Retry limit reached.
F1 Invalid response length.
F2 Invalid response code.
Table 13 on page 295.
Chapter 3: Diagnostics
Action
Go to step 26.
Go to step 26.
Go to step 27.
Go to step 27.
Go to step 26.
Go to step 26.
Go to step 26.
295