Weird message out of SAM - Help!

[Tim Medford]

This morning I went into Disks and FileSystems on our production rx3600 HPUX 11.23 server. A bunch of warning dialogs came up that I've never seen before saying:

"The logical volume manager shows this device file, /dev/dsk/c3t0d0s2, with hardware path, 0/6/0/0/0/0/1/0/0/0.0.0, as belonging to Volume group, vg00. SAM has determined that this hardware path is not currently active because either the device is disconnected, or this is not the primary path to a multiple path physical volume. This results in incorrect disk utilization information in the Disk Devices and Volume Group lists."

This is our root volume group obviously, it's configured as Raid-ADG on a p400 raid controller. I thought i had a problem with the raid controller, but I also got the same message on the 2 other LUNs I have connected to an EVA6000 via fibre channel, totally unrelated to this device.

I usually do file administration from scripts, but I'm sure I've gotten into SAM on this system before and didn't get these warnings.

Is this a problem or just a warning?

Thanks!
Tim

[Tim Nelson]

Got any relevant messages in /var/adm/syslog/syslog.log ?

vgdisplay -v /dev/vg00 ?

[TwoProc]

Did you maybe lose an I/O card cage or bay? If you've got those hardware cards plugged into the same card cage/bay/etc you'd see that type of problem. It certainly looks like you've lost contact with some disks. Like Tim Nelson, I think you need to start looking in the system log files.

[Tim Medford]

This is really odd, I haven't changed anything on the system, and there's nothing in the logs at all. The last time I did anything was to create a new ignite tape a couple weeks ago.

An ioscan -fnC disk looks totally normal to me, and here's the output from vgdisplay on /dev/vg00.

Why would it report the same issue on the volumes connected to the EVA? Is there some common piece of hardware between all volume groups?

--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4354
VGDA 2
PE Size (Mbytes) 32
Total PE 4344
Alloc PE 2524
Free PE 1820
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 768
Current LE 24
Allocated PE 24
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 24576
Current LE 768
Allocated PE 768
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 1152
Current LE 36
Allocated PE 36
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 32
Allocated PE 32
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 16384
Current LE 512
Allocated PE 512
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 256
Allocated PE 256
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 16384
Current LE 512
Allocated PE 512
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c3t0d0s2
PV Status available
Total PE 4344
Free PE 1820
Autoswitch On
Proactive Polling On

[Tim Medford]

I got into isee and it shows no problems, also logged into the iLO and look at the system events. It doesn't show any events other than the last system boot which was several months ago.

Is there any additional diagnostics I can run against the system? I think I'll log a call with HP as well to see if they have any ideas.

Thanks

[Tim Medford]

I logged a call with HP. After going back into Sam to recreate while on the phone with them, the problem did not occur again. Great.

There is nothing in syslog, nothing reported by the EMS or ISEE. I'm starting to wonder if this was just a bug in Sam itself.

Thanks for the replies.

[Tim Nelson]

Maybe a patch to SAM would help. There always seems to be a new one out.

I stopped using it many moons ago just for reasons like this.