January 2016 - Test - lists.nanog.org

Re: Equipment Supporting 2.5gbps and 5gbps
by Brandon Butterworth 28 Jan '16

28 Jan '16

> > With 10G it's been the opposite, nobody was using copper so SFP+ is > > cheap. Only recently has copper 10G started to become common, a bit too > > late to be worth bothering with now and as there are no copper SFP+ > > Having new servers switch to copper instead of sfp is a nuisance > > SFP+ Copper Twinax is another option for 10G to save on the transceivers I should have been more precise with terms. The context here is doing less than 10G to support old cat5/6 installations. I didn't mention Twinax as if you could use that you'd not need a 2.5 or 5g standard nor have a problem with recent servers coming with 10GbaseT instead of sfp+ when all your previous ones are connected to a SFP+ only switch with fibre or twinax cables. brandon

1 0

Google Contact
by Adam Loveless 28 Jan '16

28 Jan '16

Any Google engineers that can contact me off list? Seems our address space has been blacklisted by Google and we have to enter captchas for them now.

5 6

IX ARP Timeout
by Mike Hammett 28 Jan '16

28 Jan '16

So I'm looking at the policies, recommended configurations, etc. of other IXes. We try to model a lot of ourselves on what the Europeans do (even if we come up short in some areas). I was reading through the AMS-IX guide. https://ams-ix.net/technical/specifications-descriptions/config-guide#3.1 They recommend a four hour ARP timeout. Thoughts? Seems a bit excessive, but I don't have over 700 networks on my IX. That said, I don't have over 700 members on my IX generating a ton of ARP traffic, so I'm probably fine recommending a smaller value. I understand it's a balance between stale records and ARP volume. Just trying to gauge what the community thinks. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

5 4

GitHub outage - idle speculation thread
by Alex Forster 28 Jan '16

28 Jan '16

Github has been down for about two hours now. No good public information that I can find so far, except that they mention a "network disruption" in early status updates. However, nothing interesting is showing up in BGPlay (like a shift over to Prolexic due to a DDoS). Their colocation provider is Rackspace, but Rackspace hasn't posted about any wider issues. https://status.github.com/graphs/past_day Alex Forster

3 2

Peering Exchange
by Colton Conor 27 Jan '16

27 Jan '16

If a service provider or enterprise orders collocation at an Equinix Global Internet Exchange Point, and orders a port on the exchange from Equinix, then what happens? How does a provider actually peer with the peers on the exchange? Lets assume the SP or enterprise already has an ANS, transit from multiple providers, and a BGP router that can accept and hold full routes. You can see the members of the exchange on peeringdb.com. Many of the members say their policy is Open with little to no traffic requirements. So does just ordering a port to the exchange automatically connect you with all of these open providers, or do you have to contact each on individually?

18 24

The IPv6 Travesty that is Cogent's refusal to peer Hurricane Electric - and how to solve it
by Matthew D. Hardeman 27 Jan '16

27 Jan '16

Hi everyone, I know the long and storied history of Cogent and HE failing to peer for IPv6 and failing to provide (from either side) for IPv6 transit between their two networks has been mentioned and covered on this list before, but I am rather surprised it has not garnered much attention. Until recently, that is. I notice an increasing number of people tweeting at both HE and Cogent about the problem. From HE’s public statements on the matter, it’s pretty clear that they would gladly peer with Cogent for IPv6 but that Cogent declines to do this. I simply cannot understand Cogent’s logic on this. Cogent is the one loosing out here, to my way of thinking. They have far less IPv6 coverage than HE. I myself, on behalf of my employers, am a direct customer of IP transit services from both Cogent and HE. I don’t know about others similarly positioned, but my Cogent rep tries to call me at least twice a month. I’m going to start taking (more of) his calls and letting him know his account with us is in jeopardy come renewal time if Cogent can’t get a full IPv6 route table to happen. Today, with Cogent & HE as peers, I am world reachable via IPv6. If either peer went down however, part of the internet couldn’t reach me via IPv6 because either HE wouldn’t have a route or Cogent wouldn’t have a route. That’s ridiculous. Since Cogent is clearly the bad actor here (the burden being Cogent's to prove otherwise because HE is publicly on record as saying that they’d love to peer with Cogent), I’m giving serious consideration to dropping Cogent come renewal time and utilizing NTT or Zayo instead. While that would not immediately solve the problem that if the NTT or Zayo link went down, single-homed Cogent customers would loose access to me via IPv6, I’m actually ok with that. It at least lets ensures that when there is a problem, the problem affects only single-home Cogent clients. Thus, the problem is borne exclusively by the people who pay the bad actor who is causing this problem. That tends to get uncomfortable for the payee (i.e. Cogent). I intend to email my Cogent sales guy regarding this matter and make this a sticking point in every phone conversation I have with him. I call on others similarly situated to consider whether you may like to follow suit in this approach. I’ve come to believe that it’s best for my interests and I also believe that it’s best for the internet community at large, as ubiquitous worldwide routing of IPv6 becomes more essential with each passing day. In closing, I further add that it’s a mystery to me why Cogent wouldn’t desire an IPv6 peering with HE. Let’s face it, if any of us had to choose a single-home IPv6 internet experience, between HE or Cogent, we’d all choose HE. If those were the two options, HE is the “real” IPv6 internet and Cogent is a tiny sliver of the IPv6 internet. I have actually wondered if HE is holding IPv6 peering with Cogent hostage, contingent on peering all protocols (IPv4 and IPv6) with Cogent. There, I could see why Cogent might hesitate. To my knowledge, however, this is not the case and I have heard no public accusation that HE is imposing such a constraint. I would love to hear anyone from HE tell as much of the story as they are able. PS - As an aside, has anyone noticed HE’s been growing their network by leaps and bounds this past year? Direct peerings with AT&T and CenturyLink, more domestic US and Canadian POPs, and I believe the number of pathways across the North American continent has been improved substantially, too. Thanks, Matt Hardeman IPiFony Systems, Inc. AS6082

14 25

Multicast stream monitoring tools
by Murat Kaipov 27 Jan '16

27 Jan '16

Hello folks!We have an issue with some multicast streams. For some reason picture is very unstable in evening, during internet usage peak times. We have had monitor our links and uplinks and there wasn't any oversubscribtion. I looking for usefull multicast stream monitoring tool now. Any suggestion?Thank you!

7 8

Re: The IPv6 Travesty that is Cogent's refusal to peer Hurricane Electric - and how to solve it
by Brandon Butterworth 26 Jan '16

26 Jan '16

> From: Nick Hilliard <nick(a)foobar.org> > multihop bgp means that you don't have synchronised ethernet carrier > status between the provider and customer routers. This in turn means > that if there's an intermediate connectivity problem, bgp will need to > time out before it notices and reroutes. During this period, traffic > will be black-holed. This is a crock. It is but nobody worries about that, we trust route servers at IX carrying way more traffic than most of these access circuits. brandon

4 3

Programmable SFP+ Transcievers
by Colton Conor 26 Jan '16

26 Jan '16

What options are out there for re-programmable SFP and SFP+ transceivers? So far I have found both https://www.flexoptix.net/en/flexbox-v3-transceiver-programmer.html and http://solid-optics.com/tools/multi-fiber-tool/so-multi-fiber-tool-id1768.h… Is there anything else out there? Any opinions on these two companies? I believe they both require you to use their SFPs in order to program them, but I could be wrong.

14 17

Re: The IPv6 Travesty that is Cogent's refusal to peer Hurricane Electric - and how to solve it
by Brandon Butterworth 26 Jan '16

26 Jan '16

> From mark.tinka(a)seacom.mu Mon Jan 25 19:56:46 2016 > > On 25/Jan/16 21:28, Brandon Butterworth wrote: > > It is but nobody worries about that, we trust route servers at IX > > carrying way more traffic than most of these access circuits. > > Yes, but if those go belly-up, you have another exchange point to fall > back to, a bi-lateral peering session, or an upstream provider. Or all > three. Doesn't matter, if traffic is blackholed at an ix then it won't be failing over to another one. Same effect > A "critical" device falling over in my network is far worse prospect to > experience. The general case doesn't care about your network, it assumes you'd engineer that appropriately for the criticality and do something different/better if you need to. brandon

3 2