bstrong@sleepy.bmd.trw.com (04/11/91)
Hello,
I have a problem. We have lost connection to a site we need to
get to (for e-mail mainly). Pinging it gives no response, although
Nslookup can tell me its ip address. They are not down and can get
out onto the rest of the Internet as can we. I think I'm getting
"stuck" at one certain router and I'd like confirmation/correction on
this. Here's what's going on:
we're oz.bmd.trw.com (129.193.100.6) and we're trying to get to
afsc-bmo.af.mil (132.62.71.1)
When I did a traceroute to afsc-bmo.af.mil on 4/10/91 I got this -
1 outdsg.nba.TRW.COM
.
.
.
13 192.52.195.1
14 * * *
15 * * *
.
.
.
30 * * *
This tells me why I can't get to afsc-bmo - I'm exceeding 30 hops - but
what the heck is happening? I know there's no way it's even 30 hops to
this site - we could mail to them last week. What is this router at
192.52.195.1 doing? When I traceroute just to 192.52.195.1 I got this -
1 outdsg.nba.TRW.COM
.
.
.
13 192.52.195.1 (192.52.195.1) 1080 ms 1030 ms 1070 ms
14 192.52.195.1 (192.52.195.1) 1060 ms !P 1020 ms !P 1050 ms !P
What does the second hop with the bang 'P' for? I've never seen this !P
and didn't see anything in out documentation (using Wollongong TCP/IP for
VMS). Now, one more thing, I did another traceroute this morning
(4/11/91) and got the same thing except that the IP address, 192.52.195.1,
now has a logical address and shows up as MOFFETT-FLD-MB.DDN.MIL in the
traceroute, but the trace is still identical to the previous one. Are
these guys just configuring a new router or what? I don't know who to
contact to ask in person about it. Could someone help???
As is obvious, I'm a real novice so please look past my ignorance.
===============================================================================
Bryan Strong TRW * Ogden, UT * USA
Computing Services / Software Support
Internet: bstrong@oz.bmd.trw.com
Phone: 801.625.8090mcc@WLV.IMSD.CONTEL.COM (Merton Campbell Crockett) (04/16/91)
Several points to consider. Afsc-bmo.af.mil is at 131.62.71.1 rather than 132.62.71.1. From my vantage point on DDN, I get a network unreachable. Chances are an AF Concentrator has recently been installed or has failed. The !P response from MOFFETT-FLD-MB.DDN.MIL is a port unreachable. Look at the man page in [NETDIST.DOCS] for the distinction between port (!P), host (!H), and network (!N) unreachable states. MOFFETT-FLD-MB.DDN.MIL appears to be down or overloaded at the moment as the traceroute to your site is getting routed through MCLEAN-MB.DDN.MIL, SURAnet, NSFnet, and CERFnet even though we're only about 45 miles apart. Merton Campbell Crockett Contel Federal Systems, GSysG/WLO
malis@BBN.COM (Andy Malis) (04/16/91)
Bryan, > we're oz.bmd.trw.com (129.193.100.6) and we're trying to get to > afsc-bmo.af.mil (132.62.71.1) afsc-bmo.af.mil (actually 131.62.7.1) is an Air Force host at Norton Air Force base, behind an Air Force Concentrator (Cisgo gateway) connected to the MILNET. The Concentrator is norton-piv-1.af.mil, with addresses 26.8.0.39 and 131.62.0.1. > When I did a traceroute to afsc-bmo.af.mil on 4/10/91 I got this - > 1 outdsg.nba.TRW.COM > . > . > . > 13 192.52.195.1 > 14 * * * > 15 * * * > . > . > . > 30 * * * As of 09:30 EDT on 4/16, it appears that norton-piv-1.af.mil is dead. I'm able to ping 26.0.0.39 (another host on the same MILNET PSN), but 26.8.0.39 isn't answering. When trying a traceroute from BBN to afsc-bmo.af.mil, the NSFNET reports that the destination network is unreachable: 7 princeton-nss.near.net (192.80.80.1) 40 ms !N 40 ms !N 20 ms !N I also tried a traceroute via your host, by using "traceroute -g oz.bmd.trw.com afsc-bmo.af.mil", and found a router at TRW was reporting host unreachable: 20 129.193.76.252 (129.193.76.252) 340 ms !H * 400 ms !H > What is this router at 192.52.195.1 doing? When I > traceroute just to 192.52.195.1 I got this - > 14 192.52.195.1 (192.52.195.1) 1060 ms !P 1020 ms !P 1050 ms !P 192.52.195.1 is MOFFETT-FLD-MB.DDN.MIL, a Mailbridge between the NSFNET (and several other nets) and the MILNET. It is responding to traceroute by reporting that it is receiving datagrams using an unsupported protocol (the !P flag). You should read the traceroute man page for more information on how it works, and other indications you can receive from traceroute. In general, if you are having trouble reaching a host on the MILNET, or on a network behind a MILNET-attached router, such as an Air Force Concentrator, you should call the MILNET Monitoring Center at (800) 451-7413, or (202) 692-5726. They are also reachable by email at DCA-MMC@DCA-EMS.DCA.MIL. Regards, Andy Malis BBN Communications
jonson@SERVER.AF.MIL (Lt. Matt Jonson) (04/17/91)
<Merton Campbell Crockett writes> > Subject: Re: Goofy Router? > > Several points to consider. Afsc-bmo.af.mil is at 131.62.71.1 rather than > 132.62.71.1. Further point to consider: afsc-bmo is at 131.62.7.1... ^^^ > From my vantage point on DDN, I get a network unreachable. > Chances are an AF Concentrator has recently been installed or has failed. > Whoa! The concentrator must not have as good a rep as I thought. As it happens, the concentrator has been at Norton for quite a while, and yesterday the cisco gateway's line to the PSN had hung up - probably why you got the net unreachable. Last night, it hung again at around 1130, so today (this morning) it had been flushed from the Core Gateways' tables, and again should have been showing net unreachable. We couldn't get ahold of anyone at the site to check it during the odd hours. It is now up. We have had an outstanding problem with ciscos using the MCI card hanging on the line to the Milnet Node. We have also had a problem with the Milnet monitors just deciding to loop back ports that concentrators are connected to without contacting us. Oh, and if you look it up, the NIC still has the concentrator registered as NORTON-PIV-I, which is the name of a Unisys mainframe that has been rehomed behind the concentrator. You can contact us for further questions, but things seems to be back to normal. /matt -- Lt Matthew W Jonson jonson@server.af.mil snail-mail: Network Systems Engineer 205-279-4075 SSC/SSMT USAF DDN Program Office AV: 596-4075 Gunter AFB, AL 36114