[outages] VPN issues over Spectrum L3 boundaries

[Marty Adkins]

After getting the right TW/Spectrum folks involved, this was solved by a 
routing change.  Traffic from OH and PA sites now traverse an L3 peering 
point at Newark, and the NC site now goes via Atlanta.  The problematic 
one-way path peered in D.C. and a TW team is still working to resolve 
whether that's their issue or within L3.  Supposedly the routing changes 
that were made on Oct 22 would affect other customers as well.

-Marty

On 10/21/2019 2:19 PM, Marty Adkins wrote:
> No change for them because the one head-end is fed by L3, so there's 
> no way it can vanish from the path.  :)
>
> On 10/21/2019 1:39 PM, Biddle, Josh wrote:
>>
>> Our issues have recently magically resolved (last Thursday 10/17) due 
>> to L3 vanishing from the hop list. Our traffic now disappears into 
>> ntt.net and we are seeing two way IPsec traffic without any issues.
>>
>> Marty, did your issues resolve?
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20191024/a1a2b524/attachment.htm>