Re: Regarding Tunnel interface graph not polling
Posted: Tue Oct 08, 2019 12:08 pm
Hi,
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?
--> Yes the tunnel went to down state when I running the command.
Is the tunnel always up and never goes down?
---> It is down now.
Note: Please consider the 188.231.80.1_37, Tunnel1924448 as the other tunnel is down
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)
CODE: SELECT ALL
noHC[188.231.80.1_36]: yes
--> This option is not there for 188.231.80.1_37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
change line 1291 from
CODE: SELECT ALL
MaxBytes[188.231.80.1_36]: 12500
to
CODE: SELECT ALL
MaxBytes[188.231.80.1_36]: 1250000
---> Current Configuration existing
Target[188.231.80.1_37]: 37:[email protected]:161::::2
SetEnv[188.231.80.1_37]: MRTG_INT_IP="192.168.44.50" MRTG_INT_DESCR="Tunnel1924448"
MaxBytes[188.231.80.1_37]: 628000000
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Save the file and delete this file to remove the old bandwidth data
CODE: SELECT ALL
/var/lib/mrtg/188.231.80.1_36.rrd
---> rrd file has been deleted for 188.231.80.1_37.rrd
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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.
--> Still it is showing as zero only
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?
--> Yes the tunnel went to down state when I running the command.
Is the tunnel always up and never goes down?
---> It is down now.
Note: Please consider the 188.231.80.1_37, Tunnel1924448 as the other tunnel is down
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)
CODE: SELECT ALL
noHC[188.231.80.1_36]: yes
--> This option is not there for 188.231.80.1_37
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
change line 1291 from
CODE: SELECT ALL
MaxBytes[188.231.80.1_36]: 12500
to
CODE: SELECT ALL
MaxBytes[188.231.80.1_36]: 1250000
---> Current Configuration existing
Target[188.231.80.1_37]: 37:[email protected]:161::::2
SetEnv[188.231.80.1_37]: MRTG_INT_IP="192.168.44.50" MRTG_INT_DESCR="Tunnel1924448"
MaxBytes[188.231.80.1_37]: 628000000
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Save the file and delete this file to remove the old bandwidth data
CODE: SELECT ALL
/var/lib/mrtg/188.231.80.1_36.rrd
---> rrd file has been deleted for 188.231.80.1_37.rrd
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
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.
--> Still it is showing as zero only