How configure SAN to server?

Hi all,

I have a server with Solaris version 9. I wanted to mount SAN storage to my server. I am new at this.

Can anyone give me an overview on how to this. Any documents will be fine also. Please let me know if any information is required. Thanks in advance.

Below shows the HBA port:

luxadm -e port
Found path to 1 HBA ports
/devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl                     CONNECTED

luxadm -e dump_map /devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl
Pos AL_PA ID Hard_Addr Port WWN         Node WWN         Type
0     e0  5     e0     21000004cf44ac3d 20000004cf44ac3d 0x0  (Disk device)
1     e2  3     e2     21000004cf449f4b 20000004cf449f4b 0x0  (Disk device)
2     dc  6     dc     50800200001851a9 50800200001851a8 0xd  (SES device)
3     e8  1     e8     21000004cf44a352 20000004cf44a352 0x0  (Disk device)
4     e1  4     e1     21000004cf44a4f3 20000004cf44a4f3 0x0  (Disk device)
5     ef  0     ef     21000004cf4c2b4d 20000004cf4c2b4d 0x0  (Disk device)
6     e4  2     e4     21000004cf44ac5a 20000004cf44ac5a 0x0  (Disk device)
7     1   7d    0      210000e08b000000 200000e08b000000 0x1f (Unknown Type,Host Bus Adapter)

luxadm qlgc
Found Path to 1 FC100/P, ISP2200 Devices
Opening Device: /devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl
Detected FCode Version:       ISP2200 FC-AL Host Adapter Driver: 1.14 01/11/20
Complete

Which type or brand of storage you are using...????

Hi Reboot,

My SAN storage is using HDS 9500
while my server model: SF V880

Well I don't know much about "HDS 9500" storage,but in general you need to zone the host HBA Port ( V880 ) with the port on the Storage so that you host could see the storage.Zoning is done on the switch level and command depends upon the type of switch in use.

You can get the WWN number of the host HBA Port ( V880 ) as :

# prtconf -pv|grep -i wwn

And the WWN number of the storage port can be found out as (for brocad switch only):

# switchshow
 
and 
 
#portshow <port_number>
 

:b::b:

In my case, i have a IBM ESS Shark 800 storage and have multi os clients solaris 5.8 and 5.10 and RHEL 5. There is host attached with the storage and it has a graphical utility to create lun after adding new hard disks. Once the lun is created then i need to assign the lun to the host which has the WWPN ( not WWNN ) ip address, hostname. Then from solaris if i gave "devfsadm -Cv" i could see the lun.
This is what the procedure i follow in my site. It will vary with respect to the vendor. But i hope i may give a idea about assigning a lun to the client.

1 Like

Zoning was done by our "SAN administrator".
Now i just need to see the SAN drive to be mounted.

I hav downloaded & installed the drivers JNIC415.tar.gz & EZF_221.tar. But still cant seems to detect the SAN storage. Don't know if there is still any configuration to be done.:(:frowning:

Hi kingston, can you explain to me more about devfsadm -Cv, from man, it seems like cleaning dangling links & printing the changes to /dev and /device?

devfsadm -Cv builds devices and /dev links for new devices that is added like SAN disks on the fly, its similar to doing a boot -r or a "touch /reconfigure, reboot".

If Solaris is able to see the disks, is will show up in "format"
The best place to start is to build the devices for the disk(devfsadm -Cv or boot -r, I prefer boot -r) and then look at format.
IF the disk shows up in format, then start using it as normal(newfs and mount if ufs etc)

The luxadm command that you post, show 1 HBA, but if your server is a V880, the hba showed is the "Internal HBA" of V880.

Which HA model has installed the server?, qlogic emulex, jni?

If you have qlogic or emulex, my suggest is install the San Foundation Software to Solaris 9, you can download this package from sun.com/download.

After to install , you can use the "cfgadm -al" command to review if the hba was recognized.

Now, you say that the SAN Administrator configure the zone, then the HBA is working.

If your HBA are JNI, probably you need intsall the EZfiber package and reconfigure the HBA from this utility.

Aditionally, you can modify the /kernel/drv/sd.conf to define the targets and luns that you need see in the server.

The JNI hba are very old, but you can easily found in the internet examples of sd.conf for jni HBA.

After that you config the sd.conf , make a reboot -- -r.

But I insist that the first step is to ensure that the HBA is logged in the SAN switch,

I hope that this help a bit

Hi lufen & cerber0, both your comment helped a lot.

I added on name="sd" parent="jnic146x" target=0; to /kernel/drv/sd.conf & perform a reboot -- -r and was able to detect the san storage. :):b:

#prtdiag
========================= IO Cards =========================
                         Bus  Max
     IO   Port Bus       Freq Bus  Dev,
Brd  Type  ID  Side Slot MHz  Freq Func State Name                              Model
---- ---- ---- ---- ---- ---- ---- ---- ----- --------------------------------  ----------------------
I/O  PCI   9    B    6    33   33  2,0  ok    JNI,FCE/sd (block)                FCE-6410 
I/O  PCI   9    B    5    33   33  3,0  ok    pci-pci8086,b154.0/pci108e,1000   PCI-BRIDGE
I/O  PCI   9    B    5    33   33  0,0  ok    pci108e,1000-pci108e,1000.1       device on pci-bridge
I/O  PCI   9    B    5    33   33  0,1  ok    SUNW,qfe-pci108e,1001             SUNW,pci-qfe/pci-bridg+
I/O  PCI   9    B    5    33   33  1,0  ok    pci108e,1000-pci108e,1000.1       device on pci-bridge
I/O  PCI   9    B    5    33   33  1,1  ok    SUNW,qfe-pci108e,1001             SUNW,pci-qfe/pci-bridg+
I/O  PCI   9    B    5    33   33  2,0  ok    pci108e,1000-pci108e,1000.1       device on pci-bridge
I/O  PCI   9    B    5    33   33  2,1  ok    SUNW,qfe-pci108e,1001             SUNW,pci-qfe/pci-bridg+
I/O  PCI   9    B    5    33   33  3,0  ok    pci108e,1000-pci108e,1000.1       device on pci-bridge
I/O  PCI   9    B    5    33   33  3,1  ok    SUNW,qfe-pci108e,1001             SUNW,pci-qfe/pci-bridg+
I/O  PCI   9    A    8    33   66  1,0  ok    SUNW,m64B                         SUNW,370-4362

cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t6d0                 CD-ROM       connected    configured   unknown
pcisch0:hpc1_slot0             unknown      empty        unconfigured unknown
pcisch0:hpc1_slot1             unknown      empty        unconfigured unknown
pcisch0:hpc1_slot2             unknown      empty        unconfigured unknown
pcisch0:hpc1_slot3             unknown      empty        unconfigured unknown
pcisch2:hpc2_slot4             unknown      empty        unconfigured unknown
pcisch2:hpc2_slot5             pci-pci/hp   connected    configured   ok
pcisch2:hpc2_slot6             fibre/hp     connected    configured   ok
pcisch3:hpc0_slot7             unknown      empty        unconfigured unknown
pcisch3:hpc0_slot8             vgs8514/hp   connected    configured   ok
usb0/1                         unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb0/3                         unknown      empty        unconfigured ok
usb0/4                         unknown      empty        unconfigured ok

I was a bit confuse with this, from my previous posting "Opening Device: /devices/pci@8,600000/SUNW,qlc@2/fp@0,0:devctl" should means the HBA is qlogic, am i correct? While at prtdiag, it shows JNI. Does this means i have 2 hba, one internal & another external? :confused:

lufen is right....devfsadm -Cv will builds the new devices and remove the dangling links. After that, the assigned hard disk will be seen from format command.

you can use the following command to find out the devices which is attached in your pci slot.

prtpicl -c scsi -v |grep -i model
prtpicl -c scsi -v |grep -i manufacturer

One of my system gives the following details, from the model you can find out which is what.

prtpicl -c scsi -v |grep -i model
bash-3.00# prtpicl -c scsi -v |grep -i model
  :model         QLGC,ISP10160 
  :model         QLGC,ISP10160 
  :model         FCE-6460-N 
bash-3.00# prtpicl -c scsi -v |grep -i manu 
  :manufacturer  QLGC 
  :manufacturer  QLGC 
  :manufacturer  JNIC 

I hope it will help you to find out whether you are having scsi card or hba card or fibre network card ....whatever it is.

Regards
Kingston S

1 Like

yes beginningDBA, the V480, V490, V880 and V890 models include a INternal HBA to connect at "internal boot disk", for this reason you can see a qlogic HBA, however the HBA that you connect at the SAN is JNI.

Only for resume.

if you use the native drivers of HBA you cannot configure the HBA with solaris commans (cfgadm, luxad, etc) and is mandatory modify the /kernel/drv/sd.conf to see the SAN disks.

if you use SFS (san foundation software) to Solaris 8 and 9, or the included SAN drivers in solaris 10, you can use cfgadm, luxadm to configure the access to the disks and the /kernel/drv/sd.conf cannot need modified.

1 Like

Hi all, the answer you all gave sure helped to clear a lot of my doubts. Many thanks. :b: