Pillar Axiom: Hosts Using Qlogic Switches Lose Access to Axiom LUNs After a Slammer CU Warmstart

Asset ID:	1-72-1985037.1
Update Date:	2015-03-03
Keywords:

Solution Type Problem Resolution Sure

Solution 1985037.1 : Pillar Axiom: Hosts Using Qlogic Switches Lose Access to Axiom LUNs After a Slammer CU Warmstart

Applies to:

Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

After an Axiom software update, or some other event that causes a Slammer Control Unit (CU) warmstart, attached hosts lose complete access to the LUNs on the Axiom - when connected through Qlogic switches.

Cause

A Qlogic switch port configuration feature called IOStreamGuard is set to the default value of "Auto" for the ports that the Axiom is connected to. When the Slammer CU warmstarts, IOStreamGuard's "Auto" setting switches to "Enabled" which blocks the slammer CU host port RSCN (Request State Change Notification) from being propagated throughout the SAN.

Solution

Configure each Qlogic switch port that the Axiom is connected to, setting IOStreamGuard from the default setting of "Auto" (or "Enabled") to "Disabled".

Follow the steps below to configure IOStreamGuard for a port:

sanbox2-16port #> admin start
sanbox2-16port (admin) #> config edit
sanbox2-16port (admin-config) #> set config port 1
A list of attributes with formatting and current values will follow.
Enter a new value or simply press the ENTER key to accept the current value.
If you wish to terminate this process before reaching the end of the list
press 'q' or 'Q' and the ENTER key to do so.
Configuring Port Number: 1
------------------------
AdminState   (1=Online, 2=Offline, 3=Diagnostics,4=Down) [Online      ]
LinkSpeed    (1=1Gb/s, 2=2Gb/s, 3=Auto)                  [Auto        ]
PortType     (TL / GL / G / F / FL / Donor)              [GL          ]
TLPortMode   (1=TLTargetMode, 2=TLInitiatorMode)         [TLTargetMode]
ISLSecurity (Any / Ours / None)                         [Any         ]
SymPortName (string, max=32 chars)                      [Port1       ]
ALFairness   (True / False)                              [False       ]
ARB_FF       (True / False)                              [False       ]
InteropCredit(decimal value, 0-255)                      [0          ]
ExtCredit    (dec value increments of 11, non-loop only) [0           ]
FANEnable    (True / False)                              [True        ]
LCFEnable    (True / False)                              [False       ]
MFSEnable    (True / False)                              [True        ]
MFS_TOV      (decimal value, 10-20480 msec)              [10          ]
MSEnable     (True / False)                              [True        ]
NoClose      (True / False)                              [False       ]
IOStreamGuard(Auto / Enable / Disable)                   [Auto        ] Disable
VIEnable     (True / False)                              [False       ]
CheckAlps    (True / False)                              [False       ]
Finished configuring attributes.
This configuration must be saved (see config save command) and
activated (see config activate command) before it can take effect.
To discard this configuration use the config cancel command.
sanbox2-16port (admin-config) #>

Repeat this procedure to configure IOStreamGuard on every port that the Axiom is connected to. When all Axiom ports are configured, save and activate the configuration as follows:

sanbox2-16port (admin) #> config save
sanbox2-16port (admin) #> config activate

References

<BUG:20346844> - SLAMMER1, CU0 FAILED AND MISSING DUE TO "CRASH AT NANO_CLOCK LINE 193"
<BUG:20474400> - VMWARE HOSTS LOST CONNECTION TO AX600 AFTER UPGRADE TO 5.4.17

Attachments

This solution has no attachment