Hello,
I have a fresh Nagios XI Enterprise installation running from an .OVA template. The install and initial configuration went flawlessly. I am now running into an issue in which Nagios is not reporting all CMTS router interfaces as available services.
The weird thing is that after running the Router / Switch configuration wizard, 100% of the interfaces are identified, and I select them all to be monitored. However, none of the Upstream Physical or Logical Upstream Interfaces populate in the Host Services. (See attached)
I can see that all of the interfaces were discovered by checking the /etc/mrtg/conf.d/device.cfg files. All 2,680 of the interfaces are resident in the device config file. This core router has 2680 interfaces being reported by SNMP, and all interfaces were successfully created, I assume by cfgmaker.
Within the web interface however, Nagios is only displaying 1104 total interfaces on Core Router-1, and 1108 interfaces on Core Router-2.
I thought perhaps it was an issue with the type of interface being monitored (Upstream Interfaces) so I modeled a third CMTS, and only selected 15 random Upstream Interfaces, and they were instantiated with no problem. THis leads me to believe it is a threshold setting somewhere buried within the MRTG config.
Within Nagios XI Core Configuration Manager, the services simply don't exist, so I can't even attempt to manually enable them.
We need to monitor all physical and logical interfaces, and this is part of our selection criteria for the evaluation.
Excerpt from /etc/mrtg/conf.d/10.104.0.211.cfg
[root@localhost conf.d]# more 10.104.0.211.cfg | grep Logical | more
### Interface 5004608 >> Descr: 'Logical-Upstream-Channel-9/0.0/0' | Name: 'Logical Upstream Channel 9/0.0/0' | Ip: 'No Ip' | Eth: 'No Ether
net Id' ###
SetEnv[10.104.0.211_5004608]: MRTG_INT_IP="No Ip" MRTG_INT_DESCR="Logical-Upstream-Channel-9/0.0/0"
<td>Logical-Upstream-Channel-9/0.0/0 </td>
.
.
In this case, using interface 9/0.0/0 as an example. The SNMP Intferface ID as reported in the .cfg file is 5004608. We can also see that the .rrd file is resident in /var/lib
[root@localhost mrtg]# cd /var/lib/mrtg
[root@localhost mrtg]# ls | grep 5004608
10.104.0.211_5004608.rrd
We can also see that all 2,680 .rrd files are present, though as depicted in the attached screenshot, only 1104 interfaces are associated as Services to this Host.
[root@localhost mrtg]# ls | grep 10.104.0.211 | wc -l
2680
Please please help!
Joe Joseph
Nagios XI Services Not Populating
-
- Posts: 9
- Joined: Mon Jun 10, 2019 12:07 am
Nagios XI Services Not Populating
You do not have the required permissions to view the files attached to this post.
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios XI Services Not Populating
I believe you are hitting a max_input_vars limit in php when running the wizard
Add the following to the bottom of the /etc/php.ini
then restart httpd
Run the wizard again and they should show up.
Add the following to the bottom of the /etc/php.ini
Code: Select all
max_input_vars = 50000
Run the wizard again and they should show up.
-
- Posts: 9
- Joined: Mon Jun 10, 2019 12:07 am
Re: Nagios XI Services Not Populating
Scott,
Yes, that appears to have been the issue! I also received the following guidance from a Nagios Pre-Sales engineer.
Subject: Re: Nagios XI Enterprise Eval and Purchase
Hi Joe,
When the number of ports on the device is very large, it may be overflowing the default PHP settings.
Let's try increasing the settings by editing the /etc/php.ini file and change the following from:
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
To:
max_execution_time = 120
max_input_time = 240
memory_limit = 1024M
...and add this to the bottom of that file:
max_input_vars=50000
...then save the file.
Next, edit this file
/etc/httpd/conf/httpd.conf
add this to the bottom of that file:
LimitRequestLine 100000
Finally, restart the Apache service:
service httpd restart
Yes, that appears to have been the issue! I also received the following guidance from a Nagios Pre-Sales engineer.
Subject: Re: Nagios XI Enterprise Eval and Purchase
Hi Joe,
When the number of ports on the device is very large, it may be overflowing the default PHP settings.
Let's try increasing the settings by editing the /etc/php.ini file and change the following from:
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
To:
max_execution_time = 120
max_input_time = 240
memory_limit = 1024M
...and add this to the bottom of that file:
max_input_vars=50000
...then save the file.
Next, edit this file
/etc/httpd/conf/httpd.conf
add this to the bottom of that file:
LimitRequestLine 100000
Finally, restart the Apache service:
service httpd restart
-
- DevOps Engineer
- Posts: 19396
- Joined: Tue Nov 15, 2011 3:11 pm
- Location: Nagios Enterprises
- Contact:
Re: Nagios XI Services Not Populating
Great!alanjoseph wrote:Scott,
Yes, that appears to have been the issue! I also received the following guidance from a Nagios Pre-Sales engineer.
Subject: Re: Nagios XI Enterprise Eval and Purchase
Hi Joe,
When the number of ports on the device is very large, it may be overflowing the default PHP settings.
Let's try increasing the settings by editing the /etc/php.ini file and change the following from:
max_execution_time = 30
max_input_time = 60
memory_limit = 128M
To:
max_execution_time = 120
max_input_time = 240
memory_limit = 1024M
...and add this to the bottom of that file:
max_input_vars=50000
...then save the file.
Next, edit this file
/etc/httpd/conf/httpd.conf
add this to the bottom of that file:
LimitRequestLine 100000
Finally, restart the Apache service:
service httpd restart
Glad to hear it is resolved!
Locking