There are reasons why you don't set it to "auto". Working in a post production facility back then has taught me that some of the issues with final cut pro dropping frames when dumping to a raid storage can be caused by one side "downgrading" to 100 from 1000 and that would cause some grief. I usually set it to 1000 forced and if it drops, it drops. This holds especially true when you are dealing with video streams.
Mark On 22-May-2010, at 2:34 AM, Jason Gurtz wrote: >> It's more a matter of personal annoyance at network admins that refuse >> to acknowledge that devices change and problems evolve, and insist that >> "the rules that we have learned last century are cast in stone and must >> be followed to the end". The auto-neg/no auto-neg discussion is very >> prototypical for that :-) > > I've no idea how the CCIE re-cert process goes, but it would be great if > they added something to that process to wake up the elderly CCIEs out > there to this issue. > > We have one that comes here from time to time on a contractual basis and > I'm always setting things back to auto after he leaves. Unfortunately, > he's bringing up the CCNPs in his Co. to do the same thing :( > > I have to admit to half-believing this same idea 'till I read a post and > comments on Greg Ferro's blog: > http://etherealmind.com/network-dictionary-mythinformation/ > > Lately he followed up with details: > http://etherealmind.com/ethernet-autonegotiation-works-why-how-standard-sh > ould-be-set/ > > There *is* some stuff around here that doesn't auto-neg properly--100% old > scada-related gear. > > ~JasonG > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/