1 JAG/CCM Status Updates and Recommendations Spring COPC Meeting May 27-28, 2015 Craig Wade JAG-CCM Chairperson.

1

JAG/CCMStatus Updates and Recommendations

Spring COPC Meeting

May 27-28, 2015

Craig WadeJAG-CCM Chairperson

2

Outline• CCM Team Membership• Status of the 2nd DOD/NOAA Connection• Primary COPC Connection• NFG Connection

– DISA Update• HRPT Data Solution

3

CCM TeamMember Organization

*Jason Rance*Billy CowgillRoger SiroisTSgt Michael Dent

Air Force/557 WW

Cameron Shelton Doug Fenderson

NOAA/NWS/NCEP/NCO

Craig Wade (CCM Chair) *OSGSRussell Dyson OSPO

NOAA/NESDIS

Tracy LePire Navy/NAVO

Jackie Lord (retired) [*NCO will cover this now] NOAA/NWS/TOC (*NCO Silver Spring)

*LCDR Tristan Borne (Next CCM Chair)*Trent HancockDerek Eddington

Navy/FNMOC

Kevin Greenlee Navy/CNMOC/N6

Ken Barnett OFCM

Technical Advisor/SME/Alternate Organization

Bruce Kenison DISA Field Office USSTRATCOM

Michael Quilty DISA

* Upcoming Vacancy ** Vacant role/representative *** New to the role or group

2nd Connection NOAA/DOD

NOAA

DoD

4

CSAB Action Item 2014-2.2: CCM and CSAB will create a 2nd DOD/NOAA connection at Boulder.

Note: AFWA’s name/structure change to the 557 Weather Wing is not represented within the graphics.

2nd COPC Network Connection• Both sides have been delayed.

– The DOD OC48 between Buckley and NOAA Boulder IDP is now scheduled for installation on May 29th.

– The NOAA build-out (Phase 2) of the Boulder IDP is now pushed to the beginning of July.

• However, NCEP can test the fiber connection when it is installed, but not pass real data until the IDP is completed.

• DOD circuit cost sharing for the OC48 Boulder/Buckley:– 557WW has agreed to

cover any FY15 circuit costs.

– AF and Navy need a MOAin place by the end of Sept to split the reoccurring costs for FY2016.

– Price estimates: MRC: $17,692 (MRC: Monthly Recurring Cost)• NAVY would MIPR $106,153 a year.

5

2nd COPC Network Connection• All 3 DOD Centers have submitted request for circuits to

connect their Centers with the Buckley/Boulder circuit.– 557WW @ 1 GB.– NAVO @ 400 MB.– FNMOC @ 400 MB.

• All pending the OC48 install.

• DOD provisioning on the OC48 – 557-1Gig STS 1-21 (21 STS’s)– NAVO-400mb STS 22-30 (9 STS’s)– FNMOC-400mb STS 31-39 (9 STS’s)– With 40-48 open.

• Routing scheme being developed:– FNMOC is looking into using a few spare IPv4 subnets for

implementing our Point-to-Point circuits during the transition.– The group is considering the use of a simple IP SLA scheme.

6

Primary COPC Network Connection• Upgrades to the point-to-point connection bandwidth for both

Navy sites.– Currently FNMOC is 155mb and NAVO is 28mb. – NAVO has a TSO for upgrading to 400mb.– FNMOC will be submitting a similar request to 400mb.

• CSAB Action Item 2014-2.1: CCM will work to develop a (no extra cost) COPC network monitoring solution.– NAVO is monitoring the

NOAA circuit and the 557WW.

– Need to workout ICMPexchange with theFNMOC firewall.

7

NFG Connection• 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.– Overall concept: Establish the 2nd connection, establish a connection to

a NFG, and test latency with a large data set over a long period of time (to not impact the operational path).

• COPC Action Item 2014-1.2 To update the estimated bandwidth requirements (including ports and protocols).– CNMOC presented a draft version at the CCM meeting and is very

close to submitting the final version.– 557WW is re-validating the previous submission.

• Update on the status update on the status of the 10Gig connection from NMIC Suitland to Columbus NFG (TR: AE04NOV146720A).– TSO B48759/7RA9-01 issued for requirement as 4Gig with a 10Gig

interface. Open waiting on activation.– DISA has determined there will be NO COST to DOD for the

Suitland to Columbus connection.

8

NFG ConnectionDISA gave an update at the April CCM meeting:• Completion dates identify site’s availability to accept Partner connections.

– Site 1: Warner Robins – Jun 2013– Site 2: Columbus (Suitland) – Sept 2013– Site 3: San Antonio (Boulder) – Nov 2014 – Site 4: PAC, Yokota AFB – Q1 FY2016 (Nov, 2015)– Site 5: North Island – Q1 FY2016 (Nov, 2015)– Site 6: PAC, Hickam AFB – 2016 (estimated)– Site 7: Europe, Germany – 2016 (estimated)

• NOTE: Site Surveys still required for Europe and North Island. These surveys are tentatively scheduled for late FY2015. Site deployment schedules may be impacted by survey results.

• NFG Customers:– NOAA PKI, FAA (pending), DREN (pending), Missile Defense Agency (pending)– Enterprise Programs: Mobility and Cloud– Inclusion of these enterprise programs through NFG has caused a need for a tech refresh.

• CCM concerns for note to COPC:– With these new enterprise programs, what do we do about inconsistent capacity

impacting time sensitive METOC data?• How/who do we get to authorize a quality of service scheme?

– For either location AF must deal with the AF-gateway issues before they can receive NOAA data via the NFG?

• Should and can we move forward with both Navy sites?9

10

Final Solution through NFG

10

DoD

NOAA

HRPT Data• High Resolution Picture Transmission (HRPT) data was being

downloaded at the Monterey WFO and sent to NESDIS NSOF via the FNMOC COPC circuit.

• Many, many years ago this was a well coordinated project between the Navy, NESDIS and NWS and has worked well for years.– CCM was made aware of many important dependencies on this data

feed. (i.e. Western Region uses NOAA-AVHRR HRPT data from Monterey every day for fire detection over the western half of the US.)

• However, this connection did not meet current IT security standards and FNMOC needed it removed quickly.

• A huge thank you goes out to NWS and NCEP/NCO for implementing a new path over the OPSNet (in just days from the first request!)– FNMOC was able to remove the connection before their ATO review.

• A great example of the cooperative power of this COPC and CCM structure.

11

12

Questions