1 JAG/CCM COPC Status Updates and Recommendations NOV 4-5, 2015 LCDR Tristan Borne JAG-CCM Chairperson

2 JAG/CCM Purpose Coordinate communication issues between the Operational Processing Centers (OPC), monitor the effectiveness of those communications, and to do capacity planning and forward projection of capability needs.

3 Outline CCM Team Membership Network Outages Process Towards the End Goal –End goal diagram –Process Flow Chart –Decision Points Primary Connection Status 2 nd Connection Status Bandwidth Sizing DREN and DSRC

4 CCM Team MemberOrganization Jason Rance Billy Cowgill *Marvin Cunningham TSgt Michael Dent Air Force/557 WW Cameron Shelton Doug Fenderson NOAA/NWS/NCEP/NCO Craig Wade OSGS Russell Dyson OSPO NOAA/NESDIS Tracy LePireNavy/NAVO *LCDR Tristan Borne (CCM Chair) Trent Hancock Derek Eddington Navy/FNMOC Kevin GreenleeNavy/NAVIDFOR/N462 Ken BarnettOFCM Technical Advisor/SME/AlternateOrganization *MAJ Rubin Neypes *Bruce Kenison (alternate) DISA Field Office USSTRATCOM Quincy Allen Jagdish Rai DISA * New to the role or group

Network Outages DateOPC (circuit)Outage 12/10/15NAVO – 73WU9hrs (fiber cut) 23/10/15NAVO – 73WU1hr 34/15/15NAVO – 73WU5hrs 47/1/15FNMOC – 7CU212hrs (fiber cut) 59/16/15FNMOC – 7CU218hrs (fiber cut) NCEP circuit tracking. –Does not include DoD to DoD outages, nor data issues. 2 nd connection could help in some cases. 2 nd connection and multiple NFGs with dynamic routing should prevent many outages but not for the last mile outages.

What JAG CCM is working towards 6 DoD NOAA

Process Flow Chart 7 Navy Bandwidth upgrade NMIC SN9K Install Suitland SFP OC48 NOAA Boulder MSPP Enable 3 DOD circuits Test end to end connectivity Perform a failover test Boulder Submit the NFG connection request Test the latency through NFG Switch secondary path to NFG Final Goal: dual NFG connections Decision Point 1 Decision Point 2 COPC CCM/DISA

COPC Network Decision Points CCM / DISA Decision Point 1: COPC Action : Make a recommendation about the utilization of the 2nd COPC network path (Boulder). [Concurrent usage or regular scheduled failover tests]. –CCM recommends keeping this action item open. –Once the dual paths are in place, CCM can provide COPC recommendations for usage (concurrent or failover-only). Pursue the first NFG connection through Suitland to Columbus or through Boulder to San Antonio. COPC Decision Point 2: COPC Action Item : Implement an end-to-end latency test exchange using representative proxy data from NOAA (NESDIS, TOC, and NCEP) through NFG to each DOD OPC]. –CCM recommends keeping this action item open. Utilize NFG as primary COPC data exchange paths. Final Goal: Establish dual paths from the two NOAA access points (Suitland & Boulder). –Per 557 th WW, direction was to hold off migrating to NFG until further notice and focus on 2 nd P2P connection from Boulder AFB. –Determine the supportability of Navy going through NFG and 557 th WW staying on P2P link. 8

Primary COPC Network Connection Upgrades to the bandwidth for both Navy sites are pending a switch upgrade at NMIC. Currently 557 th is 1gb, FNMOC is 155mb, and NAVO is 28mb. Both FNMOC and NAVO have TSOs for upgrading to 400mb. F2F meeting with the NMIC: –Understand why the SN9K installation has been delayed at NMIC. –COPC/Navy working with NMIC in coordinating this install with DISA. 9

2 nd COPC Network Connection Status Boulder: The commercial segment for circuit (6QU2) has been delivered by CenturyLink. –Waiting on a part (SFP for the OC48). NCEP NCO has reached out to the CISCO rep and CISCO understands the criticality of the order and is working to resolve it. –All 3 Operation Centers (557 1GB, 400MB, & 400MB) TSOs have been issued but on hold. –The NOAA build-out (Phase 2) of the Boulder IDP was completed and expect FOC in However DoD exchange will be available when the circuit is fully functioning. DoD circuit cost sharing for the OC48 Boulder/Buckley: –Planning to use a DD Form 1144 Support Agreement as the official document for sharing costs to replace the MOA method. 10

Bandwidth Requirements COPC Action Item To update the estimated bandwidth requirements (including ports and protocols). Both CNMOC and 557WW have validated their requirements for bandwidth, ports, and protocols. Sizing of a 4GB path for the DoD/NOAA exchange through NFG should be appropriate. Recommend closing this action item. 11

12 Questions

13 Backup Slides

14 - R Z OCT 11 FM: USCYBERCOM FT. GEORGE G. MEADE MD SUBJECT: (U//FOUO) USCYBERCOM TASKORD J , ESTABLISHMENT OF THE NIPRNET FEDERAL DEMILITARIZED ZONE (DMZ). // OPER/GLADIATOR SHIELD// MSGID/ORDER/USCYBERCOM/ J / PRIORITIZE ACTIONS IN SUPPORT OF MOVING ALL CONNECTIONS BETWEEN THE NIPRNET AND NETWORKS BELONGING TO EXECUTIVE BRANCH DEPARTMENTS, AGENCIES, CLEARED DEFENSE CONTRACTORS AND EDUCATIONAL INSTITUTIONS INTO THE NIPRNET FEDERAL DMZ. /TASKORD/(U//FOUO)// REF/A/DOC/(U) OPORD OPERATION GLADIATOR SHIELD (OGS)/COMMANDER, U.S. CYBER COMMAND (CDRUSCYBERCOM)/231800MAY11 (S//REL TO USA, FVEY)// REF/B/DOC/ (U) WARNORD , ESTABLISHMENT OF THE NIPRNET FEDERAL DEMILITARIZED ZONE/USCYBERCOM/ Z SEP 11 (S//REL TO USA, FVEY)// - R Z OCT 11 ZYB FM COMFLTCYBERCOM FT GEORGE G MEADE MD MSGID/GENADMIN/FLTCYBERCOM/-/OCT// SUBJ/ESTABLISHMENT OF NIPRNET FEDERAL DEMILITARIZED ZONE (DMZ)// REF/A/MSGID:TASKORD/USCC/071652ZOCT2011/-/NOTAL// AMPN/REF A IS USCYBERCOM (USCC) TASKORD J , ESTABLISHMENT OF THE NIPRNET FEDERAL DMZ.// USCYBERCOM TASKORD J , ESTABLISHMENT OF THE NIPRNET FEDERAL DEMILITARIZED ZONE (DMZ).