[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

8.8

Cannot send large ping packets without them timing out.  Intermittant, but very consistant. Ping -t xxx.xxx.xxx.xxx -l 17000 request timed out

Asked by captclam in Miscellaneous Networking, Internet Control Message Protocol (ICMP)

Tags: Request timed out ICMP echo failures ping payload size

I cannot seem to ping servers or workstations on my network with a packet size that exceeds anything greater than 20000.  Some can go higher than others, and it is not at all consistent.  If for instance I use a payload size of 9000, and ping for 10 minutes 80% of the packets go through.  If I increase it to 15000, the it goes down to (say) 20% and if I crank it up to 65000 it never goes through.  

Even if I stay on the same network segment I cannot go much higher than 30000.  If I try to ping my gateway, it has an exact limit size of 17900.  I don't know if that is the max a Cisco router will repond to by design or what the deal is there.  I am connecting my core server farm switches together via bridge group virtual interfaces, could that have anything to do with it?

I see no interface errors, bandwidth or queue length problems on any of my routers.  I see no duplex mismatch problems on the switches.  I have tried from numerous stations and get the same thing.  I have tried disabling and enabling checksum offloading, updating drivers and forcing duplex and speed on all test stations.

I could really use some help on this one.  My wireshark packet captures look pretty much fine, with the expection of occasional big delays (770ms) during a conversation, and packets arriving out of order that are fixed with SACK.  No window sizing clamping down to near nothing- nothing that would indicate a massive problem.  The only symption is users complaining about long lag periods in their apps.

See example here:

C:\Users\BertnErnie>ping 10.102.1.31 -t -l 19000

Pinging 10.102.1.31 with 19000 bytes of data:
Request timed out.
Request timed out.
Reply from 10.102.1.31: bytes=19000 time=7ms TTL=127
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.102.1.31: bytes=19000 time=8ms TTL=127
Request timed out.
Request timed out.
Request timed out.
Reply from 10.102.1.31: bytes=19000 time=9ms TTL=127
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 10.102.1.31:
    Packets: Sent = 31, Received = 3, Lost = 28 (90% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 9ms, Average = 8ms

It doesn't make any difference if I extend the timeout period.

Can someone please help me understand why this is happening?  I have verified all router interfaces between segments
[+][-]02/04/09 04:08 PM, ID: 23555243Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]02/05/09 06:12 AM, ID: 23559387Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02/16/09 04:13 PM, ID: 23655280Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]02/16/09 04:26 PM, ID: 23655382Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]02/16/09 05:59 PM, ID: 23655803Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02/16/09 06:07 PM, ID: 23655838Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02/16/09 10:38 PM, ID: 23656774Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]02/17/09 05:02 AM, ID: 23658927Expert Comment

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]02/27/09 02:47 PM, ID: 23760311Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]02/27/09 06:05 PM, ID: 23761307Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zones: Miscellaneous Networking, Internet Control Message Protocol (ICMP)
Tags: Request timed out ICMP echo failures ping payload size
Sign Up Now!
Solution Provided By: giltjr
Participating Experts: 1
Solution Grade: B
 
 
Loading Advertisement...
20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20080625