cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1304
Views
0
Helpful
4
Replies

min/avg/max = 999999999/858993458/4294967295 ms

pepsico_anz1
Level 1
Level 1

just for fun, explain this???!!!

HOCT-LG#ping 10.198.147.150

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.198.147.150, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 999999999/858993458/4294967295 ms

oh and it actually replied very quickly, like <10ms WTF?

HOCT-LG#ping 10.198.147.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.198.147.1, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms

4 Replies 4

glen.grant
VIP Alumni
VIP Alumni

We have seen issues like this in the past and its usually a code bug , would check there first for your code version.

thought it would be, just kinda insteresting how it affects some destinations but not others

Just tells me: you can do magic things with software (bugs) ;-)

john.cottingim
Level 1
Level 1

I know this is a very old thread. I was unable to find anyone that answered this elsewhere...

--

This not a software bug as others have suggested. The odd min/avg/max time is caused by the machine that's replying to the echo-request not complying to RFC792 https://tools.ietf.org/html/rfc792.

According to RFC792, "The data received in the echo message must be returned in the echo reply message."

In the case above, the host 10.198.147.150 does reply, but replies with the string: "abcdefghijklmnopqrstuvwabcdefghi" as the data instead of what the Cisco device sent. That string that was being echoed back is typically whats sent from a Windows machine as the data portion of the ICMP Echo-Request packet. However, Cisco does not send that specific string in its echo-request packets.

If you were to do an extended ping and validate the reply data, the Cisco device will show "CCCCC" instead of "!!!!!" indicating that the data received was not the data that was sent.

The odd timing displayed is Cisco's interpretation of the time-stamp that should have been in the reply packet, but was not.

I hope this helps!

Thanks

JC

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: