Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread David Charlebois
Just read this on http://www.ctvnews.ca/business/bell-aliant-says- double-cable-cut-that-led-to-cell-outages-was-perfect-storm-1.3547018 "Bell spokesman Nathan Gibson says the first cut was by a highway construction crew near Drummondville, Que. He says service wasn't impacted in any significant

Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread JASON BOTHE
Interesting enough, we did not lose connectivity to our offices in PEI, so I assume there is some diversity from that point in the Bell network. J~ > On 15, Aug 2017, at 3:37 PM, Rod Beck wrote: > > Well Hibernia had those routes. I thought it would have been the 360 > terrestrial cable and H

Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread Rod Beck
Well Hibernia had those routes. I thought it would have been the 360 terrestrial cable and Hibernia's underwater cable from Halifax to their Boston landing station. From: NANOG on behalf of Clinton Work Sent: Tuesday, August 15, 2017 10:07 PM To: nanog@nanog.

Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread Clinton Work
I can't speak for the Bell Aliant network, but I'm only aware of two diverse fiber routes out of Halifax, Nova Scotia. Halifax -> New Brunswick -> Quebec City is the Canadian route and Halifax -> Boston is the diverse route. On Tue, Aug 15, 2017, at 01:52 PM, Jared Mauch wrote: > Perhaps some

Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread Jared Mauch
> On Aug 15, 2017, at 1:22 PM, Rod Beck wrote: > > Did we ever get any resolution on why this was such a big outage? Appears > there were two fiber cuts. Were the fibers damaged in the same conduit? Is > this a collapsed ring scenario? > > > http://www.cbc.ca/news/canada/newfoundland-labrado

Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread Rod Beck
In other words, bad luck. Probability dictates if enough time transpires, every bad thing will happen. 😝 From: NANOG on behalf of Clinton Work Sent: Tuesday, August 15, 2017 8:59 PM To: nanog@nanog.org Subject: Re: Last Week's Canadian Fiber Cut My understand

Re: Last Week's Canadian Fiber Cut

2017-08-15 Thread Clinton Work
My understanding is that the Bell Aliant outage was a double fault situation. Bell Aliant had a fiber cut on one of their fiber routes early in the morning and then they had a fault on the diverse fiber route before the first trouble could be repaired. On Tue, Aug 15, 2017, at 11:22 AM, Rod Be

Last Week's Canadian Fiber Cut

2017-08-15 Thread Rod Beck
Did we ever get any resolution on why this was such a big outage? Appears there were two fiber cuts. Were the fibers damaged in the same conduit? Is this a collapsed ring scenario? http://www.cbc.ca/news/canada/newfoundland-labrador/concerns-about-backup-bell-outage-1.4239064 Roderick Beck D

Re: Virtual or Remote Peering

2017-08-15 Thread Fredrik Korsbäck
How well does this service work? I understand it usually involves point-to-multipoint Switched Ethernet with VLANs and resold IX ports. Sounds like a service for ISP that would like to peer, but have relatively small volumes for peering purposes or lopsided volumes. Roderick Beck Director of

Virtual or Remote Peering

2017-08-15 Thread Rod Beck
How well does this service work? I understand it usually involves point-to-multipoint Switched Ethernet with VLANs and resold IX ports. Sounds like a service for ISP that would like to peer, but have relatively small volumes for peering purposes or lopsided volumes. Roderick Beck Director of

Re: (Network Orchestrators evaluation) : tail-f vs Anuta vs UBIqube vs OpenDaylight

2017-08-15 Thread James Bensley
On 10 August 2017 at 02:01, Kasper Adel wrote: > Hi, Hi Kim, > This is not a vendor bashing thread. > > We are a group of networking engineers less experience with software) in > the middle of the process of procuring a network automation/orchestration > controller, if that is even a good defin