Overview
- Amount of time it takes for a token to complete one full trip.
- Shows the path the token took.
- Time is measured from when a source receives the token to when it receives it again.
- Average of all the token round trips for every master in the capture.
- Long average round-trip time shows problems that may be consistent every trip.
- Fails if Average Token Round-Trip time is more than 2000ms (2 seconds).
- Warning if Average Token Round-Trip time is more than 85ms (0.085 seconds).
Why it fails
- Problems with wiring.
- There may be a device offline.
- Token disruptions (caused by wiring or devices that are offline).
- Too many masters in the network using the token, holding onto token longer because they have more to say.
- Device(s) that are trying to talk too much.
How to fix it
- Check for token disruptions.
- If there are token disruptions, look for offline devices or check wiring.
- If no token disruptions, sort the drill down to find the device pair with the longest token passing time (sort using Mean (ms))
- Check the configuration of the devices with the longest time with the token.
- Check how busy the device is – it could be overwhelmed
Watch us troubleshoot average token round-trip time in this live troubleshooting webinar of a shopping mall site! Skip ahead to 2:54 for the average token round-trip time diagnostic check.
Comments
0 comments
Please sign in to leave a comment.