This support forum board is for support questions relating to
Nagios XI , our flagship commercial network monitoring solution.
jyoti22
Posts: 254 Joined: Mon Mar 23, 2015 4:50 am
Post
by jyoti22 » Tue Sep 15, 2015 6:05 pm
I have configured vMA and vCenter as per doc "box293_check_vmware manual"
I have added few hosts also in monitoring successfully. However when doing it after some time I got below error
Code: Select all
[nagios@NagiosXI libexec]$ /usr/local/nagios/libexec/check_by_ssh -E 1 -l vi-admin -H 10.xx.xx.xx -C "~/box293_check_vmware.pl --server xx.xx.xx.xx --check vCenter_Name_Version"
CRITICAL - Plugin timed out after 10 seconds
[nagios@NagiosXI libexec]$
I did not made any changes still this error occurred. Please help me to resolve it
Box293
Too Basu
Posts: 5126 Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Post
by Box293 » Tue Sep 15, 2015 7:12 pm
Hey that looks like something that belongs to me
How many CPU's and how much memory does your vMA have?
Please refer to page 6 and 72 of the manual.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
jyoti22
Posts: 254 Joined: Mon Mar 23, 2015 4:50 am
Post
by jyoti22 » Wed Sep 16, 2015 12:41 pm
vMA was built with default values as
600 MB memory and 1 CPU
I guess this is the reason of error. Please let me know what can be memory and CPU configuration needed if I add more than 70 ESXi hosts on vMA
Thanks.
tgriep
Madmin
Posts: 9190 Joined: Thu Oct 30, 2014 9:02 am
Post
by tgriep » Wed Sep 16, 2015 3:17 pm
In the manual, this is what is recommended for the CPU and memory requirements.
I recommended the vMA has 2 CPUs and 2GB Memory at a minimum.
Be sure to check out our
Knowledgebase for helpful articles and solutions!
Box293
Too Basu
Posts: 5126 Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Post
by Box293 » Wed Sep 16, 2015 4:51 pm
I would suggest 4-8 CPUs and at least 8GB RAM.
Page 72 of the manual shows how to check how much memory is being used.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .
jyoti22
Posts: 254 Joined: Mon Mar 23, 2015 4:50 am
Post
by jyoti22 » Fri Sep 18, 2015 5:28 pm
Thanks a lot!. After adding CPU and memory, ESXi working fine Now.
hsmith
Agent Smith
Posts: 3539 Joined: Thu Jul 30, 2015 11:09 am
Location: 127.0.0.1
Contact:
Post
by hsmith » Mon Sep 21, 2015 9:06 am
Hi jyoti22,
Are we all right to close this one up and mark it resolved?
Former Nagios Employee.
me.
jyoti22
Posts: 254 Joined: Mon Mar 23, 2015 4:50 am
Post
by jyoti22 » Mon Sep 21, 2015 11:57 am
Yes. It can be closed. before that I have one question on ESXi. I have few servers which are not part of vCenter. Please advice how can I add those ESXi servers in Nagios.
tgriep
Madmin
Posts: 9190 Joined: Thu Oct 30, 2014 9:02 am
Post
by tgriep » Mon Sep 21, 2015 4:27 pm
If you can't add those server to your existing vCenter server, you can use the standard VMWare wizard as long as you know the username and password for them.
Be sure to check out our
Knowledgebase for helpful articles and solutions!
Box293
Too Basu
Posts: 5126 Joined: Sun Feb 07, 2010 10:55 pm
Location: Deniliquin, Australia
Contact:
Post
by Box293 » Mon Sep 21, 2015 4:37 pm
The box293_check_vmware plugin works directly against ESXi servers as well. Just put the ESXi host address in the --server argument.
This is explained in the manual.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new
Privacy Policy .