Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Continuous ping

Hi Guys,

Is it normal to have the odd timeouts when doing a continous ping from my home to a public ip across the internet or is this a problem?

Any help will be greatly apprecited.

Thanks,

Lake

2 ACCEPTED SOLUTIONS

Accepted Solutions
Cisco Employee

Continuous ping

Hello,

It is better next time to paste the utput you see for us to clearly see the problem. Do you sing pings missed or RTT very high?

Nik

Cisco Employee

Continuous ping

Some pings being dropped - not the best sign - though ping might not be actually droppec-  but delayed.

I mean that by default ping is using default Wait timeout for a ping response before declaring it as missed. So you can change that timeout to a higher value (-w on Windows or use context help of your ping command as it may be different depending on OS) and see if pings really missed or just arriving later.

If they missed - smth happening on the path. Again - that can be normal if provider is rate-limiting your channel to specific rate or a sign of bad link/HW.

There can be really many apsects of that - and detailed analysis needed even to say if that is fine or a problem.

Nik

5 REPLIES
Cisco Employee

Continuous ping

Hello,

It is better next time to paste the utput you see for us to clearly see the problem. Do you sing pings missed or RTT very high?

Nik

Continuous ping

I mean ping missed. I have an output but there is no timeout here. The RTT looks good yet there are the odd missed ping.

Thanks,

Lake

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=29ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=29ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Cisco Employee

Continuous ping

Some pings being dropped - not the best sign - though ping might not be actually droppec-  but delayed.

I mean that by default ping is using default Wait timeout for a ping response before declaring it as missed. So you can change that timeout to a higher value (-w on Windows or use context help of your ping command as it may be different depending on OS) and see if pings really missed or just arriving later.

If they missed - smth happening on the path. Again - that can be normal if provider is rate-limiting your channel to specific rate or a sign of bad link/HW.

There can be really many apsects of that - and detailed analysis needed even to say if that is fine or a problem.

Nik

Continuous ping

Thanks guys.

Regards,

Lake

New Member

Re:Continuous ping

Test

529
Views
0
Helpful
5
Replies