RESOLVED: PNP4Nagios mixes up performance data of IP subnets
Posted: Mon Nov 04, 2024 9:04 am
Hello everyone!
I have the following problem at the moment:
I check the phase-2 connections of various VPN tunnels. The performance data is being output like this (ANON1-9 are subnet IDs like "192.168.0.0"):
up_networks=9, down_networks=0, local_networks=1, remote_networks=8, phase2_connections=8, "ANON1"=1, "ANON2"=1, "ANON3"=1, "ANON4"=1, "ANON5"=1, "ANON6"=1, "ANON7"=1, "ANON8"=1, "ANON9"=1
I noticed that the graphs sometimes change between the subnets, ANON1 might at first have the graph of ANON1 but the next time I check ANON4 has the graph of ANON1.
I only noticed this because one subnet was behaving strange and I could immediately make it out but then I wondered why a "different subnet" suddenly was behaving the same. Until I realized that the graphs actually changed.
The known subnets of every host are stored in a json file which the script compares to the found subnets in the snmp data of the firewall.
Now for my question:
Is this a known issue? Are there any solutions to that?
Currently running on Nagios Core 4.5.7 with PNP4Nagios 0.6.25 on CentOS 7 (not recommended, I know).
Attached is a screenshot of a subnet that was just added today, 2h ago.
Another subnet was removed, now the new subnet has the graph of the old one. Thanks in advance!
Jan
I have the following problem at the moment:
I check the phase-2 connections of various VPN tunnels. The performance data is being output like this (ANON1-9 are subnet IDs like "192.168.0.0"):
up_networks=9, down_networks=0, local_networks=1, remote_networks=8, phase2_connections=8, "ANON1"=1, "ANON2"=1, "ANON3"=1, "ANON4"=1, "ANON5"=1, "ANON6"=1, "ANON7"=1, "ANON8"=1, "ANON9"=1
I noticed that the graphs sometimes change between the subnets, ANON1 might at first have the graph of ANON1 but the next time I check ANON4 has the graph of ANON1.
I only noticed this because one subnet was behaving strange and I could immediately make it out but then I wondered why a "different subnet" suddenly was behaving the same. Until I realized that the graphs actually changed.
The known subnets of every host are stored in a json file which the script compares to the found subnets in the snmp data of the firewall.
Now for my question:
Is this a known issue? Are there any solutions to that?
Currently running on Nagios Core 4.5.7 with PNP4Nagios 0.6.25 on CentOS 7 (not recommended, I know).
Attached is a screenshot of a subnet that was just added today, 2h ago.
Another subnet was removed, now the new subnet has the graph of the old one. Thanks in advance!
Jan