Re: [Nagios-users] monitor primergy servers with esx
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) [j...@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
Re: [Nagios-users] monitor primergy servers with esx
On Tue, Apr 7, 2009 at 9:11 PM, Albrecht Dreß wrote: > What exactly is your 'disk array'? A SAN? I have a script for nagios 3 > which checks the sensors (temperature, voltages, etc.) via SNMPv1 on a fsc > FibreCat SX san and a Brocade fibre switch. I don't know, though, how I can > check the disk health this way. this is just the system installation of the esx servers. It's a raid 1 sas array. I need to know when the disks go south because the whole datacenter is moving to a cybercenter where we longer can rely on the typical visual checks when changing the tapes. > I think I will upload that script to nagiosexchange, if you think you could > use it... please, do upload it. I have (at this point) no use for it, but I am sure someone else will. Nagios is great because of all the plugins. -- Natxo -- 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@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
Re: [Nagios-users] monitor primergy servers with esx
On Tue, Apr 7, 2009 at 7:58 PM, Giorgio Zarrelli wrote: > Hi, > > as I told you, all depends on the richness of the MIB. Find the MIB for your > server and send it to me. With that in my hands I will be able to tell you if > you can do that. Hi Giorgio, thanks again for your input. I have found a RAID.mib (unfortunately, it is not in the esx rpm package, but in the windows package). I have copied it to the net-snmp collection of mibs and am reviewing it. If you will like to have it I will send it off list (it's a bit big to send to everyone on the list). I am going through it and it looks promising. .iso.org.dod.internet.private.enterprises.sni.sniProductMibs.fscRAIDMIB.svrObjects.svrStatus.svrStatusLogicalDrives.0 = ok .iso.org.dod.internet.private.enterprises.sni.sniProductMibs.fscRAIDMIB.svrObjects.svrStatus.svrStatusPhysicalDevices.0 = ok Tomorroy I will try removing some disks from the server and check if those result change as well when the disks are not there. As soon as I get a working script to check the health of the disks I will post it for review in nagiosexchange (I can code some Perl, but am no Perl expert, just a sysadmin trying to control a crazy environment). 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@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
Re: [Nagios-users] monitor primergy servers with esx
Am 07.04.09 19:58 schrieb(en) Giorgio Zarrelli: What I need is monitoring the health of the disk array. Is it possible to do that with snmp What exactly is your 'disk array'? A SAN? I have a script for nagios 3 which checks the sensors (temperature, voltages, etc.) via SNMPv1 on a fsc FibreCat SX san and a Brocade fibre switch. I don't know, though, how I can check the disk health this way. I think I will upload that script to nagiosexchange, if you think you could use it... Best, Albrecht. pgpm86zd8IcVS.pgp Description: PGP signature -- 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@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
Re: [Nagios-users] monitor primergy servers with esx
Hi, as I told you, all depends on the richness of the MIB. Find the MIB for your server and send it to me. With that in my hands I will be able to tell you if you can do that. Giorgio Natxo Asenjo (natxo.ase...@gmail.com) scritto: > > I do not mean to be rude, thanks for your input. > > What I need is monitoring the health of the disk array. Is it possible > to do that with snmp > as it is with the the command amcli --list? > > TIA, > > 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@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 > -- 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@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
Re: [Nagios-users] monitor primergy servers with esx
On Tue, Apr 7, 2009 at 5:01 PM, Giorgio Zarrelli wrote: > Hi, [knip] > To collect a value, for bandwidth, let's say, I use such a string: I do not mean to be rude, thanks for your input. What I need is monitoring the health of the disk array. Is it possible to do that with snmp as it is with the the command amcli --list? TIA, 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@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
Re: [Nagios-users] monitor primergy servers with esx
Hi,
Hi,
first find the right mib describing your hardware. Second step, enable snmp v3
on your fujitsu and at the end you write a script.
Actually I wrote a nagios plugin to check memory and cpu of F5 BigIP and
another for monitoring bandwidth via snmp. all resides on finding the right
oids which match the values you are going to collect through snmpget.
To collect a value, for bandwidth, let's say, I use such a string:
SPEED=`/usr/bin/snmpget -v 3 -t 1 -r 5 -m '' -v 3 -l authPriv -a MD5 -u
${LOGIN} -A ${PASSWORD} -x DES -X ${PASSWORD} ${HOST}:161
IF-MIB::ifSpeed.${IFINDEX} | cut -d " " -f 4`
Giorgio
> Has anyone gotten to monitor it through snmp? Would you care to show how? ;)
>
> --
> Groeten,
> J.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@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
>
--
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@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
[Nagios-users] monitor primergy servers with esx
hi, I have some fujitsu-siemens primergy rx-300 s3 that I monitor with the check_fsc.pl and snmp. This works fine. I have installed the serverviewraid manager tool from fujitusu siemens so that I can monitor if the disks are ok. This works. But, here comes the question: how do I monitor the health of the array controller if I cannot install nagios-nrpe in the boxes? installing nrpe is not supported by vmware, so the option is pretty closed. I monitor citrix servers with the same tool, amcli and a batch script through nrpe. Has anyone gotten to monitor it through snmp? Would you care to show how? ;) -- Groeten, J.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@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
