HP3000-L Archives

January 2001, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"HOFMEISTER,JAMES (HP-USA,ex1)" <[log in to unmask]>
Reply To:
HOFMEISTER,JAMES (HP-USA,ex1)
Date:
Tue, 30 Jan 2001 14:05:03 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (75 lines)
Hello Folks @ 3000-l,

Re: TRACERT

Since I posted my earlier message, several folks have e-mailed me
asking what is TRACERT.

TRACERT is a tool which traces the route of IP traffic through
intermediate Routers and System Network Interfaces (IP level devices)
identifying the full IP path traveled from the source to the
destination system.

The way this is done with this version of the TRACERT tool is a packet
is sent to the destination system with a Time-To-Live (TTL) of 1 and
then the TRACERT waits for the next IP level system in-line to reply
with a ICMP message specifying TTL exceeded.  TRACERT then increases
the TTL by 1 and resends the same packet tracking the new IP address
reached at each step until the destination system or the max number of
hops is reached.


Here is a sample run of TRACERT on an right-coast HP e3000 to a
left-coast HPUX system.

:tracert.prvxl.telesup
Enter Host Name or IP addr[Press Return to exit]:wtec.cup.hp.com
Resolving IP Address.....
Enter the number of hops[min=1,max=60]:
Defaulting to 25 hops
Traceroute to wtec.cup.hp.com,hops=25
To TERMINATE Press CTRL-Y
#1 15.44.48.1  (atlagw2.atl.hp.com)  127ms 156ms 162ms
#2 15.44.216.9  (atldcr2.atl.hp.com) 168ms 194ms 199ms
#3 15.68.88.2  (atlhgw2.cns.hp.com) 690ms 715ms 725ms
#4 172.17.192.49  884ms 155ms 205ms
#5 15.73.152.2  (cuphgw1.cns.hp.com) 362ms 541ms 710ms
#6 15.36.88.5  (cuphgw5.cns.hp.com) 871ms 158ms 214ms
#7 15.75.208.38  (cup38bdipper-gw1.cup.hp.com) 382ms 574ms 756ms
#8 15.13.120.187  (wtec.cup.hp.com)   942ms *  154ms

In this example you can see that 7 IP Gateways/Routers exist between
my local MPE system and the destination system wtec.cup.hp.com.

Note:  The 172.17.192.49 address does not include a node name since
this IP address is not configured in a Domain Name Server.  I
verified this by using nslookup:

:nslookup 172.17.192.49
Server:  l3107ns1.ssr.hp.com
Address:  15.41.144.99

*** l3107ns1.ssr.hp.com can't find 172.17.192.49: Non-existent host/domain

If you are interested in testing TRACERT please contact the RC and request
patches NSTFDX5 for C.65.00 or NSTFDX4 for C.60.00 for TRACERT SR
5003-442715.

Note: If you are going to run TRACERT between 2 MPE machines it is necessary
to install the appropriate TRACERT patch on both the local and remote MPE
machines.  If you TRACERT to a remote MPE system which does not include the
TRACERT patch you will get a good TRACERT of all of the intermediate IP
Gateways/Routers, but you will get a "* *" when you reach the destination
MPE
system and you will need to CNTRL-Y to terminate TRACERT.

P.S. I am really interested in hearing test results from customers who
install this patch and are able to test TRACERT over FDDI and TOKEN RING.

Regards,

James Hofmeister
Hewlett Packard
Worldwide Technology Network Expert Center
P.S. My Ideals are my own, not necessarily my employers.

ATOM RSS1 RSS2