03-01-2015 11:55 AM - edited 03-07-2019 10:53 PM
Hi Guys,
Can someone tell me what the commands speed nonegotiate do in the TenG interface of the 4500x-32? If I enable this and I connect a host or device with settings of 1000/full duplex (manually configured), will I not run into issues with mismatch speed/duplex in the future?
interface TenGigabitEthernet1/9
speed nonegotiate
03-01-2015 12:41 PM
Hi,
You should not run to any issue as the ports are 1/10gig.
If you encounter any issue with the server being 1000/full, you can set the port on the 4500 to speed 1000 as well.
HTH
03-01-2015 02:15 PM
Hi Reza,
Thanks for the quick response. However, my problem is I cannot seem to find a command in the 4500X to set the speed and duplex to 1000/full. I am running this OS version.
Version 03.03.02.SG RELEASE SOFTWARE (fc1)
03-01-2015 03:32 PM
Hi,
You are correct. I just checked. There is no command on the 4500x to set the speed. You actually don't need the command. When you put a 1Gig SFP it will recognize the port as 1000 and when you put a SFP+ it will recognize it as 10000. You can verify that with:
"sh inter te1/0/0 capa" command.
BTW, all ports under show run or sh ip int bri show as 10G
HTH
03-03-2015 06:06 AM
Thanks Reza
@Joseph, could you please elaborate why I should not be hard coding duplex and speed on Gig interface?
03-03-2015 05:59 PM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
(At least for copper), auto-negotiation is part of the gig standard (and it's actually supposed to work [correctly]). (NB: I believe part of copper gig error detection also depends on auto negotiation.
03-20-2015 06:48 AM
Thanks Joseph
03-02-2015 04:54 AM
Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
BTW, for gig, you shouldn't be hard coding speed or duplex settings.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide