Installing Vendor Hardware agents onto Puredisk

[Lee_C]

Hello,

Does anyone have experience of installing vendor specific hardware agents e.g. HP management agents onto PureDisk for monitoring purposes?

Can you let me know if you had any issues with them?

Can you also let me know if you had any issues with monitoring direct attached storage, in our case HP MSA60 shelves?

Thanks

[S_Williamson]

Hi Lee

As far as I am aware this is not possible. The PDOS is a cut down SUSE and it doesnt seem to work and if it did work it might break next time PDOS was upgraded. We have tested it before with no success.

What we have done in this instance is to install some HP CLI utils

# check for existing rpms
rpm -qa | grep hpa
# remove any older versions of the hpacucli & hpaducli utilities, using rpm -e

# install the new rpms
rpm -i hpacucli-8.70-8.0.noarch.rpm
rpm -i hpaducli-8.60-8.0.noarch.rpm

Then run the command line like this. This is one of ours with a MSA70 attached and currently has a faulty disk. We feed the output into our monitoring utility which looks for the word "Failed" and then flags an error for us.

[servername]:~ # hpacucli ctrl all show config

Smart Array P400i in Slot 0 (Embedded)    (sn: PH87MQ8477     )

   array A (SAS, Unused Space: 0 MB)


      logicaldrive 1 (136.7 GB, RAID 1, OK)

      physicaldrive 1I:1:1 (port 1I:box 1:bay 1, SAS, 146 GB, OK)
      physicaldrive 1I:1:2 (port 1I:box 1:bay 2, SAS, 146 GB, OK)


Smart Array P800 in Slot 2                (sn: PAFGF0P9SY8130)

   array A (SAS, Unused Space: 0 MB)


      logicaldrive 1 (5.7 TB, RAID 6 (ADG), OK)

      physicaldrive 1E:1:1 (port 1E:box 1:bay 1, SAS, 300 GB, OK)
      physicaldrive 1E:1:2 (port 1E:box 1:bay 2, SAS, 300 GB, OK)
      physicaldrive 1E:1:4 (port 1E:box 1:bay 4, SAS, 300 GB, OK)
      physicaldrive 1E:1:5 (port 1E:box 1:bay 5, SAS, 300 GB, OK)
      physicaldrive 1E:1:6 (port 1E:box 1:bay 6, SAS, 300 GB, OK)
      physicaldrive 1E:1:7 (port 1E:box 1:bay 7, SAS, 300 GB, OK)
      physicaldrive 1E:1:8 (port 1E:box 1:bay 8, SAS, 300 GB, OK)
      physicaldrive 1E:1:9 (port 1E:box 1:bay 9, SAS, 300 GB, OK)
      physicaldrive 1E:1:10 (port 1E:box 1:bay 10, SAS, 300 GB, OK)
      physicaldrive 1E:1:11 (port 1E:box 1:bay 11, SAS, 300 GB, OK)
      physicaldrive 1E:1:12 (port 1E:box 1:bay 12, SAS, 300 GB, OK)
      physicaldrive 1E:1:13 (port 1E:box 1:bay 13, SAS, 300 GB, OK)
      physicaldrive 1E:1:14 (port 1E:box 1:bay 14, SAS, 300 GB, OK)
      physicaldrive 1E:1:15 (port 1E:box 1:bay 15, SAS, 300 GB, OK)
      physicaldrive 1E:1:16 (port 1E:box 1:bay 16, SAS, 300 GB, Failed)
      physicaldrive 1E:1:17 (port 1E:box 1:bay 17, SAS, 300 GB, OK)
      physicaldrive 1E:1:18 (port 1E:box 1:bay 18, SAS, 300 GB, OK)
      physicaldrive 1E:1:19 (port 1E:box 1:bay 19, SAS, 300 GB, OK)
      physicaldrive 1E:1:20 (port 1E:box 1:bay 20, SAS, 300 GB, OK)
      physicaldrive 1E:1:21 (port 1E:box 1:bay 21, SAS, 300 GB, OK)
      physicaldrive 1E:1:22 (port 1E:box 1:bay 22, SAS, 300 GB, OK)
      physicaldrive 1E:1:23 (port 1E:box 1:bay 23, SAS, 300 GB, OK)
      physicaldrive 1E:1:24 (port 1E:box 1:bay 24, SAS, 300 GB, OK)
      physicaldrive 1E:1:25 (port 1E:box 1:bay 25, SAS, 300 GB, OK, active spare)

   unassigned

      physicaldrive 1E:1:3 (port 1E:box 1:bay 3, SAS, 300 GB, OK)

   Expander 248 (WWID: 5001438004ED0E00, Port: 1E, Box: 1)

   Expander 250 (WWID: 500143800607F13F)

   Enclosure SEP (Vendor ID HP, Model MSA70) 247 (WWID: 5001438004ED0E25, Port: 1E, Box: 1)

   SEP (Vendor ID HP, Model P800) 249 (WWID: 500143800607F13E)

[teiva-boy]

PureDisk is a closed OS, while on an open platform, it's no different than say a DataDomain or Exagrid box.  Which means no user installed apps.

[Lee_C]

Thanks for your feedback.  I was curious as to how you fed the output to your monitoring system.

[S_Williamson]

One of the guys here wrote a perl script and setup a cron job to run it every 15 minutes. They basically executes the command line shown above.