RE: Output Drops on Interface

Pavel,

BTW, your postings are nice.

> I had an ECN in the network for over a year, and NOT ONE
> SINGLE PACKET was ever ECN Capable, although billions were dropped
> by WRED
> across many routers.

It's probably not the router(s)' fault.

The TCP applications winging the routers need to first indicate that
they're ECN capable, before ECN marking takes place (rfc3168).

Code writer, switch on the ECT bit pleez :-)

-
Daniel

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
Pavel Bykov
Sent: Dienstag, 7. April 2009 22:52
To: `yc `lepi
Cc: Mark Stephanus Chandra; ccielab_at_groupstudy.com
Subject: Re: Output Drops on Interface

eshedalonie, It is not a router but an L3 switch, so there is no fully
functional WRED, and it all depends on a linecard installed.
"show port capabilities" would reveal more information.

ECN is not present on the platform in question.

Furthermore, ECN is pointless. It was an interesting experiment, and it
stayed that way. I had an ECN in the network for over a year, and NOT ONE
SINGLE PACKET was ever ECN Capable, although billions were dropped by WRED
across many routers.

2009/4/7 WW)W WWWW W <eshedalonie_at_gmail.com>

> I Would use in such case QOS - WRED + ECN
> To give buffer and avoid tail drop packets.
> and also notify the tcp applications to slow down.
>
>
>
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t8/feature/guide/ftwrdecn.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

--
Pavel Bykov
----------------
Don't forget to help stopping the braindumps, use of which reduces value of
your certifications. Sign the petition at http://www.stopbraindumps.com/
Blogs and organic groups at http://www.ccie.net