1

JAG/CCMCOPC Status Updates and

Recommendations

NOV 4-5, 2015

LCDR Tristan BorneJAG-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• 2nd Connection Status• Bandwidth Sizing• DREN and DSRC

4

CCM TeamMember Organization

Jason RanceBilly Cowgill*Marvin CunninghamTSgt Michael Dent

Air Force/557 WW

Cameron Shelton Doug Fenderson

NOAA/NWS/NCEP/NCO

Craig Wade OSGSRussell Dyson OSPO

NOAA/NESDIS

Tracy LePire Navy/NAVO

*LCDR Tristan Borne (CCM Chair)Trent HancockDerek Eddington

Navy/FNMOC

Kevin Greenlee Navy/NAVIDFOR/N462

Ken Barnett OFCM

Technical Advisor/SME/Alternate Organization

*MAJ Rubin Neypes*Bruce Kenison (alternate)

DISA Field Office USSTRATCOM

Quincy AllenJagdish Rai

DISA

* New to the role or group

Network Outages

Date OPC (circuit) Outage1 2/10/15 NAVO – 73WU 9hrs (fiber cut)

2 3/10/15 NAVO – 73WU 1hr

3 4/15/15 NAVO – 73WU 5hrs

4 7/1/15 FNMOC – 7CU2 12hrs (fiber cut)

5 9/16/15 FNMOC – 7CU2 18hrs (fiber cut)

6

7

8

9

10

115

• NCEP (@NSOF) circuit tracking.– Does not include DoD to DoD outages, nor data issues.

• 2nd connection could help in some cases.• 2nd 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

DoDNOAA

Process Flow Chart

7

Navy Bandwidth upgrade

NMIC SN9K Install

SuitlandSFP 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

COPCCCM/DISA

COPC Network Decision PointsCCM / DISA Decision Point 1:• COPC Action 2015-1.4: 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 2013-1.5: 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 557th WW, direction was to hold off migrating to NFG until further notice and focus on 2nd 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 ConnectionUpgrades to the bandwidth for both Navy sites are pending a switch upgrade at NMIC.• Currently 557th 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

2nd 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 (557th @ 1GB, FNMOC @ 400MB, & NAVO @ 400MB) TSOs have been issued but on hold.

– The NOAA build-out (Phase 2) of the Boulder IDP was completed and expect FOC in 2016. 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 2014-1.2 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 071652Z OCT 11FM: USCYBERCOM FT. GEORGE G. MEADE MDSUBJECT: (U//FOUO) USCYBERCOM TASKORD J3-11-0508, ESTABLISHMENT OF THENIPRNET FEDERAL DEMILITARIZED ZONE (DMZ). //OPER/GLADIATOR SHIELD//MSGID/ORDER/USCYBERCOM/ J3-11-0508/ PRIORITIZE ACTIONS IN SUPPORT OF MOVINGALL CONNECTIONS BETWEEN THE NIPRNET AND NETWORKS BELONGING TO EXECUTIVEBRANCH DEPARTMENTS, AGENCIES, CLEARED DEFENSE CONTRACTORS AND EDUCATIONALINSTITUTIONS INTO THE NIPRNET FEDERAL DMZ. /TASKORD/(U//FOUO)//REF/A/DOC/(U) OPORD 11-002 OPERATION GLADIATOR SHIELD (OGS)/COMMANDER, U.S.CYBER COMMAND (CDRUSCYBERCOM)/231800MAY11 (S//REL TO USA, FVEY)//REF/B/DOC/ (U) WARNORD 11-0377, ESTABLISHMENT OF THE NIPRNET FEDERALDEMILITARIZED ZONE/USCYBERCOM/ 021834Z SEP 11 (S//REL TO USA, FVEY)//

- R 211154Z OCT 11 ZYBFM COMFLTCYBERCOM FT GEORGE G MEADE MDMSGID/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 J3-11-0508, ESTABLISHMENT OFTHE NIPRNET FEDERAL DMZ.//

USCYBERCOM TASKORD J3-11-0508, ESTABLISHMENT OF THE

NIPRNET FEDERAL DEMILITARIZED ZONE (DMZ).