Traceroute is a network utility program to trace the path from one network to another. It displays response times that occur at each stop (hops) along the route. We can know if there is any connectivity issue or latency connecting to a target. The stops having issue can be identified by looking into the report generated by traceroute.
Command:
tracert hostname
hostname - Name of the destination server that is traced
Example:
Hop# - No. of hops that packets are traveled
RTT (Rount Trip Time) Columns - Time taken by packets to communicate with the host (both way). Three separate packets are sent. It helps to check consistency or a lack in the route.
Domain/IP Address - IP address of the router. Domain name is displayed if it's available
The data of RTT columns are important to check if there are faults in the route. Consistent times are the result of a good connectivity. There may be some hops with increased latency time but that could not be an issue. Patterns over the route, hops where the latency or timeouts (asterisks,* in RTT) occur are the elements that need to be investigated.
If the report shows high latency at the end, there could be issues with the destination servers.
If the report shows high latency at the beginning, there could be issues with the local network.
If the report shows high latency in the middle but not at beginning or end, that does not indicate an issue. It could be the router at long hop set the signal to lower priority.
Update:
There are some options available for trace route as well. Some of them are mentioned as below.
[-d] - Do not resolve IP addresses to hostnames, often making much faster results
[-h MaxHops] - Search max. number of hops for target. If we do not specify, it goes to 30 hops
[-w timeout] - Wait timeout in milliseconds for each reply
Option [-d]
Thank you.
Command:
tracert hostname
hostname - Name of the destination server that is traced
Example:
Reading the traceoute test results:
There are 6 rows. Each row represents a hop. Route can be traced up to maximum of 30 hops. There are 5 columns in each row.
Hop# - No. of hops that packets are traveled
RTT (Rount Trip Time) Columns - Time taken by packets to communicate with the host (both way). Three separate packets are sent. It helps to check consistency or a lack in the route.
Domain/IP Address - IP address of the router. Domain name is displayed if it's available
The data of RTT columns are important to check if there are faults in the route. Consistent times are the result of a good connectivity. There may be some hops with increased latency time but that could not be an issue. Patterns over the route, hops where the latency or timeouts (asterisks,* in RTT) occur are the elements that need to be investigated.
If the report shows high latency at the end, there could be issues with the destination servers.
If the report shows high latency at the beginning, there could be issues with the local network.
If the report shows high latency in the middle but not at beginning or end, that does not indicate an issue. It could be the router at long hop set the signal to lower priority.
Update:
There are some options available for trace route as well. Some of them are mentioned as below.
[-d] - Do not resolve IP addresses to hostnames, often making much faster results
[-h MaxHops] - Search max. number of hops for target. If we do not specify, it goes to 30 hops
[-w timeout] - Wait timeout in milliseconds for each reply
Option [-d]
Thank you.
Comments
Post a Comment