************************************************************************ DDN MGT Bulletin: 9411 DISA DDN Defense Communications System 25 OCT 1994 Published by: DDN Network Info Center (NIC@NIC.DDN.MIL) (800) 365-3642 DEFENSE DATA NETWORK MANAGEMENT BULLETIN The DDN MANAGEMENT BULLETIN is distributed online by the DDN Network Information Center under DISA contract as a means of communicating official policy, procedures and other information of concern to management personnel at DDN facilities. Back issues may be read through the TACNEWS server ("@n" command at the TAC) or may be obtained by FTP (or Kermit) from the NIC.DDN.MIL host [192.112.36.5] using login="anonymous" and password="guest". The pathname for bulletins is ddn-news/ddn-mgt-bulletin-nn.txt (where "nn" is the bulletin number). ************************************************************************ SUBJECT: DSNET1 T/20 ROUTE SERVER ASSIGNMENTS This message provides specific information regarding the upcoming routing assignments for DSNET1 hosts and gateways. The new T/20 routing service will provide the routing assignments for DSNET1 subscriber gateways and default gateway assignments for DSNET1 hosts. As networks move from DSNET1 to SIPRNET, the T/20 routing service will be able to provide new routing information so that hosts do not have to update their routing tables with every move. ************************************************************************* 1. This bulletin provides the primary/secondary T/20 assignments for DSNET1 gateways and hosts. It also provides, in paragraph 4, telephone numbers for assistance in configuring user gateways and hosts. Request that DSNET1 subscriber gateways and hosts switch to the new assignments listed in this message by 6 December 1994. 2. As of 6 October 1994 two T/20 route servers have been connected to DSNET1 Nodes 3 DCA1 and 30 FT-RITCHIE. Section 5 gives the IP addresses of the two new T/20s. These DSNET1 T/20s will be used temporarily to assist with DSNET1-to-SIPRNET transition of users. The T/20s will provide dynamic routing information to the subscriber gateways and default routing information to the hosts. The following information is provided to explain the responsibilities of the subscriber HOST administrators in this transition. Section 6 lists T/20 route server assignments, by PSN, that DSNET1 subscriber hosts should use to configure their static default routes. Section 6 also applies to subscriber gateways which need to configure static default routes because they are unable to obtain dynamic default routes directly from the T/20 route servers. The following information explains the responsibilities of subscriber GATEWAY administrators. Section 6 lists T/20 route server assignments, by PSN, that subscriber gateway administrators should use to configure the EGP or BGP neighbor addresses of the assigned T/20s. Section 7 shows a sample subscriber gateway configuration file for cisco routers. The Border Gateway Protocol (BGP) is the recommended protocol for subscriber gateways (although EGP service will be provided to those subscribers who can't switch to BGP). To achieve optimal routing, it is important for subscriber gateways to prefer routes from their primary routing server over their secondary routing server. This capability exists on most subscriber gateways. Specifically, Cisco gateways are able to prefer routes from one EGP/BGP neighbor over another. If you require assistance configuring your gateway to accomplish this preference, please contact the technical representative listed in section 4. 3. These assignments are based upon topological grounds to optimize routing within DSNET1. Specifically, they are based on minhop path lengths across DSNET1 and the balancing of the number of hosts and gateways assigned to each route server. Compliance to these assignments is critical to ensure maintenance of the proper level of services. Please keep in mind that geographical distances do not necessarily correspond to topological distances on DSNET1. The DSNET1 topology will be changing as its users transition to the SIPRNET. The assignments listed in Section 6 will be reviewed periodically to ensure that routing continues to be optimal. Any such significant changes will be announced in future DDN Management Bulletins. 4. Questions about this bulletin should be addressed to : Andrew Hogan, DDN DSNET1 Operations DSNET1 Mgr, HQ DISA, Code: UTDS Commercial: (703) 692-7580/81 DSN: 222-7580/81 e-mail: disnetmgr@ddn-conus.ddn.mil In CONUS, technical questions should be addressed to the CONUS Monitoring Center, 1-800-451-7413. In Europe, technical questions should be addressed to the European Monitoring Center - ETS 430-5532. In the Pacific, technical questions should be addressed to the Pacific Monitoring Center - DSN 456-1472, 1473 or 1474. 5. The IP addresses of the new T/20 routing servers are: Address Name ---------------------------- 22.9.0.3 ARLINGTON 22.9.0.30 SITE-R ================================================================== 6. T/20 Route Server to PSN Assignments ===================================== This table lists a primary and a secondary T/20 route server assigned to each PSN. DSNET1 HOST Administrators must use this table to configure primary and secondary default routes. Static routes may also be used by gateways that are unable to obtain dynamic default routes from the T/20 route servers. DSNET1 gateway administrators must also use this table to configure the EGP or BGP neighbor address of the assigned T/20s. Primary Secondary No. Name Name Address Name Address --------------- ------------------- --------------------- 1 RAMSTEIN SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 2 VAIHINGEN ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 3 DCA1 ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 4 YOKOTA SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 5 FT.BELVOIR SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 7 PENTAGON ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 8 SCOTT SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 9 ANDREWS ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 10 FTHOOD ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 11 FTHUACHUCA ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 12 MCCLELLAN SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 13 WAHIAWA SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 14 FT-DETRICK ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 15 FT-MONMOUTH SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 16 PUGET-SOUND SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 17 FT.MCPHERSON ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 20 DCA2 ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 21 LANGLEY ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 22 STOCKTON SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 23 WRIGHT-PAT SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 24 ROCKISLAND SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 26 OFFUTT SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 30 FT-RITCHIE SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 31 NTCC ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 32 BOLLING ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 33 HICKAM-AFB ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 34 MACDILL SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 35 HANCOCK-FLD SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 39 DHAHRAN ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 40 ABERDEEN SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 42 KELLY-AFB ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 45 HILL SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 50 YONGSAN SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 55 COROZAL ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 57 FRANKFURT SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 65 SANDIEGO ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 66 JACKSONVILLE ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 68 MILDENHALL SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 70 NORFOLK ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 71 AFSD SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 72 PATRICK-AFB SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 81 WHEELER-AFB ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 100 SEMBACH ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 101 ROTA ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 104 RAMSTEIN2 ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 106 CROUGHTON ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 126 FT-BRAGG SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 134 VICENZA ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 168 GSA1 ARLINGTON 22.9.0.3 SITE-R 22.9.0.30 169 GSA2 SITE-R 22.9.0.30 ARLINGTON 22.9.0.3 7. Sample config file for cisco routers: router bgp network (repeat if more than one directly connected network) neighbor remote-as 3418 neighbor remote-as 3418 Comment: 3418 is the autonomous system of the T/20 route servers.