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.


A Solaris STMS Running Mechanism Defect Led to a Failure to Update the Disk Types of Newly Mapped LUNs

Publication Date:  2012-07-19 Views:  378 Downloads:  0
Issue Description

Product and version information:

  • S5500T V100R001 V100R002
  • S5600T V100R001 V100R002
  • S5800T V100R001 V100R002
  • S6800T V100R001 V100R002
  • Host operating system: Solaris10u3

When the STMS software was running on the Solaris host, changing the initiator multipathing mode on the storage array resulted in a failure to update disk types on the Solaris host. For example: Set the initiator's multipathing mode to ALUA and map a LUN to the host. Corresponding logical disks are generated on the Solaris host. Then set the initiator's multipathing mode to default. Scan for LUNs on the host. The logical disks generated by STMS are not updated to physical disks. Changing the initiator's multipathing mode from default to ALUA also resulted in the same problem.

Alarm Information
Handling Process
Delete the LUN mapping. Change the initiator's multipathing mode to a desired value and restart the host. Then map the LUN to the host again.
Root Cause
Solaris STMS cannot update disk path management modes promptly.

 1. In initial deployment, select a proper initiator multipathing mode before mapping any LUNs to hosts.
 2. Do not unnecessarily change initiator's multipathing mode on Solaris hosts. If it is absolutely necessary, restart the host after the changes.