"advisory" object
Susan R. Harris
Mon Aug 28 16:07:31 CEST 1995
Hi Dale! On Steve Heimlich's request, we've been telling people that their best source of info for the advisories is ANS (noc at ans.net). We've also occasionally sent out this internal doc, to give people some initial help. ------------------- How to Create Advisory Lines for RADB Route Objects In order to route your network traffic over ANSnet (AS690), you must include an advisory line (also known as an "advisory field" or "advisory attribute") in each Route object you submit to the Routing Arbiter Database (RADB). Advisory lines specify: --The peer or adjacent ASs (autonomous systems) that will announce the route to AS690. --Optionally, the AS690 routers that will listen for these announcements, and --The order in which you prefer to have your traffic routed. The use of advisory lines is a temporary measure; advisories won't be needed once ANS installs software that eliminates the need to specify the routers that peer directly with ANSnet. EXAMPLE ADVISORY LINE Here is an example of a Route object containing an advisory line: route: 193.101.106.0/24 descr: DETECON Deutsche Telepost Consulting GmbH descr: Langer Grabenweg 35 descr: D-53175 Bonn descr: Postfach 26 01 01 descr: D-53153 Bonn descr: GERMANY origin: AS1270 comm-list: COMM_NSFNET advisory: AS690 1:701(136) 2:701(134) 3:1800 mnt-by: MAINT-AS1270 changed: nsfnet-admin at merit.edu 950308 source: RADB The advisory line above indicates that, for the IP prefix 193.101.106.0/24, AS690 will prefer AS701 over AS1800; i.e., if AS701 announces 193.101.106.0/24 to AS690, AS690 will forward traffic to addresses matching this prefix to AS701. (If AS701 is down or otherwise not announcing this route to AS690, then AS690 will forward traffic to AS1800 if the latter is announcing 193.101.106.0/24 to AS690.) Further, an announcement of this route by AS701 that is received at the node known as NSS 136 (in AS690) will be preferred over that received at NSS 134; if AS690 receives an announcement of 193.101.106.0/24 from AS701 at both NSSs, it will forward all traffic to destinations matching that prefix to the AS701 router that peers with NSS 136. HOW TO DETERMINE PEER AUTONOMOUS SYSTEMS If you don't know which AS transmits your traffic to AS690, there are several ways to find the information: --The easiest way is to check with your network provider. --If that doesn't work, the 'prtraceroute' tool is helpful, as it is a form of traceroute that displays the ASs that a packet traverses. Prtraceroute is available from: http://www.ra.net/routing.arbiter/RA/RADB.tools.docs.html ftp://ftp.ra.net/routing.arbiter/pride/prtraceroute-2.0beta2.shar.gz ftp://ftp.ra.net/routing.arbiter/pride/prtraceroute.README --If you don't have prtraceroute available, you can also use traceroute. PRTRACEROUTE EXAMPLE To use prtraceroute to identify the AS adjacent to AS690, start by tracing the route from your local network to ANSnet. The example below shows the route to the ANS backbone network, and uses an arbitrary prefix for ANSnet: prtraceroute 140.222.1.1 1 AS237 merit-gw.med.umich.edu 198.108.60.1 2 AS237 tcags-f0.med.umich.edu 141.214.254.3 3 ??? F-BACKBONE.c-CCB.UMNET.UMICH.E 141.211.1.1 4 AS237 fdd3-0.michnet1.mich.net 198.108.3.1 5 ??? cpe2-fddi-1.Chicago.mci.net 192.203.195.5 6 AS3561 border2-hssi2-0.Chicago.mci.ne 204.70.25.9 7 ??? core-fddi-1.Chicago.mci.net 204.70.3.81 8 AS3561 core-hssi-2.Boston.mci.net 204.70.1.45 9 ??? core-hssi-2.NewYork.mci.net 204.70.1.1 10 AS3561 border2-fddi0-0.NewYork.mci.ne 204.70.3.18 11 ??? sprint-nap-ds3.NewYork.mci.net 204.70.45.6 12 AS690 192.157.69.4 192.157.69.4 13 AS690 192.157.69.4 192.157.69.4 You can now query the RADB to determine which provider maintains 204.70.45.6, the router that interfaces directly with AS690 and immediately precedes AS690 on the list. Enter the command: whois -h whois.ra.net 204.70.45.6 The output is an MCI Route object. Here is a partial listing: route: 204.70.45.4/30 descr: MCI NYU Border 1 origin: AS3561 mnt-by: MCI mnt-by: MCI [...] withdrawn: 941007 source: MCI This Route object shows that the route originates in AS3561, which is maintained by MCI. You may now want to contact MCI for help in preparing your advisory line. For MCI contact information, enter this command: whois -h whois.ra.net MAINT-AS3561 The output is an RADB Maintainer object. Here is a partial listing: mntner: MAINT-AS3561 descr: People authorized to make changes for AS3561 admin-c: Not Available from RADB upd-to: AS3561 at ra.net [...] notify: rr-types at mci.net mnt-by: MAINT-AS3561 [...] source: RADB You can then send e-mail to rr-types at mci.net for further information. If there is no "notify:" field, the "tech-c:", "auth:", and "changed:" fields may provide alternate contacts that can probably help you. TRACEROUTE EXAMPLE As with prtraceroute, start by tracing the route from your local network to ANSnet. The example below shows the route to the ANS backbone network using an arbitrary prefix for ANSnet: traceroute 140.222.1.1 1 merit-gw.med.umich.edu (123.456.78.99) 2 ms 100 ms 148 ms 2 tcags-f0.med.umich.edu (141.214.254.3) 6 ms 3 ms 2 ms 3 F-BACKBONE.c-CCB.UMNET.UMICH.EDU (141.211.1.1) 4 ms 5 ms 4 ms 4 fdd3-0.michnet1.mich.net (198.108.3.1) 55 ms 7 ms 99 ms 5 cpe2-fddi-1.Chicago.mci.net (192.203.195.5) 9 ms 4 ms 5 ms 6 border2-hssi2-0.Chicago.mci.net (204.70.25.9) 11 ms 9 ms 9 ms 7 core-fddi-1.Chicago.mci.net (204.70.3.81) 9 ms 9 ms 9 ms 8 core-hssi-2.Boston.mci.net (204.70.1.45) 29 ms 29 ms 65 ms 9 core-hssi-2.NewYork.mci.net (204.70.1.1) 136 ms 226 ms 161 ms 10 border2-fddi0-0.NewYork.mci.net (204.70.3.18) 33 ms 33 ms 34 ms 11 sprint-nap-ds3.NewYork.mci.net (204.70.45.6) 39 ms 37 ms 79 ms 12 fd-0.enss218.t3.ans.net (192.157.69.4) 38 ms 40 ms 39 ms 13 fd-0.enss218.t3.ans.net (192.157.69.4) 39 ms !H 37 ms !H 71 ms Since traceroute does not display any AS numbers that you can check, note the DNS name for the router that immediately precedes AS690 on the list. The name shows that the router is maintained by MCI. You can now query the InterNIC for MCI contact information: whois -h rs.internic.net mci.net Here is a partial listing of the output: MCI Telecommunications Communications (MCI2-DOM) internetMCI Provisioning 100 Perimeter Park Drive, Suite 1 Morrisville, NC 27560 Domain Name: MCI.NET Administrative Contact, Technical Contact, Zone Contact: MCI Internet Services (MCI-IS) hostmaster at mci.net (800) 773-6248 [...] If you have further questions about Route object advisory lines, send e- mail to noc at ans.net. On Sun, 27 Aug 1995, Dale S. Johnson wrote: > Did anyone ever finish publishing this? > > From swinnett at BBN.COM Tue Aug 8 11:11:54 1995 > Received: from merit.edu (merit.edu [35.1.1.42]) by home.merit.edu (8.6.12/merit-2.0) with ESMTP id LAA05443 for <dsj at home.merit.edu>; Tue, 8 Aug 1995 11:11:52 -0400 > Received: from BBN.COM (LABS-N.BBN.COM [128.89.0.100]) by merit.edu (8.6.12/merit-2.0) with SMTP id LAA18409 for <dsj at merit.edu>; Tue, 8 Aug 1995 11:11:52 -0400 > Message-Id: <199508081511.LAA18409 at merit.edu> > Date: Tue, 8 Aug 95 11:11:43 EDT > From: Steven Winnett <swinnett at BBN.COM> > To: dsj at merit.edu > cc: swinnett at BBN.COM > Subject: RADB Syntax Question > Status: RO > > Dale, > > Where is the syntax for "advisory" in the RADB route object defined? > It's not in RIPE-181. > > Thanks., > > Steve Winnett > BBN > > -------- Logged at Mon Aug 28 17:26:21 MET DST 1995 ---------
[ rr-impl Archive ]