CPU/Memory are showing unknown in Nagios XI
-
Mani.Murugesan
- Posts: 67
- Joined: Fri May 12, 2017 1:37 am
Re: CPU/Memory are showing unknown in Nagios XI
Please find output of the attachment and Let me know What configuration settings detail we required
You do not have the required permissions to view the files attached to this post.
Re: CPU/Memory are showing unknown in Nagios XI
The port looks to be open on the device but is still could be a configuration setting on the Fortigate system.
Can you login to the Fortigate unit with a terminal, display the running configuration and post it here?
Can you login to the Fortigate unit with a terminal, display the running configuration and post it here?
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
Ok . We will reply
-
Mani.Murugesan
- Posts: 67
- Joined: Fri May 12, 2017 1:37 am
Re: CPU/Memory are showing unknown in Nagios XI
Please find the attachment for the below running configuration,
You do not have the required permissions to view the files attached to this post.
Re: CPU/Memory are showing unknown in Nagios XI
I am not familiar with the Fortigate Commands but from what I see, only the IP address in this range are allowed to access SNMP on the device so the Nagios server has to be in that range.
Is the Nagios server in that range?
In my previous post, I be wrong about the port being open. When it says open|filtered, that means that the nmap command could not determine whether a port is open or filtered, so it may not be truly open.
The community string has a special character in it and to use that in Nagios XI, you would have to create a user macro and use them in place of the community string in the wizards.
To do that, edit this file:
Add your special character community string like the example below
Save the file and restart nagios by running the following as root.
Then, when you run the Wizard, you would use $USER9$ in place of the community string.
Code: Select all
192.168.86.1 - 192.168.86.30In my previous post, I be wrong about the port being open. When it says open|filtered, that means that the nmap command could not determine whether a port is open or filtered, so it may not be truly open.
The community string has a special character in it and to use that in Nagios XI, you would have to create a user macro and use them in place of the community string in the wizards.
To do that, edit this file:
Code: Select all
/usr/local/nagios/etc/resource.cfgCode: Select all
$USER9$=Commun!tyCode: Select all
service nagios restartBe 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
We Will try and let you know