Installation guide

50 Book Title without trademarks, or an abbreviated book title • March 2008
Solaris Issues
SES vs. SD Paths for UTM LUNs
Bug 6500605 –For Solaris 10u4 and Solaris 8 and 9, the host cannot see the storage
device's management UTM LUN.
Workaround –Perform the following commands on the data host:
# setenv LD_LIBRARY_PATH /opt/SMgr/agent
# java -classpath /opt/SMgr/agent/SMagent.jar
devmgr.versioned.agent.DeviceIdentifier | grep "Volume
Access"
You should then receive output like the following, indicating which arrays have
access LUNs visible to the agent:
/dev/rdsk/c5t200600A0B82458D4d31s2 [Storage Array fms-lca1,
Volume
Access, LUN 31, Volume ID <600a0b80002458d20000000000000000>]
/dev/rdsk/c5t200700A0B82458D3d31s2 [Storage Array fms-lca1,
Volume
Access, LUN 31, Volume ID <600a0b80002fc0740000000000000000>]
UTM LUNs Controlled by “Solaris Traffic Manager”
Bug 6594360 –After you upgrade to S10U3 (or later), the in-band management UTM
LUN's are controlled by Solaris Traffic Manager (MPxIO). In most cases, in-band
management will not fail as a result of this; however, it is best practice to ensure that
the UTM LUN's are not controlled by MPxIO. Performing the following workaround
task will help prevent problems.
Workaround –Use the format inquire command to get the Vendor and Product
IDs. (The VID needs to be 8 characters.)
1. Edit the file /kernel/drv/scsi_vhci.conf
The following line should read:
device-type-scsi-options-list = "SUN Universal Xport",
"disable-option"; disable-option = 0x7000000
2. Run the stmsboot -u command.
Respond to the prompts as follows: