Beginning to integrate some of the 3560 gigabit switches in our infrastructure and have a question concerning speed/duplex. I know Cisco had always recommended hard coding speed/duplex vice auto on the earlier switches, but I thought I had heard that with the newer gigabit switches that Auto worked well with gigabit nics. Can anybody shed some light on this subject. Thanks Jr.
I agree with Jon. As long as the clients (End stations or Servers), have the nic cards configured for auto negotiation mode, they will jel along real well with Cisco switch Gig ports which also are configured for auto negotiation mode.
Thanks guys, I found a Cisco doc yesterday which was a link from your doc KC, which recommends using auto vice hard coding. Looking to reduce some issues we have when our desktop people put out new pc's and not letting me know they put out a pc until I see a port throwing errors.
With modern equipment, auto usually works as expected, so current recommendations appear to suggest its usage.
Older equipment, especially 10 Mbps ports, either didn't support auto or it didn't always work. This led, I think, to a lot of the history of avoiding it, especially for network to network device connections. Also, some network device ports were "late" in providing the feature compared to host systems.
On these forums, the general consensus, whether to use it or not, appears to be, yes for client hosts, usually yes for server hosts, but divided opinion between network devices. One argument for its continued usage between network devices is a link comes up just a little faster when hard coded.
Personally, I prefer auto everywhere unless I have a situation where I know it doesn't work correctly. This both to avoid the management hassle of some ports configured for hard settings and other auto, and to avoid people "forgetting" to reset port settings correctly when there is some type of device failure recovery where ports are repatched.
In the last several years, when I often run down extremely poor performance, it's often a duplex mis-match caused by one side being hard coded and the other auto.
Yes Joseph, I agree with you. The new Cisco switches using 1Gb seems to be able to take advantage of the auto setting better than some of the older switches. Our network staff, myself included, have been tossing this around since we are in the process of a complete infrastructure upgrade to get ready for VOIP. My experience when there is a performance issue is to look at the switch port to see if there are any CRC's or collisions, which usually indicate a speed/duplex mismatch. Like I said our desktop staff doesn't totally understand this issue even though we have discussed setting up pc's, printers, etc correctly. As for connectivity between network devices, I am using trunks and if I am correct they default to auto, thus they connect at the 1Gb. We will be going with 10Gb with our new equipment to connect VM servers and our edge switches for increased throughput.
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 ...