Re: 30 second delay before ping command will succeed
- From: "David Schwartz" <davids@xxxxxxxxxxxxx>
- Date: 28 Dec 2006 13:05:32 -0800
airish@xxxxxxxxxx wrote:
In a site-specific networking environment (other sites do not
experience this problem), we consistently observe a 30 second delay
from the time the networking cable is plugged into the system and the
time that the ICMP ping command will succeed.
Requests to ping the server within this 30 second period from initial
network connection will timeout.
It is an important feature of our application to dynamically
connect/disconnect from various networks.
Does anyone have any ideas on how to troubeshoot/eliminate this 30
second delay?
Thanks in advance for your thoughts on this issue.
Imagine if that delay didn't exist. Imagine further that some idiot
connected switch A to switch B with two cables. Now imagine a broadcast
packet being sent over and over between switch A and B and out all live
ports on both switches. Boom. Your network is now useless.
Now, imagine if there's a brief delay after the cable is connected. The
switch sends some probe packets but no live traffic. If it gets its
probe packets back on another port, it knows there is a loop and can
deactivate the port.
Waiting 30 seconds for loop detection is essential in any situation
where a loop is possible.
Your switch may or may not make this optional, but think long and hard
before you shut it off.
DS
.
- References:
- 30 second delay before ping command will succeed
- From: airish
- 30 second delay before ping command will succeed
- Prev by Date: Re: Problem in Networking at Kernel Level
- Next by Date: Re: ProFTPD Passive Transfers - Inexplicable Wierdness
- Previous by thread: 30 second delay before ping command will succeed
- Next by thread: Re: 30 second delay before ping command will succeed
- Index(es):
Relevant Pages
|
Loading