xpinfo and LUSE

[Siegfried Schmidt_1]

Why does xpinfo show only the information of the 1. LDEV that belongs to a LUSE consisting of 5 LDEVs ?
I executed 'xpinfo' without setting any option. The output shows that device: c4t0d2 is located in RAID Group: 1-1, CU:LDev: 00:03 and Type is: OPEN-9*5.
BUT, the output does NOT show any information about the other 4 LDEVs that belong to c4t0d2.
All explanations are greatly appreciated.

[Sanjay Kumar Suri]

If you have RAID Manager then use the command raidscan as in the example:

#raidscan -p CL1-A -fx | more

In case of LUSE, the 5th columns will show 1 unless the LUN is a LUSE. In the case of LUSE it will indeicate how many volumes have been combined.

In the partenthesis is the CU and LDEV numbers. For CU=0, the CU# is omitted.

For example in your case the ouput could be:
5(03, 04, 05, 06, 07)

Let me know if this helps.

sks

[V.Tamilvanan]

Hi,
When you check the size of c4t0d2 on xpinfo it will be the combined size of all 5 LDEVs.
Even in my system also the behavior is same.
When you configure 5 ldevs as LUSE these 5 ldevs are addressed with the actual LDEV name of First LDEV and combining the size of all the five. So what you are unable to see the other four ldevs in xpinfo.

[Siegfried Schmidt_1]

Thanks Sanjay and Tamil for your reply.
Unfortunately I don't have RAID Manager in use. Is RAID Manager part of the software delivered with the XP, or is it part of HP-UX ? Sanjay, could you kindly provide the 'raidscan' description (man-page) ?

Since xpinfo does not provide the desired information, I am wondering, if we could ask HP to close this gap. Maybe my comparison is not appropriate, but EMC's SYMCLI command 'symdev' provides information of ALL Hypervolumes - also of those that are Metavolume members.

[Sanjay Kumar Suri]

1. RAID Manager XP is host-based software package that includes the CCI (Command control interface).

2. It enables you to initiate BC and CA commands from UNIX based host systems.

3. RAID Manager XP is a independent software. You must ask HP to get an installation CD.

4. Some help on raidscan is given below.

sks

#raidscan -h
Model : Raid-Manager-XP/HP-UX
Ver&Rev: 01.12.06
Usage : raidscan [options] for HORC
-h Help/Usage
-z Set to the interactive mode
-zx Set to the interactive mode and HORCM monitoring
-q Quit(Return to main())
-p [hgrp] Specify the port_name(CL1-A or cl1-a... cl3-a or CL3-A... for the expansion(Lower) port)
-pd[g] Specify the raw_device
-pi <'strings'> Specify the 'strings' for -find option without using STDIN
-t Specify the target_ID
-l Specify the LUN#
-m Scan the specified MU# only
-s Specify the Seq#(Serial#) of the RAID
-f[f] Specify display of the volume-type
-f[x] Specify display of the LDEV#(hex)
-f[g] Specify display of the Group-name
-f[d] Specify display of the Device file name
-f[e] Specify display of the External LUN only
-CLI Specify display of CLI format
-find[g] Find out the LDEV from the raw_device via STDIN.
-find inst [-fx] Register the Device File via STDIN to HORCM and
permits its volumes on horcm.conf in Protection Mode
-find verify [mun#] [-f[x][d]] Find out the relation between Group
on horcm.conf and DEVICE_FILE via STDIN
-find[g] conf [mun#][-g name] Display the raw_device in horcm.conf image.
For example: [ ls /dev/rdsk/* | raidscan -find [-fx] ]
For example: [ ioscan -fun | grep rdsk | raidscan -find [-fx] ]
For example: [ vgdisplay -v /dev/vg01|grep dsk|sed 's/\/*\/dsk\//\/rdsk\//g'|raidscan -find [-fx] ]