No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


[T Series]A LUN Scan Mechanism Defect on Solaris8/9 Hosts Led to a Failure to Detect LUNs in Initial Configuration

Publication Date:  2012-07-19 Views:  275 Downloads:  0
Issue Description
Product and version information:
S5500T V100R001 V100R002
S5600T V100R001 V100R002
S5800T V100R001 V100R002
S6800T V100R001 V100R002


1.The host and the storage array were properly connected through two redundant physical links. A initiator was properly added to the storage array.

2.Map a LUN to the host.

3.Run the format command to scan for LUNs. The command failed to detect any LUNs.

4.This problem existed in any of the following situations: single or double paths, direct or switch connection.

Application server operating system: Solaris 8 2/04 s28s_hw4wos_05a SPARC
Alarm Information
Handling Process

To handle the problem, perform the following steps:

1.Remove and reinsert the cable that connects the storage array and the host.
2.Run the format command on the host to scan for LUNs again. If any mapped LUNs are displayed and the quantity is correct, the scan LUN function is normal. For example, the following shows the output after a LUN is mapped from the S6800T to the host.

bash-2.03# format
Searching for disks...done

c3t54132391003732325413239100373232d0: configured with capacity of 20.00GB

       0. c0t0d0
       1. c0t1d0
       2. c3t54132391003732325413239100373232d0 /scsi_vhci/ssd@g54132391003732325413239100373232
Specify disk (enter its number):

Root Cause

1.Check that the host operating system is Solaris8 or Solaris9. We ran the cat /etc/release command on the host. The following shows the output:

bash-3.00# cat /etc/release
                      Solaris 10 10/09 s10s_u8wos_08a SPARC
           Copyright 2009 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 16 September 2009

The output indicated that the host was running Solaris 10 u8.

2.A Solaris8/9 host may fail to detect LUNs. A Solaris8/9 host sent a scan LUN command to the storage array as soon as the link between them was set up. Since no LUN mapping was added, the storage array returned no mapping, and the LUN list was vacant. No LUN list information was displayed on the host. Any operation then failed to send a scan LUN command to the storage array, and the host failed to detect any mapped LUNs.


1.A Solaris8/9 host sends the REPORT LUNS command to the storage array as soon as the link between them is set up. If no LUN mapping is added, the storage array returns no mapping, and the LUN list is vacant.
2.No LUN list information is displayed on the host. Any operation then fails to send a scan LUN command to the storage array, and the host fails to detect any mapped LUNs. You need to set up a link again before you can detect any LUNs on the host.
3.A Solaris10 host has no such problems.