<html theme="default-light" iconset="color"><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head><body text="#485663">Hi Simon,<br>
<br>
Yep, core bundles are inter-switch connections. You need to set the
port type to: "Core" instead of "Peering" or "Unknown". This should
sort out the graph aggregation.<br>
<br>
Nick<br>
<br>
<span>billynkid--- via ixpmanager wrote on 11/10/2022 05:13:</span><br>
<blockquote type="cite"
cite="mid:CADz3n9T=RQLKrD9W-N31LP784AkcWXUpwVbGhPmia+zNSiZ3-g@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr"><div>Hi IXP Manager Team,</div><div><br></div><div>We
are looking to add our intersite (core bundle?) links to IXP Manager.
However when we went through the core bundle wizard and added these
ports it add them to our overall aggregate traffic graph. Which seems
incorrect. We want to added these links for monitoring without them
counting towards our peering total as they don't. We just want to
monitor them for availability and traffic.</div><div><br></div><div>Q:
Are core bundles meant for intersite links?</div><div>Q: Do we need a
dedicated customer entry for our peering LAN to which we assign these
core bundles.</div><div>Q: If we have to create a second customer to
represent the Peering LAN how do we do that without it showing up on our
overall aggregate graphs? <br></div><div><br></div><div>Simon</div><div><br></div><div><br>--
<br><div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Simon Vass<br></div></div></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>
</body></html>