<html theme="default-light" iconset="color"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body style="font-family: Calibri; font-size: 14px;" 
text="#485663"><div style="font-size: 14px;font-family: Calibri;">Hi 
Mauricio<br><br>Mauricio Oviedo via ixpmanager wrote on 15/04/2024 
05:19:<blockquote type="cite" style="word-wrap:break-word"><meta 
http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Aptos;
        panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0cm;
        font-size:11.0pt;
        font-family:"Aptos",sans-serif;
        mso-ligatures:standardcontextual;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:#467886;
        text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0cm;
        margin-right:0cm;
        margin-bottom:0cm;
        margin-left:36.0pt;
        font-size:11.0pt;
        font-family:"Aptos",sans-serif;
        mso-ligatures:standardcontextual;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Aptos",sans-serif;
        color:windowtext;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:11.0pt;}
@page WordSection1
        {size:612.0pt 792.0pt;
        margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:1073429591;
        mso-list-type:hybrid;
        mso-list-template-ids:-1164441426 1522680882 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-text:%1-;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-18.0pt;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0cm;}
ul
        {margin-bottom:0cm;}
--></style>


<div class="WordSection1">However, I didn’t inmmediatly marked the old 
switches as inactive, and some member ports that were no longer 
connected were still associated to the old Switches. As a result the 
member ports and switch MRTG graphs were OK, but the aggregated
 overall graph did not graph anymore.<o:p></o:p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">After a long weekend I found these 2 posts where I 
got pointers about deactivating the old switches and do some clean up on
 the unused ports:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a 
href="https://www.inex.ie/pipermail/ixpmanager/2021-April/003183.html">https://www.inex.ie/pipermail/ixpmanager/2021-April/003183.html</a><o:p></o:p></p>
<p class="MsoNormal"><a 
href="https://www.inex.ie/pipermail/ixpmanager/2019-July/002297.html">https://www.inex.ie/pipermail/ixpmanager/2019-July/002297.html</a><o:p></o:p></p></div></blockquote><br>Yeah.
 This is one of those situations where if the data source is incorrect, 
there's a risk of running into problems :(<br><o:p> </o:p>
<blockquote type="cite" style="word-wrap:break-word"><div 
class="WordSection1"><p class="MsoNormal">Here a couple of questions:<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<ol style="margin-top:0cm" start="1" type="1">
<li class="MsoListParagraph" style="margin-left:0cm;mso-list:l0 level1 
lfo1">Why the aggregated graph stops working if a Switch or port cannot 
be polled by SNMP?</li></ol></div></blockquote><br>This is how MRTG 
works.  If you specify data endpoints which don't exist, then MRTG 
doesn't handle aggregate graphs.  It's a known problem with MRTG.<br><br><blockquote
 type="cite" style="word-wrap:break-word"><div class="WordSection1"><ol 
style="margin-top:0cm" start="1" type="1"><li class="MsoListParagraph" 
style="margin-left:0cm;mso-list:l0 level1 lfo1">Given that the member 
and switch graphs were OK and the information exists, is it possible to 
rebuild the aggregated graph to include the missing data? (Around 30hrs)</li></ol></div></blockquote><br>This
 isn't easy. It's possible to add up the various columns in the mrtg log
 files, but you'll likely find that the 5m maximum in+out figures will 
be incorrect due to how mrtg calculates them. The average in/out figures
 will be correct though.<br><br><blockquote type="cite" 
style="word-wrap:break-word"><div class="WordSection1"><ol 
style="margin-top:0cm" start="1" type="1"><li class="MsoListParagraph" 
style="margin-left:0cm;mso-list:l0 level1 lfo1">What would be the 
recommended procedure to remove a Switch without loosing historical 
graphs? (Right now the switches are inactive, but still in IXP Manager)</li></ol></div></blockquote><br>Two
 options here: you can replace a switch and use the same switch profile,
 or you can leave them defined as active in IXP Manager, but de-select 
the "poll" button. <br><br><blockquote type="cite" 
style="word-wrap:break-word"><div class="WordSection1"><ol 
style="margin-top:0cm" start="1" type="1"><li class="MsoListParagraph" 
style="margin-left:0cm;mso-list:l0 level1 lfo1">What would be the 
recommended procedure to upgrade a member with 3x 10G ports in LAG to a 
100G port, without loosing historical graphs?</li></ol></div></blockquote><br>If
 you delete the 3 physical ports in the virtualinterface, then add the 
new 100G port on the new switch, it should keep the aggregate intact.1<br><br>Nick<br><br><br><blockquote
 type="cite" style="word-wrap:break-word"><div class="WordSection1"><ol 
style="margin-top:0cm" start="1" type="1"><li class="MsoListParagraph" 
style="margin-left:0cm;mso-list:l0 level1 lfo1"><o:p></o:p></li></ol>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
<p class="MsoNormal">Mauricio<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>



<br><fieldset class="mimeAttachmentHeader"></fieldset><br><pre wrap="">_______________________________________________
INEX IXP Manager mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ixpmanager@inex.ie">ixpmanager@inex.ie</a>
Unsubscribe or change options here: <a class="moz-txt-link-freetext" href="https://www.inex.ie/mailman/listinfo/ixpmanager">https://www.inex.ie/mailman/listinfo/ixpmanager</a>
</pre></blockquote><br></div></body></html>