150 likes | 288 Views
Internet2 IPv6 Update. Matt Zekauskas, matt@internet2.edu APAN IPv6 Task Force 2008-January-23. Outline. Internet2 network infrastructure IPv6 status IPv6 activities. Recall: We Have Renamed. Abilene -> Internet2 Network NOC URL: http://noc.net.internet2.edu/
E N D
Internet2 IPv6 Update Matt Zekauskas, matt@internet2.edu APAN IPv6 Task Force2008-January-23
Outline • Internet2 network infrastructure IPv6 status • IPv6 activities
Recall: We Have Renamed • Abilene -> Internet2 Network • NOC URL:http://noc.net.internet2.edu/ • NOC email:noc@net.internet2.edu • Internet2 Network URLhttp://www.internet2.edu/network/ • Internet2 Network contact address (new peerings, …): network@internet2.edu
NOTE: Raleigh, Tulsa, Portland, Seattle switching equip. deferred
Internet2 network infrastructure • IPv6 continues to perform well on the Internet2 Network • Transition from Abilene layer3 network to new Internet2 network infrastructure complete [done by 30-Sep] • Using same Juniper T640 routers; still running dual-stack IPv4 and IPv6 • The backbone now supports 32 bit ASNs
Internet2 network infrastructure • R&E peerings remain unchanged • IPv6 peerings with commercial nets remain at PAIX, now served by Los Angeles router • With new commercial peering service, new opportunities to peer in Chicago, New York, Seattle and Los Angeles • Hence near-term change: commercial IPv6 to its own VRF
Internet2 Network VRFs • Research and Education • Our connectors • Our peers (GEANT2, APAN, JGN2, …) • IPv4 and IPv6 • CPS (peering service) IPv4 • CPS (peering service) IPv6 • Connectors can peer with each individually; to keep current state, encourage CPSv6, even if no CPSv4
Monitoring • Monitoring and network test points still being updated for the new network • We have at every router node • Latency (owamp) • Throughput (bwctl) [1G, 10G upon request] • On-demand testing (NDT) • All supporting IPv6
Monitoring • Consider testing to Internet2, at least ad-hoc, and possibly low-rate periodic • Owamp, and bwctl TCP tests < 30s to 1G endpoints, are no longer restricted • Please tell us if you set up periodic tests • Recent testing of peering points with DREN has exposed odd routing, configuration errors
Monitoring • We have firewall filters installed in the Juniper routers to capture IPv6 utilization (and other specific port counts) • http://vixen.grnoc.iu.edu/jfirewall-viz/index-bits.html (bits/sec) • http://vixen.grnoc.iu.edu/jfirewall-viz/ (packets/sec) • Question: what are you doing for flows?
Policy: Interconnection with other networks • Will continue to peer with IPv6 commercial networks • With new Internet2 network, will also now peer with IPv4 commercial networks (but these are a separate VRF, no mixing with R&E routes) • No transit between non-US networks and commercial IPv6 network peers • Had been providing transit between v6 networks (including commercial) • Stopped providing transit to commercial v6 peers – not their usual policy
IPv6 Activities • Internet2 IPv6 Working Group • Refocused from campus deployment effort to….. • Working with middleware and applications working groups as resource • Renewed interest in moving IPv6 to mainstream • Internet2 IPv6 Hands-on Workshops • Lesser in frequency, but still being held by request
Pointers • IPv6 working grouphttp://ipv6.internet2.edu/ • Internet2 NOC IPv6 Informationhttp://noc.net.internet2.edu/i2network/maps--documentation.html • Presentation and exercises from IPv6 Multicast Workshop http://multicast.internet2.edu/workshops/albuquerque-IPv6/