New SAN drive is not appearing in SAM

[Serguei Chipouline]

Greetings,

I had a new SAN drive added to my HP-UX 11.11 system last week. The paths to the new drives in HP-UX got added fine and I can see the newly added disk using

ioscan -fnC disk

The output of the ioscan is as follows:

Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 13 0/3/1/0.78.1.0.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c10t0d0 /dev/rdsk/c10t0d0
disk 24 0/3/1/0.78.1.0.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c10t0d1 /dev/rdsk/c10t0d1
disk 14 0/3/1/0.78.1.1.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c11t0d0 /dev/rdsk/c11t0d0
disk 23 0/3/1/0.78.1.1.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1
disk 17 0/3/1/0.78.1.2.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c12t0d0 /dev/rdsk/c12t0d0
disk 21 0/3/1/0.78.1.2.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c12t0d1 /dev/rdsk/c12t0d1
disk 18 0/3/1/0.78.1.3.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c13t0d0 /dev/rdsk/c13t0d0
disk 22 0/3/1/0.78.1.3.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c13t0d1 /dev/rdsk/c13t0d1
disk 15 0/4/1/0.23.2.0.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c14t0d0 /dev/rdsk/c14t0d0
disk 28 0/4/1/0.23.2.0.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c14t0d1 /dev/rdsk/c14t0d1
disk 16 0/4/1/0.23.2.1.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c15t0d0 /dev/rdsk/c15t0d0
disk 27 0/4/1/0.23.2.1.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c15t0d1 /dev/rdsk/c15t0d1
disk 20 0/4/1/0.23.2.2.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c16t0d0 /dev/rdsk/c16t0d0
disk 26 0/4/1/0.23.2.2.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c16t0d1 /dev/rdsk/c16t0d1
disk 19 0/4/1/0.23.2.3.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c17t0d0 /dev/rdsk/c17t0d0
disk 25 0/4/1/0.23.2.3.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c17t0d1 /dev/rdsk/c17t0d1

However, SAM utility shows a single disk device with 16 redundant paths for these 2 different LUNs:

0/0/2/0.0.0.0 1 Unused -- 578 DVD-ROM Dr
0/1/1/0.0.0 1 LVM vg00 34732 HP 36.4GMA 0/1/1/0.1.0 1 LVM vg00 34732 HP 36.4GMA 0/3/1/0.78.1.0.0.0.0 16 LVM VIP_VG 68327 IBM 21

The new device(s)

/dev/dsk/c10t0d1

appear to work fine with pvcreate/vgextend, but I'm a bit iffy to start using the disk without confirming that there is nothing wrong with the setup.

[TTr]

The ioscan tool is the one to trust. SAM has had bus in it and you may need to install patches. Even then it may still be unreliable with SAN based devices.

It looks like you have 8 device paths for each of these two LUNs (the look like SVC LUNs), do you use redundant paths in your LVM configuration(PV links)?

[Serguei Chipouline]

Yes, we are using IBM SVC + PV links. However, I have a sister DR server that is at the same patch level as my Production box (the one with the issue) and the DR machine has no problem of seeing 3 separate SAN disks in SAM for each of the SAN LUNs configured for it.

[TTr]

Based on what you have provided so far I can't see anything wrong and I would go with ioscan and the LVM commands and ignore the sam issue. Did you check if there is a sam difference between the two servers? (ioscan -l fileset | grep -i sam)

[Serguei Chipouline]

Both systems have identical SAM software versions deployed:

swlist -l fileset | grep SAM
# PHCO_36562 1.0 cumulative SAM patch
PHCO_36562.SAM 1.0 SystemAdmin.SAM
PHCO_36562.SAM-ENG-A-MAN 1.0 SystemAdmin.SAM-ENG-A-MAN
PHCO_36562.SAM-HELP 1.0 SystemAdmin.SAM-HELP
PHSS_34392.DDX-SAM B.11.11.41 Xserver.DDX-SAM
SystemAdmin.SAM B.11.11 System Administration Manager
SystemAdmin.SAM-ENG-A-MAN B.11.11 SAM-ENG-A-MAN
SystemAdmin.SAM-HELP B.11.11 On-line Help for System Adminstration Manager
SystemAdmin.SAM-JPN-E-MAN B.11.11 SAM-JPN-E-MAN
SystemAdmin.SAM-JPN-S-MAN B.11.11 SAM-JPN-S-MAN
Xserver.DDX-SAM B.11.11 X Server/SAM X0Screens Help Files

[TTr]

> ...and the DR machine has no problem of seeing 3 separate SAN disks in SAM...

Do these SAN disks have long hardware paths as in the first server or is the last digit (device number) truncated?

You have to understand that SAM gets its information from the same LVM commands and it has to parse that information and correlate disks and volumes and display it up to you in a nice form. That's where things usually go wrong and that's why I say there is nothing wrong with the disks.
You are saying the two servers are identical, unless you ignited the DR server from the first server in the last few days they can not be identical. And then you have all the peripherals and disk devices, those can not be identical in both servers.
Whatever it is, I can not point it out to you, you have to keep looking around the server.

[Serguei Chipouline]

The 2 servers in question are not identical. They are at the same patch level. The Production server uses 2 Tachyon cards while the DR server uses a single dual-port Qlogic adapter.

The hardware paths seen by the DR box for its disks are as follows:

$ ioscan -fnC disk
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 2 0/0/1/0.2.0 sdisk CLAIMED DEVICE HP DVD-ROM 305
/dev/dsk/c0t2d0 /dev/rdsk/c0t2d0
disk 0 0/0/1/1.15.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c1t15d0 /dev/rdsk/c1t15d0
disk 1 0/0/2/1.15.0 sdisk CLAIMED DEVICE HP 36.4GMAS3367NC
/dev/dsk/c3t15d0 /dev/rdsk/c3t15d0
disk 25 0/2/0/0.23.6.0.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c19t0d0 /dev/rdsk/c19t0d0
disk 36 0/2/0/0.23.6.0.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c19t0d1 /dev/rdsk/c19t0d1
disk 41 0/2/0/0.23.6.0.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c19t0d2 /dev/rdsk/c19t0d2
disk 26 0/2/0/0.23.6.1.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c20t0d0 /dev/rdsk/c20t0d0
disk 38 0/2/0/0.23.6.1.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c20t0d1 /dev/rdsk/c20t0d1
disk 42 0/2/0/0.23.6.1.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c20t0d2 /dev/rdsk/c20t0d2
disk 27 0/2/0/0.23.6.2.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c21t0d0 /dev/rdsk/c21t0d0
disk 40 0/2/0/0.23.6.2.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c21t0d1 /dev/rdsk/c21t0d1
disk 43 0/2/0/0.23.6.2.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c21t0d2 /dev/rdsk/c21t0d2
disk 28 0/2/0/0.23.6.3.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c22t0d0 /dev/rdsk/c22t0d0
disk 37 0/2/0/0.23.6.3.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c22t0d1 /dev/rdsk/c22t0d1
disk 45 0/2/0/0.23.6.3.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c22t0d2 /dev/rdsk/c22t0d2
disk 29 0/2/0/1.187.5.0.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c23t0d0 /dev/rdsk/c23t0d0
disk 33 0/2/0/1.187.5.0.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c23t0d1 /dev/rdsk/c23t0d1
disk 48 0/2/0/1.187.5.0.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c23t0d2 /dev/rdsk/c23t0d2
disk 30 0/2/0/1.187.5.1.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c24t0d0 /dev/rdsk/c24t0d0
disk 34 0/2/0/1.187.5.1.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c24t0d1 /dev/rdsk/c24t0d1
disk 47 0/2/0/1.187.5.1.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c24t0d2 /dev/rdsk/c24t0d2
disk 31 0/2/0/1.187.5.2.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c25t0d0 /dev/rdsk/c25t0d0
disk 35 0/2/0/1.187.5.2.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c25t0d1 /dev/rdsk/c25t0d1
disk 44 0/2/0/1.187.5.2.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c25t0d2 /dev/rdsk/c25t0d2
disk 32 0/2/0/1.187.5.3.0.0.0 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c26t0d0 /dev/rdsk/c26t0d0
disk 39 0/2/0/1.187.5.3.0.0.1 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c26t0d1 /dev/rdsk/c26t0d1
disk 46 0/2/0/1.187.5.3.0.0.2 sdisk CLAIMED DEVICE IBM 2145
/dev/dsk/c26t0d2 /dev/rdsk/c26t0d2

On DR system SAM reports the following disk devices:

0/0/1/0.2.0 1 Unused -- 0 HP DV0/0/1/1.15.0 1 LVM vg00 34732 HP 36.4GMA 0/0/2/1.15.0 1 LVM vg00 34732 HP 36.4GMA 0/2/0/0.23.6.0.0.0.1 8 LVM VIP_VG 65536 IBM 21 0/2/0/0.23.6.0.0.0.2 8 LVM VIP_VG 40960 IBM 21 0/2/0/0.23.6.2.0.0.0 8 LVM VIP_VG 139264 IBM 21

[TTr]

In sam, select one of the LUNs on the production server and ask sam for more information (actions -> ViewMoreInformation) and also include "show device files". Then repeat it for the other LUN and compare the output.

[Serguei Chipouline]

On Production server SAM is reporting the following details for the SAN disk it sees:

Hardware Path: 0/3/1/0.78.1.0.0.0.0
Volume Group: VIP_VG
Logical volumes utilizing space on this disk:

Logical Size Percent Disk
Volume Usage (Mbytes) Space Used
------------------------------------------------------
VIPLV01 VxFS 8312 12%
VIPLV02 VxFS 60000 87%

As for device files the following is reported:

Device File Description
------------------------------------------------------
/dev/dsk/c10t0d0 Block device file
/dev/rdsk/c10t0d0 Character device file

The alternate paths info shows the following 15 HW paths:

0/3/1/0.78.1.0.0.0.1
0/3/1/0.78.1.1.0.0.0
0/3/1/0.78.1.1.0.0.1
0/3/1/0.78.1.2.0.0.0
0/3/1/0.78.1.2.0.0.1
0/3/1/0.78.1.3.0.0.0
0/3/1/0.78.1.3.0.0.1
0/4/1/0.23.2.0.0.0.0
0/4/1/0.23.2.0.0.0.1
0/4/1/0.23.2.1.0.0.0
0/4/1/0.23.2.1.0.0.1
0/4/1/0.23.2.2.0.0.0
0/4/1/0.23.2.2.0.0.1
0/4/1/0.23.2.3.0.0.0
0/4/1/0.23.2.3.0.0.1

[TTr]

I am running out of ideas here.
Is it possible that this second disk is the same as the first and somehow because of the way it was presented, it shows up as a different SCSI unit and sam is correct?

Did you create a volume group with this second disk? (pvcreate, vgcreate etc) and you see both disks and did not destroy the first disk (by pvcreating the second disk)?

Check the LVM headers (VGRA etc.) to see if they are the same (same disk or different disks with same info). Check the LVM headers by looking at melvyn's response here http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=&threadId=1064953