Hi all,
So my domestic tables now have some 76,000 prefixes in them, as of ~ 6:30 last
night.
I guess hello HE and welcome to AKL-IX?
Domestic table for NZ was more like ~ 10,000 prefixes not that long ago!
--
Michael
___
NZNOG mailing list
NZNOG@li
They moved into 220q a few weeks back, routes went live on Megaport
Auckland yesterday.
They’re also selling transit now in Auckland, (great to see more options
arriving locally).
It does however seem that Auckland is just an extension of their Sydney POP
with traffic going AKL>SYD>USA.
On Wed,
On Wed, 19 Sep 2018 10:41:45 +1200
Michael Fincham wrote:
> I guess hello HE and welcome to AKL-IX?
Sorry, Megaport.
--
Michael
___
NZNOG mailing list
NZNOG@list.waikato.ac.nz
https://list.waikato.ac.nz/mailman/listinfo/nznog
One would assume however that being based at 220q they will also pickup
AKL-IX in due course as the other main Auckland IX.
On Wed, 19 Sep 2018 at 10:47 AM, Michael Fincham
wrote:
> On Wed, 19 Sep 2018 10:41:45 +1200
> Michael Fincham wrote:
>
> > I guess hello HE and welcome to AKL-IX?
>
> Sor
In progress
So please adjust your filters accordingly in preparation! :)
We will send out an email to AKL-IX participants shortly.
Thanks
Joe
> On 19 Sep 2018, at 6:56 am, Liam Farr wrote:
>
> One would assume however that being based at 220q they will also pickup
> AKL-IX in due course as t
HE peers everywhere they can, so yes I assume you'll see them on AKL-IX
too... APE might depend if they see value, last I checked between MegaIX
and AKL-IX you collected most of the routes on APE direct or indirect.
To be honest none of the IX's in AKL have been truely domestic for a long
time, th
Eek, I wonder if this is why my NZ domestic table size had a blow out at
around 0100 this morning and tipped one of my (smaller) boxes over the
edge...
I've spent all morning trying to triage the damn thing, knowing that the
BGP table had blown out and taken all of the TCAM memory...
We're still
Yes,
This is exactly why this happened. Vocus made a change around 0050 this
morning. We dropped some peerings when the prefix limits breached.
If your box isn't coping you could consider rejecting routes received from
Megaport with HE in the path.
Cam
-Original Message-
From: nznog-b
Thanks Cam, good idea
Turns out that the node in question only has one exit point to the
internet anyway (now), so it only really needs a default route for IPv4
and the same for IPv6
Problem solved!
Regards,
Mike
Mike Taylor
The Total Team
XMPP: mike.totalt...@gmail.com
0800 888 326 / +64
OK, so the routes are on AKL-IX now [cue a bunch more peoples import limits
breaking again].
Did we not learn anything from the last time this broke a whole bunch of stuff?
HE needs to be giving us some heads up before they turn up here and increase
the size of NZ's domestic route table by an o
Megaport AKL emailed their customers multiple times about HE turning up
their services.
NZIX also emailed.
So I assume its just 'domestic' transit providers that maybe aren't
notifying us?
Dave
On Wed, Sep 19, 2018 at 4:17 PM, Michael Fincham
wrote:
> OK, so the routes are on AKL-IX now [cue
On Wed, 19 Sep 2018 16:23:56 +1200
Dave Mill wrote:
> Megaport AKL emailed their customers multiple times about HE turning up
> their services.
>
> NZIX also emailed.
>
> So I assume its just 'domestic' transit providers that maybe aren't
> notifying us?
I don't think this is the right way to
On Wed, 19 Sep 2018 16:25:35 +1200
Michael Fincham wrote:
> I don't think this is the right way to look at it. Those routes are going to
> end up in everyone's "domestic" feeds. HE should have been here on NZNOG
> months ago making sure everyone was OK with this and ready.
And to elaborate on
They did notify, "months ago" back in June... (as below) and again
yesterday.
---
Date: Tue, 18 Sep 2018 at 11:30
Subject: Re: [Megaport Auckland IX] Upcoming large increase in prefixes
from MegaIX Auckland Route Servers
To:
Hi AKL peers,
Just a reminder regarding t
Did the AKL-IX people send an email ahead of this?
I ask because we didn't see anything so I'm wondering if we just lost it in
a spam folder somewhere or if others got missed also.
Thanks,
Dylan
On 19 September 2018 at 16:23, Dave Mill wrote:
> Megaport AKL emailed their customers multiple t
We didn’t get an email from akl IX either
On Wed, 19 Sep 2018 at 4:27 PM, Dylan Hall wrote:
> Did the AKL-IX people send an email ahead of this?
>
> I ask because we didn't see anything so I'm wondering if we just lost it
> in a spam folder somewhere or if others got missed also.
>
> Thanks,
>
>
On Wed, 19 Sep 2018 16:27:16 +1200
Liam Farr wrote:
> They did notify, "months ago" back in June... (as below) and again
> yesterday.
Yes, but how is this meant to filter out to all the other operators not on that
exchange exactly, who have spent much of the day fixing things and helping
other
If your not on the exchange directly, you only buy (domestic) transit from
an upstream, and your upstream didn't notify you... perhaps its time to
find a new upstream or have a long hard chat with your account manager /
their ops team?
On Wed, 19 Sep 2018 at 16:29, Michael Fincham
wrote:
> On We
> On 19/09/2018, at 4:28 PM, Michael Fincham wrote:
>
> On Wed, 19 Sep 2018 16:27:16 +1200
> Liam Farr wrote:
>
>> They did notify, "months ago" back in June... (as below) and again
>> yesterday.
>
> Yes, but how is this meant to filter out to all the other operators not on
> that exchange
On Wed, 19 Sep 2018 16:32:09 +1200
Nathan Ward wrote:
> Through whoever you buy domestic transit from - communication for these sorts
> of changes, and if required protecting customers who want to run such a
> service on c2610s, is a core part of such a service. If your transit
> providers are
The IX’s mailed out to their customers, I guess they assumed it would be
unwelcome noise and that members of the exchanges would get notified that way
Nathan Brookfield
Chief Executive Officer
Simtronic Technologies Pty Ltd
http://www.simtronic.com.au
On 19 Sep 2018, at 14:36, Michael Fincham
On Wed, Sep 19, 2018 at 4:35 PM, Michael Fincham
wrote:
> On Wed, 19 Sep 2018 16:32:09 +1200
> Nathan Ward wrote:
>
> > Through whoever you buy domestic transit from - communication for these
> sorts of changes, and if required protecting customers who want to run such
> a service on c2610s, is
Hey All,
We have only opened the filters for HE up on one of our route servers (RS2). We
chose RS2 because unfortunately only 50% of our peers have actually bothered to
configure their session to this route server.
The reason we chose to do it this way is to reduce the impact on participants.
IMO I think its great that a large carrier has come to our neck of the
woods, and they are openly peering on both our major IX's. This is a good
thing for internet in NZ.
Notifications were sent to the affected parties who peer, months in advance.
I don't believe HE had any malicious intent to br
On Wed, 19 Sep 2018 16:39:50 +1200
Liam Farr wrote:
> IMO I think its great that a large carrier has come to our neck of the
> woods, and they are openly peering on both our major IX's. This is a good
> thing for internet in NZ.
No contest. And I'm sure HE isn't here intentionally breaking the I
Perhaps those that had issues should use such tools as prefix limits on their
inbound feeds. We get notified by our edge routers quite regularly that the
number of prefixes has or is about to max out.
Sent from my iPhone
> On 19/09/2018, at 4:39 PM, Liam Farr wrote:
>
> IMO I think its great
Don't forget that the NZ/AU concept of 'domestic table' is a fairly unique
concept that isn't seen in much of the rest of the world- generally any
feed is going to be default, a peering feed (customer routes), or a full
table Doubt anyone thought of it ;).
Congrats to Mike & Walt on extending
If I can ask, what does a "domestic" table genuinely bring you. If you
carry routes to your edge(s) that have both peering and transit, do you
need to extend the DFZ all the way through your network? If you've got a
single exit path (or a few) do you need to extend the domestic routes any
further?
Buying 'domestic' is a way of paying for the privilege of sending/receiving
traffic to Spark :)
On Wed, Sep 19, 2018 at 5:02 PM, Tom Paseka
wrote:
> If I can ask, what does a "domestic" table genuinely bring you. If you
> carry routes to your edge(s) that have both peering and transit, do you
>
I'd call that partial transit ;-)
(BGP sanity questions remain).
On Tue, Sep 18, 2018 at 10:05 PM Dave Mill wrote:
> Buying 'domestic' is a way of paying for the privilege of
> sending/receiving traffic to Spark :)
>
> On Wed, Sep 19, 2018 at 5:02 PM, Tom Paseka
> wrote:
>
>> If I can ask, wha
Hi,
It’s been around here for a long time. Perhaps it’s a bit dated these days,
sure.
Getting through cables was expensive, so people offered connectivity to other
NZ networks at a significantly cheaper price (think at least an order of
magnitude).
It wasn’t always delivered as seperate trans
31 matches
Mail list logo
