There's really no specific problem here. You always *first* look at the final destination, looking for problem. If you find something there, then you look "upstream" (earlier hops) to find out where that problem starts.
In your case, the final destination looks good. There was a single high latency packet, but that's not statistically enough to know how often that happens. Based on what I see here, I don't think there's any problem that needs to be addressed.
For more details, see these knowledge base articles:
http://www.nessoft.com/kb/47http://www.nessoft.com/kb/24- Pete
Previous Topic
Index
