*) CRS317: fixed links not coming up after power failure;
*) CRS317: added extra information about FAN & PSU health;
*) CRS317: fixed load balancing over aggregated links;
*) CRS317: increased per port queue size;
*) CRS328-24P-4S+: make FAN work;
*) CRS328-24P-4S+: added extra information about health;
*) CRS328-24P-4S+: do not power cycle PoE outputs on reboot;
*) CRS328-24P-4S+: added voltage-level setting;
*) CRS328-24P-4S+: make SFP3 port work;
*) CRS328-24P-4S+: expose PoE port status via SNMP;
*) CRS328-4C-20S-4S+: make FAN work;
*) CRS328-4C-20S-4S+: added extra information about health;
*) CSS106: expose PoE port status via SNMP;
*) CSS106: always strip VLAN header on ports with disabled VLAN mode;
*) CSS106: make access to SwOS work over VLAN 1, put vlan header in replies;
*) CSS106: do not vlan tag RSTP BPDU packets, makes RSTP work with RouterOS;
*) CSS106: forward IGMP query messages even when IGMP snooping is disabled;
*) make PPPoE & DHCP snooping work on CRS326 & CRS328;
*) CRS326 & CRS328: make removed ACL rule stop working;
*) CRS326 & CRS328: learn MAC addresses even redirecting packets from ACL;
*) CRS326 & CRS328 & CRS317: added strict VLAN mode;
*) if “Allow From VLAN” is specified, make discovery packets use it;
*) make DHCP client work with RFC non compliant DHCP servers;
*) do not allow to create multiple VLANs with the same id;
*) provide health information (temperature, fan speed, psu state) via SNMP;
*) provide SFP port healt information via SNMP;
*) use 64bit counters under Stats tab for byte accounting;
Are you sure? I did take the time to do a manual update on my CSS106-5G-1S. Prior to the upgrade, I started a continuous ping to the switch from this PC. After starting the upgrade, i missed exactly one ping and the only indication was the top section of the page now says:
Current Installed Version 2.8 (built at Fri Jul 13 2018 04:37:01 GMT-0700 (Pacific Daylight Time))
Latest Available Version 2.7 (built at Fri Dec 15 2017 00:42:48 GMT-0800 (Pacific Standard Time))
CSS326-24G-2S+ v 2.7 doesn’t see the upgrade on the upgrade page.
After upgrading manually from 2.7 to 2.8 the switch boots into 2.0p - from that version I can upgrade manually to 2.8 …
I had a mixed result. One switch mirrored your experience, and the other went from 2.7 to 2.8 without the intermediate 2.0p version. I had to upgrade both manually.
Does anyone else run SwOS v2.8 on a CSS326-24G, monitoring with Observium?
I see a line in the changelog that says “provide SFP port healt information via SNMP” - should I expect DOM (tx/rx power) to be made available via SNMP as a result of this?
Suggestion. If you are going to ask a question that is totally unrelated to the current topic, start a new post rather than ask in an unrelated thread. For one thing it makes finding the question and answer far easier when the subject relates to the question.
Also, switch was configured for “static” for the management IP but after upgrade came back as “DHCP with fallback” - which resulted in an address change. Took me a while to find the switch. Easily set back to static but if I had more than 1 of these these I’d be irritated by this.
Hello,
We are investigating your reported issues about missing information in CRS328-24P-4S+ SFP and PoE menus.
Meanwhile, you can load primary SwOS v2.7p from Serial Console in the same way as on CRS326-24G-2S+ https://wiki.mikrotik.com/wiki/SwOS/CSS326#Reset_and_Reinstall
on my CSS326-24G-2S+ manual upgrade dont works.
switch not accessible(web) after manual upgrade.
to access the switch again, i had to boot backup SwOS.
i tried upgrade from backup SwOS(2.0p) to 2.8, and reset configuration - but no success.
