HPE EVA Storage
1837958 Members
3666 Online
110124 Solutions
New Discussion

Re: Solaris with single HBA without Secure Path

 
David Goñi
Occasional Advisor

Solaris with single HBA without Secure Path

We have a Sun machine conected to the SAN with a single HBA without Secure Path.
We have setup the Switches so that it has only one path to the EVA5000.
We present one disk to the Sun machine but we don´t see in the operating system.
Which step should we follow to setup the disk in Solaris8/9??

This is the best information I found:
ftp://ftp.compaq.com/pub/products/storageworks/whitepapers/SingleHBAforEVA_092903.pdf
but I can´t find the TAR file it mentions.

Thank
15 REPLIES 15
Craig_83
Frequent Advisor

Re: Solaris with single HBA without Secure Path

Hi - we have the same setup you described. Here is what you need to do:

â ¢ Download the platform kit that contains the fcraid driver. Here is the URL http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=326994&locale=en_US&taskId=135&prodSeriesId=326992&prodTypeId=12169&swEnvOID=211
â ¢ After you restore the above tar archive, execute the install_stgwks script. This platform kit is normally used for the EMA storage but you need the fcraid driver for the EVA. It will tell you to run config.sh and define your storage â you can ignore this.
â ¢ Now install the EVA platform kit.
â ¢ Perform a reconfigure reboot â the above steps should have created a reconfigure file under /
â ¢ Now present the Virtual Unit to the Solaris system from Command View
â ¢ Issue an drvconfig; devlinks; disks
â ¢ Now do a format and you should
David Goñi
Occasional Advisor

Re: Solaris with single HBA without Secure Path

Thank you for your information Craig.

But I still have the same problem.
I have installed Sun Solaris EVA 3.0B Platform Kit. I follow all the steps but at the end I don´t see any disk from the host.


Do I have to touch these files?
/kernel/drv/qla2300.conf
/kernel/drv/sd.conf

Thank you
Craig_83
Frequent Advisor

Re: Solaris with single HBA without Secure Path

Hi Aritz,

Did you install the EMA platform kit first? The EMA platform kit contains the fcraid that is required when SequrePath is not used. Also, what HBA are you using?

Thanks,
Craig
Esteban Cordero
Occasional Advisor

Re: Solaris with single HBA without Secure Path

I have found the same problem. I'm wondering if it has something to do with the Switch zoning. I'm using 1 port of Controler A, 1 port of Controler B and a Solaris Server on the same zone.. Should I let it see only 1 controller, or is it alright to let it see the 2 controllers?
Craig_83
Frequent Advisor

Re: Solaris with single HBA without Secure Path

Esteban,

You need to zone the switch so that the Solaris system only sees one port on the controller. Without SecurePath, multiple paths will create multiple devices pointing to the same physical unit - not good.

Here is how I have the zones:

Fabric A - Contains two Brocade switches 3900 and a 2800
zone: Sun_EVA1_NOSP_P1_FA
1,4; 1,30
zone: Sun_EVA1_NOSP_P2_FA
1,8; 1,16; 3,12

Fabric B - Also contains two Brocade switches a 3900 and 2800.
zone: Sun_EVA1_NOSP_P1_FB
2,4; 2,24; 2,30; 4,12
zone: Sun_EVA1_NOSP_P2_FB
2,8; 2,16; 2,22

The EVA is connected to ports 4 and 8 on both fabrics (1,4; 1,8 2,4;2,8). The other ports listed are solaris systems that contain a single one port HBA.

One thing to note, the older JNI HBA's will not show the WWN from the drop-down list on Add Host in Command View - you will have to enter it.
Craig
Esteban Cordero
Occasional Advisor

Re: Solaris with single HBA without Secure Path

Thanks for your reply Craig. I kept going on with the next server, a Netware one. I didn't touch the zoning yet, but this one sees and mounts the Virtual Disk presented to it without a problem, so I'm guessing it's not a zoning problem.

I have only 1 switch configured in this way:

port 1,0 Management Appliance
port 1,1 Controller A port 1
port 1,2 Controller B port 1
port 1,3 Controller A port 2
port 1,4 Controller B port 2
port 1,5 Sun 280R
port 1,6 Sun V120
port 1,7 Netware server

I made the zoning for SMA with ports 1,0 1,1 1,2
Sun 280R ports 1,1 1,2 1,5
V120 ports 1,1 1,2 1,6
Netware ports 1,1 1,2 1,7

As stated, the Netware is already using the virtual disk.. The 2 Solaris, they both have am HP HAB card identified inside the operating system as a qlogic 2003, at boot time, it says that the link is up, and seems to be initialized correctly. I tried the boot -r option, to force Solaris look for new devices, but still I am unable to see the virtual disk presented to it with the format command.
Esteban Cordero
Occasional Advisor

Re: Solaris with single HBA without Secure Path

I wish I could edit the message, I made several typos, but mainly, the HBAs inside the solaris systems are ql2300 not 2003.
Craig_83
Frequent Advisor

Re: Solaris with single HBA without Secure Path

Esteban,

The zoning on the Sun systems should be modified to only have one path. Something like:
280R 1,1; 1,5
V120 1,2; 1,6

Did you install the fcraid package and then the EVA platform kit?

Craig

Esteban Cordero
Occasional Advisor

Re: Solaris with single HBA without Secure Path

Thanks Craig. I'll modify the zoning.

I didn't install the fcraid you mention.. From that page I downloaded the Sun Solaris EVA 3.0B Platform Kit, and followed the docs in there, they didn't mention the fcraid driver. Do you mean that first I must download and install the Solaris 8.7B Platform Kit HSG 8.7b 4.11?

What if I have already istalled the EVA kit first?

Thanks in advance
Craig_83
Frequent Advisor

Re: Solaris with single HBA without Secure Path

Hi Esteban,

Yes you will have to install the HSG platform kit for Solaris first and then the EVA platform kit. Without the fcraid driver you will never see the storage.

If you have already installed the EVA platform kit, I think I would perform a 'pkgrm CPQhsv' and then install the HSG platform kit followed by the EVA kit. Then, from Command View, you should be able to add the Solaris system and from the port drop-down menu in 'Add a Host' see the WWN - remember to set the system type to 'Sun Solaris'. Now add the virtual disk(s) and present them to the new system. Finally issue a 'devfsadm' command on the Solaris system to pull in the new unit(s) and build the device files.

Craig
Esteban Cordero
Occasional Advisor

Re: Solaris with single HBA without Secure Path

Thanks for your help Craig. I'll try it out later when I can shut the Sun servers down, since they are in production. The EVA kit is uninstalled, but the ql2300 driver is still there. I'll unistall it too just in case and begin with the fcraid.
Craig_83
Frequent Advisor

Re: Solaris with single HBA without Secure Path

Hi Esteban,

The driver for the qla2300 can remain - both platform kits will check for it and take the appropriate action (install or update) as necessary.

Craig
Esteban Cordero
Occasional Advisor

Re: Solaris with single HBA without Secure Path

Thanks a lot for your help Craig, it was spot on, I did what you said and it worked flawlessly. I have to figure out what happened with the Netware server now, because it cannot see the Virtual disk presented to it now, it just sees an "unbound device object" connected to the HBA card.
Rocky_8
Regular Advisor

Re: Solaris with single HBA without Secure Path

Hi,

I am running the same steps as described, but its not working for me.
I installed the HSV platform kit on top of the fc raid manager.

Setup is the same Craigs,

Any ideas anyone ?

thanks,

rmk
Lan_4
Advisor

Re: Solaris with single HBA without Secure Path

I have a system running in Solaris 9. It has
single HBA, and no secure path. I managed to
let it see all the LUNs on EVA5000.

What I did was to edit /kernel/drv/sd,conf.

Looks like the first LUN created on EVA is LUN 1, but not 0, while solaris by default only
probe 0 at boot. So, added something like following to your /kernel//drv/sd.conf:

name="sd" parent="qla2300" target=1 lun=0;
name="sd" parent="qla2300" target=1 lun=1;
..
(depends on how many LUNs presented to the host.)

Then,
For solaris 9, run
# update_drv -f sd
# devfsadm -C

Solaris 8, you have to reboot your system:
# reboot -- -r

Hope this helps.