Network Communications Initiative NCI Coby Holloway

1. Network Communications Initiative (NCI)Coby Holloway Project Status NISN Customers' Forum June 2009

2. Agenda Project Description Project Schedule Project Status Design Implementation Approach Center Facilities Requirements Center Design Integration Guidance Linkage to Other OCIO Projects Points of Contact and Outreach Fourteenth NISN Customers� Forum 2

3. Project Description Network Communications Initiative (NCI) The NCI project provides a standardized Center border architecture across the Agency, as well as providing the necessary infrastructure to support deployment of consistent security zones (Intranet, Extranet, and Public) at each Center NCI consists of the design and deployment of Center border hardware only A follow-on activity, the Center Zoned Architecture Project (CZAP), will be responsible for the actual site transition to the infrastructure deployed during NCI Fourteenth NISN Customers� Forum 3

4. 4 Fourteenth NISN Customers� Forum

5. Project Status Initial site outreach conducted from 9/11/2008 � 12/11/2008 All sites either visited in person or via ViTS Technical face-to-face sessions held MSFC, 12/17/2008 � 12/18/2008 HQ, 1/13/2009 � 1/15/2009 Representation included Agency ITS, SOC, NISN Program Management, ITMB community, NAB community, NCI core project team, Agency OCIO The NCI project was granted approval from the ITPMB for Key Decision Point D (KDP-D) on 3/27/2009 Vendor meetings conducted 3/30/2009 � 4/3/2009 Lab procurement initiated 4/6/2009, all equipment received Design changes validation testing completed Center procurements initiated, delivery expected by July 14th SATS to be completed in August Center deployments begin September Fourteenth NISN Customers� Forum 5

6. Design Changes Since Outreach No Null-routing At NISN Edge NAT has been removed from the design Simplification of Security Zones Intranet: Server zone isolated on local routers, not on firewalls Other Security Zone changes since first outreach Move of Proxy Servers Outside of Firewalls Layer 2 Trunks On Firewalls None of the changes to the design have resulted in a significant change to the original hardware Fourteenth NISN Customers� Forum 6

7. Design Drawing 7 Fourteenth NISN Customers� Forum

8. Architecture Drawing 8 Fourteenth NISN Customers� Forum

9. Implementation Approach Site implementations will be coordinated via the NISN Service Request process Equipment will be received at MSFC and sent to the NISN Network Operation Systems Lab (NOSL) for staging, one Center at a time Equipment will be racked, powered, configured, and tested After staging in the NOSL, equipment will be sent to Center shipping and receiving, and then on to the NISN gateway Gateway personnel will rack, power, and cable the equipment Public and Private links will be brought up and tested on weekend activities Fourteenth NISN Customers� Forum 9

10. Facilities Requirements NCI Power Requirements NCI will install two racks of equipment in each center�s NISN Gateway Racks will consist of Center border router, a private firewall, NCI multilayer switch, a public firewall, a proxy server, and network management equipment Power requirements for each rack are 6 208v 20A single phase circuits 2 of the 6 will be dedicated to the Center border router devices 1 20A 208v circuit per chassis power supply The remaining 4 will be connected to power distribution devices to feed the other equipment in the rack Fourteenth NISN Customers� Forum 10

11. Rack and Power Diagram 11 Fourteenth NISN Customers� Forum

12. Center Design Integration Guidance The new NISN border architecture deployed under NCI will be deployed in parallel with the existing Center gateways Centers will interface with the NCI border via four physical interfaces from their campus LAN devices, two interfaces to each of the NCI border routers These links will carry all three zones (Intranet, Extranet, and Public) into the Center LANs Centers should determine what type of fiber is required (single mode vs. multi-mode), which devices they want to terminate to the NCI border, and how they will logically redistribute the three major security zones into their campus Fourteenth NISN Customers� Forum 12

13. OCIO Projects Related to NCI Center Zoned Architecture Project (CZAP) CZAP is the follow-on project to NCI that transitions sites from their current border architectures to the new border architecture deployed under NCI WAN Expansion (WAN-X) NCI Private-side connectivity is dependent on the decommission of existing interfaces from this project Agency URL/Content Filtering A separate project will fund an Agency URL and content filtering solution. This solution will likely be integrated with the proxy hardware deployed under NCI, but will require the procurement of software licenses and capacity analysis. Agency Wireless This project will not directly impact NCI, although it will most likely define the CZAP entrance criteria for wireless devices located at Centers TIC The TIC initiative will indirectly impact NCI, as it may result in a change to where external circuits physically connect to the backbone architecture We do not anticipate any changes to the NCI hardware deployment related to TIC Fourteenth NISN Customers� Forum 13

14. POC List Betsy Edwards, NASA Project Executive Carol S. Bryant, NASA Project Manager Don Clark, UNITeS Project Manager Arkan (DJ) Al-Dijaili, Lead Engineer Fourteenth NISN Customers� Forum 14