Sun Storage 3910 Array
 

GCS>Sun Microsystems>Sun Alert>Criteria Category>Availability
 
GCS>Sun Microsystems>Sun Alert>Release Phase>Resolved
 

Brocade SilkWorm switches running certain Fabric Operating Systems (FabOS) versions may experience a loss of access to storage via one or more paths.

This issue can occur on the following platforms:

• Brocade SilkWorm switches running FabOS prior to 4.4.0b without patch 115361-06

Note: This issue only occurs on Brocade Silkworm switches running FabOS prior to 4.4.0b, following a "link event" (online/offline/online transition or array/switch reconfiguration) requiring the host to issue a port login (PLOGI) to the storage device.

On hosts running Sun "fp" and "MPxIO" drivers, "PLOGI timeout" messages and host messages from STMS will report that LUNs are being offlined, and that the paths allowing access to those LUNs are now degraded due to the loss of one (or more) path(s). These messages will be displayed in the array syslog, similar to the following example:

    Jan 24 11:34:27 [date time hostname] fp: [ID 517869 kern.info] NOTICE: fp(1):
PLOGI to 21200 failed state=Timeout, reason=Hardware Error
Jan 24 11:34:27 [date time hostname] scsi: [ID 243001 kern.warning] WARNING:
/sbus@54,0/SUNW,qlc@1,30400/fp@0,0 (fcp1):
Jan 24 11:34:27 [date time hostname]   PLOGI to D_ID=0x21200 failed:
State:Timeout, Reason:Hardware Error. Giving up
Jan 24 11:36:11 [date time hostname] fp: [ID 517869 kern.info] NOTICE: fp(1):
PLOGI to 21200 failed state=Timeout, reason=Hardware Error
Jan 24 11:36:11 [date time hostname] scsi: [ID 243001 kern.warning] WARNING:
/sbus@54,0/SUNW,qlc@1,30400/fp@0,0 (fcp1):
Jan 24 11:36:11 [date time hostname]   PLOGI to D_ID=0x21200 failed:
State:Timeout, Reason:Hardware Error. Giving up
Jan 24 11:36:31 [date time hostname] scsi: [ID 243001 kern.info]
/sbus@54,0/SUNW,qlc@1,30400/fp@0,0 (fcp1):
Jan 24 11:36:31 [date time hostname]   offlining lun=1 (trace=0), target=21200
(trace=2800101)
Jan 24 11:36:31 [date time hostname] mpxio: [ID 779286 kern.info]
/scsi_vhci/ssd@g60020f20000097ab41b6d08700036e53 (ssd33) multipath status:
degraded, path /sbus@54,0/SUNW,qlc@1,30400/fp@0,0 (fp1) to target address:
50020f23000097ab,1 is offline

The above are examples only. On each system, the LUN numbers, target numbers, and device paths will vary. To identify that this issue is being seen, check the target trace value ("trace=2800101" above) , that the PLOGI failure state was "timeout", and check the overall sequence of events.

Note: It is important to differentiate configuration issues that will not allow port login (causing PLOGI errors), against instances where hosts should be able to PLOGI to SAN storage that they have previously used. Certain HBA drivers will not allow port login (PLOGI) from another host, generating misleading PLOGI errors. Certain storage arrays (i.e. SE99x0) that have no configured LUNs available to the host in question, will not allow port login (PLOGI), thereby generating misleading PLOGI errors.

Should the described issue occur, wait for any LUN failovers to complete (if applicable) and proceed with the following recommendations:

On the hosts(s) where the above STMS "offlining lun" and "multipath status: degraded" messages were seen immediately following the "PLOGI" timeout to that device, run the luxadm(1M) command as "root" to the identified World-Wide-Number (WWN). In the example shown above in "Symptoms", the error occurred to the storage device with a WWN of 50020f23000097ab, so the command to run would be :

     # luxadm -e forcelip 50020f23000097ab

Following the above luxadm(1M) command, check for storage connectivity via the same path displayed:

    # luxadm display 50020f23000097ab

This should show the path to storage being either ONLINE or STANDBY.

If the path being shown is neither ONLINE or STANDBY, and the "luxadm -e forecelip <WWN>" resulted in additional PLOGI errors being recorded, then the attempted recovery has not worked and recovery will require the rebooting of the switch itself. This action will potentially affect the connectivity of other hosts to the storage, so it is imperative to ensure that the issue is not due to incorrect configuration (SAN zoning or LUN mapping) and that any other host on this switch has an alternative path to the storage prior to resetting the affected switch.

This issue is addressed on the following platforms:

• Brocade SilkWorm switches running FabOS 4.4.0b or later (as delivered in patch 115361-06 or later)

Note: The appropriateness of any switch FW version for host and storage connectivity should be investigated prior to installation.

References

References

This solution has no attachment