how to present EMC disks to HPUX?

[Rick Garland]

Hi all:

Doing some studying on EMC and HPUX. My notes don't tell me how to present a set of EMC disks to HPUX so they can be seen via ioscan.

Anybody give quick synopsis?

Thanks

[Con O'Kelly · Accepted solution]

Hi Rick

In brief terms I've done the following:

1.
Allocate disks to server using EMC Volume Logix GUI. Prior to using the GUI you may need to zone the EMC switch so that the disks are visble to the server.

2. On server run:
# ioscan -f

3. Check new disks are visible to OS using:
# ioscan -fnkC disk
(New disks will have no device files)

4. Create device files
# insf -e

Thats really all there is to it.

Its a while since I've used EMC so maybe Volume Logix GUI has been replaced by new EMC software.

Cheers
Con

[Sundar_7]

OK I can tell you my understanding

Your server is probably connected to the EMC using a SAN switch.

You will need a node with some kind of SAN management software loaded. We use ECC (EMC control center) and VolumeLogix for zoning.

Each fiber card is uniquely identfied using WWN (World Wide Name).

you can assign each EMC volume to the EMC Channel adapter by creating a map file and configure using symconfigure command.

And then using fpath you can assign which fibre channel WWN sees which EMC volumes.

Once this is done, your host will start seeing the disks.

ioscan and insf in your hosts will create the device file.

I have a good summary that I can post here tommorrow

[Rick Garland]

Post that summary tomorrow. I will look and reward full points then as well.

Many thanks!

[Michael Tully]

Hi Rick,

As long as the LUN's have been presented to the front end ports you can unmask them to whatever host(s) you want. If they are not, you would have to get your SAN admin to do this. That is a quite complicated process. So in summary:

If LUN's have been presented, to the front end ports (rule of 17) i.e. 3aa and/or 14aa

If you have an ECC management station your laughing, fairly easy, if not:

Using VolumeLogix:
Find your gatekeeper device using syminq or an equivalent inq.hp binary
export the gatekeeper
export VCMDBDEVICE=/dev/rdsk/c13t0d0
get the WWN from the host using fcmsutil
/opt/fcms/bin/fcmsutil /dev/td0
Capture an exising ioscan
ioscan -fnk >/tmp/ioscan1.out

fpath adddev -w -f 3aa -r "123-129"
-f front end adapator
-r range of luns

fpath adddev -w 50060b00000adfgg -f 3aa -r "12-129"
fpath refresh

Got to the intended host and run ioscan
ioscan -fn >/tmp/ioscan2.out
diff the two files
diff /tmp/ioscan1.out /tmp/ioscan2.out
If they are different use insf to create the devices
insf -e

Be extremely careful in attempting to use symconfigure. Once committed you are actually making a bin change to your symm.

Cheers
Michael

[Shaikh Imran]

Hi,
I have used clariion FC4700 earlier with L & N class servers:
Without a FC siwtch i.e.
EMC Directly connected to Server's FC.
The steps were simple.
1) I used Navisphere Manager ( The LUN Management S/W from EMC) to create the LUN's
2) Navisphere client was installed on HP-Unix server.
3) After the LUN's were configured with the appropiate RAID's
4) Proper FC drivers installed on the HP-System
5) insf -e will create a device files as /dev/dsk/cxtxdx for all the available LUN's
6) Now you very well know what to do with /dev/dsk/cxtxdx

EMC connected with a FC switch:
I have used a Brocade DS-8 FC switch
1) The EMC's SP's were connected to the switch and also the servers which are to be
given the EMC access are connected to the same fiber switch.
2) Proper zoning is done so that the disk
(LUN's) associated with one server should not be seen by the others.
Zoning is done at the switch level.
Rest Procedure is the same from HP side.

Regards,

[Sundar_7]

Say for example if your EMC's one of the channel director is 5B then

symcfg list -SA 5B -address -available

The above command will list the VBUS, Target and LUN that are available in the channel director 5B. you can assign your EMC volume to be seen by one of those VBUS, target and LUN combination.

HP-UX can only see upto 8 LUNS from 0-7

To demonstrate, if the EMC volumes you want to assign to the hosts are 469 to 472.

# vi hosts.map
map dev 469 to dir 05B:0 target=8, LUN=2, vbus=3;
map dev 469 to dir 06B:0 target=8, LUN=2, vbus=3;
...
#

Your server should see the channel directory 05B and 06B i.e your host has more than one fibre channel adapter.

2 lines for a single EMC volume means the host will see multiple paths for the same
LUN.

# symconfigure -f hosts.map preview

Once the preview is complete

# symconfigure -f commit

The above command commits the operation.

Now we need to do LUN masking and make sure the hosts are allowed to the see the volumes that they are supposed to

VolumeLogix commands are used to do LUN masking


# cd /usr/emc/VolumeLogix
# fpath lsdb -s on

fpath will display the LUN masking configuration in place.

To make a particular volume visible to the host

# fpath adddev -w -f 5B -r "469"

Once this is done, execute ioscan and insf commands in your host to create the device files.

[Rick Garland]

Everybody who respomded:

Many thanks!
I have not been able to find my notes from a few years back - the last trime I worked with EMC. But I immensely appreciate the feedback I can always count on in the ITRC forum.

Again, many thanks!