The issue is the roll-over problem.  With so many things being added, there is 
no reliable way to determine when the individual interface counters have rolled 
over.  The solution is to use RRD as the backend, routers2 as the front end, 
and create stacked graphs from the individual components.


From: mrtg <[email protected]> on 
behalf of Rwakagabo Janvier <[email protected]>
Date: Tuesday, May 8, 2018 at 02:55
To: Rwakagabo Janvier <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [mrtg] MTRG IN AND OUT TRAFFIC DON'T MATCH

Hello

Any comment on this issue??

Regards,

Janvier R.


On 7 May 2018, at 14:59, Rwakagabo Janvier 
<[email protected]<mailto:[email protected]>> wrote:

Hello

Can you assist on finding why MRTG aggregate graph is is not matching for 
inbound and outbound traffic graphs, check below the aggregate configuration in 
mrtg.cfg, and the graph that shows the mismatch.

<PastedGraphic-1.tiff>

Target[Aggregate_Traffic]: 
#xe-0/0/1:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/3:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/4:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/5:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/7:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/8:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/9:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/10:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/11:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/12:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/13:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/14:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/15:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/16:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/17:[email protected]<mailto:[email protected]>:::::2  + 
#xe-0/0/18:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/19:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/30:[email protected]<mailto:[email protected]>:::::2 + 
#ge-0/1/0:[email protected]<mailto:[email protected]>:::::2 + 
#ge-0/1/1:[email protected]<mailto:[email protected]>:::::2 + 
#ge-0/1/2:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/27:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/1/5:[email protected]<mailto:[email protected]>:::::2 + 
#ge-0/1/7:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/21:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/22:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/25:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/30:[email protected]<mailto:[email protected]>:::::2 + 
#ge-0/1/3:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/2/0:[email protected]<mailto:[email protected]>:::::2 + 
#xe-0/0/29:[email protected]<mailto:[email protected]>:::::2
MaxBytes[Aggregate_Traffic]: 1250000000

Title[Aggregate_Traffic]: Aggregate Traffic Analysis
PageTop[Aggregate_Traffic]: <H1>Aggregate Traffic Analysis</H1>
#Target[Aggregate_Traffic]: 1:[email protected]<mailto:[email protected]>: + 
2:[email protected]<mailto:[email protected]>: + 
3:[email protected]<mailto:[email protected]>: + 
4:[email protected]<mailto:[email protected]>: + 
5:[email protected]<mailto:[email protected]>: + 
6:[email protected]<mailto:[email protected]>: + 
7:[email protected]<mailto:[email protected]>: + 
8:[email protected]<mailto:[email protected]>: + 
9:[email protected]<mailto:[email protected]>: + 
10:[email protected]<mailto:[email protected]>: + 
11:[email protected]<mailto:[email protected]>: + 
12:[email protected]<mailto:[email protected]>: + 
13:[email protected]<mailto:[email protected]>: + 
14:[email protected]<mailto:[email protected]>: + 
15:[email protected]<mailto:[email protected]>: + 
16:[email protected]<mailto:[email protected]>: + 
17:[email protected]<mailto:[email protected]>: + 
18:[email protected]<mailto:[email protected]>: + 
19:[email protected]<mailto:[email protected]>: + 
20:[email protected]<mailto:[email protected]>: + 
21:[email protected]<mailto:[email protected]>: + 
22:[email protected]<mailto:[email protected]>: + 
23:[email protected]<mailto:[email protected]>: + 
24:[email protected]<mailto:[email protected]>: + 
25:[email protected]<mailto:[email protected]>: + 
26:[email protected]<mailto:[email protected]>: + 
27:[email protected]<mailto:[email protected]>: + 
28:[email protected]<mailto:[email protected]>: + 
29:[email protected]<mailto:[email protected]>: + 
30:[email protected]<mailto:[email protected]>: + 
31:[email protected]<mailto:[email protected]>:

x.x.x.x stands for IP of he switch

Regards,

Janvier R.


_______________________________________________
mrtg mailing list
[email protected]
https://lists.oetiker.ch/cgi-bin/listinfo/mrtg

Reply via email to