inet-rtr support
Curtis Villamizar
Tue May 16 16:30:04 CEST 1995
In message <199505160141.VAA17910 at home.merit.edu>, "Dale S. Johnson" writes: > Curtis, > > As does ours: > > # inet-rtr > # > OBJ ir ATSQ ir la if pe ac tc rm ny mb ch so > OBJ ir MAND ir la if tc ac ch so > OBJ ir OPT pe ny mb rm > OBJ ir MULT if pe tc ac rm ny ch mb > OBJ ir SORT 9 > OBJ ir UNIQ ir > OBJ ir KEYS ir if > OBJ ir REC tc ac > > You say your implementation does accept inet-rtr objects? > > Would you try this one: > > inet-rtr: nss11.ans.net > localas: AS690 > ifaddr: 140.222.11.1 255.255.255.0 > ifaddr: 140.222.11.2 255.255.255.0 > ifaddr: 140.222.11.3 255.255.255.0 > ifaddr: 140.222.11.5 255.255.255.0 > ifaddr: 140.222.11.62 255.255.255.0 > ifaddr: 140.222.8.195 255.255.255.0 > ifaddr: 192.103.60.5 255.255.255.0 > ifaddr: 198.32.128.66 255.255.255.0 > ifaddr: 199.221.47.5 255.255.255.0 > peer: 140.222.8.196 AS1321 BGP passive > peer: 198.32.128.226 AS1688 BGP passive > peer: 198.32.128.65 AS1688 BGP passive > peer: 199.221.47.7 AS1957 BGP passive > peer: 198.32.128.20 AS2041 BGP passive > peer: 198.32.128.130 AS2882 BGP passive > peer: 198.32.128.67 AS3561 BGP passive > peer: 198.32.128.97 AS3561 BGP passive > peer: 198.32.128.16 AS3830 BGP passive > admin-c Steve Heimlich > tech-c: Selina Priestley > mnt-by: ANS > changed: nsfnet-admin at merit.edu 950227 > source: RADB > > --Dale Dale, I sent you a set of route objects. What happen to them? Please note the following: nslookup nss11.ans.net Server: localhost Address: 127.0.0.1 *** localhost can't find nss11.ans.net: Non-existent host/domain nslookup cnss11.t3.ans.net Server: localhost Address: 127.0.0.1 Name: cnss11.San-Francisco.t3.ans.net Address: 140.222.11.62 Aliases: cnss11.t3.ans.net hint: If (# < 128) { use cnss# } else { use enss# }. The Problem above is that the admin-c line does not have a ":" This worked for me but I changed the database name and maintainer name to make the authorization pass. Please use the real DNS names so if people ever try to verify the existance of the routers, it will be possible to do so. Curtis ps- since you are not using the inet-rtr object I sent you, the interfaces are likely to be wrong and information in the remarks that we will actually use to generate configs will be missing. This is OK as long as you make sure that the maintainer objects allow us to modify these as well as you. For the time being, I'll just put the local ANS database ahead of RADB in the path. bin/dbupdate -m curtis at ans.net -v /tmp/dsj.object Update OK: [inet-rtr] nss11.ans.net No error/warnings were found in your database update. Congratulations. ------------------------------------------------------------------------ Please use <auto-dbm at ans.net> instead of <ans-dbm at ans.net> and <auto-assign at ans.net> instead of <assign at ans.net> for fast turnaround times on all but guarded objects. If you have any question about an error or warning message, please contact <ans-dbm at ans.net>. Sincerely Yours, ANS Database Maintenance Department (Automatic Section) [curtis at curtis.ansremote.com 22] cat !$ cat /tmp/dsj.object inet-rtr: nss11.ans.net localas: AS690 ifaddr: 140.222.11.1 255.255.255.0 ifaddr: 140.222.11.2 255.255.255.0 ifaddr: 140.222.11.3 255.255.255.0 ifaddr: 140.222.11.5 255.255.255.0 ifaddr: 140.222.11.62 255.255.255.0 ifaddr: 140.222.8.195 255.255.255.0 ifaddr: 192.103.60.5 255.255.255.0 ifaddr: 198.32.128.66 255.255.255.0 ifaddr: 199.221.47.5 255.255.255.0 peer: 140.222.8.196 AS1321 BGP passive peer: 198.32.128.226 AS1688 BGP passive peer: 198.32.128.65 AS1688 BGP passive peer: 199.221.47.7 AS1957 BGP passive peer: 198.32.128.20 AS2041 BGP passive peer: 198.32.128.130 AS2882 BGP passive peer: 198.32.128.67 AS3561 BGP passive peer: 198.32.128.97 AS3561 BGP passive peer: 198.32.128.16 AS3830 BGP passive admin-c: Steve Heimlich tech-c: Selina Priestley mnt-by: MAINT-AS690 changed: nsfnet-admin at merit.edu 950227 source: ANS -------- Logged at Tue May 16 17:41:31 MET DST 1995 ---------
[ rr-impl Archive ]