CPU/Memory are showing unknown in Nagios XI

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Mani.Murugesan
Posts: 67
Joined: Fri May 12, 2017 1:37 am

CPU/Memory are showing unknown in Nagios XI

Post by Mani.Murugesan »

We are currently working on Nagios XI and under which we are continuously getting CPU/Memory utilization UNKNOWN error in the Nagios XI
I have checked everything from my end.. and from the network team..... everything is in placed ac per the configuration end
Error message is - Description table : The requested table is empty or does not exist.

below are the details -

Nagios version - Nagios XI version 5.2.2
Type of firewall - Fortiget firewall
SNMP version - V2

command is - usr/local/nagios/libexec/check_snmp_load.pl -H 10.168.108.14 -C ******** -2 -w 80 -c 90 -T stand cisco -f

Please suggest what course of action required
dwhitfield
Former Nagios Staff
Posts: 4583
Joined: Wed Sep 21, 2016 10:29 am
Location: NoLo, Minneapolis, MN
Contact:

Re: CPU/Memory are showing unknown in Nagios XI

Post by dwhitfield »

Have you tried the SNMP walk wizard? All else failing it can at least list out possibilities. Use .1 for the OID to walk everything.

Also, on the remote host, what's the output of service snmpd status?
Mani.Murugesan
Posts: 67
Joined: Fri May 12, 2017 1:37 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by Mani.Murugesan »

Thanks for your reply.

the output of the command is -
[root@#localhost ~]# service snmpd status
Redirecting to /bin/systemctl status snmpd.service
snmpd.service - Simple Network Management Protocol (SNMP) Daemon.
Loaded: loaded (/usr/lib/systemd/system/snmpd.service; disabled)
Active: active (running) since Wed 2017-06-14 13:13:25 BST; 1 weeks 1 days ago
Main PID: 4751 (snmpd)
CGroup: /system.slice/snmpd.service
└─4751 /usr/sbin/snmpd -LS0-6d -f

Jun 14 13:13:25 #localhost.localdomain
MPHSCRLS0710 snmpd[4751]: NET-SNMP ver...
Jun 14 13:13:25 #localhost.localdomain
MPHSCRLS0710 systemd[1]: Started Simpl...
Hint: Some lines were ellipsized, use -l to show in full.

I will try snmpwalk and let you know the result
Mani.Murugesan
Posts: 67
Joined: Fri May 12, 2017 1:37 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by Mani.Murugesan »

Also We tried to enable .1 as an OID. but not able to got any interfaces.

for checking when we try SNMPWALK command , below output came
Timeout:No Response from XX.XX....
You do not have the required permissions to view the files attached to this post.
Mani.Murugesan
Posts: 67
Joined: Fri May 12, 2017 1:37 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by Mani.Murugesan »

Yes we have tried service snmpd status.. and its running active..

We have tried .1 as OID usng SNMPWALK wizard.. but there would be no output from it.
Moreover when we are running SNMPWALK command.. we got "no response" error.Attached the output for your reference
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by tgriep »

I have seen that some firewalls, you enable SNMP polling on the device and you also have to setup a rule on the firewall to allow the Nagios server to poll UDP port 161, was that done as well?

What is the model number of the firewall and the version of the firmware it is running?
Be sure to check out our Knowledgebase for helpful articles and solutions!
Mani.Murugesan
Posts: 67
Joined: Fri May 12, 2017 1:37 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by Mani.Murugesan »

Hello tgriep,

thanks for the response.
Yes we already have the setting on the firewalls
Please find below details as per request.

Model details Version detail
FortiGate 280D-POE v5.4.1,build1064
FortiGate 60E v5.4.1,build5495
Fortigate 90E v5.4.1,build5735
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by tgriep »

If you cannot get the snmpwalk to run against the Fortigate devices, then you will have to verify that they are configured correctly.
I found this PDF file you can use to verify that the Fortigate devices are setup for SNMP polling. Please login to the devices and verify that the settings are correct.
http://docs.fortinet.com/uploaded/files ... e-unit.pdf

An example snmpwalk command you can use to test the Fortigate's is as follows

Code: Select all

snmpwalx xxx.xxx.xxx.xxx -v 2c -c <communitystring>
replace the xxx.xxx.xxx.xxx with the device you are testing and the <communitystring> with the device's string.

After you get the snmpwalk to work, to use the check_snmp_load plugin against a Fortigate device, you have to specify the type option like the example below. The -T fg says to poll a Fortigate device.

Code: Select all

/usr/local/nagios/libexec/check_snmp_load.pl -H 10.168.108.14 -C ******** -2 -w 80 -c 90 -T fg -f
Be sure to check out our Knowledgebase for helpful articles and solutions!
Mani.Murugesan
Posts: 67
Joined: Fri May 12, 2017 1:37 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by Mani.Murugesan »

we have tried,we got "no response" error.Attached the output for your reference
You do not have the required permissions to view the files attached to this post.
User avatar
tgriep
Madmin
Posts: 9190
Joined: Thu Oct 30, 2014 9:02 am

Re: CPU/Memory are showing unknown in Nagios XI

Post by tgriep »

Try running the following command on the Nagios server to see if port 161 UDP is open on the devices.

Code: Select all

nmap xxx.xxx.xxx.xxx -sU -p 161
Replace xxx.xxx.xxx.xxx with the IP addresses if the Fortigate units.
If the command comes back and says that the port is closed, then the Fortigate units probably doesn't have SNMP enabled.
It it reports the port is open, then I could be the SNMP version is set wrong or that the community string is incorrect.

Without seeing the configuration settings, there is not much else to go on.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked