I have been using the check_openmanage Nagios plugin for several years and
am very happy with the way it works. However, I do have a question about
one of the blacklist items, specifically the pdisk_cert item. This question
arose because I noticed a difference between the way check_openmanage
repor
Hello Trond,
First of all, I want to thank you for the excellent plugin and continued
support and development.
The purpose of this is to suggest including a whitelist option to do the
opposite of the blacklist option.
This will allow anyone to create checks with higher granularity.
For example
"Weberskirch, Timo" writes:
> the check_openmanage –no-storage options works (surely without any physical
> disk… :( ).
>
> I was on the phone with the Dell Pro Support. They told me that the MD3
> only schows the raid disk Information (not the physical
> disk informations) to external devi
Hello Trond,
the check_openmanage -no-storage options works (surely without any physical
disk... :( ).
I was on the phone with the Dell Pro Support. They told me that the MD3
only schows the raid disk Information (not the physical disk informations) to
external devices.
Also they told me t
"Weberskirch, Timo" writes:
> thank you all for your fast and helpful response. Unfortunately the problem
> persists.
>
> Is there a way to filter out the (in my opinion faulty) SAS card?
Storage components are tightly interconnected, so from the plugin side
your only option is to not check st
Hallo everyone,
thank you all for your fast and helpful response. Unfortunately the problem
persists.
Is there a way to filter out the (in my opinion faulty) SAS card?
Regards,
Timo
--
Get 100% visibility into Java/.NE
Rich writes:
> Usually, when I've seen this, it's been after doing an upgrade of an
> existing OMSA install (<= 6.x to 7.x).
>
> In general, I haven't found a good way to resolve it other than
> automating a complete uninstall of OMSA prior to installing the newer
> version.
Yes, I think the log
Usually, when I've seen this, it's been after doing an upgrade of an
existing OMSA install (<= 6.x to 7.x).
In general, I haven't found a good way to resolve it other than automating
a complete uninstall of OMSA prior to installing the newer version.
- Rih
On Wed, Aug 7, 2013 at 8:09 AM, Webers
Hello Trond,
Thank you for your fast response!
I'am new to the userlist and I hope my answer will appear in the right thread.
It's a Server 2012 Standard based SQL Failovercluster.
On each node I can see all physical and virtual disks in the web console.
Maybe there is a problem with the 6 Gbps
"Weberskirch, Timo" writes:
> maybe one of you has the same problem with the check_openmanage plugin…
>
> Last week we installed two new Dell PowerEdge R720 with OMSA v 7.3.0
> (check_openmange version: 3.7.10).
>
> Everytime I try to check my Server I get this error message:
>
> “SNMP ERROR [sto
Hallo everyone
maybe one of you has the same problem with the check_openmanage plugin...
Last week we installed two new Dell PowerEdge R720 with OMSA v 7.3.0
(check_openmange version: 3.7.10).
Everytime I try to check my Server I get this error message:
"SNMP ERROR [storage / pdisk]: Requested
"John Skarbek" writes:
> I?ve recently deployed the check_openmanage script and it works very well.
> Except for hosts that run esxi. Unless I?m doing something wrong.
You're not doing anything wrong. Openmanage, when deployed on ESXi,
doesn't have the necessary capabilities for it to work.
Good Morning,
I've recently deployed the check_openmanage script and it works very
well. Except for hosts that run esxi. Unless I'm doing something
wrong.
I've discovered that Open Manage doesn't broadcast it's OID's through
ESXi like it would if it were a linux or windows host. Howeve
rator
rwer...@pomwonderful.com
559.521.5089
From: csant...@noz.fr [csant...@noz.fr]
Sent: Thursday, May 16, 2013 6:59 AM
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_openmanage on ESXi 5.0
Hello,
I'm using nagios with the check_openma
Hello,
I'm using nagios with the check_openmanage plugins to checks my ESX
servers running on Dell PowerEdge R710.
The plugin working fine whith my ESX on version 4.1 but my problem is that
I recently upgrade it on VMware ESXi 5.0.0 Update 2 and then
check_openmanage plugin return this error:
"Bob The Junkie" writes:
> I m using Nagios and Check_Openmange to keep an eye on some Dell R710 servers
> we ve recently acquired, and I m having problems trying to stop warnings with
> non-dell certified drives appearing in the alert log.
>
> I ve separated out the different components on the s
Hi there,
I'm using Nagios and Check_Openmange to keep an eye on some Dell R710 servers
we've recently acquired, and I'm having problems trying to stop warnings with
non-dell certified drives appearing in the alert log.
I've separated out the different components on the servers to check into
Andrew Daugherity writes:
>> Please try this version (named 3.7.8-beta2) and let me know if it works
>> around your problem. Usage:
>>
>> check_openmange --snmp-timeout
>
> I think I fixed my problem (for the time being at least) by restarting
> OMSA on that server. Restarting snmpd didn't s
On Tue, Dec 11, 2012 at 06:35:35PM +, Andrew Daugherity wrote:
> Regarding your fix:
> The timeout option does appear to get passed to SNMP, however the
> actual timeout is twice what is specified. E.g. --snmp=timeout=1,
> get SNMP critical message after 2 seconds; --snmp-timeout=14, SNMP
> cr
Trond Hasle Amundsen writes:
> > A new option to specify the SNMP object timeout would be easy to add,
> > and is in my opinion a cleaner approach than just passing the plugin
> > timeout.
>
> Such an option is now implemented in the Git version:
>
> http://git.uio.no/git/?p=check_openmanage.g
Trond Hasle Amundsen writes:
> A new option to specify the SNMP object timeout would be easy to add,
> and is in my opinion a cleaner approach than just passing the plugin
> timeout.
Such an option is now implemented in the Git version:
http://git.uio.no/git/?p=check_openmanage.git;a=commit;
Andrew Daugherity writes:
> I'm troubleshooting an issue where one server is occasionally not responding
> (I think it's a firewall or snmpd issue, not this plugin), and I noticed that
> changing the timeout option to check_openmanage did not affect how long it
> took before receiving the
>
I'm troubleshooting an issue where one server is occasionally not responding (I
think it's a firewall or snmpd issue, not this plugin), and I noticed that
changing the timeout option to check_openmanage did not affect how long it took
before receiving the
SNMP CRITICAL: No response from remote
Hello,
We have updated our servers today and after updating the plugin
check_openmanage began to display an error message:
*Problem running 'omreport storage controller': Error! Invalid name=value
pair: controller*
If we launch the plugin, without disk checks, all is well:
*root@dell:~# /
t; *Phil Randal*
>
> *Infrastructure Engineer*
> *Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT*
>
> Tel: 01432 260415 | Email: phil.ran...@hoopleltd.co.uk
>
>
>
> *From:* Hölzel, Arnold [mailto:arnold.hol...@kpn.com]
> *Sent:* 16 August 2012 16:00
> *To:* nagios-us
Phil Randal
Infrastructure Engineer
Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT
Tel: 01432 260415 | Email: phil.ran...@hoopleltd.co.uk
From: Hölzel, Arnold [mailto:arnold.hol...@kpn.com]
Sent: 16 August 2012 16:00
To: nagios-users@lists.sourceforge.net
Subject: [Nagios-users] check_openm
All,
I don't know if anyone else already posted this, I just joined the mail list.
We have been using check_openmanage (brilliant piece of work!) to check the
hardware status of our Dell machines, lately we are moving from ESX 4 to ESXi 5
and found that the check_openmanage check could not help
Andrew Daugherity writes:
> Simple fix -- the package is named 'docbook-xsl-stylesheets' instead
> of 'docbook-style-xsl'. I added a variable for this to the global "if
> suse" section.
Thanks Andrew, applied and pushed to master.
Cheers,
--
Trond H. Amundsen
Center for Information Technolog
Simple fix -- the package is named 'docbook-xsl-stylesheets' instead of
'docbook-style-xsl'. I added a variable for this to the global "if suse"
section.
Diff attached.
Thanks,
Andrew Daugherity
Systems Analyst
Division of Research, Texas A&M University
check_openmanage-docbook.diff
Desc
Tobias Dinse stegbauer.info> writes:
>
> Yes, i can run all commands on the local system without errors. Thats
> why I m confused. I also can execute the check_openmanage Script manual
> on the local Maschine as Nagios User without problems. I think it must
> be an Problem between the script
Am 01.02.2012 um 17:56 schrieb Trond Hasle Amundsen:
Helmut Wollmersdorfer writes:
[...]
Thus it seems that check_openmanage works correctly. Also the disk-
array seems to work correctly (no error messages in the logs).
Is this some sort of wrong diagnostic from the firmware/controller?
Helmut Wollmersdorfer writes:
> Physical Disk 0:0:0 [Dell WDC WD1003FBYX-18Y7B0, 1.0TB] on ctrl 0
> needs attention: Undefined value 4096
Hello Helmut,
The "state" value for physical disks via SNMP is an integer, which is
translated by the plugin. There are a few defined values, and 4096 is
n
pport have changed the disk with a new.
This appeared on a PowerEdge R610 and i use the check_openmanage 3.6.5
Sincerly,
David
- Mail original -
De: "Helmut Wollmersdorfer"
À: "Nagios Users List"
Envoyé: Mercredi 1 Février 2012 16:46:21
Objet: [Nagios-users] c
Hi,
since some days I get
Physical Disk 0:0:0 [Dell WDC WD1003FBYX-18Y7B0, 1.0TB] on ctrl 0
needs attention: Undefined value 4096Physical Disk 0:0:1 [Dell
WDC WD1003FBYX-18Y7B0, 1.0TB] on ctrl 0 needs attention: Undefined
value 4096Physical Disk 0:0:2 [Dell WDC WD1003FBYX-18Y7B0, 1.0TB]
Yes, i can run all commands on the local system without errors. Thats
why I m confused. I also can execute the check_openmanage Script manual
on the local Maschine as Nagios User without problems. I think it must
be an Problem between the script output. But why it works on other
r710´s with deb
2012/1/18 Tobias Dinse :
> Hi all,
>
> i have seen that I can use this mailing list for bug reports or
> questions about the plugin "check_openmanage" from
> http://folk.uio.no/trondham/software/check_openmanage.html We have
> different Dell Servers and the Plugin mostly works. Today I have
> insta
Hi all,
i have seen that I can use this mailing list for bug reports or
questions about the plugin "check_openmanage" from
http://folk.uio.no/trondham/software/check_openmanage.html We have
different Dell Servers and the Plugin mostly works. Today I have
installed OMSA 6.5 on a Debian Squeeze
"Daugherity, Andrew W" writes:
> First of all, thanks for making this plugin. It works well and is
> very handy. As requested in the documentation, I am sending this to
> the nagios-users list rather than directly to the author.
Hello Andrew,
Excellent :) Usually a public forum is better, whe
(Resending as apparently my first attempt didn't make it through.)
First of all, thanks for making this plugin. It works well and is very handy.
As requested in the documentation, I am sending this to the nagios-users list
rather than directly to the author.
With some minor modifications, t
Corcoran Smith writes:
> First message, so please excuse any failures in format, etc!
>
> Got two issues with two boxes (out of 160!) using check_openmanage:
>
> 1) Couldn't run command 'c:\pro... ' etc
> 2) U nrecognized character xA8: marked by <-- HERE after <-- HERE near column
> 1 at /loade
Hi,
First message, so please excuse any failures in format, etc!
Got two issues with two boxes (out of 160!) using check_openmanage:
1) Couldn't run command 'c:\pro... ' etc
2) U nrecognized character xA8: marked by <-- HERE after <-- HERE near column 1
at /loader/HASH(0xa7c42c)/UNIVERSAL.pm li
the entrox writes:
> i've been using the check_openmanage script to monitor about two dozens of
> dell
> servers without a hitch (all Windows based) and we just set up about 15 or so
> new servers but this time running CentOS, i of course installed the OMSA via
> Dell's repository and also enabl
Lois Garcia writes:
> This is the output from "omreport chassis pwrsupplies -fmt ssv":
>
> C:\Users\Administrator>omreport chassis pwrsupplies -fmt ssv
> Power Supplies Information
>
> Power Supply Redundancy
> Redundancy Status;Lost
>
> Individual Power Supply Elements
>
> Index;Status;Location;
This is the output from "omreport chassis pwrsupplies -fmt ssv":
C:\Users\Administrator>omreport chassis pwrsupplies -fmt ssv
Power Supplies Information
Power Supply Redundancy
Redundancy Status;Lost
Individual Power Supply Elements
Index;Status;Location;Type;Rated Input Wattage;Maximum Output
Lois Garcia writes:
> Thank you, Trond! It looks like a power supply problem. I will take the issue
> to Dell:
>
> C:\Users\Administrator>omreport system
> Health
>
> SEVERITY : COMPONENT
> Critical : Main System Chassis
>
>
> C:\Users\Administrator>omreport chassis
> Health
>
> Main System Chass
Thank you, Trond! It looks like a power supply problem. I will take the
issue to Dell:
C:\Users\Administrator>omreport system
Health
SEVERITY : COMPONENT
Critical : Main System Chassis
C:\Users\Administrator>omreport chassis
Health
Main System Chassis
SEVERITY : COMPONENT
Ok : Fans
Ok
lois garcia writes:
> I have check_openmanage running successfully on 13 out of 16 Dell R710s.
> I am really puzzled at what is going wrong, as it seems different on each
> machine. I have tried different versions of check_openmanage and
> reinstalling the same version of Dell OMSA.
>
> The fir
I have check_openmanage running successfully on 13 out of 16 Dell R710s.
I am really puzzled at what is going wrong, as it seems different on each
machine. I have tried different versions of check_openmanage and
reinstalling the same version of Dell OMSA.
The first eight servers were built from
On 08/15/2011 11:46 PM, Trond Hasle Amundsen wrote:
> Russell Kackley writes:
>
>> I recently downloaded and started using the Nagios plugin
>> check_openmanage to provide information on our Dell PowerEdge servers to
>> Nagios. check_openmanage works very well for us, but there is one thing
>> tha
Russell Kackley writes:
> I recently downloaded and started using the Nagios plugin
> check_openmanage to provide information on our Dell PowerEdge servers to
> Nagios. check_openmanage works very well for us, but there is one thing
> that I would like to see added. Another possibility is that
I recently downloaded and started using the Nagios plugin
check_openmanage to provide information on our Dell PowerEdge servers to
Nagios. check_openmanage works very well for us, but there is one thing
that I would like to see added. Another possibility is that other
check_openmanage users cou
Jay Wahl writes:
> Love check_openmanage plugin for Nagios! It has been a great help for
> monitoring our Dell hardware. I recently built 3 Dell 900s with W2K8r2 with
> check_openmanage (v 3.6.8) and Dell OMSA (v 6.5.0).
Hi Jay,
Are you completely sure that you're using version 3.6.8? My reason
Love check_openmanage plugin for Nagios! It has been a great help for
monitoring
our Dell hardware. I recently built 3 Dell 900s with W2K8r2 with
check_openmanage (v 3.6.8) and Dell OMSA (v 6.5.0).
I am getting the following errors:
C:\Program Files\NSClient++\scripts>check_openmanage
Proble
something simple like that!
Thanks,
Daniel Ceola
-Original Message-
From: Trond Hasle Amundsen [mailto:t.h.amund...@usit.uio.no]
Sent: Tuesday, May 10, 2011 8:24 AM
To: Nagios Users List
Subject: Re: [Nagios-users] Check_Openmanage configuration question
Daniel Ceola writes:
> He
Daniel Ceola writes:
> Hello all!
Hi Daniel,
> I have a question regarding the initial configuration of
> check_openmanage. I downloaded the version of the script dated Feb 9
> (I don?t see a version number in the script) and am attempting to use
> the script through SNMP.
Tip: Run the plugin
Hello all!
I have a question regarding the initial configuration of check_openmanage. I
downloaded the version of the script dated Feb 9 (I don't see a version number
in the script) and am attempting to use the script through SNMP.
I'm attempting to begin using check_openmanage with our Dell
On 4/28/11 2:57 AM, Trond Hasle Amundsen wrote:
>> Tried check_openmanage-3.7.0-beta2.0-beta2, problem solved.
> Excellent, thanks for testing and reporting back. I've just released
> versjon 3.6.6, which contains the same bugfixes as the 3.7 beta, but not
> the (unfinished) new features:)
>
> Chee
"Randal, Phil" writes:
> Is the beta of check_openmanage.php available for testing?
Sure, I put it here:
http://folk.uio.no/trondham/software/beta/
Highlights of the template are:
- works with the plugin's new perfdata API
- removed unnecessary dependence on PHP >= 5.2 (good for rhel/ce
p; Herefordshire Council | Deputy Chief Executive's Office |
I.C.T. Services Division
Thorn Office Centre, Rotherwas, Hereford, HR2 6JT
Tel: 01432 260160
-Original Message-
From: Trond Hasle Amundsen [mailto:t.h.amund...@usit.uio.no]
Sent: 28 April 2011 10:57
To: Nagios Users Li
Steve Glasser writes:
>> That combination should work just fine. Please try either of the beta
>> versions, as I suggested in my previous email. The issue you're having
>> may very well be fixed in the betas.
>
> Tried check_openmanage-3.7.0-beta2.0-beta2, problem solved.
Excellent, thanks for t
On 4/27/11 11:03 AM, Trond Hasle Amundsen wrote:
> Steve Glasser writes:
>
>> D'oh. We are using check_openmanage with NRPE. The host o/s is CentOS
>> release 5.5. Perl is perl-5.8.8 (from rpm).
>
> That combination should work just fine. Please try either of the beta
> versions, as I suggested
Steve Glasser writes:
> D'oh. We are using check_openmanage with NRPE. The host o/s is CentOS
> release 5.5. Perl is perl-5.8.8 (from rpm).
That combination should work just fine. Please try either of the beta
versions, as I suggested in my previous email. The issue you're having
may very we
On 4/27/11 12:42 AM, nagios-users-requ...@lists.sourceforge.net wrote:
> check_openmanage with NRPE
D'oh. We are using check_openmanage with NRPE. The host o/s is CentOS
release 5.5. Perl is perl-5.8.8 (from rpm).
Cheers,
Steve Glasser | System Administrator | visp.net
Direct: 541-955-6903 |
> Ok, this actually clarifies things. Clearly, NSClient++ ignores
> everything after 'check_openmanage.exe' in your NSC.ini. There is no
> way
> that check_openmanage would complain about fans etc. when the option
> '--only storage' is specified. Since it works from command line we can
> safely as
> On Wed, Apr 27, 2011 at 5:06 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> ok, talked to dell, there is no hardware on the T105 that will allow
>> monitoring of the fan, voltage, etc.. basically the only thing you
>> can
>> monitor is the raid array which is fine as that's
> On Wed, Apr 27, 2011 at 5:06 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> ok, talked to dell, there is no hardware on the T105 that will allow
>> monitoring of the fan, voltage, etc.. basically the only thing you
>> can
>> monitor is the raid array which is fine as that's
Ashcor Technologies writes:
> ok, talked to dell, there is no hardware on the T105 that will allow
> monitoring of the fan, voltage, etc.. basically the only thing you can
> monitor is the raid array which is fine as that's all I really want to
> check with nagios.
Ok. I don't know the 100 serie
> On Tue, Apr 26, 2011 at 12:39 PM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> the server is a PowerEdge T105. It IS running slow but I'll be
>> damned if I can figure out why, I'm beggining to suspect bad ram as
>> the performance meter reports minimal load.
>
> One thi
Ashcor Technologies writes:
> the server is a PowerEdge T105. It IS running slow but I'll be damned
> if I can figure out why, I'm beggining to suspect bad ram as the
> performance meter reports minimal load.
One thing to check is the power management setting in the BIOS. We set
up a few blad
> On Tue, Apr 26, 2011 at 11:10 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Ok, now new and exciting changes... no matter what I do I get:
>> WARNING PLUGIN TIMEOUT: check_openmanage timed out after 30 seconds.
>>
>> I have -t 60 set on the check_openmanage command and als
Ashcor Technologies writes:
> Ok, now new and exciting changes... no matter what I do I get: WARNING
> PLUGIN TIMEOUT: check_openmanage timed out after 30 seconds.
>
> I have -t 60 set on the check_openmanage command and also on the NRPE
> check command line and in the NSC.ini. nothing seems t
2011/4/26 Ashcor Technologies :
>> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
>
>> Ashcor Technologies writes:
>>
>>> Thanks for the reply. I just realized from your question that I'm
>>> using a pre-compiled .exe version of your check_openmanage from here:
>>>
>>> https://www.m
On Tue, Apr 26, 2011 at 10:24 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> now my problem is this...
>>
>> Problem running 'omreport chassis fans': Error! No fan probes found
>> on this system.Problem running 'omreport chassis temps': Error!
>> No temperature probes found
Ashcor Technologies writes:
> Ok, now new and exciting changes... no matter what I do I get: WARNING
> PLUGIN TIMEOUT: check_openmanage timed out after 30 seconds.
>
> I have -t 60 set on the check_openmanage command and also on the NRPE
> check command line and in the NSC.ini. nothing seems t
> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Thanks for the reply. I just realized from your question that I'm
>> using a pre-compiled .exe version of your check_openmanage from here:
>>
>> https://www.monitoringexchange.org/inventory/Check-
Ashcor Technologies writes:
> now my problem is this...
>
> Problem running 'omreport chassis fans': Error! No fan probes found on
> this system.Problem running 'omreport chassis temps': Error! No
> temperature probes found on this system.Problem running 'omreport
> chassis volts': Error! No v
> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Thanks for the reply. I just realized from your question that I'm
>> using a pre-compiled .exe version of your check_openmanage from here:
>>
>> https://www.monitoringexchange.org/inventory/Check-
> On Tue, Apr 26, 2011 at 9:17 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> Thanks for the reply. I just realized from your question that I'm
>> using a pre-compiled .exe version of your check_openmanage from here:
>>
>> https://www.monitoringexchange.org/inventory/Check-
Ashcor Technologies writes:
> Thanks for the reply. I just realized from your question that I'm using
> a pre-compiled .exe version of your check_openmanage from here:
>
> https://www.monitoringexchange.org/inventory/Check-Plugins/Hardware/check_openmanage-exe
>
> which was probably created f
> On Tue, Apr 26, 2011 at 4:07 AM, Trond Hasle Amundsen wrote:
> Ashcor Technologies writes:
>
>> on two of my dell servers check_openmanage (via nsclient++ and nrpe)
>> return the same error:
>>
>> "Use of uninitialized value in concatenation (.) or string at
>> script/check_openmanage.pl line
Ashcor Technologies writes:
> on two of my dell servers check_openmanage (via nsclient++ and nrpe)
> return the same error:
>
> "Use of uninitialized value in concatenation (.) or string at
> script/check_openmanage.pl line 1386."
>
> both dell systems are running the latest OpenManage version
anyone???
On Tue, Apr 19, 2011 at 11:13 AM, Ashcor Technologies wrote:
> Hello All,
>
> on two of my dell servers check_openmanage (via nsclient++ and nrpe)
> return the same error:
>
> "Use of uninitialized value in concatenation (.) or string at
> script/check_openmanage.pl line 1386."
>
> b
Hello All,
on two of my dell servers check_openmanage (via nsclient++ and nrpe)
return the same error:
"Use of uninitialized value in concatenation (.) or string at
script/check_openmanage.pl line 1386."
both dell systems are running the latest OpenManage version 6.5.0.
anyone else see this o
Output from omreport storage connector controller=1 -fmt ssv
---
List of Connector(s) on Controller PERC 6/E Adapter (Slot 2)
ID;Status;Name;State;Connector Type;Termination;SCSI Rate
0;Ok;Logical Connector ;Ready;SAS Port RAID Mode;Not Applicable;Not
Applicable
Path Health
Status;Name;State;St
Adam Caines writes:
> Looks like it's reporting "path health". The 6e has both sas ports
> connected to redundant controllers in the MD1120. It's strange on
> another server, I also have a PERC H700 connect to a MD1220 with
> redundant links and it does not output the "path health" section.
[s
Looks like it's reporting "path health". The 6e has both sas ports
connected to redundant controllers in the MD1120. It's strange on another
server, I also have a PERC H700 connect to a MD1220 with redundant links and
it does not output the "path health" section.
C:\Users\Administrator>omreport
Adam Caines writes:
> Looks like some strange output on the lines for controller 1? The
> formatting is breaking there. I checked omreport storage controller
> and didn't see anything that stood out as being strange.
[snip]
> OK | 0:0 | Connector 0 [SAS Port RAID Mode] on controlle
Looks like some strange output on the lines for controller 1? The
formatting is breaking there. I checked omreport storage controller and
didn't see anything that stood out as being strange.
System: PowerEdge 1950 III OMSA version:6.4.0
ServiceTag: XXX
Adam Caines writes:
> All of the status lines appear to be Ok.
Indeed they do. This appears to be trickier than I initially
thought. Perhaps the debug output from the plugin has some clues?
Try 'check_openmanage -d --only storage'. It will attempt to print the
status of all monitored storage co
Adam Caines writes:
> Having a strange problem with check_openmanage. Use it without error on many
> other systems. Any help would be appreciated.
>
> check_openmanage version: 3.6.5 (.exe version)
> Dell OMSA version: 6.4.0
> OS: Windows Server 2008 R2
> Hardware: Poweredge 1950 with PERC 6/i
Having a strange problem with check_openmanage. Use it without error on
many other systems. Any help would be appreciated.
check_openmanage version: 3.6.5 (.exe version)
Dell OMSA version: 6.4.0
OS: Windows Server 2008 R2
Hardware: Poweredge 1950 with PERC 6/i and PERC 6/e connected to MD1120
-
Joe Beck writes:
> Yes, just after sending this post I did the things you identified.
> Verifed model vs others where this issue was not happening
> We have several r610's & this is only one with the issue.
> Then I went & looked at the omsa version & found this one was running 5.9
> where the ot
Yes, just after sending this post I did the things you identified.
Verifed model vs others where this issue was not happening
We have several r610's & this is only one with the issue.
Then I went & looked at the omsa version & found this one was running 5.9
where the others had 6.4
I removed & inst
Joe Beck writes:
> I have a couple R610’s
> Some run omreport chassis pwrmonitoring & return output
> I also have 1 that returns:
> # omreport chassis pwrmonitoring
> Power Consumption Information
>
> Error : Current probes not found
>
> Does this mean that this module just isn’t installed or ???
I have a couple R610’s
Some run omreport chassis pwrmonitoring & return output
I also have 1 that returns:
# omreport chassis pwrmonitoring
Power Consumption Information
Error : Current probes not found
Does this mean that this module just isn’t installed or ???
At this point, do I just alter th
Shawn Green writes:
> I?m in the process of rolling out check_openmanage to monitor a variety of
> hardware including R510s, M600s, and M610s. I?m running into an interesting
> issue where the alert is reporting back:
>
> SNMP ERROR [cooling]: The requested entries are empty or do not exist.
>
I'm in the process of rolling out check_openmanage to monitor a variety of
hardware including R510s, M600s, and M610s. I'm running into an interesting
issue where the alert is reporting back:
SNMP ERROR [cooling]: The requested entries are empty or do not exist.
I understand this is an SNMP er
"Bryan O'Shea" writes:
> check_openmanage and linebreaks not working in $SERVICEOUTPUT$ emails.
>
> When using the either of the following options the linebreaks seem to be
> broken:
> -e or --postmsg
>
> This is what i get in my service notification emails instead of the
> desired output of se
check_openmanage and linebreaks not working in $SERVICEOUTPUT$ emails.
When using the either of the following options the linebreaks seem to be broken:
-e or --postmsg
This is what i get in my service notification emails instead of the
desired output of seperate lines.
"Power Supply 1 [AC] need
"Tom Sommer" writes:
>>> After upgrading OpenManage to version 6.4.0 on a DELL R410,
>>> check_openmanage 3.6.4 returns
>>>
>>> CRITICAL: Amperage probe 0 [System Board System Level] reads 0 W
>>>
>>>
>>> Is this due to OpenManage changing behavior (bug), or is the hardware
>>> really faulty? (do
1 - 100 of 188 matches
Mail list logo
