I requested a beta fw and did not receive anything during the last 4 Months...Seems that the cause of this problem is clear now. ...
Have you been able to revive your switch? Is an upgrade to 2.9 possible?Will a power reset bring it back to life? Will need to visit a remote location.
Ditto!! I've been stuck in the mud for months now.CSS106-1G-4P-1S with 2.7 firmware out of the box.
Then proceeded to upgrade firmware via the web gui manually [swos-css106-2.9.bin]
Switch is no longer accessible via 192.168.88.1. Does not respond to arp.. It appears in Mikrotik neighbour discovery with firmware 2.7, its uptime started counting from 0 after the upgrade.
Will a power reset bring it back to life? Will need to visit a remote location.
Current Installed Version 2.9 (built at Mon Jan 07 2019 12:05:03 GMT+0100 (Central European Standard Time))
Latest Available Version 2.9 (built at Mon Jan 14 2019 07:49:36 GMT+0100 (Central European Standard Time))It's quite a simple procedure and takes 30 seconds. Still you should read carefully what has changed between your version and the new one, and if there are any known bugs that might be a problem to you in the new version.Can I update my switch or I need to phone for specialist???
how did you upgrade to ver 2.9? i can not find crs309 in download page?After upgrading CRS309-1G-8S+ to swos 2.9, the 192.168.88.1 can not be access any more
I had this same problem and wrote to support and got the answer to fix it. You have to switch back to router OS, install the latest routerOS version which updates the fan controller firmware, then switch back to switchOS and the fan oscillations will stop.Using SWOS 2.9 after a while, we often have a fan which constantly spins up and down, leading to an irritating noise.
Are there any options we can use to mitigate this? On routeros we don't have this issue (but I prefer the simple configuration on swos).
Device is the CRS328-24P-4S+
Did you have address acquisition in the system tab set to "DHCP with fallback" (think it might be default)? I noticed that after upgrading to 2.9 my switch pulled a DHCP address which prevented the 192.168.88.1 address to stop working. I would check if a lease was assigned to your switch as I was able to access it once I saw the ip it was assigned. The original default should have been set to "static" most likely as this setting now appears to properly work.CSS106-1G-4P-1S with 2.7 firmware out of the box.
Then proceeded to upgrade firmware via the web gui manually [swos-css106-2.9.bin]
Switch is no longer accessible via 192.168.88.1. Does not respond to arp.. It appears in Mikrotik neighbour discovery with firmware 2.7, its uptime started counting from 0 after the upgrade.
Will a power reset bring it back to life? Will need to visit a remote location.
Hi os62,I tried mr. D'Alessio's suggestion of downgrading to 2.8.
That, instead of improving matters, started to flap all ports on the switch.
So back to 2.9, and reboot-loss of 1000Base-T sfp modules on all power outages and reboots. Unfortunately.
I sure do hope this'll be fixed.
On the specifics of you issue, have you tried setting 1g full duplex manually on ubiquiti device?My new CRS312 shipped with 2.10 which does not work with 1G SFPs at all. I've been talking to support a bit with this being my latest reply (there is more conversation before about it not establishing a 1G link to my UBNT ERP):
I did more testing with the following and found the same results for all:
-10Gtek SFP+ DAC
-10Gtek 1G SFP MM fiber
-Cisco 1G SFP MM fiber
-UBNT 1G SFP MM fiber
-addon 10G SFP+ MM fiber
-Dell 1G SFP MM fiiber
-ipolex 1G SFP MM fiber
My Ubiquiti Edgerouter Pro will link to anything else I throw at, but even so I forced the port to 1000/full/no auto negotiation using ethtool.
The CRS312 will not link to anything at 1G with any of the above SFPs when it auto negotiation mode, and will always establish a simplex link when forced to 1G but obviously traffic only in one direction doesn't help me much.
As mentioned before, the CRS312 does link successfully at 10G with an EdgeSwitch, or at least it did until the SwOS version 2.10 (dated 09/03) came out. Now to even get that to link I have to reboot with it auto negotiating, force it to 1G, and then set it back to auto negotiation again. That will finally bring up the link. Additionally, all of the ports of the switch drop off entirely when I make any changes to the SFP ports.
This thread mentions at least some of what I'm dealing with: viewtopic.php?f=21&t=144031
I think the SwOS firmware is just a disaster at the moment when it comes to SFP slots. BTW, I tried RouterOS and it was no better.
I doubt there is much you or I can do until these issues evolve more, but I would ask if there is anything I can do to help the development of this firmware, please let me know.
What's new in v2.10:
*) do not ignore RSTP port state when forwarding DHCP, PPPoE or IGMP snooped packets;
*) IGMP snooping: send out IGMPv3 queries by default;
*) IGMP snooping: handle IGMPv3 leaves much better;
*) IGMP snooping: handle dropped IGMP reports much better;
*) CRS309, CRS312, CRS317, CRS326Q: fixed ACL matching by ip destination port;
*) CRS309, CRS312, CRS317, CRS326Q: fixed ICMP TTL packet switching;
*) CRS305, CSS106: make ACL work again;
*) CSS106: improve packet forwarding between different speed interfaces;
*) restart RSTP on LACP ports that got disbundled;
*) made disabling of flow-control work as expected;
*) do not account rx-overflows twice in SNMP ifInErrors;
*) CRS328-24P-4S+: make auto upgrade work;
*) CRS326Q: fixed vlan configuration on ports sfp22-sfp24 & qsfp+1.1-qsfp+2.4;
*) added support for unicode symbols in labels;
*) make DHCP & PPPoE snooping work correctly on port trunks;
*) made port lock filter out packets with unknown source addresses;
*) CRS309: make VLAN configuration work;
*) fixed problem where disabled autonegotiation on some SFP modules
became effective only after reboot;
*) CRS305, CRS326, CRS328: improved switch-chip resource allocation;
Dear Bruno,
Hi os62,
I'm sorry for the trouble downgrading the SwOS firmware in your switch.
Maybe the file you used was not the right one for your device? ...I don't know...
In every case my switch is the "CSS326-24G-2S+" and it is different from your model (CRS317-1G-16S+). Perhaps the behavior changes for this reason.
Just as a simple tip I wish to tell you that in the MikroTik download page:
https://mikrotik.com/download
I was not able to find the 2.8 version, so I solved by changing the link of the 2.9 version in the row of my device. The link is:
https://download.mikrotik.com/swos2/css ... 26-2.9.bin
and I changed it in:
https://download.mikrotik.com/swos2/css ... 26-2.8.bin
(the link works changing the "9" to "7" also).
Using the same rule, the 2.8 version for your switch should be
https://download.mikrotik.com/swos2/css ... 17-2.8.bin .
Did you use this link?
