Re: [OT]Creating a unidirectional link failure scenario

Hard coding is a sure way to cause extra work troubleshooting in the future.

Sent from handheld

On Apr 7, 2012, at 7:38 AM, "Radioactive Frog" <pbhatkoti_at_gmail.com> wrote:

> Sundeep - Try duplex and speed setting to "AUTO" on both side.
> Most algorithms on newer device/code are written to detect UDLD. In fact I
> was in CiscoLive this year and folks recommend to turn AUTO setting for
> fiber port.
>
> "Auto" does do some magic (compared to hard coding). I still see a lot of
> old administrator telling me to do manual. Why would one do it manual if
> sees no runt, fcs erros and late collisions?
>
> Thats, beside the point but;
>
> You may have to read this nice paper written ( a bit old but still helpful,
> written way back in 2004).
> Most people think - Coding duplex and speed manually is the "ANSWER" to
> everything.
> That is not entirely true :)
>
> http://www.sun.com/blueprints/0704/817-7526.pdf
>
> HTH
> frog
>
> On Fri, Apr 6, 2012 at 12:37 AM, sundeep sadhwani <
> sundeep.sadhwani_at_gmail.com> wrote:
>
>> I am probably thinkin of goin with bfd.
>> On Apr 5, 2012 10:33 PM, "Narbik Kocharians" <narbikk_at_gmail.com> wrote:
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sat Apr 07 2012 - 14:28:41 ART