190 likes | 199 Views
AARNet Network Update IPv6 Workshop APAN 23, Manilla 2007. AARNet. The AARNet Network. AARNet owns and operates a resilient and redundant multi-Gbps network across Australia. In the Eastern Australia we have deployed DWDM equipment which currently has up to 320 Gbps capacity.
E N D
AARNet Network Update IPv6 Workshop APAN 23, Manilla 2007 AARNet
The AARNet Network • AARNet owns and operates a resilient and redundant multi-Gbps network across Australia. In the Eastern Australia we have deployed DWDM equipment which currently has up to 320 Gbps capacity. • Dual STM-64c (10 Gbps) links connect major capital cities with routing being done by Juniper M320 routers
The AARNet Network(2) • At each capital city there are two geographically separated Points of Presence (PoPs) interconnected with 10 Gbps ethernet circuits. Cisco 6509-NEB-A switches are used to terminate the intra-PoP links • Remoter cities - Darwin, Alice Springs and Hobart - are currently connected by dual STM-1 (155 Mbps) circuits - terminated on Juniper M20 routers
University connections • Universities are encouraged to have diverse connections to the Juniper M320 routers at each PoP. • Institutions typically connect at 1 Gbps and we have deployed Cisco 7304 routers at each site (edge routers), and also edge servers. This allows close monitoring of each tail circuit. • So far about 75 edge routers have been deployed.
Equipment • Backbone routers are Juniper M320s • Smaller PoPs have Juniper M20 routers • Backbone switches for interconnecting PoPs are Cisco 6509-NEB-A • Cisco 7304 NPE at institutions - some 85 deployed • Cisco ONS 15454 MSPP for DWDM on the optical network
The AARNet DWDM Backbone • Provisioned for 16 wavelengths today • Expandable to 32 wavelengths • 40G (STM256) compatible
The international footprint • AARNet has a very large international footprint from the PoP in Frankfurt, Germany to Palo Alto in the US - it covers a timezone difference of 17 hours from +1 to -8 • Peering at : • Hawai’I, Seattle (Pacific Wave), PAIX, Telehouse (LA) • Singapore, Frankfurt (DE-CIX), Amsterdam (AMS-IX) • , Currently 622 Mbps to Singapore and then on to Frankfurt • The 622 Mbps link to Singapore connects to the TEIN2 nework
10G Trans Pacific • Partnership with Southern Cross Cable Networks • AUP - Research and Education only • Dual STM-64c (OC192) • Northern path to Seattle • Layer 3 routed • Southern path to Los Angeles • Layer 1/2 • Catalyse Global Astronomy Initiative • Mauna Kea, Big Island
TEIN2 Connectivity • There are four STM-1 circuits linking Perth to Singapore. • Two of these go via APCN, and the other two via SMW3 to provide diversity and fault tolerance • AARNet Singapore PoP establish at the Kim Chuan data centre from where we peer with TEIN2, Singaren and ASNet
Commodity and R&E • AARNet offers both commodity (commercial) internet and research networking • Two 10 Gbps circuits for R&E connectivity to the US. The northern link is IP and routed - the southern link will be presented as light paths (ethernet L2 circuits) • 4 x STM-4 (622 Mbps) circuits to the US - two terminating at Palo Alto, the other terminating in Los Angeles • These will be upgraded to 2 x STM16 circuits (2.5Gbps) • 2 x STM STM-1 (155 Mbps) circuits to Seattle via Hawai’i and Fiji
AARNet support for IPv6 • AARNet3 core and edge is dual stack • Still need to make services accessible via IPv6 • Web server isn’t • International transit and peering available for IPv6 • All customers can connect natively • CPE router dual stack but customer’s router/firewall may not be • IPv6 Multicast is enabled • SSM supported • Currently use a static RP for ASM
AARNet Migration Broker • http://broker.aarnet.net.au • Hexago appliance • Same as Freenet6 • Tunnel Setup Protocol • NAT Traversal support • Open to anyone who can reach it via a domestic Australian path
AARNet3 is ready… • A few institutions are using IPv6 natively in a limited fashion • Many are worried about deploying a dual stack at the edge • Stability/complexity concerns • Existing infrastructure may not support IPv6 • firewalls • Some institutions and researchers use static tunnels or broker • Uptake of IPv6 has been slow • Lack of IPv6 specific spplications • Not a huge amount of IPv6 services available • No shortage of IPv4 address space within institutions
Where to now? Ensure as many services as possible are IPv6 enabled • Connect customers if they ask • Look for more peering opportunities • Encourage IPv6 activities • AARNet sponsored and provided native connectivity to IPv6 Summit in Canberra, 4-6 December 2006