MikroTik

@rpingar - We have included a bonding fix that should solve the previously reported non-complete ARP entries. However, ARP link monitoring is not recommended for the LACP mode due to transmit hash policy on the peer device (the ARPs for link monitoring might arrive only on one slave port). This beh...

Since RouterOS 6.47beta60 version we have included a fix, see the related changelog entry:
*) crs3xx - fixed hardware offloaded bonding on Ethernet interfaces for CRS354 devices

Since RouterOS 6.47beta60 version we have included a fix, see the related changelog entry:
*) crs3xx - fixed hardware offloaded bonding on Ethernet interfaces for CRS354 devices

You can monitor Ethernet statistics with MIKROTIK-MIB. For example, try to run the snmpwalk using this OID - 1.3.6.1.4.1.14988, the "rx-drop" should be on 1.3.6.1.4.1.14988.1.1.14.1.1.55.x OIDs. The rx-drop might appear when the interface is receiving more data than the resources of the device can p...

@Xymox, rpingar, anas94c - regarding the LACP, it does look like an ARP entry never gets completed when the ARP reply is received on a certain slave port. We will try to fix this in the coming RouterOS testing releases, thanks for sharing the details. In the meantime, you could try to change the bo...

The bridge firewall/NAT rules do require the main CPU to process the frames. Creating these rules will not disable HW-offloading, but they probably will not work correctly either as the frames are forwarded through the switch chip instead of the CPU. If you let some traffic to reach the CPU (e.g. ma...

Configuration wise, cannot see any issues on the CRS354 device. I would only recommend enabling RSTP or MSTP, but this should not affect the throughput if there is no active loop. But on the CRS326 device, don't the ingress and egress rate properties limit the throughput? Have you checked if there a...

Please describe in more detail how did you test the throughput on the switch - share some basic network diagram, the actual test results (as a screenshot or terminal output) and the CRS354 configuration export.

VLANs are configured using a bridge with HW-offloaded vlan-filtering:
https://wiki.mikrotik.com/wiki/Manual:I ... _Filtering

LACP is configured using bonding:
https://wiki.mikrotik.com/wiki/Manual:C ... es#Bonding

The SwOS currently is not available for CRS354 devices, it may become available in future by software updates. We have corrected all documentation regarding it and plan to hide non-working boot options to avoid confusion. As a workaround, you can still utilize every available switch feature using Ro...

It is hard to say any precise ETA, a new SwOS version usually gets released once or twice a year.

Thank you for sharing the details, we managed to observe the same issue locally and look forward to improving this on upcoming SwOS versions.

Unfortunately, the only possible workaround is to boot your device into RouterOS when using most of the SFP+ interfaces.

@Louis2 - unfortunately, we did not manage to repeat such reboot issues, please report this to support portal or email to support@mikrotik.com @chaigeo - the switch should not generate any pause frames when the Flow Control is disabled. We look forward to improving this on upcoming SwOS versions. @...

In order to start the "multicast-querier", it looks like igmp-snooping should be disabled/enabled, we will try to improve this behavior so that it starts to work automatically. A multicast-router port should be a port where a multicast router or other uplink IGMP Snooping bridges are connected. As I...

With the current settings, can you simply disable/enable the igmp-snooping on the bridge interface and see whether multicast table still timeouts? Make sure the "multicast-querier=yes" is used. Otherwise, please share your configuration and explain which bridge ports are used for multicast transmitt...

It could be that the multicast group entry has timed out, by default membership-interval on the bridge is 4m20s. When you want to correctly forward multicast traffic on a LAN network, there must be some IGMP querier who periodically sends IGMP query messages to keep the multicast databases up to dat...

Yes, the SwOS configuration will be untouched.
Anyways, it is recommended to keep a configuration backup if something does go wrong.

@dg1kwa - please keep this forum topic strictly related to this particular RouterOS release. MDB entries do timeout after a while if no membership reports are received, see "membership-interval" property. Make sure you have some device that acts as an IGMP querier. Otherwise, create a new forum thr...

Unforunately, no. Only CRS3xx series switches and RB250/260/CSS106 devices support SwOS:
https://wiki.mikrotik.com/wiki/SwOS

Thanks @schadom, @R1st0.
We will try to fix SNMP reporting for combo interfaces in the next RouterOS version.

In the latest beta version, we included fixes regarding neighbor discovery, STP and active-backup bonding. If the packet loss is periodic (every minute) and you have some backup/alternate STP paths, try to disable the neighbor discovery on these devices or try out the beta version. What's new in 6.4...

@angriukas - this most likely is not related to switch hangs @gotsprings - you can report the issue to our support portal or emailing to support@mikrotik.com When the switch hangs, it tends to forward only small frames (from 64 bytes to around 200 bytes). To verify that you experienced the same iss...

Thanks to everyone for sharing the details! We are working on the issue, but because of the rare appearance, it gets extremely difficult to reproduce the problem. It might be related to Flow Control or switch congestion controls. For now, try to disable the Flow Control for all interfaces under the ...

@gotsprings - if the issue seems only related to SwOS and there are no cable/module issue, please report this on https://help.mikrotik.com/servicedesk/ or send an email to support@mikrotik.com

Have you enabled the "Independent VLAN Lookup" under the System menu? Have you changed any other default settings apart from VLAN related (e.g. port isolation or LAG)?
See whether disabling RSTP on the management port helps.

I guess you are using the CRS328-24P-4S+ switch, are you using the latest SwOS version?

The reported problem on the first post is only related to CRS3xx with HW-offloaded bond interfaces.

sid5632, I did not quite catch how did you repeat yours. Can you share some screenshots and provide "/interface export"?

Thank you for letting us know. This is a cosmetic issue in WinBox and we will fix it in further releases. If you run this command in CLI, you will see correct interface name:
/interface ethernet switch host print

archerious - from the description it is unclear why you do not see VLAN50 on the "Host" menu, it could be a misconfiguration and not the release issue. Have you enabled the "Independent VLAN Lookup" under the System menu? If this does not help, I would suggest reporting to support@mikrotik.com.

I would guess that CRS309 received a management IP address from the DHCP server. By default, SwOS will try to query an IP address for the first 10 seconds, so see if your DHCP server has assigned some address for the switch (you can change the settings to static address as well, see the manual ). Yo...

CRS312 device booted in SwOS by default supports jumbo frames up to 10218 bytes and you cannot change it to other values. It is the same for all CRS3xx devices booted in SwOS.

The cpu temperature (.1.3.6.1.4.1.14988.1.1.3.11.0) for CRS326-24G-2S+ stopped working with "object not found".

Thanks for sharing this, we will try to fix it in next RouterOS version.

Not really, mtxrInterfaceStatsLinkDowns is a counter that shows how many consecutive link downs the interface has (status changes from running to not running). The ifOperStatus shows the current operational state of the interface.

OID for mtxrInterfaceStatsLinkDowns - 1.3.6.1.4.1.14988.1.1.14.1.1.90

Only downstream interfaces send IGMP queries, the wiki article is updated. Thanks for sharing this.

You need to share some more specific information (e.g. detailed problem description, device configuration, network diagram, screenshots from the "IGMP" menu and preferably packet captures), so we can reproduce your issue locally and fix it. Otherwise, I cannot predict what exactly is not working.

We have included major IGMP Snooping improvements in SwOS 2.10 version. As kwinz already mentioned, if you still face some IGMP Snooping related problems, you should report this to support@mikrotik.com . A detailed problem description together with screenshots, network diagram and packet captures wo...

For CRS3xx and CSS326, the port lock will restrict MAC address learning (a static host addresses should be configured). You can allow the switch to learn the first frame it receives, this requires both options enabled. Learning of the first MAC address will reset every time an interface status chang...

SwOS only supports a partial MIKROTIK-MIB (for health, PoE-out and SFP diagnostics). To monitor interface status and some other counters, you should look for IF-MIB. Use snmpwalk to see exact OIDs.

From DHCP Snooping article : In RouterOS you can specify which bridge ports are trusted (where known DHCP server resides and DHCP messages should be forwarded). In other words, use trusted=yes on the port that is facing towards DHCP Server. If you are using multiple bridges with DHCP Snooping and Op...

@gard - we look forward to improve IGMP Snooping for CSS106 device on upcoming SwOS versions. @nfored - sending Pause frames are intended behavior for Flow Control. You can disable this under Link menu. For anyone who fails to upgrade the CSS106 to the latest version - try to load the backup firmwa...

@UpRunTech - thank you for sharing this. We managed to reproduce this locally and it will be fixed soon. Your reported issue was introduced since 6.45beta version, so the current long-term version is not affected.

@Tobei - thank you for sharing, this is the exact issue I was referring on my first post. Will be fixed in further v7 beta versions.
@jrpaz - not sure about your setup, can you share the full export

/export hide-sensitive

?

Yes, hardware VLAN switching works fine between bridged ports, however, tagged management access does not work correctly, should be fixed in further beta versions. Perhaps you managed to find out some other issues? Can you share a configuration export?

@n0xlf - we look forward to improve this on upcoming SwOS versions. @LeftyTs - what exactly happens when you try to install the new version (e.g. boots with old version, boots with backup version, does not boot at all)? Please try loading the backup firmware by pressing the reset button for a few s...

Thanks for the suggestion!
MTSP support in SwOS will not be implemented in the near future. SwOS is designed to be a simple management tool so that users can create basic networking setups. For more advanced configurations, you should stick with RouterOS.

Thank you for the provided details.
The switch does not forward the ICMP TTL exceeded and it appeared in SwOS 2.9 version. We look forward to fixing this in upcoming SwOS versions. As a workaround, you could try to use RouterOS instead.

Unfortunately, this is not possible through SwOS. In case you are using a dual-boot device (any CRS3xx series switch), you could easily set up scheduler in RouterOS.

Thank you for sharing!
Tried to repeat the behavior but to no avail. In case you did not manage to figure this out yet, I would suggest reporting to support@mikrotik.com.

Version 6.45beta62 has been released.
*) bridge - correctly handle bridge host table;
What kind of issue was there actually?

Under some occasions, hosts did not timed out correctly. Now bridge will make sure hosts are removed.

The Port Isolation menu can look confusion from the start, you almost need trial and error to wrap your head around.
However, some more description and examples are now added to Wiki. See if this manual looks better now.

I would recommend using RSTP instead as it is more commonly used, complies with other switch STP variants and gives you some configuration options.

These examples were created identical with RouterOS bridge examples, see Bridge Trunk and Access Ports . I believe we could add some note that you should use "strict" VLAN mode to enable ingress filtering and a link towards SwOS VLAN manual. In case you spot any manual error, I would appreciate that...

Regarding the fan fault-led, the SwOS v2.9 has few changes which require updated fan controller firmware that comes only within RouterOS. You should boot your CRS328-24P-4S+ in RouterOS and upgrade to the latest stable version (currently it is 6.44). Also, you can make a firmware update (/system rou...

SwOS v2.9 has few changes which require updated fan controller firmware that comes only within RouterOS. You should boot your CRS317-1G-16S+ in RouterOS and upgrade to the latest testing version (currently it is 6.44rc1, should be included in next stable version as well). After that, you can simply ...

There are some configuration differences between RB260 and CSS326. You should take a look at CSS326 manual page for VLAN configuration and here are two examples on how to create a basic VLAN configuration. In brief, use "Default VLAN ID" to strip specific VLAN header on egress port, while other VLAN...

You should be able to reset the SwOS for CRS326/CRS328/CRS317 devices in two ways: Connecting serial cable and choose "r - reset configuration". Wiki manual Or boot in RouterOS and reset with command /system swos reset-config. Available since RouterOS 6.43, Wiki manual The address 0.0.0.0 will appea...

Switch by default sends out periodic (every 2s) RSTP BPDU packets, you see these flashes probably due to this reason. You can try to disable RSTP at some 1Gbps port and see if flashing stops.

What "Default VLAN ID" have you set for ethernet and SFP interfaces and what is the RSTP State in the second setup?
Have you tried to disable RSTP on these ports?

The first part: Switch will treat both untagged and "Default VLAN ID" tagged ingress packets as they are tagged with this VLAN ID. This is meant for ingress traffic (PC --> switch). Received untagged packets will be assigned with "Default VLAN ID". It also states that received packets with already a...

The "Default VLAN ID" you can understand as a PVID (Port VLAN ID) that assign this specific VLAN to untagged ingress packets - the switch internally adds this VLAN to all incoming (untagged) PC packets. Then switch needs to decide where to forward this packet, only now comes the egress action (leave...

Since RouterOS 6.43rc29 it is possible to load, save and reset SwOS configuration, as well as upgrade SwOS and set an IP address for the switch by using RouterOS. You could try to reset SwOS configuration with a command: /system swos reset-config Also, try to upgrade SwOS to latest available version...

Have you tried these steps, info from Wiki - https://wiki.mikrotik.com/wiki/SwOS/CSS106#Reset The CSS106-5G-1S and CSS106-1G-4P-1S has built-in backup SwOS firmware which can be loaded in case standard firmware breaks or upgrade fails: Holding Reset button for few seconds while device is booting res...

We have found that there is a software issue with DHCP Snooping when you use VLAN for your access ports. When VLAN tags are not used, DHCP Snooping should work as expected. The fix will be included in following SwOS releases.

Search found 64 matches