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 MS510T...
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?
Thank you schumaku.
Yes I've even tried Gigabyte SFP adapters and they don't work too. And only between RB5009 and MS510TXUP.
If there's anything else I can help provide, please do let me know.
I've just managed to create the factory reset environment again and did a minimal system test, and this is the logs I got:
<181>1 2021-01-01T00:04:16.040Z 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(120) %% Interface VLAN-MGMT link down <181>1 2021-01-01T00:04:16.030Z 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface XGigabitEthernet10 link down <181>1 2021-01-01T00:04:16.960Z 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface XGigabitEthernet10 link down <181>1 2021-01-01T00:04:16.960Z 192.168.0.239-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface XGigabitEthernet10 link up <182>1 2021-01-01T00:04:16.960Z 192.168.0.239-1 LLDP-6-NEIGHBOR_DEL proto_lldp.c(4985) %% Neighbor deleted on port XGigabitEthernet10: Chassis ID 2C:C8:1B:FF:AE:42, Port ID bridge/sfp-sfpplus1 <181>1 2021-01-01T00:04:16.950Z 192.168.0.239-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(132) %% Interface VLAN-MGMT link up <181>1 2021-01-01T00:04:16.750Z 192.168.0.239-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(120) %% Interface VLAN-MGMT link down <182>1 2021-01-01T00:04:15.980Z 192.168.0.239-1 LLDP-6-NEIGHBOR_DISCOVER proto_lldp.c(5188) %% New neighbor on port XGigabitEthernet10: Chassis ID 2C:C8:1B:FF:AE:42, Port ID bridge/sfp-sfpplus1 <181>1 2021-01-01T00:04:15.610Z 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface XGigabitEthernet10 link up <181>1 2021-01-01T00:04:14.600Z 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(132) %% Interface VLAN-MGMT link up <181>1 2021-01-01T00:04:14.600Z 0.0.0.0-1 TRAPMGR-5-PORT_LINK_DOWN rsd_l3_intf.c(120) %% Interface VLAN-MGMT link down <181>1 2021-01-01T00:04:14.600Z 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP rsd_l3_intf.c(132) %% Interface VLAN-MGMT link up <181>1 2021-01-01T00:04:14.590Z 0.0.0.0-1 TRAPMGR-5-PORT_LINK_DOWN ksi_snmp.c(230) %% Interface XGigabitEthernet10 link down <181>1 2021-01-01T00:04:14.590Z 0.0.0.0-1 TRAPMGR-5-PORT_LINK_UP ksi_snmp.c(232) %% Interface XGigabitEthernet10 link up
This is from two times I tried to cycle the port on RB5009. It might be hard to see, that the first time (at 2021-01-01T00:04:14.590Z) the switch did not even consider the link is up and directly considered the link to be down. And the second time (at 2021-01-01T00:04:15.610Z) the link was up for a very short moment and again, two link down happened.
Above log is captured with Debug level and not skipping anything, just so it might help with debug. I have the full log available if needed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
