<html dir="ltr"><head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page Section1 {margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"
}
SPAN.EmailStyle18 {
COLOR: #1f497d; FONT-FAMILY: "Calibri","sans-serif"
}
.MsoChpDefault {
FONT-SIZE: 10pt
}
DIV.Section1 {
}
</style>
<meta content="MSHTML 6.00.6000.16705" name="GENERATOR">
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
</head>
<body lang="EN-US" vlink="purple" link="blue" ocsi="x">
<div dir="ltr"><font face="Tahoma" color="#000000" size="2">As Azrol said, this is due to using SNMPv1, and the MRTG counter rollover detection.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">If you use SNMPv1 you get 32bit counters, which roll over at about 120Mbps. So, above 100Mbps, you should use SNMPv2 64bit counters.
</font></div>
<div dir="ltr"><font face="tahoma" size="2">If you do a calculation in the Target[] definition, then rollover is calculated AFTER the calculation, and so unless you are using 64bit counters, the TOTAL must be less than 120Mbps, which yours is not - so MRTG
incorrectly assumes counter rollover and gets it wrong.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">Use SNMPv2, or if you use Routers2 use a userdefined summary instead, then it will work as you will avoid MRTG rollover problems.</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">To use SNMPv2, add ':::::2' to the end of each Target component (provided your router supports SNMPv2, of course)</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div dir="ltr"><font face="tahoma" size="2">Steve</font></div>
<div dir="ltr"><font face="tahoma" size="2"></font> </div>
<div id="divRpF625088" style="DIRECTION: ltr">
<hr tabindex="-1">
<span style="COLOR: #1f497d">It may cause by snmp version. Please use snmpv2 instead of snmpv1.</span></div>
<div>
<div class="Section1">
<p class="MsoNormal"><span style="COLOR: #1f497d">-- Azrol --</span></p>
<p class="MsoNormal"><span style="COLOR: #1f497d"></span> </p>
<div>
<div style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
MRTG of two interfaces are working well but the aggregation graph sometimes is showing wrong graph. It seems it is just forgetting to sum up the graphs.</div>
</div>
<p class="MsoNormal"> </p>
<p class="MsoNormal">i.e. </p>
<p class="MsoNormal">interface 1 current in: 64.93Mb out:18.04Mb</p>
<p class="MsoNormal">interface 2 current in:59.33 Mb out:3.12Mb</p>
<p class="MsoNormal">int1+int2 current in :11.32 Mb out: 21.17Mb</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
</div>
</div>
</body>
</html>