Silicon Graphics InfiniteStorage 4000 Series User Manual page 73

Question
Why might the rdriver fail to attach
and what can I do about it?
How can I determine whether the
resolution daemon is working?
How do I find which failover module
manages a volume in Solaris 11?
Chapter 5: Failover Drivers for the Solaris Operating System
The rdriver might not attach when no entry exists in the
rdriver.conf file to match the device, or whether rdnexus runs
out of buses.
If no physical devnode exists, then the following actions must occur:
The sd.conf file must specify LUNs explicitly.
The ssd.conf file with the itmpt HBA must specify LUNs
explicitly.
With Sun driver stacks, underlying HBA drivers dynamically
create devnodes for ssd.
You must restart the system with the reconfigure option after you
update the rdriver.conf file.
In the Solaris 9 OS, you can use the update_drv command
whether the HBA driver supports it.
Type this command, and press Enter:
ps -ef | grep rd
Check the host log messages for the volume. Storage arrays with
Asymmetric Logical Unit Access (ALUA) are managed by the
lsi_tpgs module. Storage arrays with earlier version of firmware
are managed by the lsi_sysm module.
As an alternative, list this information by entering the command
mpathadm show lu "/dev/rdsk/c0t0d0s2.
Answer
65