Nagios Support Forum

Hi Team,

Just an information, we are able to get output of tunnel interface with the nwc_health plugin but not the default nagios xi plugin.

[root@nagios libexec]# ./check_nwc_health --hostname 188.231.80.1 --community gSrou1er --mode interface-usage --name Tunnel19244140 --units KB
OK - interface Tunnel19244140 (alias !CYP-PE1 to Omdorman!) usage is in:55.27% (53.97KB/s) out:0.00% (0.00KB/s) | 'Tunnel19244140_usage_in'=55.27%;80;90;0;100 'Tunnel19244140_usage_out'=0.00%;80;90;0;100 'Tunnel19244140_traffic_in'=53.97KB;78.125;87.8906;0;97.6562 'Tunnel19244140_traffic_out'=0.00KB;78.125;87.8906;0;97.6562
[root@nagios libexec]#

Thanks

Glad you were able to find a solution, you will likely need to delete the backend /usr/local/nagios/share/perfdata/HOSTNAME/SERVICENAME.rrd so that it graphs properly though. Did you do that? Is it graphing for you properly?

Hi Team,

We have already deleted the rrd file of the service and tested. but it didn't work. Graph is still showing as 0

Thanks

Please attach both of these files AND a fresh copy of your Profile:
Thank you!

dear ssax

i have send the requested detail to your inbox

Please attach these as well (I need these for the internal details):
- Change HOSTNAME to the host and SERVICENAME to the service name in question so that I can look at the graphing details and compare the contents

Hi Team,

Can we have any update on this?

Thanks

Can you run this command as root on the Nagios server and post the /tmp/cfg.txt file here?

Thanks for running the command.
I went through it and at the time it was ran, the interface called Tunnel19244140 was not captured so there is no data for that interface.
The tunnel should be Interface 36 but it is missing.
If the tunnel was down when it was ran, then the cfgmaker command would not see it.
Was the tunnel down at the time the cfgmaker command was ran?
Is the tunnel always up and never goes down?

I do have a thought, if the tunnel drops and restarts, I would guess that the counters are reset when it comes back and that would give false data to for the bandwidth collection. That might be the cause of the issue.

Even though the tunnel interface may not exist, try this.
Edit the /etc/mrtg/mrtg.d/188.231.80.1.cfg file and remove this line (Line 1289) change line 1291 from to Save the file and delete this file to remove the old bandwidth data Wait for 20 to 30 minutes for the system to gather the bandwidth data and check the graph to see if there is data,

Another thing I notice, if that there is very little traffic outbound on that interface so it may always show zero.

dear tgriep

kinldy check the inbox i had send the result of 188.231.80.1_37 which have the rdd and xml file of _37 . Please note _36 we are not using . kindly check and let me know if you require further details.