Specifications

6-6 Sun StorEdge A1000 and A3x00/A3500FC Best Practices Guide November 2002
3f/00 targe operating conditions have changed
3f/01 microcode has been changed
3f/02 changed operating definition
3f/03 inquiry data has changed
6.2 LUNs Not Seen
There are many possible causes, but the usual scenario is after reconfiguration of the
system:
After upgrade of RAID Manager 6, see bug 4118532.
After upgrade of Solaris: usually sd.conf is lost causing LUNs above 8 are no
longer seen. This is described in the Sun StorEdge RAID Manager 6.22 Release
Notes.
With RAID Manager 6.22, upgrading to Solaris 8 requires patch no. 108553. If you
were running with patch no. 108334, it should be removed first.
Removing or adding HBA’s can cause some controllers not to be seen as described
in bug 4295322.
The creation of a LUN on the A3500FC in a multi-host environment requires a few
extra steps to ensure that the device is properly built on both hosts. When a LUN
is created with RAID Manager 6, the devices for RAID Manager and Solaris are
properly configured. However, RAID Manager 6 does not configure the devices
on the other host. You must configure the devices on the other host manually. See
bug 4336091 for further details.
Problems with adding greater than 8 LUN support can cause some or all the
LUNs not to be seen. FIN I0589-1 describes the proper way to increase the
number of LUNs, especially using the glm HBA (PCI SCSI). Note the
add16lun.sh script delivered on the RAID Manager 6.1.1u1 CD-ROM was
wrong and should not be used. See FIN I0589-1.
Having VERITAS Volume Manager 2.x installed and DMP enabled can cause loss
of access to LUNs when a failover occurs. This configuration is not supported
because its puts data at risk.
A related issue is loss of communication with the module rdac. rdac cuts off
communication when it can’t access a LUN when there is a good path in
/dev/osa for it. This can happen if LUN creation is terminated prematurely,
either by operator intervention (kill -9 or control-C), by system panic or
power failure. rdac_disks usually corrects this problem or a reconfiguration
reboot.
Adding 17 LUNs to a module connected by the FC-PCI HBA, which only
supports 16 LUNs will cause this loss of communication too, see bug 4304898.