monitor primergy servers with esx

[Natxo Asenjo]

hi,

I have done some tests. One needs the RAID.mib file and this file is
only in the windows package for serverviewraid (tsk, tsk).

Anyway, once we have this file we can test stuff.

Important OIDS:
.1.3.6.1.4.1.231.2.49.1.5.2.1 ->
.iso.org.dod.internet.private.enterprises.sni.sniProductMibs.fscRAIDMIB.svrObjects.svrPhysicalDeviceInfo.svrPhysicalDeviceTable.svrPhysicalDeviceEntry

.1.3.6.1.4.1.231.2.49.1.3 ->
.iso.org.dod.internet.private.enterprises.sni.sniProductMibs.fscRAIDMIB.svrObjects.svrStatus

Situation 1: disks are online and working fine:

$ snmpwalk server -c public -v 1 -m FSC-RAID-MIB .1.3.6.1.4.1.231.2.49.1.3

FSC-RAID-MIB::svrStatusLogicalDrives.0 = INTEGER: ok(1)
FSC-RAID-MIB::svrStatusPhysicalDevices.0 = INTEGER: ok(1)
FSC-RAID-MIB::svrStatusControllers.0 = INTEGER: ok(1)
FSC-RAID-MIB::svrStatusOverall.0 = INTEGER: ok(1)

[jose at pc2668-210307 mibs]$ snmpwalk izvm01 -c public -v 1 -m
FSC-RAID-MIB .1.3.6.1.4.1.231.2.49.1.5.2.1

FSC-RAID-MIB::svrPhysicalDeviceCtrlNr.1.1.0.0 = INTEGER: 1
FSC-RAID-MIB::svrPhysicalDeviceCtrlNr.1.2.3.0 = INTEGER: 1
FSC-RAID-MIB::svrPhysicalDeviceChannel.1.1.0.0 = INTEGER: 1
FSC-RAID-MIB::svrPhysicalDeviceChannel.1.2.3.0 = INTEGER: 2
FSC-RAID-MIB::svrPhysicalDeviceTarget.1.1.0.0 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceTarget.1.2.3.0 = INTEGER: 3
FSC-RAID-MIB::svrPhysicalDeviceLUN.1.1.0.0 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceLUN.1.2.3.0 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceModelName.1.1.0.0 = STRING: "ST373455SS"
FSC-RAID-MIB::svrPhysicalDeviceModelName.1.2.3.0 = STRING: "ST373455SS"
FSC-RAID-MIB::svrPhysicalDeviceVendorName.1.1.0.0 = STRING: "SEAGATE"
FSC-RAID-MIB::svrPhysicalDeviceVendorName.1.2.3.0 = STRING: "SEAGATE"
FSC-RAID-MIB::svrPhysicalDeviceCapacity.1.1.0.0 = INTEGER: 68
FSC-RAID-MIB::svrPhysicalDeviceCapacity.1.2.3.0 = INTEGER: 68
FSC-RAID-MIB::svrPhysicalDeviceMaxTransferRate.1.1.0.0 = INTEGER: 300
FSC-RAID-MIB::svrPhysicalDeviceMaxTransferRate.1.2.3.0 = INTEGER: 300
FSC-RAID-MIB::svrPhysicalDeviceType.1.1.0.0 = INTEGER: disk(2)
FSC-RAID-MIB::svrPhysicalDeviceType.1.2.3.0 = INTEGER: disk(2)
FSC-RAID-MIB::svrPhysicalDeviceConfiguredDisk.1.1.0.0 = INTEGER: true(2)
FSC-RAID-MIB::svrPhysicalDeviceConfiguredDisk.1.2.3.0 = INTEGER: true(2)
FSC-RAID-MIB::svrPhysicalDeviceInterface.1.1.0.0 = INTEGER: sas(6)
FSC-RAID-MIB::svrPhysicalDeviceInterface.1.2.3.0 = INTEGER: sas(6)
FSC-RAID-MIB::svrPhysicalDeviceErrors.1.1.0.0 = Counter32: 0
FSC-RAID-MIB::svrPhysicalDeviceErrors.1.2.3.0 = Counter32: 0
FSC-RAID-MIB::svrPhysicalDeviceNrBadBlocks.1.1.0.0 = Counter32: 0
FSC-RAID-MIB::svrPhysicalDeviceNrBadBlocks.1.2.3.0 = Counter32: 0
FSC-RAID-MIB::svrPhysicalDeviceSmartStatus.1.1.0.0 = INTEGER: ok(1)
FSC-RAID-MIB::svrPhysicalDeviceSmartStatus.1.2.3.0 = INTEGER: ok(1)
FSC-RAID-MIB::svrPhysicalDeviceStatus.1.1.0.0 = INTEGER: online(3)
FSC-RAID-MIB::svrPhysicalDeviceStatus.1.2.3.0 = INTEGER: online(3)
FSC-RAID-MIB::svrPhysicalDeviceFirmwareRevision.1.1.0.0 = STRING: "1651"
FSC-RAID-MIB::svrPhysicalDeviceFirmwareRevision.1.2.3.0 = STRING: "1651"
FSC-RAID-MIB::svrPhysicalDeviceSerialNumber.1.1.0.0 = STRING: "3LQ0DA03"
FSC-RAID-MIB::svrPhysicalDeviceSerialNumber.1.2.3.0 = STRING: "3LQ0DAD7"
FSC-RAID-MIB::svrPhysicalDeviceForeignConfig.1.1.0.0 = INTEGER: false(1)
FSC-RAID-MIB::svrPhysicalDeviceForeignConfig.1.2.3.0 = INTEGER: false(1)
FSC-RAID-MIB::svrPhysicalDeviceIdx.1.1.0.0 = INTEGER: 11
FSC-RAID-MIB::svrPhysicalDeviceIdx.1.2.3.0 = INTEGER: 12
FSC-RAID-MIB::svrPhysicalDeviceEntry.20.1.1.0.0 = INTEGER: 4
FSC-RAID-MIB::svrPhysicalDeviceEntry.20.1.2.3.0 = INTEGER: 4
FSC-RAID-MIB::svrPhysicalDeviceEntry.21.1.1.0.0 = INTEGER: 70007
FSC-RAID-MIB::svrPhysicalDeviceEntry.21.1.2.3.0 = INTEGER: 70007

Disks are online

Situation 2: I remove one disk from its bay

$ snmpwalk server -c public -v 1 -m FSC-RAID-MIB .1.3.6.1.4.1.231.2.49.1.3
FSC-RAID-MIB::svrStatusLogicalDrives.0 = INTEGER: prefailure(2)
FSC-RAID-MIB::svrStatusPhysicalDevices.0 = INTEGER: failure(3)
FSC-RAID-MIB::svrStatusControllers.0 = INTEGER: prefailure(2)
FSC-RAID-MIB::svrStatusOverall.0 = INTEGER: prefailure(2)

Everything is 'prefailure', except for physicaldevices, it's a
'failure' (disk is physically removed from the bay). I forgot to check
the other OID for this one, I'll post the results later.

Situation 3: 'failed' disk is back in bay, rebuilding starts:

$ snmpwalk server -c public -v 1 -m FSC-RAID-MIB .1.3.6.1.4.1.231.2.49.1.3

FSC-RAID-MIB::svrStatusLogicalDrives.0 = INTEGER: prefailure(2)
FSC-RAID-MIB::svrStatusPhysicalDevices.0 = INTEGER: ok(1)
FSC-RAID-MIB::svrStatusControllers.0 = INTEGER: prefailure(2)
FSC-RAID-MIB::svrStatusOverall.0 = INTEGER: prefailure(2)

everthing is 'prefailure' except for svrStatusPhysicalDevices.0, it is
'ok', disks is in bay.

$ snmpwalk server -c public -v 1 -m FSC-RAID-MIB .1.3.6.1.4.1.231.2.49.1.5.2.1
FSC-RAID-MIB::svrPhysicalDeviceCtrlNr.1.0.0.0 = INTEGER: 1
FSC-RAID-MIB::svrPhysicalDeviceCtrlNr.1.3.0.3 = INTEGER: 1
FSC-RAID-MIB::svrPhysicalDeviceChannel.1.0.0.0 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceChannel.1.3.0.3 = INTEGER: 3
FSC-RAID-MIB::svrPhysicalDeviceTarget.1.0.0.0 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceTarget.1.3.0.3 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceLUN.1.0.0.0 = INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceLUN.1.3.0.3 = INTEGER: 3
FSC-RAID-MIB::svrPhysicalDeviceModelName.1.0.0.0 = STRING: "MAX3073RC"
FSC-RAID-MIB::svrPhysicalDeviceModelName.1.3.0.3 = STRING: "ST373455SS"
FSC-RAID-MIB::svrPhysicalDeviceVendorName.1.0.0.0 = STRING: "FUJITSU"
FSC-RAID-MIB::svrPhysicalDeviceVendorName.1.3.0.3 = STRING: "SEAGATE"
FSC-RAID-MIB::svrPhysicalDeviceCapacity.1.0.0.0 = INTEGER: 68
FSC-RAID-MIB::svrPhysicalDeviceCapacity.1.3.0.3 = INTEGER: 68
FSC-RAID-MIB::svrPhysicalDeviceMaxTransferRate.1.0.0.0 = INTEGER: 300
FSC-RAID-MIB::svrPhysicalDeviceMaxTransferRate.1.3.0.3 = INTEGER: 300
FSC-RAID-MIB::svrPhysicalDeviceType.1.0.0.0 = INTEGER: disk(2)
FSC-RAID-MIB::svrPhysicalDeviceType.1.3.0.3 = INTEGER: disk(2)
FSC-RAID-MIB::svrPhysicalDeviceConfiguredDisk.1.0.0.0 = INTEGER: false(1)
FSC-RAID-MIB::svrPhysicalDeviceConfiguredDisk.1.3.0.3 = INTEGER: false(1)
FSC-RAID-MIB::svrPhysicalDeviceInterface.1.0.0.0 = INTEGER: sas(6)
FSC-RAID-MIB::svrPhysicalDeviceInterface.1.3.0.3 = INTEGER: sas(6)
FSC-RAID-MIB::svrPhysicalDeviceErrors.1.0.0.0 = Wrong Type (should be
Counter32): INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceErrors.1.3.0.3 = Wrong Type (should be
Counter32): INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceNrBadBlocks.1.0.0.0 = Wrong Type
(should be Counter32): INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceNrBadBlocks.1.3.0.3 = Wrong Type
(should be Counter32): INTEGER: 0
FSC-RAID-MIB::svrPhysicalDeviceSmartStatus.1.0.0.0 = INTEGER:
smartNotAvailable(3)
FSC-RAID-MIB::svrPhysicalDeviceSmartStatus.1.3.0.3 = INTEGER:
smartNotAvailable(3)
FSC-RAID-MIB::svrPhysicalDeviceStatus.1.0.0.0 = INTEGER: rebuilding(6)
FSC-RAID-MIB::svrPhysicalDeviceStatus.1.3.0.3 = INTEGER: online(3)
FSC-RAID-MIB::svrPhysicalDeviceFirmwareRevision.1.0.0.0 = STRING: "5205"
FSC-RAID-MIB::svrPhysicalDeviceFirmwareRevision.1.3.0.3 = STRING: "1652"
FSC-RAID-MIB::svrPhysicalDeviceSerialNumber.1.0.0.0 = STRING: "DQD7P7201YDH@#21"
FSC-RAID-MIB::svrPhysicalDeviceSerialNumber.1.3.0.3 = STRING: "3LQ22A92"
FSC-RAID-MIB::svrPhysicalDeviceForeignConfig.1.0.0.0 = INTEGER: false(1)
FSC-RAID-MIB::svrPhysicalDeviceForeignConfig.1.3.0.3 = INTEGER: false(1)
FSC-RAID-MIB::svrPhysicalDeviceIdx.1.0.0.0 = INTEGER: 12
FSC-RAID-MIB::svrPhysicalDeviceIdx.1.3.0.3 = INTEGER: 11

the svrPhysicalDeviceStatus of one disk is 'online', the other is 'rebuilding',

With this info I will try to write a plugin to monitor the fujitsu
raid stuff with snmp. It works with esx and windows 2k3, I see for
now. I suppose it will also work with linux.

-- 
Natxo Asenjo

------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null