Update #10: The ESPC PDA Support Team is continuing with troubleshooting the JTWC issue with our JTWC partners. The status has improved such that the workaround that uses the JTWC COOP system to send files to the PDA CBU environment is working consistently and the CBU environment is forwarding the files to the PDA OPS environment. The files are being disseminated from PDA OPS to subscribers as normal. JTWC is still working to resolve other issues and will provide updates when available. The PDA Support team is also working to acquire the JTWC ATCF-* and SHIPS_* products from the JTWC Collaboration site. These products are listed down in the body of this notification.

 

Update #9: The ESPC PDA Support Team is in a holding pattern with troubleshooting the JTWC issue with our JTWC partners. The status remains the same as was reported in Update #8. We do not know if work to resolve the network issues on the JWTC side are progressing or when the higher priority work will be completed.

The PDA Support team will pursue acquiring the JWTC ATCF-* and SHIPS_* products from another source. These products are listed down in the body of this notification.

 

Update #8: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with our JTWC partners.

The temporary fix to receive the JTWC files at PDA CBU and have them sent to PDA OPS was initially successful but we have not received any files in the last 24 hours. We have reached out to our JTWC partners via email as our partners are working a higher priority classified issue today and are only able to work with us via email at intervals of several hours. The JTWC team is continuing their network troubleshooting with the NMCI Network Team as they have time depending on other priorities.

 

Update #7: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with our JTWC partners.

The temporary fix to receive the JTWC files at PDA CBU and have them sent to PDA OPS has been successful.

The JTWC team is continuing their network troubleshooting with the NMCI Network Team. The PDA Support team is continuing to troubleshoot connectivity issues with JTWC to the PDA OPS environment.    

 

Update #6: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with our JTWC partners. We have hit a roadblock on the JTWC network side and they are working with the NMCI network support team to remediate the issue. The JTWC team has discovered that their COOP system is able to connect and send files to the ESPC CBU environment. Given this new development the team has decided for PDA to receive the JTWC files at the CBU site and then transfer them to the OPS environment where they will be ingested and processed. This temporary fix will get the data flowing through its normal path to PDA OPS and to NCCF. The JTWC team will need about another day to configure their COOP server to send the files to CBU and then the PDA Support team will configure the file transfer method between ESPC PDA CBU and ESPC PDA OPS.

 

Update #5: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with our JTWC partners. We have hit a roadblock on the JTWC network side and they will be opening a support ticket with their Network Support (NMCI) to run down that issue. After the network issue has been remediated we will reengage and continue troubleshooting the original SSH cipher issue.

 

Update #4: The ESPC PDA Support Team continues to troubleshoot the JTWC issue and has identified a possible SSH configuration compatibility issue between the sites. We have been able to reproduce the issue in our test environment and are working with JTWC to find a compatible configuration between the two sites. To this point communication between the two support teams has not been optimal. We hope to establish a conference bridge or Microsoft Teams meeting tomorrow for more effective problem resolution.

 

Update #3: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with no known Root Cause at this time. We have been successful in contacting JTWC and will be continuing troubleshooting in the next 2 hours. Our next steps will involve participation with both the JTWC and PDA support teams to perform manual sftp connections from JTWC to PDA with enhanced debugging turned on. We will then review the sftp log data for additional information.

 

Update #2: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with no known Root Cause at this time. We have been unsuccessful in receiving feedback from JTWC and as they are listed as 8x5 support we are discontinuing further troubleshooting until Monday, March 3, 2025. Our next steps will involve participation of Systems Administrators on the JTWC side to perform manual sftp connections with enhanced debugging turned on.

 

Update #1: The ESPC PDA Support Team continues to troubleshoot the JTWC issue with no known Root Cause at this time. Updates will be provided as new information becomes available.

 

Topic: PDA Product Outage: JTWC Storm Bulletins and Tropical Products 

 

Date/Time Issued: March 15, 2025 1403Z

 

Product or Data Impacted: Tropical Products.

 

Date/Time of Initial Impact: February 27, 2025 2000Z

 

Date/Time of Expected End: TBD

 

Length of the Outage/Event: TBD

 

Details/Specifics: 

Outage of JTWC products on PDA:

·  ATCF-JTWC_A-Deck

·  ATCF-JTWC_B-Deck

·  ATCF-JTWC_FST

·  SHIPS_JTWC_diag

 

List of tropical products impacted on PDA: 

·  ADT

·  MTCSWA

·  HISA

·  eTRaP

·  TCFP

This issue seems to be related to authentication or connectivity between JTWC and PDA. The PDA support Team is actively working the issue and will provide an update when available.

 

This notification was sent to ESPC.Notification@noaa.gov mailing list. If you wish to unsubscribe or subscribe to this list, please contact ESPC Help-Desk at ESPCOperations@noaa.gov with your request. Please note: it may take up to two business days to process your request. For any additional information you can reach ESPC at 301-817-3880 (24x7)