armdsp invalid array id

[80skeys]

I launched Sam - Disk and File Systems - Volume Groups and it popped up the following error message:

"The command used to retrieve information about the HP SureStore Virtual Array has failed ... INVALID ARRAY ID ... armdsp did not provide a serial number for device file /dev/dsk/c16t0d0. Please be sure that the array software utilities have been properly installed and the device file exists. The array and LUNs will be displayed but dual paths will not be collapsed."

Any idea what's going on?

[Johnson Punniyalingam]

Hi Michael,

looks like your "HP SureStore Virtual Array " needs pshyical attention,

can please take look

# ioscan -fnC disk |grep -i A6189A

or

# ioscan -fnC disk

# armdsp -a

Thanks,
Johnson

[Torsten.]

I never used commandview SDM from SAM ... anyway try

# armdiscover
# armdsp -a

and check the status.

[80skeys]

Johnson,

Below are the outputs to the commands you asked me to run. It looks like when I ran "armdiscover" it cleared up the problem. Any ideas?

f6#/opt/sanmgr/commandview/client/sbin> armdiscover
This could take several minutes ...
HP-A6218A /dev/rscsi/c19t12d0 00USE00003D8 facets6 rly-yd02

f6#/opt/sanmgr/commandview/client/sbin> ioscan -fnC disk | grep -i A6218A
disk 21 0/2/0/0.8.0.110.0.0.0 sdisk CLAIMED DEVICE HP A6218A
disk 23 0/2/0/0.8.0.110.0.0.1 sdisk CLAIMED DEVICE HP A6218A
disk 24 0/2/0/0.8.0.110.0.0.2 sdisk CLAIMED DEVICE HP A6218A
disk 25 0/2/0/0.8.0.110.0.0.3 sdisk CLAIMED DEVICE HP A6218A
disk 29 0/2/0/0.8.0.110.0.0.4 sdisk CLAIMED DEVICE HP A6218A
disk 30 0/2/0/0.8.0.110.0.0.5 sdisk CLAIMED DEVICE HP A6218A
disk 33 0/2/0/0.8.0.110.0.0.6 sdisk CLAIMED DEVICE HP A6218A
disk 36 0/2/0/0.8.0.110.0.0.7 sdisk CLAIMED DEVICE HP A6218A
disk 39 0/2/0/0.8.0.110.0.1.0 sdisk CLAIMED DEVICE HP A6218A
disk 41 0/2/0/0.8.0.110.0.1.1 sdisk CLAIMED DEVICE HP A6218A
disk 22 1/0/0/0.8.0.108.0.0.0 sdisk CLAIMED DEVICE HP A6218A
disk 26 1/0/0/0.8.0.108.0.0.1 sdisk CLAIMED DEVICE HP A6218A
disk 27 1/0/0/0.8.0.108.0.0.2 sdisk CLAIMED DEVICE HP A6218A
disk 28 1/0/0/0.8.0.108.0.0.3 sdisk CLAIMED DEVICE HP A6218A
disk 31 1/0/0/0.8.0.108.0.0.4 sdisk CLAIMED DEVICE HP A6218A
disk 32 1/0/0/0.8.0.108.0.0.5 sdisk CLAIMED DEVICE HP A6218A
disk 34 1/0/0/0.8.0.108.0.0.6 sdisk CLAIMED DEVICE HP A6218A
disk 37 1/0/0/0.8.0.108.0.0.7 sdisk CLAIMED DEVICE HP A6218A
disk 38 1/0/0/0.8.0.108.0.1.0 sdisk CLAIMED DEVICE HP A6218A
disk 40 1/0/0/0.8.0.108.0.1.1 sdisk CLAIMED DEVICE HP A6218A


Do you want me to include the "armdsp -a" output? It's very lengthy.

[Torsten.]

If the arra itself and all the commandview tools are working, it could only be a problem with SAM. Did you check for SAM general patches on ITRC?

[Johnson Punniyalingam · Accepted solution]

Hi Michael,

No problem, with HP SureStore Virtual Array only problem with >> launched Sam - Disk and File Systems <<

SAM, was unable to catch up "HP SureStore Virtual Array " disk while scanning,

NO worries ..:)

You need sreach for "SAM" critical patches.

Thanks,
Johnson

[80skeys]

armdsp -a output shows mostly "Good" status for components, except the following "Link down" for several front and back ports on the controllers. Is this normal?

Controller At M/C2:
Status:_______________________________Good
Front Port At M/C2.H2:
Status:_____________________________Good
Port Instance:______________________1
Hard Address:_______________________126
Link State:_________________________Link Down
Back Port At M/C2.J2:
Status:_____________________________Good
Port Instance:______________________1
Hard Address:_______________________126
Link State:_________________________Link Down

Controller At M/C1:
Front Port At M/C1.H2:
Status:_____________________________Good
Port Instance:______________________1
Hard Address:_______________________126
Link State:_________________________Link Down
Back Port At M/C1.J2:
Status:_____________________________Good
Port Instance:______________________1
Hard Address:_______________________126
Link State:_________________________Link Down

[80skeys]

Ignore "link down" from my last post. I found that this is normal when 7410 connected to only one host.

[Torsten.]

It is normal if nothing is connected there.

Each controller has 2 connectors for disks, 2 connectors for outside (hosts).

You probably are using only 1.

[Torsten.]

Have a look at this patch:

http://www11.itrc.hp.com/service/patch/patchDetail.do?patchid=PHCO_36562&sel={hpux:11.11,}&BC=main|search|

It lists several fixes regarding the VA family (commandview SDM).

[80skeys]

Closing thread because the explanation of SAM unable to catch up with arm commands makes sense and the links to the patches are helpful.