| SRDB ID | Synopsis | Date | ||
| 43202 | Why can't I see newly mapped LUNs on a Sun StorEdge[TM] 9900 series array? | 27 Feb 2002 |
| Status | Issued |
| Description |
After new LUNs are mapped from a StorEdge 9910 or 9960 from the SVP or Remote Console, the Solaris[TM] Operating Environment host does not recognize the new devices, even after editing sd.conf.
SOLUTION SUMMARY:
When LUNs are mapped on the StorEdge 9910 or 9960, LUN assignments are done by associating a LUN number with a particular LDEV ID. The LUN number that is assigned by the subsystem is hex. The sd driver in Solaris however identifies LUNs by their decimal address - LUN definitions in hex will be ignored. Therefore, any LUN number above 09 needs to be translated to hex in order to be correctly identified by the sd driver in /kernel/drv/sd.conf.
For example:
/devices/pci@1,4000/fibre-channel@4/sd@4,a
would translate to the following sd.conf entry:
name="sd" class="scsi" target=4 lun=10
Please note that a reconfiguration boot is required to make any changes in /kernel/drv/sd.conf effective.
INTERNAL SUMMARY:
SUBMITTER: George Bolduc APPLIES TO: Hardware/Disk Storage Subsystem/StorEdge Disk Array/StorEdge 9900 ATTACHMENTS: