VNX disk storage viewing using SAM. (HP11.11 and HP11.23)

[Mark Parsons]

Hi,

We have recently purchased vnx disk storage from EMC to replace our EVA disk storage.

This worked fine when the vnx disk storage was presented to the server when the eva disk storage was still present (see attachment - vnx-issue-pic1)

But then when we removed the eva disk storage it seems that sam gets confused (see attachment - vnx-issue-pic2)

This is only in the disk devices view in Sam - it seems to be okay for viewing volume groups / logical volumes etc etc.

EMC have told us to do this:

For 11i v1.0, and 11i v2.0, you must edit the file
/usr/sam/lib/C/pd_devinfo.txt file as follows:
1. Find the existing entry that begins:
DISK:::sdisk:::.*DGC.*3400.*::::::::::::::HPMODEL 30 LUN
2. Add the following new entries after that entry. These lines must
be put after the existing entry for this fix to work:
DISK:::sdisk:::.*DGC.*CX*.*::::::::::::::CX Series LUN:::::DISK_ARRAY,CLARIION
DISK:::sdisk:::.*DGC.*C47*.*::::::::::::::FC Series LUN:::::DISK_ARRAY,CLARIION
3. Next search for the following entry:
DISK:::disc3:::.*DGC.*3400.*:::::::::::::HP Model 30 LUN:::::DISK_ARRAY,CLARIION
4. Add the following new entries after that entry. These lines must
be put after the existing entry for this fix to work:
DISK:::disc3:::.*DGC.*CX*.*::::::::::::::CX Series LUN:::::DISK_ARRAY,CLARIION
DISK:::disc3:::.*DGC.*C47*.*::::::::::::::FC Series LUN:::::DISK_ARRAY,CLARIION
5. Save these edits and restart SAM.

This doesnt work! This is on both HP11.11 and HP11.23

Any suggestions?

Kind Regards,

Mark P.

[Bill Hassell]

SAM will get very confused if you do not remove disks correctly.

The wrong way is to yank out the cables and perhaps use rm on the disk LUN device files.

The correct way is to vgreduce any VGs that have these disks attached.

Then use rmsf -H<hardware_path> for each of the removed paths.

Then you can remove the presentation of the LUNs from the array (or pull the cables).

Finally, update the kernel with ioscan -fCdisk and look for NO_HW on any lines. Those items will need rmsf -H also.

(forget SAM for LUN manipulation like this...it is too slow and clumsy and doesn't provide any useful messages)

When you add new LUNs, the steps are:

-- # ioscan -fCdisk       # discovers the new paths for disks

-- # insf -eCdisk            # creates the device files

The attached script, cleanNO_HW.sh will cleanup the NO_HW conditions as well as device files that no longer point to valid paths.