SAM isn't displaying all devices

[Linda Champ]

I'm displaying the 'Disk & File Systems' screen from SAM which only displays one of two LUNS that are on the system.
When I run ioscan -fnCdisk both LUNs are displayed. The H/W Type is device and the status is CLAIMED.

I did a pvcreate on both of the physical devices thinking that would make them display in SAM.

I'm running 11.0 on a hp 9000/800/N4000-55 server, A5158A-PCI Tachyon TL/TS Fibre Channel. The LUNs are on an hsg080 device.

Below is the line entry for the disk from SAM and the ioscan for the 2 luns. Can't figure out what is going on with SAM.


hardware No. of Volume Total
path Paths Use Group Mbytes Description

255/0.0.1 2 LVM vg01/vg02 17361 HSG80 LUN 0x600...



ioscan -fnCdisk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
disk 3 255/0.0.1 sdisk CLAIMED DEVICE HSG80 LUN 0x60001F
E10007B21000098340195603BF
/dev/dsk/c37t0d1 /dev/rdsk/c37t0d1
disk 6 255/0.0.2 sdisk CLAIMED DEVICE HSG80 LUN 0x60001F
E10007B21000098340195603C0

/dev/dsk/c37t0d2 /dev/rdsk/c37t0d2

Linda

[Jeff Schussele]

Hi Linda,

How many Tachyon's does your system have?
Believe that the instance number - 37 - in your case is in error.
Run lssf /dev/dsk/c37t0d1 and d2 & examine the output.
lssf gives more info than iosscan.
If this points out a problem, then I'd remove the device files for them - both /dev/dsk & dev/rdsk & run insf -e to have the system recreate them.
If they come back as 37 then I'd suspect a kernel problem - probably the Tachyon driver.

HTH,
Jeff

[Charles McCary]

Linda,

is it possible that the LUN is a single LUN and that you are dealing with an alternate path issue? Sam will only display one path to a disk if it has alternate paths.

[Linda Champ]

Hi,
Thanks for looking at this. I have two Tachyons. I ran lssf on the two devices:
# lssf /dev/dsk/c37t0d1
sdisk card instance 37 SCSI target 0 SCSI LUN 1 section 0 at address 255/0.0.1 /dev/dsk/c37t0d1

# lssf /dev/dsk/c37t0d2
sdisk card instance 37 SCSI target 0 SCSI LUN 2 section 0 at address 255/0.0.2 /dev/dsk/c37t0d2

I haven't used lssf but it looks like there are two unique paths. The instance is 37, since I'm so new to this I'm not sure what this indicates..

Linda

[Jeff Schussele]

Hi Linda,

The lssf output looks normal.

The card instance # is assigned by the kernel at boot time & I thought was a "sequential" value. I'm no expert on dev file naming, but I thought that they were assigned "in order" & the 37 just didn't look right to me.

Try a diskinfo command
diskinfo /dev/rdsk/c37t0d1 & d2 & if they return OK AND the disks can be accessed & used OK, then I suspect the problem lies w/SAM.

Check the SAM patch level
& if old get the latest 11.0 SAM cumulative
PHCO_23876 here's the URL for the patch description

http://us-support.external.hp.com/wpsl/bin/doc.pl/screen=wpslDisplayPatch/sid=0a22bd290c46ac10b0?PACH_NAM=PHCO_23876&HW=s800&OS=11.00

HTH,
Jeff