12 messages in net.nether.puck.cisco-nsp[c-nsp] MTU Question on T1
FromSent OnAttachments
Richard J. SearsJan 24, 2005 12:33 pm 
Gert DoeringJan 24, 2005 12:54 pm 
Richard J. SearsJan 24, 2005 1:13 pm 
Gert DoeringJan 24, 2005 1:28 pm 
Joe MaimonJan 24, 2005 1:28 pm 
Jon LewisJan 24, 2005 1:39 pm 
Rodney DunnJan 24, 2005 2:39 pm 
Bill WichersJan 24, 2005 7:46 pm 
Richard J. SearsJan 24, 2005 8:15 pm 
Jon LewisJan 24, 2005 8:18 pm 
Jay HenniganJan 24, 2005 8:27 pm 
Gert DoeringJan 25, 2005 3:08 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[c-nsp] MTU Question on T1Actions...
From:Jay Hennigan (ja@west.net)
Date:Jan 24, 2005 8:27:44 pm
List:net.nether.puck.cisco-nsp

On Mon, 24 Jan 2005, Richard J. Sears wrote:

Hi Bill -

I am sure that they are messing it up, but they have not identified that error as of yet, even with me explaining it to them.

All they say if to do a 40000 byte packet ping from a windows box to another windows box across the T1 and until that comes back below 50ms, don't bother them!!

In that case, until you can replenish the dilithium crystals, don't bother them. I've found the "40000 car freight train engine to caboose" analogy sometimes penetrates thicker skulls when trying to explain serialization delay.

And I still get transit provider telemarketers who don't understand propagation delay promising 40 ms RTT California to Europe.

-- Jay Hennigan - CCIE #7880 - Network Administration - jay at west.net WestNet: Connecting you to the planet. 805 884-6323 WB6RDV NetLojix Communications, Inc. - http://www.netlojix.com/