Traceroute Analysis for iepm-bw.twaren.net on 12/05/2007
Connie Logg, Les Cottrell, and Yee-Ting Li. Updated: Wed Dec 5 12:51:01 CST 2007


Checking a box for a node(s) and an hour(s) followed by: Previous day's Summary | Today's Traceroute Report | Directory of Historical Traceroutes | Help
NODE \ Hour (Pacific Time)=>
00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23
<= HOUR / NODE
iepm-bw.caltech.ul-org R Sum Log Click for available bitrate plot UDP iepm-bw.caltech.ul-org; route=31; time=00:11:54; hops=6; rtt=149.895 ms..... ...... ...... ..... iepm-bw.caltech.ul-org; route=175; time=04:08:09; hops=15; rtt=201.004 ms..... ..iepm-bw.caltech.ul-org; route=31; time=05:18:30; hops=6; rtt=149.792 ms.... ...... ...... iepm-bw.caltech.ul-org; route=39; time=08:10:27; hops=6; rtt=186.261 ms..... ...... ...... *iepm-bw.caltech.ul-org; route=179; time=11:20:00; hops=16; rtt=143.783 ms.... .*'..










iepm-bw.caltech.ul-org R Sum Log Click for available bitrate plot UDP
iepm-bw.snv.ul-org R Sum Log Click for available bitrate plot UDP tttttt tttttt tttttt ttttt ttttttt tttttt tttttt tttttt tttttt tttttt tttttt tttttt ttttt










iepm-bw.snv.ul-org R Sum Log Click for available bitrate plot UDP
node1.umich.ul-org R Sum Log Click for available bitrate plot UDP node1.umich.ul-org; route=26; time=00:11:04; hops=7; rtt=212.005 ms..... ttnode1.umich.ul-org; route=26; time=01:26:13; hops=7; rtt=212.000 mstnode1.umich.ul-org; route=26; time=01:47:02; hops=7; rtt=212.002 mst ttnode1.umich.ul-org; route=26; time=02:26:37; hops=7; rtt=211.993 ms... ..... node1.umich.ul-org; route=165; time=04:02:20; hops=12; rtt=206.762 mstnode1.umich.ul-org; route=165; time=04:20:09; hops=12; rtt=206.736 ms.... ..node1.umich.ul-org; route=26; time=05:25:28; hops=7; rtt=212.010 ms... ...... ...... node1.umich.ul-org; route=98; time=08:07:52; hops=7; rtt=226.707 ms..... ...... ...... .tnode1.umich.ul-org; route=176; time=11:28:09; hops=19; rtt=206.012 mstnode1.umich.ul-org; route=176; time=11:47:43; hops=19; rtt=205.914 ms. .ttt










node1.umich.ul-org R Sum Log Click for available bitrate plot UDP
NODE \ Hour (Pacific Time)=>
00

01

02

03

04

05

06

07

08

09

10

11

12

13

14

15

16

17

18

19

20

21

22

23
<= HOUR / NODE

The above table shows the changes in the traceroutes throughout the day. There are also links to detailed traceroutes, Available Bitrate Estimation time series, alert (identification of significant drops in bitrate performance) analysis, topology maps, and information on Autonomous Systems (AS) traversed in routes.
Character encoding of routes Route numbers and Cell coloring
  • A '.' indicates that the traceroute was exactly the same as the previous one.
  • A "*" indicates that one or more hops did not respond
  • A magenta character a-z or 0-9 indicates that an ! annotation was found in the traceroute, and the character was the accompanying code. If the character is orange, it indicates that a checksum error was also found in the traceroute.
  • A '|' indicates that the last hop was not reachable (i.e. the traceroute terminated after 30 hops, possibly the end host is behind a firewall).
  • A ':' indicates the only difference from the previous route is one or more nodes only differ in the last (4th) octet of the IP address.
  • An 'a' indicates the only difference from the previous route is one or more nodes have different IP addresses but they are in the same Autonomous System (AS)
  • A "'" indicates a stutter, i.e. a router responded to multiple TTLs,
  • An orange . or | or : or * or a or '' of orange route number icon indicates there was an ICMP checksum error noted in the traceroute.
  • A red ? indicates the host was unknown (probably name was unresolvable).
  • A red t indicates the traceroute command hung and had to be terminated. There was no output.
  • A 'u' indicates that we were unable to parse traceroute.
  • Numbered blocks:
    • A red numbered block indicates that there was more than one change in the traceroute from the previous one, and it was not just the case of a single router not responding, and the router was not in the same subnet or Autonomous System (AS)
    • An orange numbered block indicates that the traceroute significantly differed from the previous one in only one hop.
    The numbers in the blocks are the route number identifiers, and have no signifcance other the fact that they are an index which points to the route in the 'R' link. In case the routenumber identifier is larger than two digits, an iconic is used and the route number in in the mouse over message. No entry probably means no measurement was made, maybe the measurement host was down. Placing the mouse over a numbered block will show the time the trace was done, the number of hops, and the RTT to the end node.
  • Table cells with a colored background indicate a change in available bitrate was detected.
The links in the row headings on the left & right are used as follows (n.b. for privacy reasons, links with an asterisk (*) are only accessible from SLAC hosts):
  • The node name link points to a detailed html page which provides router interface names and addresses and Round Trip Times) of the traceroutes for that node for that day.
  • The route numbers (if they exist) for a node can be viewed by clicking on the 'R' link next to the nodename.
  • The 'Sum' link is a pointer to the summary table of the routes for the day.
  • The 'Log' link is a pointer to log ('rawdata') of the traceroutes for the day.
  • The link is a pointer to the current graph of all the data for the selected node (i.e. for traceroutes in the past, this still points to the current days graph).
  • The name 'UDP' or 'ICMP' indicates the type of traceroute probes being used.

More information

See:

Bugs/features:

When selecting an archived (NOT today's) traceroute table and clicking on the time series graph icon for a target, only the most recent (last 10 days) performance data is provided.
/home/iepm/v3src/traceanal/traceanal created this web page on iepmbw.twaren.net for iepm on Wed Dec 5 12:55:09 2007