Something I've seen a few times -- for whatever reason, we have a radio that's only negotiating at 10M-Full or is flapping up and down. You can reboot the device and it makes no difference. Reboot the switch and it makes no difference.
However, on several occasions I've upgraded the switch from something like 1.4.7 to 1.5.0 and the port has now negotiated solid at 100-Full without any issues. My understanding was the chip firmware was burned in the ROM so there woudn't be any changes to, say, the algorithm for how a port negotiates with a radio.
Is this incorrect? What other thing might cause a port to start negotiating properly after a firmware update but not from just a restart? Does a firmware update perform some kind of a deeper level restart on the switch?
Port Negotiation
-
Dave - Employee
- Posts: 726
- Joined: Tue Apr 08, 2014 6:28 pm
- Has thanked: 1 time
- Been thanked: 158 times
Re: Port Negotiation
Matt
Yup, a firmware reset reloads/reset all network based stuff.
Dave
Yup, a firmware reset reloads/reset all network based stuff.
Dave
-
sirhc - Employee
- Posts: 7416
- Joined: Tue Apr 08, 2014 3:48 pm
- Location: Lancaster, PA
- Has thanked: 1608 times
- Been thanked: 1325 times
Re: Port Negotiation
OK so Dave is correct and Matt is correct.
With the WS line which was a mature product (switch core) when we started so there has been no code updates from SOC / Switch core manufacturer. Or at least none that we implemented as the releases covered things we are not using the core for.
Unlike the WS2 and WS3 line which are not released yet they are built on NEW chips so there has been patches from SOC / switch core manufacturer as far as driver and core function routines. THe core code for the WS2 and WS3 line has been updated from VITESSE several times and we have not even released the product yet. When we started the WS2/3 line there was code release it seemed every other week not it has slowed down as the chips have now been on the market over a year.
When you have a bad or marginal ethernet connection every time you renegotiate the connection it is like rolling a dice. The link will try and establish at highest speed but if errors are too great it modules down.
So in this case Matt with the WS line it is just happen stance on a marginal connection.
I would say these are your things to check:
Ethernet port in switch could be damaged - try different port in switch
Ethernet port in device is damaged swap device
Or cable and or Ends - Sometimes simply unplugging the connection and replugging it back in will fix it.
In the past 2 month I had tower guy climb and do just that, unplug, and re-plug in a cable to fix this very issue where a link was not staying at 100M or 1G. When temperatures change from cold to warm frequently the contraction and expansion will work lose a connection.
Always check lower connections first as you tower guy may be upset if the connection that need to be re-seated ended up being at ground level.
With the WS line which was a mature product (switch core) when we started so there has been no code updates from SOC / Switch core manufacturer. Or at least none that we implemented as the releases covered things we are not using the core for.
Unlike the WS2 and WS3 line which are not released yet they are built on NEW chips so there has been patches from SOC / switch core manufacturer as far as driver and core function routines. THe core code for the WS2 and WS3 line has been updated from VITESSE several times and we have not even released the product yet. When we started the WS2/3 line there was code release it seemed every other week not it has slowed down as the chips have now been on the market over a year.
When you have a bad or marginal ethernet connection every time you renegotiate the connection it is like rolling a dice. The link will try and establish at highest speed but if errors are too great it modules down.
So in this case Matt with the WS line it is just happen stance on a marginal connection.
I would say these are your things to check:
Ethernet port in switch could be damaged - try different port in switch
Ethernet port in device is damaged swap device
Or cable and or Ends - Sometimes simply unplugging the connection and replugging it back in will fix it.
In the past 2 month I had tower guy climb and do just that, unplug, and re-plug in a cable to fix this very issue where a link was not staying at 100M or 1G. When temperatures change from cold to warm frequently the contraction and expansion will work lose a connection.
Always check lower connections first as you tower guy may be upset if the connection that need to be re-seated ended up being at ground level.
Support is handled on the Forums not in Emails and PMs.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
Before you ask a question use the Search function to see it has been answered before.
To do an Advanced Search click the magnifying glass in the Search Box.
To upload pictures click the Upload attachment link below the BLUE SUBMIT BUTTON.
-
mhoppes - Associate
- Posts: 664
- Joined: Thu Apr 10, 2014 9:14 pm
- Location: Pennsylvania
- Has thanked: 10 times
- Been thanked: 125 times
Re: Port Negotiation
Yup... we're guessing it's cold related/ice related. I just wanted to double check on how things worked. Thanks!
4 posts
Page 1 of 1
Who is online
Users browsing this forum: No registered users and 61 guests