NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MS510TXUP compatibility issue with Mikrotik RB5009UG+S+IN via SFP?
I think that my MS510TXUP is not compatible with MikroTik RB5009UG+S+IN when connected via SFP port.
The issue is this:
When I connect my RB5009UG+S+IN via any SFP connection cable I have to MS510TXUP, on RB5009UG side it looks like the connection is up but speed negotiation failed, but on MS510TXUP side the connection is only up for about a second then it is considered disconnected.
For detail, this is the log on MS510TXUP when I try to connect RB5009UG to it:
<181>1 2021-12-04T17:53:11.124-8:00Z 192.168.14.209-1 TRAPMGR-5-STP_NEW_ROOT ksi_snmp.c(484) %% This bridge has changed to be the root bridge. <182>1 2021-12-04T17:53:11.814-8:00Z 192.168.14.209-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4985) %% Neighbor deleted on port XGigabitEthernet10: Chassis ID 06:66:B1:C4:3C:49, Port ID brg1-lan/sfp-sfpplus1 <182>1 2021-12-04T17:53:10.654-8:00Z 192.168.14.209-1 STP-6-PORT_STATE proto_stp.c(835) %% Port XGigabitEthernet10 moving from Blocking to Disabled <181>1 2021-12-04T17:53:10.194-8:00Z 192.168.14.209-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface XGigabitEthernet10 link down <181>1 2021-12-04T17:53:10.144-8:00Z 192.168.14.209-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface XGigabitEthernet10 link down <181>1 2021-12-04T17:53:10.144-8:00Z 192.168.14.209-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface XGigabitEthernet10 link up <182>1 2021-12-04T17:53:10.144-8:00Z 192.168.14.209-1 STP-6-PORT_STATE proto_stp.c(835) %% Port XGigabitEthernet10 moving from Forwarding to Blocking <182>1 2021-12-04T17:53:09.614-8:00Z 192.168.14.209-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(5188) %% New neighbor on port XGigabitEthernet10: Chassis ID 06:66:B1:C4:3C:49, Port ID brg1-lan/sfp-sfpplus1 <182>1 2021-12-04T17:53:09.074-8:00Z 192.168.14.209-1 STP-6-PORT_STATE proto_stp.c(835) %% Port XGigabitEthernet10 moving from Blocking to Forwarding <182>1 2021-12-04T17:53:09.824-8:00Z 192.168.14.209-1 STP-6-PORT_STATE proto_stp.c(835) %% Port XGigabitEthernet10 moving from Disabled to Blocking <181>1 2021-12-04T17:53:09.784-8:00Z 192.168.14.209-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface XGigabitEthernet10 link up
As far as I can tell, there's no obvious reason mentioned as why it is disconnected, and apparantly it went up twice and shutdown twice while physically it is inserted only once and still is firmly sitting in the socket.
Following mitigation are tried but no success:
1) Update firmware to newest on both sides. 1.0.4.2 on MS510TXUP, 7.0.5/7.1rc5/rc6 on RB5009, all same issue.
2) Replaced cables. At least 5 different brands of confirmed working DAC are tried, all same issue; 1 confirmed working pair of 10GBASE-SR and 1 confirmed working pair of 10GBASE-LRM adapters are tried, both same issue.
3) Factory reset of both sides. Same issue with default configurations. (Of course with default configuration the log is simpler but I wasn't being able to find a copy.)
4) Canned air blasting to clean the ports on both sides, same issue.
Also why I think this is compatibility issue between RB5009UG and MS510TXUP:
1) The same configuration works fine when RB5009UG is connected to other switches, tested are Netgear M4200 and Netgear GC752X.
2) The same configuration works fine when MS510TXUP is connected to another router, Mikrotik RB4011iGS+RM, with same firmware and almost same configuration as RB5009UG.
(BTW, MS510TXUP is not in available options in "Model" field when editing this post)
24 Replies
Reads to me like STP is blocking the port virtually as the connection does come up.
<182>1 2021-12-04T17:53:10.144-8:00Z 192.168.14.209-1 STP-6-PORT_STATE proto_stp.c(835) %% Port XGigabitEthernet10 moving from Forwarding to Blocking
....some kind of loop in the network, the Spannng Tree Protocol - on either one or both sides - is blocking/shutting the port in the test set-up I'd suspect.
I can confirm this is not the case. Three reasons:
1) I do have RSTP enabled for the whole network.
2) When tried with factory reset environment, there's nothing else connected except this only one piece of link between the router and switch.
3) The shutdown of port is not reflected within STP status page of MS510TXUP. If I create a loop, it would show such in the status page on either side. This means the port gets disconnected somehow, then STP jumped in to mark the port disabled, just like I pulled the plug on the port.
Also I think the log with same timestamp can be out of order. And apparantly, at the exact timestamp of "2021-12-04T17:53:10.144-8:00Z" there's also a link up and link down event. All three cannot be happening at the same time if that's STP causing connection status change.
OK, makes sense.
The issue reminds me to some issue we've (nah, not Netgear) experienced on an SFP+ based network link on two security appliance/router brands, and I think the customer tried some Mikrotik with an SFP+ garage and a similar set of test switches as yours. One of the discoveries was that the router side flapped the links, and did not allow using short/passive DAC.
However, you have tried industry standard fiber modules and experienced the same.
I would suggest to file a support case with Netgear, convinced their switch engineering would be keen to look into this.
YeZ can you assist to establish a link to the switch engineering?
Please do let me know what I can help. At this moment, my newest discovery is this:
After MikroTik RB4011 upgraded to 7.1.1, the DAC cable connection is also broken. However it is slightly different - the connection is seen as up by both sides, but both sides are only transmitting packets while 100% of receiving packets are with error.
I am sure this is a compatibility issue more on software level, however this only happens with MS510TXUP. I've tried the same on my other switches, M4200 and GC752X, both working totally fine.
I've got an update. I can confirm that the issue mentioned in my yesterday's post is fixed after a few reboot on both side - I don't know which reboot fixed it, but I am sure that at least first reboot on both side did not fix the issue. And after reboot, I've tried to reboot both side a few times however I was not able to recreate the issue.
Generally speaking, I think my conclusion is there's some compatibility issue between MikroTik RouterOS 7 and MS510TXUP.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
