March 2016 - Test - lists.nanog.org

Juniper QFX5200-32C junos base services license and BGP
by Stanislaw 04 Mar '16

04 Mar '16

Hi, Does anyone has a QFX5200-32C gear with a "Junos Base Services" license? Does that license technically allow running BGP? Currently I have a QFX5100 which only gives me warning "This feature requires a license" during commit but BGP routing works fine. So I'm wandering if that trick works in QFX5200..

4 3

Re: Juniper QFX5200-32C junos base services license and BGP
by Kenneth McRae 03 Mar '16

03 Mar '16

1 0

About inetnum "ownership"
by Jérôme Nicolle 03 Mar '16

03 Mar '16

Hi, How come we've had an inetnum market in place whereas an inetnum cannot have a market value ? It's my understanding that the IP adress space is nothing but numbers and that RIR/LIRs are only responsible for the uniqueness of allocations and assignements, that is, a transfer of liability over a shared and common immaterial resource, between community members. I'm wondering how did we made "Temporary and conditionnal liabality transfer" a synonym of "perpetual and inconditional usufruct transfer". May you please enlight me ? Thanks ! -- Jérôme Nicolle +33 6 19 31 27 14

11 18

sFlow vs netFlow/IPFIX
by Todd Crane 03 Mar '16

03 Mar '16

This maybe outside the scope of this list but I was wondering if anybody had advice or lessons learned on the whole sFlow vs netFlow debate. We are looking at using it for billing and influencing our sdn flows. It seems like everything I have found is biased (articles by companies who have commercial offerings for the "better" protocol) Todd Crane

16 55

Cogent & Google IPv6
by Ian Clark 02 Mar '16

02 Mar '16

Anyone know what's actually going on here? We received the following information from the two of them, and this just started a week or so ago. *From Cogent, the transit provider for a branch office of ours:* Dear Cogent Customer, Thank you for contacting Cogent Customer Support for information about the Google IPv6 addresses you are unable to reach. Google uses transit providers to announce their IPv4 routes to Cogent. At this time however, Google has chosen not to announce their IPv6 routes to Cogent through transit providers. We apologize for any inconvenience this may cause you and will notify you if there is an update to the situation. *From Google (re: Cogent):* Unfortunately it seems that your transit provider does not have IPv6 connectivity with Google. We suggest you ask your transit provider to look for alternatives to interconnect with us. Google maintains an open interconnect policy for IPv6 and welcomes any network to peer with us for access via IPv6 (and IPv4). For those networks that aren't able, or chose not to peer with Google via IPv6, they are able to reach us through any of a large number of transit providers. For more information in how to peer directly with Google please visit https://peering.google.com -- Ian Clark Lead Network Engineer DreamHost

14 22

Juniper PTX1000
by Peter Kranz 02 Mar '16

02 Mar '16

Anyone played with the newish Juniper PTX1000 platform? Seems quite interesting for compact deployments, but I've not been able to find much pricing information to see just how interesting.. Peter Kranz www.UnwiredLtd.com <http://www.unwiredltd.com/> Desk: 510-868-1614 x100 Mobile: 510-207-0000 pkranz(a)unwiredltd.com <mailto:pkranz@unwiredltd.com>

2 1

BGP MVPN RFC6513, Section 10
by Jason Iannone 02 Mar '16

02 Mar '16

Hi all, I'm having trouble interpreting under what circumstance section 10 of BGP MVPN comes into play. The way I read this section, upon the receipt of PIM/IGMP Join to (*,G) the Receiver Site PE does not signal Type 6 or Type 7 Joins until a Type 5 Source Active route is received from a Sender Site PE. If Section 10 assumes the use of ASM groups in the VPN, why develop a Type 6 Shared Tree Join A-D route for unknown sources? What are the practical minimum Juniper configurations to support Section 10 for ASM and (*,G) PIM Join when the PE doesn't know a source? CE1---PE1,C-RP-----P-----PE2---CE2 Sender Site-------------------Receiver Site 1. CE1 has no active source 2. CE2 forwards PIM Join (*,G) to PE2 toward PE1,C-RP 3. PE2 eats PIM Join, maintains (*,G) state 4. CE1 generates Register messages to PE1 5. PE1 originates Type 5 (S,G) 6. PE2 receives Type 5 (S,G) 7. PE2 verifies existing (*,G) state 8. PE2 advertises Type 7 Join (S,G) 9. PE2 does PMSI and P-Tunnel attachment 10. PE1 receives (S,G) from PE2 11. PE1 adds PMSI to downstream interfaces 12. Multicast flow end to end 13. Achievement unlocked! I'm least sure about steps 2 & 3. Comprehension challenged, Jason

3 3

Any large IPv4 space brokers?
by Paras Jha 02 Mar '16

02 Mar '16

Does anyone know of any IP space brokers other than Hilco Streambank? I'm looking to get a feel for the market a little bit. Regards Paras

6 5

AWS Direct Connect - Peering VPCs to Tier 1's and MPLS
by Jay R. Ashworth 02 Mar '16

02 Mar '16

Just got this dropped on my desk an hour ago, and I'm not finding as much material online as I might have hoped for... It looks like the easiest solution is to just hang a router/firewall at Equinix Ashburn and AWS-DC to that, and then peer it to carriers both IP and MPLS; is there a "native" way to do that from an AWS VPC instead? Any public or private replies cheerfully accepted; will summarize what I can to the list. Cheers, -- jra -- Jay R. Ashworth Baylink jra(a)baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274

8 9

Re: Thank you, Comcast. (aka patch your D-Link gear)
by Scott Weeks 01 Mar '16

01 Mar '16

--- Jason_Livingood(a)comcast.com wrote: As noted last week we're ... -------------------------------------------- Thank you for sharing this and all the other stuff over the years with the NANOG community. scott

1 0