July 2014 NOAA External Network Connectivity

Transcription

1 July 2014 NOAA External Network Connectivity

2 Goals Meet TIC requirements, including traffic symmetry. Maintain resiliency and avoid single points of failure. Maintain the ability to scale, grow, and change. Ensure efficient utilization of network circuits and resources. Provide cost-effective solutions for both smaller and larger NOAA offices.

3 Traffic Symmetry Solutions A given office or location connects to all external resources and the through a single TIC stack. Simplest solution. Poor availability due to outages and routine maintenance. Difficulty growing and scaling. A given office or location maintains connections to multiple TIC sites, but only one may be in use at any given time. Warm spare concept; backup pipe is unused until primary breaks. Inefficient use of resources; expensive. Difficult to ensure backup will always work properly when needed. An office or location connects via an entity that controls traffic routing on both sides of the TIC stacks, ensuring symmetry. High availability; automatically resilient under failures. Easy to scale and add additional connections. Efficient use of resources; allows load-balancing.

4 Provider A Regional Provider 2 Provider B Other External Without X-Wave, 2 independently chooses it s own best path back to the NOAA customer, breaking symmetry. NCPS MONITORING Seattle Boulder Ft. Worth PACKET FILTERING CONTENT FILTERING WEB PROXY S. Spring

5 Provider A Regional Provider 2 Provider B Other External With X-Wave, 2 chooses it s own best path back to X-Wave, and X-Wave sends it correct symmetric return TIC site. Preferred path is to viathe Seattle X-Wave NCPS MONITORING Seattle Boulder Ft. Worth PACKET FILTERING CONTENT FILTERING WEB PROXY Preferred path is via Seattle VRF A VRF B S. Spring

6 NOAA TIC Architecture Initial TICAPs established All external (e.g., non-fed) traffic must route through one of these sites Seattle, WA Denver, CO Dallas, TX Honolulu, HI McLean, VA Approved NOAA TICAP NOAA Multi-agency TICAP

7 NOAA TIC Architecture (2) NOAA s current networks (N-Wave, OPSnet, etc.) will continue to provide enterprise connectivity to NOAA sites NOAA will continue to leverage commercial and R&E partners for continued access via TIC sites NOAA will use N-Wave where applicable to support TICAP transport NOAA is pursuing a new, external peering network: X-Wave

8 NOAA TIC Architecture (3) NOAA will use N-Wave where applicable to support TICAP transport N-Wave National Network 2014

9 NOAA Interim TIC Architecture ISPs, PNWG ISPs, FRGP ISPs, LEARN ISPs, UH, HIX ISPs, MAX Se NCPS MONITORING Boulder Sand Pt SSMC Ft Worth PACKET FILTERING CONTENT FILTERING WEB PROXY Denver Seattle Dallas Honolulu McLean

10 X-Wave Provide a peering infrastructure for network redundancy and failover between TICAP sites Enforce symmetrical IP traffic routing through the TIC Consolidate and share ISP connections and R&E network connectivity External networks can land in X-Wave, for routing to NOAA via TIC X-Wave can provide locations for Science DMZs and low-risk public data delivery

11 Typical Science DMZ PerfSonar X-Wave border routers SPAN/Mirror Other NOAA TICAPs TIC Firewalls/IPS GigaMon PerfSonar PerfSonar Virtual Machines Data Transfer Nodes Globus/GridFTP HTTP LDM etc TIC Monitoring Einstein IDS etc N-Wave aggregation routers Remote NOAA Field Offices Science DMZ switch/router NOAA Campus Legend Switch/Router Server/Appliance 10 GE 40 GE Storage

12 Regional Provider Provider A 2 Provider B Other External X-Wave Se NCPS MONITORING Boulder Sand Pt IRC Ft Worth SSMC PACKET FILTERING CONTENT FILTERING WEB PROXY Denver Seattle Dallas Honolulu McLean

13 Thank You Questions? Alex Hsia X-Wave Network Architect