HP SIM not seeing DISKS in a D2700 Disk Enclosure

[robert70]

Hi We have

rx2800 i2 integrity server - open vms 8.4

D2700 Disk Enclosure connected via a P411 Smart controller

When logged onto the SMH we see the P411 controller but no info on the disk spindles

Anybody out there had similar problems?

Dave$ product show product
------------------------------------ ----------- ---------
PRODUCT                              KIT TYPE    STATE
------------------------------------ ----------- ---------
HP I64VMS ACUXE V6.40-11P09A         Full LP     Installed
HP I64VMS AVAIL_MAN_BASE V8.4        Full LP     Installed
HP I64VMS CDSA V2.4-322              Full LP     Installed
HP I64VMS CSWS V2.2                  Full LP     Installed
HP I64VMS CSWS_PHP V5.2-17           Full LP     Installed
HP I64VMS CXX V7.4-4                 Full LP     Installed
HP I64VMS DWMOTIF V1.7               Full LP     Installed
HP I64VMS DWMOTIF_SUPPORT V8.4       Full LP     Installed
HP I64VMS FORTRAN V8.2-0             Full LP     Installed
HP I64VMS GNV V2.1-3                 Full LP     Installed
HP I64VMS HPBINARYCHECKER V1.1       Full LP     Installed
HP I64VMS JAVA142 V1.4-26            Full LP     Installed
HP I64VMS KERBEROS V3.2-228          Full LP     Installed
HP I64VMS MGMTAGENTS V3.4-1          Full LP     Installed
HP I64VMS OPENVMS V8.4               Platform    Installed
HP I64VMS SAMBA V1.2-ECO1            Full LP     Installed
HP I64VMS SMH V2.2-0                 Full LP     Installed
HP I64VMS SSL V1.4-476               Full LP     Installed
HP I64VMS TCPIP V5.7-13ECO4          Full LP     Installed
HP I64VMS TDC_RT V2.3-20             Full LP     Installed
HP I64VMS VMS V8.4                   Oper System Installed
HP I64VMS WBEMCIM V2.99-A100614      Full LP     Installed
HP I64VMS WBEMPROVIDERS V2.2-3       Full LP     Installed
HP VMS T4 V4.3-1                     Full LP     Installed
VMSPORTS I64VMS CURL V7.32           Full LP     Installed
VMSPORTS I64VMS ZLIB V1.2-8          Full LP     Installed
------------------------------------ ----------- ---------

$show sys/proc=smh*

00000485 SMHANDLER       HIB      8       43   0 00:00:00.00       270    280
000081F6 SMH$CPQHOST     LEF      5     4081   0 00:00:00.29       416    597
000081F7 SMH$CPQSYSINFO  LEF      5      719   0 00:00:00.05       252    280
000081F8 SMH$CPQSTDEQIP  LEF      5      679   0 00:00:00.05       264    299
000081F9 SMH$CPQHEALTH   LEF      5    13259   0 00:00:00.16       441    453
000081FA SMH$CPQTHRESH   LEF      5     1082   0 00:00:00.01       272    298
000081FB SMH$CPQNIC      LEF      6     1666   0 00:00:00.12       392    459
000081FD SMH$CPQSTORE    LEF      5     2913   0 00:00:00.25       279    335
000081FE SMH$CPQIDA      LEF      6      984   0 00:00:00.10       325    368

[robert70]

screenshot of smh "storage" page here

[Craig A Berry]

I don't know what (if anything) is wrong with SMH, but I suggest using SAS$UTIL to see what it thinks is attached to the RAID controller.

$ mcr sas$util

SAS> show controller

SAS> set controller <adapter name from above>

SAS> show disk/full

[robert70]

I get this .......................

Dave$ mcr sas$util
SAS>
SAS> show controller
A default controller is not set.  All matching controllers displayed
No controllers found matching request.

[Hoff]

Did this configuration ever work?   If that Smart Array P411 controller hasn't been configured, then not much will see anything connected past that controller.

For SMH,  you'll want to confirm the SMH version is V2.2 or later.

If VMS is seeing the disks and SMH isn't (and SMH is V2.2 or later), then this would likely be a problem with SMH or with its configuration.  If so, I'd probably next try an snmpwalk from another system, and see if that reports anything interesting.  (Here's an overview of the MSA$UTIL tool, which is similar to the SAS$UTIL stuff — MSA$UTIL is used for the bus controllers, AFAIK.)  Then ring up HP support.

As for SMH in general,  I'd be very skeptical around running that product where it's accessible from an untrusted network.  (I've duplicated a few of the SMH bugs against VMS, though those are unpatched AFAIK.)

[robert70]

Thanks Hoff

This setup has not worked before no - this is the 1st time I have tried to get SMH running on our Box

SMH version 2.2-1 is in use

I can aceess the disks with the MSA$util

also my mistake on the 1st post - i believe the controller connected to the D2700 disk enclosure is actually a P821 (controller pkc0:) - see below list of contollers and disks in D2700 enclosure

So I need to configure the P821 controller to get this working?

MSA> sh controller
A default controller is not set.  All matching controllers displayed

Adapter: _PKA0:
   P410i            (c) HP                       5001438018AC7B10 Software 5.78
   Port Address: 50014380-18ac7b10
Supported Redundancy Mode:   Not Available.
Cache:
   100 megabyte read cache   300 megabyte write cache
   Cache is GOOD, and Cache is enabled.
   No unflushed data in cache.
Battery:
   Battery is fully charged.

Adapter: _PKB0:
   P411             (c) HP                           PACCT9SYQV6L Software 6.22
   Port Address: 50014380-0844a4c0
Supported Redundancy Mode:   Not Available.
Cache:
   144 megabyte read/write cache
   Cache is not configured, and Cache is disabled.
   No unflushed data in cache.
Battery:
   Battery is not reported as present.

Adapter: _PKC0:
   P812             (c) HP                         PAGXQ0BRH3P031 Software 6.22
   Port Address: 50014380-240688b0
Supported Redundancy Mode:   Dual Domain.
         Dual Domain Mode:   Not Redundant.
Cache:
   228 megabyte read cache   684 megabyte write cache
   Cache is GOOD, and Cache is enabled.
   No unflushed data in cache.
Battery:
   Battery is fully charged.
MSA>
MSA> set controller pkb0
MSA> show disks
MSA> show disk
MSA> set controller pkc0
MSA> show disk

 SAS device                                              [Disk]
 Disk 201: bus: 1, Target id: 8, Port: 1E,  Box/Enclosure: 2, Bay: 1,  size 136.
73 [146.82]GB
  Disk 201, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 201, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 202: bus: 1, Target id: 9, Port: 1E,  Box/Enclosure: 2, Bay: 2,  size 136.
73 [146.82]GB
  Disk 202, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 202, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 203: bus: 1, Target id: 10, Port: 1E,  Box/Enclosure: 2, Bay: 3,  size 136
.73 [146.82]GB
  Disk 203, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 203, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 204: bus: 1, Target id: 11, Port: 1E,  Box/Enclosure: 2, Bay: 4,  size 136
.73 [146.82]GB
  Disk 204, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 204, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 205: bus: 1, Target id: 12, Port: 1E,  Box/Enclosure: 2, Bay: 5,  size 136
.73 [146.82]GB
  Disk 205, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 205, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 206: bus: 1, Target id: 13, Port: 1E,  Box/Enclosure: 2, Bay: 6,  size 136
.73 [146.82]GB
  Disk 206, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 206, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 207: bus: 1, Target id: 14, Port: 1E,  Box/Enclosure: 2, Bay: 7,  size 136
.73 [146.82]GB
  Disk 207, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 0.
  Disk 207, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 208: bus: 1, Target id: 15, Port: 1E,  Box/Enclosure: 2, Bay: 8,  size 136
.73 [146.82]GB
  Disk 208, Spare for unit 0

 SAS device                                              [Disk]
 Disk 209: bus: 2, Target id: 0, Port: 1E,  Box/Enclosure: 2, Bay: 9,  size 136.
73 [146.82]GB
  Disk 209, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 209, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 210: bus: 2, Target id: 1, Port: 1E,  Box/Enclosure: 2, Bay: 10,  size 136
.73 [146.82]GB
  Disk 210, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 210, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 211: bus: 2, Target id: 2, Port: 1E,  Box/Enclosure: 2, Bay: 11,  size 136
.73 [146.82]GB
  Disk 211, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 211, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 212: bus: 2, Target id: 3, Port: 1E,  Box/Enclosure: 2, Bay: 12,  size 136
.73 [146.82]GB
  Disk 212, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 212, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 213: bus: 2, Target id: 4, Port: 1E,  Box/Enclosure: 2, Bay: 13,  size 136
.73 [146.82]GB
  Disk 213, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 213, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 214: bus: 2, Target id: 5, Port: 1E,  Box/Enclosure: 2, Bay: 14,  size 136
.73 [146.82]GB
  Disk 214, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 214, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 215: bus: 2, Target id: 6, Port: 1E,  Box/Enclosure: 2, Bay: 15,  size 136
.73 [146.82]GB
  Disk 215, # 0, size 286683296 blocks, (136.70 [146.78] GB), Unit 1.
  Disk 215, # 1, size 656 blocks, (0.32 [0.34] MB), Unused.

 SAS device                                              [Disk]
 Disk 216: bus: 2, Target id: 7, Port: 1E,  Box/Enclosure: 2, Bay: 16,  size 136
.73 [146.82]GB
  Disk 216, Spare for unit 1

 SAS device                                              [Disk]
 Disk 217: bus: 2, Target id: 8, Port: 1E,  Box/Enclosure: 2, Bay: 17,  size 136
.73 [146.82]GB
  Disk 217, # 0, size 286677120 blocks, (136.70 [146.78] GB), Unit 2.
  Disk 217, # 1, size 6832 blocks, (3.34 [3.50] MB), Unused.

 SAS device                                              [Disk]
 Disk 218: bus: 2, Target id: 9, Port: 1E,  Box/Enclosure: 2, Bay: 18,  size 136
.73 [146.82]GB
  Disk 218, # 0, size 286677120 blocks, (136.70 [146.78] GB), Unit 2.
  Disk 218, # 1, size 6832 blocks, (3.34 [3.50] MB), Unused.
MSA>

[robert70]

as you say Hoff since vms is seeing the disks ok via the msa$util it looks like there is a problem with SMH

I will raise a call with HP and report back in due course

[Hoff]

Smart Array P821?  Do you mean P812?   That might not be supported by SMH.  

Also per the release notes I linked earlier, the system you're on requires SMH V2.2-1, and you apparently don't have that.

Start with the most current SMH.

Then ring HP.

[robert70 · Accepted solution]

yes sorry typo!

I do mean P812

and you are correct - the P812 is not supported on SMH

this has gone to engineering so hopefully get a fix/solution in the near future

I had updated the SMH to version 2.2-1.

Dave$ product show history
------------------------------------ ----------- ----------- --- -----------
PRODUCT                              KIT TYPE    OPERATION   VAL DATE
------------------------------------ ----------- ----------- --- -----------
HP I64VMS VMS84I_UPDATE V6.0         Patch       Install     Val 30-JUL-2014
HP I64VMS VMS84I_FIBRE_SCSI V6.0     Patch       Install     Val 29-JUL-2014
HP I64VMS VMS84I_UPDATE V9.0         Patch       Install     Val 29-JUL-2014
HP I64VMS VMS84I_PCSI V4.0           Patch       Install     Val 29-JUL-2014
HP I64VMS SMHPAT V2.2-1              Patch       Install     Val 28-JUL-2014

.

.

.

.

.

.

.

.

Oddly enough I also have a P410i adapter connected to the internal disk rack of the rx2800 i2 

and SMH cant see this either ! - even though it is supposed to be supported.

All the SMH sees is the P411 connected to our Tape Drive!

Will update this in the future with any fix/solution to these problems

[robert70]

HP Engineering now have a fixfor this and will be released on "SMHv2.2-2" in the near future

In the meantime I have a temp fix if anyone needs it urgently