This content has been marked as final. Show 10 replies
Thanks for your prompt response.
So it implies the mpxio method could
still be used for HDS San
(BTW, could the Hitachi's own multipathing
systems e.g. HDLM be used as an alternative?)
You suggested to change the scsi_vhci.conf file
But I notice that there's also the
ssd.conf file involved in our Netapp SAN
What do we have to change for this file
(or this is not needed for HDS and must be removed?)
You can use HDLM. But it's not free software. In case you by it - read Doc's about HDLM on Solaris.
In case you plan use MPXIO - you need customize scsi_vhci.conf.
We don't know what changes you make in ssd.conf. Generaly this file not direct effect on multipathing but can tune some timeouts.
It can be configured for specific device ( Vendor/Device Name ) or globaly.
In my opinion you not need modify this file. Best - you shop what lines was modified.
Yes, the file ssd.conf seems like what you said,
only define some netapp specifics & timeouts
(I'll list them at the bottom). I think I will simply
revert to the original ssd.conf (which I have a backup) before configuring it for HDS
Now from my understanding, the following steps
are required to enable mpxio to use the HDS San:
(Pls correct me if there're some steps not
required. I've just found this from someone's blog, but it is for solaris10)
1. Add a line to kernel/drv/fp.conf
2. Edit the scsi_vhci.conf
to remove the Netapp related entries and
add those which are HDS specific (as you told
me in your first response)
3. Do the command
(Note since my solaris is 9 , so I cannot
do the better syntax stmsboot -D fp -e But my box
is a sunfire 245 whose internal disk should not
be fibre and so won't matter ??? True ?)
which will reboot for me and enable mpxio
4. Do another boot by
I have questions about 1 & 3 which I hope
you could clarify for me
For 1, I notice that in my present working
multipathing with the Netapp san , I do
not even have the line mpxio-disable="no".
, yet it is still working
For 3, the manual says stmsboot -e
does 3 things
(a) add the line
mpxio-disable="no" to fp.conf
(b) make things right for the vfstab file
(c) enable mpxio
If so, then is step 1 really redundant ?
BTW, I know mpxio works only of my Solaris
has certain patches installed. How do I find out
which the patch pre-requisites?
P.S. Here are the added lines in my ssd.conf
#`ssd-config-list="NETAPP LUN", "netapp-ssd-config";
ssd-config-list="NETAPP LUN", "netapp-ssd-config";
It's Look like correct.
Step 1 and step 3. Do same. Select One.
stmsboot will cause rebot system.
So you not need do one more reboot.
For get list of patches - see DocID 1012190.1
Thanks again Nik
You mentioned finding that DocID to look at what
patches to have.
I have a valid Sun Support Contract , which would
enable me to login to read them,
Have gone in and read the doc.
But do not quite understand it.
Will try to spend more time in finding out
the details of the patches.
Edited by: webbburt777 on 2011/10/31 下午 5:35
For latest SAN 4.4.15
You shoulf install patches:
113042-19 For Qlogic Card
114477-04 For SNIA CARD
114478-08 For SNIA CARD
114878-10 For jfca card
119914-14 FOr Emulex card
Download all patches and analyse dependency.
Try install all. In case patche can't be installed becouse this package not installed -
in most case you not install drivers for HBA that not installed.
Thanks for the detailed info, Nik
By the way, we will have to install a second
HBA card for another server to do multipathing.
I would like to know the brand (and model no.)
of the first HBA card so as to get the second
card to be of same model
What's the best way to find this info
for Solaris 9
You need analyze output of
prtdiag -v - It show what card installed at what slot.
For prtconf - try seach words wwn and see around for vendor name.
Thanks Nik for the hints to find out
the HBA card model.
Actually before I saw your answer, I
searched in the solaris 9 forum
and found this method which also tells me
which tells me it is Emulex LP10000
Now I have a further question regarding
the driver used for this emulex card.
On one of the servers, the driver reported
by the prtpicl command is:
whereas on another server (which was installed later than the one using lpfc) , it is
Now I am going to insert one more emulex card
into the server which uses the lpfc driver
, does it matter if the driver for the new card is emlxs or I must make sure it is also lpfc ?