July 2014 - Test - lists.nanog.org

Peering Latency
by Sam Norris 04 Jul '14

04 Jul '14

Hey all - new to the list but not to the community... Wondering if this is typical when there is too small of a pipe between peering arrangements: >From Level3 to Time Warner ADDRESS STATUS 2 4.69.133.206 4ms 4ms 4ms 3 4.69.153.222 9ms 4ms 4ms 4 4.69.158.78 8ms 4ms 4ms (L3) 5 66.109.9.121 28ms 53ms 29ms (TWC) <------ 6 107.14.19.87 30ms 28ms 28ms 7 66.109.6.213 27ms 28ms 28ms 8 72.129.1.1 32ms 32ms 32ms 9 72.129.1.7 27ms 26ms 25ms 10 67.52.158.145 28ms 29ms 31ms >From TWC to Level3 # ADDRESS RT1 RT2 RT3 STATUS 2 24.43.183.34 5ms 5ms 6ms 3 72.129.1.14 8ms 8ms 8ms 4 72.129.1.2 6ms 8ms 8ms 5 107.14.19.30 7ms 8ms 8ms 6 66.109.6.4 8ms 8ms 8ms 7 107.14.19.86 5ms 5ms 5ms 8 66.109.9.122 34ms 33ms 31ms (TWC) <------ 9 4.69.158.65 31ms 30ms 29ms (L3) 10 4.69.153.221 33ms 33ms 34ms 11 4.69.133.205 32ms 32ms 31ms I am showing, typically at night, a 20-40ms jump when hopping from Level3 to Time Warner and back in Tustin, CA. This does not happen when using Cogent or other blended providers bandwidth. I believe they are probably stuffing too many bits thru the peering there and wondering whats the best way to prove to them both (we pay for both) that they need to fix it. During non-peak traffic times these look normal (sub 10s). Sam

3 2

cant reach beyond 129.250.x.y
by Miguel Mata 03 Jul '14

03 Jul '14

Hi guys and gals, somehow it seems that just part of our network (a /24) can't reach beyond "NTT America, Inc." We seem to stop on 129.250.193.186. Somebody from NTT can contact me off list please. -- Miguel Mata El Salvador CTO Comunicaciones IBW El Salvador tel.: ++(503) 2278-5068 fax: ++(503) 2207-1310 mmata(a)ibw.com "La confianza es la mejor conexion"

2 1

Re: Feedback Requested: Routing Resilience Manifesto
by Larry Sheldon 03 Jul '14

03 Jul '14

On 7/3/2014 3:31 AM, Suresh Ramasubramanian wrote: > On Thu, Jul 3, 2014 at 1:00 PM, David Hofstee <david(a)mailplus.nl> > wrote: >> About #3... I had a little discussion on abuse-wg@RIPE a while ago >> about keeping records up to date and relevant. See below. >> >> Nobody at RIPE cares much at the moment (to actually pick up this >> subject). Maybe they need a push with a TerexRH400. > > You get a lot of network and DNS types and maybe 1% of them will be > concerned with the mechanics of abuse prevention - that's the other > group down the hall, and "they are not the internet police". Which, I maintain,, is why the "manifesto" needs to be recast for Management, because it is Management that is supposed to define mission goals and job assignments, which might very well involve operation as network police for the local piece of The Internet (which does in fact extend to the end devices in your shop). Ah > well .. maybe that's better than hamfisted lanham act takedowns of > whitehat dynamic dns providers - but those are two extremes. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

1 0

GVT Brazil - contact
by Oliver Doug 03 Jul '14

03 Jul '14

There are anyone up there from GVT Brazil who are able to contact me inbox? Having some issues to hire a fixed phone number plan to a customer. Cheers, Douglas S. Oliveira Eletel Telecom +55 19 9 8182-8816 +55 19 9 9915-0538

2 1

Feedback Requested: Routing Resilience Manifesto
by Andrei Robachevsky 03 Jul '14

03 Jul '14

Colleagues, A small group of network operators has been working on defining a minimal, but feasible package of recommended measures that, if deployed on a wide scale, could result in visible improvements to the security and resilience of the global routing system. Many operators are ahead of the curve and already implement much more than the proposed recommendations. But we believe that gathering support for these relatively small steps could pave the road to more significant actions on a global scale. We called this set of recommendations a Routing Resilience Manifesto – you can find a draft document here: https://www.routingmanifesto.org/. This initial version of the Manifesto was drafted by a small group, but we need a wider community review, your feedback, and, ultimately, your support to make this initiative fly. It was already presented at several venues, like RIPE and NANOG, and now we open it for a more detailed review. Please note that this is very much a work in progress. Please review the document and provide your feedback and text suggestions online or via routingmanifesto(a)isoc.org by 31 August 2014. Regards, Andrei Robachevsky Internet Society

9 11

Re: Feedback Requested: Routing Resilience Manifesto
by Scott Weeks 02 Jul '14

02 Jul '14

--- mpetach(a)netflight.com wrote: From: Matthew Petach <mpetach(a)netflight.com> Once that's done, all that's left is the naked routing run. With the way temperatures have been, I'm all in favour of that--pick a date, let's make it happen! --------------------------------------------------------- Nooooooo!!!! A buncha hefty NANOGers running naked? Noooo!!!! Like Valdis said, where's the mind bleach??? :-) scott

1 0

Re: Feedback Requested: Routing Resilience Manifesto
by Larry Sheldon 02 Jul '14

02 Jul '14

On 7/2/2014 1:00 PM, Jared Mauch wrote: > > On Jul 2, 2014, at 1:52 PM, William Herrin <bill(a)herrin.us> wrote: > >> People will notice you streaking across a football field. They won't >> pay the slightest attention to what you have to say but they sure will >> notice you. Shall we organize a naked routing run? > > No, but how else do you suggest we work to address these problems? I am no longer active in the field, but back in the day, the ways of successfully selling stuff to management involved some mix of: It will improve sales. It will reduce costs. It will allow you to do something you want to do. It will keep you out of court and jail. No variation "It is the right thing to do" ever worked unless management thought of it. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

4 3

softlayer network contact
by jason matthews 02 Jul '14

02 Jul '14

can someone from softlayer/networklayer contact me off list please. thanks, j. Jason Matthews VP of Technical Operations Apsalar, Inc.

1 0

Re: Feedback Requested: Routing Resilience Manifesto
by Larry Sheldon 02 Jul '14

02 Jul '14

On 7/2/2014 11:20 AM, William Herrin wrote: > Seriously, manifesto? What's next, some routing unabombers? Oh wait, I > guess we already have those, don't we? Seriously. And it is actually a deeper wound than that. The whole document (or as much of it as I was willing to read, anyway) is worded like it had been copied out of the Ernesto Guevara Handbook. -- Requiescas in pace o email Two identifying characteristics of System Administrators: Ex turpi causa non oritur actio Infallibility, and the ability to learn from their mistakes. (Adapted from Stephen Pinker)

1 0

Erroneous Leap Second Introduced at 2014-06-30 23:59:59 UTC
by Tim Heckman 02 Jul '14

02 Jul '14

Hey Everyone, I just was alerted to one of the systems I managed having a time skew greater than 100ms from NTP sources. Upon further investigation it seemed that the time was off by almost exactly 1 second. Looking back over our NTP monitoring, it would appear that this system had a large time adjust at approximately 00:00 UTC: - http://puu.sh/9Rs6O/a514ad7c97.png (times are in Pacific in these graphs, sorry about that) A few of our systems did alert early this morning, indicating they were going to be receiving a leap second today. However, I was unable to determine the exact cause for NTP believing a leap second should be added. And after some time a few of the systems were no longer indicating that a leap second would be introduced. This specific system is hosted in AWS US-WEST-2C and uses the 0.amazon.pool.ntp.org pool. Has anyone else seen any erroneous leap seconds being added to their system? Cheers! -Tim Heckman

3 5