Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Array Status

I saw this post awhile back , and thought I would like to setup the Array Status for a few of my HP Servers,mainly my DL360 G5, G3's I also have a new DL360 G6

I tried so many MIBS and just cant seem to extract the info I want such as

Array_Drive_Bay ; Drive Size and Array Drive Bay Status

I tried mib walking using the Network Tool Set , also the ones suggested in the older post ... all to no avail ... My goal is to setup an alert so if I lose anyone drive within an array it will send an email

Anyone have any success in this? ... I can Disk Volumes details Drive Info , just cant seem to find the proper mibs for the Array stuff .. any help would be appreciated

Missing Array Status.JPG

Find more posts tagged with

Accepted answers

All comments

jbaulsir

Here are the pollers I use for monitoring the array controller card (SCSI) and an external array. Looks like you using iSCSI could you provide more details on the setup? Do you have an external array connected via a iSCSI team?

PS. Change HP_Array.txt to HP_Array.UnDP

HP_Array.txt

TohAtin

JB,

I am really more interested in the internal drives and not the iscsi arrays .. most of my servers are setup for the internal drives as raid 5 or 1+0 depending on the applications they run ..

chris.newton

If you look under content exchange I have created some UNDP's for hp servers that include your requirements, have a look and see if they help saves you the hassle of searching for them.

TohAtin

Chris,

Bingo ... those mibs is what I was after .. thanks again ... we can close this thread