I have a mikrotik router CCR1009-8G-1S-1S+ with 2 providers connected into it. It worked well for about half a year. Now I started to experience a strange issue, a link (ether5) from one provider started to go down for about a minute, next it is restored up again. See the screen shot for details
ether_down_str2.png
The provider claims that the problem is not at their end.
Can someone help me ?
Cable? Connectors?
jarda, patch cord with RJ45 connectors, everything checked, everything ok from physical point of view
I don’t know how much configuration is tied to ether5 in your router, but it might be helpful to try a different physical interface.
I’ve seen issues with switch-based gigabit interfaces on Mikrotik having issues connecting to certain hardware…
e.g.:
1100AH didn’t want to form a link with a Cisco 4500-series switch on any of its switched-ethernet ports, but had no trouble using ether12…
My 2011 wouldn’t connect to my cablemodem on ether1-5 but worked fine on the 10/100 ports…
2011 series had issues using gigabit ports talking to other gigabit devices at customers’ sites (don’t recall what devices, etc)
I’m not saying this is what’s affecting you, but it’s possible - it’s one of those things that I’ve never gotten to the bottom of, and so it lingers in my subconscious like a ghost in the dark - will it come out tonight?
I haven’t tried these with current RoS version so maybe that’s been fixed already (I no longer work with the company that has tons of 2011 routers deployed as CPE, so my only real-world router right now is the one at my house, and I’ve just been too lazy to try moving my config to ether1 for a test)
I have new information from my internet provider. They told me that most likely my network has a DHCP client which floods their network, that’s why a security mechanism restarts the switch’s port. The problem is : I can’t find the DHCP client. I have a quite small network and I have no idea which component of it can flood the provider’s network with DHCP packets.
Ok, I solved the problem. My mikrotik is working as DNS server, but because of miss-configuration it was open to the public internet. A lot of people started to use it, it received thousands of requests per second, the switch port (from provider) is shutting down itself when there are too much traffic going through. So the problem was solved by adding firewall rules which blocks access to DNS ports.
This happened randomly after i removed a nearby unmanaged switch between my AP and Mikrotik for client isolation.
I think its a power thing, the power doesn’t seem to suffice the crappy cable from 2nd floor (server) to 4th floor (AP).
I tried putting it back the way it was, & i got it solved. Still i need my client isolation tho.
ISPModem—MT—D-Link_Unmanaged_SW----ASUS AP----SW===UniFIAP2/4F
Apr/24/2020 11:46:26 interface,info ether4-(Hotspot Switch Port) link down
Apr/24/2020 11:46:26 route,debug,event Interface change
Apr/24/2020 11:46:26 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:46:26 route,debug,event status=UP
Apr/24/2020 11:46:26 route,debug,event mtu=1500
Apr/24/2020 11:46:26 route,debug,event Link down
Apr/24/2020 11:46:26 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:46:26 route,debug,event Update
Apr/24/2020 11:46:26 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:46:27 interface,info ether4-(Hotspot Switch Port) link up (speed 100M, full duplex)
Apr/24/2020 11:46:27 route,debug,event Interface change
Apr/24/2020 11:46:27 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:46:27 route,debug,event status=UP,RUNNING
Apr/24/2020 11:46:27 route,debug,event mtu=1500
Apr/24/2020 11:46:27 route,debug,event Link up
Apr/24/2020 11:46:27 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:46:27 route,debug,event Update
Apr/24/2020 11:46:27 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:23 interface,info ether4-(Hotspot Switch Port) link down
Apr/24/2020 11:47:23 route,debug,event Interface change
Apr/24/2020 11:47:23 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:23 route,debug,event status=UP
Apr/24/2020 11:47:23 route,debug,event mtu=1500
Apr/24/2020 11:47:23 route,debug,event Link down
Apr/24/2020 11:47:23 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:23 route,debug,event Update
Apr/24/2020 11:47:23 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:24 interface,info ether4-(Hotspot Switch Port) link up (speed 100M, full duplex)
Apr/24/2020 11:47:24 route,debug,event Interface change
Apr/24/2020 11:47:24 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:24 route,debug,event status=UP,RUNNING
Apr/24/2020 11:47:24 route,debug,event mtu=1500
Apr/24/2020 11:47:24 route,debug,event Link up
Apr/24/2020 11:47:24 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:24 route,debug,event Update
Apr/24/2020 11:47:24 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:38 hotspot,debug hotspot1: static host 192.168.9.79 removed: idle timeout
Apr/24/2020 11:47:43 interface,info ether4-(Hotspot Switch Port) link down
Apr/24/2020 11:47:43 route,debug,event Interface change
Apr/24/2020 11:47:43 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:43 route,debug,event status=UP
Apr/24/2020 11:47:43 route,debug,event mtu=1500
Apr/24/2020 11:47:43 route,debug,event Link down
Apr/24/2020 11:47:43 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:43 route,debug,event Update
Apr/24/2020 11:47:43 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:44 interface,info ether4-(Hotspot Switch Port) link up (speed 100M, full duplex)
Apr/24/2020 11:47:44 route,debug,event Interface change
Apr/24/2020 11:47:44 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:44 route,debug,event status=UP,RUNNING
Apr/24/2020 11:47:44 route,debug,event mtu=1500
Apr/24/2020 11:47:44 route,debug,event Link up
Apr/24/2020 11:47:44 route,debug,event interface=ether4-(Hotspot Switch Port)
Apr/24/2020 11:47:44 route,debug,event Update
Apr/24/2020 11:47:44 route,debug,event interface=ether4-(Hotspot Switch Port)