[FL-IX] AS4258 route issues

[Savvas Bout]

Confirmed, issue seems resolved. We've reactivated our sessions.

Met vriendelijke groet / Best Regards,

Savvas Bout

*Netrouting Data Facilities **a.new.experience*

*INT:* +31 88 045 46 00 *US:* +31 88 045 46 00 *EXT:* 221 *Skype*:
savvas_bout

*E:* savvas.bout at netrouting.com *I:* www.netrouting.com *Y**: A look inside
data center Spijkenisse <https://www.youtube.com/watch?v=EvifSn54QL0>*

*P*  *Please do not print this email unless it is absolutely
necessary. **Disclaimer:
This e-mail and any attachment sent with it are intended exclusively for
the addressee(s), and may not be passed on to, or made available for use by
any person other than the addressee(s). If this e-mail is not addressed to
you, we ask you to notify the sender by return e-mail and delete and
destroy the original e-mail and any copies. Netrouting rules out any and
every liability resulting from any electronic transmission.*

On Tue, May 31, 2016 at 10:57 AM, Michael Scott <mxsq at wolfe.net> wrote:

> Cameron,
>
> We have found the problem. One of peers in a remote location mistakenly
> started sending us a full route table and our max prefix was also
> misconfigured for this peer as well. The misconfiguration has been
> corrected and the peer session was temporarily shutdown.
>
> We apologize for the inconvenience to everyone.
>
>
> *Michael Scott | General Manager*
> *Wolfe Internet*
> ---------------------------------------------
> OFFICE: +1 (206) 414-7886
> EMAIL: mxsq at wolfe.net
> WEB: www.wolfe.net
> ---------------------------------------------
> Assistant: Karen Farmer
> office: (206) 414-7976
> email: karenf at wolfe.net
>
>
>
> On May 31, 2016, at 7:38 AM, Byrne, Cameron <Cameron.Byrne at T-Mobile.com
> <Cameron.Byrne at t-mobile.com>> wrote:
>
> This is correct, Wolf is blackholing IPv6 traffic.
>
> NOC, please remove them from route server.
>
> Wolf, please fix your stuff
>
> ping6 2600:: source  2607:fb90:12f0:5::1
> PING6 2600:: (2600::) from 2607:fb90:12f0:5::1: 56 data bytes
> Request 0 timed out
> Request 1 timed out
> Request 2 timed out
> Request 3 timed out
> Request 4 timed out
>
> --- 2600:: ping6 statistics ---
> 5 packets transmitted, 0 packets received, 100.00% packet loss
> traceroute6 2600:: source  2607:fb90:12f0:5::1
> traceroute to 2600:: (2600::) from 2607:fb90:12f0:5::1, 30 hops max, 16
> byte packets
> <snip>
> 3  2001:504:40:108::1:20  1.455 ms  1.232 ms  1.612 ms
> 4  * 2001:504:40:108::1:20  * *
> 5  * * *
> 6  * * *
> 7  * * *
> 8  * * *
> 9  * * *
>
>
>
> *From:* Members [mailto:members-bounces at lists.fl-ix.net
> <members-bounces at lists.fl-ix.net>] *On Behalf Of *Savvas Bout
> *Sent:* Tuesday, May 31, 2016 6:57 AM
> *To:* members at lists.fl-ix.net
> *Subject:* [FL-IX] AS4258 route issues
>
> Hi,
>
> Is anyone else experiencing route issues over AS4258? They seems to be
> sending about 14k prefixes over the routeserver but any traffic that is
> sent over these routes ends up dead:
>
> edge2-mx240.mia1.us# <http://edge2-mx240.mia1.us/> run show route
> receive-protocol bgp 2001:504:40:108::1:4 | match 4258 | count
> Count: 13818 lines
>
> Sample route:
>
> edge2-mx240.mia1.us# <http://edge2-mx240.mia1.us/> run show route
> 2a02:2770::21a:4aff:feac:4576
>
> inet6.0: 29919 destinations, 101600 routes (29916 active, 3 holddown, 0
> hidden)
> + = Active Route, - = Last Active, * = Both
>
> 2a02:2770::/32     *[BGP/170] 09:33:57, localpref 400, from
> 2001:504:40:108::1:4
>                       AS path: 4258 32248 6939 196752 I, validation-state:
> unverified
>                     > to 2001:504:40:108::1:41 via xe-1/3/0.11
>
>
> Met vriendelijke groet / Best Regards,
>
> Savvas Bout
>
> *Netrouting Data Facilities* *a.new.experience*
>
> *INT:* +31 88 045 46 00 *US: *+31 88 045 46 00 *EXT:* 221 *Skype*:
> savvas_bout
>
> *E:* savvas.bout at netrouting.com *I:* www.netrouting.com *Y**: A look
> inside data center Spijkenisse
> <https://www.youtube.com/watch?v=EvifSn54QL0>*
>
> *P*  *Please do not print this email unless it is absolutely necessary. **Disclaimer:
> This e-mail and any attachment sent with it are intended exclusively for
> the addressee(s), and may not be passed on to, or made available for use by
> any person other than the addressee(s). If this e-mail is not addressed to
> you, we ask you to notify the sender by return e-mail and delete and
> destroy the original e-mail and any copies. Netrouting rules out any and
> every liability resulting from any electronic transmission.*
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fl-ix.net/pipermail/members/attachments/20160531/b2081210/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 14500 bytes
Desc: not available
URL: <http://lists.fl-ix.net/pipermail/members/attachments/20160531/b2081210/attachment.png>