For a long time i have religously hardcoded speed and duplex on all my switch to switch and switch to server connections. However, I have read some info on the Sun site that seems to suggest the is way of working is outdated and that Network technologies are mature enough now to allow the network admin to configure auto\auto. They even suggest that in some instances hard coding speed and duplex can cause the incorrect detection of downed interfaces causing problems with STP.
What do you think?
Shold we start trusting auto negotiation??
Does anyone have any documentation from Cisco that recommends either method?
ASFAIK that manual config of 100 Mbps @ full duplex do not interact properaly with interfaces configd with auto.This is because as per RFC standard both interfces recuire to send auto-negoatiation parameters for link only when both ends are confgd for auto-neg.If one end is hard coded then there will b duplex mismatch resulting errors and resulting switch interface to operate in half duplex.
As cisco recomondes always manually confgd 10/100-Mbps fastethernet & 10/100/1000Mbps gig ethernet on both link ends for critical connections to servers or 3rd party equipment.
Use auto-neg for interconnecting cisco devices and user workstations.
My experience has been with current gen equipment, there's often less issues with auto working correctly vs. someone forgeting to properly configure both sides of the connection expecially when for some reason they connect to a different port (like when dealing with a hardware failure).
I think you will see very few problems between cisco devices leaving them as auto . And unless you run into a specfic problem I wouldn't hardcode them . We run into very few problems for speed/duplex anymore and when it is it is usually because the "server guys decided to hardcode the speed /duplex because they fail to understand the implications of hardcoding . They think if they hardcode the server the switch will automatically adjust itself to 100/full and we all know that isn't true it will default to 100/half.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...