rrd does not exist after wizard rerun

ian_couch · Post by **ian_couch** » Thu May 31, 2012 11:57 am

Hi Scott,
Here's the capture, and comments from the server administrator, keeping in mind that the node in question is addressed as 172.31.1.101:

From what I can tell, these errors are SNMP issues with the hosts involved. I could probably dig deeper, but it would take some time, and I don't think they are related to the issue.

I ran the wizard again, and had the same results. The new interfaces were not added to the mrtg.cfg config.

As far as where the issue is, it appears to be something with the configuration wizard, but I suppose an issue with the mrtg configuration could prevent the changes from being applied, as well. There may be a log somewhere (ask Scott) that could give us a clue, where the breakdown is occuring.

[root@nagios1 mrtg]# env LANG=C /usr/bin/mrtg /etc/mrtg/mrtg.cfg

SNMP Error:
Received SNMP response with error code
error status: noSuchName
index 1 (OID: 1.3.6.1.2.1.2.2.1.10.32)
SNMPv1_Session (remote host: "192.168.2.1" [192.168.2.1].161)
community: "********"
request ID: 1873994313

PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/bin/../lib64/mrtg2/SNMP_util.pm line 492
SNMPGET Problem for ifInOctets.32 ifOutOctets.32 on OpMon@192.168.2.1:::::1:v4only
at /usr/bin/mrtg line 2202
SNMP Error:
Received SNMP response with error code
error status: noSuchName
index 1 (OID: 1.3.6.1.2.1.2.2.1.10.33)
SNMPv1_Session (remote host: "192.168.2.1" [192.168.2.1].161)
community: "********"
request ID: 1873994314

PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/bin/../lib64/mrtg2/SNMP_util.pm line 492
SNMPGET Problem for ifInOctets.33 ifOutOctets.33 on OpMon@192.168.2.1:::::1:v4only
at /usr/bin/mrtg line 2202
2012-05-31 10:19:12: ERROR: Target[172.31.1.100_11][_IN_] ' $target->[4]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[172.31.1.100_11][_OUT_] ' $target->[4]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[10.2.26.26_5003][_IN_] ' $target->[207]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[10.2.26.26_5003][_OUT_] ' $target->[207]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_181][_IN_] ' $target->[486]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_181][_OUT_] ' $target->[486]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_185][_IN_] ' $target->[490]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_185][_OUT_] ' $target->[490]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_212][_IN_] ' $target->[513]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_212][_OUT_] ' $target->[513]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_228][_IN_] ' $target->[525]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_228][_OUT_] ' $target->[525]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_229][_IN_] ' $target->[526]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_229][_OUT_] ' $target->[526]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_233][_IN_] ' $target->[527]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_233][_OUT_] ' $target->[527]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_241][_IN_] ' $target->[532]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_241][_OUT_] ' $target->[532]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_244][_IN_] ' $target->[534]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_244][_OUT_] ' $target->[534]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_246][_IN_] ' $target->[536]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_246][_OUT_] ' $target->[536]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_261][_IN_] ' $target->[550]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_261][_OUT_] ' $target->[550]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_265][_IN_] ' $target->[554]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_265][_OUT_] ' $target->[554]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_272][_IN_] ' $target->[560]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_272][_OUT_] ' $target->[560]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_275][_IN_] ' $target->[563]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_275][_OUT_] ' $target->[563]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_276][_IN_] ' $target->[564]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_276][_OUT_] ' $target->[564]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_394][_IN_] ' $target->[592]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_394][_OUT_] ' $target->[592]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_395][_IN_] ' $target->[593]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_395][_OUT_] ' $target->[593]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_396][_IN_] ' $target->[594]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.1.1_396][_OUT_] ' $target->[594]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[172.31.1.34_423][_IN_] ' $target->[1407]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[172.31.1.34_423][_OUT_] ' $target->[1407]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.2.1_32][_IN_] ' $target->[1564]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.2.1_32][_OUT_] ' $target->[1564]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.2.1_33][_IN_] ' $target->[1565]{$mode} ' did not eval into defined data
2012-05-31 10:19:12: ERROR: Target[192.168.2.1_33][_OUT_] ' $target->[1565]{$mode} ' did not eval into defined data
[root@nagios1 mrtg]#

scottwilkerson · Post by **scottwilkerson** » Thu May 31, 2012 2:06 pm

can you run the following

Code: Select all

ls -l /etc/mrtg/mrtg.cfg

Also, can you send your /etc/mrtg/mrtg.cfg to me in a PM

Scott

ian_couch · Post by **ian_couch** » Thu May 31, 2012 3:10 pm

Here is the command run:
[root@nagios1 mrtg]# ls -l /etc/mrtg/mrtg.cfg
-rw-r--r-- 1 apache nagios 2369057 May 31 09:59 /etc/mrtg/mrtg.cfg. I'll pm you the file momentarily.

Ian.

scottwilkerson · Post by **scottwilkerson** » Thu May 31, 2012 4:00 pm

Can you tell me what interfaces/port you were trying to add to 172.31.1.101

this will be the file name of the RRD's it cannot find.

thanks.

Was it by chance any of these?
2,3,4,5,9,10

ian_couch · Post by **ian_couch** » Fri Jun 01, 2012 7:53 am

It wasn't. The interfaces are a physical interface, which I believe has index #11, and a configured sub-interface, with index #12. I don't know for sure which one is index 11, but I assum that is the physical interface, not that it should matter. The server admin says that even after discovery is run , 11 and 12 do not show up in the file.

edit: It might be worth considering that when this device was first added, the interfaces were originally 'admin down' and have since been put into service, hence the need to revisit the device in nagios to begin monitoring state and bandwidth.

scottwilkerson · Post by **scottwilkerson** » Fri Jun 01, 2012 9:15 am

Ok, here's what we need to do

Run the following from the command line of your XI machine replacing <COMMUNITY_STRING> with your community string

Code: Select all

/usr/bin/cfgmaker --show-op-down --zero-speed=10000000000 --snmp-options=:::::2 --noreversedns <COMMUNITY_STRING>@172.31.1.101 > 172.31.1.101_mrtg

This will create a file named 172.31.1.101_mrtg that you can open and view the results.

Copy interface 11 & 12 sections to your /etc/mrtg/mrtg.cfg

The wizard is designed to check to see if a switch/router has ever been added to the mrtg.cfg, and if it has it skips that part because adding it a second time can break the config.

ian_couch · Post by **ian_couch** » Fri Jun 01, 2012 9:32 am

Thanks Scott, we'll give that a try.

What would the procedure be then to add interfaces to a router/switch that already has interfaces in the mrtg.conf file, when interfaces are being turned up after the node has been already added and these interfaces now need to be monitored? Could the wizard be changed to only add interfaces that aren't there already, or were previously admin down? Quite frequently in our production environment interfaces are turned up or turned down. Removal for a turn down seems pretty straightforward (i.e. service deletion) , but adding them this way would be a problem for staff that don't have access to the shell on the nagios server. I guess the server admins could do it all the time, but I don't think that would be a practical solution for us. The alternative solution, deleting all references to the node and then re-adding it to the server database wouldn't work either, as I'm assuming in that case we would lose the previously created .rrd files , since they would likely be overwritten, losing all historical bandwidth records.

scottwilkerson · Post by **scottwilkerson** » Fri Jun 01, 2012 2:05 pm

Unfortunately at this time with the current wizard what I outlines above would need to be done.

We do have a different wizard in development that doesn't use mrtg at all and can add/remove interfaces more dynamically, but it will be a little while before it will be available.

pnnagios · Post by **pnnagios** » Thu Oct 18, 2012 11:06 am

Does anyone know if this issue has been addressed in the Nagios XI 2012R1.0 release?

Thank you,

Paul

scottwilkerson · Post by **scottwilkerson** » Thu Oct 18, 2012 11:40 am

We have a document outlining the standard procedure for adding ports to existing wizards.
http://assets.nagios.com/downloads/nagi ... Router.pdf

Nothing relating to this has changed in 2012.

We did start development on a hiperf switch wizard that you can feel free to test, I would consider it Alpha release, I have attached it here, it can be added through Admin -> Manage Config Wizards

You should also extract the zip and add the items in templates directory to Admin -> graph Templates

hiperf_switch.zip

Nagios Support Forum

rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun

Re: rrd does not exist after wizard rerun