Netonix Forums

I upgraded from 1.3.8 to 1.4.6 on a ws-12-250-ac switch and port 14 that has a Mikrotik S-RJ01 SFP in it has become unstable.

I did the upgrade at 2am and by 5am I had over 300 emails about the LAG resetting. When I checked the switch log file it showed it was because port 14 kept having a link state change.

I have removed the LAG and even disabled the port on the switch and the corresponding port on the router and still the switch log shows

Code: Select all

Jan 22 05:35:55 UI: Log cleared by admin
Jan 22 05:36:52 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:36:52 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:37:02 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:37:02 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:39:12 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:39:12 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:39:22 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:39:22 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:41:42 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:41:42 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:44:22 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:44:22 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:44:32 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:44:32 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:44:42 Port: link state changed to 'up' (1G) on port 14
Jan 22 05:44:42 Port: link state changed to 'up' (1G) on port 14

It had been stable for over a week (when I installed the SFP) on 1.3.8. Is the SFP not compatible?

I am also after the firmware upgrade getting a significant amount of TX Drops on all active Ethernet ports. Never got any before the upgrade.

if you have issues with SFP modules you may need to change the speed/duplex settings on the SFP port as that was added in later firmware to help support more SFP makes.

You may also need to pull and re-insert the SFP module.

I tried both Auto and forced 1G on the SFP port and it made no difference.

I ran out to the tower and removed the SFP. I did not have time to do more as I had to get somewhere else.

After removing the sfp I got this message in the switch.

Code: Select all

Jan 22 08:50:02 SFP: SFP module removed, canceling I2C recovery

Also it has been over a half hour and the TX errors on the other ports seems to have ceased.

Also this was a brand new SFP and in 1.4.5 support was officially added for this module.

Is it common to need to reseat the SFP after a fw upgrade?

No Seth that is not common obviously.

Could be a bad SFP, could be a hiccup

Remember if you set the SFP to 1G or Auto you need to make sure the device on the other end of that cable is also set to 1G or Auto as they must match.

Sometimes when changing speed/duplex on an SFP module you do need to re-seat it but this is not us it is the SFP module that need reinitialized.

Yes I did remember to force it on the router side as well. I am certain the module did not go bad at the exact time as the FW update.

Either my module is not compatible with 1.4.6 but is with 1.3.8 or it needs to be reseated (as you suggested).

I will try placing it in the switch again when I am in the office Monday as the tower is only a couple of blocks away.

When I say it is bad I have found SFP modules that anytime I rebooted the switch (not a power cycle) such as from a firmware upgrade I had to reseat them. I removed them from service replacing them with and identical module and I had joy.

So yes modules can be or go bad in a way they act this way.

I have also come across some brands that always act this way and I used them elsewhere or got rid of them.

Would a reboot of the switch from the GUI accomplish the same thing as unplugging the switch when it comes to resetting the SFP port? Just trying to know whether after a FW upgrade I have to plan to go out and reseat the SFP or just perform a reboot from the GUI.

Also, I do not have any issue with these SFPs in my Mikrotik switches or routers. Not saying that the Netonix is the issue, but I also don't think the SFP is "bad". It is just not 100% compatible with the Wisp Switch.

Yes and I can probably find many SFP brands that do not work properly in MT gear.

There is compatibility issues with SFP modules and devices.

I have SFP modules that do not work in Cisco and or UBNT gear but work fine in my gear.

It all has to do with rather or not the vendor stuck to the standards.

Usually no, a warm reboot will not fix it as it does not power cycle the SFP module which is what is needed. Pulling and inserting resets the modules.

Most of the known issues with our switch and SFP modules has been with MT modules.

You're just going to have to experiment and find modules that give you no issues.

We also do not provide a list of modules that we guarantee work because I have found same model SFP modules that when you tear them apart have differnt chipsets in them. This happens less with more expensive modules but cheap OEM Chinese Modules are known to do this a lot.