noaa’s nws telecommunication gateway rth washington
DESCRIPTION
NOAA’s NWS Telecommunication Gateway RTH Washington. Fred Branski Office of the Chief Information Officer NOAA’s National Weather Service 20 th NamEurDEx Meeting May 22-24, 2007. NWSTG/RTH Functional Overview. The NWSTG/RTH is the central communication facility of the NWS; - PowerPoint PPT PresentationTRANSCRIPT
NOAA’sNWS Telecommunication Gateway
RTH Washington
NOAA’sNWS Telecommunication Gateway
RTH Washington
Fred Branski
Office of the Chief Information Officer
NOAA’s National Weather Service
20th NamEurDEx Meeting
May 22-24, 2007
Fred Branski
Office of the Chief Information Officer
NOAA’s National Weather Service
20th NamEurDEx Meeting
May 22-24, 2007
“Taking the pulse of the planet”“Taking the pulse of the planet”
NWSTG/RTH Functional Overview
NWSTG/RTH Functional Overview
The NWSTG/RTH is
the central communication facility of the NWS;
the primary acquisition and distribution center for NWS data and products;
the primary acquisition and distribution center for international data and products to meet WMO, ICAO and bi-laterally agreed US requirements;
A major data exchange hub for NOAA and other agency data and products.
Will become Washington Global Information Systems Center (GISC) within the WMO Information System (WIS).
The NWSTG/RTH is
the central communication facility of the NWS;
the primary acquisition and distribution center for NWS data and products;
the primary acquisition and distribution center for international data and products to meet WMO, ICAO and bi-laterally agreed US requirements;
A major data exchange hub for NOAA and other agency data and products.
Will become Washington Global Information Systems Center (GISC) within the WMO Information System (WIS).
“Taking the pulse of the planet”“Taking the pulse of the planet”
Replacement & Backup NWSTG (RTG/BTG)
Replacement & Backup NWSTG (RTG/BTG)
Full functional replacement of existing capabilities
Expanded capacity and capability
Transition to new technology
– Message queuing (MQ) for internal transport
– Network centric systems interconnectivity
– Relational database central processing engine
– NAS/SAN storage solutions
Highly scaleable architecture
Planned Hardware refresh
Full functional replacement of existing capabilities
Expanded capacity and capability
Transition to new technology
– Message queuing (MQ) for internal transport
– Network centric systems interconnectivity
– Relational database central processing engine
– NAS/SAN storage solutions
Highly scaleable architecture
Planned Hardware refresh
“Taking the pulse of the planet”“Taking the pulse of the planet”
Government Networking Requirements - NOAANetGovernment Networking Requirements - NOAANet
• IP-based networking solution
− Any-to-any connectivity
− High degree of bandwidth scalability
− Optimum redundancy and survivability
− IP convergence (i.e., voice, video and data over IP)
− High-end performance
• Network security remains paramount, particularly in light of today’s socio-political threats
• Segmentation from the public Internet
• Minimizes risk of security or privacy breaches
“Taking the pulse of the planet”“Taking the pulse of the planet”
RTG/BTG/NOAANet StatusRTG/BTG/NOAANet Status
RTG & BTG connections to NOAANet in place
Internal NWS connections underway
External Gateway migrations planned
– Began December 01, 2006
– Initially two Access Points for external connectivity
– One within the RTG facility but external to the infrastructure (temporary to facilitate transitions)
– One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, others?
– Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)
RTG & BTG connections to NOAANet in place
Internal NWS connections underway
External Gateway migrations planned
– Began December 01, 2006
– Initially two Access Points for external connectivity
– One within the RTG facility but external to the infrastructure (temporary to facilitate transitions)
– One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, others?
– Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)
“Taking the pulse of the planet”“Taking the pulse of the planet”
NOAANet TransitionNOAANet Transition
NOAANet: RTG OC-12 / BTG OC-3 (OC-12 in progress)
Customer transitions to NOAANET: Dec 01, 2006 to May 31, 2007
Internal underway, NWS regions done, NCF, NESDIS soon
External – began December 01, 2006
– Initially two Access Points for external connectivity
– One within the RTG facility but external to the infrastructure (temporary to facilitate transitions)
– One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, Others?
– Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)
NOAANet: RTG OC-12 / BTG OC-3 (OC-12 in progress)
Customer transitions to NOAANET: Dec 01, 2006 to May 31, 2007
Internal underway, NWS regions done, NCF, NESDIS soon
External – began December 01, 2006
– Initially two Access Points for external connectivity
– One within the RTG facility but external to the infrastructure (temporary to facilitate transitions)
– One in New York City– GTS, AFTN / FAA / Hawaii / Micronesia, Others?
– Possibly Atlanta, Chicago, Tacoma, ??? (based on need &cost)
“Taking the pulse of the planet”“Taking the pulse of the planet”
RTG/BTG/NOAANet StatusRTG/BTG/NOAANet Status
RTG IOC June 26, 2006 / RTG FOC – July 31, 2006
Performance Metric Threshold– System Availability (averaged monthly) 99.90% – Warning Message Latency (averaged monthly) 10 seconds– Routine Message Latency (averaged monthly) 60
seconds– Daily Traffic Volume (averaged monthly) 1.2TB
NWSTG Performance Results (measured Feb 06, 2006) Performance Category Threshold Actual
– System Availability 99.90% 100%– Warning Message Latency 10 seconds < 1 second– Routine Message Latency 60 seconds < 1 second– Daily Traffic Volume 1.2TB 1.1TB
RTG IOC June 26, 2006 / RTG FOC – July 31, 2006
Performance Metric Threshold– System Availability (averaged monthly) 99.90% – Warning Message Latency (averaged monthly) 10 seconds– Routine Message Latency (averaged monthly) 60
seconds– Daily Traffic Volume (averaged monthly) 1.2TB
NWSTG Performance Results (measured Feb 06, 2006) Performance Category Threshold Actual
– System Availability 99.90% 100%– Warning Message Latency 10 seconds < 1 second– Routine Message Latency 60 seconds < 1 second– Daily Traffic Volume 1.2TB 1.1TB
“Taking the pulse of the planet”“Taking the pulse of the planet”
RTH Washington Thruput TimesRTH Washington Thruput Times
Frames (frames/sec)
Bytes (bytes/sec)
Bandwidth Utilization Total
Bandwidth Utilization
RTH Exeter – RTH Washington Link Thursday, May 17 2007
Psbl traffic shaping issue
To KWBC
To EGRRCapped?
Bursting
No issues with frames
RTH Exeter – RTH Washington Text Link Thursday, May 17 2007
Bytes from EGRR
500 Kb
Min, Avg & Max input delay
1 Minute
1.5 Mb
20 Seconds
RTH Exeter – RTH Washington Text Link Thursday, May 17 2007 Products from
EGRR
500
# Products by size
500
1000
1000
RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007
Bytes from EGRR
4 Mb
Min, Avg & Max input delay
50 Seconds
6 Mb
100 Seconds
RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007 Products from
EGRR
500
# Products by size
500
1500
1500
RTH Exeter – RTH Washington Pictorial Link Thursday, May 17 2007
Bytes from EGRR
50 Kb
10 Seconds
Min, Avg & Max input delay
20 Seconds
Products from EGRR
RTH Exeter – RTH Washington Pictorial Link Thursday, May 17 2007
10
# Products by size
10
RTH Exeter – RTH Washington Text Link Thursday, May 17 2007
Avg Thruput to EGRRTransmission Delay
Internal Delay
Total Delay
100 Minutes
2.78 Hours
RTH Exeter – RTH Washington Text Link Thursday, May 17 2007
Max Thruput to EGRRTransmission Delay
Internal Delay
Total Delay
100 Minutes
200 Minutes
4.44 Hours
RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007
Avg Thruput to EGRRTransmission Delay
Internal Delay
Total Delay
100 Minutes
200 Minutes
3.89 Hours
RTH Exeter – RTH Washington Binary Link Thursday, May 17 2007
Max Thruput to EGRRTransmission Delay
Internal Delay
Total Delay
100 Minutes
200 Minutes
4.44 Hours
Bandwidth Utilization
Bandwidth Utilization Total
Bytes (bytes/sec)
Frames (frames/sec)
CMC – RTH Washington Link Thursday, May 17 2007To KWBC
To CWRO
CMC – RTH Washington Text Link Thursday, May 17 2007 Bytes from CWTO
50 Kb
150 Kb
Min, Avg & Max input delay
50 Seconds
100 Seconds
Products from CWTO
CMC – RTH Washington Text Link Thursday, May 17 2007
100
300
# Products by size
100
300
CMC – RTH Washington Binary Link Thursday, May 17 2007 Bytes from CWTO
200 Kb
800 Kb
Min, Avg & Max input delay
10 Seconds
40 Seconds
CMC – RTH Washington Binary Link Thursday, May 17 2007 Products from
CWTO
100
500
# Products by size
100
500
RTH Washington All products Thursday, May 17 2007 Bytes to KWBC
200 Mb
600 Mb
Min, Avg & Max input delay
100 Seconds
200 Seconds
RTH Washington All products Thursday, May 17 2007 Products to
KWBC
10 K
40 K
# Products by size
10 K
40 K
RTH Washington All products Thursday, May 17 2007
Avg Inter-System ThruputTransmission Delay
Internal Delay
Total Delay
60 Seconds
20 Seconds
140 Seconds
RTH Washington All products Thursday, May 17 2007
Transmission Delay
Internal Delay
Total Delay
Max Inter-System Thruput
100 Seconds
200 Seconds
600 Seconds
“Taking the pulse of the planet”“Taking the pulse of the planet”
IssuesIssues
MTN Cloud 1 Expiry
– Contract end - Dec 2007
– BT interested in 1 year extension
– WMO coordination underway, meeting late 2007
RTH Exeter – RTH Washington Link
– Delays up to 5 hours
– Psbl traffic shaping issue
– Traffic growth expected
– Should we up bandwidth up current link or wait for cloud 1 replacement?
MTN Cloud 1 Expiry
– Contract end - Dec 2007
– BT interested in 1 year extension
– WMO coordination underway, meeting late 2007
RTH Exeter – RTH Washington Link
– Delays up to 5 hours
– Psbl traffic shaping issue
– Traffic growth expected
– Should we up bandwidth up current link or wait for cloud 1 replacement?
“Taking the pulse of the planet”“Taking the pulse of the planet”
IssuesIssues
CMC – Washington Link
– No problem with existing traffic on link– Plan to move NAEFS data to operational link– Psbl move of RADAR data to link– NWS/OCIO investigating cost of upgrade – Should we look at NESDIS requirement also?
WMO Information System (WIS)?
– Euro GISC – Washington GISC interaction & needs?– Metadata catalogue coordination?– Communication requirements?– When to address this - next meeting?
CMC – Washington Link
– No problem with existing traffic on link– Plan to move NAEFS data to operational link– Psbl move of RADAR data to link– NWS/OCIO investigating cost of upgrade – Should we look at NESDIS requirement also?
WMO Information System (WIS)?
– Euro GISC – Washington GISC interaction & needs?– Metadata catalogue coordination?– Communication requirements?– When to address this - next meeting?
“Taking the pulse of the planet”“Taking the pulse of the planet”
Your Data and Product AdvocatesData Management Staff
Fred [email protected] (301) 713-0864 ext 146Julie Hayes - Family of Services Manager [email protected] (301) 713-0864 ext 120Walter Smith - Team Lead, Data [email protected] (301) 713-0864 ext 139Richard Robinson - Data Manager [email protected] (301) 713-0864 ext 179Cynthia Cromwell – Data Manager [email protected] (301) 713-0864 ext 143
KWBC Communication Control Center (CCC) - Tech ControlPoint of contact 24 hours every [email protected]: (301) 713-0902 Fax: (301) 587-1773
“Taking the pulse of the planet”“Taking the pulse of the planet”
Thank You!Thank You!
Additional
Questions???
Additional
Questions???