Page 1 of 1

Esxi host given Critical error

Posted: Tue Jun 03, 2014 10:37 am
by Rupender
Hi,

Please clarify what is wrong with this?


***** Nagios XI Alert *****

Nagios has detected a problem with this service.

Notification Type: PROBLEM

Service: Datastore usage for VMHost
Host: X.X.X.96
Address: X.X.X.96
State: CRITICAL
Info:
CHECK_ESX3.PL CRITICAL - Storages : RADSHARE=89648.00 MB (5.84%), TEMPSTORAGE=864534.00 MB (16.49%), prt-sf-1=191620.00 MB (18.72%), p2t-01=240880.00 MB (12.38%), hussman=1373168.00 MB (67.06%), hussman2=1965422.00 MB (37.49%), prt-rapid-2=316928.00 MB (15.48%), PRT_DS_3=263408.00 MB (12.88%), prt-1059=340351.00 MB (6.49%), mv-data-recovery=637024.00 MB (31.11%), prt-cdc-2=1534496.00 MB (74.94%), prt-mvr-datastore-1=943624.00 MB (18.00%), PRT_DS_1=605616.00 MB (29.62%), NU-hc3=1435704.00 MB (70.11%), prt-sf-2=1011640.00 MB (49.40%), gc-ds2=1782953.00 MB (34.01%), prt-principal-datastore-1=168.00 MB (0.02%), gc-ds1=734153.00 MB (35.01%), datastore1=121386.00 MB (90.49%), prt-cdc1=1351856.00 MB (66.02%), mw-riverside-datastore-1=866556.00 MB (45.92%), mw-ds1=2436027.00 MB (23.23%), prt-rapid-1=69646.00 MB (3.40%), prt-licg-1=135868.00 MB (6.64%), nj-ds1=2234982.00 MB (35.53%), prt-exchange-store1=2085742.00 MB (39.78%), PRT_DS_2=124848.00 MB (6.11%), gc-ds3=844420.00 MB (16.11% ), prt-cdc3=27528.00 MB (1.34%), VeeamBackup_VEEAM-SERVER is not accessible
Date/Time: 2014-06-03 09:00:11

Re: Esxi host given Critical error

Posted: Tue Jun 03, 2014 10:48 am
by tmcdonald

Code: Select all

datastore1=121386.00 MB (90.49%)
Probably that. Is the reading not accurate? What are your warning/critical thresholds?

Re: Esxi host given Critical error

Posted: Tue Jun 03, 2014 10:56 am
by Rupender
It is NagiosXI 2014R1.0

I don't know where to use Warning/Critical threshold?




[root@localhost ~]# /usr/local/nagios/libexec/check_esx3.pl -H 192.168.153.96 -f /usr/local/nagiosxi/etc/components/vmware/192_168_153_96_auth.txt -l VMFS
CHECK_ESX3.PL CRITICAL - Storages : RADSHARE=89648.00 MB (5.84%), TEMPSTORAGE=864534.00 MB (16.49%), prt-sf-1=191616.00 MB (18.72%), p2t-01=240872.00 MB (12.38%), hussman=1373168.00 MB (67.06%), hussman2=1965390.00 MB (37.49%), prt-rapid-2=316904.00 MB (15.48%), PRT_DS_3=263408.00 MB (12.88%), prt-1059=340147.00 MB (6.49%), mv-data-recovery=637024.00 MB (31.11%), prt-cdc-2=1534496.00 MB (74.94%), prt-mvr-datastore-1=943624.00 MB (18.00%), PRT_DS_1=605608.00 MB (29.62%), NU-hc3=1435704.00 MB (70.11%), prt-sf-2=1011640.00 MB (49.40%), gc-ds2=1782953.00 MB (34.01%), prt-principal-datastore-1=168.00 MB (0.02%), gc-ds1=734153.00 MB (35.01%), datastore1=121386.00 MB (90.49%), prt-cdc1=1351856.00 MB (66.02%), mw-riverside-datastore-1=866556.00 MB (45.92%), mw-ds1=2433703.00 MB (23.21%), prt-rapid-1=69641.00 MB (3.40%), prt-licg-1=135864.00 MB (6.63%), nj-ds1=2231746.00 MB (35.47%), prt-exchange-store1=2085737.00 MB (39.78%), PRT_DS_2=124848.00 MB (6.11%), gc-ds3=844420.00 MB (16.11%), prt-cdc3=27528.00 MB (1.34%), VeeamBackup_VEEAM-SERVER is not accessible | RADSHARE=89648.00MB;; TEMPSTORAGE=864534.00MB;; prt-sf-1=191616.00MB;; p2t-01=240872.00MB;; hussman=1373168.00MB;; hussman2=1965390.00MB;; prt-rapid-2=316904.00MB;; PRT_DS_3=263408.00MB;; prt-1059=340147.00MB;; mv-data-recovery=637024.00MB;; prt-cdc-2=1534496.00MB;; prt-mvr-datastore-1=943624.00MB;; PRT_DS_1=605608.00MB;; NU-hc3=1435704.00MB;; prt-sf-2=1011640.00MB;; gc-ds2=1782953.00MB;; prt-principal-datastore-1=168.00MB;; gc-ds1=734153.00MB;; datastore1=121386.00MB;; prt-cdc1=1351856.00MB;; mw-riverside-datastore-1=866556.00MB;; mw-ds1=2433703.00MB;; prt-rapid-1=69641.00MB;; prt-licg-1=135864.00MB;; nj-ds1=2231746.00MB;; prt-exchange-store1=2085737.00MB;; PRT_DS_2=124848.00MB;; gc-ds3=844420.00MB;; prt-cdc3=27528.00MB;;

Re: Esxi host given Critical error

Posted: Tue Jun 03, 2014 11:11 am
by tmcdonald
It should follow the standard of -w and -c for warning and critical, respectively. You can run it with just -h for help output, or -? for usage.

https://www.monitoringexchange.org/inve ... check_esx3