Fabric Merge Failure Reasons And Actions - IBM TotalStorage SAN140M Installation And Service Manual

No action is required for an isolated event or if the reporting ISL
approaches 100% throughput. If the event persists, perform one of the
following:
• Relieve the congestion by adding parallel ISLs between the
fabric elements reporting the problem.
• Increase the ISL link speed between the fabric elements
reporting the problem (from 1 Gbps to 2 Gbps, or 10 Gbps( with
XPM card installed).
• Reroute Fibre Channel traffic by moving device connections to a
less-congested region of the fabric.
Was the maintenance action successful?
NO YES
↓
The fabric, ISL, and product are operational. Exit MAP.
Contact the next level of support. Exit MAP.
22
Event code 150 indicates a fabric merge process failed during ISL
initialization. An incompatible zone set was detected or a problem
occurred during delivery of a zone merge frame. This event code
always precedes event code 070, and represents the reply of an
adjacent fabric element in response to a zone merge frame. Obtain
supplementary event data as follows:
a. At the Event Log, examine the first 12 bytes (0 through 11) of
event data.
b. Bytes 0 specifies the E_Port reporting the problem. Bytes 8
through 11 specify the failure reason as listed in

Fabric merge failure reasons and actions

Table 21
Bytes 8 - 11 Merge failure reason
01 Invalid data length.
08 Invalid zone set format.
09 Invalid data.
0A Cannot merge.
Chapter 3: Maintenance analysis procedures (MAPS)
Table 21.
Action
Go to step 23.
Go to step 23.
Go to step 24.
Go to step 24.
151