Let us know, please follow these steps:
http://assets.nagios.com/downloads/nagi ... Router.pdf
mrtg.cfg is huge
-
snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: mrtg.cfg is huge
Exact same result. Ran from CLI just to be sure and still get nothing. Here is the portion of the mrtg.cfg file that pertains to this interface, with company sensitive info edited out:
Code: Select all
#### ADDED BY NAGIOSXI (USER: <USER>, DATE: 2013-10-15 13:03:11) ####
# Created by
# /usr/bin/cfgmaker --show-op-down --zero-speed=100000000000 --snmp-options=:::::2 --noreversedns <SNMP COMMUNITY>@<IP ADDRESS>
### Global Config Options
# for UNIX
# WorkDir: /home/http/mrtg
# or for NT
# WorkDir: c:\mrtgdata
### Global Defaults
# to get bits instead of bytes and graphs growing to the right
# Options[_]: growright, bits
EnableIPv6: no
######################################################################
# System:
# Description: Cisco IOS Software, 2801 Software (C2801-SPSERVICESK9-M), Version 12.4(6)T7, RELEASE SOFTWARE (fc5)
# Technical Support: http://www.cisco.com/techsupport
# Copyright (c) 1986-2007 by Cisco Systems, Inc.
# Compiled Thu 29-Mar-07 05:41 by khuie
# Contact:
# Location:
######################################################################
### Interface 1 >> Descr: 'FastEthernet0/0' | Name: 'Fa0/0' | Ip: '' | Eth: '30-78-30-30-31-33-31-61-35-64-63-39-39-61' ###
### The following interface is commented out because:
### * it is administratively DOWN
#
# Target[<IP ADDRESS>_1]: 1:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
# SetEnv[<IP ADDRESS>_1]: MRTG_INT_IP="" MRTG_INT_DESCR="FastEthernet0/0"
# MaxBytes[<IP ADDRESS>_1]: 12500000
# Title[<IP ADDRESS>_1]: Traffic Analysis for 1 --
# PageTop[<IP ADDRESS>_1]: <h1>Traffic Analysis for 1 -- </h1>
# <div id="sysdetails">
# <table>
# <tr>
# <td>System:</td>
# <td> in </td>
# </tr>
# <tr>
# <td>Maintainer:</td>
# <td></td>
# </tr>
# <tr>
# <td>Description:</td>
# <td>FastEthernet0/0 att-unman </td>
# </tr>
# <tr>
# <td>ifType:</td>
# <td>ethernetCsmacd (6)</td>
# </tr>
# <tr>
# <td>ifName:</td>
# <td>Fa0/0</td>
# </tr>
# <tr>
# <td>Max Speed:</td>
# <td>12.5 MBytes/s</td>
# </tr>
# </table>
# </div>
### Interface 2 >> Descr: 'FastEthernet0/1' | Name: 'Fa0/1' | Ip: '' | Eth: '30-78-30-30-31-33-31-61-35-64-63-39-39-62' ###
Target[<IP ADDRESS>_2]: 2:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_2]: MRTG_INT_IP="" MRTG_INT_DESCR="FastEthernet0/1"
MaxBytes[<IP ADDRESS>_2]: 12500000
Title[<IP ADDRESS>1_2]: Traffic Analysis for 2 --
PageTop[<IP ADDRESS>_2]: <h1>Traffic Analysis for 2 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>FastEthernet0/1 att-unman </td>
</tr>
<tr>
<td>ifType:</td>
<td>ethernetCsmacd (6)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Fa0/1</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>12.5 MBytes/s</td>
</tr>
</table>
</div>
### Interface 3 >> Descr: 'Serial0/1/0' | Name: 'Se0/1/0' | Ip: '' | Eth: '' ###
Target[<IP ADDRESS>_3]: 3:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_3]: MRTG_INT_IP="" MRTG_INT_DESCR="Serial0/1/0"
MaxBytes[<IP ADDRESS>_3]: 248000
Title[<IP ADDRESS>_3]: Traffic Analysis for 3 --
PageTop[<IP ADDRESS>_3]: <h1>Traffic Analysis for 3 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td><DESCRIPTION> </td>
</tr>
<tr>
<td>ifType:</td>
<td>frame-relay (32)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Se0/1/0</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>248.0 kBytes/s</td>
</tr>
</table>
</div>
### Interface 4 >> Descr: 'Null0' | Name: 'Nu0' | Ip: '' | Eth: '' ###
### The following interface is commented out because:
### * it is a cisco Null0 interface
#
# Target[<IP ADDRESS>_4]: 4:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
# SetEnv[<IP ADDRESS>_4]: MRTG_INT_IP="" MRTG_INT_DESCR="Null0"
# MaxBytes[<IP ADDRESS>_4]: 1250000000
# Title[<IP ADDRESS>_4]: Traffic Analysis for 4 --
# PageTop[<IP ADDRESS>_4]: <h1>Traffic Analysis for 4 -- </h1>
# <div id="sysdetails">
# <table>
# <tr>
# <td>System:</td>
# <td> in </td>
# </tr>
# <tr>
# <td>Maintainer:</td>
# <td></td>
# </tr>
# <tr>
# <td>Description:</td>
# <td>Null0 </td>
# </tr>
# <tr>
# <td>ifType:</td>
# <td>Other (1)</td>
# </tr>
# <tr>
# <td>ifName:</td>
# <td>Nu0</td>
# </tr>
# <tr>
# <td>Max Speed:</td>
# <td>1250.0 MBytes/s</td>
# </tr>
# </table>
# </div>
### Interface 6 >> Descr: 'Loopback0' | Name: 'Lo0' | Ip: '' | Eth: '' ###
### The following interface is commented out because:
### * it is a Software Loopback interface
#
# Target[<IP ADDRESS>_6]: 6:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
# SetEnv[<IP ADDRESS>_6]: MRTG_INT_IP="" MRTG_INT_DESCR="Loopback0"
# MaxBytes[<IP ADDRESS>_6]: 1000000000
# Title[<IP ADDRESS>_6]: Traffic Analysis for 6 --
# PageTop[<IP ADDRESS>_6]: <h1>Traffic Analysis for 6 -- </h1>
# <div id="sysdetails">
# <table>
# <tr>
# <td>System:</td>
# <td> in </td>
# </tr>
# <tr>
# <td>Maintainer:</td>
# <td></td>
# </tr>
# <tr>
# <td>Description:</td>
# <td>Loopback0 </td>
# </tr>
# <tr>
# <td>ifType:</td>
# <td>softwareLoopback (24)</td>
# </tr>
# <tr>
# <td>ifName:</td>
# <td>Lo0</td>
# </tr>
# <tr>
# <td>Max Speed:</td>
# <td>1000.0 MBytes/s</td>
# </tr>
# </table>
# </div>
### Interface 7 >> Descr: 'Serial0/1/0.100' | Name: 'Se0/1/0.100' | Ip: '' | Eth: '' ###
Target[<IP ADDRESS>_7]: 7:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_7]: MRTG_INT_IP="" MRTG_INT_DESCR="Serial0/1/0.100"
MaxBytes[<IP ADDRESS>_7]: 66000
Title[<IP ADDRESS>_7]: Traffic Analysis for 7 --
PageTop[<IP ADDRESS>_7]: <h1>Traffic Analysis for 7 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td><DESCRIPTION> </td>
</tr>
<tr>
<td>ifType:</td>
<td>frame-relay (32)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Se0/1/0.100</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>66.0 kBytes/s</td>
</tr>
</table>
</div>
-
snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: mrtg.cfg is huge
Another "exciting" development. I added another interface on a different router. This one is located in Sweden. This configuration is almost identical to the setup of the NON-working interface located in Germany. Same port name, same port type, same port speed and CDR, even the portions of the mrtg.cfg file that pertain to these ports is identical (as far as I can see) except for the obvious difference of IP and port number.
The strange part, is that the one in Sweden works, the one in Germany still does not...
The strange part, is that the one in Sweden works, the one in Germany still does not...
Re: mrtg.cfg is huge
Are the mrtg sections for both these interfaces the same, or even slightly different? If different, can you post the respective sections of you mrtg file?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
-
snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: mrtg.cfg is huge
They look the same to me, but I'll post them here anyway. Doesn't hurt to have a couple extra pairs of eyes on it. One thing to note. Usually, with the way these routers are configured, we monitor the sub-interfaces (in this case Se0/1/0.100), rather than the physical interfaces (Se0/1/0) because the sub-interfaces are configured for whatever CDR we pay for, while the port is configured slightly differently. On the working router, the sub-interface is the one that we added, and it's working fine. I logged into the Germany router (the one that isn't working) to look at the ports, and the sub-interface says it's not passing traffic, but the physical interface is. I thought that might have been my problem so I added the physical interface instead, but it still didn't work. A "sh int Se0/1/0" on the router itself shows that it definitely is passing traffic, though.
NON-working router sub-interface:
NON-working router physical interface (this interface is the one that is being monitored):
Working router sub-interface (the interface being monitored):
Working router physical interface:
NON-working router sub-interface:
Code: Select all
### Interface 7 >> Descr: 'Serial0/1/0.100' | Name: 'Se0/1/0.100' | Ip: '' | Eth: '' ###
Target[<IP ADDRESS>_7]: 7:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_7]: MRTG_INT_IP="" MRTG_INT_DESCR="Serial0/1/0.100"
MaxBytes[<IP ADDRESS>_7]: 66000
Title[<IP ADDRESS>_7]: Traffic Analysis for 7 --
PageTop[<IP ADDRESS>_7]: <h1>Traffic Analysis for 7 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>Serial0/1/0.100 PVC to RPM MNCBGED1P12-0525 sw0/1921 </td>
</tr>
<tr>
<td>ifType:</td>
<td>frame-relay (32)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Se0/1/0.100</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>66.0 kBytes/s</td>
</tr>
</table>
</div>
Code: Select all
### Interface 3 >> Descr: 'Serial0/1/0' | Name: 'Se0/1/0' | Ip: '' | Eth: '' ###
Target[<IP ADDRESS>_3]: 3:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_3]: MRTG_INT_IP="" MRTG_INT_DESCR="Serial0/1/0"
MaxBytes[<IP ADDRESS>_3]: 248000
Title[<IP ADDRESS>_3]: Traffic Analysis for 3 --
PageTop[<IP ADDRESS>_3]: <h1>Traffic Analysis for 3 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>Serial0/1/0 link to MGX/GFN/GSR MNCBGEE1.1.21.5.1 </td>
</tr>
<tr>
<td>ifType:</td>
<td>frame-relay (32)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Se0/1/0</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>248.0 kBytes/s</td>
</tr>
</table>
</div>
Code: Select all
### Interface 11 >> Descr: 'Serial0/1/0.100' | Name: 'Se0/1/0.100' | Ip: '' | Eth: '' ###
Target[<IP ADDRESS>_11]: 11:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_11]: MRTG_INT_IP="" MRTG_INT_DESCR="Serial0/1/0.100"
MaxBytes[<IP ADDRESS>_11]: 66000
Title[<IP ADDRESS>_11]: Traffic Analysis for 11 --
PageTop[<IP ADDRESS>_11]: <h1>Traffic Analysis for 11 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>Serial0/1/0.100 PVC to +VPN_Name;, RPM +RPM_PE; +RPM_Subinterface; Conn ID +PVC_ </td>
</tr>
<tr>
<td>ifType:</td>
<td>frame-relay (32)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Se0/1/0.100</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>66.0 kBytes/s</td>
</tr>
</table>
</div>
Code: Select all
### Interface 3 >> Descr: 'Serial0/1/0' | Name: 'Se0/1/0' | Ip: '' | Eth: '' ###
Target[<IP ADDRESS>_3]: 3:<SNMP COMMUNITY>@<IP ADDRESS>:::::2
SetEnv[<IP ADDRESS>_3]: MRTG_INT_IP="" MRTG_INT_DESCR="Serial0/1/0"
MaxBytes[<IP ADDRESS>_3]: 248000
Title[<IP ADDRESS>_3]: Traffic Analysis for 3 --
PageTop[<IP ADDRESS>_3]: <h1>Traffic Analysis for 3 -- </h1>
<div id="sysdetails">
<table>
<tr>
<td>System:</td>
<td> in </td>
</tr>
<tr>
<td>Maintainer:</td>
<td></td>
</tr>
<tr>
<td>Description:</td>
<td>Serial0/1/0 frame link to MGX +MGXport; +FRnumber; </td>
</tr>
<tr>
<td>ifType:</td>
<td>frame-relay (32)</td>
</tr>
<tr>
<td>ifName:</td>
<td>Se0/1/0</td>
</tr>
<tr>
<td>Max Speed:</td>
<td>248.0 kBytes/s</td>
</tr>
</table>
</div>
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: mrtg.cfg is huge
This may take a bit of work but can you post your entire mrtg.cfg? If you have multiple configs please post the config with the broken interface checks, and also post the first bit of the main mrtg.cfg up until the first interface starts. Thanks!
-
snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: mrtg.cfg is huge
Yeah that did take a while, heh. Here is the full mrtg.cfg with company info removed. The NON-working router is the last entry in the config, and I have added a comment where the config for that router begins. I had to upload as an attachment as it's to many characters to post.
You do not have the required permissions to view the files attached to this post.
-
sreinhardt
- -fno-stack-protector
- Posts: 4366
- Joined: Mon Nov 19, 2012 12:10 pm
Re: mrtg.cfg is huge
OK, so, we have a script that has been already setup and ready to properly parse out configs and separate them for mrtg optimization. I will do some quick testing this weekend and ship it off to you, but presently your config is still just going to be one gigantic config by the time you are done, fyi.
Nagios-Plugins maintainer exclusively, unless you have other C language bugs with open-source nagios projects, then I am happy to help! Please pm or use other communication to alert me to issues as I no longer track the forum.
-
snapon_admin
- Posts: 952
- Joined: Mon Jun 10, 2013 10:39 am
- Location: Kenosha, WI
- Contact:
Re: mrtg.cfg is huge
I'm confused what you mean by this:
Do you mean you have a script that is going to optimize my current mrtg config, but that we will have to live with it the way it is until I hear back from you? If that's the case, that's not a problem at all. Or are you saying that the script that is writing the mrtg.cfg file is already setup to optimize the format of the config?
This is only a small portion of what we will be adding overall, I just stopped here when I ran into an issue. If you mean that, in general, our config file will end up being gigantic by the time we are done, I have also already prepared for that. Until a better solution to mrtg is created, this is what we're planning to deal with. If need be, I'll break it up into multiple mrtg.cfg files so I don't run into issues further down the road. Also, I appreciate all the help from everyone so far. These forums have yet to let me down, so thanks for that.
Do you mean you have a script that is going to optimize my current mrtg config, but that we will have to live with it the way it is until I hear back from you? If that's the case, that's not a problem at all. Or are you saying that the script that is writing the mrtg.cfg file is already setup to optimize the format of the config?
This is only a small portion of what we will be adding overall, I just stopped here when I ran into an issue. If you mean that, in general, our config file will end up being gigantic by the time we are done, I have also already prepared for that. Until a better solution to mrtg is created, this is what we're planning to deal with. If need be, I'll break it up into multiple mrtg.cfg files so I don't run into issues further down the road. Also, I appreciate all the help from everyone so far. These forums have yet to let me down, so thanks for that.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: mrtg.cfg is huge
Yes the script will break up your configurations for you so they are checked separately. I think Spenser is still working on it.