Table of Contents Section 1: Introduction... 2 1.1 Purpose... 2 1.2 Background..... 2 Section 2: VPN Structure.... 3 2.1 VPN Description... 3 Section 3: Network Design... 4 3.1 Access Solutions...... 4 3.2 VPN Access Design... 5 Section 4: Suppport... 6 4.1 OPSnet Technical Support...... 6 4.2 OPSnet Technical Support... 7 Section 5: Subscribing to the FOS Via OPSnet... 8 5.1 FOS Agreements and Fees... 8-11 5.2 FOS Point of Contact... 12 Section 6: Connection Checklist... 13 6.1 Checklist... 13 Page 1 of 13 October 5, 2011
Section 1: Introduction 1.1 Purpose The purpose of this document is to outline the interconnect options being offered by the National Weather Service for access to the Telecommunications Gateway (TG) using the Office of Operational System Network (OPSnet). 1.2 Background OPSnet is an enterprise network using Request for Comments (RFC) compliant carrier provided Multi- Protocol Label Switching System (MPLS) transport services across a true IP backbone with any to any capability. The OPSnet design utilizes RFC compliant MPLS Virtual Private Network (VPN) services offered by the carrier allowing it to establish multiple, private intranet backbones across the same network. The Telecommunications Gateway network operates out of Silver Spring, Maryland at the National Weather Service headquarters campus. To support continuity of operations or COOP, the TG has implemented a Backup Telecommunications Gateway (BTG) at another geographic location that will allow for a failover of network operations and services in the event of a catastrophic failure of the primary network at headquarters. Page 2 of 13 October 5, 2011
Section 2: VPN Structure 2.1 VPN Description Partner Hub and spoke topology o Hub(s): TG, BTG o Spokes: Partner connections Provides access to TG/BTG IP data services o TGDATA FTP/HTTP Cluster For those partners that require access to the Partner VPN, their interface design should factor in security controls that meet the partner s security requirements. The hub and spoke topology will limit route advertisements so partners will only receive hub routes with the VPN. Page 3 of 13 October 5, 2011
Section 3: Network Design 3.1 Access Solutions The NWS is offering two design solutions when making connections to the MPLS backbone, a direct connection into the Verizon backbone or a gateway for partners using other carrier solutions. Direct Partner orders a MPLS circuit directly from NWS carrier (Verizon), in coordination with NWS. The NWS will then authorize the carrier to grant access into appropriate VPN(s). The partner will host the circuit on their premise and peer directly with the NWS carrier. Direct connection requirements: Layer 3 device with WAN support on their premise One interface per VPN, physical or logical Border Gateway Protocol (BGP) support Global IP addressing Gateway NWS will host a connection to the MPLS backbone at a predefined carrier hotel location. The partner will terminate a circuit from their carrier at the NWS specified carrier hotel location, in coordination with the NWS. The partner will then have two options for connecting to the NWS backbone. Option 1: Partner will co-locate a layer 3 device at the carrier hotel to host the partner s carrier circuit. This device will support an Ethernet interface to the NWS gateway device. Option 2: Partner will have their carrier s circuit directly terminated on the NWS gateway device, in coordination with the NWS Gateway connection requirements: Option 1 o A layer 3 device with WAN support at carrier hotel o Ethernet interface(s) o One interface per VPN, physical or logical o Border Gateway Protocol (BGP) or Open Shortest Path First (OSPF) support o Public IP addressing Option 2 o A layer 3 device with WAN support on their premise o One interface per VPN, physical or logical o Border Gateway Protocol (BGP) or Open Shortest Path First (OSPF) support o Global IP addressing Partners can gain access to one or both VPNs using either one of the access solutions. For both access solutions, the following exceptions are subject to approval by the NWS: Static routing Private IP addressing Gateway location: TBD Cost Information: TBD Page 4 of 13 October 5, 2011
3.2 VPN Access Design Physical Topology The following access design shows partners 1 3 with direct connections, partners 4 5 with an NWS gateway connection using option 2 and partner 6 with an NWS gateway connection using option 1. Page 5 of 13 October 5, 2011
Section 4: Support 4.1 OPSnet Technical Support For technical support on identifying your access solution, please contact the NWS OPS34 Branch OPSnet Engineering Support Team: Program Manager Phil Craig Phone: 1-888-NOAANET (1-888-662-2638) Email: NOAAnet.support@noaa.gov Network Engineer Keith Myers Phone: 1-888-NOAANET (1-888-662-2638) Email: NOAAnet.support@noaa.gov Engineering Support Christopher D. Parris Phone: 1-888-NOAANET (1-888-662-2638) Email: NOAAnet.support@noaa.gov Page 6 of 13 October 5, 2011
Section 4: Support 4.2 Verizon Technical Support For technical support in ordering your MPLS circuit from Verizon, please contact: (1) Verizon Federal Sales Representative for the National Weather Service Then contact: Emily Waldron Verizon Federal Office: 703-886-7007 Mobile: 703-999-4738 Email: emily.waldron@verizonbusiness.com Page 7 of 13 October 5, 2011
Section 5: Subscribing to the Family of Services (FOS) via OPSnet 5.1 FOS Agreements/User Fees When subscribing to the FOS you must complete a FOS Agreement. The FOS Agreement can be obtained from the following locations: http://www.weather.gov/datamgmt/fos/fosindex.html Your agreement should include: 1. name of your company 2. which service(s) you want to subscribe to 3. the signature, printed name, title, and date Page 8 of 13 October 5, 2011
Section 5: Subscribing to the Family of Services (FOS) via OPSnet Continued 5.1 FOS Agreements/User Fees The annual maintenance fees, covers one U.S. Government fiscal year, the period October 1, 2011, through September 30, 2012. The annual maintenance fee is the sum of the base cost and the circuit bandwidth cost for the Direct Connect Access to OPSnet and/or the sum of the base cost, the circuit bandwidth cost, and the carrier hotel cost for the NYAP Connection to OPSnet for the service (s) chosen by the Applicant. Please note that the final Product/Service Price has been rounded to the nearest dollar. The Government s user fees for fiscal year 2012 are: Direct Carrier Total Cost for Connect Hotel New York Cost Access Point Base Costs Server Access Service (SAS) $ 38,896 $ 38,896 Radar Product Service (RPS) $ 14,306 $ 14,306 Data Circuit Costs T1/1.544 Mbps $ 711 $ 12,989 $ 13,700 2xT1/3Mbps $ 1,381 $ 20,529 $ 21,910 6 Mbps/Fractional DS3 $ 2,762 $ 83,384 $ 86,146 DS3/45Mbps $ 20,714 - - Total Costs SAS - T1/1.544 Mbps $ 39,607 $ 52,596 SAS - 2xT1/3Mbps $ 40,277 $ 60,806 SAS - 6 Mbps/Fractional DS3 $ 41,658 $ 125,042 SAS - DS3 $ 59,610 RPS - T1/1.544 Mbps $ 15,017 $ 28,006 RPS - 2xT1/3Mbps $ 15,687 $ 36,216 RPS - 6 Mbps/Fractional DS3 $ 17,068 $ 100,452 RPS - DS3 $ 35,021 SAS and RPS - 2xT1/3Mbps $ 54,583 $ 75,112 SAS and RPS - 6 Mbps/Fractional DS3 $ 55,964 $ 139,348 SAS and RPS - DS3 $ 73,916 Page 9 of 13 October 5, 2011
Section 5: Subscribing to the Family of Services (FOS) via OPSnet Continued 5.1 FOS Agreements/User Fees Annual user fees are due to the NWS each year by October 1, and cover a one-year period from October 1 through September 30 of the following year. Fees are prorated on a quarterly basis as shown below: 1st Quarter - October, November & December - Full Fee 2nd Quarter - January, February & March - 75% of Fee 3rd Quarter - April, May & June - 50% of Fee 4th Quarter - July, August & September - 25% of Fee Page 10 of 13 October 5, 2011
Section 5: Subscribing to the Family of Services (FOS) via OPSnet Continued 5.1 FOS Agreements/User Fees 1. determine what your fees are 2. fees are remitted via Automated Clearing House (ACH) ACH Instructions Please contact Julie Hayes (Julie.Hayes@noaa.gov) for information on remitting your user fees via Automatic Clearing House (ACH). The receipt of your agreement form and user fees will be the authorization for you to negotiate with the communications carrier for connection to the Server Access Service (SAS) and/or the Radar Products Service (RPS). The NWS will process and return to you a properly executed copy of the agreement form for your records and retain a copy at the NWS. Page 11 of 13 October 5, 2011
Section 5: Subscribing to the Family of Services (FOS) via OPSnet 5.2 Family of Services Point of Contact FAMILY OF SERVICES PROGRAM MANAGER Julie L. Hayes E-mail: julie.hayes@noaa.gov Phone No.: (301) 713-0864 ext 120 Page 12 of 13 October 5, 2011
Section 6: Connection Checklist 6.1 Checklist Step 1. Decide on service(s) desired Step 2. Fill out the FOS Agreement Form Step 3. Contact the FOS Program Manager Step 4. Contact NWS OPSnet Technical Support Team (Networking) to coordinate connection schedule. Step 5. Order Equipment and Circuit(s) Step 6. Configure connection Page 13 of 13 October 5, 2011